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 |
|---|---|---|---|---|---|---|
29.060 | General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | TS | 12.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.060/29060-c90.zip | |
29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | TS | 12.12.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.061/29061-cc0.zip | |
28.703 | Telecommunication management; Core Network (CN) 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.703/28703-c10.zip | |
29.079 | Optimal media routeing within the IP Multimedia Subsystem (IMS); Stage 3 | TS | 12.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.079/29079-c30.zip | |
29.108 | Application of the Radio Access Network Application Part (RANAP) on the E-interface | TS | 12.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.108/29108-c00.zip | |
29.109 | Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3 | TS | 12.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.109/29109-c20.zip | |
29.118 | Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification | TS | 12.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.118/29118-c70.zip | CS Fallback in the Evolved Packet System (EPS) enables the provisioning of CS-domain services (e.g. voice call, Location Services (LCS) or supplementary services) by reuse of CS infrastructure when the UE is served by E-UTRAN. Additionally, SMS delivery via the CS core network is realized without CS fallback.
The present document specifies the procedures and the SGs Application Part (SGsAP) messages used on the SGs interface between the Mobility Management Entity (MME) in the EPS and the Visitor Location Register (VLR), to allow location management coordination and to relay certain messages related to GSM circuit switched services over the EPS system.
The present document also specifies the use of Stream Control Transmission Protocol (SCTP) for the transport of SGsAP messages.
The present document is applicable to the MME in the EPS and to the VLR. The functional split between the MME and the VLR is defined in 3GPP TS 23.272 [7]. |
29.119 | GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.119/29119-c00.zip | |
29.120 | Mobile Application Part (MAP) specification for Gateway Location Register (GLR) | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.120/29120-c00.zip | |
29.139 | 3GPP system - fixed broadband access network interworking; Home (e)Node B - security gateway interface | TS | 12.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.139/29139-c10.zip | |
29.162 | Interworking between the IM CN subsystem and IP networks | TS | 12.7.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.162/29162-c70.zip | The IM CN subsystem interworks with the external IP networks through the Mb reference point.
This document details the interworking between the IM CN subsystem and external IP networks for IM service support. It addresses the issues of control plane interworking and, user plane interworking for specific interworking use cases. Clause 10 describes the IMS-Ix interface requirements in the form of Use Cases which require H.248 protocol procedures. Subclause 10.4 then details the additional Information Elements required to perform the specific procedures.
The IP version Interworking, between IP version 4 (IETF RFC 791 [9] ) and IP version 6 (IETF RFC 2460 [10] ) detailed in terms of the processes and protocol mappings required in order to support both IMS originated and terminated calls. |
29.163 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks | TS | 12.16.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.163/29163-cg0.zip | The present document specifies the principles of interworking between the 3GPP IM CN subsystem and BICC/ISUP based legacy CS networks, in order to support IM basic voice, data and multimedia calls.
The present document addresses the areas of control and user plane interworking between the IM CN subsystem and CS networks through the network functions, which include the MGCF and IM-MGW. For the specification of control plane interworking, areas such as the interworking between SIP and BICC or ISUP are detailed in terms of the processes and protocol mappings required for the support of both IM originated and terminated voice and multimedia calls.
Other areas addressed encompass the transport protocol and signalling issues for negotiation and mapping of bearer capabilities and QoS information.
The present document specifies the interworking between 3GPP profile of SIP (as detailed according to 3GPP TS 24.229 [9]) and BICC or ISUP, as specified in ITU-T Recommendations Q.1902.1 to Q.1902.6 [30] and ITU-T Q761 to Q764 [4] respectively.
The present document also specifies the interworking between circuit switched multimedia telephony service, as described in 3GPP TS 26.110 [78] 3GPP TS 26.111 [79], and ITU-T Recommendation H.324 [81] and packet switched multimedia services, as described in 3GPP TS 26.114 [104], in particular and the interworking between the 3GPP profile of SIP and the inband control protocols for multimedia communication as specified in ITU-T Recommendations H.245 [82] and H.324 Annex K [81].
The present document addresses two interworking scenarios with respect to the properties of the CS network:
- The CS network does not use any 3GPP specific additions.
- The CS network uses 3GPP specific additions. |
29.164 | Interworking between the 3GPP CS domain with BICC or ISUP as signalling protocol and external SIP-I networks | TS | 12.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.164/29164-c00.zip | The present document defines interworking procedures between a 3GPP CS domain (see 3GPP TS 23.205 [2]) which applies either BICC or ISUP as signalling protocol, and external networks that use SIP-I (see ITU-T Q.1912.5 [20], Profile C) as signalling protocol. The document also describes the related interworking architecture. The control plane interworking is performed by an interworking unit at the interconnection between the 3GPP CS domain and an external SIP-I network. The user plane interworking is performed by an MGW. The present document defines stage 2 procedures for the control of the MGW.
The present specification reuses existing interworking procedures of 3GPP TS 29.163 [4] and ITU-T Q.1912.5 [20], Profile C, as far as possible. |
29.171 | Location Services (LCS); LCS Application Protocol (LCS-AP) between the Mobile Management Entity (MME) and Evolved Serving Mobile Location Centre (E-SMLC); SLs interface | TS | 12.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.171/29171-c30.zip | |
29.172 | Location Services (LCS); Evolved Packet Core (EPC) LCS Protocol (ELP) between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity (MME); SLg interface | TS | 12.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.172/29172-c60.zip | |
29.173 | Location Services (LCS); Diameter-based SLh interface for Control Plane LCS | TS | 12.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.173/29173-c30.zip | |
29.201 | Representational State Transfer (REST) reference point between Application Function (AF) and Protocol Converter (PC) | TS | 12.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.201/29201-c40.zip | |
29.202 | Signalling System No. 7 (SS7) signalling transport in core network; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.202/29202-c00.zip | |
29.204 | Signalling System No. 7 (SS7) security gateway; Architecture, functional description and protocol details | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.204/29204-c00.zip | |
29.205 | Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.205/29205-c00.zip | |
29.212 | Policy and Charging Control (PCC); Reference points | TS | 12.14.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.212/29212-ce0.zip | |
29.013 | Signalling interworking between ISDN supplementary services; Application Service Element (ASE) and Mobile Application Part (MAP) protocols | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.013/29013-c00.zip | |
29.168 | Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3 | TS | 12.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.168/29168-ca0.zip | |
29.219 | Policy and charging control: Spending limit reporting over Sy reference point | TS | 12.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.219/29219-c40.zip | |
29.228 | IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents | TS | 12.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.228/29228-ca0.zip | |
29.229 | Cx and Dx interfaces based on the Diameter protocol; Protocol details | TS | 12.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.229/29229-c90.zip | |
29.230 | Diameter applications; 3GPP specific codes and identifiers | TS | 12.13.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.230/29230-cd0.zip | |
29.231 | Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.231/29231-c00.zip | The present document describes the protocols to be used when SIP-I is optionally used as call control protocol in a 3GPP CS core network on Nc interface, see 3GPP TS 23.231 [1]. The SIP-I protocol operates between (G)MSC servers. The SIP-I architecture consists of a number of protocols. The following types of protocols are described: call control protocol, resource control protocols and user plane protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.231 [1] and TS 23.153 [2].
Interworking of SIP-I on Nc to external networks is described by TS 29.235 [3].
The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 8 and later. |
29.232 | Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 | TS | 12.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.232/29232-c10.zip | |
29.235 | Interworking between SIP-I based circuit-switched core network and other networks | TS | 12.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.235/29235-c20.zip | |
29.238 | Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3 | TS | 12.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.238/29238-c60.zip | |
29.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase X; CAMEL Application Part (CAP) specification | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.078/29078-c00.zip | The present document specifies the CAMEL Application Part (CAP) supporting the fourth phase of the network feature Customized Applications for Mobile network Enhanced Logic. CAP is based on a sub-set of the ETSI Core INAP CS-2 as specified by ETSI EN 301 140‑1 [26]. Descriptions and definitions provided by ETSI EN 301 140‑1 [26] are directly referenced by this standard in the case no additions or clarifications are needed for the use in the CAP. |
29.213 | Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping | TS | 12.14.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.213/29213-ce0.zip | |
29.273 | Evolved Packet System (EPS); 3GPP EPS AAA interfaces | TS | 12.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.273/29273-c90.zip | The present document defines the stage-3 protocol description for several reference points for the non-3GPP access in EPS:
- The SWa reference point between an un-trusted non-3GPP IP access and the 3GPP AAA Server/Proxy.
- The STa reference point between a trusted non-3GPP IP access and the 3GPP AAA Server/Proxy.
- The SWd reference point between the 3GPP AAA Proxy and 3GPP AAA Server.
- The SWx reference point between the 3GPP AAA Server and the HSS.
- The S6b reference point between the 3GPP AAA Server/Proxy and the PDN GW.
- The SWm reference point between the 3GPP AAA Server/Proxy and the ePDG.
- The reference point between the 3GPP AAA Server/Proxy and the EIR.
The present document also defines the stage 3 protocol description for the following reference points defined for Non-seamless WLAN offload in 5GS:
- the SWa' reference point between a non-3GPP WLAN access, possibly via a 3GPP AAA Proxy, and the NSWO NF; and
- the SWd' reference point between the 3GPP AAA Proxy, possibly via an intermediate 3GPP AAA Proxy, and the NSWO NF. |
29.214 | Policy and charging control over Rx reference point | TS | 12.12.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.214/29214-cc0.zip | |
29.276 | 3GPP Evolved Packet System (EPS); Optimized handover procedures and protocols between E-UTRAN access and cdma2000 HRPD Access; Stage 3 | TS | 12.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.276/29276-c30.zip | |
29.277 | Optimised handover procedures and protocol between EUTRAN access and non-3GPP accesses (S102); Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.277/29277-c00.zip | |
29.278 | Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part (CAP) specification for IP Multimedia Subsystems (IMS) | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.278/29278-c00.zip | |
29.279 | Mobile IPv4 (MIPv4) based mobility protocols; Stage 3 | TS | 12.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.279/29279-c10.zip | |
29.280 | Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC | TS | 12.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.280/29280-c30.zip | |
29.281 | General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U) | TS | 12.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.281/29281-c10.zip | |
29.282 | Mobile IPv6 vendor specific option format and usage within 3GPP | TS | 12.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.282/29282-c20.zip | |
29.272 | Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol | TS | 12.11.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.272/29272-cb0.zip | |
29.240 | 3GPP Generic User Profile (GUP); Stage 3; Network | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.240/29240-c00.zip | |
29.215 | Policy and Charging Control (PCC) over S9 reference point; Stage 3 | TS | 12.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.215/29215-c90.zip | |
29.305 | InterWorking Function (IWF) between MAP based and Diameter based interfaces | TS | 12.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.305/29305-c30.zip | |
29.275 | Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3 | TS | 12.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.275/29275-c70.zip | |
29.328 | IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents | TS | 12.15.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.328/29328-cf0.zip | |
29.303 | Domain Name System Procedures; Stage 3 | TS | 12.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.303/29303-c40.zip | |
29.332 | Media Gateway Control Function (MGCF) - IM Media Gateway; Mn interface | TS | 12.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.332/29332-c10.zip | |
29.311 | Service Level Interworking (SLI) for messaging services | TS | 12.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.311/29311-c10.zip | |
29.335 | User Data Convergence (UDC); User data repository access protocol over the Ud interface; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.335/29335-c00.zip | |
29.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface; Stage 3 | TS | 12.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.333/29333-ca0.zip | |
29.337 | Diameter-based T4 Interface for communications with packet data networks and applications | TS | 12.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.337/29337-c70.zip | |
29.329 | Sh interface based on the Diameter protocol; Protocol details | TS | 12.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.329/29329-c60.zip | |
29.343 | Proximity-services (ProSe) function to ProSe application server aspects (PC2); Stage 3 | TS | 12.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.343/29343-c30.zip | |
29.334 | IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3 | TS | 12.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.334/29334-ca0.zip | |
29.336 | Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications | TS | 12.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.336/29336-c60.zip | The present document describes the Diameter-based interfaces between the HSS and other network elements involved in the architecture for interworking with packet data networks and applications, such as Machine-Type Communications (MTC).
In particular, this document specifies the S6m interface between the Home Subscriber Server (HSS) and the MTC Interworking Function (MTC-IWF), the S6n interface between the HSS and the MTC-AAA and the S6t interface between the HSS and the Service Capability Exposure Function (SCEF). The procedures over those interfaces are defined in 3GPP TS 23.682 [2]. |
29.364 | IP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperability | TS | 12.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.364/29364-c30.zip | This specification standardizes
- the structure and the coding of the service data that are transported over the Sh interface between an Application Server supporting Multimedia Telephony supplementary services as defined in 3GPPP TS 22.173 [1] and the HSS. Two optional formats are specified. One is based on a binary coding of the service data and supports the subset of MMTEL services corresponding to PSTN/ISDN and CS supplementary services. The other uses an XML format and supports the full set of MMTEL Services.
- the structure and the coding of a set of generic IMS user group data over the Sh interface.
- the structure and the coding of the service data (ODB Information for IMS Oriented Services) that are transported over the Sh interface between an Application Server supporting services that are subject to IMS-ODB as defined in 3GPP TS 22.041[25] and the HSS.
- the structure and the coding of the IMS CAMEL subscription data transported using Sh interface. |
29.368 | Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS) | TS | 12.6.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.368/29368-c60.zip | |
29.414 | Core network Nb data transport and transport signalling | TS | 12.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.414/29414-c00.zip | |
29.415 | Core network Nb interface user plane protocols | TS | 12.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.415/29415-c00.zip | |
29.468 | Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3 | TS | 12.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.468/29468-c50.zip | |
29.338 | Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs) | TS | 12.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.338/29338-c60.zip | |
29.658 | SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification | TS | 12.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.658/29658-c00.zip | |
29.345 | Inter-Proximity-services (Prose) function signalling aspects; Stage 3 | TS | 12.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.345/29345-c40.zip | |
29.806 | Study on IP Multimedia Subsystem (IMS) Proxy Call Session Control Function (P-CSCF) restoration procedures | TR | 12.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.806/29806-c10.zip | The present document analyses existing P-CSCF restoration mechanism limitations and drawbacks, as defined by 3GPP TS 23.380 [2] and 3GPP TS 24.229 [3], and proposes alternative solutions that could minimize such limitations.
Expected output from this document is a proposal of an enhanced P-CSCF restoration mechanism. |
29.807 | Study on General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTP-C) overload control mechanisms | TR | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.807/29807-c00.zip | The present document investigates various aspects related to the support of the GTP-C signalling based load / overload control solution as specified in 3GPP TS 23.401 [2] and TS 23.060 [3], as also concluded in TR 23.843 [4], with the main focus on:
• Definition of "Load Control" and "Overload Control" related information with enough precision to guarantee a common multi-vendor interpretation of this information allowing inter-operability between various GTP-C nodes;
• Mechanisms to address various "Notes", which are targeted to the stage 3, specified in clause 8.2.5, clause 8.2.6 & clause 10.2 of the 3GPP TR 23.843 v1.0.0 [4].
This technical report addresses the following aspects related to the "GTP-C signalling based load and overload control" feature in detail:
- Investigation and study of the following aspects related to the "Load Control Information" to fulfill the normative requirements or to produce recommendations.
- Definition of the "Load Control Information" by evaluating various parameters which can be exchanged under this information.
- Inclusion of "Load Control Information" in GTP-C messages.
- Potential enhancements to the existing node selection algorithm to take information received from "Load Control Information" into account.
- Investigation and study of the following aspects related to the "Overload Control Information" to fulfill the normative requirements or to produce recommendations.
- Definition of the "Overload Control Information" by evaluating various parameters which can be exchanged under this information.
- Inclusion of the "Overload Control Information" in GTP-C messages.
- Message throttling algorithms and message prioritization when congestion mitigation is applied.
- Propagation of the MME/SGSN identity to the PGW to ensure that the overload mitigation is always applied to the currently serving MME/SGSN.
- Potential interactions with the existing overload control mechanisms when the overload factor is received within the "Overload Control Information".
- Investigation and study of the following the other deployment related aspects to fulfill the normative requirements or to produce recommendations.
- Applicability of this feature to 3GPP and non-3GPP based GTP-C interfaces.
- Methods to discover the support of this feature by the peer node in the network.
- Supporting the feature across the PLMN boundary.
- Issues within the network with partial support of this feature.
- Overload mitigation policies when this feature support is not enabled in the network. |
29.809 | Study on Diameter overload control mechanisms | TR | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.809/29809-c00.zip | The present document investigates possible enhancements of the Diameter base protocol (IETF RFC 6733 [2] and existing Diameter applications to support overload control mechanisms in 3GPP core networks.
This work is based on the results of the feasibility study on Core Network Overload available in 3GPP TR 23.843 [3] and the related work done in the IETF Diameter Maintenance and Extensions (DiME) working group.
This study will cover:
- Identification of the set of requirements for an improved overload control mechanism over Diameter based signaling interfaces used in 3GPP core networks.
- Identification, evaluation and selection of candidate solutions for overload control mechanisms, including:
- Mechanisms to detect overload situations e.g. notification of Diameter end-point signaling load;
- Mechanisms to exchange overload control policies between Diameter end-points;
- Details on the expected behaviour of 3GPP core network nodes supporting the defined overload control mechanism (Diameter end-points and Diameter agent);
- Evaluation of the impacts of the proposed solution(s) on existing Diameter-based Technical Specifications and Diameter based signalling networks (internal operator networks, inter-operator network (e.g. IPX).
- Recommendations on the solutions to select depending of the applicability context (interfaces, application, network, etc.)
The results of this study will contribute to the work done within the IETF DiME working group on Diameter overload control, through official liaison statement from 3GPP or company-driven individual contributions, which includes:
- Provide feedback from 3GPP on the requirements for Diameter overload control mechanisms defined in IETF Draft draft-ietf-dime-overload-reqs-06 [4]);
- Contribute to the specification of the IETF standard mechanism for overload control over Diameter.
The results of this study will be used to identify the changes required in the 3GPP specifications to support overload control mechanisms over Diameter-based 3GPP interfaces and applications. |
29.817 | Study on eXtensible Markup Language (XML) based access of the Application Function (AF) to the Policy and Charging Rules Function (PCRF) | TR | 12.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.817/29817-c10.zip | The Technical Report describes solutions for an XML based protocol (e.g. SOAP, Restful HTTP, etc.) between the AF and the PCRF for the case of non IMS applications. The scope of this work is to provide an XML based equivalent to the Diameter based signalling that is presently specified in 3GPP TS 29.214 [5].
This study covers the following alternatives:
- XML based protocol between AF and PCRF;
- Adding a new protocol converter (as a stand-alone entity) between PCRF and AF
Investigate a suitable transport protocol for XML, charging issues in case of 3rd party SPs, security issues.
Roaming in both home routed and local break out and signalling routing aspects (e.g. DRA handling and others aspects) has also been included.
Necessary changes to 3GPP specifications are identified. |
29.828 | Study on extended IP Multimedia Subsystem (IMS) media plane security features and Transmission Control Protocol (TCP) related Network Address Translation (NAT) traversal support; IMS H.248 profiles aspects | TR | 12.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.828/29828-c10.zip | The present document investigates the IMS H.248 profiles requirements and procedures to support the stage 2 requirements specified in 3GPP TS 33.328 [2] for Extended IMS media plane security features.
This includes in particular the following aspects:
1. Provide end-to access edge protection of session based messaging (MSRP) traffic using TLS and certificates fingerprints exchanged over SDP;
2. Provide end-to-end protection of session based messaging (MSRP) traffic using TLS;
3. Provide end-to access edge protection of BFCP based traffic, using TLS and certificates fingerprints exchanged over SDP;
4. Provide optional support of TLS protection of BFCP and MSRP based traffic at the Conference Server.
5. Analyse requirements and procedures for end-to-end TCP bearer connection control and related NAT traversal support.
NOTE: this aspect is not specific to media security and may result in normative work via another work item.
6. Provide support of TCP-based IP transport connections for TLS security sessions, which includes possible NAT traversal support during the TCP connection establishment phase, possible correlations between the establishment (and release) events of TCP connections with TLS session establishment (and release).
7. Provide end-to access edge protection of T.38 fax using DTLS.
This study will cover:
- Identification of the key issues and the main design considerations that should drive the definition of stage 2 requirements and procedures for the Iq, Ix and Mp profiles;
- Identification of the requirements and procedures for the Iq, Ix and Mp profiles for support of end-to-access edge and end-to-end media security for session-based messaging (MSRP [6]) and conferencing (BFCP [16]);
- Identification of the requirements and procedures for the Iq profile for support of end-to-access edge media security for T.38 fax over UDPTL/UDP transport;
- Identification of the ITU-T H.248 extensions necessary to fulfil the 3GPP requirements and identification of potential missing gaps that should be taken into account by ITU-T Q3/16;
- Conclusions and Recommendations for the normative work.
The results of this study will be used to identify the changes required in the 3GPP specifications to support Extended IMS media plane security. |
29.854 | Study on shared data update for multiple subscribers | TR | 12.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.854/29854-c20.zip | The present document analyses the use cases for the need of update of subscription data shared by multiple subscribers, the existing mechanisms in 3GPP networks which is or may be used for shared data update, possible solutions and impact on the existing interfaces and relevant elements.
The recommendation of the document is used to decide whether it is required to standardize any solution, and which is the final preferred solution if further standardization is needed. |
29.909 | Diameter-based protocols usage and recommendations in 3GPP | TR | 12.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.909/29909-c00.zip | |
29.935 | Study on User Data Convergence (UDC) data model | TR | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.935/29935-c00.zip | |
29.949 | Study on technical aspects on roaming end-to-end scenarios with Voice over LTE (VoLTE) IP Multimedia Subsystem (IMS) and other networks | TR | 12.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.949/29949-c20.zip | |
29.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-c00.zip | |
31.101 | UICC-terminal interface; Physical and logical characteristics | TS | 12.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-c20.zip | |
31.103 | Characteristics of the IP Multimedia Services Identity Module (ISIM) application | TS | 12.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.103/31103-c20.zip | |
31.104 | Characteristics of the Hosting Party Subscription Identity Module (HPSIM) application | TS | 12.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.104/31104-c10.zip | |
31.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 12.12.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-cc0.zip | |
31.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications | TS | 12.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-c20.zip | |
31.116 | Remote APDU Structure for (U)SIM Toolkit applications | TS | 12.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-c10.zip | |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 12.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-c00.zip | |
29.292 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem (IMS) and MSC Server for IMS Centralized Services (ICS) | TS | 12.7.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.292/29292-c70.zip | |
31.130 | (U)SIM Application Programming Interface (API); (U)SIM API for Java™ Card | TS | 12.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.130/31130-c00.zip | |
31.131 | C-language binding to (U)SIM API | TS | 12.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-c00.zip | |
31.133 | IP Multimedia Services Identity Module (ISIM) Application Programming Interface (API); ISIM API for Java Card™ | TS | 12.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.133/31133-c00.zip | |
31.213 | Test specification for (U)SIM; Application Programming Interface (API) for Java Card™ | TS | 12.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.213/31213-c00.zip | |
31.220 | Characteristics of the Contact Manager for 3GPP UICC applications | TS | 12.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.220/31220-c00.zip | |
31.221 | Contact Manager Application Programming Interface (API); Contact Manager API for Java Card | TS | 12.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.221/31221-c00.zip | |
31.829 | Conformance requirements for IP Multimedia Services Identity Module (ISIM) application test specification | TR | 2.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.829/31829-200.zip | The present document objective is to develop a technical report listing the conformance requirements extracted from TS 31.103. This technical report will then be a basis for a gap analysis of test coverage and the subsequent development of test cases to verify the conformance of Terminals with features for the ISIM application.
The conformance requirements should allow:
• Ensuring that content of the ISIM when available is read and used by the ME
• Reusing of existing test specifications in 3GPP
• Providing recommendations when necessary to fulfil the test purpose |
29.344 | Proximity-services (ProSe) function to Home Subscriber Server (HSS) aspects; Stage 3 | TS | 12.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.344/29344-c40.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 12.6.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-c60.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 12.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-c00.zip | |
32.101 | Telecommunication management; Principles and high level requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-c00.zip | |
32.107 | Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) | TS | 12.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.107/32107-c10.zip | |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 12.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-c20.zip | |
32.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 12.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-c30.zip | |
32.111-6 | Telecommunication management; Fault Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 12.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-6/32111-6-c10.zip | |
32.121 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.121/32121-c00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.