3GPP TS V ( )

Transcription

1 TS V ( ) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IMS Management Object (MO); Stage 3 (Release 10) The present document has been developed within the 3 rd Generation Partnership Project ( TM ) and may be further elaborated for the purposes of. The present document has not been subject to any approval process by the Organizational Partners and shall not be implemented. This Specification is provided for future development work within only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the TM system should be obtained via the Organizational Partners' Publications Offices.

2 2 TS V ( ) Keywords LTE, UMTS, IMS, SIP, Multimedia, Management, GSM Postal address support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: Fax: Internet 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, 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 is a Trade Mark of ETSI registered for the benefit of its Members and of the Organizational Partners LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association

3 3 TS V ( ) Contents Foreword Scope References Definitions and abbreviations Definitions Abbreviations IMS Management Object Management Object parameters General Node: /<X> /<X>/AppID /<X>/Name /<X>/ConRefs/ /<X>/ConRefs/<X> /<X>/ConRefs/<X>/ConRef /<X>/PDP_ContextOperPref /<X>/P-CSCF_Address /<X>/Timer_T /<X>/Timer_T /<X>/Timer_T /<X>/Private_user_identity /<X>/Public_user_identity_List/ /<X>/Public_user_identity_List/<X> /<X>/Public_user_identity_List/<X>/Public_user_identity /<X>/Home_network_domain_name /<X>/Ext/ /<X>/ICSI_List/ /<X>/ICSI_List/<X> /<X>/ICSI_List/<X>/ICSI A /<X>/ICSI_List /<X>/ICSI_Resource_Allocation_Mode /<X>/LBO_P-CSCF_Address/ /<X>/LBO_P-CSCF_Address/<X> /<X>/LBO_P-CSCF_Address/<X>/Address /<X>/LBO_P-CSCF_Address/<X>/AddressType /<X>/Resource_Allocation_Mode /<X>/Voice_Domain_Preference_E_UTRAN /<X>/SMS_Over_IP_Networks_Indication /<X>/Keep_Alive_Enabled /<X>/Voice_Domain_Preference_UTRAN /<X>/Mobility_Management_IMS_Voice_Termination /<X>/SigCompPolicy/ /<X>/SigCompPolicy/<X> /<X>/SigCompPolicy/<X>/AccessNetworkType /<X>/RegRetryBaseTime /<X>/RegRetryMaxTime Annex A (informative): Management Object DDF Annex B (informative): IMS Client Provisioning Application Characteristics (CP AC) B.1 General B.2 Definition of the IMS Client Provisioning Application Characteristics Annex C (informative): Change history... 36

4 4 TS V ( )

5 5 TS V ( ) Foreword This Technical Specification has been produced by the 3 rd Generation Partnership Project (). 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.

6 6 TS V ( ) 1 Scope This document defines a mobile device IMS 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 [12]. The IMS Management Object consists of relevant parameters that can be managed for the IM CN Subsystem. This includes the basic framework defined in TS [4] and TS [5], and early IMS as defined in TS [3]. This also includes relevant parameters that can be managed for the application of SMS over IP networks defined in TS [5a]. The IMS Management Object defines a repository of data into the ME including parameters that are provisioned from the ISIM application (i.e. TS [11]) or, after derivation, from the USIM application (i.e. TS [10]). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the IMS 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 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] TR : "Vocabulary for Specifications". [2] TS : "Numbering, addressing and identification". [3] TS : "Architectural requirements". [4] TS : "IP Multimedia Subsystem (IMS); Stage 2". [5] TS : "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". [5a] TS : "Support of SMS over IP networks; Stage 3". [6] Void. [7] Void. [8] RFC 1123: "Requirements for Internet Hosts -- Application and Support". [9] Void. [10] TS : "Characteristics of the USIM application". [11] TS : "Characteristics of the IP Multimedia Services Identity Module; (ISIM) Application". [12] OMA-ERELD-DM-V1_ A : "Enabler Release Definition for OMA Device Management, Version 1.2". [13] Void. [14] TS : " Architectural requirements".

7 7 TS V ( ) [15] TS : " Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". [16] TS : "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3". [17] TS : "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3". [18] RFC 5626: "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR [1] apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AC CN CP CSCF DDF DM ICSI IMS IP ISIM MO OMA P-CSCF PDP SIP UE USIM Application Characteristics Core Network Client Provisioning Call Session Control Function Device Description Framework Device Management IMS Communication Service Identifier IP Multimedia core network Subsystem Internet Protocol IM Services Identity Module Management Object Open Mobile Alliance Proxy CSCF Packet Data Protocol Session Initiation Protocol User Equipment Universal Subscriber Identity Module 4 IMS Management Object The IMS Management Object is used to manage settings of the UE for IM CN Subsystem protocols. The Management Object covers generic parameters for the IM CN subsystem. The Management Object enables the management of the settings on behalf of the end user. The Management Object Identifier is: urn:oma:mo:ext-3gpp-ims:1.0. Protocol compatibility: This MO is compatible with OMA DM 1.2. The following nodes and leaf objects are possible under the _IMS node:

8 8 TS V ( ) <X> AppID Name? ConRefs <X> + ConRef PDP_ContextOperPref P-CSCF_Address? Timer_T1 Timer_T2 Timer_T4 Private_ user_ identity Public_ user_ identity_list <X> + Public_user_ identity Home_ network_ domain_ name ICSI_List <X> * ICSI Resource_Allocation_Mode? ICSI_Resource_Allocation_Mode? LBO_P-CSCF_Address? <X> + Address Voice_Domain_Preference_E_UTRAN? AddressType Voice_Domain_Preference_UTRAN? SMS_over_IP_Networks_Indication? Keep_Alive_Enabled Mobility_Management_IMS_Voice_Termination? SigCompPolicy? <X> + AccessNetworkType RegRetryBaseTime? RegRetryMaxTime? Ext? Figure 1: The IMS Management Object 5 Management Object parameters 5.1 General This clause describes the parameters for the IMS Management Object. 5.2 Node: /<X> This interior node acts as a placeholder for one or more accounts for a fixed node.

9 9 TS V ( ) - Occurrence: OneOrMore - Format: node - Access Types: Get - Values: N/A The interior node is mandatory if the UE supports the IM CN Subsystem. Support for a UE is defined by the user agent role as defined in TS [5]. NOTE: One node is normally used. More nodes are only used in case the terminal supports multiple UICCs. 5.3 /<X>/AppID The AppID identifies the type of the application service available at the described application service access point. The value is globally unique. - Occurrence: One - Format: chr - Access Types: Get - Value: <ap2001> NOTE: The value of the _IMS/AppID is determined by OMA. 5.4 /<X>/Name The Name leaf is a name for the _IMS settings. - Occurrence: ZeroOrOne - Format: chr - Access Types: Get - Values: <User displayable name> 5.5 /<X>/ConRefs/ The ConRefs interior node is used to allow a reference to a list of network access point objects. - Occurrence: One - Format: node - Access Types: Get - Values: N/A 5.6 /<X>/ConRefs/<X> This run-time node acts as a placeholder for one or more network access point objects. - Occurrence: OneOrMore - Format: node - Access Types: Get - Values: N/A

10 10 TS V ( ) 5.7 /<X>/ConRefs/<X>/ConRef The ConRef leaf represents one or more network access point objects. - Occurrence: One - Format: chr - Values: <A network access point object> 5.8 /<X>/PDP_ContextOperPref The PDP_ContextOperPref leaf indicates an operator s preference to have a dedicated PDP context for SIP signalling. - Occurrence: One - Format: bool - Values: 0, 1 0 Indicates that the operator has no preference for a dedicated PDP context for SIP signalling. 1 Indicates that the operator has preference for a dedicated PDP context for SIP signalling. The PDP_ContextOperPref leaf indicates a preference only. TS [5] describes the normative options and the procedures for establishment of a dedicated PDP context for SIP signalling. 5.9 /<X>/P-CSCF_Address The P-CSCF_Address leaf defines an FQDN or an IPv4 address to an IPv4 P-CSCF. - Occurrence: ZeroOrOne - Format: chr - Values: <A fully qualified domain name> or IPv4 address> The P-CSCF_Address leaf shall only be used in early IMS implementations as described in TS [3]. The FQDN, or host name as defined by RFC 1123 [8], is represented as character-labels with dots as delimiters. EXAMPLE: pcscf.operator.com 5.10 /<X>/Timer_T1 The Timer_T1 leaf defines the SIP timer T1 the RTT estimate. - Occurrence: One - Format: int - Values: <The round trip time> The Timer_T1 leaf is an estimate for the round trip time in the system (UE P-CSCF). The timer value shall be given in milliseconds. The default value is recommended in TS [5]. The Timer_T1 is a 32 bits unsigned integer.

11 11 TS V ( ) EXAMPLE: 2000 (milliseconds) 5.11 /<X>/Timer_T2 The Timer_T2 leaf defines the SIP timer T2 the maximum retransmit interval for non-invite requests and INVITE responses. - Occurrence: One - Format: int - Values: < The maximum retransmit interval for non-invite requests and INVITE responses> The Timer_T2 leaf is an estimate for the maximum retransmit interval for non-invite requests and INVITE responses. The timer value shall be given in milliseconds. The default value is recommended in TS [5]. The Timer_T2 is a 32 bits unsigned integer. EXAMPLE: (milliseconds) 5.12 /<X>/Timer_T4 The Timer_T4 leaf defines the SIP timer T4 the maximum duration a message will remain in the network. - Occurrence: One - Format: int - Values: <The maximum duration a message will remain in the network> The Timer_T4 leaf is an estimate for the maximum duration a message will remain in the network. The timer value shall be given in milliseconds. The default value is recommended in TS [5]. The Timer_T4 is a 32 bits unsigned integer. EXAMPLE: (milliseconds) 5.13 /<X>/Private_user_identity The Private_user_identity leaf represents the private user identity. - Occurrence: One - Format: chr - Access Types: Get - Values: <A private user identity> NOTE: The Private_user_identity leaf value is populated by the UE using the procedures to obtain the private user identity specified in TS [5]. The format of the private user identity is defined by TS [2]. EXAMPLE: @ims.mnc015.mcc234.3gppnetwork.org 5.14 /<X>/Public_user_identity_List/ The Public_user_identity_List interior node is used to allow a reference to a list of public user identities.

12 12 TS V ( ) - Occurrence: One - Format: node - Access Types: Get - Values: N/A 5.15 /<X>/Public_user_identity_List/<X> This run-time node acts as a placeholder for one or more public user identities. - Occurrence: OneOrMore - Format: node - Access Types: Get - Values: N/A 5.16 /<X>/Public_user_identity_List/<X>/Public_user_identity The Public_user_identity leaf represents one or more public user identities. - Occurrence: One - Format: chr - Access Types: Get - Values: <A public user identity> NOTE: The Public_user_identity leaf value is populated by the UE using the procedures to obtain the public user identity specified in TS [5]. The temporary public user identity if derived is populated and stored as the topmost element in the Public_user_identity_List as specified in TS [5]. The format of the public user identity is defined by TS [2]. EXAMPLE: sip: @ims.mnc015.mcc234.3gppnetwork.org 5.17 /<X>/Home_network_domain_name The Home_network_domain_name leaf indicates the operator s home network domain. - Occurrence: One - Format: chr - Access Types: Get - Values: <The home network domain name> NOTE: The Home_network_domain_name leaf value is populated by the UE using the procedures to obtain the home network domain name specified in TS [5]. The format of the home network domain name is defined by TS [2]. EXAMPLE: ims.mnc015.mcc234.3gppnetwork.org

13 13 TS V ( ) 5.18 /<X>/Ext/ The Ext is an interior node for where the vendor specific information about the -IMS 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 - Values: N/A 5.19 /<X>/ICSI_List/ The ICSI_List interior node is used to allow a reference to a list of IMS communication service identifiers that are supported by a subscriber s network for that subscriber. - Occurrence: One - Format: node - Access Types: Get - Values: N/A 5.20 /<X>/ICSI_List/<X> This run-time node acts as a placeholder for zero or more IMS communication service identifiers that are supported by a subscriber s network for that subscriber. - Occurrence: ZeroOrMore - Format: node - Values: N/A 5.21 /<X>/ICSI_List/<X>/ICSI The ICSI leaf represents zero or more IMS communication service identifiers that are supported by a subscriber s network for that subscriber. - Occurrence: One - Format: chr - Values: <A communication services identifier> The format of the communication services identifier is defined by TS [2] 5.21A /<X>/ICSI_List /<X>/ICSI_Resource_Allocation_Mode The ICSI_Resource_Allocation_Mode leaf indicates whether UE initiates resource allocation for the media controlled by IM CN subsystem when a certain ICSI is used for the IMS session and when both UE and network can initiate resource allocation.

14 14 TS V ( ) - Occurrence: ZeroOrOne - Format: bool - Values: 0, 1 0 Indicates that the UE attempts to initiate resource allocation for the media controlled by IM CN subsystem. 1 Indicates that the UE does not attempt to initiate resource allocation for the media controlled by IM CN subsystem. NOTE: When value 1 is set, the network initiates resource allocation for the media controlled by IM CN subsystem. In absence of the parameter, UE attempts to initiate resource allocation for the media controlled by IM CN subsystem when a certain ICSI is used for the IMS session and when both UE and network can initiate resource allocation /<X>/LBO_P-CSCF_Address/ The LBO_P-CSCF_Address interior node is used to allow a reference to a list of P-CSCFs. - Occurrence: ZeroOrOne - Format: node - Access Types: Get - Values: N/A 5.23 /<X>/LBO_P-CSCF_Address/<X> This run-time node acts as a placeholder for one or more P-CSCF Addresses. Note that the order in which these nodes appear implies the priority of the address, where the first appearing has the highest priority. - Occurrence: OneOrMore - Format: node - Access Types: Get - Values: N/A 5.24 /<X>/LBO_P-CSCF_Address/<X>/Address The Address leaf defines the FQDN of a P-CSCF. - Occurrence: One - Format: chr - Values: <A fully qualified domain name>, <an IPv4 address>, <an IPv6 address> The FQDN, or host name as defined by RFC 1123 [8], is represented as character-labels with dots as delimiters. EXAMPLE: pcscf.operator.com

15 15 TS V ( ) 5.25 /<X>/LBO_P-CSCF_Address/<X>/AddressType The AddressType leaf defines the type of address stored in the Address leaf node. - Occurrence: One - Format: chr - Values: 'FQDN', 'IPv4', 'IPv6'. EXAMPLE: 'FQDN' NOTE: Populating P-CSCF address list with only entries havingaddresstype values of either 'IPv4' or 'IPv6' results in coupling of the home operator's network topology to the data stored in the IMS MO in the UE. Unless the list also contains at least one entry of type FQDN, any changes in the network topology will have to be followed by the update of the IMS MO of each affected UE before service could be restored for that UE /<X>/Resource_Allocation_Mode The Resource_Allocation_Mode leaf indicates whether UE initiates resource allocation for the media controlled by IM CN subsystem for all IMS sessions not covered by any "ICSI Resource Allocation Mode", when both UE and network can initiate resource allocation. - Occurrence: ZeroOrOne - Format: bool - Values: 0, 1 0 Indicates that the UE attempts to initiate resource allocation for the media controlled by IM CN subsystem. 1 Indicates that the UE does not attempt to initiate resource allocation for the media controlled by IM CN subsystem. NOTE: When value 1 is set, the network initiates resource allocation for the media controlled by IM CN subsystem. In absence of the parameter, UE attempts to initiate resource allocation for the media controlled by IM CN subsystem for all IMS sessions not covered by any "ICSI Resource Allocation Mode", when both UE and network can initiate resource allocation /<X>/Voice_Domain_Preference_E_UTRAN The Voice_Domain_Preference_E_UTRAN leaf indicates network operator's preference for selection of the domain to be used for voice communication services by the UE. - Occurrence: ZeroOrOne - Format: int - Values: 1, 2, 3, 4 1 Indicates that the UE does not attempt to initiate voice sessions over the IM CN Subsystem using an E-UTRAN bearer. This value equates to "CS Voice only" as described in TS [14]. 2 Indicates that the UE preferably attempts to use the CS domain to originate voice sessions. In addition, a UE, in accordance with TS [16], upon receiving a request for a session including voice, preferably attempts to

16 16 TS V ( ) use the CS domain for the audio media stream. This value equates to "CS Voice preferred, IMS PS Voice as secondary" as described in TS [14]. 3 Indicates that the UE preferably attempts to use the IM CN Subsystem using an E-UTRAN bearer to originate sessions including voice. In addition, a UE, in accordance with TS [16], upon receiving a request for a session including voice, preferably attempts to use an E-UTRAN bearer for the audio media stream. This value equates to "IMS PS Voice preferred, CS Voice as secondary" as described in TS [14]. 4 Indicates that the UE attempts to initiate voice sessions over IM CN Subsystem using an E-UTRAN bearer. In addition, a UE, upon receiving a request for a session including voice, attempts to use an E-UTRAN bearer for all the the audio media stream(s). This value equates to "IMS PS Voice only" as described in TS [14]. NOTE: For Voice_Domain_Preference_E_UTRAN leaf values 2, 3 and 4, whether the UE does attempt to use the IM CN subsystem using an E-UTRAN bearer for voice session initiation or termination is further guided by the "IMS Voice over PS session" indicator. See TS [15] and TS [16] /<X>/SMS_Over_IP_Networks_Indication The SMS_Over_IP_Networks_Indication leaf indicates network operator's preference for selection of the domain to be used for short message service (SMS) originated by the UE. - Occurrence: ZeroOrOne - Format: bool - Values: 0, 1 0 Indicates that the SMS service is not to be invoked over the IP networks. 1 Indicates that the SMS service is preferred to be invoked over the IP networks /<X>/Keep_Alive_Enabled The Keep_Alive_Enabled leaf indicates whether the UE sends keep alives. - Occurrence: One - Format: bool - Values: 0, 1 0 Indicates that the UE does not send keep alives. 1 Indicates that the UE is to send keep alives. TS [5] describes the normative behaviour for the UE sending keep alives when the Keep_Alive_Enabled leaf indicates that sending keep alives is enabled /<X>/Voice_Domain_Preference_UTRAN The Voice_Domain_Preference_UTRAN leaf indicates network operator's preference for selection of the domain to be used for voice communication services by the UE. - Occurrence: ZeroOrOne - Format: int

17 17 TS V ( ) - Values: 1, 2, 3 1 Indicates that the UE does not attempt to initiate voice sessions over the IM CN Subsystem using an UTRAN PS bearer. This value equates to "CS Voice only" as described in TS [14]. 2 Indicates that the UE preferably attempts to use the CS domain to originate voice sessions. In addition, a UE, in accordance with TS [16], upon receiving a request for a session including voice, preferably attempts to use the CS domain for the audio media stream. This value equates to "CS Voice preferred, IMS PS Voice as secondary" as described in TS [14]. 3 Indicates that the UE preferably attempts to use the IM CN Subsystem using an UTRAN PS bearer to originate sessions including voice. In addition, a UE, in accordance with TS [16], upon receiving a request for a session including voice, preferably attempts to use an UTRAN PS bearer for the audio media stream. This value equates to "IMS PS Voice preferred, CS Voice as secondary" as described in TS [14] /<X>/Mobility_Management_IMS_Voice_Termination This leaf applies if a UE utilises the services provided by EPS or GPRS to provide packet-mode communication between the UE and the IM CN subsystem. The Mobility_Management_IMS_Voice_Termination leaf indicates whether the UE mobility management performs additional procedures as specified in TS [17] and TS [15] to support terminating access domain selection by the network. - Occurrence: ZeroOrOne - Format: bool - Values: 0, 1 0 Mobility Management for IMS Voice Termination disabled. 1 Mobility Management for IMS Voice Termination enabled.

18 18 TS V ( ) 5.32 /<X>/SigCompPolicy/ This interior node indicates the presence of a home operator policy list indicating the usage of IMS procedures for SIP signalling compression used for the initial registration - Occurrence: ZeroOrOne - Format: node - Values:N/A 5.33 /<X>/SigCompPolicy/<X> This run-time node acts as a placeholder for one or more SigCompPolicy indicating the usage of IMS procedures for SIP signalling compression used for the initial registration - Occurrence: OneOrMore - Format: node - Values: N/A 5.34 /<X>/SigCompPolicy/<X>/AccessNetworkType The AccessNetworkType leaf represents an access network type to indicate that IMS procedures for SIP signalling compression are not to be used. - Occurrence: One - Format: chr - Values: <access network type> The access network type is one of the values coded according to the access-type field defined for the P-Access- Network-Info header in TS [6]. Editor s Note [TEI10][CR 0056]: It is FFS whether it is possible to disable sigcomp for certain access network types (e.g. GERAN, UTRAN) 5.35 /<X>/RegRetryBaseTime The RegRetryBaseTime leaf represents the value of the base-time parameter of the algorithm defined in subclause 4.5 of RFC 5626 [18]. - Occurrence: ZeroOrOne - Format: int - Values: <base time > The base time value shall be given in seconds.

19 19 TS V ( ) 5.36 /<X>/RegRetryMaxTime The RegRetryMaxTime leaf represents the value of the max-time parameter of the algorithm defined in subclause 4.5 of RFC 5626 [18]. - Occurrence: ZeroOrOne - Format: int - Values: <maximum time > The maximum time value shall be given in seconds. 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. <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE MgmtTree PUBLIC "-//OMA//DTD-DM-DDF 1.2//EN" " <MgmtTree> <VerDTD>1.2</VerDTD> <Man>--The device manufacturer--</man> <Mod>--The device model--</mod> <NodeName>_IMS</NodeName> <Description> IMS settings</description> <node/> <OneOrMore/> <DFTitle>The IMS Management Object.</DFTitle> <DDFName/> <NodeName>AppID</NodeName> <chr/>

20 20 TS V ( ) <One/> <DFTitle>The Application ID.</DFTitle> <NodeName>Name</NodeName> <chr/> <ZeroOrOne/> <Dynamic/> <DFTitle>User displayable name for the node.</dftitle> <NodeName>ConRefs</NodeName> <!-- The ConRefs node starts here. --> <node/> <One/> <DFTitle>A collection of network access point objects.</dftitle> <DDFName/> <NodeName/>

21 21 TS V ( ) <node/> <OneOrMore/> <Dynamic/> <DFTitle>The "name" node for a network access point object.</dftitle> <DDFName/> <NodeName>ConRef</NodeName> <chr/> <One/> <DFTitle>The ConRef (network access point object).</dftitle> <NodeName>PDP_ContextOperPref</NodeName> <bool/> <One/> <DFTitle>Indication of the operator's preference for a dedicated PDP context for IMS signalling.</dftitle>

22 22 TS V ( ) <NodeName>P-CSCF_Address</NodeName> <chr/> <ZeroOrOne/> <Dynamic/> <DFTitle>The address of the P-CSCF.</DFTitle> <NodeName>Timer_T1</NodeName> <int/> <One/> <DFTitle>RFC 3261, timer T1.</DFTitle> <NodeName>Timer_T2</NodeName> <int/> <One/>

23 23 TS V ( ) <DFTitle>RFC 3261, timer T2.</DFTitle> <NodeName>Timer_T4</NodeName> <int/> <One/> <DFTitle>RFC 3261, timer T4.</DFTitle> <NodeName>Private_user_identity</NodeName> <chr/> <One/> <DFTitle>The private user identity.</dftitle> <NodeName>Public_user_identity_List</NodeName> <!-- The Public_user_identity_List node starts here. --> <node/>

24 24 TS V ( ) <One/> <DFTitle>A collection of public user identity objects.</dftitle> <DDFName/> <NodeName/> <node/> <OneOrMore/> <Dynamic/> <DFTitle>The "name" node for a public user identity object.</dftitle> <DDFName/> <NodeName>Public_user_identity</NodeName> <chr/> <One/> <DFTitle>The public user identity.</dftitle> <NodeName>Home_network_domain_name</NodeName>

25 25 TS V ( ) <chr/> <One/> <DFTitle>The home network domain name.</dftitle> <NodeName>ICSI_List</NodeName> <!-- The ICSI_List node starts here. --> <node/> <One/> <DFTitle>A collection of IMS communication services identifier objects.</dftitle> <DDFName/> <NodeName/> <node/> <OneOrMore/> <Dynamic/> <DFTitle>The "name" node for an IMS communication services identifier object.</dftitle> <DDFName/> <NodeName>ICSI</NodeName>

26 26 TS V ( ) <chr/> <One/> <DFTitle>The IMS communication services identifier.</dftitle> <NodeName>ICSI_Resource_Allocation_Mode</NodeName> <bool/> <ZeroOrOne/> <DFTitle>Indicates whether UE initiates resource allocation for the media controlled by IM CN subsystem when a certain ICSI is used for the IMS session and when both UE and network can initiate resource allocation for IMS media.</dftitle> <NodeName>LBO_P-CSCF_Address</NodeName> <node/> <ZeroOrOne/> <Dynamic/> <DFTitle>A collection of addresses of the P-CSCF for IMS Local Breakout.</DFTitle>

27 27 TS V ( ) <DDFName/> <NodeName/> <node/> <OneOrMore/> <Dynamic/> <DFTitle>The "name" node for a P-CSCF address.</dftitle> <DDFName/> <NodeName>Address</NodeName> <chr/> <One/> <DFTitle>The P-CSCF Address.</DFTitle> <NodeName>AddressType</NodeName> <chr/> <One/>

28 28 TS V ( ) <DFTitle>The type of P-CSCF Address.</DFTitle> <NodeName>Resource_Allocation_Mode</NodeName> <bool/> <ZeroOrOne/> <DFTitle>Indicates whether UE initiates resource allocation for the media controlled by IM CN subsystem for all IMS sessions not covered by any "ICSI Resource Allocation Mode" when both UE and network can initiate resource allocation.</dftitle> <NodeName>Voice_Domain_Preference_EUTRAN</NodeName> <int/> <ZeroOrOne/> <DFTitle>Network operator's preference for voice domain for E-UTRAN according to TS </DFTitle> <NodeName>Voice_Domain_Preference_UTRAN</NodeName>

29 29 TS V ( ) <int/> <ZeroOrOne/> <DFTitle>Network operator's preference for voice domain for UTRAN according to TS </DFTitle> <NodeName>SMS_over_IP_Networks_Indication</NodeName> <bool/> <ZeroOrOne/> <DFTitle>Indicates whether the SMS service is preferred to be invoked over the IMS domain, or it shall not be invoked over the IMS domain.</dftitle> <NodeName>Keep_Alive_Enabled</NodeName> <bool/> <One/> <DFTitle>Indication whether the sending of keep alives by the UE is enabled.</dftitle>

30 30 TS V ( ) <NodeName>Mobility_Management_IMS_Voice_Termination</NodeName> <bool/> <ZeroOrOne/> <DFTitle>Indicates whether the UE mobility management performs additional procedures as specified in TS and TS to support terminating access domain selection by the network.</dftitle> <NodeName>SigCompPolicy</NodeName> <node/> <ZeroOrOne/> <Dynamic/> <DFTitle>Interior node indicating the presence of a home operator policy list indicating the usage of IMS procedures for SIP signalling compression used for the initial registration.</dftitle> <DDFName/> <NodeName/> <node/> <OneOrMore/>

31 31 TS V ( ) <Dynamic/> <DFTitle>The "name" node for a SigCompPolicy.</DFTitle> <DDFName/> <NodeName>AccessNetworkType</NodeName> <chr/> <One/> <DFTitle>The Access Network Type.</DFTitle> <NodeName> RegRetryBaseTime</NodeName> <int/> <ZeroOrOne/> <DFTitle> Represents the value of the base-time parameter of the algorithm defined in subclause 4.5 of RFC 5626</DFTitle> <NodeName> RegRetryMaxTime</NodeName>

32 32 TS V ( ) <int/> <ZeroOrOne/> <DFTitle> Represents the value of the max-time parameter of the algorithm defined in subclause 4.5 of RFC 5626 </DFTitle> <NodeName>Ext</NodeName> <!-- The Extension node starts here. --> <node/> <ZeroOrOne/> <Dynamic/> <DFTitle>A collection of all Extension objects.</dftitle> <DDFName/> </MgmtTree>

33 33 TS V ( ) Annex B (informative): IMS Client Provisioning Application Characteristics (CP AC) B.1 General This annex defines the IMS Client Provisioning Application Characteristics (CP AC) as supported in the Enabler Release Definition OMA-ERELD-DM-V1_2 [12]. If the initial IMS parameters cannot be provisioned as specified in OMA-ERELD-DM-V1_2 [12], initial IMS parameters can be provisioned using OMA CP. If a client is provisioned with IMS related parameters by both OMA DM and OMA CP, the client will use the IMS related parameters provisioned by OMA DM. B.2 Definition of the IMS Client Provisioning Application Characteristics IDENTIFYING INFORMATION ####################### APPID: _IMS. APPID type: OMNA. Owner: CT1 Working Group. Contact: TSG CT WG1. Registration version: 1.0. Registration timestamp: Application description: IP Multimedia Subsystem. Application reference: IMS specifications, TS , TS and TS URL: WELL-KNOWN PARAMETERS ##################### Characteristic/name: APPLICATION/APPID. Status: Required. Occurs: 1/1. Default value: None. Used values: N/A. Interpretation: The Application ID - this is the same as for the MO DDF Characteristic/name: APPLICATION/NAME. Status: Required. Occurs: 0/1. Default value: ap2001. Used values: ap2001. Interpretation: User displayable name for the application Characteristic/name: APPLICATION/PROVIDER-ID. Status: Required. Occurs: 0/1. Default value: None. Used values: N/A. Interpretation: An identifier for the IMS service provider that provides the client provisioning. This is used to distinguish between settings for different IMS service providers within a client.

34 34 TS V ( ) Characteristic/name: APPLICATION/APPREF. Status: Required. Occurs: 0/1. Default value: None. Used values: N/A. Interpretation: The APPREF parameter defines the reference identity of the IMS APPLICATION characteristic. The APPREF parameter value is unique in the scope of the provisioning document. The TO-APPREF parameter included in other APPLICATION characteristic can be used for referring to the IMS APPLICATION characteristic Characteristic/name: APPLICATION/TO-NAPID. Status: Required. Occurs: 1/1. Default value: None. Used values: N/A. Interpretation: The reference to the connectivity characteristics used for IMS APPLICATION-SPECIFIC PARAMETERS ############################### Characteristic/name: APPLICATION/PDP_CONTEXTOPERPREF. Status: Required. Occurs: 1/1. Default value: None. Used values: 0 and 1. Interpretation: Indication of the operator s preference for a dedicated PDP context for IMS signalling Characteristic/name: APPLICATION/P-CSCF_ADDRESS. Status: Optional. Occurs: 0/1. Default value: 0. Used values: N/A. Interpretation: The address of the P-CSCF in FQDN format or an IPv4 address Characteristic/name: APPLICATION/TIMER_T1. Status: Required. Occurs: 0/1. Default value: N/A. Used values: Integer. Interpretation: RFC 3261, timer T Characteristic/name: APPLICATION/TIMER_T2. Status: Required. Occurs: 0/1. Default value: N/A. Used values: Integer. Interpretation: RFC 3261, timer T Characteristic/parameter: APPLICATION/TIMER_T4. Status: Required. Occurs: 0/1. Default value: N/A. Used values: Integer. Interpretation: RFC 3261, timer T PARAMETER VALUES ################ Characteristic/name/parameter: APPLICATION/PDP_CONTEXTOPERPREF/0. Status: Optional. Interpretation: Indicates that the operator has no preference for a dedicated PDP context for SIP signalling Characteristic/name/parameter: APPLICATION/PDP_CONTEXTOPERPREF/1.

35 35 TS V ( ) Status: Optional. Interpretation: Indicates that the operator has preference for a dedicated PDP context for SIP signalling APPLICATION-SPECIFIC PARAMETERS ############################### Characteristic/name: APPLICATION/KEEP_ALIVE_ENABLED. Status: Required. Occurs: 1/1. Default value: None. Used values: 0 and 1. Interpretation: Indication whether the sending of keep alives by the UE is enabled ###END###

36 36 TS V ( ) Annex C (informative): Change history Change history Date TSG # TSG Doc. CR R Subject/Comment Old New WG doc ev Version 0.0.1: Preliminary proposal Version 0.0.2: Version after CN1 # Version 1.0.0: Version after CN1#36 and editorial corrections Version 1.1.0: Version after CN1#37 and editorial corrections N N TSG- NP- Version created by MCC Version approved in TSG-27. V6.0.0 created TSG Corrections to TS due to comments from OMA DM C TSG Miscellaneous corrections C TSG Removal of APN from the IMS MO C TSG Corrections for the IMS Management Object C TSG TSG IMS MO and ISIM usage clarification C P-CSCF address used in early IMS implementations C TSG Adding Client Provisioning Application Characteristics to IMS MO Rel C TSG TSG TSG TSG TSG AppID for the _IMS MO determined by OMA C Corrections to client provisioning for the IMS MO C Value range for int-parameters C Support for DM 1.2 and higher in IMS MO C Management Object identifier for the IMS MO in rel C TSG TSG TSG TSG TSG IMS MO Extension for Communication Service Identifier C MO ICSI list is subscription based C Correction of OMA DM reference C Changes to support IMS Local Breakout C MO DDF XML bug fix C TSG Adding possibility to provision mode of the resource allocation used for IMS media C TSG TSG DFTitle update C Defining configuration data for the voice domain selection C

37 37 TS V ( ) TSG TSG TSG Defining configuration data for the SMS domain selection C Corrections in IMS MO C IMS MO Changes for Keep alive C TSG Correction to take into account Voice Domain Selection for Iu mode C TSG TSG TSG TSG Upgrade to Rel Correct terminating domain selection for IMS voice Ues Correction of names for voice domain preference C SigComp disabling C TSG MO for providing max-time and base-time registration parameters provision C