id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
36.820
|
LTE for 700 MHz digital dividend
|
TR
|
11.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.820/36820-b20.zip
|
The present document a technical report for the LTE for 700 MHz digital dividend work item. It is intended to define both FDD and TDD arrangements on the 698-806 MHz frequency band in Region 3.
|
36.822
|
LTE Radio Access Network (RAN) enhancements for diverse data applications
|
TR
|
11.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.822/36822-b00.zip
|
The present document constitutes the output of the initial evaluation phase for the work item “LTE RAN Enhancements for Diverse Data Applications” (LTE_eDDA). The document captures agreements and descriptions related to the evaluation methodology used, descriptions of enhancement proposals and their evaluation results, and conclusions and recommendations for further work within the scope of the LTE_eDDA work item.
|
36.823
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Carrier aggregation enhancements; User Equipment (UE) and Base Station (BS) radio transmission and reception
|
TR
|
11.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.823/36823-b01.zip
|
The purpose of this report is to summarize studies of radio requirements for the Base Station (BS) and User Equipment (UE) radio transmission and reception as part of the Rel-11 work on LTE Carrier Aggregation Enhancements.
|
36.824
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE coverage enhancements
|
TR
|
11.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.824/36824-b00.zip
|
The scope of this study item is given in [2].
|
36.826
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Relay radio transmission and reception
|
TR
|
11.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.826/36826-b30.zip
|
The present document is the technical report on the "Relays for LTE” work item [2]. The overall objective of the WI is to specify Relays for LTE in Rel-10 timeframe.
This document is intended to gather the relevant background information in order to address Relay Node (RN) requirements as well as propose suitable updates to the specifications under the responsibility of RAN4. RAN4 have agreed to focus on fixed RN.
|
36.828
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Further enhancements to LTE Time Division Duplex (TDD) for Downlink-Uplink (DL-UL) interference management and traffic adaptation
|
TR
|
11.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.828/36828-b00.zip
|
The scope of this study item is given in [2]
|
36.829
|
Enhanced performance requirement for LTE User Equipment (UE)
|
TR
|
11.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.829/36829-b10.zip
|
The objective of this study is to evaluate the feasibility and potential performance improvements of interference cancellation/mitigation techniques for LTE/ LTE-Advanced FDD and TDD UE receivers, based on realistic network scenarios. Scope of the work includes:
▪ Identify realistic deployment scenarios, traffic models, interference models, and performance metrics to evaluate the performance of advanced receiver to mitigate inter-cell interference.
- Evaluation should be based on realistic modelling of inter-cell interference, including both synchronous and asynchronous operations among macro eNBs, different precoders, ranks and powers applied over consecutive subframes, and effect of CRS and control channels to which different precoder is applied compared with data channels.
▪ Study and evaluate feasibility and potential gain by advanced receiver at link and system levels:
- Identify the scenarios and conditions where inter-cell interference mitigation is effective
- Identify the receiver structures that could be a baseline to specify performance requirement.
▪ Receiver structures targeting spatial domain interference mitigation such as IRC are to be considered as a starting point.
▪ Receiver structures targeted to TDM-eICIC are only to be studied under the eICIC enhancements WI.
▪ Details of interference modelling for performance requirements and conformance testing shall be specified in the WI phase. Some complexity considerations should be taken into account during the SI phase to avoid over simplified model later on that doesn’t reflect the performance benefits found.
|
36.833-1-07
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 7
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-07/36833-1-07-b00.zip
|
The present document is a technical report of the work item for LTE Advanced Carrier Aggregation in Band 7 which was approved at TSG RAN #53 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-1-38
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 38
|
TR
|
11.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-38/36833-1-38-b10.zip
|
The present document is a technical report of the work item for LTE Advanced Carrier Aggregation in Band 38 which was approved at TSG RAN #52 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-1-41
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 41
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-41/36833-1-41-b00.zip
|
The present document is a technical report of the LTE Advanced Carrier Aggregation in Band 41 work item which was approved at TSG RAN #52 [2]. The objective of this work item is to provide specification support for intra-band contiguous carrier aggregation in LTE TDD Band 41.
The report provides motivation, requirements and a list of recommended changes to the specifications.
|
36.837
|
Public safety broadband high power User Equipment (UE) for band 14
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.837/36837-b00.zip
|
The present document is the Technical Report on Public safety broadband high power User Equipment (UE) for Band 14 for Region 2.
The purpose of this TR is to study the radio requirements for Public safety broadband high power User Equipment (UE) as part of the Rel-11 work item for a new Power Class for Band 14 for Region 2. The normative requirements resulting from this TR will be addressed in the applicable release 11 Technical Specifications (TS)
|
36.839
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Mobility enhancements in heterogeneous networks
|
TR
|
11.1.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.839/36839-b10.zip
|
The present document is intended the capture the output of the Study Item on HetNet mobility improvements for LTE.
The study aims to look at various mobility improvements such as possible improvements to support seamless and robust mobility of users between LTE macro to pico cells in Heterogeneous networks, better strategies to identify and evaluate small cells, handover performance with and without eICIC features, improvements to re-establishment procedures etc. It is also expected to consider these in the context of Carrier aggregation in Home eNodeBs.
|
36.850
|
Inter-band carrier aggregation
|
TR
|
11.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.850/36850-b20.zip
|
The present document is a technical report for Inter-band Carrier Aggregation under Rel-11 time frame. The purpose is to gather the relevant background information and studies in order to address Inter-band Carrier Aggregation requirements.
This TR covers relevant background information and studies in order to address Inter-band Carrier Aggregation requirements for the Rel-11 band combinations in table 1-1.
Table 1-1: Release 11 inter-band carrier aggregation combinations
WI code
WI title
Class
LTE_CA_B3_B7
LTE Advanced Carrier Aggregation of Band 3 and Band 7
A3
LTE_CA_B4_B17
LTE Advanced Carrier Aggregation of Band 4 and Band 17
A2
LTE_CA_B4_B13
LTE Advanced Carrier Aggregation of Band 4 and Band 13
A1
LTE_CA_B4_B12
LTE Advanced Carrier Aggregation of Band 4 and Band 12
A2
LTE_CA_B5_B12
LTE Advanced Carrier Aggregation of Band 5 and Band 12
A3
LTE_CA_B7_B20
LTE Advanced Carrier Aggregation of Band 7 and Band 20
A1
LTE_CA_B2_B17
LTE Advanced Carrier Aggregation of Band 2 and Band 17
A1
LTE_CA_B4_B5
LTE Advanced Carrier Aggregation of Band 4 and Band 5
A1
LTE_CA_B5_B17
LTE Advanced Carrier Aggregation of Band 5 and Band 17
A3
LTE_CA_B3_B20
LTE Advanced Carrier Aggregation of Band 3 and Band 20
A1
LTE_CA_B8_B20
LTE Advanced Carrier Aggregation of Band 8 and Band 20
A3
LTE_CA_B3_B5
LTE Advanced Carrier Aggregation of Band 3 and Band 5
A1
LTE_CA_B4_B7
LTE Advanced Carrier Aggregation of Band 4 and Band 7
A3
LTE_CA_B11_B18
LTE Advanced Carrier Aggregation of Band 11 and Band 18
A5
LTE_CA_B1_B18
LTE Advanced Carrier Aggregation of Band 1 and Band 18
A1
LTE_CA_B1_B19
LTE Advanced Carrier Aggregation of Band 1 and Band 19
A1
LTE_CA_B1_B21
LTE Advanced Carrier Aggregation of Band 1 and Band 21
A5
LTE_CA_B3_B8
LTE Advanced Carrier Aggregation of Band 3 and Band 8
A2
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
The contents of this TR is moved to/provided in TR 36.852-11 Release 11 [24].
|
36.852-11
|
LTE Advanced inter-band Carrier Aggregation (CA) (2DL/1UL)
|
TR
|
11.1.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.852-11/36852-11-b11.zip
|
The present document is a technical report for Inter-band Carrier Aggregation under Rel-11 time frame. The purpose is to gather the relevant background information and studies in order to address Inter-band Carrier Aggregation requirements.
This TR covers relevant background information and studies in order to address Inter-band Carrier Aggregation requirements for the Rel-11 band combinations in table 1-1.
Table 1-1: Release 11 inter-band carrier aggregation combinations
WI code
WI title
Class
LTE_CA_B3_B7
LTE Advanced Carrier Aggregation of Band 3 and Band 7
A3
LTE_CA_B4_B17
LTE Advanced Carrier Aggregation of Band 4 and Band 17
A2
LTE_CA_B4_B13
LTE Advanced Carrier Aggregation of Band 4 and Band 13
A1
LTE_CA_B4_B12
LTE Advanced Carrier Aggregation of Band 4 and Band 12
A2
LTE_CA_B5_B12
LTE Advanced Carrier Aggregation of Band 5 and Band 12
A3
LTE_CA_B7_B20
LTE Advanced Carrier Aggregation of Band 7 and Band 20
A1
LTE_CA_B2_B17
LTE Advanced Carrier Aggregation of Band 2 and Band 17
A1
LTE_CA_B4_B5
LTE Advanced Carrier Aggregation of Band 4 and Band 5
A1
LTE_CA_B5_B17
LTE Advanced Carrier Aggregation of Band 5 and Band 17
A3
LTE_CA_B3_B20
LTE Advanced Carrier Aggregation of Band 3 and Band 20
A1
LTE_CA_B8_B20
LTE Advanced Carrier Aggregation of Band 8 and Band 20
A3
LTE_CA_B3_B5
LTE Advanced Carrier Aggregation of Band 3 and Band 5
A1
LTE_CA_B4_B7
LTE Advanced Carrier Aggregation of Band 4 and Band 7
A3
LTE_CA_B11_B18
LTE Advanced Carrier Aggregation of Band 11 and Band 18
A5
LTE_CA_B1_B18
LTE Advanced Carrier Aggregation of Band 1 and Band 18
A1
LTE_CA_B1_B19
LTE Advanced Carrier Aggregation of Band 1 and Band 19
A1
LTE_CA_B1_B21
LTE Advanced Carrier Aggregation of Band 1 and Band 21
A5
LTE_CA_B3_B8
LTE Advanced Carrier Aggregation of Band 3 and Band 8
A2
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.871
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Downlink Multiple Input Multiple Output (MIMO) enhancement for LTE-Advanced
|
TR
|
11.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.871/36871-b00.zip
|
This TR collects the work done under the Study Item “Downlink MIMO Enhancement for LTE-Advanced” [2].
|
37.803
|
Universal Mobile Telecommunications System (UMTS) and LTE; Mobility enhancements for Home Node B (HNB) and Home enhanced Node B (HeNB)
|
TR
|
11.2.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.803/37803-b20.zip
|
This document captures the results of the study item on H(e)NB enhanced mobility in RP-110456[2]. It identifies the existing mobility functions for UMTS and LTE, the use cases and requirements for enhancements, and reviews and compares scenarios and techniques for enhancement of the mobility functionality. Aspects of RAN sharing related to H(e)NB mobility are also included.
|
37.804
|
Study on UMTS/LTE in 900 MHz band and coexistence with 850 MHz band
|
TR
|
11.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.804/37804-b10.zip
|
The present document is a technical report of the UMTS/LTE in 900 MHz band study item, which was established at TSG RAN#52. The objective of the study item is to study how we can provide UTRA and E-UTRA specification support for FDD in the 900 MHz band in Japan, and also to study the possible harmonized specification support between the 900 MHz band in Japan and 900 MHz band in Korea.
|
37.806
|
Extending 850 MHz study Technical Report
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.806/37806-b00.zip
|
The present document contains the findings of the Study Item [28] of a more harmonised frequency variant approach within the frequency range of 806-849/851-894 MHz.
|
37.809
|
Evolved Universal Terrestrial Radio Access (E-UTRA) medium range and Multi-Standard Radio (MSR) medium range / local area Base Station (BS) class requirements
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.809/37809-b00.zip
|
The present document is the Technical Report for the Work Item on E-UTRA medium range and MSR medium range/local area BS class requirements.
|
37.812
|
Radio Frequency (RF) requirements for Multi-band and Multi-standard radio (MB-MSR) Base Station (BS)
|
TR
|
11.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.812/37812-b30.zip
|
The present document is the Technical Report for the Work Item on Multi-band and Multi-standard radio BS requirements.
|
37.868
|
RAN Improvements for Machine-type Communications
|
TR
|
11.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.868/37868-b00.zip
|
The present document is intended to capture the output of the Study Item on RAN Improvements for Machine-type Communications.
The study aims to study the traffic characteristics of different M2M applications with machine-type communications and define new traffic models based on these findings. RAN enhancements for UTRA and EUTRA to improve the support of machine-type communications based on the SA1 requirements should be studied.
The RAN improvements should enable or improve the usage of RAN resources efficiently, and/or reduce the complexity when a large number of machine-type communications devices possibly need to be served based on the existing features as much as possible. Meanwhile, minimize the changes of existing specifications and the impaction of Human-to-Human terminals in order to keep the complexity related to M2M optimizations at a minimum level.
|
44.160
|
General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol Iu mode
|
TS
|
11.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.160/44160-b00.zip
| |
45.860
|
Signal Precoding Enhancements for EGPRS2 DL
|
TR
|
11.5.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.860/45860-b50.zip
|
The present document contains the results from the 3GPP study item on Signal Precoding Enhancements for EGPRS2 DL, SPEED.
The following is covered by the study:
• Objectives for the study
• Common assumptions to be used in the evaluation
• Technical work and performance evaluations based on the objectives
|
21.902
|
Evolution of 3GPP system
|
TR
|
10.0.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.902/21902-a00.zip
|
The present document describes a long term, high level roadmap, intended to guide the future work of 3GPP. It is focussed on items pertinent to the evolution of 3GPP specifications, and identifies concepts and trends to be considered by 3GPP when defining future work items. It does not contain details of proposed technologies, rather it contains pointers to direct the activities of the appropriate TSGs in elaborating future releases of the 3GPP standard. As a result, not all of the topics covered herein are within the remit of 3GPP to discuss, and description of such items will not be extensively developed. E.g. Spectrum is an ITU-R/WRC issue and therefore outside the scope of 3GPP. The document is designed to be a "living document" and will be updated accordingly over its lifetime in order to reflect future developments and innovations.
|
22.813
|
Study of use cases and requirements for enhanced voice codecs for the Evolved Packet System (EPS)
|
TR
|
10.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.813/22813-a00.zip
|
This study defines and analyses the new use cases in the environment of EPS and its future services. It evaluates how much the newly defined requirements are met by the already available codecs in 3GPP releases prior to Rel-10. Potential new requirements for voice codecs are elaborated in due course.
Specifically, the objective of this study item is to:
• Identify service and system requirements,
• Identify high level requirements,
• Assess the existing codecs in respect to identified requirements,
• Define a strategy for EPS voice codec(s) standardization,
• Identify some use cases for enhanced voice and mixed content conversational multimedia service for EPS (see Annex A).
Starting from Rel-8 timeframe, MTSI as a conversational multimedia service is provided over EPS. MTSI is the main service for which the enhancements are targeted. This does not however exclude the enhanced service requirements from being later adopted to other services where such enhancements are needed and are found suitable.
|
22.814
|
Location Services (LCS) support in Evolved Packet Core (EPC) for non-3GPP accesses
|
TR
|
10.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.814/22814-a00.zip
|
This Technical Report (TR) presents the results of the Study on LCS support for non-3GPP accesses.
One main concept of EPC is to support a variety of different access systems (existing and future) ensuring mobility and service continuity between these access systems. In that perspective, the LCS support for non 3GPP accesses should be also taken into account. However, historically, TS 22.071 has been applicable only to 3GPP accesses and any new requirements for non 3GPP accesses have not been discussed yet.
Therefore we need to consider how to support LCS in EPC for non 3GPP accesses, e.g. 3GPP2 and WiMAX. Supporting LCS in EPC for non 3GPP access does not necessarily mean that all positioning methods available in various kinds of non 3GPP accesses should be supported in EPC or inventing new positioning methods for other accesses. However, how to realize the presentation of location information in EPC when users are connected in non 3GPP accesses should be at least taken into account. In addition, the service scenarios should be discussed whether new service requirements are needed for the users camping on non 3GPP accesses through EPC.
This work will examine whether requirements in TS 22.071 would be applicable for non 3GPP accesses and specify new service requirements for the users connected to non 3GPP accesses through EPC.
Consideration will be given, but not limited, to the following:
• High level requirements of LCS support for non 3GPP accesses;
• Location information provided to the LCS client for non 3GPP accesses;
• QoS requirements of LCS support for non 3GPP accesses.
• Priority between different LCS services for non 3GPP accesses.
• Privacy requirements of LCS support for non 3GPP accesses.
• Periodic location report of LCS services for non 3GPP accesses.
• Impact on the LCS client and the LCS server to support LCS services for non 3GPP accesses
|
22.893
|
Advanced requirements for IP interconnect
|
TR
|
10.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.893/22893-a00.zip
|
This document studies the technical requirements for carrier grade inter-operator IP Interconnection of Services for the support of Multimedia services provided by IMS and for legacy voice and video PSTN/PLMN services transported over IP infrastructure (e.g. VoIP). These requirements should take into account the new and developing, convergent interconnect models currently being developed outside 3GPP.
Requirements should fulfil:
• Identification of the technical requirements for IP Service Interconnection (service control and user plane aspects) between Service Providers.
• Identification of requirements for the Stage 2 & 3 work to identify relevant existing specifications, initiate enhancements and the development of the new specifications as necessary.
• Supporting of IP Service Interconnection models as defined by other bodies (e.g. GSMA, ETSI, ITU-T).
|
23.824
|
IP-Short-Message-Gateway (IP-SM-GW) enhancements for interworking with Open Mobile Alliance (OMA) Converged IP Messaging (CPM)
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.824/23824-a00.zip
|
The present document specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities (TS 23.228 [9]). These include (but are not limited) to:
1 Enhancements to the HSS;
2 Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
3 Authentication of service usage and registration;
4 Transfer of UE Terminated SMS, UE Originated SMS, and Delivery reports;
5 Mechanisms to handle SMS when there is more than one IP connection active with the UE, etc.
The document also specifies the capabilities and enhancements needed to support the service level interworking for the Short Message service as defined in the TS 23.040 [2] and in this specification and the Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0-20070816-C [12]. The features supported from the IM specification are limited to the exchange of short or large immediate messages in pager mode.
NOTE: The page-mode immediate message as defined in TS 24.247[14] is considered as a subset of OMA-TS-SIMPLE-IM-V1_0-20070816-C [12].
The service requirements are described in TS 22.340 [18].
|
23.829
|
Local IP Access and Selected IP Traffic Offload (LIPA-SIPTO)
|
TR
|
10.0.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.829/23829-a01.zip
|
Support of Local IP access for the Home (e)NodeB Subsystem and of Selected IP traffic offload for the Home (e)NodeB Subsystem and for the macro layer network is required in TS 22.220 [3] and TS 22.101 [2].
This Technical Report describes the following functionalities:
- Local IP access – LIPA – to residential/corporate local network for Home (e)NodeB Subsystem;
- Selected IP traffic offload – SIPTO – (e.g. Internet traffic) for Home (e)NodeB Subsystem;
- Selected IP traffic offload (e.g. Internet traffic, corporate traffic) for the macro network (3G and LTE only).
The report is intended to analyse the architectural aspects to achieve these objectives and to gather the technical content until it can be included in the relevant technical specifications.
|
23.831
|
IP Multimedia Subsystem (IMS) service continuity; Inter-UE transfer enhancements; Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.831/23831-a00.zip
|
This technical report intends to develop enhancements to Rel-9 IMS Service Continuity in TS 23.237 [2], specifically in the functional area of Inter-UE Transfer. The main objective is to provide enhancements to mobility of media flows of a session between different UEs (Inter-UE Transfer) with respect to the following aspects:
- Extension of Inter-UE Transfer and Collaborative Session capabilities specified in Rel-09 to multiple UEs belonging to different IMS subscriptions under the same operator.
- Establishment of a Collaborative Session at session setup.
- Support for control of media components of a Collaborative Session by more than one UE simultaneously.
- Transfer of control of a Collaborative Session.
- Controller initiated media modification on a Controllee UE (e.g. video resolution).
- Discovery of ongoing IMS multimedia sessions on different UEs.
- Inter-UE Transfer initiated by the target UE when:
- the target UE belongs to the Collaborative Session but it is not a Controller UE;
- the target UE does not belong to the Collaborative Session and wants to join;
- Inter-UE Transfer is performed without establishing a Collaborative Session.
- Replication of an ongoing multimedia session from one UE on another UE.
- Inter-UE Transfer between UEs connected to the IMS via an IP-CAN and ICS entities that provide interworking with UEs in the CS Domain.
- Execution of MMTEL services for Collaborative Sessions.
This document contains the results of an assessment of alternative architectures to support Inter-UE Transfer enhancements.
|
23.832
|
IP Multimedia Subsystem (IMS) aspects of architecture for Home Node B (HNB); Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.832/23832-a00.zip
|
This Technical Report describes an IMS capable HNB SubSystem (the HNB and the HNB Gateway) as an optional capability of HNB that allows e.g. an operator to offload CS traffic to the IMS. The HNB and HNB Gateway are described in TR 23.830 [5], and the capabilities of these network elements are assumed by this TR.
To achieve this and to satisfy the related requirements and use cases captured in TS 22.220 [2], the objective is to investigate the following:
• an architecture to enable IMS capable HNB Subsystem to use the IMS for CS terminals using a corresponding equivalent IMS services (voice service in IMS Multimedia Telephony);
• the impacts of the IMS capable HNB Subsystem to idle mode mobility for all supported UE types (e.g. IMS registration/de-registration);
• service continuity at least in the direction from IMS capable HNB Subsystem to macro network;
• support for pre-Rel‑9 CS and IMS UEs when using IMS capable HNB Subsystem.
The TR will analyze solutions for the related architectural issues and capture the conclusions.
|
23.834
|
Study on General Packet Radio Service (GPRS) Tunelling Protocol (GTP) based S2b; Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.834/23834-a00.zip
|
The objective of this feasibility study is to investigate solutions and benefits for supporting a new GTP option for S2b network based mobility.
The study will develop the stage 2 message flows necessary to support S2b based on GTP and mobility between S5/S8 based on GTP and S2b based on GTP.
|
23.845
|
Study on User Data Convergence (UDC) evolution
|
TR
|
10.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.845/23845-a00.zip
|
The present document is addressing a number of topics regarding User Data Convergence evolution. Some of these topics were identified in the Rel9 work but have been delayed, others are new.
These topics are largely independent of each other and are studied separately in this document.
They will be normally addressed through the following steps:
- a description of the topic to be addressed with its interest, the associated requirements to cover or issues to be solved
- a description of the alternative solutions including their impact on 3GPP specifications
- a comparison of the solutions
- a conclusion with recommendations.
|
23.856
|
Single Radio Voice Call Continuity (SRVCC) enhancements; Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.856/23856-a00.zip
|
SR-VCC has been standardized in Release 8 TS 23.216 [3] to provide seamless continuity when UE handovers from E-UTRAN to UTRAN/GERAN.
This document contains the results of feasibility study of the requirements and the alternative solutions to improve the handover performance of SRVCC.
The objective of this study is as follows:
- Evaluating the performance of current Rel‑8 SRVCC solution;
- Enhancing the performance of the SR-VCC Flow Break with regard to the roaming and non-roaming case;
- Enhancing SR-VCC handover performance while minimizing the impacts on the network architecture for the directions
- from EUTRAN to UTRAN/GERAN; and
- from UTRAN to UTRAN/GERAN.
|
23.860
|
Enabling coder selection and rate adaptation for UTRAN and E-UTRAN for load adaptive applications; Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.860/23860-a00.zip
|
The system enhancements to enable codec rate adaptation at voice call setup over E-UTRA was standardized in Rel-9 in TS 23.401 [2].
The scope of this document is to study and specify enhancements to existing codec selection and codec rate adaptation based on network loading conditions and operator policies over UTRA and E-UTRA. Potential enhancements are definition of the signalling and interfaces enabling:
- To perform codec selection based on network loading conditions and operator policies during call establishment phase over both UTRA and E-UTRA;
- To perform codec data rate adaptation (if possible for the selected codec and needed by the service) based on network loading conditions during call establishment phase over UTRA;
- To perform codec data rate adaptation (if possible for the selected codec and needed by the service) for non-voice RTP-based services based on network loading conditions at call setup over E-UTRA;
- To perform codec data rate adaptation (if possible for the selected codec and needed by the service) based on network loading indications during an on-going call over both UTRA and E-UTRA;
- Support of codec rate adaptation by IMS Core Network entities (e.g., MGCF/MGW, IBCF/TrGW, etc.);
- Setting of Maximum Bit Rate (MBR) to be greater than the Guaranteed Bit Rate (GBR) over E-UTRA.
The solutions can be moved to normative specifications independently of each other once the study on the particular solution has been concluded.
|
23.886
|
Feasibility Study of Single Radio Video Call Continuity (vSRVCC); Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.886/23886-a00.zip
|
The objective of the feasibility study is to investigate a solution for supporting single radio the video call continuity from E-UTRAN/HSPA to UTRAN-CS based on the Rel-8/9 Single Radio Voice Call Continuity (SRVCC) architecture as specified in TS 23.216 [2] and TS 23.237 [3], and study the mechanisms to resolve the key issues. It is not expected that the SRVCC architecture will be modified unless any of the key issues cannot be resolved with the current architecture.
The study will be performed to the scenarios where IMS session using bidirectional voice and synchronised video such as defined in TS 22.173 [4], originated in E-UTRAN/HSPA and the UE moves to UTRAN and continues the service over UTRAN in the CS domain.
The video call continuity from E-UTRAN/HSPA to GERAN is not supported.
|
23.889
|
Local Call Local Switch (LCLS) system impacts; Feasibility study
|
TR
|
10.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.889/23889-a00.zip
|
The present document provides a study into the Core Network impacts for providing a solution for Local Call Local Switching. The document analyses and evaluates different solutions to determine the benefits provided compared to the identified impacts.
Specific considerations are given to the following areas:-
- Sending of correlation information between the two legs of the call to the BSS
- Triggering to enable/release Local Call Local Switch (e.g. based on activation of Supplementary Services, etc.)
- Support of existing Supplementary Services
- Support of existing Lawful Intercept functionality
- Impacts to the user plane handling on the A-interface
- Impacts to the MSC-S – MGW Interface (Mc Interface)
- Impacts to the MSC-S – MSC-S Interface (Nc Interface)
The solution(s) considered for local call local switch should keep the core network impacts to a minimum, e.g. the impacts on the nodal functions, existing call flows, call establishment and call release.
The contents of this report when stable shall determine the modifications to existing core network specifications.
|
23.894
|
System enhancements for the use of IP Multimedia Subsystem (IMS) services in local breakout and optimal routeing of media
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.894/23894-a00.zip
|
This study intends to investigate the general problem of system enhancements for the use of IMS services in local breakout and optimal routeing of media.
In particular the above issues will be addressed identifying
- solutions for the home operator to control
- whether the IMS user may connect to a PDN in the visited network, and
- whether connections to PDNs provided from the home and visited network may exist in parallel;
- solutions to enable the IMS network to be aware of whether local breakout can be invoked or not;
- solutions to allow the home operator to determine which of the IMS sessions (for a given UE) can be handled in local breakout and which in home routed mode, and what information (e.g. operator's policies, customer's subscription profile, UE connectivity, and location of the remote end terminal/service) is needed for the decision;
- solutions to allow the UE to concurrently use IMS services through local breakout and other IMS services through home routeing;
- the feasibility of having the local breakout option in IMS service nodes:
- is there a need for a P-CSCF at both PDN accesses?
- if one P-CSCF is enough, what requirements are there for connectivity between the PDNs?
- if methods are necessary to discover an additional P-CSCF in the visited network after the UE has moved to the visited network, even if the network-layer mobility mechanisms can sustain IP connectivity to the previously discovered P-CSCF in the home network;
- the exact location of the decision point in the home network whether to use local breakout (application or delegated to IP-CAN);
- solutions for SIP/SDP signalling related to the use of IMS services through local breakout.
- interactions with network entities such as NAT (as specified in TS 23.228 [8]) when providing IMS services through local breakout;
- interactions with and support of PCC to provide IMS services through local breakout;
- security implications if there is need for multiple P-CSCFs per UE.
Moreover:
- describing a set of scenarios where the selection of an alternative media path (i.e., different to the signalling path) provides benefits to IMS operators by reducing the number of network entities in the media path;
- providing requirements for suitable mechanisms to achieve optimal media routeing;
- analysing the potential solution(s) to solve those scenarios in line with IMS procedures, while taking into account any impact of extensions required to existing functions/procedures (e.g., NAT, transcoding, Security, PCC, BCF, LI, etc.);
- reducing the number of options for solving the same requirement and agree on a preferred solution.
In the end this study will provide conclusions with respects to what further specification work is required in order to fulfil the requirements for the use of IMS services through local breakout and achieve optimal routeing of media.
|
24.837
|
IP Multimedia (IM) Core Network (CN) subsystem inter-UE transfer enhancements; Stage 3
|
TR
|
10.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.837/24837-a00.zip
|
This technical report intends to develop enhancements to Rel-9 IMS service continuity stage 3 within the scope of 3GPP TS 24.237 [6], specifically in the area of inter-UE transfer. This technical report serves as a collection and a base for decision on alternative solution proposals for the different enhancement to Rel-9 IMS service continuity stage 3.
This technical report will be used to move the agreed solutions into the main specifications, once the content has stabilized.
Editor's Note: This TR reflects those inter-UE transfer issues, which are currently reflected in 3GPP TR 23.837. As currently SA2 did not move any of the Rel-10 inter-UE transfer topics to 3GPP TS 24.237, it is not sure which of these features will be finally part of Rel-10. The content of this TR will be scoped to those features, which SA2 decides to make part of the Rel-10 version of 3GPP TS 24.237.
|
25.317
|
High Speed Packet Access (HSPA); Requirements on User Equipments (UEs) supporting a release-independent frequency band combination
|
TS
|
10.1.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.317/25317-a10.zip
|
The present document specifies requirements on UEs supporting a frequency band combination that is independent of release. TSG-RAN has agreed that the standardisation of new frequency band combinations of DB-DC-HSDPA may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a band combination of operation that is specified in a later release, it is necessary to specify some extra requirements.
For example, Band I-XI combination for DB-DC-HSDPA (referred to as DB-DC-HSDPA configuration 4 in [2]) is contained in the Release 10 specifications. In order to implement a UE conforming to Release 9 but supporting this configuration, it is necessary for the UE to additionally conform to some parts of the Release 10 specifications, such as the radio frequency and radio resource management requirements for the configuration.
All DB-DC-HSDPA configurations are fully specified in this release of the specifications. The present document does not contain any requirements for UEs supporting DB-DC-HSDPA configurations independent of release.
|
25.864
|
Downlink configurations for Four-carrier High Speed Download Packet Access (4C-HSDPA)
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.864/25864-a00.zip
|
The present document is intended to maintain the list of 4C-HSDPA downlink configurations in the context of the work item “For carrier HSDPA” [2]. Each downlink configuration is composed of the frequency band(s) and the number of downlink adjacent carriers in each band.
In addition, the present document also captured the framework to specify the Rx core requirements for 4C-HSDPA.
|
25.865
|
Improvements of distributed antenna for 1.28 Mcps TDD
|
TR
|
10.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.865/25865-a00.zip
|
The present document is intended to capture the output of the study item on improvements of distributed antenna for 1.28Mcps TDD, which was approved at TSG RAN#47. The objective of this study item is to study the potential enhancement techniques for the distributed antenna.
|
29.816
|
Study on PCRF failure and restoration
|
TR
|
10.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.816/29816-a00.zip
|
The present document contains the results of the study on PCRF failure and restoration.
Target failure and recovery scenarios are detailed; the following scenarios are addressed (incl. roaming):
- Single PCRF deployment (covering also the equivalent scenario of multiple PCRFs with a fixed assignment of PCRFs);
- Multiple PCRFs and the DRA is used;
PCRF node failures of different type (e.g. complete outage, loss of dynamic data) and the aspect of reliability in signaling connections will be studied.
Functional requirements for solutions to handle such cases in a standardized way are defined, considering the network elements PCRF, PCEF, BBERF, AF and DRA and taking operators’ preferences into account (e.g. minimal impact on user experience versus maximal control/minimum risk for the operator).
The study describes the potential solutions, which include procedures and signalling between PCRF and other PCC related network nodes, and procedures and signalling between Diameter clients (i.e. PCEF/BBERF/AF) and the DRA.
Per solution the impacted 3GPP specifications and the necessary changes therein are listed.
The study report finally evaluates the solutions and draws conclusions with respect to the type of solutions and their feasibility in terms of implementation effort/complexity.
|
30.820
|
Telecommunication management; Project scheduling and open issues for SA5, Release 10
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.820/30820-a00.zip
|
The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC.
Status list of Work items can be found in Annex A of the present document.
|
31.828
|
UICC access to IMS
|
TR
|
10.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.828/31828-a00.zip
| |
32.825
|
Telecommunication management; Charging management; Rc reference point study
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.825/32825-a00.zip
|
The present document is a study report for Rc reference point supported by ABMF (Accounting Balance Management Function).
The study covers the drive and requirement analysis, existing architectures, key issues analysis, recommandations, etc.
The study aims at producing recommendations for the following aspects:
- 3GPP work item and specification;
- Charging requirements and principles;
- Charging architecture and Rc networking scenarios;
- Charging data and protocols;
- Technical recommandations
|
32.826
|
Telecommunication management; Study on Energy Savings Management (ESM)
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.826/32826-a00.zip
|
In the context of 3GPP Self-Organizing Networks (SON), this study investigates about Energy Savings Management in LTE / SAE networks, with the objective to contribute to the protection of our environment and the environment of future generations. One is forced to admit that, in addition, network energy consumption reduction will enable mobile network operators to save their OPEX.
The present document covers:
• Motivations of mobile network operators for the introduction of energy savings control mechanisms
• Analysis of possible mechanisms for Energy Savings Management via OAM
• Usage of existing IRPs to be used for the purpose of Energy Savings Management
• Identification of new IRP to be potentially defined
• Conclusions
• Recommendations on Energy Savings Management
• Identification of items for standardization as a result of this study
|
32.827
|
Telecommunication management; Integration of device management information with Itf-N
|
TR
|
10.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.827/32827-a10.zip
|
UE Management provides the network operator with the opportunity to manage and monitor the actual user experience of their subscribers via the remote management of the user equipement.
UE management over Itf-N provides the ability to minimize the complexibity and reduce the OPEX and CAPEX costs of managing the UE by the ingegrated management capabilities.
UE management over Itf-N provides the capabilites for service provisioning and personalized subscriber profile backup for the UE via DMS, to improve the subscriber satisfaction and thus contribute to subscriber retention.
The UE can provide measurments of the quality of radio network and the actual service being delivered to the user, collection of these measurements via Itf-N can be used by Centralized SON or manual optimization.
This document is to study UE management over Itf-N, including the following aspects:
- Subscriber profile configuration over Itf-N;
- Collection of UE measurements over Itf-N. Includes protocol definition over Itf-N and study of appropriate UE measurements defined in RAN WGs;
- Retrieval of UE measurement logs over Itf-N. Includes file format definition over Itf-N and study of appropriate solutions for measurement logging policy configuration and log retrieval over Itf-N.
To support the UE measurement log collection via Itf-N, this document will study how to support the UE measurement log transfer mechanisms measurement logging policy configuration and measurement log retrieval by DMS using existing UE management protocol procedures, and identify a suitable protocol from a network management perspective. This document will also study how to do the mapping between the selected protocol and Itf-N.
|
32.828
|
Telecommunication management; Study on alignment of 3GPP generic Network Resource Model (NRM) Integration Reference Point (IRP) and the TeleManagement Forum (TMF) Shared Information/Data (SID) model
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.828/32828-a00.zip
|
The present document studies how to allow the two organizations (3GPP and TMF) to evolve their respective NRMs and SID in a manner that they would become aligned to support consistent and integrated management of mobile and fixed networks. This study:
• identifies the non-aligned, contradicting or overlapping parts between NRMs and SID
• identifies the non-aligned, contradicting or overlapping parts regarding specification methodology
• proposes possibilities to align the parts identified above;
• ensures that the proposal allows usage of the 3GPP Generic NRM IRP independently of SID
• ensures that the proposal allows usage of mobile specific NRMs to be used as they are
• drives the alignment process with TMF
• identifies any required changes in the 3GPP specifications
• identifies required changes in the TMF specifications to be communicated to the TMF
• ensures that 3GPP remains full owner of the aligned part of the NRM specifications
• defines a procedure how aligned specifications can be maintained and updated in a consistent manner
Special emphasis has been given to the borderline between generic and harmonized part and the network technology specific parts of the models. In case new requirements had been identified during the alignment process, they have been taken into account as well.
It is not intended to add the mobile specific parts of the 3GPP Network Resource Models to the TMF SID.
These model aspects are published by 3GPP only. Interface aspects (e. g. the Alarm IRP) are outside of the scope of this Study.
|
32.829
|
Telecommunication management; Study on alignment of 3GPP alarm Integration Reference Point (IRP) and TeleManagement Forum (TMF) Interface Program (TIP) fault management
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.829/32829-a00.zip
|
The present document collects, compares and analyzes the specifications of Fault Management (FM) as defined by 3GPP and TMF. These two organizations have both a complete set of FM specifications consisting of requirement, technology-independent and solution set specification for
- Fault Management interface – operations and notifications and
- Alarm content
The present documentidentifies similarities and differences of the Fault Management capabilities in 3GPP and TMF and provides recommendations to align these capabilities.
|
32.831
|
Telecommunication management; Study on alignment of 3GPP Performance Management (PM) and TeleManagement Forum (TMF) Interface Program (TIP) Performance Management
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.831/32831-a00.zip
|
The present document provides consistent and aligned PM and PM interfaces in 3GPP and TMF. The present document:
• identifies similarities and differences of the PM capabilities in 3GPP and TMF TIP PM BA;
• proposes enhancements to 3GPP PM solutions for converged networks and to satisfy TMF TIP PM BA requirements;
• identifies any required changes in the 3GPP specifications;
• identifies any required changes in the TMF specifications (to be communicated to TMF).
Backwards compatibility of the PM IRP should be maintained as much as possible by re-using existing specifications to the maximum extent.
The counter collected by each of the Network Elements (NE) and the definition of those are NE specific and there is no intention to harmonize those.
However KPIs with a network view should be explored.
|
32.832
|
Telecommunication management; Study on alarm correlation and alarm root cause analysis
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.832/32832-a00.zip
|
The present document:
• defines the management services offered by Alarm Correlation (AC) process and alarm root cause analysis (ARCA) process;
• Identifies the benefits of the AC process and ARCA process from views of network operators;
• Identifies the possible locations of the AC and ARCA processes within the IRP framework.
• Identifies possible IRP standard solutions, including enhancement of existing IRP standard solutions.
|
34.172
|
Terminal conformance specification; Assisted Global Navigation Satellite Systems (A-GNSS); Frequency Division Duplex (FDD)
|
TS
|
10.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.172/34172-a20.zip
|
The present document specifies the measurement procedures for the conformance test of the minimum performance requirements for FDD mode of UTRA user equipment (UE) that supports Assisted Global Navigation Satellite Systems (A-GNSS). It includes the measurement procedures for the conformance test of both UE‑based and UE‑assisted A‑GNSS. It excludes performance requirements for UEs where the only A-GNSS supported is A-GPS L1C/A which are specified in TS 34.171 [26].
Tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the "definition and applicability" part of the test.
|
36.807
|
Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.807/36807-a00.zip
|
The purpose of the present document is to summarize the study of radio requirements for the User Equipment (UE) radio transmission and reception as part of the Rel-10 work item on;
a) Carrier Aggregation for LTE (CA)
b) Enhanced DL Multiple Antenna Transmission for LTE (DLMA)
c) UL Multiple Antenna transmission for LTE (ULMA)
d) Fixed Wireless CPE RF Requirements (CPE)
|
36.808
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Carrier Aggregation; Base Station (BS) radio transmission and reception
|
TR
|
10.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.808/36808-a10.zip
|
The purpose of this TR is to summarize the study of radio requirements for the Base Station (BS) radio transmission and reception as part of the Rel-10 work item on Carrier Aggregation for LTE (CA).
|
36.811
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Adding 2 GHz band LTE Frequency Division Duplex (FDD) (Band 23) for Ancillary Terrestrial Component (ATC) of Mobile Satellite Services (MSS) in North America
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.811/36811-a00.zip
|
The present document is a technical report for Adding 2 GHz LTE for ATC of MSS in North America work item, which was approved at 3GPP TSG RAN#47 [2]. The objective of this work item is to add the 2 GHz band LTE for ATC of MSS in North America to the appropriate 3GPP core specifications for LTE FDD networks. In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, study results and specification recommendations.
|
36.812
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE TDD 2600MHz in US work item Technical Report
|
TR
|
10.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.812/36812-a10.zip
|
The present document is a technical report of the LTE TDD in 2600MHz for US work item which was approved at TSG RAN #47 [2]. The objective of this work item is to provide specification support for LTE TDD in the 2496 to 2690MHz band in the US.
The report provides motivation for requirements and a list of recommended changes to the specifications.
|
36.813
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE L-Band Technical Report
|
TR
|
10.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.813/36813-a10.zip
|
The present document is a technical report for “Adding L-Band LTE for ATC of MSS in North America” work item, which was approved at 3GPP TSG RAN#48 [2]. The objective of this work item is to add L-Band to the appropriate 3GPP core specifications for LTE FDD networks. In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, study results and specification recommendations.
|
36.817
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Uplink multiple antenna transmission; Base Station (BS) radio transmission and reception
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.817/36817-a00.zip
|
The purpose of this TR is to summarize the study of radio requirements for the Base Station (BS) radio transmission and reception as part of the Rel-10 work item on Uplink Multiple Antenna Transmission for LTE (LTE UL MIMO).
|
37.801
|
UMTS-LTE 3500 MHz Work Item Technical Repor
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.801/37801-a00.zip
|
The present document is a technical report of the UMTS-LTE 3500 MHz work item, which was established at TSG RAN#38. The objective of the work item is to study current band plans in the frequency bands 3.4-3.6 GHz and 3.6-3.8 GHz, where they exist, with respect to feasibility for WCDMA as well as LTE. For these current band plans, suitable band arrangements, which are adopted by regulators, shall be identified for the purpose of developing specifications, without excluding other future arrangements.
|
37.802
|
Multi-standard radio Base Station (BS) Radio Frequency (RF) requirements for non-contiguous spectrum deployments
|
TR
|
10.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.802/37802-a10.zip
|
The present document is the technical report for the work item on Multi-standard radio Base Station RF requirements for non-contiguous spectrum deployments, which was approved at TSG RAN#48. The objective of the WI is to specify RF requirements for MSR specifications such that common RF components can be used for multi-RAT deployments where more than one spectrum block is in use, and where the blocks are non-contiguous in frequency within a band.
|
51.010-5
|
Mobile Station (MS) conformance specification; Part 5: Inter-Radio-Access-Technology (RAT) (GERAN / UTRAN) interaction Abstract Test Suite (ATS)
|
TS
|
10.21.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-5/51010-5-al0.zip
|
The present document specifies the Abstract Test Suites (ATS) and partial IXIT proforma for the Network Layer (Layer 3) at the mobile radio interface of the GSM/3GPP mobile stations (MS) conforming to the TSs for Layer 3, for the digital cellular telecommunications systems.
The present document is valid for MS implemented according to R99, 3GPP Release 4, Release 5, Release 6, Release 7, Release 8, Release 9 or Release 10.
The ISO standards for the methodology of conformance testing and the TTCN language are used as the basis for the test specifications.
|
22.127
|
Service requirement for the Open Services Access (OSA); Stage 1
|
TS
|
9.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.127/22127-900.zip
|
This document specifies the stage 1 requirements for realisation of an Open Service Access (OSA).
OSA enables applications to make use of network functionality through an open standardised interface (the OSA API). OSA provides the glue between applications and network functionality. In this way applications implementing the services become independent from the underlying network technology.
Applications which make use of network functionality offered through the OSA interface are not standardised by 3GPP.
The network functionality offered through the OSA interface may or may not be standardised by 3GPP.
OSA is one toolkit, amongst others, that enables certain aspects of the requirements of the Virtual Home Environment (VHE) concept to be realised.
|
23.198
|
Open Service Access (OSA); Stage 2
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.198/23198-900.zip
|
The present document specifies the stage 2 of the Open Service Access (OSA).
|
23.820
|
Study of IMS restoration procedures
|
TR
|
9.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.820/23820-900.zip
|
The present document identifies the changes required in the 3GPP IMS specifications so that a consistent state is restored in the IMS Core Network, after, or during a planned, or unplanned stop of a network element. The study will go through the following steps:
• Establish the requirements that should be covered with these procedures. That is which are the impacts to the end user service that are acceptable and which are not, after a network failure.
• List the service interruption scenarios that need to be studied.
• Provide solutions, so that in all the service interruption scenarios listed, the impacts to the end user service comply with the requirements. These solutions provide procedures for the automatic restoration to a consistent state in the network and indicate how to trigger these procedures.
• Analyze the impacts of the solutions in the current specifications.
• Conclusion and recommended way forward.
It is important to realise that these procedures are meant to be operational procedures for restoration and so care must be taken with what is existing and will exist with OA&M procedures to avoid overlap which could cause clashes.
|
23.826
|
Feasibility study on Voice Call Continuity (VCC) support for emergency calls
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.826/23826-900.zip
|
This document contains the results of the feasibility study into the architectural requirements and alternatives for the support of active voice call continuity between Circuit Switched (CS) domain and the IP Multimedia Subsystem (IMS) for emergency calls. Considerations include overall requirements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The Feasibility Study considers different solutions for offering voice call continuity for emergency calls when users move between the GSM/UMTS CS Domain and the IP Connectivity Access Network (e.g., WLAN interworking) with home IMS functionality. The objective is to identify an architectural solution that allows completely automatic connectivity to the correct PSAP (from the end-user point of view) as specified in TS 23.167 [4], and allow for the possibility of a domain transfer as specified in TS 23.206 [3]. The study will also identify configuration impacts upon existing networks in order to realize the desired functionality.
Existing solutions developed by the 3GPP (e.g. 3GPP system to Wireless Local Area Network Interworking (I-WLAN)) should be reused as much as possible.
|
23.830
|
Architecture aspects of Home Node B (HNB) / Home enhanced Node B (HeNB)
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.830/23830-900.zip
|
This Technical Report describes the architectural aspects of specific UTRAN and E-UTRAN base stations, known as Home NodeBs and Home eNodeBs, which provide services in e.g. residential or enterprise deployments.
NOTE: This feasibility study has led to normative modifications of various specifications; the contents of this technical report should therefore be considered out of date.
To achieve this, the objectives are to (a) document the architectural assumptions taken by other working groups as part of their previous and ongoing work on Home Node B/Home eNodeB and Closed Subscriber Groups (CSG), and to (b) identify any outstanding issues not properly addressed in Rel-8.
Starting from the resulting architectural baseline, the intention is to derive architectural requirements arising from the outstanding Rel-8 issues and the Rel-9 requirements on Home NodeB and Home eNodeB as laid down by SA WG1 in TS 22.220 [2]. Based on this, the objective is to discuss and conclude on solutions for the architectural issues arising from those requirements.
|
23.838
|
IP Multimedia Subsystem (IMS) service continuity enhancements; Service, policy and interaction; Stage 2
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.838/23838-900.zip
|
This technical report intends to develop enhancements for Rel-8 IMS Service Continuity and solutions for mobility of media flows and control of a session between different devices under the same subscription (i.e. Inter-UE Transfer) to a state where they can be transferred to normative specifications, focusing on the following aspects:
For Inter-UE transfer:
- Inter-UE Transfer scenarios for transferring/retrieval/addition/deletion of media flows in a Collaborative Session;
- Inter-UE Transfer scenarios for establishment or continuation of a Collaborative Session while transferring control;
- Transferring media flows to the target UE whilst keeping the Collaborative Session control in the source UE.
For IMS Service Continuity Enhancement:
- Management of operator policy and user preferences;
- Interaction and coexistence with underlying mobility mechanisms and corresponding policies;
- Further capabilities for the support of mid-call services during session transfer, in addition to those defined in TS 23.292 [6], TS 23.237 [5] and TS 23.216 [6];
- Session Continuity for speech and video over CS.
IMS Service Continuity will be restricted to service continuity using IMS procedures, i.e. mobility mechanisms on the IP-CAN level are not within the scope of this document This document does not overlap with the underlying EPC and SRVCC features, even though there could be cross-references between the corresponding Technical Specifications.
|
23.868
|
Feasibility study on extension of support for IP Multimedia Subsystem (IMS) emergency calls
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.868/23868-900.zip
|
The present document provides a study investigating possible limitations of the solution for IMS emergency calls defined for Rel-7 in TS 23.167 [2], as well as possible extensions of that solution to reduce or eliminate some or all of the identified limitations.
The study item is expected mainly to concern IMS although some aspects of IP-CAN support may also be included. The study item has the following objectives
- Evaluate the feasibility of supporting IMS emergency calls for combinations of IP access network A and IMS core network B not supported in Rel-7 including but not limited to the following cases:
- A is any IP access network and B is the home 3GPP compliant IMS network for any emergency calling UE with adequate security credentials
- A is any IP access network and B is a visited 3GPP compliant IMS network for any emergency calling roaming UE with adequate security credentials
Additional user cases may also be proposed and evaluated during the SI if deemed applicable.
- Evaluate other enhancements to the solution for IMS emergency calls in Release 7 that may improve performance and/or reduce complexity
- Evaluate the feasibility of better aligning the solution in TS 23.167 [2] with applicable IETF standards and draft standards (e.g. from the Ecrit and Geopriv working groups)
- Any enhancement to the support of IMS emergency calls shall remain backward compatible to the solution in Rel-7 from the perspective of the UE and any 3GPP network element. Furthermore, any enhancement should be based on the solution in Rel-7 and should avoid unnecessarily adding new network entities, protocols and interfaces and moving existing functions from one entity to another.
The study item is expected to enable SA WG2 to decide which of the above objectives if any may be worth supporting in Rel-8 and which extensions to the current solution would then be appropriate.
|
23.870
|
Single Radio Voice Call Continuity (SR-VCC) support for IMS Emergency Calls
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.870/23870-900.zip
|
SRVCC as specified in TS 23.216 [3], provides handover of voice calls from E-UTRAN/HSPA to UTRAN/GERAN or from E-UTRAN to CDMA2000 1x. SRVCC of IMS emergency calls is not supported in TS 23.216 [3], and thus handover of such calls will have unpredictable effects, in the worst case causing the call to fail. This is a serious concern for operators and their subscribers, and may cause regulatory violations in some parts of the world.
Therefore, the objective of this document is to study both the EPS and IMS aspects of how to best support the handover of ongoing emergency calls for the following scenarios:
- E-UTRAN to UTRAN/GERAN CS.
- HSPA to UTRAN/GERAN CS.
- E-UTRAN to CDMA2000 1x CS.
|
23.879
|
Study on Circuit Switched (CS) domain services over evolved Packet Switched (PS) access
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.879/23879-900.zip
|
The present document contains the results of the study of the architectural requirements of CS Domain Services over evolved PS access and concludes with a way forward. Considerations include overall requirements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The objective is to describe an architecture that is capable of extending the 'traditional' MSC-Server based set of CS voice, supplementary and value-adding services and business principles (e.g. for roaming and interconnect) to the evolved PS access. The intention is also to give a CS handover-like user experience for voice calls when changing between evolved PS and legacy CS accesses. The architecture will however not be limited to the provision of speech services over evolved PS accesses; on the contrary, through the exploitation of the Combinational services, it will be possible to harness the capabilities of IMS to provide new, innovative services to the end user. Handover of the parallel PS session towards legacy 3GPP access will be considered as well, but may be limited by the capabilities of the legacy system and operator preferences.
Co-existence with IMS centric Single Radio VCC solutions shall be studied as well.
|
23.883
|
Study on enhancements to IMS Centralized Services (ICS)
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.883/23883-900.zip
|
The following aspects of IMS Centralized Services (ICS), though studied in Release 8 (and to some extent documented in TR 23.892 [2]), required further study and are herein documented:
- ICS supplementary service data management (e.g. Supplementary Services data synchronization).
- Management of Telephony Application Server (TAS) user configuration for an ICS UE when PS access cannot be used.
Consideration shall be given to attaining a consistent user experience, and managing and enforcing operator policies as well as user preferences. Heterogeneous access technologies over which the IMS service is provided shall also be taken into account.
|
23.891
|
Evaluation of LCS Control Plane Solutions for EPS
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.891/23891-900.zip
|
This TR studies various alternatives for the stage 2 control plane LCS Reference Architecture for Evolved Packet Core.
This document does not document the radio signal measure and/or position methods for the E-UTRAN. Those are addressed in RAN specifications.
|
23.869
|
Support for Internet Protocol (IP) based IP Multimedia Subsystem (IMS) Emergency calls over General Packet Radio Service (GPRS) and Evolved Packet Service (EPS)
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.869/23869-900.zip
| |
25.866
|
1.28 Mcps TDD Home Node B (HNB) study item technical report
|
TR
|
9.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.866/25866-900.zip
|
This document is a technical report of the 1.28Mcps TDD Home NodeB study item, which was approved in TSG RAN#41.
The goal of this study item is,
- To characterise the 1.28Mcps TDD Home NodeB environment.
- To determine the feasibility of a solution and to outline any obstacles for providing high data rate low cost services in home NodeB environment.
- High level HNB requirements are understood not to be complete; hence the report includes a description of the motivation of requirements needed to progress the work
- Whenever possible to offer recommendations for specifications
|
25.907
|
Evaluation of path-loss technologies for Location Services (LCS)
|
TR
|
9.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.907/25907-901.zip
|
<Editor's note: Text in this section is cited from the original text in 'Annex A.1 Overview'>
Path-loss technologies cover a broad scope of specific location technologies, including: RSSI Trilateration technologies, certain Enhanced Cell-ID technologies, and RF pattern matching technologies. For the purposes of this Study Item, individual technology groups to be evaluated will be treated independently as Annexes to the TR.
In this TR, Annex.A should:
- Describe pattern matching and outline it's benefits and challenges.
- Illustrate the required messaging to support RF pattern matching technologies, as well as the projected performance improvements associated with additional messaging/measurement support.
- Confirm the performance capability of RF pattern matching Technology on the UMTS air-interface, over all environments. Both in terms of accuracy and location result latency:
- Dense Urban
- In-Building
- Rural
- Illustrate the Standardized architecture for RF pattern matching technologies as related to the UMTS and future air interfaces.
- Provide an outline of anticipated standardization requirements for improved performance and interoperability of RF pattern matching technologies.
- Provide a conclusion based on the information contained herein and a recommendation to the 3GPP regarding standardization of RF pattern matching Technologies within the RAN.
|
25.913
|
Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)
|
TR
|
9.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.913/25913-900.zip
|
This document is related to the technical report for the study item "Evolved UTRA and UTRAN" [1]. The objective of the study item is to develop a framework for the evolution of the 3GPP radio-access technology towards a high-data-rate, low-latency and packet-optimized radio access technology.
This document provides guidance and collects requirements which an evolved UTRA and UTRAN system should meet.
|
29.198-01
|
Open Service Access (OSA) Application Programming Interface (API); Part 1: Overview
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-01/29198-01-900.zip
|
The present document is the first part of the 3GPP Specification defining the Application Programming Interface (API) for Open Service Access (OSA), and provides an overview of the content and structure of the various parts of this specification, and of the relation to other standards documents.
The OSA-specifications define an architecture that enables service application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-02
|
Open Service Access (OSA) Application Programming Interface (API); Part 2: Common data definitions
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-02/29198-02-900.zip
|
The present document is Part 2 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Common Data definitions of the OSA. The Common Data definitions contain data-types that are common across the rest of the OSA API. All aspects of the Common Data are defined here, these being:
- Data definitions;
- IDL Description of the data types;
- WSDL Description of the data types;
- Reference to the Java™ API description of the data types.
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-03
|
Open Service Access (OSA) Application Programming Interface (API); Part 3: Framework
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-03/29198-03-900.zip
|
The present document is Part 3 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Framework aspects of the interface. All aspects of the Framework are defined in the present document, these being:
• Sequence Diagrams;
• Class Diagrams;
• Interface specification plus detailed method descriptions;
• State Transition diagrams;
• Data definitions;
• IDL Description of the interfaces.
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-04-1
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 1: Call control common definitions
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-1/29198-04-1-900.zip
|
The present document is Part 4, Sub-part 1 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the common definitions used by the Call Control Service Capability Features (SCF).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-04-2
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 2: Generic call control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-2/29198-04-2-900.zip
|
The present document is Part 4, Sub-part 2 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Generic Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Generic Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-04-3
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 3: Multi-party call control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-3/29198-04-3-900.zip
|
The present document is Part 4, Sub-Part 3 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multi-Party Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi-Party Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-04-4
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 4: Multimedia call control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-4/29198-04-4-900.zip
|
The present document is Part 4, Sub-part 4 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multi-Media Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi-Media Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-04-5
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 5: Conference call control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-5/29198-04-5-900.zip
|
The present document is Part 4, Sub-Part 5 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Conference call control Service Capability Feature (SCF) aspects of the interface. All aspects of the Conference call control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-05
|
Open Service Access (OSA) Application Programming Interface (API); Part 5: User interaction Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-05/29198-05-900.zip
|
This document is Part 5 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the User Interaction (UI) Service Capability Feature (SCF) aspects of the interface. All aspects of the User Interaction SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-06
|
Open Service Access (OSA) Application Programming Interface (API); Part 6: Mobility Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-06/29198-06-900.zip
|
The present document is Part 6 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Mobility Service Capability Feature (SCF) aspects of the interface. All aspects of the Mobility SCF are defined here, these being:
- Sequence Diagrams
- Class Diagrams
- Interface specification plus detailed method descriptions
- State Transition diagrams
- Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-07
|
Open Service Access (OSA) Application Programming Interface (API); Part 7: Terminal capabilities Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-07/29198-07-900.zip
|
The present document is part of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All aspects of the Terminal Capabilities SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-08
|
Open Service Access (OSA) Application Programming Interface (API); Part 8: Data session control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-08/29198-08-900.zip
|
The present document is Part 8 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Data Session Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Data Session Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-10
|
Open Service Access (OSA) Application Programming Interface (API); Part 10: Connectivity manager Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-10/29198-10-900.zip
|
The present document is Part 10 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Connectivity Manager Service Capability Feature (SCF) aspects of the interface. All aspects of the Connectivity Manager SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-11
|
Open Service Access (OSA) Application Programming Interface (API); Part 11: Account management Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-11/29198-11-900.zip
|
The present document is Part 11 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Account Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Account Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-12
|
Open Service Access (OSA) Application Programming Interface (API); Part 12: Charging Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-12/29198-12-900.zip
|
The present document is Part 12 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Charging Service Capability Feature (SCF) aspects of the interface. All aspects of the Charging SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-13
|
Open Service Access (OSA) Application Programming Interface (API); Part 13: Policy management Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-13/29198-13-900.zip
|
The present document is part 13 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Policy Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Policy Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data Definitions
• IDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-14
|
Open Service Access (OSA) Application Programming Interface (API); Part 14: Presence and Availability Management (PAM) Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-14/29198-14-900.zip
|
The present document is part 14 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Presence and Availability Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Presence and Availability Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data Definitions
• IDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-15
|
Open Service Access (OSA) Application Programming Interface (API); Part 15: Multi-media Messaging (MM) Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-15/29198-15-900.zip
|
The present document is Part 15 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multi Media Messaging Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi Media Messaging SCF are defined here, these being:
• Sequence Diagrams.
• Class Diagrams.
• Interface specification plus detailed method descriptions.
• State Transition diagrams.
• Data definitions.
• IDL Description of the interfaces.
• WSDL Description of the interfaces.
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-16
|
Open Service Access (OSA) Application Programming Interface (API); Part 16: Service broker Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-16/29198-16-900.zip
|
The present document is Part 16 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Service Broker Capability Feature (SCF) aspects of the interface. All aspects of the Service Broker SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-01
|
Open Service Access (OSA); Parlay X web services; Part 1: Common
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-01/29199-01-900.zip
|
The present document is Part 1 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Common aspects of the Parlay X Web Services. The following are defined here:
Name spaces.
Data definitions.
Fault definitions.
WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-02
|
Open Service Access (OSA); Parlay X web services; Part 2: Third party call
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-02/29199-02-900.zip
|
The present document is Part 2 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.127 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Third Party Call Web Service aspects of the interface. All aspects of the Third Party Call Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-03
|
Open Service Access (OSA); Parlay X web services; Part 3: Call notification
|
TS
|
9.3.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-03/29199-03-930.zip
|
The present document is Part 3 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Call Notification Web Service aspects of the interface. All aspects of the Call Notification Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-04
|
Open Service Access (OSA); Parlay X web services; Part 4: Short messaging
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-04/29199-04-900.zip
|
The present document is Part 4 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Short Messaging Web Service aspects of the interface. All aspects of the Short Messaging Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.