3GPP IMS and UMTS Specifications -- 29 Series:
Signalling Protocols - Stage 3 - intra-fixed-network
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.002 |
CT3 |
|
Mobile Application Part (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 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.
|
|
|
| |
| Up |
Rapporteur: Ulrich Wiehe |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Toshiyuki Tamura |
|
|
|
|
|
|
|
|
| | |
|
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.
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.
|
|
|
| |
| Up |
Rapporteur: Ragnar Huslende |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.078 |
CT4 |
|
CAMEL Phase 4 -
CAMEL Application Part (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.
|
|
|
| |
| Up |
Rapporteur: Phil Hodges |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.109 |
CT4 |
|
GAA - Zh and Zn Interfaces based on the Diameter protocol - Stage 3 |
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 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).
|
|
|
| |
| Up |
Rapporteur: Pekka Laitinen |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Juha Rasanen |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: Nigel Holland |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: Thomas Belling |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: Thomas Belling |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.202 |
CT4 |
|
SS7 Signalling Transport in Core Network - Stage 3 |
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.
|
|
|
| |
| Up |
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.
|
|
|
| |
| Up |
Rapporteur: Ulrich Wiehe |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
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.
|
|
|
|
| |
| Up |
Rapporteur: Juha Rasanen |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.208 |
CT3 |
|
End-to-end Quality of Service (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.
|
|
|
| |
| Up |
Rapporteur: Thomas Belling |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: J. Javier Pastor |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: Juha Rasanen |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: J. Javier Pastor |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: Thomas Belling |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: J. Javier Pastor |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: J. Javier Pastor |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.228 |
CT4 |
|
IP Multimedia (IM) Subsystem Cx and Dx Interfaces -
Signalling Flows and Message Contents |
This TS specifies:
|
| (1) |
The interactions between the HSS (Home Subscriber Server) and the CSCF (Call Session Control Functions),
referred to as the Cx interface;
| |
| (2) |
The interactions between the CSCF and the SLF (Server Locator Function), referred to as the Dx interface.
|
The user profile, including the IFC (initial filter criteria), are defined in annex of this document. It is formally defined using UML and XML, but it is represented hereunder in the following figure (in dotted lines, the optional elements).
|
|
|
| |
| Up |
Rapporteur: German Blanco |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: German Blanco |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Kalle Tammi |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.232 |
CT4 |
|
Media Gateway Controller (MGC) - Media Gateway (MGW) interface - Stage 3 |
|
This TS 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 protocol as specified in ITU-T. The BICC architecture
as described in
3GPP TS 23.205
and
3GPP TS 29.205
defines the usage of this protocol.
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.
|
|
|
| |
| Up |
Rapporteur: Ian David Chalmers Park |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.234 |
CT4 |
|
3GPP System to WLAN
Interworking -
Stage 3 |
This TS defines the stage-3 protocol description for several reference points in the WLAN-3GPP
Interworking System.
The present document is applicable to:
|
| - |
The Dw reference point between the 3GPP AAA Server and an SLF.
| |
| - |
The Wa reference point between the WLAN AN and the 3GPP AAA Proxy.
| |
| - |
The Wd reference point between the 3GPP AAA Proxy and 3GPP AAA Server.
| |
| - |
The Wx reference point between the 3GPP AAA Server and the HSS.
| |
| - |
The Wm reference point between the 3GPP AAA Server and the PDG.
| |
| - |
The Wg reference point between the 3GPP AAA Server/Proxy and the WAG.
| |
| - |
The Pr reference point between the 3GPP AAA Server and the PNA.
|
|
|
|
| |
| Up |
Rapporteur: Paul Sitch |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Nigel. H Berry |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.328 |
CT4 |
|
IP Multimedia (IM) Subsystem Sh Interface -
Signalling Flows and Message Contents |
This TS specifies:
|
| 1. |
The interactions between the HSS (Home Subscriber Server) and the SIP AS (Application Server) and
between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh
reference point.
| |
| 2. |
The interactions between the SIP AS and the SLF (Subscription Locator Function) and between the OSA SCS
and the SLF. This interface is referred to as the Dh reference point.
|
|
|
|
| |
| Up |
Rapporteur: Nigel. H Berry |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Nigel. H Berry |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.332 |
CT4 |
|
Media Gateway Control Function (MGCF) - IM Media Gateway -
Mn Interface |
|
This TS 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.
The present document is valid for a third generation PLMN (UMTS) complying with Release 6 and later.
|
|
|
| |
| Up |
Rapporteur: Peter Schmitt |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Phil Hodges |
|
|
|
|
|
|
|
|
|
|
