focus on internet & telecom standardization topics

hist. pages: SIP/IMS, SEC...
  Home Search
Organizations
# IETF   # 3GPP   # ETSI
# Alliances, Fora, & other SDOs
Standardization work
# IETF WGs: RFCs   # RFC index
# 3GPP Specifications  
# ETSI TISPAN NGN   # ETSI SCP
  # 3GPP
Prev Next 21.xxx  22.xxx  23.xxx  24.xxx  25.xxx  26.xxx  27.xxx  28.xxx  29.xxx  29.198.xx  29.199.xx
Index Table 31.xxx 32.1xx 32.2xx 32.3xx 32.4xx 32.5xx 32.6xx 32.7xx 33.xxx 34.xxx 35.xxx
Top 36.xxx 37.xxx - - - - - - - - -
41.xxx 42.xxx 43.xxx 44.xxx 45.xxx 46.xxx 48.xxx 49.xxx 51.xxx 52.xxx 55.xxx
01.xxx 02.xxx 03.xxx 04.xxx 05.xxx 06.xxx 07.xxx 08.xxx 09.xxx 11.xxx 12.xxx

3GPP Specifications -- 29 Series
Signalling Protocols - Stage 3 - intra-fixed-network

List elaborated from: http://www.3gpp.org/ftp/Specs/html-info/29-series.htm
Last update: July 6, 2010. Each line is a link to the TS (or TR) description, which points to the "3GPP specification detail" page that gives access to MS Word versions (as zip files, possibly including associated files) as well as pdf versions.
WG3GPP Releases
 TS 29.002 ct4 34567 89 MAP - Mobile Application Part
 TS 29.007 ct3 34567 89 General requirements on interworking between the PLMN and the ISDN or PSTN
 TS 29.010 ct4 34567 89 Information element mapping between MS-BSS and BSS-MSC
 TS 29.011 ct4 34567 89 Signalling Interworking for supplementary services
 TS 29.013 ct4 34567 89 Signalling interworking between ISDN supplementary services ASE and MAP protocols
 TS 29.016 ct1 34567 89 SGSN-VLR - Gs interface network service specification
 TS 29.018 ct4 34567 89 SGSN-VLR - Gs interface layer 3 specification
 TS 29.060 ct4 34567 89 GTP across the Gn and Gp interface
 TS 29.061 ct3 34567 89 Interworking between the PLMN supporting Packet-based Services and PDNs
 TS 29.078 ct4 34567 89 CAMEL Phase X - CAP specification
 TS 29.108 ran3 34567 89 Application of RANAP on the E-interface
 TS 29.109 ct4 67 89 GAA - Zh and Zn interfaces based on Diameter
 TS 29.118 ct1 89A MME-VLR SGs interface specification
 TS 29.119 ct4 34567 89 GTP specification for GLR
 TS 29.120 ct4 34567 89 MAP specification for GLR
 TS 29.140 ct4 6 MMS - MM10 interface based on Diameter protocol
 TS 29.161 ct3 67 89 Interworking between PLMN supporting packet based Services with WLAN and PDNs
 TS 29.162 ct3 67 89 Interworking between the IM CN Subsystem and IP Networks
 TS 29.163 ct3 67 89 Interworking between the IMS and CS Networks
 TS 29.164 ct3 7 89 Interworking between 3GPP CS Domain with BICC/ISUP and external SIP-I Networks
 TS 29.165 ct3 89A Inter-IMS Network to Network Interface (NNI)
 TS 29.168 ct3 89 Cell Broadcast Centre interfaces with the Evolved Packet Core
 TS 29.171 ct4 9A LCS-AP between MME and E-SMLC - SLs interface
 TS 29.172 ct4 9 EPC LCS Protocol ELP between GMLC and MME - SLg interface
 TS 29.173 ct4 9 Diameter-based SLh interface for Control Plane LCS
 TS 29.198 ct 3 OSA API
 TS 29.202 ct4 4567 89 SS7 Signalling Transport in Core Network
 TS 29.204 ct4 7 89 SS7 Security Gateway - Architecture, Functional Description and Protocol Details
 TS 29.205 ct4 4567 89 Application of Q.1900 series to bearer independent CS core network architecture
 TS 29.207 ct3 56 Policy Control over Go interface
 TS 29.208 ct3 56 End-to-End QoS signalling flows
 TS 29.209 ct3 6 Policy control over Gq interface
 TS 29.210 ct3 6 Charging Rule Provisioning over Gx interface
 TS 29.211 ct3 6 Rx interface and Rx/Gx signalling flows
 TS 29.212 ct3 7 89 Policy and Charging Control over Gx reference point
 TS 29.213 ct3 7 89 Policy and Charging Control signalling flows and QoS parameter mapping
 TS 29.214 ct3 7 89 Policy and Charging Control over Rx reference point
 TS 29.215 ct3 89 Policy and Charging Control over S9 reference point
 TS 29.228 ct4 567 89 Cx and Dx interfaces - Signalling flows and message contents
 TS 29.229 ct4 567 89 Cx and Dx interfaces - Diameter protocol details
 TS 29.230 ct4 67 89 Diameter applications - 3GPP specific codes and identifiers
 TS 29.231 ct4 89 Application of SIP-I Protocols to CS core network architecture
 TS 29.232 ct4 4567 89 MGC-MGW interface
 TS 29.234 ct4 67 89 I-WLAN - 3GPP System to WLAN Interworking
 TS 29.235 ct3 89 Interworking between SIP-I based CS core network and other networks
 TS 29.238 ct4 9 IBCF-TrGW Ix interface
 TS 29.240 ct4 67 89 GUP - Generic User Profile
 TS 29.272 ct4 89 MME and SGSN related interfaces based on Diameter protocol
 TS 29.273 ct4 89 3GPP EPS AAA interfaces
 TS 29.274 ct4 89 Evolved GPRS Tunnelling Protocol (eGTP) for EPS
 TS 29.275 ct4 89 Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols
 TS 29.276 ct4 89 Optimized Handover Procedures & Protocols between E-UTRAN & cdma2000 HRPD
 TS 29.277 ct4 89 Optimized Handover Procedures & Protocols between E-UTRAN & 1xRTT
 TS 29.278 ct4 567 89 CAMEL Phase 4 - CAMEL Application Part (CAP) specification for IMS
 TS 29.279 ct4 89 Mobile IPv4 (MIPv4) based Mobility protocols
 TS 29.280 ct4 89 3GPP EPS Sv interface (MME to MSC) for SRVCC
 TS 29.281 ct4 89 GPRS Tunnelling Protocol for User Plane (GTPv1-U)
 TS 29.282 ct4 89 Mobile IPv6 vendor specific option format and usage within 3GPP
 TS 29.292 ct3 89 ICS - Interworking between IMS and MSC Server
 TS 29.303 ct4 89 DNS procedures for EPS
 TS 29.305 ct4 89 InterWorking Function (IWF) between MAP based and Diameter based interfaces
 TS 29.311 ct4 89A Service Level Interworking for Messaging Services
 TS 29.328 ct4 567 89 Sh interface - Signalling flows and message contents
 TS 29.329 ct4 567 89 Sh interface - Diameter protocol details
 TS 29.332 ct4 67 89 MGCF-(IM)MGW - Mn interface
 TS 29.333 ct4 7 89 MRFC-MRFP Mp interface
 TS 29.334 ct4 9 IMS ALGCF - IMS Access Media Gateway (IMA-MGW) - Iq Interface
 TS 29.335 ct4 9 User Data Convergence (UDC) - User data repository access protocol over the Ud interface
 TS 29.364 ct3 89 IMS Application Server Service Data Descriptions for AS interoperability
 TS 29.414 ct3 4567 89 Core network Nb data transport and transport signalling
 TS 29.415 ct3 4567 89 Core network Nb interface user plane protocols
 TR 29.800 ct4 7 SS7 Security Gateway - Architecture, functional description and protocol details
 TR 29.801 ct4 7 Feasibility study of using M2PA in 3GPP networks
 TR 29.802 ct4 7 (G)MSC-S - (G)MSC-S Nc interface based on the SIP-I protocol
 TR 29.804 ct3 8 3GPP System Architecture Evolution (SAE): CT WG3 aspects
 TR 29.805 ct4 8 InterWorking Function (IWF) between MAP based and Diameter based interfaces
 TR 29.814 ct3 7 Bandwidth saving at Nb interface with IP transport
 TR 29.846 ct1 6 MBMS - CN1 procedure description
 TR 29.847 ct1 6 Conferencing based on SIP, SDP, and other protocols
 TR 29.863 ct3 7 8 Feasibility Study for the multimedia inter-working between the IMS and CS networks
 TR 29.864 ct4 8 Study on IMS Application Server (AS) service data descriptions for AS interoperability
 TR 29.865 ct3 8 Inter-IMS network to network interface
 TR 29.882 ct4 8 Customized Alerting Tone (CAT) in 3G CS domain
 TR 29.903 ct4 56 Feasibility Study on SS7 signalling transport in the core network with SUA layer
 TR 29.909 ct3 89 Diameter-based protocols usage and recommendations in 3GPP
 TR 29.962 ct3 6 Signalling interworking between the 3GPP profile of the SIP and non-3GPP SIP usage
 TR 29.994 ct1 34567 89 Recommended infrastructure measures to overcome specific MS and UE faults
TISPANETSI
 TS 29.412 ct3 7 8 Trunking Gateway Control Procedures ES 283 012
 TS 29.612 ct3 7 " "
 TS 29.421 ct3 7 8 Endorsement of 3GPP TS 29.162 TS 183 021
 TS 29.424 ct4 7 8 H.248 Profile for controlling Trunking Media Gateways ES 283 024
 TS 29.624 ct3 7 " "
 TS 29.427 ct3 7 Endorsement of 3GPP TS 29.163 ES 283 027
 TS 29.527 ct3 8 " "
 TS 29.433 ct4 7 8 Endorsement of 3GPP TS 29.228 and 29.229 TS 183 033
 TS 29.458 ct3 89 SIP Transfer of IP Multimedia Service Tariff Information TS 183 058
 TS 29.658 ct3 89 " "
3GPP TS 29.002 ct4
MAP specification
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.

This TS 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 (Mobile Application Part) consists of a set of MAP services that are provided to MAP service-users by a MAP service-provider. 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.
V3.20  V4.18  V5.13  V6.17  V7.15  V8.14  V9.2  -  -  -
List  Index Rapporteur: Ulrich Wiehe
GSM antecedent(s): TS 09.02
3GPP TS 29.007 ct3
General requirements on interworking between the PLMN and the ISDN or PSTN
This TS 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.
V3.15  V4.14  V5.14  V6.4  V7.4  V8.1  V9.0  -  -  -
List  Index Rapporteur: Thomas Belling
GSM antecedent(s): TS 09.07
3GPP TS 29.010 ct4
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)
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) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002) 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 (TS 48.008) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002) 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 (TS 48.008) and RANAP (3GPP TS 25.413)
iv) to provide a detailed specification for the interworking as in i) and ii) above when the MSC also processes the information.

Interworking for supplementary services is given in 3GPP TS 29.011. Interworking for the short message service is given in 3GPP TS 23.040 and 3GPP TS 24.011. Interworking between the call control signalling of 3GPP TS 24.008 and the PSTN/ISDN is given in TS 09.03, 3GPP TS 29.007 and TS 49.008. Interworking between the 'A' and 'E' interfaces for inter-MSC handover signalling is given in 3GPP TS 29.007 and TS 49.008.

V3.12  V4.8  V5.7  V6.9  V7.1  V8.2  V9.1  -  -  -
List  Index Rapporteur: Peter Schmitt
GSM antecedent(s): TS 09.10
3GPP TS 29.011 ct4
Signalling Interworking for supplementary services
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.
V3.0  V4.0  V5.0  V6.0  V7.0  V8.0  V9.0  -  -  -
List  Index Rapporteur: Ulrich Wiehe
GSM antecedent(s): TS 09.11
3GPP TS 29.013 ct4
Signalling interworking between ISDN supplementary services Application Service Element (ASE) and MAP protocols
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 3GPP TS 29.002. 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 3GPP TS 23.093. This specification clarifies the interworking within the HLR between these protocols for the Call Completion to Busy Subscriber (CCBS) service.
V3.1  V4.1  V5.1  V6.1  V7.1  V8.1  V9.0  -  -  -
List  Index Rapporteur: Ulrich Wiehe
GSM antecedent(s): TS 09.13
3GPP TS 29.016 ct1
SGSN-VLR - Gs interface network service specification
This TS 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.
V3.1  V4.1  V5.0  V6.0  V7.0  V8.0  V9.0  -  -  -
List  Index Rapporteur: Peter Dawes
GSM antecedent(s): TS 09.16
3GPP TS 29.018 ct4
SGSN-VLR - Gs interface layer 3 specification
This TS 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. The required procedures between VLR and SGSN are defined in detail in the present document.
V3.11  V4.5  V5.5  V6.5  V7.3  V8.2  V9.0  -  -  -
List  Index Rapporteur: Peter Dawes
GSM antecedent(s): TS 09.18
3GPP TS 29.060 ct4
GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface
This TS 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.

From release 8 onwards, the normative specification of the user plane of GTP version 1 is 3GPP TS 29.281. All provisions about GTPv1 user plane in the present document shall be superseded by 3GPP TS 29.281.
V3.19  V4.11  V5.14  V6.21  V7.15  V8.11  V9.3  -  -  -
List  Index Rapporteur: Toshiyuki Tamura
GSM antecedent(s): TS 09.60
3GPP TS 29.061 ct3
Interworking between the Public Land Mobile Network (PLMN) supporting Packet based Services and Packet Data Networks (PDN)
This TS defines the requirements for Packet Domain interworking between a:
a) PLMN and PDN;
b) PLMN and PLMN.

The present document is valid for a PLMN in A/Gb mode as well as for a PLMN 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". Please note, that the A interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.

For inter-working between EPC PLMN and external networks, the present document is valid for both 3GPP accesses and non-3GPP accesses.

The present document also defines, in clause 17, the protocol for the Gmb interface, and in clause 19, the protocol for the Mz interface. It also defines, in clause 18, the usage of Radius at the Pk Reference Point between the GGSN and the Presence Network Agent.

The term 'Packet Domain' includes both EPC based and non-EPC based Packet Domains.
V3.14  V4.10  V5.9  V6.15  V7.12  V8.6  V9.3  -  -  -
List  Index Rapporteur: Ragnar Huslende
GSM antecedent(s): TS 09.61
3G descendant(s): TS 29.161
3GPP TS 29.078 ct4
CAMEL Phase 4 - CAP specification
This TS 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. Descriptions and definitions provided by ETSI EN 301 140-1 are directly referenced by this standard in the case no additions or clarifications are needed for the use in the CAP.
V3.16  V4.9  V5.10  V6.6  V7.6  V8.3  V9.2  -  -  -
List  Index Rapporteur: Phil Hodges
GSM antecedent(s): TS 09.78
3GPP TS 29.108 ran3
Application of the Radio Access Network Application Part (RANAP) on the E-interface
This TS describes the subset of Radio Access Network Application Part (RANAP) messages and procedures, defined in 3GPP TS 25.413, which is used on the E-interface. A general description can be found in 3GPP TS 23.002 and 3GPP TS 23.009.

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.
V3.3  V4.4  V5.4  V6.3  V7.1  V8.0  V9.0  -  -  -
List  Index Rapporteur: Alexander Vesely
GSM antecedent(s): TS 09.08
3GPP TS 29.109 ct4
GAA - Zh and Zn Interfaces based on the Diameter protocol
This TS defines the Diameter based implementation for bootstrapping Zh interface (BSF-HSS) and Dz interface (BSF-SLF) for HSS resolution for the BSF, 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.

This TS 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.

This specification is a part of the Generic Authentication Architecture (GAA) specification series. The diameter based implementation 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.

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).
-  -  -  V6.9  V7.12  V8.4  V9.2  -  -  -
List  Index Rapporteur: Pekka Laitinen
see also: 3GPP TS 24.109, 3GPP TS 33.220
3GPP TS 29.118 ct1
Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification
CS Fallback in the Evolved Packet System (EPS) enables the provisioning of CS-domain services (e.g. voice call, Short Message Service (SMS), Location Services (LCS) or supplementary services) by reuse of CS infrastructure when the UE is served by E-UTRAN.

This TS 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.
-  -  -  -  -  V8.6  V9.2  V10.0  -  -
List  Index Rapporteur: Yannick Lair
3GPP TS 29.119 ct4
GTP specification for GLR
This TS describes the signalling requirements and procedures used at network elements related to the GLR (Gateway Location Register) for GTP (GPRS Tunnelling Protocol) 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.
V3.0  V4.0  V5.0  V6.0  V7.0  V8.0  V9.0  -  -  -
List  Index Rapporteur: Shinichiro Aikawa
3GPP TS 29.120 ct4
MAP specification for GLR
This TS describes the signalling requirements and procedures used at network elements related to the GLR (Gateway Location Register) for MAP (Mobile Application Part) 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.
V3.1  V4.0  V5.0  V6.0  V7.0  V8.0  V9.0  -  -  -
List  Index Rapporteur: Kazuo Mitamura
3GPP TS 29.140 ct4
MMS - MM10 interface based on Diameter protocol
This TS defines the procedures and the transport protocol for use in the Multimedia Messaging Service (MMS) based on Diameter. The present document is applicable to the MM10 interface between an MMS Relay/Server and the MSCF.

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. Where this is not possible, extensions to Diameter are defined within this document.
-  -  -  V6.4  -  -  -  -  -  -
List  Index Rapporteur: Yvette Koza
3GPP TS 29.161 ct3
Interworking between the Public Land Mobile Network (PLMN) supporting Packet based Services with WLAN Access and Packet Data Networks (PDN)
This TS defines the requirements for Packet Domain interworking between:
a) a PLMN with WLAN access and a PDN;
b) a PLMN with WLAN access and a PLMN.
-  -  -  V6.3  V7.2  V8.0  V9.0  -  -  -
List  Index Rapporteur: Juha Rasanen
3G antecedent(s): TS 29.061
see also: 3GPP TS 22.234, TS 23.234, TS 24.234, TS 29.234, TS 33.234, TS 32.252
3GPP TS 29.162 ct3
Interworking between the IM CN Subsystem and IP Networks
The IM CN subsystem interworks with the external IP networks through the Mb reference point. This TS details the interworking between the IM CN subsystem and external IP networks for IM service support. It addresses the issues of control plane interworking, user plane interworking and IP version interworking.
-  -  -  V6.2  V7.3  V8.3  V9.5  -  -  -
List  Index Rapporteur: Nigel Holland
3G antecedent(s): TS 29.421
3GPP TS 29.163 ct3
Interworking between the IP Multimedia (IM) Core Network (CN) Subsystem and Circuit Switched (CS) Networks
This TS 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 calls.

This 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 calls.

Other areas addressed encompass the transport protocol and signalling issues for negotiation and mapping of bearer capabilities and QoS information.
-  -  -  V6.12  V7.19  V8.11  V9.2  -  -  -
List  Index Rapporteur: Thomas Belling
3G antecedent(s): TS 29.527
3GPP TS 29.164 ct3
Interworking between the 3GPP CS Domain with BICC or ISUP as Signalling Protocol and external SIP-I Networks
This TS defines interworking procedures between a 3GPP CS domain (see 3GPP TS 23.205) which applies either BICC or ISUP as signalling protocol, and external networks that use SIP-I (see ITU-T Q.1912.5, 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 and ITU-T Q.1912.5, Profile C, as far as possible.
-  -  -  -  V7.0  V8.1  V9.1  -  -  -
List  Index Rapporteur: Thomas Belling
3GPP TS 29.165 ct3
Inter-IMS Network to Network Interface (NNI)
The objective of this document is to address the Inter-IMS Network to Network Interface (II-NNI) consisting of Ici and Izi reference points between IMS networks in order to support end-to-end service interoperability.

The present document will address the issues related to control plane signalling (3GPP usage of SIP and SDP protocols, required SIP headers) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues as transport protocol, media and codecs actually covered in a widespread set of 3GPP specifications. A profiling of the Inter-IMS Network to Network Interface (II-NNI) is also provided.

Charging aspects will be addressed as far as SIP signalling is concerned.
-  -  -  -  -  V8.5  V9.3  V10.0  -  -
List  Index Rapporteur: Antonio Ascolese
3G antecedent(s): TR 29.865
3GPP TS 29.168 ct3
Cell Broadcast Centre interfaces with the Evolved Packet Core
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).

The present document supports the following functions.
  - Warning Message Transmission function in the EPS.
-  -  -  -  -  V8.3  V9.1  -  -  -
List  Index Rapporteur: Julien Laganier
3GPP TS 29.171 ct4
LCS Application Protocol (LCS-AP) between the Mobile Management Entity (MME) and Evolved Serving Mobile Location Centre (E-SMLC) - SLs interface
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.
-  -  -  -  -  -  V9.1  V10.0  -  -
List  Index Rapporteur: Robert Gross
3GPP TS 29.172 ct4
Evolved Packet Core (EPC) LCS Protocol (ELP) between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity (MME) - SLg interface
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. The ELP message set is applicable to the SLg interface between the MME and the GMLC. ELP is developed in accordance to the general principles stated in 3GPP TS 23.271.
-  -  -  -  -  -  V9.1  -  -  -
List  Index Rapporteur: Robert Gross
3GPP TS 29.173 ct4
Diameter-based SLh interface for Control Plane LCS
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.

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 are mapped into the descriptions of the SLh Diameter commands.
-  -  -  -  -  -  V9.0  -  -  -
List  Index Rapporteur: Lionel Morand
3GPP TS 29.198 ct
Open Service Architecture (OSA) Application Programming Interface (API)
This document specifies the stage 3 of the Open Service Architecture (OSA) Application Programming Interface (API). The concepts and the functional architecture of the Open Service Architecture (API) are described by 3GPP TS 23.127.
V3.4  -  -  -  -  -  -  -  -  -
List  Index Rapporteur: Musa Unmehopa
3GPP TS 29.202 ct4
SS7 Signalling Transport in Core Network
The Core Network enables the transport of SS7 signalling protocols between two entities by means of different underlying networks (e.g. MTP-based, IP-based or ATM-based).

The transport of SS7 signalling protocol messages of any protocol layer that is identified by the MTP level 3 layer, in SS7 terms, as a user part (MTP3-user) shall be accomplished in accordance with the protocol architecture defined in the following sub-clauses. The list of these protocol layers includes, but is not limited to, Signalling Connection Control Part (SCCP).

The transport of protocols which can be identified as SCCP-users, like for example TCAP, and in turn the transport of TCAP-users like MAP and CAP, shall also be accomplished in accordance with the defined protocol architectures, since their protocol messages are transferred as SCCP payload.

This TS defines the possible protocol architectures for transport of SS7 signalling protocols in Core Network.
-  V4.3  V5.2  V6.0  V7.0  V8.1  V9.0  -  -  -
List  Index Rapporteur: Phil Hodges
3GPP TS 29.204 ct4
SS7 Security Gateway - Architecture, Functional Description and Protocol Details
The absence of security in Signalling System No. 7 (SS7) networks is an identified security weakness in 2G systems. This was formerly perceived not to be a problem, since the SS7 networks were the provinces of a small number of large institutions. This is no longer the case, and so there is now a need for security precautions.

For 3G systems it is a clear goal to be able to protect inter-network SS7 signalling protocols. The protection is done by security gateways which are located at the network border. As a consequence intra network SS7 signalling is not protected and network elements other than Security Gateways are not impacted.

This TS provides functional description of the SS7 Security Gateway. The document covers also network architecture, routeing considerations, and protocol details.
-  -  -  -  V7.1  V8.0  V9.0  -  -  -
List  Index Rapporteur: Ulrich Wiehe
3G antecedent(s): TR 29.800
3GPP TS 29.205 ct4
Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture
This TS 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. The Q.1902 operates between (G)MSC servers. The BICC architecture as described in ITU-T Q.1902 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 and 3GPP TS 23.153.
-  V4.3  V5.2  V6.1  V7.0  V8.2  V9.1  -  -  -
List  Index Rapporteur: Alf Heidermark
3GPP TS 29.207 ct3
Policy Control over Go Interface
This TS provides the stage 3 specification of the Go interface. The functional requirements and the stage 2 specifications of the Go interface are contained in 3GPP TS 23.002 and 3GPP TS 23.207. The Go interface is the interface between the GGSN and the Policy Decision Function (PDF). The present document defines:
- the protocol to be used between PDF and GGSN over the Go interface;
- the signalling interactions to be performed between PDF and GGSN over the Go interface;
- the information to be exchanged between PDF and GGSN over the Go interface.
-  -  V5.9  V6.5  -  -  -  -  -  -
List  Index Rapporteur: Juha Rasanen
3G descendant(s): TS 29.212
3GPP TS 29.208 ct3
End-to-end QoS Signalling Flows
This TS gives examples of QoS signalling flows for resource reservation to provide end-to-end QoS. The flows are used as bases of developing QoS related protocol descriptions for new and existing specifications. This specification adds detailed flows of Service Based Local Policy (SBLP) procedures over the Go and Gq interfaces and their relationship with the bearer level signalling flows over the Gn interface. The calls flows depicted in this Technical Specification represent usual cases, i.e. not all situations are covered. Detailed information provided in 3GPP TS 29.207 shall be taken into consideration. This specification also describes the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters.
-  -  V5.9  V6.7  -  -  -  -  -  -
List  Index Rapporteur: Thomas Belling
3G descendant(s): TS 29.213
3GPP TS 29.209 ct3
Policy control over Gq Interface
This TS provides the stage 3 specification of the Gq interface. The functional requirements and the stage 2 specifications of the Gq interface are contained in 3GPP TS 23.002 and 3GPP TS 23.207. The Gq interface is used for session based policy set-up information exchange between the Policy Decision Function (PDF) and the Application Function (AF). 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.
-  -  -  V6.7  -  -  -  -  -  -
List  Index Rapporteur: Susana Fernandez
3G descendant(s): TS 29.214
3GPP TS 29.210 ct3
Charging Rule Provisioning over Gx Interface
This TS provides the stage 3 specification of the Gx reference point. The functional requirements and the stage 2 specifications of the Gx reference point are contained in 3GPP TS 23.125. The Gx reference point is for provisioning service data flow based charging rules between the Traffic Plane Function (TPF) and the Charging Rules Function (CRF), also known as Service Data Flow Based Charging Rules Function. The present document defines:
- the protocol to be used between TPF and CRF over the Gx reference point;
- the information to be exchanged between TPF and CRF over the Gx reference point.

Whenever it is possible the present document specifies the requirements for this 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. 3GPP TS 29.211 provides call flows for Flow Based Charging, covering the signalling on the Gx reference point.
-  -  -  V6.7  -  -  -  -  -  -
List  Index Rapporteur: Juha Rasanen
3G descendant(s): TS 29.212
3GPP TS 29.211 ct3
Rx Interface and Rx/Gx Signalling Flows
This TS provides the stage 3 specification of the Rx reference point interface. The functional requirements and the stage 2 specifications of the Rx reference point are contained in 3GPP TS 23.125. The Rx reference point is used to exchange Flow Based Charging information between the Charging Rules Function (CRF) and the Application Function (AF). Whenever it is possible the present document specifies the protocol by reference to specifications produced by the IETF within the scope of Diameter and to the Gq specification 3GPP TS 29.209. The present specification also provides detailed signalling flows for FBC procedures over the interfaces that correspond to Rx and Gx reference points.
-  -  -  V6.4  -  -  -  -  -  -
List  Index Rapporteur: Susana Fernandez
3G descendant(s): TS 29.213,   TS 29.214
3GPP TS 29.212 ct3
Policy and Charging Control over Gx Reference Point
This TS provides the stage 3 specification of the Gx reference point for the present release. The functional requirements and the stage 2 specifications of the Gx refernce point are contained in 3GPP TS 23.203. The Gx reference point lies between the Policy and Charging Rule Function and the Policy and Charging Enforcement 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.
-  -  -  -  V7.12  V8.8  V9.3  -  -  -
List  Index Rapporteur: Thomas Belling
3G antecedent(s): TS 29.207, TS 29.210
3GPP TS 29.213 ct3
Policy and Charging Control Signalling Flows and QoS Parameter Mapping
This TS adds detailed flows of Policy and Charging Control (PCC) over the Rx and Gx reference points and their relationship with the bearer level signalling flows over the Gn interface.

The calls flows depicted in this Technical Specification represent usual cases, i.e. not all situations are covered. Detailed information provided in 3GPP TS 29.212 and 3GPP TS 29.214 shall be taken into consideration. The present specification also describes the binding and the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters.
-  -  -  -  V7.10  V8.8  V9.3  -  -  -
List  Index Rapporteur: Susana Fernandez
3G antecedent(s): TS 29.208, TS 29.211
3GPP TS 29.214 ct3
Policy and Charging Control over Rx Reference Point
This TS provides the stage 3 specification of the Rx reference point for the present release. The functional requirements and the stage 2 specifications of the Rx reference point are contained in 3GPP TS 23.203. The Rx reference point lies between the Application Function and the Policy and Charging Rule 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.
-  -  -  -  V7.10  V8.8  V9.3  -  -  -
List  Index Rapporteur: Susana Fernandez
3G antecedent(s): TS 29.209, TS 29.211
3GPP TS 29.215 ct3
Policy and Charging Control (PCC) over S9 reference point
This TS 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. 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.
-  -  -  -  -  V8.6  V9.3  -  -  -
List  Index Rapporteur: Susana Fernandez
>>> Next Page
  
© 2005-2010 Joël Repiquet, All Rights Reserved.