3GPP TS 24.216: Communication Continuity Management Object
Specification: 24216
Summary
This document defines the Communication Continuity Management Object, which is used to manage settings of the UE for communication continuation capabilities, including Voice Call Continuity (VCC), Service Continuity (SC), and inter UE transfer.
Specification Intelligence
This is a Technical Document in the Unknown Series series, focusing on Technical Document. The document is currently in approved by tsg and under change control and is under formal change control.
Classification
Type: Technical Document
Subject: Unknown Series
Series: 24.xxx
Target: Technical Implementers
Specifics
Status: Change Control
Version
930.0.0
Release 930
0 technical • 0 editorial
Full Document v930
3GPP TS 24.216 V9.3.0 (2010-09) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Communication Continuity Management Object (MO) (Release 9) EMBED Word.Picture.8 The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices. Keywords UMTS, IMS, SIP, Multimedia, Management, GSM, LTE 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS™ is a Trade Mark of ETSI registered for the benefit of its members 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM Association Contents TOC \o "1-9" Foreword PAGEREF _Toc273371869 \h 4 1 Scope PAGEREF _Toc273371870 \h 5 2 References PAGEREF _Toc273371871 \h 5 3 Definitions and abbreviations PAGEREF _Toc273371872 \h 5 3.1 Definitions PAGEREF _Toc273371873 \h 5 3.2 Abbreviations PAGEREF _Toc273371874 \h 5 4 Communication Continuity Management Object PAGEREF _Toc273371875 \h 6 5 Management Object parameters PAGEREF _Toc273371876 \h 7 5.1 General PAGEREF _Toc273371877 \h 7 5.2 Node: /PAGEREF _Toc273371878 \h 7 5.3 / /Name PAGEREF _Toc273371879 \h 8 5.4 / /VDI/ PAGEREF _Toc273371880 \h 8 5.5 / /VDN/ PAGEREF _Toc273371881 \h 8 5.6 / /Preferred_domain/ PAGEREF _Toc273371882 \h 8 5.7 / /Immediate_DT/ PAGEREF _Toc273371883 \h 9 5.8 / / DT_CS-to-IM_CN_direction / PAGEREF _Toc273371884 \h 9 5.9 / / DT_IM_CN-to-CS_direction / PAGEREF _Toc273371885 \h 9 5.10 / / DT_in_held_waiting_calls/ PAGEREF _Toc273371886 \h 10 5.11 / /STI/ PAGEREF _Toc273371887 \h 10 5.12 / /STN/ PAGEREF _Toc273371888 \h 10 5.13 / /OperatorPolicy PAGEREF _Toc273371889 \h 10 5.14 / /OperatorPolicy/ PAGEREF _Toc273371890 \h 11 5.15 / /OperatorPolicy/ /MediaPref PAGEREF _Toc273371891 \h 11 5.16 / /OperatorPolicy/ /MediaPref/MediaPrefId PAGEREF _Toc273371892 \h 11 5.17 / /OperatorPolicy/ /MediaPref/MediaorGroups PAGEREF _Toc273371893 \h 11 5.18 / /OperatorPolicy/ /MediaPref/MediaorGroups/ / PAGEREF _Toc273371894 \h 11 5.19 / /OperatorPolicy/ /MediaPref/MediaorGroups/ /Media PAGEREF _Toc273371895 \h 12 5.20 / /OperatorPolicy/ /MediaPref/RestrictedAccessNetworkType PAGEREF _Toc273371896 \h 12 5.21 / /OperatorPolicy/ /MediaPref/RestrictedAccessNetworkType/ PAGEREF _Toc273371897 \h 12 5.22 / /OperatorPolicy/ /MediaPref/RestrictedAccessNetworkType / /AccessNetworkType PAGEREF _Toc273371898 \h 13 5.23 / /OperatorPolicy/ /MediaPref/PreferredAccessNetworks PAGEREF _Toc273371899 \h 13 5.24 / /OperatorPolicy/ /MediaPref/ PreferredAccessNetworks/ PAGEREF _Toc273371900 \h 13 5.25 / /OperatorPolicy/ /MediaPref/ PreferredAccessNetworks/ /AccessNetworkType PAGEREF _Toc273371901 \h 13 5.26 / /OperatorPolicy/ /MediaPref/SC_media_transfer PAGEREF _Toc273371902 \h 14 5.27 / /OperatorPolicy/ /MediaPref/ SC_non_transferable_media / PAGEREF _Toc273371903 \h 14 5.28 / /InterUETransferSCCASURI/ PAGEREF _Toc273371904 \h 14 5.29 / /Ext/ PAGEREF _Toc273371905 \h 15 Annex A (informative): Management Object DDF PAGEREF _Toc273371906 \h 16 Annex B (informative): Change history PAGEREF _Toc273371907 \h 26 Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. 1 Scope This document 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 [4]. The Communication Continuity Management Object consists of relevant parameters that can be managed for Communication Continuity capabilities. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the Communication Continuity Management Object document. References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". [2] 3GPP TS 23.003: "Numbering, addressing and identification". [3] 3GPP TS 24.206: "Voice call continuity between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 3". [4] OMA-ERELD-DM-V1_2-20060602-C: "Enabler Release Definition for OMA Device Management, Candidate Version 1.2". [5] 3GPP TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity ; Stage 3". [6] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". [7] IETF RFC 4566 (July 2006): " SDP: Session Description Protocol". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] apply. For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.003 [2] apply: VCC Domain Transfer Number (VDN) VCC Domain Transfer URI (VDI) 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CN Core Network DDF Device Description Framework DM Device Management DT Domain Transfer IMS IP Multimedia core network Subsystem IP Internet Protocol MO Management Object OMA Open Mobile Alliance SC Service Continuity SIP Session Initiation Protocol ST Session Transfer STI SC Transfer URI STN SC Transfer Number UE User Equipment VCC Voice Call Continuity VDI VCC Domain Transfer URI VDN VCC Domain Transfer Number 4 Communication Continuity Management Object The Communication Continuity Management Object is used to manage settings of the UE for communication continuation capabilities. The Management Object covers parameters for communication continuation related capabilities. The Management Object enables the management of the settings on behalf of the end user. The Communication Continuity MO covers settings of the UE for the following capabilities: - Voice Call Continuity (VCC) as specified in 3GPP TS 24.206 [3]; - Service Continuity (SC) as specified in 3GPP TS 24.237 [5]; - inter UE transfer as specified in 3GPP TS 24.237 [5]. NOTE: The Communication Continuity MO can be expanded to cover settings of further communication continuity capabilities. The Management Object Identifier is: urn:oma:mo:ext-3gpp-communication-continuity:1.0. Protocol compatibility: This MO is compatible with OMA DM 1.2. The following nodes and leaf objects are possible under the Communication Continuity node: EMBED Visio.Drawing.11 Figure 1: The Communication Continuity Object 5 Management Object parameters 5.1 General This clause describes the parameters for the Communication Continuity Management Object. 5.2 Node: / This interior node acts as a placeholder for one or more accounts for a fixed node. - Occurrence: OneOrMore - Format: node - Access Types: Get - Values: N/A The interior node is mandatory if the UE supports one or more Communication Continuity capabilities. Support for a UE is defined by the related roles as defined by the related communication continuity service, as listed in clause 4 of this specification. NOTE: One node is normally used. 5.3 / /Name The Name leaf is a name for the Communication Continuity settings. - Occurrence: ZeroOrOne - Format: chr - Access Types: Get - Values: 5.4 / /VDI/ The VDI leaf is the VCC Transfer URI that the user includes in SIP INVITE requests to initiate domain transfer. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: < A VCC VDI > The format of the VCC VDI is defined by 3GPP TS 23.003 [2]. EXAMPLE: sip:[email protected] 5.5 / /VDN/ The VDN leaf is the VCC Transfer Number that the user includes in a circuit switched call setup to initiate domain transfer. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: < A VCC VDN > The format of the VCC VDN is defined by 3GPP TS 23.003 [2]. EXAMPLE: +12125555555 5.6 / /Preferred_domain/ The Preferred domain leaf represents the operator’s preferred domain for UE originated calls/sessions. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: 0, 1, 2, 3 0 – Indicates the preference for CS domain. 1 – Indicates the preference for IM CN subsystem. 2 – Indicates the preference for CS domain only. 3 – Indicates the preference for IM CN subsystem only. 5.7 / /Immediate_DT/ The Immediate Domain Transfer leaf indicates whether to initiate a VCC domain transfer immediately to the operator’s preferred domain when that domain becomes available. This operator policy only affects ongoing sessions. - Occurrence: One - Format: bool - Access Types: Get, Replace - Values: 0, 1 0 – Indicates the preference to not initiate domain transfer immediately to the preferred domain when that domain becomes available. 1 – Indicates the preference to initiate domain transfer immediately to the preferred domain when that domain becomes available. NOTE 1: If the Immediate Domain Transfer operator policy indicates that the domain transfer is not immediately required then it is up to the VCC UE to decide when to perform the domain transfer if the preferred domain is available. 5.8 / / DT_CS-to-IM_CN_direction / The Domain Transfer CS-to-IM CN direction leaf indicates if a VCC domain transfer from CS domain to IMS is restricted. - Occurrence: One - Format: bool - Access Types: Get, Replace - Values: 0, 1 0 – Indicates that the network operator prefers the domain transfer in the CS to IM CN subsystem direction can occur. 1 – Indicates that the network operator prefers the domain transfer in the CS to IM CN subsystem direction cannot occur. 5.9 / / DT_IM_CN-to-CS_direction / The Domain Transfer IM CN-to-CS direction leaf indicates if a VCC domain transfer from IM CN subsystem to CS domain is restricted. - Occurrence: One - Format: bool - Access Types: Get, Replace - Values: 0, 1 0 – Indicates that the network operator prefers the domain transfer in the IM CN subsystem to CS direction can occur. 1 – Indicates that the network operator prefers the domain transfer in the IM CN subsystem to CS direction cannot occur. 5.10 / / DT_in_held_waiting_calls/ The Domain Transfer in held_waiting calls leaf indicates whether a VCC domain transfer is restricted when the VCC UE is engaged in an active and a held/waiting call/session on the transferring-out domain (the restriction doesn’t apply in the case the VCC UE is losing coverage in the transferring-out domain). If the operator policy requires restriction in the Domain Transfer in held_waiting calls then the VCC UE should not consider other operator policy for the domain transfer. - Occurrence: One - Format: bool - Access Types: Get, Replace - Values: 0, 1 0 – Indicates that the network operator prefers the domain transfer can occur when the VCC UE is engaged in an active and a held/waiting call/session on the transferring-out domain. 1 – Indicates that the network operator prefers the domain transfer cannot occur when the VCC UE is engaged in an active and a held/waiting call/session on the transferring-out domain. 5.11 / /STI/ The STI leaf is the SC Transfer URI that the user includes in SIP INVITE requests to initiate session transfer. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: < A SC STI > The format of the SC STI is defined by 3GPP TS 23.003 [2]. EXAMPLE: sip:[email protected] 5.12 / /STN/ The STN leaf is the SC Transfer Number that the user includes in a circuit switched call setup to initiate session transfer. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: < A SC STN > The format of the SC STN is defined by 3GPP TS 23.003 [2]. EXAMPLE: +12125555555 5.13 / /OperatorPolicy This interior node indicates the presence of an operator policy list used to allow the session transfer of the media on the specified access networks. - Occurrence: ZeroOrOne - Format: node - Access Types: Get, Replace - Values:N/A 5.14 / /OperatorPolicy/ This run-time node acts as a placeholder for one or more OperatorPolicy to allow the session transfer of the media on the specified access networks. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: N/A 5.15 / /OperatorPolicy/ /MediaPref This interior node indicates one or more operator media preferences; each preference contains the operator preferences associated to each media or a group of media. - Occurrence: One - Format: node - Access Types: Get, Replace - Values: N/A 5.16 / /OperatorPolicy/ /MediaPref/MediaPrefId The MediaPrefId leaf is a name for the operator media preference. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: < preference number X> 5.17 / /OperatorPolicy/ /MediaPref/MediaorGroups This interior node indicates one or more media or group of media access networks that are subject to the operator preferences. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: N/A 5.18 / /OperatorPolicy/ /MediaPref/MediaorGroups/ / This run-time node acts as a placeholder for one or more media to which the operator preferences are applicable. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: N/A 5.19 / /OperatorPolicy/ /MediaPref/MediaorGroups/ /Media This leaf indicates the media, for which the operator policy are applicable by the UE with SC capabilities for session transfer - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: one or more of the value coded according to the IETF RFC 4566 [7]. 5.20 / /OperatorPolicy/ /MediaPref/RestrictedAccessNetworkType The RestrictedAccessNetworkType node indicates one or more restricted access technologies according to the operator preferences related to the session origination and the session transfer of the media on the specified access networks. - Occurrence: ZeroOrOne - Format: node - Access Types: Get, Replace - Values: N/A 5.21 / /OperatorPolicy/ /MediaPref/RestrictedAccessNetworkType/ This run-time node acts as a placeholder for one or more access networks, according to the operator preferences to avoid the session origination and the session transfer of the media on the specified access networks. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: N/A 5.22 / /OperatorPolicy/ /MediaPref/RestrictedAccessNetworkType / /AccessNetworkType The AccessNetworkType leaf indicates an access technology that should be avoided if the current rule is active, according to the operator preferences to avoid the session origination and the session transfer of the media on the specified access networks type. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: one of the values coded according to the access-type field defined for the P-Access-Network-Info header in 3GPP TS 24.229 [6]. 5.23 / /OperatorPolicy/ /MediaPref/PreferredAccessNetworks The PreferredAccessNetworks node indicates one or more preferred access network technologies according to the operator preferences related to the session origination and the session transfer of the media on the specified access networks. - Occurrence: ZeroOrOne - Format: node - Access Types: Get, Replace - Values: N/A 5.24 / /OperatorPolicy/ /MediaPref/ PreferredAccessNetworks/ This run-time node acts as a placeholder for one or more access networks, according to the operator policy are preferred for the session origination and the session transfer of the media on the specified access networks. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: N/A 5.25 / /OperatorPolicy/ /MediaPref/ PreferredAccessNetworks/ /AccessNetworkType The AccessNetworkType leaf indicates an access technology that should be considered preferred if the current rule is active, for the session origination and the session transfer of the media on the specified access networks type. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: one of the values coded according to the access-type field defined for the P-Access-Network-Info header in 3GPP TS 24.229 [6]. 5.26 / /OperatorPolicy/ /MediaPref/SC_media_transfer This leaf provides to the UE the indication whether the media shall/should/may transferred to target access network according to the operator preferences to allow the session transfer of the media on the specified access networks. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: shall– Indicates that the UE shall start session transfer according to the home operator’s list of preferred access networks as soon as possible; should – Indicates that the UE start session transfer according to the home operator’s list of preferred access networks, if session transfer is possible and desirable after having taken into account the Local Operating Environment Information; may - Indicates that the UE is free.to decide whether or not to start session transfer in accordance with user preferences (when configured), if session transfer is possible and desirable after having taken into account the Local Operating Environment Information. 5.27 / /OperatorPolicy/ /MediaPref/ SC_non_transferable_media / This leaf provides to the UE the indication on the behaviour expected in case of media which cannot be transferred to other Access Networks, according to the operator preferences to allow the session transfer of the media on the specified access networks. - Occurrence:One - Format: chr - Access Types: Get, Replace - Values: keep– Indicates that the UE will prevent the execution of the media transfer for those media. drop- Indicates that the UE will perform the media transfer dropping the non transferable media. 5.28 / /InterUETransferSCCASURI/ This leaf contains the inter UE transfer SCC AS URI used in 3GPP TS 24.237 [5]. - Occurrence: One - Format: chr - Access Types: Get, Replace - Value: 5.29 / /Ext/ The Ext is an interior node for where the vendor specific information about the Communication Continuity MO is being placed (vendor meaning application vendor, device vendor etc.). Usually the vendor extension is identified by vendor specific name under the ext node. The tree structure under the vendor identified is not defined and can therefore include one or more un-standardized sub-trees. - Occurrence: ZeroOrOne - Format: node - Access Types: Get, Replace - Values: N/A Annex A (informative): Management Object DDF This DDF is the standardized minimal set. A vendor can define it’s own DDF for the complete device. This DDF can include more features than this minimal standardized version. Annex B (informative): Change history Change history DateTSG #TSG Doc.CRRevSubject/CommentOldNewWG doc2007-01Version 0.0.0: Preliminary proposal0.0.02007-01Version 0.0.1: Version after CT1#450.0.00.0.12007-02Version 2.0.0: Editor introduced TS number, sent to TSG CT 35 for information and approval0.0.11.0.02007-03Version 1.0.0 approved by CT#35 in CP-070128 and version 7.0.0 created by MCC1.0.07.0.02007-06CT#36CP-07037700011Corrections to parameters in 24.2167.0.07.1.0C1-0709422007-06CT#36CP-07037700021Introduction of operator policies7.0.07.1.0C1-0713412007-09CT-37CP-0705930003Editorial modification of the CC object7.1.07.2.0C1-0715412008-12CT-42CP-0808740008CC MO URN7.2.07.3.0C1-0850832008-12CT-42CP-0809680009Introduction of STI, STN in SC MO and IMS SC Operator Policy coding7.3.08.0.02008-12CT-42Editorial cleanup by MCC7.3.08.0.02009-03CT-43CP-09011900111MO syntax correction8.0.08.1.0C1-0910222009-03CT-43CP-09014700121IMS SC Operator Policy coding8.0.08.1.0C1-0909172009-03CT-43CP-0901190014MO DDF XML bug fix8.0.08.1.0C1-0902912009-09CT-45CP-09066900162Alignment with stage 28.1.08.2.0C1-0930202009-12CT-46Upgrade to Rel-98.2.09.0.02010-03CT-47CP-1001420019Inter UE Transfer SCC AS URI9.0.09.1.0C1-1007062010-06CT-48CP-10034400211Update scope of TS to correctly cover functionality specified. 9.1.09.2.0C1-1018982010-09CT-49CP-10049300231Correcting DDF and Description of Communication Continuity MO9.2.09.3.0C1-102698 STYLEREF ZA 3GPP TS 24.216 V9.3.0 (2010-09) PAGE 6 STYLEREF ZGSM Release 9 3GPP 1.2 --The device manufacturer-- --The device model-- Communication_Continuity Communication Continuity settings The Communication Continuity Management Object. Name User displayable name for the node. text/plain VDI The VCC Transfer URI. VDN The VCC Transfer Number. Preferred_domain Preferred_domain text/plain Immediate_DT Immediate_DT text/plain DT_CS-to-IM_CN_direction DT_CS-to-IM_CN_direction text/plain DT_IM_CN-to-CS_direction DT_IM_CN-to-CS_direction text/plain DT_in_held_waiting_calls DT_in_held_waiting_calls text/plain STI The SC Transfer URI. STN The SC Transfer Number. OperatorPolicy A collection of Operator Policy The "name" node for the MediaPref object. MediaPref A collection of MediaPreferences MediaPrefId Media Preference Id text/plain MediaorGroups A collection of Media or group of media Media Media A collection of Media text/plain RestrictedAccessNetworkType A collection of Access Network Types Access NetworkType AccessNetworkType A collection of access network type PreferredAccessNetworks A collection of Access Network Types Access Network Type AccessNetworkType A collection of access network type SC_media_transfer SC_media_transfer text/plain SC_non_transferable_media SC_non_transferable_media text/plain InterUETransferSCCASURI the inter UE transfer SCC AS URI Ext A collection of all Extension objects.
Version Control
Version Control
Toto je jediná verze této specifikace.
v930
Download & Access
24216-930
Technical Details
AI Classification
Category: 7. Testování a interoperabilita
Subcategory: 7.1 Conformance Testing
Function: Test specification
Relevance: 7/10
Version Information
Release: Rel-9
Version: 930
Series: 24_series
Published: 2010-09
Document Info
Type: Technical Specification
TSG: Core Network and Terminals;
WGs:
CTCT1
Keywords & Refs
Keywords:
SIPLTEGSMIMS+1
Refs: 5 references
Partners
Contributors:
TTCARIBETSI+3
File Info
File: 24216-930
Processed: 2025-06-22
3GPP Spec Explorer - Enhanced specification intelligence