id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2
values | version stringclasses 560
values | working_group stringclasses 30
values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
23.823 | Intra Domain Connection of RAN Nodes to Multiple CN Nodes | TR | 2.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.823/23823-200.zip | This Technical Report evaluates the feasibility of implementing a function above the BSC/RNC nodes to provide similar functions as the NNSF function in BSC/RNC nodes that is specified in TS 23.236 [2]. This Technical Report also identifies the impacts on specifications. |
23.839 | Study on support of Broadband Forum (BBF) access Interworking | TR | 0.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.839/23839-070.zip | Based on requirements documented in the stage 1 specifications, this technical report addresses system architecture impacts to support BBF Access Interworking. The study includes multiple phases and covers aspects such as basic connectivity, mobility, authentication and authorisation, policy and QoS aspects, IP Flow mobility, traffic offload, convergence etc.
In each Building Block, the TR describes what changes are expected to normative TSs, e.g. TS 23.402 [3] and TS 23.203 [4].
The work is divided into three separate Building Blocks. See clause 4 for an outline of the content of each building block. |
23.857 | Study of Evolved Packet Core (EPC) nodes restoration | TR | 1.10.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.857/23857-1a1.zip | The present document contains the study on EPC nodes failure and restoration.
This document will consider any necessary operational protocol recovery mechanisms in the EPS in order to restore the subscriber service in the event of EPC node failure or clean up the hanging resource in other EPC nodes if the recovery of the failed node is not possible. The document will address the following aspects:
- list the different network failure scenarios to be analyzed for EPC nodes: MME, S4-SGSN, SGW and PGW;
- identify precisely the problems resulting from the current definition of the standards;
- list various possible solutions;
- identify pros and cons of possible solutions;
- conclude on potential enhancements to the standards (depending on gains vs complexity). |
23.885 | Feasibility Study of Single Radio Voice Call Continuity (SRVCC) from UTRAN/GERAN to E-UTRAN/HSPA; Stage 2 | TR | 1.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.885/23885-140.zip | The objective of the feasibility study is to investigate a solution for supporting Single Radio Voice Call Continuity (SRVCC) from 3GPP UTRAN/GERAN CS access to 3GPP E-UTRAN/HSPA access, for voice call initiated in LTE/HSPA access and previously handed over to UTRAN/GERAN CS access, as well as for the voice call directly initiated in UTRAN/GERAN CS access.
This Technical Report investigates solutions for SRVCC for voice calls that are anchored in the IMS.
Coordination between the SRVCC for voice call and the handover of non‑voice PS bearers is also covered. |
23.888 | System improvements for Machine-Type Communications (MTC) | TR | 1.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.888/23888-170.zip | This Technical Report studies and evaluates architectural aspects of the System Improvements for Machine Type Communications requirements specified in TS 22.368 [2].
Specifically, the following system improvements are considered:
- Architectural enhancements to support a large number of Machine-Type Communication (MTC) devices in the network;
- Architectural enhancements to fulfil MTC service requirements;
- Support combinations of architectural enhancements for MTC, though not all combinations may by possible.
The end-to-end aspects of communication between MTC devices and MTC servers (which can be located outside or inside the network operator's domain) are out of the scope of this study. However, the transport services for MTC as provided by the 3GPP system and the related optimizations are considered in this study. In addition, the aspects needed to ensure that MTC devices and/or MTC servers and/or MTC applications do not cause peak loads of short duration (e.g. a "busy minute" rather than a "busy hour") are within the scope of this TR.
Even though some provided solutions may be beneficial for communications from a MTC Device towards another MTC Device, this particular type communication has not been explicitly considered in this Technical Report.
This Technical Report analyzes architectural aspects to achieve these objectives and to gather technical content until it can be included in the relevant technical specifications.
NOTE: Some aspects in this feasibility study have led into normative specification in TS 23.682 [20], TS 23.060 [21], TS 23.401 [5], TS 23.221 [22] and TS 23.272 [23]. The text of the present document was not updated to align with normative specifications. |
23.975 | IPv6 migration guidelines | TR | 1.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.975/23975-130.zip | |
24.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-a00.zip | |
24.826 | Study on impacts on signalling between User Equipment (UE) and core network from energy saving | TR | 1.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.826/24826-110.zip | The present document contains the result of the study on the impacts on signalling between the UE and core network when energy saving measures are applied to network entities.
The study aims, within the defined CT1 work areas, at:
- analysing UE idle mode procedures and signalling between the UE and core network resulting from switch on/off of radio equipment in all types of 3GPP accesses, including home cell deployment and I-WLAN, as well as power adaptation of radio equipment (where applicable);
- performing a corresponding analysis for connected mode UEs;
- analysing similar impacts from activation status of non-3GPP access networks;
- documenting limitations, weaknesses and inefficiencies in these procedures, with emphasis on mass effects in the signalling between the UE and core network; and
- studying potential optimizations and enhancements to these procedures.
The study also evaluates potential enhancements to 3GPP specifications under CT1 responsibility.
This study takes into account decisions made by other 3GPP working groups in their related work. |
29.935 | Study on User Data Convergence (UDC) data model | TR | 0.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.935/29935-0a0.zip | |
32.833 | Telecommunication management; Study on management of converged networks | TR | 0.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.833/32833-060.zip | The present document investigates which new functionalities regarding a true end to end management are enabled by a converged OSS. The fragments looked at are Fault Management, Performance Management and Configuration Management. |
33.859 | Study on the Introduction of Key Hierarchy in Universal Terrestrial Radio Access Network (UTRAN) | TR | 1.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.859/33859-110.zip | The objective of this work item is to study potential solutions for introducing an "E-UTRAN-like" key hierarchy in UTRAN, to improve the security level in UTRAN in the presence of the new deployment scenarios and to ensure that a security breach in UTRAN will not propagate into E-UTRAN. The study covers the technical feasibility and consequences. The impacts of such potential solution on UTRAN of earlier releases are identified. Interworking with earlier releases of UTRAN, GERAN and E-UTRAN is also studied.
The UTRAN key hierarchy is assumed to be built on top of (R99+) UMTS AKA, without requiring any changes to the authentication protocol or USIM. Therefore, it could in principle be used also in GERAN as long as USIMs are used and the SGSN, MSC/VLR, and ME are updated. However, the benefit of introducing the key hierarchy in GPRS is smaller than for the circuit switched part, as the traffic protection already terminates in the core network. Solution details for GERAN are not discussed further.
The study covers both PS and CS part of UTRAN. |
33.914 | Single Sign On (SSO) application security for common IP Multimedia Subsystem (IMS) based on SIP Digest | TR | 0.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.914/33914-060.zip | The objective of this study item is to provide reference material for IMS based non-UICC based Single Sign On (SSO) to applications. This study item targets to re-use the SIP Digest Credentials for SSO to applications by re-using Common IMS and existing security elements. The study should describe needed extension to enable a re-use of SIP Digest credentials in Common IMS for providing security between a terminal and an application server. The study aims to maximise the commonalities of the SSO_APS with the currently defined application security approaches in 3GPP while efficiently satisfying the needs of Common IMS deployments using SIP Digest.
The Technical Report targets to bring forth approaches with a security level for access to applications using SSO_APS that is at least as good as that provided by SIP Digest for Common IMS. This Technical Report is intended to be used where the usage of UICC is not possible in a UICC-less environment. If the usage of UICC is possible, then it is expected to used, but that is outside the scope of the present study.
The scope of this Technical Report (Study Item Code SSO_APS) is restricted to environments where the storage of credentials on a UICC is not mandated. |
36.116 | Evolved Universal Terrestrial Radio Access (E-UTRA); Relay radio transmission and reception | TS | 0.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.116/36116-040.zip | |
36.816 | Evolved Universal Terrestrial Radio Access (E-UTRA); Study on signalling and procedure for interference avoidance for in-device coexistence | TR | 1.3.1 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.816/36816-131.zip | The present document is intended to capture the output of the study item on Signalling and procedure for interference avoidance for in-device coexistence, which was approved at TSG RAN#48.
The objective of the SI is to investigate suitable mechanisms for interference avoidance from signalling and procedure point of view to facilitate the coexistence scenario that LTE and GPS/ ISM radio within the same device working in adjacent frequencies or sub-harmonic frequencies. The work under this study should take the following steps:
（1） Evaluate whether existing RRM mechanisms could be utilized to effectively solve the coexistence problems that arise in supporting the scenarios abovementioned and guarantee the required QoS in LTE with proper GPS/ISM operation.
（2） If legacy signaling and procedure are not sufficient to ensure required performance in the interested coexistence scenario, study enhanced mechanisms to better avoid interference and mitigate the impact caused by ISM radio.
Impact on legacy LTE UEs should be minimized.
NOTE: The candidate solutions should be firstly considered in the non-CA (carrier aggregation) cases. |
36.826 | Evolved Universal Terrestrial Radio Access (E-UTRA); Relay radio transmission and reception | TR | 0.17.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.826/36826-0h0.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. |
37.806 | Extending 850 MHz study Technical Report | TR | 0.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.806/37806-030.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.976 | Measurement of radiated performance for Multiple Input Multiple Output (MIMO) and multi-antenna reception for High Speed Packet Access (HSPA) and LTE terminals | TR | 1.8.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.976/37976-180.zip | |
43.868 | GERAN improvements for Machine-Type Communications (MTC) | TR | 0.5.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.868/43868-050.zip | The present document contains the results from the study of improvements for Machine-type Communications in GERAN.
The following items are in the scope of the study:
- GERAN enhancements for Smart metering
- Enhancements which enable or improve efficient use of RAN resources and/or which lower complexity when a large number of MTC devices are served.
- GERAN enhancements for overload and congestion control on the radio, A and Gb interface
- GERAN enhancements regarding identifiers used for MTC devices in the radio access network |
22.168 | Earthquake and Tsunami Warning System (ETWS) requirements; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.168/22168-900.zip | This Technical Specification defines the stage one description of the Earthquake and Tsunami Warning System (ETWS) Requirements. Stage one is the set of requirements seen primarily from the users’ and service providers’ points of view.
This TS includes information applicable to network operators, service providers, terminal and network manufacturers, in case of deployment of ETWS. ETWS deployment depends on operator decision or national regulations.
This TS contains the core requirements for the Earthquake and Tsunami Warning System, which are sufficient to provide a complete service.
This TS also contains regional requirements for Earthquake and Tsunami Warning System. |
22.813 | Study of use cases and requirements for enhanced voice codecs for the Evolved Packet System (EPS) | TR | 0.9.9 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.813/22813-099.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.893 | Advanced requirements for IP interconnect | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.893/22893-100.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). |
22.913 | Location Services (LCS) support in Evolved Packet Core (EPC) for non-3GPP accesses | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.913/22913-100.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.947 | Study on Personal Broadcast Service (PBS) | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.947/22947-100.zip | |
23.812 | Feasibility study on IP Multimedia Subsystem (IMS) evolution | TR | 0.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.812/23812-080.zip | The scope of the technical report is to capture the results of a study into the feasibility of enhancing IMS network architecture. This report intends to study the feasibility of enhancing IMS network architecture as follows,
- Investigating architectural improvements to reduce the complexity of signalling procedures by reducing the signalling hops, or the number of options and combinations (by looking at different groupings of combining existing entities);
- Investigating means to improve system-level load balancing and reliability;
- Investigating possibilities for reducing configuration workload to save OPEX.
- Investigating the introduction of IMS Overload Control mechanisms.
Backward compatibility with current IMS specifications shall be ensured.
NOTE: overlap with SA5 and CT4 work need to be monitored.
This report is intended to explore potential architecture improvements and also provide conclusions on the above aspects with respect to potential future normative specification work.
There are a number of functions involved in call session setup in IMS network. Interfaces and interactions between network elements may be a little complicated and not that efficient. It is deemed beneficial to review the current IMS architecture including aspects such as the possible optimization of interfaces/reference points (by looking at different groupings of combining existing entities), reducing options of solutions for the same issues, relevancy of certain functions etc.
IMS network service availability largely relies on the reliability of network entities. If some network elements implementing critical functions (e.g. S-CSCF, HSS) fail, service availability may be impacted. Moreover network elements may not be fully utilized because network load may not be well distributed, e.g. some nodes may be overloaded due to sudden traffic increase, while others may be under loaded to some extent. Though there are some element level approaches to solve these problems, some system level solutions should be studied, for example, the method to distribute load between network elements in different geographical locations especially when a disaster happens, such as earthquake.
Network expansion may require significant manual configurations, and the network maintenance and upgrade may be time-consuming and also may be costly for operators. Introducing self-organization features may improve the network intelligence and reduce the efforts of manual configuration.
The objectives of the study for investigating the introduction of IMS Overload Control mechanisms are to:
- Determine the parts of IMS architecture for which overload control mechanisms are needed;
- Evaluate the applicability of candidate solutions for Overload Control to the SIP entities of the IP multimedia core network architecture, including:
- mechanisms having already been specified or studied within 3GPP and their possible enhancements,
- mechanisms specified or studied by other bodies (e.g. ETSI TISPAN, IETF) and their possible enhancements,
- other mechanisms, if proposed within this work item;
- Provide recommendations based on analysis. |
23.823 | Intra Domain Connection of RAN Nodes to Multiple CN Nodes | TR | 1.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.823/23823-120.zip | This Technical Report evaluates the feasibility of implementing a function above the BSC/RNC nodes to provide similar functions as the NNSF function in BSC/RNC nodes that is specified in TS 23.236 [2]. This Technical Report also identifies the impacts on specifications. |
23.832 | IP Multimedia Subsystem (IMS) aspects of architecture for Home Node B (HNB); Stage 2 | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.832/23832-100.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.848 | Study on enhancements to IP Multimedia Subsystem (IMS) border functions for interconnection of IMS based services | TR | 0.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.848/23848-090.zip | The objective of this document is to analyse and identify enhancements needed in the current 3GPP IMS interconnection architecture driven by the needs that new business models/service delivery scenarios impose at the interconnection points of the IMS operators.
The present document will covers network to network interconnection as main objective and addresses the issues related to both control and user plane functionalities including:
- signalling treatment,
- numbering/naming/addressing,
- IP interworking,
- policy management,
- e2e QoS,
- transcoding,
- security,
- charging.
The purpose of this document is to formulate architectural solutions for the enhanced functionalities identified to cover all IMS operator’s needs in this widespread environment. These solutions should be applicable for an IMS operator in a common IMS environment (i.e. regardless the access being used) as well as for direct and indirect interconnection paradigms. Finally, the best solution/s should be agreed and impacted normative work in 3GPP identified to update current 3GPP specifications with the output of this work. |
23.884 | Local Call Local Switching, Feasibility Study | TR | 0.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.884/23884-010.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 potential correlation information between the two legs of the call to be sent to the BSS (e.g. in case of MSC pooling)
- 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)
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.889 | Local Call Local Switch (LCLS) system impacts; Feasibility study | TR | 1.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.889/23889-140.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 | 1.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.894/23894-130.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.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 9.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-900.zip | |
26.950 | Study on Surround Sound codec extension for Packet Switched Streaming (PSS) and Multimedia Broadcast/Multicast Service (MBMS) | TR | 0.5.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.950/26950-050.zip | |
29.875 | Interworking Proxy between GTP based and PMIP based interfaces | TR | 1.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.875/29875-120.zip | The present document is to evaluate the feasibility of introduction of an Interworking Proxy (IWP) between GTP-based S8 and, PMIP-based S8 and S9 interfaces as described in 3GPP TS23.402 [2] Annex A. This evaluation will be based on the study of various concrete interworking deployment scenarios for which an IWP may be used. For each scenario, it will be analysed how the IWP fulfils the specific interworking requirements and performs the mapping of procedures and the corresponding parameter handling. The U-plane Interworking will also be analysed for each scenario.
The present document will study the mechanism for the interworking scenarios, e.g. IWP selection, message binding. |
32.452 | Telecommunication management; Performance Management (PM); Performance measurements Home Node B (HNB) Subsystem (HNS) | TS | 1.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.452/32452-130.zip | |
32.453 | Telecommunication management; Performance Management (PM); Performance measurements Home enhanced Node B (HeNB) Subsystem (HeNS) | TS | 0.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.453/32453-060.zip | |
32.541 | Telecommunication management; Self-Organizing Networks (SON); Self-healing concepts and requirements | TS | 1.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.541/32541-170.zip | |
32.825 | Telecommunication management; Charging management; Rc reference point study | TR | 2.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.825/32825-200.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 | 2.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.826/32826-200.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 | 1.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.827/32827-110.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. |
33.837 | Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI) | TR | 2.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.837/33837-201.zip | The scope of this report is to develop solutions to protect mobile subscribers from receiving unsolicited communication over IMS and to analyze these solutions in respect of their requirements and impacts on standardized interfaces.
This activity will take into account the study done in TISPAN TR 187 009 on “Feasibility study of prevention of unsolicited communications in the NGN”. This work will also be coordinated with ongoing activity in other SDOs (e.g. TISPAN, IETF and OMA). It is preferred that a common solution can be defined for protection against UC in both IMS and NGN deployments. |
36.571-2 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; UE positioning in E-UTRA; Part 2: Protocol conformance | TS | 1.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.571-2/36571-2-100.zip | The present document specifies the protocol conformance testing for the 3rd Generation E-UTRAN User Equipment (UE) supporting UE positioning.
This is the second part of a multi-part test specification. The following information can be found in this part:
- the overall protocol conformance test structure;
- the protocol conformance test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The Implementation Conformance Statement (ICS) pro-forma could be found in the 3rd part of the present document.
The present document is valid for UE implemented according to 3GPP Release 9. |
36.571-5 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; UE positioning in E-UTRA; Part 5: UE positioning test scenarios and assistance data | TS | 1.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.571-5/36571-5-100.zip | The present document specifies the test scenarios and assistance data required for the conformance test for FDD or TDD mode of UTRA and E-UTRA for the User Equipment (UE) that supports one or more of the defined positioning methods. For UTRA these are Assisted Global Positioning System (A-GPS) and Assisted Global Navigation Satellite System (A-GNSS). For E-UTRA these are A-GNSS, Observed Time Difference of Arrival (OTDOA) and Enhanced Cell ID (ECID). |
22.142 | Value Added Services (VAS) for Short Message Service (SMS) requirements | TS | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.142/22142-800.zip | |
22.258 | Service requirements for an All-IP Network (AIPN); Stage 1 | TS | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.258/22258-800.zip | The present document describes the service requirements for the All-IP Network (AIPN) including service requirements for Evolved UTRA and UTRAN. Where appropriate, references are made to service requirements within other 3GPP specifications that are applicable to the AIPN. |
22.812 | Study into network selection requirements for non-3GPP access | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.812/22812-800.zip | The present document considers the network selection procedures requirements for non-3GPP access types. The network selection principles covered include both automatic and manual selection. Also considered is the operator management of network preferences for non-3GPP access types and how the device accesses networks offered through non-3GPP access.
Non-3GPP access includes any method by which the UE is connected either to a core network or to a server other than by using the radio bearers standardised by 3GPP. Examples are: BlueTooth, WLAN and fixed (wired connections).
UEs considered in this study are UEs able to connect to a non-3GPP network in addition to its 3GPP capabilities (i.e. dual mode, multi-mode UEs).
This work in this TR is applicable to GSM and UMTS and there are no additional considerations of EPS (Evolved Packet System).
Roaming and handover conditions between 3GPP and non-3GPP networks is not under the scope of this document and will not be treated here. They may be referred to, however, for the consistency of use cases and access description consistency.
Connection to a 3GPP operator's core network by WLAN is out of scope where this is I-WLAN. This is covered in [2].
Use of the Generic Access Network is out of scope.
Considerations of tariffing are out of scope. |
22.984 | Unauthenticated Packet Switched (PS) emergency calls | TR | 0.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.984/22984-030.zip | The present document gives an overview of the problems related to Unauthenticated PS based Emergency Calls (UAPSEC) and provides information on this topic in comparison to the existing unauthenticated CS based emergency call.
Major areas of work the document takes into account are security aspects, architectural aspects and signalling aspects. It also considers the case where the subscriber has got a PS subscription but no subscription to IMS services.
The document explains on the differences between the scenarios that allowed unauthenticated CS emergency calls without encountering too big problems and the scenarios that make Unauthenticated PS based Emergency Calls different in this respect.
It elaborates on these new scenarios, for example on the Distributed Denial of Service Attacks (DDOS) scenario. |
23.142 | Value-added Services for SMS (VAS4SMS); Interface and signalling flow | TS | 0.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.142/23142-040.zip | |
23.822 | Framework for Gq' / Rx harmonization | TR | 0.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.822/23822-030.zip | This document provides information that will be used to align the Rx and Gq' reference points. The document analyses several options and recommends options for alignment, taking the architectural and protocol aspects into account. |
23.826 | Feasibility study on Voice Call Continuity (VCC) support for emergency calls | TR | 0.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.826/23826-070.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.827 | Feasibility study of mobility between 3GPP-WLAN interworking and 3GPP systems | TR | 0.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.827/23827-040.zip | This TR studies and defines the appropriate solutions for supporting mobility and roaming between 3GPP-WLAN Interworking system and 3GPP Systems so that ongoing 3GPP PS based services can be maintained with minimal impact on the end-user’s perceived quality on the services at a change of the access network (between I-WLAN and 3GPP Access Systems). The solutions should impose minimum changes to the 3GPP PS core network and the terminals as well as the WLAN access.
Within the TR, different mechanisms are described along with their characteristics. A comparison of the pros and cons of the different mechanisms is included. |
23.868 | Feasibility study on extension of support for IP Multimedia Subsystem (IMS) emergency calls | TR | 0.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.868/23868-040.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.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 | 0.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.869/23869-070.zip | |
23.879 | Study on Circuit Switched (CS) domain services over evolved Packet Switched (PS) access | TR | 1.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.879/23879-120.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.894 | System enhancements for the use of IP Multimedia Subsystem (IMS) services in local breakout and optimal routeing of media | TR | 0.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.894/23894-060.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. |
23.937 | Feasbility study of mobility between 3GPP-WLAN interworking and 3GPP systems | TR | 0.0.2 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.937/23937-002.zip | This TR studies and defines the appropriate solutions for supporting mobility and roaming between 3GPP-WLAN Interworking system and 3GPP Systems so that ongoing 3GPP PS based services can be maintained with minimal impact on the end-user’s perceived quality on the services at a change of the access network (between I-WLAN and 3GPP Access Systems). The solutions should impose minimum changes to the 3GPP PS core network and the terminals as well as the WLAN access.
Within the TR, different mechanisms are described along with their characteristics. A comparison of the pros and cons of the different mechanisms is included. |
23.982 | IP Multimedia System (IMS) centralized services | TR | 0.3.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.982/23982-031.zip | This document contains the results of the feasibility study into the architectural requirements and alternatives for the delivery of consistent services to the user mainly via IMS centralized services regardless of the attached access type; e.g. CS domain access or IP-CAN. Considerations include overall requirements, architectural requirements, alternative architectures and evaluation of potential architectural solutions.
The study considers how to access IMS-based multimedia telephony services while still allowing innovative services. It includes investigation into call/session establishment via CS domain access and IP-CAN and for calls/sessions transferred across CS domain access and IP-CAN, including the interactions with domain selection. It provides consideration for the handling of the multiple medias that are enabled by the multimedia telephony communication service. The solution should be applicable for terminals with VCC capabilities and for non-VCC capable terminals. Impact on legacy terminals with the same subscription (e.g. SIM swapping) should be studied.
The second objective of the study is an investigation into the means to support and the need of the evolution of a network towards the IMS centralized services architecture. The assumption for this evolution is that some networks may not immediately migrate all services to the IMS centralized services architecture. In addition, given that some calls may not be rerouted to IMS during the migratory period, the study shall also investigate how to ensure that equivalent services are implemented in IMS and CS. |
24.293 | ICS Protocol over USSD bearer | TS | 0.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.293/24293-020.zip | The present document describes the I1 interface between IMS Centralized Services (ICS) UE and Service Centralization and Continuity (SCC) Application Server (AS).
This specification defines a new application layer protocol over I1 interface, specifies the interaction between the ICS UE and the SCC AS including session control procedures and supplementary services control procedures.
For the current version of the specification the application layer protocol is run over Unstructured Supplementary Service Data (USSD) transport, however the application layer protocol is not restricted to USSD transport.
The overall ICS architecture is specified in 3GPP TS 23.292 [3].
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the IMS centralized services. |
24.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 8.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-810.zip | |
25.822 | UMTS 700 MHz Work Item Technical Report | TR | 1.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.822/25822-100.zip | The present document is a technical report of the UMTS 700 MHz work item, which was approved to establish in TSG RAN#35. The purpose of the work item is to provide UMTS specification support for UTRA/FDD in the new band allocations on pairing
• 698-716 MHz UL with 728-746 MHz DL and
• 746-768 MHz DL with 776-798 MHz UL.
UMTS 700 MHz work item is covering also E-UTRA aspects, especially narrower BW options 1.4 MHz and 3.0 MHz. Because E-UTRA work is still ongoing, changes for new specifications will be covered under E-UTRA work item.
In addition to schedule and status of the work item, the report includes a description of the motivation of requirements and specification recommendations. |
25.825 | Dual-cell High Speed Downlink Packet Access (HSDPA) operation | TR | 1.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.825/25825-100.zip | The present document is intended to capture findings produced in the context of the Feasibility Study on Dual-Cell HSDPA operation [1].
The work under this study item aims at assessing the feasibility, benefits and complexity of combining network radio resources (i.e. cells) to achieve enhanced user experience and enhanced user experience consistency. The assessment focuses on scenarios with the following constraints:
• The dual cell operation only applies to downlink HS-DSCH.
• The two cells belong to the same Node-B and are on different carriers.
• The two cells do not use MIMO to serve UEs configured for dual cell operation.
• Primary priority: The two cells operate on adjacent carrier frequencies in the same frequency band. Other allocations can be considered with lower priority
In order to characterize benefits of Dual-Cell HSDPA operation, possible enhancements of performance throughout the cell and in particular in the outer area of the cell coverage are evaluated considering:
• UE receiver impairments caused by the implementation of dual-cell operation,
• Node B scheduler architecture (per carrier or joint scheduler),
• Load balancing when coupled with joint scheduling vs. per carrier scheduling.
Furthermore, impacts on implementation and complexity within the UTRA and UE, impacts systems operation (e.g. UL controlchannel coverage and operation of legacy UE), and impacts on the core specifications due to introducing Dual-Cell HSDPA operation are identified. |
25.828 | UMTS 2300 TDD Work Item Technical Report | TR | 0.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.828/25828-030.zip | This document is the technical report of the UMTS 2300MHz WI which was approved in TSG RAN meeting #38 [1].
The purpose of this TR is to summarize a study of radio requirements for UTRA TDD－1.28Mcps TDD in the 2300MHz Band:
• 2300-2400 MHz: Up-link and Down-link (UE transmit and receive, Node B transmit and receive) |
29.238 | Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3 | TS | 0.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.238/29238-060.zip | |
29.334 | IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3 | TS | 0.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.334/29334-040.zip | |
29.612 | TISPAN; Interworking; Trunking Gateway Control Procedures for interworking between NGN and external CS networks | TS | 1.1.3 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.612/29612-113.zip | The present document defines the control procedures for trunk gateways when PSTN/ISDN emulation and PSTN/ISDN simulation services in an NGN Network require interworking with ETSI PSTN/ISDN services in a ISUP network. Interworking with BICC networks is not included in the scope of TISPAN R1.
Existing profiles will be evaluated, in order to determine if they can be re-used, with possible modifications, or if a completely new profile is to be defined. |
29.624 | TISPAN; H.248 Profile for controlling Trunking Media Gateways; Protocol specification | TS | 1.1.6 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.624/29624-116.zip | The present document defines the profile of the Gateway Control Protocol (ITU-T Recommendation H.248.1 [3]), for controlling Trunking Media Gateways (TMGW) for both the PSTN/ISDN Emulation and IMS Core Subsytems. Thus the scope of this Profile is a subset of the 3GPP profile for the Mn interface defined in TS 129 332 [2]. |
29.803 | 3GPP System Architecture Evolution (SAE): CT WG4 aspects | TR | 0.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.803/29803-090.zip | The present document discusses and describes procedures and protocols from CT4 aspects of Evolved Packet System (EPS) towards a higher-data-rate, lower-latency, packet-optimized system that supports multiple access technologies.
These CT4 aspects include selection and study of protocols and procedures that will be used in the evolved system (e.g. within evolved packet core network, between EPC and current GPRS core network, between EPC and HSS/AAA, and between 3GPP and non-3GPP access), and describes impacts and required enhancements for related network protocols, including GTP and IETF protocols based on stage2 architecture requirements.
In addition, the present document also includes description of the new identities and addressing schemes required by Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet System (EPS), and in particular functional requirements and protocols for enhancing existing capabilities for EPS/E-UTRAN, e.g. MBMS and network sharing.
The present document is used as a place holder for CT4 EPS materials to be moved to appropriate 3GPP technical specifications when the TR is sufficiently stable. |
30.818 | Telecommunication management; Project scheduling and open issues for SA5, Release 8 | TR | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.818/30818-800.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. |
32.821 | Telecommunication management; Study of Self-Organizing Networks (SON) related Operations, Administration and Maintenance (OAM) for Home Node B (HNB) | TR | 1.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.821/32821-101.zip | The present document intends to study the following:
1) Define SON OAM solution architecture for both LTE and UMTS home NodeB.
2) Identify differences between SON OAM solution architecture for LTE Marco eNodeB and that for LTE and UMTS home NodeB; Propose aligned SON OAM solution architecture.
3) Identify what can be standardized for SON for LTE and UMTS NodeB in 3GPP SA5.
4) Prepare the work for a later implementation work item. |
32.823 | Telecommunication management; Self-Organizing Networks (SON); Study on self-healing | TR | 0.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.823/32823-020.zip | The present document is focused on studying on self-healing of SON. This study provides the general procedure of self-healing, and collects the use cases of self-healing and proposed related requirements. The findings and proposals of the study may be used to help generate new Technical Specifications (TS) and/or enhance existing Technical Specifications. |
33.178 | Security aspects of early IP Multimedia Subsystem (IMS) | TS | 1.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.178/33178-100.zip | The present document documents an interim security solution for early IMS implementations that are not fully compliant with the IMS security architecture specified in TS 33.203 [2]. For security reasons, the provisions in this TR only apply to IMS procedures used over the 3GPP PS domain. |
33.224 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer | TS | 1.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-100.zip | |
33.812 | Feasibility study on the security aspects of remote provisioning and change of subscription for Machine to Machine (M2M) equipment | TR | 1.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.812/33812-150.zip | The scope of this Technical Report is to study the remote subscription management for M2M Equipment (M2ME) when the Machine Communications Identity Module (MCIM) application resides in the UICC and when the MCIM application resides in the M2M equipment. The remote subscription management includes tasks such as remote subscription provisioning and/or remote change of subscription.
The scope of this study includes the definition of a trust model for remote subscription management for M2ME.Security threats and security requirements are identified, and an evaluation of the candidate solutions is presented.
The security implications of the following requirements are within the scope of the study (based on section 5.2.2 of TR 22.868)
1. The possibility to change subscription for M2MEs out in the field (e.g. after contract expiry) without direct human intervention.
2. The possibility to allocate the M2ME at initial power up to a network operator without direct human intervention.
Furthermore, this study includes the following items:
- an investigation of candidate security solutions architectures that allow remote subscription management to take place in a secure manner;
- an identification of current USIM/ISIM functionality that may need to be incorporated in a MCIM application, with or without changes to allow remote subscription management for the M2ME;
- an identification of functionality in the network, in the UICC or in the M2ME, that may need to be added due to the remote subscription management method;
- the study may identify principle requirements for protected storage and the execution environment (e.g. by collaborating with relevant working groups such as the OMTP Hardware group)
This study is beyond the scope of the first requirement identified in SA1 TR 22.868 since section 5.2.2 of TR 22.868 contains a requirement to have "Tamper Save/Theft proof terminal including a UICC". |
33.828 | IP Multimedia Subsystem (IMS) media plane security | TR | 1.6.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.828/33828-161.zip | |
33.922 | Security aspects for inter-access mobility between non 3GPP and 3GPP access network | TS | 2.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.922/33922-200.zip | This document studies the security architecture, i.e. the security features and the security mechanisms for inter-access mobility between 3GPP access system and non-3GPP access systems. For the general architecture for inter-access mobility cf. TR 23.882. This report is meant to provide more detail on the security aspects of inter-access mobility.
The scope should be extended to the mobility between two non-3GPP access systems, which interwork with 3GPP core entities. An example would be the mobility between two WLAN access systems providing 3GPP IP access.
Disclaimer: This TR reflects the discussions held in 3GPP SA3 while 3GPP SA3 was working towards TS 33.402 [14]. This TR may therefore be useful to better understand the basis on which decisions in TS 33.402 [14] were taken, and which alternatives were under discussion. However, none of the text in this TR shall be quoted as reflecting 3GPP’s position in any way. Rather, 3GPP’s position on security for non-3GPP access to EPS is reflected in the normative text in TS 33.402 [14]. Information in the TR may be inaccurate and outdated. One example of outdated text can be found in clauses 4.1 and 4.2 on alternatives for authentication protocols. The choices of authentication protocols finally made by 3GPP can be found in TS 33.401 [13] and TS 33.402 [14] respectively. |
33.978 | Security aspects of early IP Multimedia Subsystem (IMS) | TR | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.978/33978-800.zip | The present document documents an interim security solution for early IMS implementations that are not fully compliant with the IMS security architecture specified in TS 33.203 [2]. For security reasons, the provisions in this TR only apply to IMS procedures used over the 3GPP PS domain. |
36.444 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M3 Application Protocol (M3AP) | TS | 1.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.444/36444-100.zip | |
36.445 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M1 data transport | TS | 1.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.445/36445-100.zip | |
36.801 | Evolved Universal Terrestrial Radio Access (E-UTRA); Measurement Requirements | TR | 0.0.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.801/36801-001.zip | The present document should identify the required UE and BS measurements for E-UTRA, e.g. for mobility, positioning, and traffic. It should also identify the requirements, i.e. the measurements interval, the reporting accuracy, granularity and performance requirements. Furthermore it should also identify the constraints, content and size of neighbour cell lists, e.g. multi mode multi RAT operation, provisioning of measurement occurances need for parallel measurements, i.e. mobility and positioning. The purpose of this TR is to provide specification support for RAN WG1,2,3,4.
This document is intended to gather the agreements rather than comparing different solutions.
NOTE: This document is a living document, i.e. it is permanently updated and presented to TSG-RAN meetings. |
36.803 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | TR | 1.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.803/36803-110.zip | The purpose of this TR is to summarize the study of radio requirements for the User Equipment (UE) radio transmission and reception as part of the work item on Evolved Universal Terrestrial Radio Access (E-UTRA). |
36.804 | Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception | TR | 1.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.804/36804-120.zip | The present document summarizes the studies of radio requirements for the Base Station (BS) radio transmission and reception as part of the work item on Evolved Universal Terrestrial Radio Access (E-UTRA). |
36.902 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Self-configuring and self-optimizing network (SON) use cases and solutions | TR | 1.2.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.902/36902-120.zip | The present document provides descriptions of agreed use cases and solutions with regards to self configuring and self optimizing networks.
The scope of the self configuring and self optimizing functionality is defined in TS 36.300 [2]. |
22.258 | Service requirements for an All-IP Network (AIPN); Stage 1 | TS | 7.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.258/22258-700.zip | The present document describes the service requirements for the All-IP Network (AIPN) including service requirements for Evolved UTRA and UTRAN. Where appropriate, references are made to service requirements within other 3GPP specifications that are applicable to the AIPN. |
22.259 | Service requirements for Personal Network Management (PNM); Stage 1 | TS | 7.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.259/22259-730.zip | |
22.982 | Study of Customised Alerting Tone (CAT) requirements | TR | 0.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-030.zip | |
23.125 | Overall high level functionality and architecture impacts of flow based charging; Stage 2 | TS | 7.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.125/23125-700.zip | The present document specifies the overall high level functionality and architecture impacts of Flow Based Charging. |
23.259 | Personal Network Management (PNM); Procedures and information flows; Stage 2 | TS | 0.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-040.zip | |
23.803 | Evolution of policy control and charging | TR | 7.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.803/23803-700.zip | The present document intends to study the following items:
1) Complete harmonization and merger of the policy control and flow based charging architecture and procedures;
2) Possible architectures and solutions for adding end-user subscription differentiation and general policy control aspects to the policy- and charging control;
3) Alternative solutions for binding bearers to services (provided today by the authorization token). This includes studying solutions for the network to control bearer usage by service flows.
Editors Note: The document may also study the impact on policy control and flow based charging architecture based on the conclusion and approved recommendations of the E2E QoS Work Item in a Release 7 context if deemed feasible. |
23.805 | Selective disabling of User Equipment (UE) capabilities; Report on technical options and conclusions | TR | 0.3.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.805/23805-031.zip | The present document presents an assessment of different service architecture implementations for the new Selective Disabling of UE Capabilities specified in TS 22.011, Section 4.5.
For each service architecture the document provides:
• A detailed description of the architecture
• An assessment of the architecture against the SA1 requirements described in TS 22.011, Section 4.5.
• An assessment of the architecture’s strengths and weaknesses
The document provides a conclusion identifying the preferred service architecture of the SA2 TSG. |
23.807 | Feasibility study for enhancement of radio performance for Voice over IP Multimedia Subsystem (VoIMS); Report on technical options and conclusions | TR | 0.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.807/23807-030.zip | The present document describes architecture changes for Voice over IMS service to allow enhancement of radio performances in RAN. This work focuses on the PS domain with the assumption that voice services are supported in this domain.
Two radio optimization methods have been identified to provide radio optimisation for VoIMS: Unequal Error Protection (UEP) and Header Removal (HR). With the information currently available in RNC, RNC cannot use these optimisation methods. More study is then needed to describe which additional information are needed by RNC and how these information can be provided to RNC.
Radio optimisations for the SIP signalling are out of the scope of this TR. The study will focus on the bearer optimisation for user data.
Radio optimisations with no architecture impact outside the UTRAN are out of the scope of this TR. |
23.808 | Supporting Globally Routable User Agent URI in IMS; Report and conclusions | TR | 1.0.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.808/23808-101.zip | The present document is a temporary container for the architectural impacts on IM CN subsystem for supporting GRUU. The contents of this report when stable will be the base for CRs to 3GPP Technical Specifications e.g. TS 23.228 [2].
GRUU is a URI, the creation and use of which is defined in an IETF specification draft-ietf-sip-gruu-0 [1] in order to route SIP messages to a specific SIP User Agent (UA) instance. The support of GRUU in IMS is to enable routing of SIP messages to a specific instance of a registered public user identity even when a single public user id is registered from multiple UEs. |
23.809 | One Tunnel solution for Optimisation of Packet Data Traffic | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.809/23809-100.zip | The present document is a temporary container for a stage-2 like description of an architecture that uses direct tunnelling of user plane data between the RNC and the GGSN, which is known as One Tunnel approach. The content of this report when stable will be moved into 3GPP Technical Specification TS 23.060 [1].
This report will further develop the One Tunnel approach described in TR 23.873 [2] and identify what changes are needed to PS core and potentially to UTRAN functionalities and protocols to support the One Tunnel functionality. This include the investigation of the functions added after Rel‑4 up to Rel‑6 (e.g. Iu-flex, Network sharing, MBMS, etc) and either verify that they are not affected or address any conflicts between these functions and the One Tunnel function.
The resulting system architecture shall be fully interoperable with pre-Rel‑7 nodes and it should retain the existing network capabilities, or those that cannot be delivered need to be clearly documented. |
23.817 | Feasibility study on enhancement of radio performances for Voice over IMS (VoIMS); Report on Technical options and conclusions | TR | 0.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.817/23817-010.zip | The present document describes architecture changes for Voice over IMS service to allow enhancement of radio performances in RAN. This work focuses on the PS domain with the assumption that voice services are supported in this domain.
Two radio optimization methods have been identified to provide radio optimisation for VoIMS: Unequal Error Protection (UEP) and Header Removal (HR). With the information currently available in RNC, RNC cannot use these optimisation methods. More study is then needed to describe which additional information are needed by RNC and how these information can be provided to RNC.
Radio optimisations for the SIP signalling are out of the scope of this TR. The study will focus on the bearer optimisation for user data.
Radio optimisations with no architecture impact outside the UTRAN are out of the scope of this TR. |
23.818 | Optimisations and Enhancements for Realtime IMS Communication | TR | 0.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.818/23818-0a0.zip | The scope of the technical report is to capture the results of a study into the optimisations and enhancements of the system for mass market real-time communication (IMS multimedia telephony).
The objective is to provide a study into optimisations and enhancements for the support realtime services based on IMS with regards to the following aspects:
- Analysis of IMS session establishment procedures (e.g. signalling flows, bearer establishment) in order to reduce call establishment time for multimedia telephony to obtain the same, or at least similar, characteristics as exists for CS telephony;
- Analysis of impacts of any non call related IMS signalling (e.g. due to Presence) on the efficiency and service aspects of active real time communication sessions and the establishment of such sessions;
- Analysis into mechanisms to inform the IMS of loss of the signalling bearer transport through the IP-CAN;
- Analysis and identification of architecture and information flow impacts due to the dynamic allocation of users to Application Servers, including analysing any potential impacts at initial registration, session establishment and provision of user data in the HSS;
- Identification of any stage 2 impacts in order to support multimedia telephony services;
- Efficient interworking with other VoIP networks, e.g. regarding call establishment time and simplified call flows.
The study is intended to provide conclusions on the above aspects with respect to future normative specification work. |
23.819 | Terminating session handling | TR | 1.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.819/23819-130.zip | 3GPP has specified how to combine CS call and IMS Sessions but has not yet addressed the interworking between e.g. a pure IMS voice/video session and a combination of a CS call and an IMS session.
The present document studies how to handle terminating real-time sessions and calls taking into account different domains (CS, IMS) and different UE capabilities (CSI, IMS VoIP, etc.). |
23.836 | Quality of Service (QoS) and policy aspects of 3GPP - Wirless Local Area Network (WLAN) interworking | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.836/23836-100.zip | Some 3GPP PS based services (e.g. VoIP over IMS, PS streaming, etc) require strict QoS provisioning. In order to support such services over I-WLAN, QoS Provisioning in 3GPP-WLAN Interworking is required.
IEEE 802.11 WLAN standards are currently not supporting QoS mechanisms, therefore QoS provisioning was not considered in Rel-6 work for 3GPP-WLAN Interworking. As IEEE is currently finalizing QoS amendments to 802.11 WLAN standards, QoS-related aspects of the 3GPP-WLAN architecture should be studied.
In the context of end-to-end QoS provisioning being studied in TR 23.802, provisioning of QoS within I-WLAN as an IP-CAN is important. It shall be defined if and how QoS provisioning in I-WLAN can interact with the end-to-end QoS framework.
Flow based charging and service/subscription based policy control are studied in TR 23.803 as generic features to support the access to PS based services from different IP-CANs. In order to leverage the generic charging and service/subscription based policy control within I-WLAN as another IP-CAN, the Gateway element in case of 3GPP-WLAN Interworking has to provide the needed functionalities, e.g. for Policy Enforcement.
The followings are objectives of the document.
- investigate the necessity and reliability of the applicable QoS mechanism between the WLAN UE and PDG, and the possible impacts to the 3GPP-WLAN interworking entities;
- ensure that the architecture for 3GPP/WLAN Interworking defined by TS 23.234 is supported by the following QoS-related mechanisms being developed in 3GPP:
a. E2E QoS architecture being studied in TR 23.802;
b. Policy and charging evolution capabilities being studied in TR 23.803. |
23.837 | Location Services (LCS) architecture for 3GPP system - Wireless Local Area Network (WLAN) interworking | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.837/23837-100.zip | The present document investigates solutions for providing LCS over 3GPP WLAN interworking architecture. The architectural requirements and different possible LCS architectures to provide the location services over I-WLAN are analyzed. The procedures to obtain the location information of a WLAN UE attached to I-WLAN network are also studied. The LCS aspects for I-WLAN as IP-CAN in the IMS Emergency call, i.e., the emergency location information handling for I-WLAN are described in this TR. |
23.847 | Enhancements to IMS service functionalities facilitating multicast bearer services | TR | 0.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.847/23847-020.zip | This study analyzes the feasibility and applicability of using multicast bearers (e.g. MBMS) in the context of IMS-based applications.
This study item captures the results of the technical considerations and solutions for transporting IMS services over multicast bearers with a focus on the possible enhancements to IMS functionalities and relevant charging, security and service provision procedures.
A brief summary of considerations include:
- Signalling procedures of multicast enabled IMS services should be analyzed based on the grouped communication scenarios and possible optimisations to the delivery mechanisms should be investigated.
- Charging and policy control procedures according to the PCC architecture.
- Service provision procedures both in network elements and UEs.
- Possible security requirements to multicast enabled IMS functionalities and bearer service entities.
- Real-time QoS requirements e.g. delay , interruption.
- UE capability requirements. |
23.882 | 3GPP system architecture evolution (SAE): Report on technical options and conclusions | TR | 1.15.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.882/23882-1f1.zip | The objective of this feasibility study is to develop a framework for an evolution or migration of the 3GPP system to a higher-data-rate, lower-latency, packet-optimized system that supports, multiple RATs. The focus of this work will be on the PS domain with the assumption that voice services are supported in this domain.
NOTE: This feasibility study has led into work items specifying LTE/SAE and the contents of this study should be considered out of date.
The main objectives are to address the following aspects:
1) Overall architecture impacts stemming from requirements coming out from TSG-RAN's Study Item on Radio Evolution (see SP‑040915). The architectural developments should take into account the targets for the evolution of the radio-interface, e.g.:
i) whether there is a need for a modified network architecture and/or different functional split between network nodes (compared to the current 3GPP architecture);
ii) how to provide a very low latency (including C-plane) for the overall network (including core network, radio access network and radio access technology);
iii) how to provide the efficient support of the various types of services, especially from the PS domain (e.g. Voice over IP, Presence).
2) Overall architecture impacts stemming from the work in SA1 on an All-IP Network (AIPN) (see TS 22.258 [4]), e.g.:
i) support of a variety of different access systems (existing and future) and access selection based on combinations of operator policies, user preferences and access network conditions;
ii) how to realize improvements in basic system performance e.g. communication delay, communication quality, connection set-up time, etc.;
iii) how to maintain the negotiated QoS across the whole system; in particular to address inter-domain and inter-network interworking, and, QoS on the network link to the Base Station site.
NOTE: Although used in the SA WG1 TS 22.258 [4], the All-IP Network (AIPN) term is not used in the network architecture in this SAE TR as mapping between the term AIPN used in SA1 and the evolved architecture is not deemed necessary to progress the SAE work. Instead, the requirements on AIPN in TS 22.258 [4] are treated as overall system requirements. Even though the AIPN includes an evolved, IP based, core network and evolved IMS domain, the scope of this SAE TR does not include the IMS domain aspects.
3) Overall architecture aspects of supporting mobility between heterogeneous access networks, including service continuity. E.g.:
i) service continuity between I-WLAN and the 3GPP PS domain;
ii) how to support multiple radio access technologies and terminal mobility between different radio access technologies;
iii) how to maintain and support the same capabilities of access control (authentication, authorization), privacy and charging when moving between different radio access technologies.
Migration aspects should be taken into account for the above, i.e. how to migrate from the existing architecture.
In the course of conducting this feasibility study additional individual Work Items may be identified and prepared to address certain aspects and to take care of the respective specification work. The timelines of those Work Items may or may not concur with the timeline of this feasibility study. |
24.259 | Personal Network Management (PNM); Stage 3 | TS | 0.6.2 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.259/24259-062.zip | |
25.812 | Requirements for evolved Universal Terrestrial Radio Access (UTRA) and Universal Terrestrial Radio Access Network (UTRAN) | TR | 0.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.812/25812-000.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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.