3GPP Specifications -- 24 Series (page 2 of 2)
|
|
|
|
|
| | |
|
3GPP TS 24.206 |
ct1 |
|
Voice Call Continuity between the
Circuit-Switched (CS) domain and the
IP Multimedia Core Network (CN) (IMS) subsystem
- Stage 3 |
This TS provides the protocol details for voice call continuity between the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP) and the protocols of the 3GPP Circuit-Switched (CS) domain (CAP, MAP, ISUP, BICC and the NAS call control protocol for the CS access).
Voice call continuity allows users to move between the CS domain and the IP Connectivity Access Network (e.g., WLAN interworking) with home IM CN subsystem functionality.
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP, SIP Events and SDP, either directly, or as modified by
3GPP TS 24.229.
Where this is not possible, extensions to SIP are defined within the present document. The document has therefore been structured in order to allow both forms of specification.
The present document is applicable to User Equipment (UEs), Application Servers (AS) and Media Gateway Control Functions (MGCF) providing voice call continuity capabilities.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.216 |
ct1 |
|
Communication Continuity Management Object (MO) |
This TS
defines the Communication Continuity Management Object. The management object is compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA-ERELD _DM-V1_2.
The Communication Continuity Management Object consists of relevant parameters that can be managed for Communication Continuity capabilities.
|
|
|
- | |
- | |
- | |
- | |
V7.4 | |
V8.3 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.229 |
ct1 |
|
IP Multimedia Call Control Protocol based on
SIP and SDP - Stage 3 |
This TS defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem
based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP).
Where possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of SIP and SDP. Where this is not possible, extensions to SIP and SDP are
defined within the present document. The document has therefore been structured in order to allow both forms of
specification.
As the IM CN subsystem is designed to interwork with different IP-Connectivity Access Networks (IP-CANs), the IP-CAN
independent aspects of the IM CN subsystem are described in the main body and annex A of this specification.
Aspects for connecting a UE to the IM CN subsystem through specific types of IP-CANs are documented separately in
the annexes or in separate documents.
|
|
|
- | |
- | |
V5.23 | |
V6.24 | |
V7.20 | |
V8.12 | |
V9.4 | |
V10.0 | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.234 |
ct1 |
|
WLAN User Equipment (WLAN UE) to Network Protocols - Stage 3 |
This TS specifies the network selection, including Authentication and Access Authorization using Authentication,
Authorization and Accounting (AAA) procedures used for the interworking of the 3GPP System and WLANs.
In addition to these, the present document also specifies the Tunnel management procedures used for
establishing an end-to-end tunnel from the WLAN UE to the 3GPP network via the Wu reference point.
The present document is applicable to the WLAN User Equipment (UE) and the network. In this technical
specification the network includes the WLAN and 3GPP network.
Tunnel management signalling is carried between WLAN-UE and WLAN by WLAN Access Technology specific protocols,
however this signalling is transparent to the WLAN.
Tunnel management procedures are defined to be independent of the underlying WLAN access technology and
as such can be reused independently of the underlying technology.
The present document specifies procedures within I-WLAN necessary in order for IMS emergency calls to be supported
when I-WLAN is used as the underlying access network. These involve both network selection as well as tunnel
management procedures.
|
|
|
- | |
- | |
- | |
V6.7 | |
V7.6 | |
V8.3 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.237 |
ct1 |
|
IMS Service Continuity |
IP Multimedia (IM) Core Network (CN) subsystem Service Continuity (SC) provides the capability of continuing
ongoing communication sessions with multiple media across different access networks or across different user
equipments (UEs) under the control of the same subscriber.
The present document provides the protocol details for enabling IMS SC based on the Session Initiation protocol (SIP)
and the Session Description Protocol (SDP) and the protocols of the 3GPP Circuit-Switched (CS) domain (e.g. CAP,
MAP, ISUP, BICC and the NAS call control protocol for the CS access).
The present document is applicable to User Equipment (UEs) and Application Servers (AS) providing IMS Service
Continuity capabilities.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.5 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.238 |
ct1 |
|
SIP based user configuration |
The present document provides a Session Initiation Protocol (SIP) based protocol framework that serves as a means of
user configuration of supplementary services in the IP Multimedia (IM) Core Network (CN) subsystem. The protocol
framework relies upon the contents of the Request-URI in a SIP INVITE request to enable basic configuration of
services without requiring use of the Ut interface.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support user configuration of supplementary services.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.2 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.239 |
ct1 |
|
IMS Flexible alerting supplementary service |
The present document provides the protocol details for the Flexible Alerting supplementary service in the IP
Multimedia (IM) Core Network (CN) subsystem based on the requirements from 3GPP TS 22.173.
Flexible Alerting (FA) causes a call to a pilot identity to branch the call into several legs to alert several termination
addresses (group members) simultaneously. The first leg to be answered is connected to the calling party. The other call
legs are abandoned.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the FA supplementary service.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.2 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.247 |
ct1 |
|
Messaging Service using the IP Multimedia (IM) Core Network
(CN) Subsystem - Stage 3 |
This TS provides the protocol details for the messaging service within the IP Multimedia CN Subsystem
(IMS) based on the Session Initiation Protocol (SIP), the Session Description Protocol (SDP) and, the Message Session
Relay Protocol (MSRP). The document covers immediate messaging, session based messaging and session-based
messaging conferences, as described in
3GPP TS 22.340.
Where possible this document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of SIP, SDP and, MSRP, either directly, or as modified by
3GPP TS 24.229.
This document is applicable to Application Servers (ASs) , Media Resource Function Controllers (MRFCs),
Media Resource Function Processors (MRFPs) and to User Equipment (UE) providing messaging capabilities.
This document does not cover the signalling between a MRFC and a MRFP.
|
|
|
- | |
- | |
- | |
V6.10 | |
V7.4 | |
V8.4 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.259 |
ct1 |
|
Personal Network Management (PNM) |
Personal Network Management (PNM) is a home network-based application and provides the home network-based
management of Personal Network (PN) consisting of multiple devices belonging to a single user, as described in
3GPP TS 22.259 and 3GPP TS 23.259.
The present document provides the protocol details for enabling PNM services in the
IM CN subsystem based on the protocols of XCAP, SIP and SDP.
The present document provides the protocol details for enabling PNM services in
Circuit Switched (CS) domain based on the protocols of CAP, MAP, ISUP, USSD and BICC.
The present document is applicable to User Equipment (UEs) and Application Servers (AS) providing PNM
capabilities.
The present document makes no PNM specific enhancements to SIP, SIP events or SDP specified in
3GPP TS 24.229.
The present document makes no PNM specific enhancements to CAP, MAP, ISUP, USSD and BICC.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.2 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.279 |
ct1 |
|
Combining Circuit Switched (CS) and
IP Multimedia Subsystem (IMS) Services - Stage 3 |
|
This TS provides the technical realisation for the combination of Circuit Switched calls and
IM sessions when using them simultaneously between the same two users.
This document describes the use of CS and IM services in combination, using the existing procedures
that have been defined for CS and IMS. It includes the necessary function as adding an IM session to
an ongoing CS call, adding a CS call to an ongoing IM session, supplementary services as they relate
to CSICS and supporting capability exchange.
This document is applicable to UE and Application Servers providing for the combination of
Circuit Switched calls and IM sessions.
|
|
|
- | |
- | |
- | |
- | |
V7.7 | |
V8.2 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.285 |
ct1 |
|
Allowed Closed Subscriber Group (CSG) List - Management Object (MO) |
The present document specifies an Allowed Closed Subscriber Group (CSG) List Management Object (MO).
The Allowed CSG List MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2
and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler
Release Definition OMA-ERELD-DM-V1_2.
The Allowed CSG List MO consists of relevant parameters for that can be used by the UE to select the appropriate CSG
cell based on its subscription.
The usage of the Allowed CSG List for in the idle mode process and the mobility management procedure is defined in
3GPP TS 23.122, 3GPP TS 24.008 and 3GPP TS 24.301.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.4 | |
V9.2 | |
V10.0 | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.0 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.292 |
ct1 |
|
IP Multimedia Core Network subsystem Centralized Services - Stage 3 |
IP Multimedia (IM) Core Network (CN) subsystem centralized services (ICS) allow for the delivery of consistent IMS
services to the user regardless of the attached access type (e.g. CS domain access or IP-CAN).
This TS provides the protocol details for the realization of ICS based on the Session Initiation protocol
(SIP), the Session Description Protocol (SDP) and the protocols of the 3GPP Circuit-Switched (CS) domain (e.g. CAP,
MAP, ISUP, BICC and the NAS call control protocol for the CS access).
This document makes no ICS specific enhancements to SIP or SDP beyond those specified in 3GPP TS 24.229.
The present document is applicable to User Equipment (UEs), MSC Servers and Application Servers (AS) providing
ICS capabilities.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.6 | |
V9.4 | |
V10.0 | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.294 |
ct1 |
|
IP Multimedia Subsystem (IMS) Centralized Services (ICS) protocol via I1 interface |
The present document describes the I1 interface between IMS Centralized Services (ICS) UE and Service Centralization and Continuity (SCC) Application Server (AS).
This specification defines a new application layer protocol over I1 interface, specifies the interaction between the ICS UE and the SCC AS including session control procedures and supplementary services control procedures.
The protocol is intended to be independent of the transport protocol used so it can be applied to a number of technologies that need different transport protocols.
The overall ICS architecture is specified in 3GPP TS 23.292.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the IMS centralized services.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.301 |
ct1 |
|
Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS) |
This TS specifies the procedures used by the protocols for mobility management and session management
between User Equipment (UE) and Mobility Management Entity (MME) in the Evolved Packet System (EPS). These
protocols belong to the non-access stratum (NAS).
The EPS Mobility Management (EMM) protocol defined in the present document provides procedures for the control of
mobility when the UE is using the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN).
The EMM protocol also provides control of security for the NAS protocols.
The EPS Session Management (ESM) protocol defined in the present document provides procedures for the handling of
EPS bearer contexts. Together with the bearer control provided by the access stratum, this protocol is used for the
control of user plane bearers.
For both NAS protocols the present document specifies procedures for the support of inter-system mobility between
E-UTRAN and other 3GPP or non-3GPP access networks:
|
| - |
For inter-system mobility between E-UTRAN and GERAN or UTRAN, this includes rules for a mapping
between parameters and procedures used by the NAS protocols defined in the present document and the NAS
protocols specified in 3GPP TS 24.008.
| |
| - |
For inter-system mobility between E-UTRAN and generic non-3GPP access networks, this includes specific
NAS procedures to maintain IP connectivity to the PDN Gateway and to provide parameters needed by the UE
when using mobility management based on Dual-Stack Mobile IPv6 (see 3GPP TS 24.303) or MIPv4
(see 3GPP TS 24.304).
|
The present document is applicable to the UE and to the MME in the EPS.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.6 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.302 |
ct1 |
|
Access to the Evolved Packet Core (EPC)
via non-3GPP access networks |
The present document specifies the discovery and network selection procedures for access to 3GPP Evolved Packet
Core (EPC) via non-3GPP access networks and includes Authentication and Access Authorization using
Authentication, Authorization and Accounting (AAA) procedures used for the interworking of the 3GPP EPC and the
non-3GPP access networks.
The present document also specifies the Tunnel management procedures used for establishing an end-to-end tunnel
from the UE to the ePDG to the point of obtaining IP connectivity and includes the selection of the IP mobility mode.
Editors Note: The scope of the authentication between the UE and EPC to be specified in this document is FFS.
The non-3GPP access networks considered in this present document are cdma2000® HRPD and Worldwide
Interoperability for Microwave Access (WiMAX) , and any access technologies covered in 3GPP TS 23.402. These
non-3GPP access networks can be trusted or untrusted access networks.
The present document is applicable to the UE and the network. In this technical specification the network is the 3GPP
EPC.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.6 | |
V9.3 | |
V10.0 | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.303 |
ct1 |
|
Mobility management based on Dual-Stack Mobile IPv6 |
The present document specifies the signalling procedures for accessing the 3GPP Evolved Packet Core network and
handling the mobility between 3GPP and non-3GPP accesses via the S2c reference point defined in
3GPP TS 23.402.
The present document is applicable to the User Equipment (UE) and the network node implementing the Home Agent
functionality.
In addition the present document specifies the procedures used for the DSMIPv6 Home Agent discovery, for
bootstrapping the DSMIPv6 security association between the UE and the Home Agent and for managing the DSMIPv6
tunnel. The specification of these procedures is compliant to IETF RFCs.
DSMIPv6 procedures can be used independently of the underlying access technology.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.6 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.304 |
ct1 |
|
Mobility management based on Mobile IPv4 -
UE - foreign agent interface |
The present document describes the stage 3 aspects of mobility management for User Equipment (UE) using IETF
Mobile IPv4 foreign agent mode to access the Evolved Packet Core Network (EPC) through trusted non-3GPP access
networks and for mobility management of UE between the 3GPP access network and trusted non-3GPP access
networks.
In particular, the present document describes the UE - Mobile IPv4 Foreign Agent (FA) interface stage 3 aspects, where
the FA functionality is located within the access network in the non-3GPP access domain.
The present document is applicable to the User Equipment (UE) and the network node implementing the FA
functionality.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.1 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.305 |
ct1 |
|
Selective Disabling of 3GPP User Equipment Capabilities (SDoUE) - Management Object (MO) |
This TS specifies a mobile device Selective Disabling of 3GPP UE Capabilities (SDoUE) Management Object (MO) and the rules and corresponding behaviour of the UE with regard to the selective disabling of 3GPP UE capabilities, for example, when services or functions are disabled/enabled.
The SDoUE MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2.
The SDoUE MO consists of the relevant parameters that can be managed for selective disabling of 3GPP UE capabilities.
The SDoUE MO defines a repository of data into the ME.
The service requirements for selective disabling of 3GPP UE capabilities are defined in 3GPP TS 22.011.
|
|
|
- | |
- | |
- | |
- | |
V7.4 | |
V8.2 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.312 |
ct1 |
|
Access Network Discovery and Selection Function (ANDSF)
Management Object (MO) |
The present document defines management objects that can be used by the Access Network Discovery and Selection
Function (ANDSF) and the UE.
The Management Object (MO) is compatible with the OMA Device Management (DM) protocol specifications,
version 1.2 and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the
Enabler Release Definition OMA-ERELD-DM-V1_2.
The MO consists of relevant parameters for intersystem mobility policy- and access network discovery information that
can be managed by the ANDSF.
The service requirements and the functional requirements for the access network discovery and selection are described
in 3GPP TS 22.278 and in 3GPP TS 23.402 respectively.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.5 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.323 |
ct1 |
|
Trace Management Object (MO) |
This document defines the IMS service level tracing management object. The management object is compatible with
OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device
Description Framework as described in the Enabler Release Definition OMA-ERELD _DM-V1_2.
The IMS service level tracing management object consists of relevant parameters that can be managed for IMS service
level tracing capabilities.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.1 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.327 |
ct1 |
|
Mobility between 3GPP I-WLAN and 3GPP systems -
GPRS and 3GPP I-WLAN aspects |
This document specifies the signalling procedures for handling the mobility of a UE between 3GPP Wireless Local
Area Network Interworking (I-WLAN) and GPRS systems.
The present document is applicable to the User Equipment (UE) and the network nodes supporting mobility between
3GPP I-WLAN and GPRS systems.
In addition, the present document specifies the procedures used between the UE and the network nodes for the attach
and detach cases. It also specifies how the UE performs handover when moving from I-WLAN to GPRS systems and
vice-versa.
This document is based on DSMIPv6 procedures specified in 3GPP TS 24.303 and will specify additional details
specific to the I-WLAN and GPRS systems in the context of mobility between those two accesses.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.6 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.341 |
ct1 |
|
Support of SMS over IP networks - Stage 3 |
This TS
provides the protocol details for SMS over IP within the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events as defined in 3GPP TS 24.229.
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SIP Events, either directly, or as modified by 3GPP TS 24.229.
The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing SMS over IP functionality.
|
|
|
- | |
- | |
- | |
- | |
V7.5 | |
V8.4 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 24.801 |
ct1 |
|
3GPP System Architecture Evolution (SAE) - CT WG1 aspects |
The present document discusses and describes the CT1 aspects of the 3GPP System Architecture Evolution (SAE)
towards a higher-data-rate, lower-latency, packet-optimized system that supports multiple access technologies.
In particular, these CT1 aspects include the Non-Access-Stratum (NAS) functions to be performed by the User
Equipment (UE) in idle mode, the NAS signalling procedures between the UE and the evolved packet core network
(EPC) via the E-UTRAN, and the layer 3 signalling procedures between the UE and the EPC via non-3GPP access
networks.
The present document also considers the requirements on the NAS between the UE and the core network which arise
from specific services like MBMS and network functions like security, QoS, and mobility within the E-UTRAN or
between the E-UTRAN and other 3GPP or non-3GPP access networks.
The present document is intended as a holding place for CT1 SAE material until it stabilises sufficiently to be moved to
appropriate 3GPP technical specifications.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 24.819 |
ct1 |
|
Protocol impact from providing IMS services via fixed broadband - Stage-3 |
The present document is a temporary container for the functional models, flows and protocol details for the IM CN
subsystem behaviour when providing IMS services via fixed broadband access. This service is based on the Session
Initiation Protocol (SIP), the Session Description Protocol (SDP), other protocols, the Gq interface and the Cx interface.
The contents of this report will be moved into appropriate 3GPP Technical Specifications.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 24.841 |
ct1 |
|
Presence service based on SIP - Functional models, information flows and protocol details |
The present document is a temporary container for the functional models, flows and protocol details for the presence
service within the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and
SIP Events.
Where possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of SIP and SIP Events. Where this is not possible, extensions to SIP are defined
within the present document. The document has therefore been structured in order to allow both forms of specification.
The present document includes information applicable to network operators, service providers and manufacturers.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 24.879 |
ct1 |
|
Combining Circuit-Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions |
The present document provides the technical realisation for the combination of Circuit Switched calls and IM sessions
when using them simultaneously between the same two users.
The present document describes the use of CS and IM services in combination, using the existing procedures that have
been defined for CS and IMS. It includes the necessary function as adding an IM session to an ongoing CS call, adding
a CS call to an ongoing IM session, supplementary services as they relate to CSICS and supporting capability exchange.
The present document is applicable to UE and Application Servers providing for the combination of Circuit Switched
calls and IM sessions.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 24.880 |
ct1 |
|
Media server control using the IP Multimedia (IM) Core Network (CN) subsystem - Stage 3 |
The present document describes the implementation options and requirements for a media server control protocol to be
used with the Mr and ISC interfaces.
This Technical Report includes the study of the following items:
|
| - |
Define the requirements for a media server control protocol.
| |
| - |
Consider existing standards work that should be studied for the definition of a media server control protocol.
| |
| - |
Study and determine whether the media server control protocol should be carried in SIP or whether SIP should
be used to setup a dedicated control interface.
| |
| - |
Study whether the AS directing the SIP session to the MRFC is always the same SIP-AS that should control the
MRFC.
| |
| - |
Determine whether the media server control protocol should have a package naming and extension capability
(similar to H.248 packages) to allow the support and registration of different media processing capabilities.
| |
| - |
Determine the SIP call flows and SDP capabilities associated with the media server control protocol and whether
these SIP messages need to be passed through a S-CSCF proxy function or whether it is more efficient to have a
direct AS-MRFC interface.
|
This Technical Report will be used to move into the specification phase for a media server control protocol.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TR 24.930 |
ct1 |
|
Signalling Flows for the Session Setup in the IM CN Subsystem based on SIP and SDP - Stage 3 |
This TR gives examples of the session setup in the IM CN subsystem based on SIP and SDP.
These signalling flows provide detailed signalling flows, which expand on the overview information flows provided in 3GPP TS 23.228.
The flows focus on a basic session setup, i.e. no flows will be provided for topology hiding, for sessions with IBCF involved or for sessions having certain features.
The signalling flows provided in this document follow the methodology developed in 3GPP TS 24.228. The following additional considerations apply:
|
| a) |
3GPP TS 24.228 shows separate signalling flows with no configuration hiding between networks, and with configuration hiding between networks. Separate signalling flows are not shown in the present document;
| |
| b) |
3GPP TS 24.228 breaks down the functionality of the various CSCFs. The functionality of the S-CSCF and I-CSCF is not relevant for the session setup procedure. Therefore S-CSCFs and I-CSCFs are collapsed into a single entity labelled "Intermediate IM CN subsystem entities".
|
|
|
|
- | |
- | |
- | |
- | |
V7.5 | |
V8.2 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.503 |
|
|
|
This TS together with the endorsed document provides the necessary SIP/SDP specifications for
supporting TISPAN Release 2 requirements.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.504 |
|
|
|
In addition, a service "Communication Diversion Notification" (CDIVN) to the CDIV PSTN/ISDN simulation services
is described in the present document.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.604 |
ct1 |
|
Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem;
Protocol specification |
This TS specifies the stage 3, Protocol Description of the Communications Diversion (CDIV)
supplementary services, based on stage one and two of the ISDN Communication diversion supplementary services. It
provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation
Protocol (SIP) and the Session Description Protocol (SDP).
In addition, the "Communication Diversion Notification" (CDIVN) CDIVservice is described in the present document.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the CDIV supplementary service.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.7 | |
V9.4 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.405 |
ct1 |
|
TISPAN - PSTN/ISDN simulation services: Conference (CONF); Protocol specification |
This TS specifies the, stage three, Protocol Description of the Conference (CONF) service based on stage
one and two of the ISDN CONF supplementary service. Within the Next Generation Network (NGN) the stage 3 is
specified using the IP-Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session
Description Protocol (SDP).
The present document specifies centralized conferencing, using a conference focus, distributed conferencing is out of
scope.
The present document does not cover the cases of:
|
| a) |
cascading conference services; and
| |
| b) |
the support of the PSTN/ISDN conference service hosted in the PSTN.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.605 |
ct1 |
|
Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem - Protocol specification |
This TS specifies the stage three Protocol Description of the Conference (CONF) service based on stage
one and two of the ISDN CONF supplementary service. It provides the protocol details in the IP Multimedia (IM) Core
Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document specifies centralized conferencing, using a conference focus, distributed conferencing is out of
scope.
The present document does not cover the cases of :
|
| a) |
cascading conference services; and
| |
| b) |
the support of the PSTN/ISDN conference service hosted in the PSTN.
|
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the CONF supplementary service.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.3 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
V7.0 | |
V8.0 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.2 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
V7.0 | |
V8.2 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.4 | |
V9.1 | |
V10.0 | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.4 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
V7.0 | |
V8.0 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.610 |
ct1 |
|
Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem - Protocol specification |
This TS specifies the stage three Protocol Description of the Communication Hold (HOLD) services,
based on stages one and two of the ISDN Hold (HOLD) supplementary services. It provides the protocol details in the
IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session
Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the HOLD supplementary service.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.3 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
V7.1 | |
V8.1 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.611 |
ct1 |
|
Anonymous Communication Rejection (ACR) and Communication Barring (CB)using IP Multimedia (IM) Core Network (CN) subsystem - Protocol specification |
This TS specifies the stage three, Protocol Description of the Anonymous Communication Rejection
(ACR) and Communication Barring (CB) supplementary service, based on stage one and two of the ISDN
supplementary service Anonymous Call Rejection (ACR), Incoming Communication Barring (ICB) and Outgoing
Communication Barring (OCB). It provides the protocol details in the IP Multimedia (IM) Core Network (CN)
subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the ACR and CB supplementary services.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.2 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.416 |
ct1 |
|
TISPAN - PSTN/ISDN simulation services - Malicious Communication Identification (MCID) - Protocol specification |
|
This TS specifies the, stage three, Protocol Description of the Malicious Call Communication
Identification (MCID) service based on the stage one and two of ISDN Malicious Call Identification supplementary
service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call
Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). The MCID service
will store session related information independent of the service requested.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.616 |
ct1 |
|
Malicious Communication Identification (MCID)using IP Multimedia (IM) Core Network (CN) subsystem - Protocol specification |
This TS specifies the stage three Protocol Description of the Malicious Call Communication
Identification (MCID) service based on the stage one and two of ISDN Malicious Call Identification supplementary
service. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session
Initiation Protocol (SIP) and the Session Description Protocol (SDP). The MCID service will store session related
information independent of the service requested.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the MCID supplementary service.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.6 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.423 |
ct1 |
|
TISPAN - PSTN/ISDN simulation services - XCAP over the Ut interface for Manipulating NGN PSTN/ISDN Simulation Services |
|
This TS defines a protocol used for manipulating data related to PSTN/ISDN Simulation services. The
protocol is based on the XML Configuration Access Protocol (XCAP). A new
XCAP application usage is defined for the purpose of manipulating PSTN/ISDN Simulation services data. The common
XCAP related aspects that are applicable to PSTN/ISDN services are specified in the present document. The protocol
allows authorized users to manipulate service-related data either when they are connected to IMS or when they are
connected to non-IMS networks (e.g. the public Internet).
|
|
|
- | |
- | |
- | |
- | |
V7.1 | |
V8.2 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.623 |
ct1 |
|
XCAP over the Ut interface for Manipulating Simulation Services |
This TS defines a protocol used for manipulating data related to supplementary services. The protocol is
based on the XML Configuration Access Protocol (XCAP) RFC 4825. A new
XCAP application usage is defined for the purpose of manipulating the supplementary services data. The common
XCAP related aspects that are applicable to supplementary services are specified in the present document. The protocol
allows authorized users to manipulate service-related data either when they are connected to IMS or when they are
connected to non-IMS networks (e.g. the public Internet).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support XCAP application usage for manipulating data related to supplementary services.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.2 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.428 |
ct1 |
|
TISPAN - Common Basic Communication procedures - Protocol specification |
This TS describes the stage three protocol for basic communication procedures common to several
services when at least one Application Server (AS) is included in the communication. The common procedures are
based on stage three specifications for services.
The present document contains examples of signalling flows for the common basic communication procedures.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.628 |
ct1 |
|
Common Basic Communication procedures using the IM CN subsystem - Protocol specification |
This TS describes the stage three protocol for basic communication procedures common to several
services in the IP Multimedia (IM) Core Network (CN) subsystem when at least one Application Server (AS) is
included in the communication. The common procedures are based on stage three specifications for supplementary
services.
The present document contains examples of signalling flows for the common basic communication procedures.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the common basic communication procedures.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.2 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.629 |
ct1 |
|
Explicit Communication Transfer (ECT) using the IM CN subsystem - Protocol specification |
This TS specifies the stage three (protocol description) of the Explicit Communication transfer (ECT)
supplementary service, based on stage one and two of the ISDN ECT supplementary service. It provides the protocol
details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the
Session Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the ECT supplementary service.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.3 | |
V9.0 | |
V10.0 | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.430 |
ct1 |
|
TISPAN - Presence Service Capability - Protocol Specification |
This TS provides the protocol details for the presence service within the IP Multimedia (IM) Core
Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events as defined in ETSI ES 283 003.
Where possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of SIP and SIP Events, either directly, or as modified by ETSI ES 283 003.
The Presence XDMS and Resource List Server (RLS) specific data formats and XCAP application usages are within the
scope of the present document. These are used within the context of the generic XDM capability described in
TS 183 038.
The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing presence
functionality.
|
|
|
- | |
- | |
- | |
- | |
V7.0 | |
V8.0 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- | |
- | |
- | |
- | |
V7.0 | |
V8.0 | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.447 |
ct1 |
|
TISPAN - NGN IMS Supplementary Services - Advice Of Charge (AOC) |
This TS specifies the stage three Protocol Description of the Advice Of Charge (AOC) service, based on
stage 1 and 2 of the ISDN Supplementary Service Advice Of Charge for all calls (permanent mode). Within the
TISPAN NGN Release 2 Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia
Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
Three AOC services exist:
|
| a) |
Charging information at communication set-up time (AOC-S)
The AOC-S service enables a user to receive information about the charging rates at communication set-up time
and also to receive further information during the communication if there is a change of charging rates.
| |
| b) |
Charging information during the communication (AOC-D)
The AOC-D service enables a user to receive information on the recorded charges for a communication during
the active phase of the communication.
| |
| c) |
Charging information at the end of the communication (AOC-E)
The AOC-E service enables a user to receive information on the recorded charges for a communication when the
communication is terminated.
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.647 |
ct1 |
|
Advice Of Charge (AOC) using the IM CN subsystem - Protocol Specification |
This TS specifies the stage three Protocol Description of the Advice Of Charge (AOC) service, based on
stage 1 and 2 of the ISDN Supplementary Service Advice Of Charge for all calls (permanent mode). It provides the
protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP)
and the Session Description Protocol (SDP).
Three AOC services exist:
|
| a) |
Charging information at communication set-up time (AOC-S)
The AOC-S service enables a user to receive information about the charging rates at communication set-up time
and also to receive further information during the communication if there is a change of charging rates.
| |
| b) |
Charging information during the communication (AOC-D)
The AOC-D service enables a user to receive information on the recorded charges for a communication during
the active phase of the communication.
| |
| c) |
Charging information at the end of the communication (AOC-E)
The AOC-E service enables a user to receive information on the recorded charges for a communication when the
communication is terminated.
|
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the AOC supplementary services.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.3 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.654 |
ct1 |
|
Closed User Group (CUG) using the IM CN subsystem - Protocol Specification |
This TS specifies the stage three Protocol Description of the Closed User Group (CUG) service, based on
stage one and two of the ISDN Communication diversion supplementary services. It provides the protocol details in the
IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session
Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the CUG supplementary service.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.3 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.615 |
ct1 |
|
Communication Waiting (CW) using the IM CN subsystem - Protocol Specfication |
This TS specifies the stage 3, Protocol Description of the Communication Waiting (CW) service, based
on stage 1 and stage 2 of the ISDN call waiting supplementary services. It provides the protocol details in the IP
Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session
Description Protocol (SDP).
The Communication Waiting (CW) service enables a user to be informed, that very limited resources are available for
an incoming communication. The user then has the choice of accepting, rejecting or ignoring the waiting call (as per
basic call procedures).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the CW supplementary service.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.3 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 24.642 |
ct1 |
|
CCBS and CCNR using the IM CN subsystem - Protocol Specification |
This TS specifies the stage three Protocol Description of the Completion of Communications to Busy
Subscriber (CCBS) service and the Completion of Communication on no Reply (CCNR) service, based on stage one
and two of the ISDN supplementary services. It provides the protocol details in the IP Multimedia (IM) Core Network
(CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The Completion of Communications to Busy Subscriber CCBS service enables user A, encountering a busy
destination B, to have the communication completed without having to make a new communication attempt when the
destination B becomes not busy.
The Completion of Communications on No Reply CCNR supplementary service enables user A, encountering a
destination B which does not answer the communication (No Reply), to have the communication completed without
having to make a new communication attempt when the destination becomes not busy after having initiated an activity.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the CCBS and CCNR supplementary services.
|
|
|
- | |
- | |
- | |
- | |
- | |
V8.5 | |
V9.3 | |
V10.0 | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
