3GPP Specifications -- 29 Series (page 2 of 2)
|
|
|
|
|
|
- | |
- | |
V5.21 | |
V6.16 | |
V7.13 | |
V8.9 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
V5.13 | |
V6.11 | |
V7.9 | |
V8.10 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
V6.10 | |
V7.14 | |
V8.10 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.231 |
ct4 |
|
Application of SIP-I Protocols to CS core network architecture |
This TS describes the protocols to be used when SIP-I is optionally used as call control protocol in a
3GPP CS (Circuit Switched) core network on Nc interface, see
3GPP TS 23.231. The SIP-I protocol operates between (G)MSC servers.
The SIP-I architecture consists of a number of protocols. The following types of protocols are described: call control
protocol, resource control protocols and user plane protocol for this architecture. The architecture complies with the
requirements imposed by 3GPP TS 23.231 and 3GPP TS 23.153.
Interworking of SIP-I on Nc to external networks is described by TS 29.235.
The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 8 and later.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.4 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.232 |
ct4 |
|
MGC-MGW interface |
|
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.
|
|
|
- | |
V4.17 | |
V5.19 | |
V6.14 | |
V7.11 | |
V8.9 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.234 |
ct4 |
|
3GPP System to WLAN Interworking |
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.
|
|
|
|
- | |
- | |
- | |
V6.15 | |
V7.12 | |
V8.3 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.5 | |
V9.5 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.238 |
ct4 |
|
Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface; Ix interface; Stage 3 |
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. The underlying reference model and stage 2 information is described in Annex I of 3GPP TS 23.228 and in 3GPP TS 29.162. The CS architecture is described in Annex A of 3GPP TS 29.235.
This specification describes the application of H.248 Ix profile for both Ix and CS-Ix interfaces. 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.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.240 |
ct4 |
|
3GPP Generic User Profile (GUP) -
Stage 3 -
Network |
This TS 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.
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.
|
|
|
- | |
- | |
- | |
V6.1 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.272 |
ct4 |
|
MME and SGSN related interfaces based on Diameter protocol |
This TS describes the Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN)
related diameter-based interfaces towards the Home Subscriber Server (HSS), and the MME and the SGSN related
diameter-based interface towards the Equipment Identity Register (EIR).
This specification defines the Diameter application for the MME-HSS, S6a reference point, and for the SGSN-HSS,
S6d reference point. The interactions between the HSS and the MME/SGSN are specified, including the signalling
flows.
This specification defines the Diameter application for the MME-EIR, S13 reference point, and for the SGSN-EIR, S13
reference point. The interactions between the MME/SGSN and the EIR are specified, including the signalling flows.
If there is no specific indication, the SGSN in the specification refers to a S4-SGSN which supports S4 interface.
The Evolved Packet System stage 2 description (architecture and functional solutions) is specified in 3GPP TS 23.401 and in 3GPP TS 23.060.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.7 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.273 |
ct4 |
|
3GPP EPS AAA interfaces |
This TS defines the stage-3 protocol description for several reference points for the non-3GPP access in
EPS.
The present document is applicable to the following reference points:
|
| - |
SWa between an un-trusted non-3GPP IP access and the 3GPP AAA Server/Proxy.
| |
| - |
STa between a trusted non-3GPP IP access and the 3GPP AAA Server/Proxy.
| |
| - |
SWd between the 3GPP AAA Proxy and 3GPP AAA Server.
| |
| - |
SWx between the 3GPP AAA Server and the HSS.
| |
| - |
S6b between the 3GPP AAA Server/Proxy and the PDN GW.
| |
| - |
H2 between the 3GPP AAA Server and the HA.
| |
| - |
SWm between the 3GPP AAA Server/Proxy and the ePDG.
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.5 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.6 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.7 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.276 |
ct4 |
|
Optimized Handover Procedures and Protocols between E-UTRAN Access and cdma2000 HRPD Access |
This TS specifies the stage 3 of the Evolved Packet System S101 interface 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.
It also specifies the S103 interface between the Serving GW and HRPD PDSN. 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.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.6 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.277 |
ct4 |
|
Optimized Handover Procedures and Protocols between E-UTRAN Access and 1xRTT Access |
This TS 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. 1x CS signalling messages are
those messages that are defined for A21 interface as described in 3GPP2 A.S0008-C. 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.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.6 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.278 |
ct4 |
|
CAMEL Phase 4 - CAP specification for IMS |
|
This TS specifies the CAMEL Application Part (CAP) supporting the fourth phase of the network feature
Customized Applications for Mobile network Enhanced Logic (CAMEL) 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.
|
|
|
- | |
- | |
V5.4 | |
V6.1 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.280 |
ct4 |
|
3GPP EPS Sv interface (MME to MSC) for SRVCC |
This TS 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 VoIP/IMS over EPS to CS domain over 3GPP UTRAN/GERAN access or from UTRAN (HSPA) to
3GPP UTRAN/GERAN access.
If there is no specific indication, the term "MSC server" denotes 3GPP MSC server enhanced for SRVCC as defined in
3GPP TS 23.216.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.4 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.281 |
ct4 |
|
GPRS Tunnelling Protocol for User Plane (GTPv1-U) |
This TS defines the user plane 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;
| |
| - |
the S1-U, X2, S4, S5, S8 and S12 interfaces of the Evolved Packet System (EPS);
|
This definition ensures full backwards compatibility with RNC, SGSN and GGSN implementations according to release
7 of 3GPP TS 29.060.
NOTE: Releases previous to Release-8 have used 3GPP TS 29.060 as normative definition of the user plane
of GTP. This shall be considered when essential corrections are included in the present document or in
pre-release-8 version of 3GPP TS 29.060.
Fallback from GTPv1-U to GTPv0-U shall not be supported. Therefore, 3GPP Rel-8 and onwards GTPv1-U entity
should not listen to the well-known GTPv0 port 3386. If GTPv1 entity listens to the GTPv0 port, the entity shall silently
discard any received GTPv0-U message.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.5 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.2 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.292 |
ct3 |
|
ICS - Interworking between IMS and MSC Server |
IMS Centralized Services (ICS) enable the delivery of IM CN subsystem based multimedia telephony and
supplementary services as defined in 3GPP TS 24.173 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 and NAS signalling as
described in 3GPP TS 24.008 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.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.4 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.303 |
ct4 |
|
Domain Name System Procedures |
|
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.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.4 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.305 |
ct4 |
|
InterWorking Function (IWF) between
MAP based and Diameter based interfaces |
The present document is to specify the InterWorking Function (IWF) between MAP-based Gr, Gf interfaces and
Diameter-based S6a, S6d, S13, S13a interfaces.
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.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.3 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.311 |
ct4 |
|
Service Level Interworking for Messaging Services |
The present document specifies the protocol details of service level interworking between Instant Message as specified
in OMA-TS-SIMPLE_IM 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 and a generic IP Connectivity Access Network (IP-CAN)
as specified in the 3GPP TS 24.341. These include:
|
| - |
Procedures to implement service level interworking between IM and SM.
| |
| - |
Enhancement of the IP-SM-GW as an Application Server to support service selection, authorization and
mapping between IM and SM protocols.
| |
| - |
Interaction between service level interworking and transport layer interworking.
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.1 | |
V9.0 | |
V10.1 | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
|
- | |
- | |
V5.16 | |
V6.15 | |
V7.12 | |
V8.9 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
V5.11 | |
V6.7 | |
V7.8 | |
V8.6 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
V6.14 | |
V7.12 | |
V8.8 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.333 |
ct4 |
|
MRFC-MRFP Mp Interface |
This TS
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, the functional requirements are described in
3GPP TS 23.333.
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.
|
|
|
- | |
- | |
- | |
- | |
V7.5 | |
V8.4 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.335 |
ct4 |
|
User Data Convergence (UDC); User data repository access protocol over the Ud interface; Stage 3 |
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.
Details related to the data model used with LDAP (e.g., directory tree) are left outside the scope of this specification.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.364 |
ct3 |
|
IMS Application Server Service Data Descriptions for AS interoperability |
Application Servers can store their service data on the HSS through the Sh interface as transparent data, meaning that
the HSS may not be aware of the structure and the semantics of this data, only the Application Server has this
knowledge. Standardizing the data formats would facilitate interoperation among Application Servers supplied by the
same, or different, vendors. These Application Server vendors may be primary and secondary suppliers of the same
service provider within a service provider"s IMS network. This is especially true for the Multimedia Telephony
supplementary services that can achieve a wide deployment and are here addressed by this specification.
This specification standardizes the structure and the coding of the service data that are transported over the Sh interface
between an Application Server supporting Multimedia Telephony supplementary services as defined in 3GPP TS 22.173
and the HSS. Two optional formats are specified. One is based on a binary coding of the service data and
supports the subset of MMTEL services corresponding to PSTN/ISDN and CS supplementary services. The other uses
an XML format and supports the full set of MMTEL Services.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.3 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.414 |
ct3 |
|
Core network Nb data transport and transport signalling |
|
This TS 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 with BICC-based Nc, and in 3GPP TS 23.231 with SIP-I based Nc. For BICC-based Nc, the User Plane protocol that uses this bearer data
transport (Nb UP) is described in 3GPP TS 29.415. 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.
|
|
|
- | |
V4.5 | |
V5.1 | |
V6.1 | |
V7.3 | |
V8.3 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.415 |
ct3 |
|
Core network Nb interface user plane protocols |
|
This TS 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. Note that the present
document does not preclude an implementation of a combined MSC Server and MGW.
|
|
|
- | |
V4.4 | |
V5.2 | |
V6.1 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.801 |
ct4 |
|
Feasibility study of using M2PA in 3GPP networks |
The present document provides a study into the advantage and disadvantage of M2PA comparing with M3UA and
provides a study into the possibility of introducing M2PA in 3GPP.
The present document also specifies the functionalities required on the protocol level to meet the requirements of BICC,
MAP and CAP.
If necessary, the interactive between M2PA and M3UA should be studied.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.804 |
ct3 |
|
3GPP System Architecture Evolution (SAE): CT WG3 aspects |
The present document discusses and describes procedures and protocols from CT3 aspects of System Architecture
Evolution (SAE) towards a higher-data-rate, lower-latency, packet-optimized system that supports multiple access
technologies.
These CT3 aspects include the PCC enhancements (including impacts coming from the inter-access system handover,
roaming and LBO), the QoS aspects for both 3GPP and non-3GPP networks, inter-working with external networks,
MBMS and any other functions in the Evolved Packet Core (EPC) network that CT3 has impact on.
The present document is used as a placeholder for CT3 SAE materials to be moved to appropriate 3GPP technical
specifications when it is sufficiently stable. As such, neither all the discussions within this document are finished nor
the procedures need to be completed. This TR may also contain some empty clauses. This TR will no longer be updated
on a systematic manner and therefore contained information may become outdated.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.805 |
ct4 |
|
InterWorking Function (IWF) between MAP based and Diameter based interfaces |
The present document is to evaluate the feasibility of introduction of an InterWorking Function (IWF) between MAP-based
and Diameter-based interfaces. This evaluation will be based on the study of various concrete interworking
deployment scenarios for which an IWF can/could be used. For each scenario, it will be analysed how the IWF fulfils
the specific interworking requirements and performs the mapping of procedures and the corresponding parameter
handling.
The present document will study the related mechanism for the interworking scenarios, e.g. addressing. The other
mechanism, such as security, will also be described in this document as a part of the whole solution.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.814 |
ct3 |
|
Bandwidth saving at Nb interface with IP transport |
The present document investigates solutions for a simple, optional transport format for the Nb interface and IP transport
that allows transporting several RTP/NbFP/codec payload PDUs of different user plane connections within one packet.
The solution shall minimise impacts to existing network characteristics, in particular jitter and packet delay. The
transport format shall be suitable for any type of payload transported within NbFP. Though primarily intended and
possibly optimised for NbFP transport within 3GPP circuit-switched core networks, the multiplexing design shall be
generic and future proof by not precluding support of non-NbFP payload types, e.g. standard VoIP bearers or other
interfaces such as Iu.
Furthermore, backward compatible signalling extensions required to negotiate the use of this transport option, to set up
multiplexing connections, and to assign bearers to these connections are investigated.
The benefits and drawbacks of multiplexing at the Nb interface are investigated.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.847 |
ct1 |
|
Conferencing based on SIP, SDP, and other protocols - Functional models, information flows and protocol details |
|
The present document is a temporary container for the functional models, flows and protocol details for the
conferencing service within the IP Multimedia Core Network subsystem (IMS) based on the Session Initiation Protocol
(SIP), SIP Events, the Session Description Protocol (SDP) , the Conference Policy Control Protocol (CPCP) and other
protocols. The document covers also instant messaging conferences. The contents of this report when stable will be
moved into the Technical Specification 3GPP TS 23.218, 3GPP TS 24.228 and 3GPP TS 24.229.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.863 |
ct3 |
|
Feasibility Study for the multimedia inter-working between the IP Multimedia Core Network (CN) Subsystem (IMS) and Circuit Switched (CS) networks |
The present document provides a feasibility study for the interworking of multimedia calls between the IP Multimedia
CN Subsystem and CS networks (i.e. PSTN, ISDN and GSM/UMTS CS networks).
The present document study and outlines different solutions and functionality required within the MGW to deliver the
user plane aspects between IM CN subsystems and CS networks for support of basic multimedia calls. It also outlines
the solutions and functionality required within the MGCF and SGW to deliver the control plane aspects between IM CN
subsystems and CS networks to support basic multimedia calls.
The document also studies the MONA interworking impacts, and which parts of MONA are feasible, or even possible,
to interwork.
The user plane interworking necessary to cover the basic multimedia calls is also outlined and studied.
The different aspects studied for the different scenarios should encompass the transport protocol, transcoding and
signalling issues for negotiation and mapping of bearer capabilities and QoS information.
|
|
|
- | |
- | |
- | |
- | |
V7.2 | |
V8.2 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.864 |
ct4 |
|
Study on IMS Application Server (AS) service data descriptions for AS interoperability |
|
The present document studies requirements for application server service data definition. It also studies the transfer of
the defined service data between an application server and the HSS. Further, it exposes a service data definition for a
telephony application server for services as defined in 3GPP TS 22.173. Finally it provides recommendations for
how the framework can be reused and extended for future IMS service definitions.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.865 |
ct3 |
|
Inter-IMS network to network interface |
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.
Charging aspects will be addressed as far as SIP signalling is concerned.
The purpose of this document is to prepare some material that could be moved to the foreseen Technical Specification
for the profiling of the Inter-IMS Network to Network Interface (II-NNI) and to propose if any needed modifications of
the 3GPP core specifications are required.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.882 |
ct4 |
|
Customized Alerting Tone (CAT) in 3G CS domain |
|
The present document provides a study into providing a Customized Alerting Tones in the 3GPP CS domain. The
document covers the functional description, network architecture and protocol definition to support CAT in the 3GPP
CS domain for speech and multimedia calls.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.903 |
ct4 |
|
Feasibility Study on SS7 signalling transport in the core network with SCCP-User Adaptation (SUA) layer |
The scope of this Technical Report (TR) is to capture the results of a feasibility study on SS7 signalling transport (e.g.
MAP & CAP) in a 3GPP core network with SCCP-User Adaptation (SUA) for Release-5.
With this purpose in mind, this TR evaluates the advantages and disadvantages associated with the implementation of
SUA in the core network, and compares it with the SCCP/M3UA option. Therefore, an overview of M3UA is provided
in this document for reference. This TR covers all scenarios such as SUA peer to peer as well as interworking with
legacy SS7 network, plus the interworking between SUA and SCCP/M3UA. This TR also identifies and studies the
technical issues related to SUA implementation and proposes the possible technical solutions that will enable the effient
implementation of SUA, with minimum impacts on the available services.
More generally, the aim of this TR is to identify and strive to solve all issues introduced by such evolution of the core
network signalling. At the end of the feasibility study, the open issues are reported and their importance is assessed.
Also discussed are the benefits and drawbacks with respect to the introduction of SUA into 3GPP core network
signalling.
|
|
|
- | |
- | |
V5.0 | |
V6.0 | |
- | |
- | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.909 |
ct3 |
|
Diameter-based protocols usage and recommendations in 3GPP |
The present document contains a common set of principles, rules and recommendations across 3GPP WGs to ensure
Diameter-based interfaces have the same treatment for release control and generating new applications-id. Also to
address in a unified manner the use/re-use of AVPs, and other Diameter BASE (see IETF RFC 3588) related
decisions.
The present document covers all aspects of Diameter usage within 3GPP, including description of the current situation
of Diameter usage in different 3GPP WGs (CT3, CT4, SA5) in Release 6/7, describe recommendations and conditions
to re-use existing Diameter applications (3GPP or IETF application-id), commands, AVPs and/or AVP values, describe
recommendations and conditions to define new Diameter applications, commands, AVPs and/or AVP values, and any
other related issues, e.g. the cross-release issue, whether to apply proposed guideline back to existing Diameter
applications or not, or only new SAE Diameter interfaces, etc.
To achieve maximum benefit from this work it is strongly recommended that all 3GPP Diameter-based protocols follow
the recommendations in the present document.
The present document also serves a placeholder for Diameter inter-operator considerations with brief guidelines on how
to deploy & realize the inter-operator Diameter-based roaming infrastructure.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.1 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.962 |
ct3 |
|
Signalling interworking between the 3GPP profile of the SIP and non-3GPP SIP usage |
The present document investigates the SIP signalling interworking between entities of IM CN subsystems behaving as
specified in the 3GPP profile of SIP and SDP in 3GPP TS 24.229, with related call flow examples in
3GPP TS 24.228, and SIP network entities external to the IM CN subsystems, which may not adhere to the 3GPP
profile of SIP and SDP.
The present document assumes that GPRS access and service based local policy using the Go interface is applied.
Non-GPRS access to IMS may have implications on the TR, which are not yet discussed.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 29.994 |
ct1 |
|
Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults |
The present document clarifies recommended measures which may be adopted by 3GPP infrastructure utilising GSM or
GERAN as access network to enable inter-working to be obtained between network and various User Equipment (UE)
implementations of the 3GPP specification. The objective is to obtain compatibility without changing the consolidated
set of specifications. The present document describes the recommended changes to the infrastructure to cater for
specific faults within some types of UE.
The lifetime of the herein described measures together with their potential impact on optimal network performance is
out of the scope of the present document.
|
|
|
V3.0 | |
V4.0 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
V7.0 | |
V8.1 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.421 |
ct3 |
|
TISPAN - NGN Release 1 - Endorsement of 3GPP TS 29.162 Interworking between IM CN Sub-system and IP networks |
This TS describes the interworking between the TISPAN IMS and an external IP network including other
IMS networks for IP multimedia service support.
The present document addresses the areas of control and user plane interworking through the network functions, which
include the IBCF and I-BGF. For the specification of control plane interworking, the interworking between IMS SIP
and an external SIP profile are detailed in terms of the procedures required for the support of both IMS originated and
terminated SIP sessions.
In particular, the present document describes the protocol mappings for support of communications between networks
using different IP versions or between networks with NATs operating at their border.
|
|
|
- | |
- | |
- | |
- | |
V7.0 | |
V8.0 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
V7.0 | |
V8.0 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.427 |
ct3 |
|
TISPAN - Endorsement of the SIP-ISUP Interworking between the IM CN subsystem and CS networks [3GPP TS 29.163 (Release 7), modified] |
This TS provides the ETSI endorsement of the 3GPP TS 29.163 (V7.1.0).
The clauses 7.2.3 and 7.4 of 3GPP TS 29.163 specify the signalling interworking between ISDN User Part (ISUP)
protocols and SIP in order to support services that can be commonly supported by ISUP and SIP-based network
domains.
The clause 9.2.3.3.5 specifies how ringing tone is applied at the gateway when interworking ISUP and SIP.
The present document specifies the principles of interworking between the ETSI TISPAN IMS and ISUP based legacy
CS networks, in order to support IM basic voice calls, therefore all the references to interworking between IMS and
BICC are out of scope of the present document.
The present document is a protocol interworking specification; therefore all references to the user plane interworking
are out of scope of the present document.
The present document specifies the interworking between ETSI SIP profile (as specified within ETSI ES 283 003) and
ISUP, as specified in EN 300 356-1 respectively.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
V7.0 | |
V8.1 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 29.458 |
ct3 |
|
TISPAN - SIP Transfer of IP Multimedia Service Tariff Information - Protocol specification |
This TS specifies the Stage 3 of the real-time transfer of tariff information between a Charge
Determination Point (CDP) and a Charge Generation Point (CGP) by means of the Session Initiation Protocol (SIP).
It identifies the protocol procedures and switching functions needed to support the transfer of tariff information related
to IP multimedia services. The information needed to support the ISDN User part (ISUP) signalling aspects of charging
(ES 201 296) for Advice of Charge information purposes is also specified, however, it can be used for other
purposes as well where applicable.
The present document is applicable to an environment where different operators are working together. It is also
applicable to a single network operator environment.
Whether the present document is applicable to a national environment and/or can be used for inter-network purposes
depends on regulatory demands and/or bilateral agreements. It should be noted that there are network requirements and
signalling limitations that are not covered because they are outside the scope of the present document. Examples of
these are as follows:
|
| - |
the on-line provided advice of charge information may not accurately reflect the correct charging rate due to
discount rates, special charging arrangements, etc. It is out of scope to ensure alignment of this information;
| |
| - |
complaint handling between network operators in case of incorrect advice of charge information;
| |
| - |
explicit encryption or special security mechanisms;
| |
| - |
usage of the transferred tariff information for charging purposes;
| |
| - |
interaction between UE and CGP for possible confirmation of provided tariffs;
| |
| - |
any function behind the CGP towards the UE.
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.4 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
