id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
28.828
|
Study on charging aspects for enhanced support of non-public networks
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.828/28828-i00.zip
|
The present document studies the charging aspects for enhanced support of non-public networks on the TS 23.501 [2], TS 23.502 [3], TS 23.503 [4], TS 23.228 [5] and TS 23.167 [6] incorporating conclusions from TR 23.734 [7] and TR 23.700-07 [8].
The following is studied:
- Charging scenarios and potential charging requirements for Non-Public Networks (i.e. Stand-alone Non-Public Network (SNPN) or Public Network Integrated NPN (PNI-NPN)).
- Possible charging solutions for Non-Public Networks with potential impact on charging architecture, charging functions and charging procedures.
- End user charging and Inter-Provider charging by considering the different business roles.
|
28.829
|
Study on network and service operations for energy utilities
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.829/28829-i01.zip
|
The present document considers service requirements introduced by the SEI work item related to telecom management [2] and [3]. This feasibility study identifies use cases and requirements for exposing capabilities of the 3GPP management system to external energy utility service providers. The study further considers how management capabilities or what information can be provided to MNOs by the external energy utility service providers. The study will consider both energy utility use cases and requirements. The study of FS_NSCE [4] can be considered for the technical investigation.
|
28.830
|
Study on Fault Supervision Evolution
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.830/28830-i10.zip
|
The present document investigates potential use cases, requirements and solutions for the fault supervision evolution, its relation with performance management and fault supervision, relation and interaction with MDAS and COSLA, and potential enhancements for MDA assisted fault management. The present document provides conclusions and recommendations on the normative work.
|
28.831
|
Study on basic Service-Based Management Architecture (SBMA) enabler enhancements
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.831/28831-i00.zip
|
The present document …
|
28.832
|
Study on management aspects of Ultra-Reliable and Low Latency Communications (URLLC)
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.832/28832-i01.zip
|
The present document investigates the potential requirements related to management of the URLLC features defined in RAN side. It documents key issues related to configuration management of URLLC features and to the performance measurements for URLLC service. It provides potential solutions and recommendations for the normative work.
|
28.833
|
Study on management aspects of 5GLAN
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.833/28833-i01.zip
|
The present document studies the potential use cases, requirements, and enhancements for the management (e.g. performance measurement and related new KPIs regarding VN group communication) to support 5G-LAN capabilities defined by TS 23.501 [2]. The present document provides conclusions and recommendations on standardization phase.
|
28.834
|
Study on management of cloud-native Virtualized Network Functions (VNF)
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.834/28834-i01.zip
|
The present document studies potential use cases, requirements and solutions for the management of cloud-native virtualized network function and the impacts on the 3GPP management system. The present document provides conclusions and recommendations on the next steps in the standardization.
|
28.835
|
Study on management aspects of 5G Multiple Operator Core Network (MOCN) network sharing phase 2
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.835/28835-i01.zip
|
The present document studies on potential requirements, impact on interaction between MOP and POP/NEP, and management architecture and more potential performance measurements of 5G MOCN network sharing.
|
28.836
|
Study on intent-driven management for network slicing
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.836/28836-i00.zip
|
The present document specifies potential use cases, requirements, and solutions for intent driven management for network slicing. The document provides conclusions and recommendations on the next steps in the standardization.
|
28.837
|
Study on management of trace/ Minimization of Drive Tests (MDT) phase 2
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.837/28837-i00.zip
|
The present document studies potential enhancements for the management of Trace/MDT based on the existing 5G data collection job "TraceJob" specified in TS 28.621 (stage 1) [2], TS 28.622 (stage 2) [3], TS 28.623 (stage 3) [4] and the Trace/MDT management framework specified in TS 32.421 (stage 1) [5], TS 32.422 (stage 2) [6] and TS 32.423 (stage 3) [7]. The document provides conclusions and recommendations on the next steps in the standardization.
|
28.838
|
Study on measurement data collection to support RAN intelligence
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.838/28838-i00.zip
|
The present document contains the concept, use cases, requirements, and potential solutions for collecting the measurement data to support AI/ML enabled RAN with the AI/ML functions residing in OAM.
|
28.839
|
Study on charging aspects for time sensitive networking
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.839/28839-i10.zip
|
The present document studies the charging aspects for the support of Time Sensitive Networking based on requirements from TS 22.261 [2] and TS 22.104 [7] of 5G system and vertical domains, the architecture, functional and protocol to enable Time Sensitive Communication and Time Synchronization, described in TS 23.501 [3], TS 23.502 [4], TS 23.503 [5], TR 23.734 [6] and TS 24.519 [8].
The following are studied:
- possible charging scenarios and requirements for 5G System integration as a bridge in TSN network;
- possible charging scenarios and requirements for the Time Sensitive Communications and Time Synchronization service;
- possible new charging aspects for the following key items:
- QoS requirements for TSN (e.g. support for TSC QoS Flows, QoS mapping from TSN QoS information to 5GS QoS profile);
- Edge computing scenario support in TSN Transport (e.g. DS-TT and NW-TT);
- charging enhancement (e.g. new triggers) due to policy control for TSN traffic which may impact the charging;
- potential charging solutions for the above charging scenarios and requirements and taking in account TSN application requirements (e.g. instance survival time).
|
28.840
|
Study on CHF segmentation
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.840/28840-i10.zip
|
The present document studies the CHF discovery and selection in order to support the discovery of a CHF by the NF consumers like SMF, AMF, SMSF and PCF based on information about network segments that the CHF belongs to.
The following are studied:
- possible charging scenarios and requirements which makes use of CHF Segmentation.
- potential charging solutions which make use of CHF Segmentation.
|
28.841
|
Study on management aspects of Internet of Things (IoT) Non-Terrestrial Networks (NTN) enhancements
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.841/28841-i01.zip
|
The present document studies on management aspects of IoT NTN enhancements. It investigates specific IoT NTN related parameters which should be considered by O&M, investigates NRM enhancement, performance measurement and related new KPIs of IoT NTN. It studies the key issues associated with service and network management of IoT NTN enhancements (whether as NG-RAN or E-UTRAN) and potential solutions, and provides recommendations for the further normative work.
|
28.842
|
Study on data management phase 2
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.842/28842-i10.zip
|
The present document studies potential enhancements related to management of management data, specifically enhancing mechanisms for discovery and reporting of management data, retrieval of stored management data, and managing external management data.
|
28.843
|
Study on structure of charging for verticals
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.843/28843-i10.zip
|
The present document studies the charging aspects to better support vertical scenarios, which is different with the existing customer charging baseline, specified in TS 32.240 [2], and makes the evolution of charging specifications clearer, which focuses on studying the charging principles and references of verticals charging, and aims to provides an guideline for other charging management TSs that specify the verticals charging.
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [1].
|
28.844
|
Study on charging aspects of satellite in the 5G System (5GS)
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.844/28844-i00.zip
|
The present document studies on charging aspects of satellite in 5GS based on the TS 23.501 [2] and TS 23.502 [3]:
This study item is to investigate the following aspects of the satellite access:
- Possible business scenarios;
- Possible charging scenarios and potential charging requirements;
- Identify the potential charging solutions.
This study item is to investigate the following aspects of the satellite backhaul:
- Possible business scenarios;
- Possible charging scenarios and potential charging requirements, e.g. related to PCC/QoS control enhancement;
- Identify the potential charging solutions.
|
28.845
|
Study on charging aspects of ranging based services and sidelink positioning
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.845/28845-i00.zip
|
The present document studies the charging aspects for Ranging based services and Sidelink Positioning
The following are in the scope:
• Identify the business roles of the Ranging based services and Sidelink Positioning;
• Identify the potential charging scenarios and requirements of the Ranging based services and Sidelink Positioning;
• Identify the potential charging solutions for the Ranging based services and Sidelink Positioning.
|
28.863
|
Study on Key Quality Indicators (KQIs) for 5G service experience
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.863/28863-i00.zip
|
The present document investigates the definition and scenarios for KQI. The KQIs and the evaluation of the KQIs for each of the identified scenarios will be investigated. It also provides the analysis for the relation of KQI with the SLS requirements.
|
28.864
|
Study on Enhancement of the management aspects related to NetWork Data Analytics Functions (NWDAF)
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.864/28864-i01.zip
|
The present document studies the management enhancement for NWDAF (Network Data Analytics Function).
In the present document, with regarding to the analytic, data management and trained ML model provisioning services provided by the NWDAF, also considering different NWDAF deployment scenarios, some fundamental key issues related the management enhancement for NWDAF are discussed. And the corresponding potential solutions are provided and evaluated.
The present document also provides recommendations for the normative specifications work.
|
28.865
|
Study on Deterministic Communication Service Assurance (DCSA)
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.865/28865-i10.zip
|
The present document studies potential key issues and solutions for provisioning and assurance of deterministic communication services, e.g. management of related network functions, potential new service requirements and new performance measurements, etc. The present document provides conclusions and recommendations on the normative work.
|
28.903
|
Study on alignment with ETSI MEC for edge computing management
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.903/28903-i01.zip
|
The present document studies the solutions to support alignment with ETSI MEC from the management perspective for edge computing.
It also identifies potential issues and solutions to support GSMA OPG [2] requirement in coordination with ETSI MEC [3].
|
28.907
|
Study on enhancement of management of non-public networks
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.907/28907-i01.zip
|
TS 28.557 [2] introduces management support for non-public networks based on stage 1 service requirements in TS 22.261 [3]. The present document is studies further enhancements to management of non-public networks including the following aspects:
- Study enhanced management of SNPN and PNI-NPN. For example, study new requirements and potential solutions of management capability exposure for SNPN and PNI-NPN, and how the mobile network operator and vertical customer cooperate to realize management and orchestration of network in MNO-Vertical Managed Mode in TS 28.557 [2].
- Study management of vertical as an authorized NPN service customer, e.g. the management of authorized capability of utilizing management services and management data.
- Study requirements and potential solutions to support end to end network management (including RAN domain and CN domain) in NPN scenarios.
|
28.908
|
Study on Artificial Intelligence/Machine Learning (AI/ ML) management
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.908/28908-i10.zip
|
The present document studies the Artificial Intelligence / Machine Learning (AI/ML) management capabilities and services for 5GS where AI/ML is used, including management and orchestration (e.g. MDA, see 3GPP TS 28.104 [2]), 5GC (e.g. NWDAF, see 3GPP TS 23.288 [3], and NG-RAN (e.g. RAN intelligence defined in 3GPP TS 38.300 [16] and 3GPP TS 38.401 [19]).
|
28.909
|
Study on evaluation of autonomous network levels
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.909/28909-i00.zip
|
The present document studies on evaluation of autonomous network levels. It introduces the relevant studies in other SDOs, concepts of autonomous network levels evaluation and key effectiveness indicators (KEI). It identifies key issues related to autonomous network levels evaluation, documents potential solutions, and provides recommendations for the further normative work.
|
28.910
|
Study on enhancement of autonomous network levels
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.910/28910-i00.zip
|
The present document studies on enhancement of autonomous network levels. It introduces the relevant study items and work items in 3GPP, identifies the additional generic MnS requirements of generic autonomous network level for the scenarios defined in Rel-17 and documents potential solutions for the identified generic MnS requirements. It also identifies the enhanced autonomy capabilities corresponding to different autonomous network levels for additional management use cases which is not defined in Rel-17 and documents potential solutions for the enhanced autonomy capabilities. Based on the investigation and studies, it provides recommendations for the further normative work.
|
28.912
|
Study on enhanced intent driven management services for mobile networks
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.912/28912-i01.zip
|
The present document investigates new areas for enhancing the intent driven management services of 5G network. It identifies and documents key issues and evaluates potential solutions, and provides recommendations for the normative work.
|
28.913
|
Study on new aspects of Energy Efficiency (EE) for 5G phase 2
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.913/28913-i01.zip
|
The present document investigates the opportunities for defining new Energy Efficiency (EE) KPIs and new Energy Saving (ES) solutions for 5G. It identifies and documents key issues related to energy efficiency and energy saving, documents and evaluates potential solutions, and provides recommendations for the normative work.
|
28.925
|
Study on enhancement of service based management architecture
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.925/28925-i00.zip
|
The present document studies on the potential enhancement of service based management architecture based on the existing 5G service based management architecture.
|
29.002
|
Mobile Application Part (MAP) specification
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.002/29002-i00.zip
|
It is necessary to transfer between entities of a Public Land Mobile Network (PLMN) information specific to the PLMN in order to deal with the specific behaviour of roaming Mobile Stations (MS)s. The Signalling System No. 7 specified by CCITT is used to transfer this information.
The present document describes the requirements for the signalling system and the procedures needed at the application level in order to fulfil these signalling needs.
Clauses 1 to 6 are related to general aspects such as terminology, mobile network configuration and other protocols required by MAP.
MAP consists of a set of MAP services that are provided to MAP service-users by a MAP service-provider.
Figure 1.1/1: Modelling principles
Clauses 7 to 13A of the present document describe the MAP services.
Clauses 14 to 17 define the MAP protocol specification and the behaviour of service provider (protocol elements to be used to provide MAP services, mapping on to TC service primitives, abstract syntaxes, etc.).
Clauses 18 to 25 describe the MAP user procedures that make use of MAP services.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
|
29.007
|
General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.007/29007-i00.zip
|
The present document identifies the Mobile‑services Switching Centre/Interworking Functions (MSC/IWFs) and requirements to support interworking between:
a) PLMN and PSTN;
b) PLMN and ISDN;
for circuit switched services in the PLMN. It is not possible to treat ISDN and PSTN as one type of network, even when both ISDN and PSTN subscribers are served by the same exchange because of the limitations of the PSTN subscribers access i.e. analogue connection without D‑channel signalling.
Within the present document, the requirements for voice and non‑voice (data) calls are considered separately.
From R99 onwards the following services are no longer required by a PLMN:
- the dual Bearer Services "alternate speech/data" (BS 61) and "speech followed by data" (BS 81);
- the dedicated services for PAD (BS 4x) and Packet access (BS 5x);
- the single asynchronous and synchronous Bearer Services (BS 21..26, BS 31..34).
From Rel-4 onwards the following services are no longer required by a PLMN:
- the synchronous Bearer Service non-transparent (BS 30 NT);
- the Basic Packet access;
- Non-transparent facsimile (TS 61/62 NT) for the A/Gb mode and GERAN Iu mode.
If a PLMN still provides these services it shall fulfil the specification of former releases.
The present document is valid for a PLMN in A/Gb mode as well as in Iu mode. If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". If text applies to both of the systems, but a distinction between the ISDN/PSTN and the PLMN is necessary, the term "PLMN" is used.
NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
|
29.010
|
Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling Procedures and the Mobile Application Part (MAP)
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.010/29010-i00.zip
|
The scope of the present document is:
i) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-MSC interface (Call Control and Mobility Management parts of 3GPP TS 24.008 [4]) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002 [9]) where the MSC acts as a transparent relay of information;
ii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages sent on the BSC-MSC interface (3GPP TS 48.008 [12]) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002 [9]) where the MSC acts as a transparent relay of information;
iii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (3GPP TS 48.008 [12]) and RANAP ((3GPP TS 25.413 [7]);
iv) to provide a detailed specification for the interworking as in i) and ii) above when the MSC also processes the information;
v) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-SGSN interface (GPRS mobility part of 3GPP TS 24.008 [4]) and parameters contained in MAP services sent over the SGSN-HLR interface (3GPP TS 29.002 [9]);
vi) to provide a detailed specification for the interworking between information elements contained in RANAP messages sent on the SGSN-RNC interface (3GPP TS 25.413 [7]) and parameters contained in S1AP messages sent on the MME-eNodeB interface (3GPP TS 36.413 [21]);
vii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (3GPP TS 48.008 [12]) or RANAP messages (3GPP TS 25.413 [7]) during SRVCC handovers.
Interworking for supplementary services is given in 3GPP TS 29.011 [11]. Interworking for the short message service is given in 3GPP TS 23.040 [3] and 3GPP TS 24.011. Interworking between the call control signalling of 3GPP TS 24.008 [4] and the PSTN/ISDN is given in GSM 09.03 [13], 3GPP TS 29.007 [10] and 3GPP TS 49.008 [14] [14]. Interworking between the 'A' and 'E' interfaces for inter-MSC handover signalling is given in 3GPP TS 29.007 [10] and 3GPP TS 49.008 [14] [14].
|
29.011
|
Signalling Interworking for supplementary services
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.011/29011-i00.zip
|
The scope of this Technical Specification is to provide a detailed specification for interworking between the A interface protocol and the Mobile Application Part for handling of supplementary services. The MAP interfaces of interest are the B-, C-, D- and E-interfaces.
The A-, C-, D- and E-interfaces are physical interfaces while the B-interface is an internal interface defined for modelling purposes. Information relating to the modelling interface is not normative in this specification.
Supplementary service signalling may be passed by the MSC/VLR between the A- and E-interfaces after inter-MSC handover. This procedure is transparent as far as supplementary services are concerned therefore interworking concerning this process is not described in this specification.
Clause 2 describes general procedures for interworking between the A- and D- physical interfaces.
Clause 3 describes the general procedures for the SS version negotiation.
Clause 4 describes the mapping of layer 3 radio path messages with Transaction Capabilities (TC) transaction sublayer messages for interworking between the A- and D- physical interfaces.
Clause 5 describes specific interworking procedures for all interfaces relating to call related SS activity.
Clause 6 describes specific interworking procedures for all interfaces relating to call independent SS activity. Clause 6 also covers the interworking between the MAP User (see 3GPP TS 29.002) and the SS handling functions of the network entities (see 3GPP TS 24.010 and 3GPP TS 24.080).
Reference is made to the following Technical Specifications:
- 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x-series,
for definition of supplementary services;
- 3GPP TS 23.011, 3GPP TS 23.08x and 3GPP TS 23.09x-series,
for technical realisation of supplementary services;
- 3GPP TS 24.010, 3GPP TS 24.080, 3GPP TS 24.08x and 3GPP TS 24.09x-series,
for radio path signalling procedures for supplementary services;
- 3GPP TS 29.002 (MAP).
|
29.013
|
Signalling interworking between ISDN supplementary services; Application Service Element (ASE) and Mobile Application Part (MAP) protocols
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.013/29013-i00.zip
|
The scope of the present document is to provide a specification for interworking between the ISDN Application Service Element (ASE) protocol for supplementary services and the Mobile Application Part (MAP) protocol on MAP D-interface protocol for handling of supplementary services within the digital cellular telecommunications system (Phase 2+). This version of the specification includes the interworking for the Call Completion to Busy Subscriber (CCBS) service between the ISDN CCBS-ASE and MAP.
The MAP protocol for CCBS service is specified in GSM 09.02. The ISDN CCBS-ASE protocol is specified in ETS 300 356‑18. The ISDN CCBS-ASE protocol is also commonly referred to as the SSAP protocol in GSM 03.93. This specification clarifies the interworking within the HLR between these protocols for the Call Completion to Busy Subscriber (CCBS) service.
Clause 4 describes the mapping between MAP application layer messages and SSAP application layer messages.
Clause 5 describes the mapping between MAP message parameters and SSAP message parameters.
Clause 6 describes the dialogue handling on the SSAP interface.
Clause 7 describes the SCCP layer addressing for messages on the SSAP interface.
|
29.016
|
General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.016/29016-i00.zip
|
The present document specifies or references the subset of MTP and SCCP which is used for the reliable transport of BSSAP+ messages in the Gs interface. The present document references the 3GPP TS 29.202 which specifies alternative transport layers that can be applied instead of the MTP. The present document also specifies the SCCP addressing capabilities to be provided in the Gs interface.
The present document is divided into two main parts, clause 5 dealing with the use of MTP and clauses 6 and 7 dealing with the use of SCCP.
Clause 5 of the present document deals with the subset of the MTP that is required between an SGSN and a VLR. It is intended that this implementation of MTP is compatible with a full MTP implementation. Clause 4 references the 3GPP TS 29.202 which specifies alternatives to the MTP.
The SCCP is used to provide message routing between the SGSN and the VLR. The SCCP routing principles specified in the present document allow to connect one SGSN to several VLR. No segmentation at SCCP level is needed on the Gs interface. Only SCCP class 0 is used on the Gs interface. Clauses 6 and 7 identify the SCCP subset that should be used between an SGSN and an VLR.
|
29.018
|
General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.018/29018-i00.zip
|
The present document specifies or references procedures used on the Serving GPRS Support Node (SGSN) to Visitors Location Register (VLR) interface for interoperability between GSM circuit switched services and GSM packet data services.
The present document specifies the layer 3 messages and procedures on the Gs interface to allow coordination between databases and to relay certain messages related to GSM circuit switched services over the GPRS subsystem.
The functional split between VLR and SGSN is defined in 3GPP TS 23.060 [8]. The required procedures between VLR and SGSN are defined in detail in the present document.
|
29.060
|
General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.060/29060-i00.zip
|
The present document defines the second version of GTP used on:
- the Gn and Gp interfaces of the General Packet Radio Service (GPRS);
- the Iu, Gn and Gp interfaces of the UMTS system.
NOTE: The version number used in the message headers is 0 for the first version of GTP described in GSM 09.60, and 1 for the second version in 3GPP TS 29.060.
From release 8 onwards, the normative specification of the user plane of GTP version 1 is 3GPP TS 29.281 [41]. All provisions about GTPv1 user plane in the present document shall be superseded by 3GPP TS 29.281 [41].
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
|
29.079
|
Optimal media routeing within the IP Multimedia Subsystem (IMS); Stage 3
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.079/29079-i00.zip
|
The present document defines optional Optimal Media Routeing (OMR) procedures that can be applied by entities in the IP Multimedia Subsystem (IMS) that control media resources and are capable of manipulating the Session Description Protocol (SDP) as defined by IETF RFC 4566 [6].
The OMR procedures in the present specification relate to the handling of OMR-specific SDP attributes that are documented in TS 24.229 [4]. The OMR procedures use SDP offer/answer related procedures in IETF RFC 3264 [5] and in 3GPP TS 24.229 [4] in a backward-compatible manner.
The 3GPP network architecture, including the configuration and network entities of the IMS, is defined in 3GPP TS 23.002 [2]. The Stage 2 of the IMS is defined 3GPP TS 23.228 [3]. Annex Q of 3GPP TS 23.228 [3] documents the architecture and call flows for OMR.
The OMR procedures in this document are applicable to the following IMS entities that perform as an IMS-ALG or UA according to 3GPP TS 24.229 [4] and that control media resources:
- an IBCF acting as an IMS-ALG;
- a P-CSCF acting as IMS-ALG;
- an AS acting as B2BUA and adapting IMS-ALG procedures to control an MRF;
- an AS acting as B2BUA and adapting UA procedures to control an MRF; and
- an MGCF acting as UA.
NOTE 1: An AS acting as B2BUA to perform application functions such as conferencing or announcements will normally perform separate originating and terminating UA procedures, treating the media resource as an endpoint. An AS acting as B2BUA offering transcoding options will typically follow IMS-ALG procedures.
NOTE 2: The controlled media resource can be a TrGW, IMS-AGW, MRF, or a media function of the entity performing OMR.
The OMR procedures are not applicable for an UE.
|
29.108
|
Application of the Radio Access Network Application Part (RANAP) on the E-interface
|
TS
|
18.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.108/29108-i00.zip
|
The present document describes the subset of Radio Access Network Application Part (RANAP) messages and procedures, defined in 3GPP TS 25.413 [4], which is used on the E‑interface. A general description can be found in 3GPP TS 23.002 [7] and 3GPP TS 23.009 [2].
For the initiation and execution of relocation of SRNS (relocation for short, throughout the whole document) between MSCs a subset of RANAP procedures are used. For the subsequent control of resources allocated to the User Equipment (UE) RANAP procedures are used. The Direct Transfer Elementary Procedure (EP) of RANAP, is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G_MSC.
|
29.109
|
Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.109/29109-i10.zip
|
The present stage 3 specification defines the Diameter based implementation for bootstrapping Zh interface (BSF-HSS) and Dz interface (BSF-SLF) for HSS resolution for the BSF, the MAP based implementation for bootstrapping Zh' interface (BSF-HLR) and GAA Application Zn interface (BSF-NAF) in Generic Authentication Architecture (GAA). This specification also defines the Web Services based implementation for GAA Application Zn reference point (BSF-NAF). The definition contains procedures, message contents and coding. The procedures for bootstrapping and usage of bootstrapped security association are defined in 3GPP TS 33.220 [5].
The present document also specifies the Diameter and Web Services based implementation for the GAA Application Push Function Zpn reference point (BSF-NAF). The procedures for bootstrapping are defined in 3GPP TS 33.223 [23].
This specification is a part of the Generic Authentication Architecture (GAA) specification series.
The diameter based implementation for the Zh interface is based on re-usage of Cx interface Multimedia-Auth-Request/Answer messages originally between CSCF and HSS. These messages are defined in 3GPP TS 29.229 [3]. The 3GPP IMS mobility management uses the same definitions between CSCF and HSS. The present document defines how the defined messages are used with the bootstrapping and GAA application procedures (e.g. subscriber certificates) and the application logic that is needed in GAA network elements (BSF, HSS, and NAF).
Figure 1.1 depicts the relationships of these specifications to the other specifications for the Diameter based implementations.
Figure 1.1: Relationships to other specifications
Figure 1.2 provides an informal overall quick introduction to the whole signalling procedures in GAA system. The important identifiers are marked bold and optional data items are italicised. The Ub and Ua interfaces, not defined in this TS, are simplified.
NOTE: The Zh' interface (BSF-HLR) is not represented in this figure.
Figure 1.2: The whole signalling procedure in GAA system
Figure 1.3 provides an informal overall quick introduction to the whole signalling procedures in GAA Push Function. The important identifiers are marked bold and optional data items are italicised. The Ua and Upa interfaces, not defined in this TS, are simplified.
Figure 1.3: Signalling procedure in GAA Bootstrapping Push Function
|
29.116
|
Representational state transfer over xMB reference point between content provider and BM-SC
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.116/29116-i00.zip
|
The present document describes the REST-based protocol for the xMB reference point between the Content Provider and the BM-SC. The xMB reference point and related stage 2 protocol procedures are defined in 3GPP TS 23.246 [2] and in 3GPP TS 26.346 [3].
|
29.119
|
GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR)
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.119/29119-i00.zip
|
The present document describes the signalling requirements and procedures used at network elements related to the GLR for GTP within the 3GPP system at the application level.
The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3GPP TS 29.060.
|
29.120
|
Mobile Application Part (MAP) specification for Gateway Location Register (GLR)
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.120/29120-i00.zip
|
The present document describes the signalling requirements and procedures used at network elements related to the GLR for MAP within the 3GPP system at the application level.
The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3GPP TS 29.002.
|
29.139
|
3GPP system - fixed broadband access network interworking; Home (e)Node B - security gateway interface
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.139/29139-i00.zip
|
The present document specifies the H(e)NB – SeGW interface. The interface is used for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum. The interworking procedure provides the IP connectivity to a 3GPP UE using a H(e)NB connected to a Fixed Broadband Access network as specified in 3GPP TS 23.139 [2].
The specification covers the QoS aspects and Tunnel management procedures.
|
29.153
|
Service capability exposure functionality over Ns reference point
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.153/29153-i00.zip
|
This document defines the protocol for Ns reference point between the Service Capability Exposure Function (SCEF) and RAN Congestion Awareness Function (RCAF).
The Ns reference point and related stage 2 procedures are defined in 3GPP TS 23.682 [2].
|
29.154
|
Service capability exposure functionality over Nt reference point
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.154/29154-i00.zip
|
This document defines the protocol for Nt reference point. The Nt reference point includes Nt application and Nta application.
The functional requirements and the stage 2 specifications of the Nt application are contained in 3GPP TS 23.203 [2]. The Nt application of Nt reference point lies between Service Capability Exposure Function (SCEF) and Policy and Charging Rules Function (PCRF), it supports the negotiation of background data transfer policy and is documented in the main body of this document.
The functional requirements and the stage 2 specifications of the Nta application are contained in clause 5.6.4.1a of 3GPP TS 23.682 [x5]. The Nta application of Nt reference point lies between SCEF and PCRF, it supports the event monitoring configuration for a group of UEs and the corresponding event reporting. The Nta application is documented in Annex A.
NOTE: Nta is a stage 3 name of Diameter Application due to extensibility rule mentioned in IETF RFC 6733 [15].
|
29.155
|
Traffic steering control; Representational State Transfer (REST) over St reference point
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.155/29155-i00.zip
|
The present document describes the Representational State Transfer (REST) protocol-based St reference point, which is used to provision the traffic steering control information to the TSSF from the PCRF.
|
29.168
|
Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.168/29168-i00.zip
|
The present document specifies the procedures and the SBc Application Part (SBc-AP) messages used on the SBc-AP interface between the Mobility Management Entity (MME) and the Cell Broadcast Centre (CBC), and between the Public Warning System – Inter Working Function (PWS-IWF) and the CBC.
The present document supports the following functions:
- Warning Message Transmission function in the EPS,
- Warning Message Transmission function in the 5GS via the PWS-IWF (see 3GPP TS 23.041 [14]).
NOTE: The SBc-AP interface is a logical interface between the MME and the CBC and also between the PWS-IWF and the CBC, when connected to 5GC. The PWS-IWF may not be always explicitly mentioned in the remainder of the present document.
|
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
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.171/29171-i00.zip
|
The present document specifies the procedures and information coding for LCS Application Protocol (LCS-AP) that is needed to support the location services in E-UTRAN. The LCS-AP message set is applicable to the SLs interface between the E-SMLC and the MME. LCS-AP is developed in accordance to the general principles stated in 3GPP TS 23.271 [3].
|
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
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.172/29172-i10.zip
|
The present document specifies the procedures and information coding for the EPC LCS Protocol (ELP) that is needed to support the location services in E-UTRAN, UTRAN and GERAN. The ELP message set is applicable to the SLg interface between the MME and the GMLC and the Lgd interface between the SGSN and the GMLC. ELP is developed in accordance to the general principles stated in 3GPP TS 23.271 [2].
|
29.173
|
Location Services (LCS); Diameter-based SLh interface for Control Plane LCS
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.173/29173-i00.zip
|
The present document describes the Diameter-based SLh interface between the GMLC and the HSS defined for the Control Plane LCS in EPC.
LCS procedures over the SLh interface are defined in the 3GPP TS 23.271 [2].
This specification defines the Diameter application for the GMLC-HSS, SLh reference point. The interactions between the HSS and the GMLC are specified, including the signalling flows. As LCS procedures over the Diameter-based SLh interface are identical to the MAP-based Lh interface, the descriptions of the Lh MAP operations defined in the 3GPP TS 29.002 [3] are mapped into the descriptions of the SLh Diameter commands.
|
29.201
|
Representational State Transfer (REST) reference point between Application Function (AF) and Protocol Converter (PC)
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.201/29201-i00.zip
|
The present document describes the Representational State Transfer (REST) reference point, which is used to exchange application level session information between the Protocol Converter (PC) and the Application Function (AF). REST shall be used as an architectural style as appropriate.
|
29.202
|
Signalling System No. 7 (SS7) signalling transport in core network; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.202/29202-i00.zip
|
The present document defines the possible protocol architectures for transport of SS7 signalling protocols in Core Network.
|
29.204
|
Signalling System No. 7 (SS7) security gateway; Architecture, functional description and protocol details
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.204/29204-i00.zip
|
The present document provides functional description of the SS7 Security Gateway. The document covers also network architecture, routeing considerations, and protocol details.
|
29.205
|
Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.205/29205-i00.zip
|
The present document describes the protocols to be used when ITU-T Q.1902 "Bearer Independent Call Control" is used as call control protocol in a 3GPP Bearer Independent CS core network 3GPP TS 23.205 [1] The Q.1902 operates between (G)MSC servers .The BICC architecture as described in ITU-T Q.1902 [6]-[10] consists of a number of protocols. The following types of protocols are described: call control protocol, bearer control protocols and a resource control protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.205 [1] and TS 23.153 [2].
The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 4 and later.
Note: Q.1902 can be used in other network architectures than the one defined in 3GPP TS 23.205 [1]
|
29.212
|
Policy and Charging Control (PCC); Reference points
|
TS
|
18.2.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.212/29212-i20.zip
|
The present document provides the stage 3 specification of the Gx, Gxx and Sd reference points for the present release. The present document also provides the Diameter variant of St reference point for the present release. The functional requirements and the stage 2 specifications of the Gx, Gxx, Sd and St reference points are contained in 3GPP TS 23.203 [7]. The Gx reference point lies between the Policy and Charging Rule Function and the Policy and Charging Enforcement Function. The Gxx reference point lies between the Policy and Charging Rule Function and the Bearer Binding and Event Reporting Function. The Sd reference point lies between the Policy and Charging Rule Function and the Traffic Detection Function. The St reference point lies between the Policy and Charging Rule Function and the Traffic Steering Support Function.
Whenever it is possible the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
|
29.215
|
Policy and Charging Control (PCC) over S9 reference point; Stage 3
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.215/29215-i00.zip
|
The present document provides the Stage 3 specification of the S9 reference point for the present release. The functional requirements of Stage 2 specification for the S9 reference point are contained in 3GPP TS 23.203 [2]. The S9 reference point lies between the PCRF in the home PLMN (also known as H-PCRF) and the PCRF in the visited PLMN (also known as V-PCRF).
Whenever it is possible the present document specifies the requirements for the protocols by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible extensions to Diameter are defined within the present document.
|
29.217
|
Policy and Charging Control (PCC); Congestion reporting over Np reference point
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.217/29217-i00.zip
|
The present document provides the stage 3 specification of the Np reference point. The functional requirements and the stage 2 specifications of the Np reference point are contained in 3GPP TS 23.203 [2]. The Np reference point lies between the RAN Congestion Awareness Function (RCAF) and the Policy and Charging Rules Function (PCRF) for the non-roaming case, between the RCAF and the H-PCRF for the home-routed scenario and between the RCAF and the V-PCRF for the visited access scenario.
NOTE: If not specified explicitly, the PCRF also means H-PCRF for the home-routed scenario or V-PCRF in the visited access scenario in the specification.
|
29.219
|
Policy and charging control: Spending limit reporting over Sy reference point
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.219/29219-i00.zip
|
The present document provides the stage 3 specification of the Sy reference point for the present release. The functional requirements and the stage 2 specifications of the Sy reference point are contained in TS 23.203 [2]. The Sy reference point lies between the Policy and Charging Rule Function (PCRF) and the Online Charging System (OCS). The internal OCS functionality for policy counter provision management pertaining to Sy is specified in TS 32.296 [16].
|
29.229
|
Cx and Dx interfaces based on the Diameter protocol; Protocol details
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.229/29229-i10.zip
|
The present document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter base protocol as specified in IETF RFC 6733 [28].
The present document is applicable to:
- The Cx interface between the I-CSCF/S-CSCF and the HSS.
- The Dx interface between the I-CSCF/S-CSCF and the SLF.
Whenever it is possible, this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter base protocol as specified in IETF RFC 6733 [28]. Where this is not possible, extensions to Diameter base protocol as specified in IETF RFC 6733 [28] are defined within this document.
|
29.232
|
Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.232/29232-i10.zip
|
The present document describes the protocol to be used on the Media Gateway Controller (MGC) – Media Gateway (MGW) interface. The Media Gateway Controllers covered in this specification are the MSC server and the GMSC server. The basis for this interface profile is the H.248.1 [10] protocol as specified in ITU-T. The usage of this protocol is described in 3GPP TS 23.205 [2] and 3GPP TS 29.205 [7] for BICC circuit switched core network, in 3GPP TS 23.231 [54] and 3GPP TS 29.231 [57] for SIP-I circuit switched core network.
This profile includes the support for the enhanced MSC server to provide access to IMS Centralised services as described in 3GPP TS 23.292 [59] and thus the procedures related to this interface are described in 3GPP TS 29.292 [60]. As a result the interworking with SIP and the associated MGW control procedures described in 3GPP TS 29.163[61] for the interworking between BICC/ISUP circuit switched core network and IP Multimedia core network are incorporated.
This specification describes the changes to H.248 which are needed to handle 3GPP specific traffic cases. This is done by using the H.248 standard extension mechanism. In addition certain aspects of the base protocol H.248 are not needed for this interface and thus excluded by this profile.
|
29.235
|
Interworking between SIP-I based circuit-switched core network and other networks
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.235/29235-i00.zip
|
The present document specifies the interworking between SIP-I based circuit-switched core network, as specified in TS 23.231 [3] and TS 29.231 [4], with out-of-band transcoder control related procedures in TS 23.153 [5], and:
- an external SIP-I based signalling network compliant to ITU-T Recommendation Q.1912.5 [6],
- an ISUP (ITU-T Recommendations Q.761 to Q.764 [7]) based network such as an ISUP based 3GPP CS Domain or a PSTN,
- a BICC (ITU-T Recommendations Q.1902.1 to Q.1902.6 [8]) based network such as an BICC based 3GPP CS Domain as specified in TS 23.205 [9] and TS 29.205 [10],
- an IP Multimedia Subsystem, as specified in TS 23.228 [11] and TS 24.229 [12].
|
29.238
|
Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3
|
TS
|
18.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.238/29238-i20.zip
|
The present document describes the protocol to be used on the Interconnection Border Control Function (IBCF) – Transition Gateway (TrGW) interface and the CS-IBCF – CS-TrGW interface. The basis for this protocol is the H.248 protocol as specified in ITU-T. The Profile provides MG control function for IMS and CS Border Control. The IMS architecture is described in 3GPP TS 23.228 [2]. The underlying reference model and stage 2 information is described in Annex I of 3GPP TS 23.228 [2] and in 3GPP TS 29.162 [18]. The CS architecture is described in Annex A of 3GPP TS 29.235 [17].
This specification describes the application of H.248 Ix profile for both Ix and CS-Ix interfaces (see Figure 1.1 and Figure 1.2). Required extensions use the H.248 standard extension mechanism. In addition certain aspects of the base protocol H.248 are not needed for this interface and thus excluded by this profile.
Figure 1.1: Reference model for IMS Border Control Functions
Figure 1.2: Reference model for CS Border Control Functions
The reference model for the IBCF and the TrGW supporting the ATCF/ATGW function is shown in Figure 1.x below.
Figure 1.3: Reference model for IBCF/TrGW with ATCF/ATGW function
See 3GPP TS 23.237 [38] clause 5.2 for a comprehensive description of the reference model.
NOTE: The Ix profile is applied over both IMS and CS Ix interfaces.
In the following text the terms IBCF and TrGW also include respectively the CS-IBCF and CS-TrGW functionalities.
|
29.240
|
3GPP Generic User Profile (GUP); Stage 3; Network
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.240/29240-i00.zip
|
The present document defines the stage 3 network protocol description to the 3GPP Generic User Profile (GUP), which includes the elements necessary to realise the stage 2 requirements in 3GPP TS 23.240 [1].
The fact of having several domains within the 3GPP mobile system (e.g. Circuit-Switched, Packet-Switched, IP Multimedia Subsystem) and access technologies (e.g. GERAN, UTRAN and WLAN) introduces a wide distribution of data associated with the user. Further, the new functions both in terminals and networks mean that the data related to users, services and user equipment will be increased greatly. This causes difficulties for users, subscribers, network operators and value added service providers to create, access and manage the user-related data located in different entities.
The objective of specifying the 3GPP Generic User Profile is to provide a conceptual description to enable harmonised usage of the user-related information located in different entities. Technically the 3GPP Generic User Profile provides an architecture, data description and interface with mechanisms to handle the data.
|
29.250
|
Nu reference point between SCEF and PFDF for sponsored data connectivity
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.250/29250-i00.zip
|
The present document provides the stage 3 specification of the Nu reference point. The functional requirements and the stage 2 specifications of the Nu reference point are specified in 3GPP TS 23.682 [2]. The Nu reference point lies between the Packet Flow Description Function (PFDF) and the Service Capability Exposure Function (SCEF).
|
29.251
|
Gw and Gwn reference point for sponsored data connectivity
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.251/29251-i00.zip
|
The present document provides the stage 3 specification of the Gw and Gwn reference points. The functional requirements and the stage 2 specifications of the Gw and Gwn reference points are specified in 3GPP TS 23.203 [2]. The Gw reference point lies between the Packet Flow Description Function (PFDF) and the Policy and Charging Enforcement Function (PCEF). The Gwn reference point lies between the Packet Flow Description Function (PFDF) and the Traffic Detection Function (TDF).
|
29.275
|
Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.275/29275-i00.zip
|
The present document specifies the stage 3 of the PMIPv6 Based Mobility and Tunnelling Protocols used over the PMIP-based S2a, S2b, S5, and S8 reference points defined in 3GPP TS 23.402 [3], and are thus applicable to the Serving GW, PDN Gateway, ePDG, and Trusted Non-3GPP Access. Protocols specifications are compliant with relevant IETF RFCs. In this specification PMIP refers to PMIPv6 as defined in IETF RFC5213 [4] taking into account the corrections regarding the protocol number definition in IETF RFC6275 [8].
|
29.276
|
3GPP Evolved Packet System (EPS); Optimized handover procedures and protocols between E-UTRAN access and cdma2000 HRPD Access; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.276/29276-i00.zip
|
The present document specifies the stage 3 of the Evolved Packet System S101and S121 reference points between the MME and the HRPD Access Network. The S101 interface supports procedures for Pre-Registration, Session Maintenance and Active handoffs between E-UTRAN and HRPD networks. The S121 interface supports procedures for RIM information exchange between the MME and the HRPD Access Network.
It also specifies the S103 interface between the Serving GW and HSGW. This User Plane interface is used to forward DL data to minimize packet losses in mobility from E-UTRAN to HRPD. Signalling procedures on the S101 interface are used to set up tunnels on the S103 interface.
|
29.277
|
Optimised handover procedures and protocol between EUTRAN access and non-3GPP accesses (S102); Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.277/29277-i00.zip
|
The present document specifies the stage 3 of the Evolved Packet System S102 interface between the MME and the 1x CS IWS to relay the 1xCS signalling messages documented in 3GPP TS 23.216 [2] and 3GPP TS 23.272 [4]. 1x CS signalling messages are those messages that are defined for A21 interface as described in 3GPP2 A.S0008-D [3] and 3GPP2 A.S0009-D [6]. The S102 interface messages shall be based on A21 messages.
The S102 interface is used to support UEs that do not transmit and receive on both the LTE and 1x radio interfaces simultaneously. S102 protocol aspects for SRVCC from E-UTRAN access to 3GPP2 1xCS is covered in this specification. Handling of non-voice component and protocol aspects for SRVCC from 3GPP2 1xCS to E-UTRAN direction is not specified in this release.
The S102 interface is also used to support CS fallback to 1xRTT procedures from E-UTRAN access to CDMA 1x RTT CS domain and to support SMS over S102 with the CDMA 1xRTT CS domain through support of registration over EPS procedures as specified in 3GPP TS 23.272[4].
|
29.278
|
Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part (CAP) specification for IP Multimedia Subsystems (IMS)
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.278/29278-i00.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 for IP Multimedia CN subsystems. CAP is based on a sub-set of the ETSI Core INAP CS-2 as specified by EN 301 140‑1 [4]. Descriptions and definitions provided by EN 301 140‑1 [4] are directly referenced by this standard in case no additions or clarifications are needed for the use in the CAP.
|
29.279
|
Mobile IPv4 (MIPv4) based mobility protocols; Stage 3
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.279/29279-i10.zip
|
The present document specifies the stage 3 of the MIPv4 Based Mobility Protocol used over the S2a reference point defined in 3GPP TS 23.402 [3], and is thus applicable to the PDN Gateway and Trusted Non-3GPP Access. Protocol specification is compliant with relevant IETF RFCs.
|
29.280
|
Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.280/29280-i00.zip
|
The present document describes the Sv interface between the Mobility Management Entity (MME) or Serving GPRS Support Node (SGSN) and 3GPP MSC server enhanced for SRVCC. Sv interface is used to support Inter-RAT handover from IMS based voice service over EPS to CS domain over 3GPP UTRAN/GERAN access or from UTRAN (HSPA) to 3GPP UTRAN/GERAN access and to support Inter-RAT handover from IMS based voice and video service over EPS to CS domain over 3GPP UTRAN access. Sv interface is also used to support Inter-RAT handover from voice service in CS domain over 3GPP UTRAN/GERAN access to IMS based service over LTE or UTRAN (HSPA).
If there is no specific indication, the term "MSC server" denotes 3GPP MSC server enhanced for SRVCC or 3GPP MSC server enhanced for vSRVCC as defined in 3GPP TS 23.216 [2].
|
29.282
|
Mobile IPv6 vendor specific option format and usage within 3GPP
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.282/29282-i00.zip
|
The present document specifies the format and usage of the Mobile IPv6 Vendor Specific Option [2] within the Third Generation Partnership Project.
|
29.283
|
Diameter data management applications
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.283/29283-i00.zip
|
The common functional architecture for support of Mission Critical (MC) services is specified in 3GPP TS 23.280 [21].
The functional architecture for support of Mission Critical Push To Talk (MCPTT) services is specified in 3GPP TS 23.379 [18].
The functional architecture for support of Mission Critical Video (MCVideo) services is specified in 3GPP TS 23.281 [19].
The functional architecture for support of Mission Critical Data (MCData) services is specified in 3GPP TS 23.282 [20].
This 3GPP Technical Specification (TS) specifies:
1. The interactions between the MC Service User Database and the MC Service Server:
- This interface between the MCPTT User Database and the MCPTT Server is referred to as the MCPTT-2 reference point, as specified in 3GPP TS 23.379 [18].
- This interface between the MCVideo User Database and the MCVideo Server is referred to as the MCVideo-2 reference point, as specified in 3GPP TS 23.281 [19].
- This interface between the MCData User Database and the MCData Server is referred to as the MCData-2 reference point, as specified in 3GPP TS 23.282 [20].
- This interface between the MCData User Database and the MCData Server is referred to as the MCVideo-2 reference point, as specified in 3GPP TS 23.282 [20].
2. The interactions between the MC Service User Database and the Configuration Management Server. This interface is referred to as the CSC-13 reference point.
|
29.292
|
Interworking between the IP Multimedia (IM) Core Network (CN) subsystem (IMS) and MSC Server for IMS Centralized Services (ICS)
|
TS
|
18.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.292/29292-i10.zip
|
IMS Centralized Services (ICS) enable the delivery of IM CN subsystem based multimedia telephony and supplementary services as defined in 3GPP TS 24.173 [4] to users regardless of the attached access network type; e.g. CS domain access or IP-CAN.
The present document specifies the principles of interworking between the IM CN subsystem and CS domain in order to enable ICS for UEs using CS domain access.
The present document addresses the area of registration procedures interworking between the CS domain and IM CN subsystem.
The present document addresses the areas of control and user plane interworking between the IM CN subsystem and CS domain through an MSC Server enhanced for ICS and CS-MGW respectively. This includes the signalling procedures between the MSC Server and CS-MGW. For the specification of control plane interworking, present document defines the protocol interworking between the 3GPP profile of SIP as described in 3GPP TS 24.229 [2] and NAS signalling as described in 3GPP TS 24.008 [3] required for the support of IM CN subsystem based multimedia telephony and supplementary services.
The present document addresses the area of supplementary service configuration interworking between the CS domain and IM CN subsystem.
The present document is applicable to the MSC Server and CS-MGW.
|
29.303
|
Domain Name System Procedures; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.303/29303-i00.zip
|
The present document describes Domain Name System (DNS) Procedures for the Evolved Packet System. This document covers the Evolved Packet Core gateway node selection using DNS (e.g. SGW and PGW nodes) excluding all User Equipment (UE) initiated DNS-based discovery and selection procedures.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
The present document also describes the Domain Name System (DNS) Procedures for the Evolved Packet System interworking with the 5G System, as specified in 3GPP TS 23.501 [28] and 3GPP TS 23.502 [29].
|
29.305
|
InterWorking Function (IWF) between MAP based and Diameter based interfaces
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.305/29305-i00.zip
|
The present document is to specify the InterWorking Functions (IWF)
- between MAP-based Gr, Gf interfaces and Diameter-based S6a, S6d, S13, S13a interfaces;
- between the S6a interface with SMS subscription data on the MME side and the S6a interface without SMS subscription data plus the MAP-based D interface for SMS subscription on the HSS side;
- between MAP-based C for SMS interface and Diameter-based S6c interface;
- between MAP-based E for SMS interface and Diameter-based SGd interface.
The InterWorking Function between the S6a interface with SMS subscription data and the S6a interface without SMS subscription data plus the MAP-based D interface for SMS subscription (S6a/S6a+D) is described in Annex A.
The InterWorking Function between MAP-based C for SMS interface and Diameter-based S6c interface is described in Annex A.3
The InterWorking Function between MAP-based E for SMS interface and Diameter-based SGd interface is described in Annex A.2
For each IWF scenario, the present document will specify the mapping of related procedures and the corresponding parameter handling.
The present document will also specify the related mechanisms for the IWF, e.g. message routing, user data handling. The other mechanism, such as security, will also be described in this document as a part of the whole solution.
If there is no specific indication, the SGSN in the specification refers to a S4-SGSN which supports S4 interface.
|
29.309
|
Bootstrapping Server Function (GBA BSF) Services
|
TS
|
18.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.309/29309-i20.zip
|
The present document specifies the stage 3 protocol and data model for the Nbsp Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the GBA BSF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The stage 2 architecture and procedures of SBA-enabled GBA is specified in 3GPP TS 33.220 [14] and 3GPP TS 33.223 [15].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
|
29.311
|
Service Level Interworking (SLI) for messaging services
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.311/29311-i00.zip
|
The present document specifies the protocol details of service level interworking between Instant Message (OMA-TS-SIMPLE_IM [4]) or Chat Session (OMA-TS-CPM_Conv_Fnct [17]) using the 3GPP IP Multimedia CN subsystem and the Short Message Service over both legacy CS/PS network as specified in the 3GPP TS 23.040 [2] and a generic IP Conectivity Access Network (IP-CAN) as specified in the 3GPP TS 24.341 [5]. These include:
- Procedures to implement service level interworking between IM and SM;
- Procedures to implement service level interworking between CPM and SM;
- Enhancement of the IP-SM-GW as an Application Server to support service selection, authorization and mapping between IM or CPM and SM protocols; and
- Interaction between service level interworking and transport layer interworking.
|
29.329
|
Sh interface based on the Diameter protocol; Protocol details
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.329/29329-i00.zip
|
The present document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on the Diameter base protocol as specified in IETF RFC 6733 [15].
The present document is applicable to:
- The Sh interface between an AS and the HSS.
- The Sh interface between an SCS and the HSS.
Whenever it is possible this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter base protocol as specified in IETF RFC 6733 [15]. Where this is not possible, extensions to the Diameter base protocol as specified in IETF RFC 6733 [15] are defined within this document.
|
29.330
|
IP Multimedia Subsystem (IMS); Sc Interface based on the Diameter protocol;
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.330/29330-i10.zip
|
The present document describes the diameter-based Sc interface between Data Channel Signalling Function (DCSF) and Home Subscriber Server (HSS) and specifies:
1. The interactions between the Data Channel Signalling Function (DCSF) and Home Subscriber Server (HSS) at the Sc reference point, including the procedures and signalling flows.
2. The protocol specifications and implementations, including the diameter application, commands and message contents at the Sc reference point.
The IP Multimedia Subsystem (IMS) supporting DC architecture and procedures are specified in 3GPP TS 23.228 [2].
Whenever it is possible this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter base protocol as specified in IETF RFC 6733 [3]. Where this is not possible, extensions to the Diameter base protocol as specified in IETF RFC 6733 [3] are defined within this document.
|
29.332
|
Media Gateway Control Function (MGCF) - IM Media Gateway; Mn interface
|
TS
|
18.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.332/29332-i20.zip
|
The present document describes the protocol to be used on the Media Gateway Control Function (MGCF) – IM Media Gateway (IM-MGW) interface. This interface provides the Media Gateway Control for interworking between the IP Multimedia Subsystem (IMS) and CS domain (ISUP, BICC and SIP-I). The basis for this protocol is the H.248 protocol as specified in ITU-T. The IMS architecture is described in 3GPP TS 23.228 [1]. The interaction of the MGCF-IM MGW interface signalling procedures in relation to the SIP, and BICC/ISUP signalling at the MGCF are described in 3GPP TS 29.163[4].
The interaction of the MGCF-IM MGW interface signalling procedures in relation to the IMS SIP and SIP-I on Nc at the MGCF are described in 3GPP TS 29.235[47].
This specification describes the application of H.248 on the Mn interface. Required extensions use the H.248 standard extension mechanism. In addition certain aspects of the base protocol H.248 are not needed for this interface and thus excluded by this profile.
In addition this profile provides support for PSTN/ISDN Emulation as required by ETSI TISPAN.
The specification contains a normative Annex defining the H.248.1 Profile in accordance with ITU-T recommendations for H.248.1 applications. Where there exists any contradiction between the normative Annex A and the rest of the specification, the Nornative Annex shall take precidence. The main body of the specification provides an introduction to the use of the profile for the Mn interface and introduces any specific functionality (e.g. new packages) associated to the Mn.
|
29.333
|
Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface; Stage 3
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.333/29333-i10.zip
|
The present document describes the protocol to be used on the Multimedia Resource Function Controller (MRFC) – Multimedia Resource Function Processor (MRFP) interface (Mp interface). The IMS architecture is described in 3GPP TS 23.228 [1], the functional requirements are described in 3G TS 23.333 [25]
This specification defines a profile of the Gateway Control Protocol (H.248.1), for controlling Multimedia Resource Function Processor supporting in-band user interaction, conferencing and transcoding for multimedia-services.
The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 7 and later.
|
29.334
|
IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.334/29334-i10.zip
|
The present document describes the protocol to be used on the IMS Application Level Gateway (ALG) – IMS Access Gateway (IMS-AGW) interface. The basis for this protocol is the H.248 protocol as specified in ITU-T. The IMS architecture is described in 3GPP TS 23.228 [2]. The underlying reference model and stage 2 information is described in Annex G of 3GPP TS 23.228 [2] and in 3GPP TS 23.334 [23].
This specification describes the application of H.248 on the Iq interface (see Figure 1). Required extensions use the H.248 standard extension mechanism. In addition certain aspects of the base protocol H.248 are not needed for this interface and thus excluded by this profile.
Figure 1: Reference model for IMS access
The reference model for the IMS-ALG and the IMS-AGW supporting the ATCF/ATGW function is shown in Figure 1a below.
Figure 1a: Reference model for IMS-ALG/IMS-AGW with ATCF/ATGW function
See 3GPP TS 23.237 [38] clause 5.2 for a comprehensive description of the reference model.
The reference model for the P-CSCF enhanced for WebRTC (eP-CSCF) and the IMS-AGW enhanced for WebRTC (eIMS-AGW) to support WebRTC client access to IMS is shown in Figure 1b as below, see 3GPP TS 23.228 [2] Annex U for a comprehensive description of the reference model.
Figure 1b: Reference Architecture for eP-CSCF/eIMS-AGW supporting WebRTC access to IMS
NOTE: The presence of dashed elements in the figure depends on the configuration.
PCC functional elements are present only for EPC access with QoS.
The corresponding PCC elements for fixed access are also optionally supported but not shown.
The NAT in figure 1b is meant for non-cellular access to IMS.
|
29.335
|
User Data Convergence (UDC); User data repository access protocol over the Ud interface; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.335/29335-i00.zip
|
The present document specifies the stage 3 of the Ud interface between the Front-Ends (FEs) and the User Data Repository (UDR) in the User Data Convergence (UDC architecture).
This 3GPP Technical Specification (TS) specifies the protocol and interactions between the FE and the UDR for Ud reference point, in particular:
- The details of the LDAP protocol that are to be considered
- The details of the SOAP envelope that provide support for subscriptions to notifications and notifications about data changes service (S/N operations).
The User Data Convergence Stage 2 description (architecture and information flows) is specified in 3GPP TS 23.335 [10].
The UDR data model used with LDAP (i.e. attributes, object classes and directory information tree) is implementation specific and is left outside the scope of 3GPP specifications. For multivendor interoperability between FEs and UDR specific integration projects are needed. Some examples of Ud data models are described in 3GPP TR 29.935 [19].
|
29.337
|
Diameter-based T4 Interface for communications with packet data networks and applications
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.337/29337-i00.zip
|
The present document describes the Diameter based interface between the Machine Type Communications-InterWorking Function (MTC-IWF) and the Short Message Service-Service Centre (SMS-SC) for communications with packet data networks and applications.
This specification defines the Diameter application for the T4 reference point between the MTC-IWF and the SMS-SC. The interactions between the MTC-IWF and the SMS-SC are specified.
MTC-IWF and SMS-SC (SMS-IWMSC) may also support the Diameter application for the SGd reference point to exchange SGd-OFR and SGd-OFA commands via T4. The stage 3 description for the SGd Diameter application is specified in 3GPP TS 29.338 [13].
The stage 2 description for communications with packet data networks and applications (architecture and functionality) is specified in the 3GPP TS 23.682 [2].
|
29.343
|
Proximity-services (ProSe) function to ProSe application server aspects (PC2); Stage 3
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.343/29343-i00.zip
|
This document provides the stage 3 specification of the PC2 reference point. The functional requirements and the stage 2 procedures of the PC2 reference point are contained in 3GPP TS 23.303 [2]. The PC2 reference point lies between the ProSe Function and ProSe Application Server.
|
29.344
|
Proximity-services (ProSe) function to Home Subscriber Server (HSS) aspects; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.344/29344-i00.zip
|
The present document describes the Diameter-based PC4a interface between the Proximity-based Services (ProSe) Function and the Home Subscriber Server (HSS) defined for ProSe.
This specification defines the Diameter application for PC4a reference point between the ProSe Function and the HSS.The interactions between the ProSe Function and the HSS are specified.
The stage 2 description for Proximity-based Services (ProSe) features in EPS is specified in 3GPP TS 23.303 [2].
|
29.345
|
Inter-Proximity-services (Prose) function signalling aspects; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.345/29345-i00.zip
|
The present document describes the Diameter-based interfaces between the Proximity Services (ProSe) Function in the HPLMN and the ProSe Function in a local PLMN (PC6 interface) or between the Proximity Services (ProSe) Function in the HPLMN and the ProSe Function in a visited PLMN (PC7 interface).
This specification defines the Diameter application for PC6/PC7 reference points between the ProSe Functions. The interactions between the ProSe Functions are specified.
The stage 2 description for Proximity Services (ProSe) features in EPS is specified in 3GPP TS 23.303 [2].
|
29.368
|
Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.368/29368-i00.zip
|
The present document provides the stage 3 specification of the Tsp reference point for the present release. The functional requirements and the stage 2 specifications of the Tsp reference point are contained in TS 23.682 [2]. The Tsp reference point lies between the Service Capability Server (SCS) and the Machine Type Communication Inter Working Function (MTC-IWF).
|
29.380
|
Mission Critical Push To Talk (MCPTT) media plane control interworking with Land Mobile Radio (LMR) systems; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.380/29380-i00.zip
|
The present document specifies the media plane control protocols and interactions with the media needed to support a Mission Critical Push To Talk (MCPTT) system interworking with a Land Mobile Radio (LMR) system. This interworking includes both the signalling and the media planes between the MCPTT system and the LMR system. The function between the MCPTT system and the LMR system is referred to as an Interworking Function (IWF).
The IWF supports the basic group and other features as specified in 3GPP TS 23.283 [24].
|
29.388
|
V2X Control Function to Home Subscriber Server (HSS) aspects (V4); Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.388/29388-i00.zip
|
The present document describes the Diameter-based V4 interface between the V2X Control Function and the Home Subscriber Server (HSS) defined for V2X services.
This specification defines the Diameter application for V4 reference point between the V2X Control Function and the HSS. The interactions between the V2X Control Function and the HSS are specified.
The stage 2 description for V2X service features in EPS is specified in 3GPP TS 23.285 [2].
|
29.389
|
Inter-V2X Control Function Signalling aspects (V6); Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.389/29389-i00.zip
|
The present document describes the Diameter-based interfaces between the V2X Control Function in the HPLMN and the V2X Control Function in the VPLMN (V6 interface).
This specification defines the Diameter application for V6 reference points between the V2X Control Functions. The interactions between the V2X Control Functions are specified.
The stage 2 description for V2X service features in EPS is specified in 3GPP TS 23.285 [2].
|
29.405
|
Nq and Nq' Application Protocol (Nq-AP); Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.405/29405-i00.zip
|
The present document specifies the procedures and the Nq and Nq' Application Protocol (Nq-AP) messages used on the Nq/Nq' interfaces between the RAN Congestion Awareness Function (RCAF) and the Mobility Management Entity (MME) or the Serving GPRS Support Node (SGSN). The related stage 2 requirements are specified in 3GPP TS 23.401 [2] and 3GPP TS 23.060 [3].
|
29.413
|
Application of the NG Application Protocol (NGAP) to non-3GPP access
|
TS
|
18.5.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.413/29413-i50.zip
|
The present document describes the applicability of NG Application Protocol (NGAP) messages and procedures, defined in 3GPP TS 38.413 [2], to non-3GPP access. A general description for non-3GPP access can be found in 3GPP TS 23.501 [3], 3GPP TS 23.502 [4], and 3GPP TS 23.316 [6].
|
29.414
|
Core network Nb data transport and transport signalling
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.414/29414-i00.zip
|
The present document specifies the bearer data transport and bearer control protocols used between MGWs within the CS core network across the Nb Interface. The present document assumes that the implementation of the split of the call control and the bearer transport and control, as specified in 3GPP TS 23.205 [1] with BICC-based Nc, and in 3GPP TS 23.231 [30] with SIP-I based Nc,, see figure 1. For BICC-based Nc, the User Plane protocol that uses this bearer data transport (Nb UP) is described in 3GPP TS 29.415 [3]. The transport format for the Nb interface with IP transport can optionally allow RTP multiplexing. Note that the present document does not preclude an implementation of a combined MSC Server and MGW.
Figure 1: CS core network logical architecture
|
29.415
|
Core network Nb interface user plane protocols
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.415/29415-i00.zip
|
The present document specifies the user plane protocol of the bearer used between two MGWs within the BICC-based CS core network, called the Nb UP protocol. The present document assumes the implementation of the split between call control and the bearer transport and control, as specified in 3GPP TS 23.205 [1], see figure 1. Note that the present document does not preclude an implementation of a combined MSC Server and MGW.
Figure 1: CS core network logical architecture
|
29.468
|
Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.468/29468-i00.zip
|
This document defines the protocol for the MB2 reference point between the Group Communication Service Application Server (GCS AS) and the Broadcast-Multicast Service Centre (BM-SC).
The MB2 reference point and related stage 2 procedures are defined in TS 23.468 [4] as part of the Group Communication System Enablers for LTE. The stage 1 requirements for Group Communication System Enablers are specified in TS 22.468 [2].
|
29.511
|
5G System; Equipment Identity Register Services; Stage 3
|
TS
|
18.3.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.511/29511-i30.zip
|
The present document describes the stage 3 protocol and data model for the N5g-eir Service Based Interface between the 5G-EIR and its consumers over which the service to check the equipment identity as described in 3GPP TS 23.501 [2] is performed. It provides the stage 3 protocol definitions and message flows, and specifies the API for each service offered by the 5G-EIR.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
|
29.524
|
5G System; Cause codes mapping between 5GC interfaces; Stage 3
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.524/29524-i10.zip
|
The present document specifies the mapping:
- performed by the AMF between HTTP responses (Status Codes and Protocol or Application Errors) returned by 5GC NFs to the AMF and 5GMM Cause values sent to UEs;
- performed by the SMF between HTTP responses (Status Codes and Protocol or Application Errors) returned by 5GC NFs to SMF and 5GSM Cause values sent to UEs;
- performed by the SMF between N4 errors returned by the UPF and 5GSM Cause values sent to UEs.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.