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 |
|---|---|---|---|---|---|---|
32.837 | Gap analysis between 3GPP SA5 specifications and Next Generation Mobile Networks (NGMN) Next Generation Operations Requirements (NGCOR) | TR | 0.13.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.837/32837-0d0.zip | The present document makes a gap analysis between the Next Generation Mobile Networks (NGMN) Alliance's "Next Generation Converged Operations Requirements (NGCOR) Requirements" [2] as compared to 3GPPRelease 13 OAM Technical Specifications, and provides recommendation towards NGCOR compliance including suggestions for further 3GPP specification enhancements.
This document addresses the compliance information corresponding to the publication of NGCOR phase II, "NGCOR NEXT GENERATION CONVERGED OPERATIONS REQUIREMENTS" V1.4 [22]. |
33.806 | Pilot development of Security Assurance Specification for MME Network Product class for 3GPP network product classes | TR | 0.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.806/33806-090.zip | The present document … |
33.895 | Study on Security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | TR | 1.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.895/33895-100.zip | The present study investigates the security aspects of the service requirements specified by SA1 in TS 22.101 [11] clause 26, on the integration of SSO frameworks with 3GPP networks for various operator authentication configurations (e.g. configurations using GBA or not using GBA).
In particular, this study evaluates existing interworking solutions between SSO frameworks and 3GPP authentication mechanisms against the SA1 service requirements. The study is not limited to evaluation of existing interworking solutions and new interworking solutions may be developed as appropriate.
The study covers the security requirements to enable the operator to become the preferred SSO Identity Provider by allowing the usage of credentials on the UE for SSO services, as well as ways for the 3GPP operator to leverage its trust framework and its reliable and robust secure credential handling infra-structure to provide SSO service based on operator-controlled credentials. |
36.833-1-08 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 8 | TR | 0.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-08/36833-1-08-040.zip | The present document is a technical report of the work item for LTE Advanced Contiguous Carrier Aggregation in Band 8 which was initially approved at TSG RAN #67 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications. |
36.881 | Study on latency reduction techniques for LTE | TR | 0.8.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.881/36881-080.zip | This document is related to the technical report for the study item “Study on latency reduction techniques for LTE” [2]. The purpose of this TR is to capture the findings from TSG RAN WG2 and WG1 according to their respective objectives, and to draw a conclusion on way forward.
This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings. |
36.898 | Network Assistance for Network Synchronization | TR | 1.9.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.898/36898-190.zip | The present document captures the results of the study item on Network Assistance for Network Synchronization in LTE in RP-151084 [2]. It identifies the existing LTE functions that may need network based synchronization and their synchronization-related requirements, and reviews and compares techniques for enhancement of RAN functionality. |
41.033 | Lawful Interception requirements for GSM | TR | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.033/41033-d00.zip | This Technical Report describes the interface requirements of a mechanism which will deliver intercept from GSM mobile stations, including both speech and data product.
The stage 1 description of Lawful Interception will be specified in 3GPP TS 42.033.
The stage 2 description of Lawful Interception will be specified in 3GPP TS 43.033. |
42.033 | Lawful Interception; Stage 1 | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.033/42033-d00.zip | This Technical Specification provides the stage 1 description for a lawful interception function to be implemented in a given GSM PLMN in order for a network operator to be able to fulfil national lawful requirements. It shall be noted that national variation may exist but it is not the intention for this specification to encompass all of them. The purpose of this specification is to cover the options which may be selectable according to national regulations or as required by the GSM PLMN operator in co-operation with their suppliers.
In the preparation of this specification general reference was made to the European Union Council Resolution, January 1995: "International Requirements for the Lawful Interception of Telecommunications". |
43.033 | 3G security; Lawful Interception; Stage 2 | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.033/43033-d00.zip | The present document gives the stage 2 description of Lawful Interception within a PLMN for circuit switched systems and GPRS. It does not address the interface between the PLMN and the LEA lawful intercepted product and related information collection functions. This is outside the scope of the GSM standard.
The structure of the present document is as follows:
- clause 4 covers the architecture of the interception system;
- clause 5 describes how interception is activated, deactivated and interrogated within the interception system;
- clause 6 describes how the system is provisioned, defines events at which interception takes place and what kind of information is generated at each event;
- clause 7 provides brief descriptions of various intercept cases;
- clause 8 reviews security requirements for access to the interception system;
- annex A provides information flows to illustrate when intercepted traffic and related data is generated;
- annex B describes an interception system for GPRS. The annex is subdivided into 5 sections that are identical in structure to clauses 4 through 8, but applicable to a GPRS clause rather than a GSM circuit switched system. |
44.118 | Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol; Iu mode | TS | 13.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.118/44118-d00.zip | |
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 | 13.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.160/44160-d00.zip | |
45.876 | Uplink Multi-User MIMO | TR | 0.2.0 | R6 | https://www.3gpp.org/ftp/Specs/archive/45_series/45.876/45876-020.zip | The present document details the output of the 3GPP study item on UL MU-MIMO [2]. It is intended to gather information in order to draw a conclusion on the UL MU-MIMO technology based on the link level and system level evaluations.
The following items are covered in this document:
• Objectives for the study.
• Concept description.
• Performance evaluations.
• Complexity analysis. |
22.817 | Study on UICC/USIM enhancements | TR | 0.4.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.817/22817-041.zip | The present report identifies use cases and potential requirements for new USIM services with a focus on:
- Instances where the USIM is used inside terminals with specialised functionalities (e.g. radio modems, 3G Notebook terminals);
- Possible enhancements to facilitate USIM-UICC support for new services;
• Possible enhancements to facilitate an improved user experience when interacting with the UE; and
- Evolution from the USAT towards multimedia USIM toolkit support.
The present report covers only use cases and services that cannot be fully implemented and easily realised using the existing standards, but instead require some enhancement of the present UICC/USIM requirements. Alternative technical solutions (i.e. non USIM-based solutions) are also introduced and referenced for use cases in order to provide a more complete picture of how they might best be realised. |
23.704 | Study on Circuit Switched (CS) / Packet Switched (PS) coordination in shared network; Stage 2 | TR | 1.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.704/23704-110.zip | The present document investigates relevant scenarios and possible solutions to enhance the CS/PS Coordination in a shared UTRAN/GERAN network as currently specified in TS 23.251 [2].
Within this technical report relevant mobility scenarios shall be investigated and it shall be evaluated per scenario if any issues with CS/PS Coordination can be expected. The investigation shall be done for non-supporting UEs and for any UE in shared networks where no Multiple PLMN list is broadcasted. Solutions to solve found issues shall be evaluated and agreed for subsequent normative specification.
The scenarios that need to be handled will at least include:
- CS handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- PS Handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- Redirection;
- Cell reselection;
- CSFB;
- rSRVCC and SRVCC;
- PLMN selection at handover based on UE capability;
- Registration to PS domain in a shared network after CS only registration has been performed. |
23.705 | Study on system enhancements for user plane congestion management | TR | 0.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.705/23705-0b0.zip | The present document studies and defines system enhancements for user plane congestion management based on the Stage-1 normative requirements defined in TS 22.101 [3].
Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces are identified.
Normative specifications will be developed based on the conclusions of the present document. |
23.861 | Network based IP flow mobility | TR | 1.16.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.861/23861-1g0.zip | Release 8 EPS introduced a multi access 3GPP system where different heterogeneous access systems are connected to a common core network. However, in Release 8 EPS, the subscriber cannot communicate using multiple accesses simultaneously. The subscriber can establish a single PDN connection or multiple simultaneous PDN connections in Release 8 EPS, but all the traffic exchanged by the subscriber, regardless of the PDN connection it belongs to, is routed through the same access system. Similarly, Release 8 introduced mobility enhancements to the I-WLAN architecture to support session continuity for any application between 3GPP and I-WLAN accesses, but this will not be further developed in Rel‑13.
Devices with multiple wireless interfaces (e.g. 3GPP , WLAN, etc.) are becoming commonly available and the set of applications running in the mobile devices is diversifying with some applications suited to run over 3GPP access systems and other applications well suited to run over some other - complementary - access systems (e.g. ftp transfer via WiFi in parallel to VoIP over LTE).
The scope of this document is to study the scenarios, requirements and solutions for UEs with multiple interfaces which will simultaneously connect to 3GPP access and one, and only one, non-3GPP WLAN access.
The clause 7.1 refer to the study for the support of IP flow mobility for s2c completed in Rel‑10 and the results have been transferred in TS 23.261. This clause will not be modified nor maintained during Rel‑13 work. Solutions which was studied includes the possibility of dynamically routeing to specific accesses individual flows generated by the same or different applications belonging to the same PDN connection. The study of solutions to support routing of different PDN connections through different access systems is also in the scope of this TR. This study item also investigates the mechanisms for provisioning the UE with operator's policies for multi access PDN connectivity and flow mobility.
The scope of Rel‑13 work is to identify the requirements and solutions for UEs with multiple interfaces which are simultaneously connected to 3GPP access and a WLAN access using a network-based mobility protocol, PMIP and GTP based S2a and S2b access to EPS.
The solutions studied from Rel‑13 consider the following aspects:
- The support of a PDN Connection active over multiple accesses simultaneously.
- The association of one or multiple IP flows belonging to a PDN connection to an access system.
- The movement of one or multiple IP flows belonging to a PDN connection between different access systems.
- The triggers for IP flow mobility in the UE and the network.
- UE-initiated and network-initiated NBIFOM.
- The impact and the relationship to 3GPP related policies (e.g. PCC, ANDSF, ISRP, ISMP, RAN policy with no ANDSF etc.), if any, to support NBIFOM.
This work item doesn't include the scenario where the same IP flow is routed via different access system simultaneously.
Scenarios and solutions described in this document are applicable independently of whether IMS or non-IMS applications are used. |
23.896 | Technical Report on Support for fixed broadband access networks convergence | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.896/23896-c00.zip | Editor's note: This clause will describe the scope of the feasibility study for P4C.
This Technical Report addresses stage 2 study for the Evolved Packet System (EPS) to facilitate policy and charging control in the fixed broadband access network in the convergent scenario where a single operator is deploying both the fixed broadband access network and the Evolved Packet Core (EPC).
The scope of this TR is to consider the convergent scenario where the PCRF controls directly the network element(s) in the fixed broadband access without the mediation of a different policy server, such as the BPCF defined in TS 23.139 [20].
The work in this TR takes the fixed broadband accesses as specified by BroadBand Forum as a reference. This does not preclude the applicability of the solutions described in this TR to other types of fixed broadband accesses.
This TR will address policy and charging control for:
- Traffic to/from fixed devices connected to the fixed broadband access network (e.g. PC, IPTV Set top Box).
- Traffic exchanged by 3GPP UEs connected via WLAN or H(e)NB when both the fixed broadband access network and the EPC are under the control of the EPS operator.
The work is organized in the building blocks and this TR address the Building block listed below, for an outline of the content of each building block refers to clause 4:
- BB1: Policy and Charging Control for supporting traffic from fixed terminals and NSWO traffic from 3GPP UEs in fixed broadband access networks (P4C-F).
- BB3: Policy and Charging Control for 3GPP UEs connected to fixed broadband access network via S2b and S2c reference points for EPC routed traffic (P4C-S2bc).
- BB4: Policy and Charging Control for EPC routed traffic over fixed broadband access networks of 3GPP UEs connected via H(e)NB in convergent scenarios (P4C-HeNB).
- BB5: Policy and Charging Control for supporting Layer 2 traffic in fixed broadband access network (P4C-FL2).
- BB6: Policy and Charging Control for 3GPP UEs connected to fixed broadband forum access networks as Trusted network in Convergence scenario (P4C-TC).
NOTE: The Building Block 2 P4C-TI is addressed in TR 23.839 [28]. |
24.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-c00.zip | |
28.403 | Telecommunication management; Performance Management (PM); Performance measurements for Wireless Local Area Network (WLAN) | TS | 0.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.403/28403-010.zip | |
28.601 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.601/28601-c00.zip | The present document describes the Network Resource Model (NRM) Integration Reference Point (IRP) requirements for Interworking WLAN (IWLAN). According to the structure of IWLAN defined in 3GPP TS 23.234 [6], the present document is focusing on the definition of NRM IRP requirements on the 3GPP part (e.g. WAG, PDG, 3GPP AAA, etc). |
28.602 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.602/28602-c00.zip | The present document is an Integration Reference Point (IRP) named "Core Network (CN) and non-3GPP access interworking system Network Resource Model IRP", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management (CM) information to one or several 'IRPManagers' (typically Network Managers) concerning interworking network resources.
According to the structure of IWLAN defined in 3GPP TS 23.234 [5], several nodes are defined in 3GPP (e.g. WAG, PDG, 3GPP AAA, etc). The present document is focusing on the definition of NRM IRP IOCs for management support.
It reuses relevant parts of the generic NRM in 3GPP TS 28.622 [6], either by direct reuse or sub-classing, and in addition to that defines I-WLAN specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP IS (3GPP TS 32.602 [7]) or the Bulk CM IRP IS (3GPP TS 32.612 [8]). However, which Interface IRP that is applicable is outside the scope of the present document.
The present document supports the Federated Network Information Model (FNIM) concept described in 3GPP TS 32.107 [16] in that the relevant Information Object Classes (IOCs) defined in the present document are directly or indirectly inherited from those specified in the Umbrella Information Model (UIM) of 3GPP TS 28.620 [17]. |
28.606 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.606/28606-c10.zip | The present document is part of an Integration Reference Point (IRP) named Core Network (CN) and non-3GPP access Interworking System Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Core Network (CN) and non-3GPP access Interworking System resources. The Core Network (CN) and non-3GPP access Interworking System NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the Core Network (CN) and non-3GPP access Interworking System NRM IRP.
This Solution Set specification is related to 3GPP TS 28.602 V12. 0.X [4]. |
28.682 | Telecommunication management; Wireless Local Area Network (WLAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 0.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.682/28682-020.zip | |
29.161 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services with Wireless Local Area Network (WLAN) access and Packet data Networks (PDN) | TS | 12.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.161/29161-c00.zip | The present document defines the requirements for Packet Domain interworking between a:
a) PLMN with WLAN access and PDN;
b) PLMN with WLAN access and PLMN.
The present document also defines, in clause 12, the usage of Radius at the Pp Reference Point between the Packet Data Gateway and the Presence Network Agent, see 3GPP TS 23.141 [18]. |
31.901 | Review of dedicated 3GPP UICC features (Red_UCe) | TR | 1.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.901/31901-100.zip | The present document presents a review of the USIM, ISIM and the related Toolkit aspects (respectively found in TS 31.102 [3], TS 31.103 [4] and TS 31.111 [5]) features and their mandatory/optional support in the light of actual use or demand in the field is to be conducted. The technical report documents the justification for the support of features identified as not being implemented or required (e.g. from SA1 requirements). When a common understanding is reached about a potential need for a modification of the required support of a feature, it will be listed for further consideration by CT6. Should any normative work be derived from the content of the study, it will be carried out as part of a separate work item. |
32.176 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.176/32176-c00.zip | The present document is part of an Integration Reference Point (IRP) named Subscription Management (SuM) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning SuM resources. The SuM NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the SuM NRM IRP.
This specification is related to 3GPP TS 32.172 [5] V10.2.X. |
32.252 | Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.252/32252-c00.zip | The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain and subsystem (offline charging);
- the content of real-time charging messages per domain / subsystem (online charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in 3GPP TS 32.240 [1].
The present document specifies the Offline and Online Charging description for the 3GPP interworked Wireless LAN (WLAN), based on the functional stage 2 description of 3GPP WLAN interworking in 3GPP TS 23.234 [201] as well as the Charging support and Charging differentiation for Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems, based on the functional stage 2 description of mobility between 3GPP-WLAN and 3GPP systems in 3GPP TS 23.327 [202]. This charging description includes the offline and online charging architecture and scenarios specific to the 3GPP interworked WLAN, as well as the mapping of the common 3GPP charging architecture specified in 3GPP TS 32.240 [1] onto the 3GPP interworked WLAN. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in 3GPP TS 32.240 [1].
- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3GPP TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in 3GPP TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the billing system or a mediation device) is specified in 3GPP TS 32.297 [52].
- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in 3GPP TS 32.299 [50].
- The Online and Offline Charging description for Trusted WLAN Access Network to the 3GPP EPC, based on the functional stage 2 description in 3GPP TS 23.402 [209], is specified in 3GPP TS 32.251 [11].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 3GPP TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document 3GPP TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [102]. |
32.646 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.646/32646-c00.zip | The present document specifies the Solution Sets for the UTRAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.642 V11.4.X [4]. |
32.652 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.652/32652-c00.zip | The present document specifies the GERAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. |
32.656 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.656/32656-c00.zip | The present document specifies the Solution Sets for the GERAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.652 V11.2.X [4]. |
32.676 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.676/32676-c00.zip | The present document specifies the Solution Set (SS) definitions for the IRP whose semantics is specified in State Management IRP: Information Service (IS) (3GPP TS 32.672 [1]).
This Solution Set definitions specification is related to 3GPP TS 32.672 V11.0.X. |
32.796 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.796/32796-c00.zip | The present document is part of an Integration Reference Point (IRP) named Generic Radio Access Network (RAN) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Generic RAN resources. The Generic RAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the Generic RAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.792 V11.0.X [4]. |
32.838 | Telecommunication management; Gap analysis between 3GPP SA5 specifications and NGMN Top Operational Efficiency (OPE) recommendations | TR | 1.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.838/32838-190.zip | The present document provides a gap analysis between NGMN Top OPE Recommendations [2] and OAM capabilities offered by 3GPP SA5 Integration Reference Points (IRPs).
Based on this gap analysis, it provides a support status of SA5 specifications against NGMN Top OPE Recommendations. For each Top OPE Recommendation, the SA5 solution is described when it exists. Otherwise, some action may be considered to address the Top OPE recommendation.
Based on that information, a support status is produced which can take the following values:
- Supported,
- Partially Supported,
- Not Supported,
- Not Applicable. |
32.839 | Management Specification Tooling Environment | TR | 0.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.839/32839-011.zip | As a result of the analysis of the requirements for the harmonization of the 3GPP and TM Forum Information Models in the context of FMC basic use cases were developed [1], [2]. These use cases led to the recognition that it would be necessary to define common operation model elements applicable for wire-line and wireless networks. This document defines these common model elements.
To be noted:
- The Umbrella Operation Model (UOM) described in this document provides the set of interfaces/operations etc. that have been agreed for convergence to strengthen consistency of representation and semantics of network management operations in the fixed and mobile environments.
- The UOM is necessary but not sufficient for implementation.
- The UOM cannot be used directly for implementation. Implementation classes must be derived from those in the UOM by Inheritance or some other appropriate mechanism.
- Classes derived from those in the UOM (e.g. for the fixed environment) may use different names from those used in the UOM. |
32.849 | Study on Charging aspects of Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks | TR | 1.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.849/32849-110.zip | The objective of this study item is to document missing elements and information with regard to the roaming architecture for Voice over IMS with Local Breakout.
The present document collects and evaluates end-to-end roaming scenarios under different aspects of charging. The main scenarios presented will include mobile originating calls with and without the use of the loopback mechanism and mobile terminating call scenarios.
It will analyse operator requirements in consideration of the roaming scenarios and the existing Charging specifications
The conclusions are presented in a further clause with assumptions made and proposed further proceedings on that issues. |
33.268 | Security aspects of Public Warning System (PWS) | TS | 0.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.268/33268-001.zip | This clause shall start on a new page.
The present document … |
33.833 | Study on security issues to support Proximity Services (ProSe) | TR | 1.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.833/33833-180.zip | The present document contains a study of the security aspects of Proximity Services (ProSe) and an evaluation of possible technical solutions needed to support such services. The Stage 1 requirements for these services are defined in TS 22.278 [2] and TS 22.115 [3]. These requirements include a list of general requirements on ProSe Security, Authorization and Privacy (TS 22.278 [2] clause 9.4), which are taken into consideration when developing the security key issues, security requirements and security solutions in the present document.
Different possible Stage 2 solutions for Proximity Services are studied in TR 23.703 [4].
Normative provisions/requirements are included in the present specification solely for the purposes of studying solutions and are not to be considered as implying normative requirements on 3GPP entities.
NOTE: Lawful Interception (LI) aspects are not covered in this document. |
33.895 | Study on Security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | TR | 0.12.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.895/33895-0c0.zip | The present study investigates the security aspects of the service requirements specified by SA1 in TS 22.101 [11] clause 26, on the integration of SSO frameworks with 3GPP networks for various operator authentication configurations (e.g. configurations using GBA or not using GBA).
In particular, this study evaluates existing interworking solutions between SSO frameworks and 3GPP authentication mechanisms against the SA1 service requirements. The study is not limited to evaluation of existing interworking solutions and new interworking solutions may be developed as appropriate.
The study covers the security requirements to enable the operator to become the preferred SSO Identity Provider by allowing the usage of credentials on the UE for SSO services, as well as ways for the 3GPP operator to leverage its trust framework and its reliable and robust secure credential handling infra-structure to provide SSO service based on operator-controlled credentials. |
36.832 | LTE in the 1670-1675MHz Band for the United States | TR | 1.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.832/36832-100.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.833 | Intra-band Non-contiguous CA for Band 4 for LTE | TR | 0.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.833/36833-020.zip | This clause shall start on a new page.
The present document is the technical report for the LTE Advanced Intra-band Non-contiguous Carrier Aggregation in Band 4 work item, which was approved at TSG RAN #56 [2]. |
36.834 | LTE Advanced intra-band contiguous Carrier Aggregation in Band 3 | TR | 0.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.834/36834-030.zip | The present document is a technical report of the work item for LTE-Advanced Intra-band Contiguous Carrier Aggregation in Band 3 which was approved at TSG RAN #57 [3]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications. |
36.838 | Intra-band contiguous CA in Band 27 for LTE | TR | 0.0.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.838/36838-001.zip | The present document is a technical report of the work item for LTE Advanced Contiguous Carrier Aggregation in Band 27 which was initially approved at TSG RAN #58 [2]. A revised WID was approved at TSG RAN #59 [3]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications. |
36.841 | Evolved Universal Terrestrial Radio Access (E-UTRA); Intra-band non-contiguous Carrier Aggregation (CA) for band 25 for LTE | TR | 12.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.841/36841-c00.zip | The present document is a technical report of the LTE Advanced Intra-band Non-contiguous Carrier Aggregation in Band 25 work item which was approved at TSG RAN #53 [2]. The objective of this work item is to provide specification support for intra-band non-contiguous carrier aggregation in LTE FDD Band 25.
The report provides motivation, requirements and a list of recommended changes to the specifications. |
36.844 | Study on expansion of LTE in the 1670-1675 MHz Band for the United States to include 1670-1680 MHz Band | TR | 12.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.844/36844-c00.zip | The present document is a technical report for “Expansion of LTE_FDD_1670_US to include 1670-1680 MHz Band for LTE in the US” study item, which was approved at 3GPP TSG RAN#59 [2]. The ID assigned to the study item is FS_LTE_FDD_1670_US. The objective of this study item is to facilitate and harmonize the characteristics and efficient use of 1670-1680MHz DL duplexed with band 24 UL for LTE FDD deployment in US. In addition to the schedule and status of the study items, the report includes a description of the motivation, requirements, study results and specification recommendations. |
36.851 | Inter-band carrier aggregation | TR | 1.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.851/36851-100.zip | The present document is a technical report for Inter-band Carrier Aggregation under Rel-12 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-12 band combinations in table 1-1.
Table 1-1: Release 12 inter-band carrier aggregation combinations
WI code
WI title
Class
LTE_CA_B1_B7
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 7
A3
LTE_CA_B2_B4
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 4
A4
LTE_CA_B23_B29
LTE Advanced inter-band Carrier Aggregation of Band 23 and Band 29
A1
LTE_CA_B3_B26
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 26
A1
LTE_CA_B3_B19
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 19
A1
LTE_CA_B1_B8
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 8
A1
LTE_CA_B3_B28
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 28
A1
LTE_CA_B1_B26
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 26
A1
LTE_CA_B39_B41
LTE Advanced inter-band Carrier Aggregation of Band 39 and Band 41
A3
LTE_CA_B2_B12
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 12
A1
LTE_CA_B2_B13
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 13
A1
LTE_CA_B19_B21
LTE Advanced inter-band Carrier Aggregation of Band 19 and Band 21
A5
LTE_CA_B12_B25
LTE Advanced inter-band Carrier Aggregation of Band 12 and Band 25
A1
LTE_CA_B2_B5
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 5
A1
LTE_CA_B1_B18
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 18
A1
LTE_CA_B7_B28
LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 28
A1
LTE_CA_B5_B25
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 25
A1
LTE_CA_B1_B11
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 11
A5
LTE_CA_B8_B11
LTE Advanced inter-band Carrier Aggregation of Band 8 and Band 11
A5
LTE_CA_B5_B7
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 7
A1
LTE_CA_B1_B3
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 3
A3
LTE_CA_B1_B28
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 28
A2
LTE_CA_B4_B27
LTE Advanced inter-band Carrier Aggregation of Band 4 and Band 27
A1
LTE_CA_B3_B27
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 27
A1
LTE_CA_B8_B27
LTE Advanced inter-band Carrier Aggregation of Band 8 and Band 27
A3
LTE_CA_B3_B20_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 20
A1
LTE_CA_B7_B20_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 20
A1
LTE_CA_B41_B42
LTE Advanced inter-band Carrier Aggregation of Band 41 and Band 42
A5
LTE_CA_B5_B13
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 13
A3
LTE_CA_B7_B22
LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 22
A5
LTE_CA_B2_B5_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 5
A1
The scope of the report has been further extended [6] to cover the 2 DL fallback modes for the 3 DL Carrier Aggregation combinations with single UL configuration. These 3 DL/1UL combinations are listed in table 1-2. In addition, the report also covers the LTE TDD-FDD joint operation including Carrier Aggregation combinations [7], captured in Table 1-3.
Table 1-2: Release 12 inter-band carrier aggregation combinations (3 DL/1UL)
WI code
WI title
LTE_CA_B2_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 5 and Band 30
LTE_CA_B2_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 29 and Band 30
LTE_CA_B1_B5_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 5 and Band 7
LTE_CA_B2_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 30
LTE_CA_B1_B3_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 20
LTE_CA_B1_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 7 and Band 20
LTE_CA_B7_B8_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 8 and Band 20
LTE_CA_B1_B18_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 18 and Band 28
LTE_CA_3DL_FB_BW
Additional bandwidth combinations for LTE Advanced inter-band Carrier Aggregation to support 3DL fallback
LTE_CA_B4_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 7 and Band 12
Table 1-3: Release 12 inter-band carrier aggregation combinations (LTE TDD-FDD joint operation)
WI code
WI title
Class
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 1 and Band 41)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 1 and Band 42)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 3 and Band 40)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 8 and Band 40)
A1
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 3 and Band 42)
A2
LTE_CA_B26_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 26, Band 41 and Band 41
-
LTE_CA_B3_B38
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 38
A3
LTE_CA_B19_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 19, Band 42 and Band 42
A1
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications. |
36.853 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced; LTE-Advanced 3 Band Carrier Aggregation (CA) (3DL/1UL) | TR | 2.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.853/36853-220.zip | The present document is a technical report for 3DL Inter-band Carrier Aggregation under Rel-12 time frame. The purpose is to gather the relevant background information and studies in order to address 3DL Inter-band Carrier Aggregation requirements.
This TR covers relevant background information and studies in order to address 3DL Inter-band Carrier Aggregation requirements for the Rel-12 band combinations in table 1-1.
Table 1-1: Release 12 3DL inter-band carrier aggregation combinations
WI code
WI title
LTE_CA_B2_B2_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 2 and Band 1
LTE_CA_B2_B4_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 4 and Band 13
LTE_CA_B2_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 5 and Band 30
LTE_CA_B2_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 30
LTE_CA_B2_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 29 and Band 30
LTE_CA_B4_B4_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 4, Band 4 and Band 13
LTE_CA_B4_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 5 and Band 30
LTE_CA_B4_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 12 and Band 30
LTE_CA_B4_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 29 and Band 30
LTE_CA_B1_B3_B8
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 8
LTE_CA_B1_B5_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 5 and Band 7
LTE_CA_B2_B4_B5
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 5
LTE_CA_B2_B4_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 12
LTE_CA_B2_B5_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 5 and Band 12
LTE_CA_B2_B12_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 12
LTE_CA_B3_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 20
LTE_CA_B3_B8_B27
LTE Advanced 3 band Carrier Aggregation (3DL/1UL) for Band 3, Band 8 and Band 27
LTE_CA_B4_B5_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 5 and Band 12
LTE_CA_B4_B12_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 12 and Band 12
LTE_CA_B1_B3_B5
LTE Advanced 3 Band Carrier Aggregation(3DL/1UL) for Band 1, Band 3 and Band 5
LTE_CA_B1_B3_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 20
LTE_CA_B1_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 7 and Band 20
LTE_CA_B7_B8_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 8 and Band 20
LTE_CA_B3_B7_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 7
LTE_CA_B3_B3_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 3 and Band 7
LTE_CA_B1_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 42 and Band 42
LTE_CA_B3_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 42 and Band 42
LTE_CA_B1_B3_B19
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 19
LTE_CA_B2_B4_B29
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 29
LTE_CA_B4_B4_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 4 and Band 7
LTE_CA_B4_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 7 and Band 12
LTE_CA_B39_B39_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 39, Band 39 and Band 41
LTE_CA_B39_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 39, Band 41 and Band 41
LTE_CA_B2_B2_B29
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 2 and Band 29
LTE_CA_B1_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 41, and Band 41
LTE_CA_B2_B2_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 2, and Band 12
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications. |
36.855 | Feasibility of positioning enhancements for E-UTRA | TR | 0.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.855/36855-070.zip | Positioning mechanisms were specified in 3GPP as a key feature for E-UTRA networks since Release 9, e.g. OTDOA, E-CID etc. They are not only used in helping meet regulatory requirements, but also utilized with increasing importance to enable all kinds of location based applications.
The proliferation of heterogeneous network deployments brings some challenges also in the area of efficient terminal positioning and calls for the study of enhanced mechanisms and positioning performance requirements.
The addition of multiple nodes in heterogeneous networks can improve the position accuracy remarkably if the specificities of such deployments are taken into account in the positioning mechanisms. Some examples include the support of several transmission points with identical cell IDs and improved support for positioning in carrier aggregation.
Furthermore, the accuracy of current positioning mechanisms and in particular OTDOA and E-CID based on UE Rx-Tx time difference measurement is only defined for limited scenarios:
• Limited channel bandwidth for the cells to be measured (reference and neighbour cells)
• Tests defined assuming single Tx antenna. Practical network might have Tx diversity on antenna port 6 which is used for RSTD measurements
It is desirable to study the possibility of enhanced accuracy for other practical deployment scenarios.
The present document is the Technical Report for the Study Item on positioning enhancements for E-UTRA. |
36.861 | Technical Report for Study Item: Study on LTE FDD in the bands 1980-2010 MHz and 2170-2200 MHz | TR | 0.5.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.861/36861-051.zip | The present document contains the result of the Study item on LTE FDD in the bands 1980-2010 MHz and 2170-2200 MHz, which has been approved in RP-121420 [5] at TSG RAN#57, Sep 2012.
The objective of this study is to facilitate and harmonize the efficient use of these bands for terrestrial IMT, especially LTE, for Korea and other applicable countries in Region 3. |
36.978 | Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE) antenna test function definition for two-stage Multiple Input Multiple Output (MIMO) Over The Air (OTA) test method | TR | 1.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.978/36978-110.zip | The present document contains the findings of the Study Item (FS_LTE_MIMO_OTA_ATF) to describe the antenna test function for the two-stage MIMO OTA test method. |
37.842 | Evolved Universal Terrestrial Radio Access (E-UTRA) and Universal Terrestrial Radio Access (UTRA; Radio Frequency (RF) requirement background for Active Antenna System (AAS) Base Station (BS) | TR | 1.9.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.842/37842-190.zip | The present document is the Technical Report for the Work Item on Base Station (BS) Radio Frequency (RF) requirements for Active Antenna System (AAS), which was approved at TSG RAN#59. The present document captures the background and the decisions on the specification of RF requirements that are applicable to AAS BS. |
37.905 | Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Derivation of test points for User Equipment (UE) radio transmission and reception conformance test cases | TR | 0.0.2 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.905/37905-002.zip | The present document specifies and contains the derivation of Test Points for RF test cases, thereby 3GPP TSG RAN WG5 will have a way of storing the input contributions provided. The test cases are described in TS36.521-1[2].
The test cases which have been analysed to determine Test Points are included as .zip files.
The present document is applicable from Release 10 up to the release indicated on the front page of the present Terminal conformance specifications. |
44.118 | Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol; Iu mode | TS | 12.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.118/44118-c00.zip | |
45.871 | Study on Multiple Input Multiple Output (MIMO) for GSM/EDGE downlink | TR | 0.4.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.871/45871-040.zip | The present document contains investigations carried out and during the 3GPP study item on MIMO for GSM/EDGE Downlink.
The following items are covered in this study report:
- Objectives for the study
- Overview of MIMO for Downlink concept
- Conceptual design of several functional blocks of this solution
- Performance evaluations related to envisaged functional blocks belonging to MIMO for Downlink
- Compatibility analysis |
45.926 | Solutions for GSM/EDGE Base Transceiver Station (BTS) energy saving | TR | 1.7.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.926/45926-170.zip | |
22.801 | Study on non-MTC mobile data applications impacts | TR | 1.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.801/22801-110.zip | To make the network better suited for mobile data applications, the aim/scope of this study is to:
• Capture real world data / analysis.
• Identify services scenarios / use cases for mobile data applications.
• Identify potential problems / issues caused by different mobile data applications.
• Identify potential service and operational requirements for possible enhancements to the system. |
22.888 | Study on enhancements for Machine-Type Communications (MTC) | TR | 0.8.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.888/22888-081.zip | Objective of this work item is to study additional requirements, use cases and functionality beyond that specified by the Release 10 NIMTC work item on the following aspects:
• network improvements for MTC Device to MTC Device communications via one or more PLMNs.
Note: direct-mode communication between devices is out of scope.
• possible improvements for MTC Devices that act as a gateway for 'capillary networks' of other devices.
Note: capillary networks themselves are out of scope of 3GPP.
• network improvements for groups of MTC Devices that are co-located with other MTC Devices.
• improvements on network selection mechanisms and steering of roaming for MTC devices.
• possible enhancements to IMS to support MTC.
• possible improvements for location tracking of MTC Devices.
• service requirements on communications between PLMN and the MTC User/MTC Server (e.g. how the MTC User can set event to be monitored with MTC Monitoring).
• possible service requirements to optimize MTC Devices.
• possible New MTC Features to further improve the network for MTC.
For each of the aspects above, the Study will need to identify what kind of (if any) impacts there are on 3GPP standards. |
22.895 | Study on service aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.895/22895-100.zip | The Single Sign-On (SSO) framework integration with 3GPP network resource and services intends to execute a comprehensive set of use cases and service requirements to serve various operator authentication configurations.
The scope of the Single Sign-On (SSO) integration study is to:
- provide service and deployment scenarios for 3GPP operators adopting an integrated approach to SSO, including web, person-to-person and M2M service scenarios;
- provide transparent identification and seamless authentication to Application Services on behalf of the user;
- support a comprehensive set of use cases of integration of different Identity and SSO frameworks (e.g OpenID) for various operator authentication configurations;
- define use cases and provide service requirements for Operators sharing controlled user credentials with Affiliated Application Service Providers;
- define use cases and service requirements associated with ensuring that the intended user is making use of the associated SSO capability (including the case when the UE has been stolen or lost);
- realize the Identity Provider role within the 3GPP network ecosystem and its influence among outside internet web service providers; and
- provide an enhanced user experience with secure, reliable access and authentication to Affiliated Application Services. |
22.896 | Study on continuity of data sessions to local networks | TR | 1.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.896/22896-110.zip | The present document studies use cases and potential requirements for Continuity of Data Sessions of a UE to Local Networks.
Local IP Access (LIPA) signifies the capability of a UE to obtain access to a local residential/enterprise IP network (subsequently called a local network) that is connected to one or more H(e)NBs and to communicate with entities in the local network through Data Sessions. Basic functionality for Local IP Access (LIPA) has been specified in 3GPP
Rel-10.
The current study item investigates extending LIPA functionality to allow access to the local network when a UE is under coverage of the macro network and provide related mobility support. |
22.988 | Study on alternatives to E.164 for Machine-Type Communications (MTC) | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.988/22988-100.zip | |
23.839 | Study on support of Broadband Forum (BBF) access Interworking | TR | 1.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.839/23839-1a0.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.843 | Study on Core Network Overload (CNO) solutions | TR | 0.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.843/23843-090.zip | The present document investigates core network signalling overload scenarios and potential general handling solutions, in particular:
1. Identify and document events that have occurred and caused network disturbances due to signalling overload. In addition, identify and document scenarios that have high probability of occurrence in the 3GPP network, which may result in signalling overload for core network entities. Such scenarios/events may include HLR/HSS overload by RNC restart, denial of service attacks, and misbehaving/3GPP-non-compliant mobiles causing unpredictable system response;
2. Analyse the criticality of the scenarios and determine whether it is required to take actions for the identified scenarios;
3. Study ways to mitigate and/or eliminate the impact on the core network from signalling overload scenarios that are identified to be critical.
The information provided about the HSS/HLR overload will serve as a starting basis for the study. All currently deployed 3GPP networks should be covered in the study, including LTE
The study should avoid overlap with other parallel activities within 3GPP, and work in close cooperation with the specific WG needs to be maintained.
During the study, if potential security threats such as denial of service attack scenarios are identified, SA WG3 must then be informed to take appropriate measures. |
23.844 | Feasibility study on IP Multimedia Subsystem (IMS) based peer-to-peer content distribution services; Stage 2 | TR | 0.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.844/23844-050.zip | This study focuses on the enhancement of IMS to support Peer-to-Peer Content Distribution Services in respect of GPRS, EPC and other underlying access network technologies but not intend to modify GPRS or EPC for P2P mechanism.
The objectives are to study IMS based Peer-to-Peer Content Distribution Services on the architectural level with the following aspects:
- Creating solutions in order to fulfil the use cases and requirements as defined by SA WG1 while avoiding duplicate work in other SDOs, such as IETF [e.g., PPSP, P2PSIP, ALTO, and DECADE], and re-using their work. The solutions should:
- Apply the same IMS user management/registration procedure as other IMS services;
- Be able to provide the UE with the appropriate AS to obtain the addresses of other Peers, from which the UE can retrieve the requested content;
- Re-use ISC interface for service triggering;
- Be able to select qualified User Peers among available UEs according to the policies preconfigured in the network.
- Elaborate alternative solutions, which support the following network access technologies:
- Mobile access only (e.g. UTRAN, E-UTRAN, I-WLAN);
- Fixed access only (e.g. xDSL, LAN);
- Fixed and mobile convergence scenarios.
- Evaluate possible impacts and improvements on network when IMS based Peer-to-Peer Content Distribution Services are deployed, such as the interactions that are needed to adapt the peer-to-peer overlay properties to the configuration and the resources of the network.
- Identify QoS, mobility, charging and security related requirements in the case of Peer-to-Peer Content Distribution Services on IMS.
The assessment on alternative solutions and the final conclusion of this study should not only take TR 22.906 [2] into consideration but also comply with the related normative work in SA WG1. |
23.852 | Study on S2a Mobility based on GPRS Tunnelling Protocol (GTP) and Wireless Local Area Network (WLAN) access to the Enhanced Packet Core (EPC) network (SaMOG); Stage 2 | TR | 1.7.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.852/23852-171.zip | This Study item is to study:
1. The addition of a S2a based on GTP option. In particular this SID will develop the necessary stage 2 message flows to support S2a based on GTP and mobility between GTP-S5/S8 and GTP-S2a.
2. Supporting WLAN access to EPC through S2a via mechanisms:
2.1 with no impact to the UE;
2.2 with impact to the UE.
Solutions requiring modifications to non 3GPP link-layers will not be considered. It is expected that the result of this Study Item may be used by 3GPP-BBF interworking activities (BBAI). |
23.853 | Operator Policies for IP Interface Selection (OPIIS) | TR | 0.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.853/23853-060.zip | This Technical Report describes solutions that define:
- operator policies for selecting an IP interface in the UE for routing of IP flows among a choice of available interfaces in both 3GPP and non-3GPP accesses;
- system architecture for distribution of these policies to the UE.
Editor's note: The working assumption is that the ANDSF architecture is used for distribution of the operator policies defined in this TR.
The solutions described in this TR shall clarify how the operator policies defined in this TR relate with the ANDSF policies.
The report is intended to document the analysis of the architectural aspects to achieve these objectives in order to select a solution and include it in the relevant technical specifications. |
23.858 | Usage Monitoring Control PCC Enhancement | TR | 0.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.858/23858-070.zip | The scope of this technical report is to capture the results of a study that investigates if enhancements to the existing policy control architecture are needed in the area of usage monitoring control. The goals of the study are to derive possible requirements and architecture enhancements for:
1. Monitoring of service (s) / application (s) in more than one usage monitoring group;
2. Disabling a service (s) / application (s) from the existing usage monitoring group of services/group of applications;
3. Excluding the usage of a particular service (s) / application (s) from the accumulated usage for the IP-CAN session/TDF session;
4. Usage control for a subscriber group, e.g. the members of a family or a company subscriber, or a group of devices belonging to subscribers that share the same usage allowance threshold.
In addition, study the different proposed solutions for effective time based usage monitoring and how associated start and end of usage is defined. |
23.859 | Local IP access (LIPA) mobility and Selected IP Traffic Offload (SIPTO) at the local network | TR | 0.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.859/23859-090.zip | This Technical Report describes the solutions to implement the architectural aspects based on the requirements from TS 22.220 [3], clauses 5.7 and 5.9, and TS 22.101 [2], clause 4.3.5, for LIPA and SIPTO at the local network.
This includes:
- the support of mobility for LIPA between the H(e)NBs located in the local IP network;
- functionality to support Selected IP Traffic Offload requirements at the local network, including mobility.
The report is intended to document the analysis of the architectural aspects to achieve these objectives in order to include the solutions in the relevant technical specifications. |
23.862 | Evolved Packet Core (EPC) enhancements to support interworking with data application providers; Stage 2 | TR | 0.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.862/23862-040.zip | This Technical Report describes solutions for interworking between mobile operators and data application providers. The solutions developed will describe a framework for authentication, authorization, policy and charging for various interworking scenarios.
Solutions developed as part of this work item will cover the following different relationships between mobile operators and data application providers for both roaming and non-roaming cases when
- mobile operator owns all the application layer entities;
- mobile operator does not own all the application layer entities.
The technical report will investigate charging, policy and group addressing capabilities for interworking between mobile operators and data application providers. Updates to 3GPP functions and interfaces will be specified for solutions based on IMS and/or EPC.
On-going work for authentication and other aspects in other 3GPP work items will not be duplicated. It will be investigated whether changes to 3GPP specifications are needed and if so which ones. The work item will focus on impacts to IMS and EPC. |
23.863 | Support of Short Message Service (SMS) in IP Multimedia Subsystem (IMS) without Mobile Station International ISDN Number (MSISDN); Stage 2 | TR | 1.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.863/23863-150.zip | This Technical Report is to specify architecture enhancement toward SMS submit/delivery mechanism in IMS to allow IMS registered UE to:
- Receive and send SMS without requiring an MSISDN associated as part of their IMS subscription record in HSS and
- any possible enhancements towards the related storing and forwarding mechanism if the UE is out of reach.
There are three potential aspects for these IMS UEs without MSISDN that need to be investigated:
1) Server - IMS UE communication via SMS (e.g. for M2M).
2) IMS UE to IMS UE communication via SMS for person to person communications. Both UEs do not have MSISDN.
3) SMS Interworking between IMS UE without MSISDN and traditional UE (e.g. CS) with MSISDN.
Normative specification work (if needed or feasible) for each of these areas can be started independently. |
23.866 | Study on system improvements for energy efficiency | TR | 0.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.866/23866-040.zip | The present document is for investigating deployment aspects that relate to energy efficiency, including potential system enhancements that support energy efficient deployments. System enhancements may be anticipated in the area of functions that have major influence on deployment like functions that support pools of CN nodes or functions that enable multiple CN nodes to serve the same or overlapping areas. The initial focus is on PS domain. This study should avoid any overlap with the work by RAN/CT/SA5 by taking into account the work that has been and is going on in these WGs. Proposals have to be well justified to be considered in this document. |
24.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 11.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-b00.zip | |
25.317 | High Speed Packet Access (HSPA); Requirements on User Equipments (UEs) supporting a release-independent frequency band combination | TS | 11.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.317/25317-b00.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. |
26.951 | Enhancements to Multimedia (EMM); EMM, DDE and IPME Aspects | TR | 2.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.951/26951-200.zip | The present document contains the results of the work items EMM , EMM-DDE and EMM-IPME as approved in SA in SP-120025. This document does not include the results from the EMM-EFEC work item. |
28.101 | Management of Converged Networks; Requirements | TS | 0.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.101/28101-000.zip | The present document is part of a TS family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
TS 32.xy1 Fixed Mobile Convergent (FMC) Network Management; FMC Architecture and Model; Requirements
TS 32.xy2 Fixed Mobile Convergent (FMC) Network Management; FMC Architecture and Model; Stage 2
In a fixed mobile convergent (FMC) network, the services offered to end users need resources from networks of different technologies.
NM standards of different technologies are the responsibilities of various standardization organizations (SDOs) and organizations. Various SDO/organizations may have defined different network management (NM) protocols to manage their respective network resources. Their managed resource models are mostly different from one another. Different parts of the large FMC network may be managed by different organizations.
The key challenge of FMC NM is the production of a set of specifications whose implementations would
a) Reduce FMC operators’ CAPEX and OPEX and
b) Facilitate OSS (playing the role of IRPManager) to integrate the various NM services consumed into the so-called “end-to-end” view of the FMC network under management.
Since network resource models are designed and maintained by different SDO/organizations and the provision of the “end-to-end” view requires defined relations among network resource models, this set of specifications would include:
1. Model architecture, called Federated Network Model (FNM), identifying various network resource models and their relations among each other;
2. The governance of each network resource model and the working procedures among SDO/organizations (that are designers and maintainers of the network resource model) involved.
The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for item 1 and item 2 above.
This clause shall start on a new page.
The present document … |
28.102 | Management of Converged Networks; Stage 2 | TS | 0.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.102/28102-000.zip | FFS |
28.401 | Telecommunication management; Performance Management (PM); Performance measurements for Core Network (CN) and non-3GPP access Interworking System | TS | 0.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.401/28401-020.zip | The present document describes the measurements for CN and non-3GPP interworking system.
TS 32.401 [3] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a interworking system. Only measurement types that are specific to interworking system are defined within the present documents. Vendor specific measurement types used in interworking system are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. measurements related to WAG, PDG and so on);
- Header 2: Measurement function (e.g. FFS);
- Header 3: Measurements. |
28.601 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 0.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.601/28601-011.zip | The present document describes the Network Resource Model (NRM) Integration Reference Point (IRP) requirements for Interworking WLAN (IWLAN). According to the structure of IWLAN defined in 3GPP TS 23.234 [6], the present document is focusing on the definition of NRM IRP requirements on the 3GPP part (e.g. WAG, PDG, 3GPP AAA, etc). |
28.602 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.602/28602-030.zip | The present document is an Integration Reference Point (IRP) named "Core Network (CN) and non-3GPP access interworking system Network Resource Model IRP", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management (CM) information to one or several 'IRPManagers' (typically Network Managers) concerning interworking network resources.
According to the structure of IWLAN defined in 3GPP TS 23.234 [5], several nodes are defined in 3GPP (e.g. WAG, PDG, 3GPP AAA, etc). The present document is focusing on the definition of NRM IRP IOCs for management support.
It reuses relevant parts of the generic NRM in 3GPP TS 28.622 [6], either by direct reuse or sub-classing, and in addition to that defines I-WLAN specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP IS (3GPP TS 32.602 [7]) or the Bulk CM IRP IS (3GPP TS 32.612 [8]). However, which Interface IRP that is applicable is outside the scope of the present document.
The present document supports the Federated Network Information Model (FNIM) concept described in 3GPP TS 32.107 [16] in that the relevant Information Object Classes (IOCs) defined in the present document are directly or indirectly inherited from those specified in the Umbrella Information Model (UIM) of 3GPP TS 28.620 [17]. |
28.606 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 0.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.606/28606-010.zip | The present document is part of an Integration Reference Point (IRP) named Core Network (CN) and non-3GPP access Interworking System Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Core Network (CN) and non-3GPP access Interworking System resources. The Core Network (CN) and non-3GPP access Interworking System NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the Core Network (CN) and non-3GPP access Interworking System NRM IRP.
This Solution Set specification is related to 3GPP TS 28.602 V12. 0.X [4]. |
28.611 | Telecommunication management; Evolved Packet Core (EPC) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 0.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.611/28611-011.zip | |
28.612 | Telecommunication management; Evolved Packet Core (EPC) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.612/28612-030.zip | |
28.616 | Telecommunication management; Evolved Packet Core (EPC) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 0.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.616/28616-010.zip | |
30.007 | Guideline on WI/SI for new Operating Bands | TR | 0.2.0 | RP | https://www.3gpp.org/ftp/Specs/archive/30_series/30.007/30007-020.zip | The present document a technical report for the <Work item name> work item.
The Scope of the TR should be kept short. Details of the Work Item objective should be given in the Background section (Clause 4). |
33.823 | Security for usage of Generic Bootstrapping Architecture (GBA) with a User Equipment (UE) browser | TR | 1.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.823/33823-110.zip | This work in this Technical Report has the following scope:
- Study the potential threats for different GBA credentials use scenarios via a web browser. These new use scenarios (e.g. using HTML forms, using Javascript, using widgets) are not covered by current specifications.
The scope of this Technical Report will cover the following:
- Study, identify and specify any protection mechanism that maybe additionally required for the GBA credentials;
- Study, identify and potentially specify usage control for GBA credentials;
- Study, identify and potentially specify access control mechanism for GBA module;
- Study, identify and potentially specify the usage of web based GBA as an extension on the current protocol mechanisms used on Ua reference point (e.g. new Ua protocol identifier);
- Identify and outline how GBA can be used with HTML Forms and Javascript securely (e.g. describing GBA - web specific common practices and examples).
This Technical Report will collect the potential specification improvements, which are then at a later stage of work transferred to the appropriate Technical Specifications. The potential improvements for access control to GBA credentials and potential Ua protocol impacts will then be documented in TS 33.220 [2]. The threat analysis, common security implementation practices and examples may build a new chapter 5 in TS 33.222 [3].
Relation to GBA variants defined in other documents: Web based GBA aims at defining web enhancements for the use of HTML forms with GBA. It is a new variant for the Ua interface and does not affect the Ub interface, as opposed to the GBA variants defined in TS 33.220. Web based GBA is orthogonal to these other GBA variants and can be used with any of them. |
33.829 | Extended IP Multimedia Subsystem (IMS) media plane security features | TR | 1.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.829/33829-110.zip | The present document details relevant use cases/services for different user groups and corresponding solutions for IMS media plane security which are not covered by TS 33.328 [3]. The corresponding requirements in the Rel-9 study documented in TR 33.828 [2] will be used as a basis. The covered use cases/services are: conference calls, protection of non-RTP media, early media, communication diversion, deferred delivery, protected media recording, video on demand, AS-terminated media security, transcoder functionality and SRVCC. Example user groups are enterprises, National Security and Public Safety (NSPS) organizations, different government authorities, and general public.
Editor’s Note: The list of covered use cases/services shall be updated when the study is finalized.
Editor’s Note: It is for further study whether protection of early media is possible in IMS. |
33.868 | Study on security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements | TR | 0.17.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.868/33868-0h0.zip | The present document studies the security aspects of System Improvements for Machine Type Communication. In particular, the goals of the present document are:
- To identify and analyze the threats to the MTC system within the scope of the service requirements, functionality and use cases as specified in TS 22.368 [9].
- To identify possible security and privacy impacts induced by the system architecture improvement for machine type communications based on TR 23.887 [26] and TS 23.682 [23].
- To determine possible security requirements based on the analysis above and describe the possible solutions to meet those requirements.
Machine-type communication aspects of (x)SIMs and/or new models for the management of (x)SIM are out of scope of the present document. |
33.914 | Single Sign On (SSO) application security for common IP Multimedia Subsystem (IMS) based on SIP Digest | TR | 2.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.914/33914-200.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.416 | Mobile Relay for E-UTRA | TS | 0.0.2 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.416/36416-002.zip | The present document is the technical report for the study item on Mobile Relay for E-UTRA [1], which was approved at TSG RAN#53. The objective of the SI is to first identify the scenario(s) and requirements then identify the key properties of mobile relays and assess the benefits of mobile relays over existing solutions in fast-moving environments. |
36.809 | Radio Frequency (RF) pattern matching location method in LTE | TR | 0.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.809/36809-030.zip | The objective of this study [20] is to evaluate the use of measurements for positioning, which are currently specified for UE and eNodeB for other purposes but are not currently included in LPP and LPPa, for an RF pattern matching positioning technology in LTE.
The RFPM performance with these measurements will be compared to the RFPM performance based on the measurements currently specified for the E-CID location method.
The implementation could be an E-SMLC based eNodeB-assisted location service using existing E-UTRAN measurements which are provided to the E-SMLC via the LPPa positioning protocol and UE-assisted location service using existing UE measurements (RSRP, RSRQ and UE Rx-Tx time difference only) which are provided to the E-SMLC via LPP positioning protocol.
The present document is intended to complement already 3GPP standardized location methods and existing 3GPP location work items. |
36.827 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced carrier aggregation band 41 | TR | 11.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.827/36827-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.831 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced Carrier Aggregation (CA) in band 7 | TR | 11.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.831/36831-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.836 | Evolved Universal Terrestrial Radio Access (E-UTRA); Study on mobile relay | TR | 2.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.836/36836-210.zip | The present document covers the Study on Mobile Relay for E-UTRA . The objective is to first identify scenario(s) and requirements then identify the key properties of Mobile Relays and assess the benefits of Mobile Relays over existing solutions in fast-moving environments. |
36.841 | Evolved Universal Terrestrial Radio Access (E-UTRA); Intra-band non-contiguous Carrier Aggregation (CA) for band 25 for LTE | TR | 0.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.841/36841-010.zip | The present document is a technical report of the LTE Advanced Intra-band Non-contiguous Carrier Aggregation in Band 25 work item which was approved at TSG RAN #53 [2]. The objective of this work item is to provide specification support for intra-band non-contiguous carrier aggregation in LTE FDD Band 25.
The report provides motivation, requirements and a list of recommended changes to the specifications. |
36.888 | Study on provision of low-cost Machine-Type Communications (MTC) User Equipments (UEs) based on LTE | TR | 2.1.1 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.888/36888-211.zip | As LTE deployments evolve, operators would like to reduce the cost of overall network maintenance by minimising the number of RATs. Machine-Type Communications (MTC) is a market that is likely to continue expanding in the future. Many MTC UE's are targeting low-end (low average revenue per user, low data rate) applications that can be handled adequately by GSM/GPRS. Owing to the low-cost of these devices and good coverage of GSM/GPRS, there is very little motivation for MTC UE suppliers to use modules supporting the LTE radio interface. As more and more MTC UE's are deployed in the field, this naturally increases the reliance on GSM/GPRS networks. This will cost operators not only in terms of maintaining multiple RATs, but it will also prevent operators from reaping the maximum benefit out of their spectrum (given the non-optimal spectrum efficiency of GSM/GPRS). Given the likely high number of MTC UE's, the overall resource they will need for service provision may be correspondingly significant, and inefficiently assigned.
Therefore, it is necessary to find a solution to ensure that there is a clear business benefit to MTC UE vendors and operators for migrating low-end MTC UE's from GSM/GPRS to LTE networks. |
37.808 | Passive Intermodulation (PIM) handling for Base Stations (BS) | TR | 0.6.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.808/37808-060.zip | The present document is the technical report for the study item on Passive InterModulation (PIM) handling for Base Stations, which was approved at TSG RAN#55 [7]. The objective of the WI is to investigate the PIM issue from an overall perspective and to conclude on a way forward for the PIM problem and propose corresponding requirements for the BS specifications. |
37.977 | Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Verification of radiated multi-antenna reception performance of User Equipment (UE) | TR | 0.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.977/37977-050.zip | |
43.801 | Solutions for Voice services over Adaptive Multi-user channels on One Slot (VAMOS) enhancements | TR | 0.5.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.801/43801-050.zip | The present document contains the results from the 3GPP study item on VAMOS Enhancements. This includes study of the following aspects:
- Objectives of the study.
- Common assumptions for the evaluation of candidate techniques.
- Candidate techniques including those that utilize network synchronization, and further those that use inter-cell interference coordination/mitigation and inter-cell channel state sharing in and between BSS. A candidate technique will support frequency hopping.
- Evaluations of candidate techniques based on the objectives.
VAMOS enhancements will also investigate a new logical interface between BSSs in A/Gb mode which applies to control plane only and can be utilised by VAMOS enhancement solutions, since no logical interface between BSSs in A/Gb mode exists in current specifications. |
43.802 | GERAN study on mobile data applications | TR | 0.4.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.802/43802-040.zip | The present document contains the results from the feasibility study on efficient support of mobile data applications for human communications in GERAN.
The following aspects shall be covered in the study:
- Analysis on relevant traffic profiles from GERAN perspective for the mobile data applications of human communications
- Analysis on the impacts on GERAN network based on the identified traffic profiles
- GERAN enhancements to alleviate these impacts with regards to: Radio resource utilization; signalling procedures; RR states and transition between them and Battery lifetime
- Common assumptions on simulations and evaluations for candidate solutions |
43.868 | GERAN improvements for Machine-Type Communications (MTC) | TR | 2.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.868/43868-200.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 |
23.812 | Feasibility study on IP Multimedia Subsystem (IMS) evolution | TR | 1.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.812/23812-120.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.813 | Study on policy solutions and enhancements | TR | 0.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.813/23813-060.zip | The objective is to study an evolved policy solution through enhancement of 3GPP policy framework. One of the aims of the study is to ensure a policy architecture that provides an extensible framework for easy reuse with new IP based services by identifying areas where improvement of specifications are feasible. The study item will look into solutions for the examples in the section above.
Existing components for consideration in the Policy Study are functions and interfaces to/from
- PCRF, PCEF and BBERF;
- SPR, HSS;
- ANDSF;
- IMS policy decision making entities.
The study aims to provide a more comprehensive way (e.g. going beyond existing 3GPP PCC framework) to handle operator policies for all IP / service flows (IMS and non-IMS) in a coordinated manner and under varying network conditions while keeping in view aspects such as:
- user preferences;
- user subscriptions;
- service requirements;
- terminal capabilities (including converged terminals);
- network capabilities (3GPP and those non 3GPP accesses inter- working with 3GPP);
- Session transfer and terminating policies;
- Security policy control, e.g. firewalling and gating.
Roaming scenarios are considered as part of this study. Compatibility with existing system architecture elements are protected and backward compatibility is expected. All types of policies i.e. static/pre-provisioned, dynamic, network based, UE based are considered in the study.
When a key issue is resolved sufficiently to be incorporated into the specification in an independent manner, the study work may move forward for a decision for normative specification work on such issue(s) using a new work item or a TEI. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.