5 Management Object parameters

24.1673GPP3GPP IMS Management Object (MO)Release 18Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1 General

This clause describes the parameters for the 3GPP IMS Management Object.

5.2 Node: /<X>

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 the IM CN Subsystem. Support for a UE is defined by the user agent role as defined in 3GPP TS 24.229 [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 3GPP_IMS/AppID is determined by OMA.

5.4 /<X>/Name

The Name leaf is a name for the 3GPP_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

5.7 /<X>/ConRefs/<X>/ConRef

The ConRef leaf represents a network access point object.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– 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

– Access Types: Get, Replace

– 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. 3GPP TS 24.229 [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

– Access Types: Get, Replace

– Values: <an FQDN> or <an IPv4 address>

The P-CSCF_Address leaf shall only be used in early IMS implementations as described in 3GPP TS 23.221 [3].

The FQDN, or host name as defined in subclause 25.1 of RFC 3261 [23].

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

– Access Types: Get, Replace

– 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 3GPP TS 24.229 [5]. The Timer_T1 is a 32 bits unsigned integer.

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

– Access Types: Get, Replace

– 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 3GPP TS 24.229 [5]. The Timer_T2 is a 32 bits unsigned integer.

EXAMPLE: 16000 (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

– Access Types: Get, Replace

– 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 3GPP TS 24.229 [5]. The Timer_T4 is a 32 bits unsigned integer.

EXAMPLE: 17000 (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 3GPP TS 24.229 [5].

The format of the private user identity is defined by 3GPP TS 23.003 [2].

EXAMPLE: 234150999999999@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.

– 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 a public user identity.

– 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 3GPP TS 24.229 [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 3GPP TS 24.229 [5].

The format of the public user identity is defined by 3GPP TS 23.003 [2].

EXAMPLE: sip: 234150999999999@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 3GPP TS 24.229 [5].

The format of the home network domain name is defined by 3GPP TS 23.003 [2].

EXAMPLE: ims.mnc015.mcc234.3gppnetwork.org

5.18 /<X>/Ext/

The Ext is an interior node for where the vendor specific information about the 3GPP-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

– Access Types: Get, Replace

– Values: N/A

5.21 /<X>/ICSI_List/<X>/ICSI

The ICSI leaf represents one IMS communication service identifier that is supported by a subscriber’s network for that subscriber.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: <A communication services identifier>

The format of the communication services identifier is defined by 3GPP TS 24.229 [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.

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– 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.

5.22 /<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, Replace

– 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, the IPv4 address or the IPv6 address of a P-CSCF.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: <an FQDN>, <an IPv4 address>, <an IPv6 address>

The FQDN, or host name as defined in subclause 25.1 of RFC 3261 [23].

EXAMPLE: pcscf.operator.com

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

– Access Types: Get, Replace

– 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.

5.26 /<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

– Access Types: Get, Replace

– 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.

5.27 /<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

– Access Types: Get, Replace

– 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 3GPP TS 23.221 [3].

2 – Indicates that the UE preferably attempts to use the CS domain to originate voice sessions. In addition, a UE, in accordance with 3GPP TS 24.292 [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 3GPP TS 23.221 [3].

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 3GPP TS 24.292 [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 3GPP TS 23.221 [3].

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 3GPP TS 23.221 [3].

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 3GPP TS 24.301 [15] and 3GPP TS 24.292 [16].

5.28 /<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

– Access Types: Get, Replace

– 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.

5.29 /<X>/Keep_Alive_Enabled

The Keep_Alive_Enabled leaf indicates whether the UE sends keep alives.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the UE does not send keep alives.

1 – Indicates that the UE is to send keep alives.

3GPP TS 24.229 [5] describes the normative behaviour for the UE sending keep alives when the Keep_Alive_Enabled leaf indicates that sending keep alives is enabled.

5.30 /<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

– Access Types: Get, Replace

– 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 3GPP TS 23.221 [3].

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 3GPP TS 24.292 [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 3GPP TS 23.221 [3].

5.31 /<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 3GPP TS 24.008 [17] and 3GPP TS 24.301 [15] to support terminating access domain selection by the network.

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Mobility Management for IMS Voice Termination disabled.

1 – Mobility Management for IMS Voice Termination enabled.

5.32 void

5.33 void

5.34 void

5.35 /<X>/RegRetryBaseTime

The RegRetryBaseTime leaf represents the value of the base-time (if all failed) parameter of the algorithm defined in subclause 4.5 of RFC 5626 [18].

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <base-time>

The base-time value shall be given in seconds.

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

– Access Types: Get, Replace

– Values: <maximum time>

The maximum time value shall be given in seconds.

5.37 /<X>/PhoneContext_List/

The PhoneContext_List interior node is used to allow a reference to a list of phone-context parameter values for other local numbers, than geo-local or home-local numbers, as defined in subclause 5.1.2A.1.5 of 3GPP TS 24.229 [5].

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.38 /<X>/PhoneContext_List/<X>

This run-time node acts as a placeholder for one or more phone-context parameter values.

– Occurrence: OneOrMore

– Format: node

– Access Types: Get

– Values: N/A

5.39 /<X>/PhoneContext_List/<X>/PhoneContext

The PhoneContext leaf defines the value of the phone-context parameter.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: <phone-context>

5.40 /<X>/PhoneContext_List/<X>/Public_user_identity

The Public_user_identity leaf defines zero or more public user identities to which the phone-context parameter value is associated.

– Occurrence: OneOrMore

– Format: chr

– Access Types: Get, Replace

– Values: <A public user identity>

5.41 /<X>/SS_domain_setting

The SS_domain_setting leaf indicates the network operator’s preference for the selection of the domain used by the UE when performing supplementary services (SS) setting control for voice services.

NOTE 1: The SS_domain_setting leaf does not provide a mechanism for the network operator to select the domain used for mobile originating USSD requests.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: 0, 1, 2

0 – Indicates that the UE only uses the PS domain for SS setting control

1 – Indicates that the UE only uses the CS domain for SS setting control

2 – Indicates that the UE uses the PS domain for SS setting control when the PS domain is being used by the UE for voice services, and the UE uses the CS domain for SS setting control when the CS domain is being used by the UE for voice services

The network operator can select the preference for the selection of the domain used by the UE when performing supplementary services (SS) setting control for voice services, according to the domain(s) where the supplementary services are provisioned. For example:

– if the supplementary services are provisioned only in the PS domain, the UE can be restricted to configure only the supplementary services part of the IMS multimedia telephony communication service by setting value "0";

NOTE 2: If voice services are centralized in IMS, and if the UE accesses the CS domain for voice services, the supplementary services part of the IMS multimedia telephony communication service can also be configured in the PS domain by the UE.

– if the supplementary services are provisioned only in the CS domain, the UE can be restricted to configure only the supplementary services for CS speech by setting value "1"; and

NOTE 3: If the supplementary services are provisioned in the PS domain, then the supplementary services part of the IMS multimedia telephony communication service can also be configured by a UE accessing the CS domain towards an MSC server enhanced for ICS implementing the interworking between call independent supplementary service signalling and the XCAP application usage for manipulating supplementary services data, as specified in 3GPP TS 29.292 [22].

– if the supplementary services are provisioned in both the CS domain and PS domain, then value "2" can be set to restrict the UE to:

a) configure the supplementary services for CS speech when the UE is using the CS domain for voice services; and

b) configure the supplementary services part of the IMS multimedia telephony communication service when the UE is using the PS domain for voice services.

5.42 /<X>/PS_domain_IMS_SS_control_preference

The PS_domain_IMS_SS_control_preference leaf provides a means to define the method for which Supplementary Services as defined by 3GPP TS 22.173 [19] are controlled by the UE when SS setting control is to be invoked over the PS domain.

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the IMS SS setting control for services defined by 3GPP TS 22.173 [19] is to be invoked using XCAP/Ut as defined by 3GPP TS 24.623 [20]

1 – Indicates that the IMS SS setting control for services defined by 3GPP TS 22.173 [19] is to be invoked using SIP-based user configuration as defined by 3GPP TS 24.238 [21]

NOTE: The usage of other methods for controlling the IMS SS setting control are out of the scope of this parameter.

The UE uses the information stored in the PS_domain_IMS_SS_control_preference leaf either when the SS_domain_setting leaf is set to "0", or when SS_domain_setting is set to "2" and the domain currently used for voice services is the PS domain.

5.43 /<X>/Media_type_restriction_policy

This interior node describes the media type restriction policy.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

The media type restriction policy consists of zero or more media type restriction policy parts. Each media type restriction policy part is described by a child node.

A media type is restricted from inclusion in a SDP message according to the media type restriction policy indicated by this interior node, if at least one child node restricts inclusion of the media type in the SDP message.

The media type restriction policy does not influence SDP messages exchanged in an IMS emergency call.

5.44 /<X>/Media_type_restriction_policy/<X>/

This interior node describes the media type restriction policy part.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

The media type restriction policy part consists of a mandatory media type in the Media_type child node and zero or more conditions in child nodes other than the Media_type child node.

NOTE: If the Media_type child node is the sole child node, the media type indicated in the Media_type child node is restricted from inclusion in a SDP message according to the media type restriction policy part in all circumstances.

The media type restriction policy part indicated by this interior node restricts inclusion of a media type in an SDP message if:

a) the media type is indicated in the Media_type child node;

b) the following is true:

1) this node does not have an IP-CAN child node; or

2) the following is true:

A) the SDP message contains an "m=" SDP line of the media type;

B) the "m=" SDP line is associated with a "c=" SDP line;

C) the "c=" SDP line indicates an IP address;

D) the IP address is associated with an IP-CAN bearer; and

E) the IP-CAN bearer is of an IP-CAN indicated in the IP-CAN child node;

c) the following is true:

1) this node does not have an ICSI child node; or

2) the SDP message describes session offered or established by SIP signalling related to an IMS communication service identified in the ICSI child node; and

d) the following is true:

1) this node does not have a Roaming child node; or

2) the following is true:

A) this node has a Roaming child node;

B) the SDP message contains an "m=" SDP line of the media type;

C) the "m=" SDP line is associated with a "c=" SDP line;

D) the "c=" SDP line indicates an IP address;

E) the IP address is associated with an IP-CAN bearer; and

F) the UE roams in the IP-CAN of the IP-CAN bearer.

5.45 /<X>/Media_type_restriction_policy/<X>/Media_type

This leaf indicates a restriction applicable for a media type.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: a media type as described in RFC 4566 [rfc4566], subclause 8.2.1

5.46 /<X>/Media_type_restriction_policy/<X>/IP-CAN

This leaf indicates a restriction applicable for an IP-CAN.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: one of the values specified in table 5.46-1.

Table 5.46-1: Possible values for the IP-CAN leaf

Value	Description
1	Evolved Packet System (EPS)
2	Evolved Packet Core (EPC) via Wireless Local Access Network (WLAN)
3	General Packet Radio Service (GPRS)
4	5G core (5GC) via NG-RAN
5	5G core (5GC) via non-3GPP access
6	5G core (5GC) via E-UTRA
7	5G core (5GC) via NR
0, 8-255	Not assigned

5.47 /<X>/Media_type_restriction_policy/<X>/ICSI

This leaf indicates a restriction applicable for an ICSI.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.48 /<X>/Media_type_restriction_policy/<X>/Roaming

This leaf indicates a restriction applicable when media are transported to or from an IP-CAN where the UE roams.

– Occurrence: ZeroOrOne

– Format: null

– Access Types: Get, Replace

– Values: null

5.49 /<X>/Default_EPS_bearer_context_usage_restriction_policy

This interior node describes the default EPS bearer context usage restriction policy.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.50 /<X>/Default_EPS_bearer_context_usage_restriction_policy/<X>/

This interior node describes the default EPS bearer context usage restriction policy part.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.51 /<X>/Default_EPS_bearer_context_usage_restriction_policy/<X>/Media_type

This leaf indicates a media type condition.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: a media type as described in RFC 4566 [rfc4566], subclause 8.2.1

5.52 /<X>/Default_EPS_bearer_context_usage_restriction_policy/<X>/ICSI

This leaf indicates an ICSI condition.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.53 /<X>/Reliable_18x_policy

This interior node describes the reliable 18x policy. In the absence of this node, the UE sends SIP 18x response reliably or not up to the implementation.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

NOTE 1: If the INVITE request is subject to an IMS communication service which does not match the ICSI condition in any of the reliable 18x policy parts and if there is no reliable 18x policy part without ICSI, it is IMS communication service and/or implemention dependent whether to send the SIP 18x responses reliably.

NOTE 2: Some IMS communication services require that SIP 18x responses are not sent reliably. Mandating that the UE send all SIP 18x responses reliably could prevent those IMS communication services from operating correctly.

5.54 /<X>/Reliable_18x_policy/<X>/

This interior node describes the reliable 18x policy part.

– Occurrence: OneOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.55 /<X>/Reliable_18x_policy/<X>/ICSI

This leaf indicates an ICSI condition.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

In absence of the parameter, UE applies the reliable 18x policy indicated in the Send_18x_Reliably parameter on all IMS services.

5.56 /<X>/Reliable_18x_policy/<X>/Send_18x_Reliably

This leaf indicates whether the SIP 18x responses (other than SIP 183 response) against an INVITE request subject to the IMS service indicated in the ICSI leaf are to be sent reliably.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the SIP 18x responses (other than SIP 183 response) are to be sent unreliably.

1 – Indicates that the SIP 18x responses (other than SIP 183 response) are to be sent reliably.

5.57 /<X>/EPS_initial_attach_ConRefs

This interior node describes the policy on the PDN connection established during the EPS attach procedure.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.58 /<X>/EPS_initial_attach_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

5.59 /<X>/EPS_initial_attach_ConRefs/<X>/ConRef

The ConRef leaf represents a network access point object.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: <A network access point object>

5.60 /<X>/Precondition_disabling_policy

This leaf contains the precondition disabling policy.

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– Values: one of the values specified in table 5.60-1.

Table 5.60-1: Possible values for the Precondition_disabling_policy leaf

Value	Description
0	the UE is allowed to use the precondition mechanism
1	the UE is not allowed to use the precondition mechanism

The default value is ‘0’.

5.61 /<X>/Timer_Emerg-reg

The optional Timer_Emerg-reg leaf defines the operator’s emergency registration request timeout policy.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <The maximum time before the UE consider the emergency REGISTER request or the emergency call attempt as failed.>

The Timer_Emerg-reg leaf is the maximum time from deciding that an emergency service is to be established via the IM CN subsystem until completion of the emergency registration procedure, including any required IP-CAN procedures. Upon timer expiry the UE considers the emergency REGISTER request or the emergency call attempt as failed (see 3GPP TS 24.229 [5]). The timer value shall be given in seconds. The configurable value is between 8 and 20 seconds as defined in 3GPP TS 24.229 [5]. The Timer_Emerg-reg is a 16 bits unsigned integer.

NOTE: If the maximum time is set to a value smaller than 10 seconds, the Timer_Emerg-reg can expire before the supervision timer of a necessary IP-CAN procedure, e.g. an EPS attach procedure (see 3GPP TS 24.301 [3]), expires.

5.62 /<X>/Policy_on_local_numbers

This interior node describes the policy on local numbers.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.63 /<X>/Policy_on_local_numbers/<X>/

This interior node describes a part of the policy on local numbers.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.64 /<X>/Policy_on_local_numbers/<X>/ICSI

This leaf indicates an ICSI.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.65 /<X>/Policy_on_local_numbers/<X>/Local_number_type

This leaf indicates a local number type.

– Occurrence: One

– Format: int

– Access Types: Get, Replace

– Values: values indicate in table 5.65-1.

Table 5.65-1: Possible values for the Local_number_type leaf

Value	Description
1	home-local number
2	geo-local number
0, 3-255	not assigned

5.66 /<X>/3GPP_PS_data_off

The interior node contains configuration parameters for 3GPP PS data off.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.67 /<X>/3GPP_PS_data_off/SMSoIP_exempt

The leaf indicates whether the SMS over IP is a 3GPP PS data off exempt service.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the SMS over IP is not a 3GPP PS data off exempt service.

1 – Indicates that the SMS over IP is a 3GPP PS data off exempt service.

NOTE: This MO is used when the UE is in the home PLMN or the EHPLMN, or the SMSoIP_roaming_exempt node is not configured when the UE is in the VPLMN.

5.67a /<X>/3GPP_PS_data_off/SMSoIP_roaming_exempt

The leaf indicates whether the SMS over IP is a 3GPP PS data off exempt service when the UE is in the VPLMN:

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the SMS over IP is not a 3GPP PS data off roaming exempt service.

1 – Indicates that the SMS over IP is a 3GPP PS data off roaming exempt service.

5.68 /<X>/3GPP_PS_data_off/non_3GPP_ICSIs_exempt

The interior node contains IMS communication service identifiers of the IMS communication services not defined by 3GPP which are 3GPP PS data off exempt services.

– Occurrence: One

– Format: node

– Access Types: Get, Replace

– Values: N/A

NOTE: This MO is used when the UE is in the home PLMN or the EHPLMN, or the non_3GPP_ICSIs_roaming_exempt node is not configured when the UE is in the VPLMN.

5.68a /<X>/3GPP_PS_data_off/non_3GPP_ICSIs_roaming_exempt

The interior node contains IMS communication service identifiers of the IMS communication services not defined by 3GPP which are 3GPP PS data off exempt services when the UE is in the VPLMN.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.69 /<X>/3GPP_PS_data_off/non_3GPP_ICSIs_exempt/<X>

The interior node contains an IMS communication service identifier of the IMS communication service not defined by 3GPP which is a 3GPP PS data off exempt service.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.69a /<X>/3GPP_PS_data_off/non_3GPP_ICSIs_roaming_exempt/<X>

The interior node contains an IMS communication service identifier of the IMS communication service not defined by 3GPP which is a 3GPP PS data off exempt service when the UE is in the VPLMN.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.70 /<X>/3GPP_PS_data_off/non_3GPP_ICSIs_exempt/<X>/non_3GPP_ICSI_exempt

The interior node contains an IMS communication service identifier of the IMS communication service not defined by 3GPP which is a 3GPP PS data off exempt service.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.70a /<X>/3GPP_PS_data_off/non_3GPP_ICSIs_roaming_exempt/<X>/non_3GPP_ICSI_roaming_exempt

The interior node contains an IMS communication service identifier of the IMS communication service not defined by 3GPP which is a 3GPP PS data off exempt service when the UE is in the VPLMN.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.71 /<X>/SMSoIP_usage_policy

The SMSoIP_usage_policy leaf indicates the policy on usage of SMS over IP.

If the SMS_Over_IP_Networks_Indication leaf specified in subclause 5.28 is set to the "0: Indicates that the SMS service is not to be invoked over the IP networks" value, then the SMSoIP_usage_policy leaf has no effect.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: 0, 1, 2

0 – Indicates that SMS over IP is used only if voice over PS is available and only on the IP-CAN bearer that is used for the transport of SIP signalling associated with voice over PS.

1 – Indicates that SMS over IP is used only if voice over PS is available and on any IP-CAN bearer.

2 – Indicates that SMS over IP is used irrespective of whether voice over PS is available and on any IP-CAN bearer.

5.72 Void

5.73 /<X>/Timer_Emerg-request

The optional Timer_Emerg-request leaf defines the operator’s emergency request timeout policy.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <The maximum time between sending of an initial INVITE request for an emergency session and receiving an 18x response to the INVITE request.>

The Timer_Emerg-request leaf is the maximum time between sending of an initial INVITE request for an emergency session and receiving an 18x response to the INVITE request. The timer value shall be given in seconds. The configurable value is between 5 and 15 seconds as defined in 3GPP TS 24.229 [5]. The Timer_Emerg-request is an 8 bits unsigned integer.

5.74 /<X>/IMS_Registration_Policy

The interior node contains configuration parameters for the IMS registration handling.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.75 /<X>/IMS_Registration_Policy/<X>/

The interior node describes the IMS registration handling policy part.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

The IMS registration handling policy part consists of a mandatory Stay_Registered_When_VoPS_Not_Supported child node indicating whether the UE stays registered when VoPS is not supported. If it is set to false, the Deregistration_Timer child node indicates the time duration in second before deregistration.

5.76 /<X>/IMS_Registration_Policy/<X>/Stay_Registered_When_VoPS_Not_Supported

The leaf indicates whether the UE stays registered or not from IMS when moving to area where IMS Voice Over PS Session is not supported.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

1 – Indicates that the UE maintains the registration as required for IMS services;

0 – Indicates that the UE deregisters from IMS as defined in annex B, annex L, annex U and annex W in 3GPP TS 24.229 [5].

NOTE: The value 1 implicitly indicates that there is no services other than voice is to be provided based on IMS, thus if the value 1 is set then the UE does not perform the initial IMS registration when camps on the network and gets the indication that IMS voice over PS session is not supported.

5.77 /<X>/IMS_Registration_Policy/<X>/Deregistration_Timer

The Deregistration_Timer leaf indicates the time before deregistration on the UE when moving to area where IMS Voice Over PS Session is not supported.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <The time a UE stays registered when VoPS_Not_Supported is received>

The use of this leaf is as defined in annex B, annex L, annex U and annex W in 3GPP TS 24.229 [5]. The timer value shall be given in seconds. The Deregistration_Timer is a 16 bits unsigned integer.

NOTE 1: Setting the value ‘0’ leads to immediate deregistration

NOTE 2: Setting small timer values can lead to frequent registrations and deregistrations with significant impact on UE battery life and network load especially in areas of fringe coverage for IMS Voice Over PS.

5.78 /<X>/Allow_Handover_PDN_connection_WLAN_and_EPS

The leaf indicates options for when a UE roaming in a VPLMN, is allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: 0, 1, 2

0 – Indicates that a UE roaming in a VPLMN and having an ongoing session, is not allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS.

1 – Indicates that a UE roaming in a VPLMN and having an ongoing session, is allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS;

2 – Indicates that a UE roaming in a VPLMN is not allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS using handover procedures, irrespective of if the UE is in a session or not.

NOTE 1: When handover is restricted a UE can select another IP-CAN type in idle mode, e.g. due to UE domain preference using the procedures to re-establish PDN connectivity for IMS access specified in 3GPP TS 24.229 [5].

NOTE 2: If this MO is configured, it is assumed that ANDSF objects are configured consistent with this MO.

5.79 /<X>/Default_QoS_Flow_usage_restriction_policy

This interior node describes the default QoS Flow usage restriction policy. The policy is used to control whether the UE is allowed to send media on the 5G QoS Flow associated with the default QoS rule.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.80 /<X>/Default_QoS_Flow_usage_restriction_policy/<X>/

This interior node describes the default QoS Flow usage restriction policy part.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.81 /<X>/Default_QoS_Flow_usage_restriction_policy/<X>/Media_type

This leaf indicates a media type condition.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: a media type as described in RFC 4566 [24], subclause 8.2.1

5.82 /<X>/Default_QoS_Flow_usage_restriction_policy/<X>/ICSI

This leaf indicates an ICSI condition.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.83 /<X>/Timer_Emerg-non3gpp

The optional Timer_Emerg-non3gpp leaf defines the time before setup an emergency call over the available non-3GPP access when no 3GPP access supporting emergency call is found.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <The maximum time for searching a 3GPP access usable for establishing an emergency call before performing the emergency call over the available non-3GPP access>

The use of this leaf is as defined in annex R and annex W of 3GPP TS 24.229 [5]. The timer configurable value is between 5 and 20 seconds as defined in subclause 7.8 of 3GPP TS 24.229 [5].

5.84 /<X>/Session_Timer_Policy

The interior node contains configuration parameters for the Session Timer policy.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

In the absence of this node, the Session_Timer policy is up to the implementation.

5.85 /<X>/Session_Timer_Policy/Session_Timer_Support

The leaf indicates whether the UE supports the Session Timer extension as per RFC 4028 [26] and 3GPP TS 24.229 [5].

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

1 – Indicates that the UE supports the Session Timer extension.

0 – Indicates that the UE does not support the Session Timer extension.

NOTE: The value 1 indicates that the UE supports the capability mentioned in table A.4 of 3GPP TS 24.229 [5] and includes the necessary header during call handling as per the procedures defined in RFC 4028 [26].

5.86 /<X>/Session_Timer_Policy/Session_Timer_Initial_Interval

The leaf indicates the initial timer interval value for specifying the header field value of the Session-Expires header when sending initial INVITE request or when responding with 200 (OK) response to the received INVITE request.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <Session Timer initial interval value>

The timer value shall be given in seconds. The Session_Timer_Initial_Interval is a 16 bits unsigned integer.

NOTE: The minimum value for the Session_Timer_Initial_Interval is 90 seconds as per RFC 4028 [26].

EXAMPLE: 1800 (seconds)

5.87 /<X>/Session_Timer_Policy/Session_Timer_Initial_MT_Refresher

The leaf indicates the value of the refresher parameter in the Session-Expires header to be used by the terminating UE when adding the refresher parameter for the first time.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: <value for refresher parameter>

Possible values for refresher parameter in Session-Expires header are defined by RFC 4028 [26].

EXAMPLE: uac

5.88 /<X>/Access_Point_Name_Parameter_Reading_Rule

The UE can get the APN name from multiple sources. For example UICC via EF_ACL parameter, Network provided or User specified. The values provided by these different sources may differ. The optional Access_Point_Name_Parameter_Reading_Rule leaf defines which input source should the UE use to read the APN parameters.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: 0, 1, 2

0 – Indicates that UE should use APN values provided by UICC as per 3GPP TS 31.102 [10] rules.

1 – Indicates that UE should use values provided by network

2 – Indicates that UE should use the values provided by user via UE settings menu or any other method

In the absence of this node, which source to use for reading APN parameter is implementation specific.

5.89 /<X>/Allow_Handover_PDU_session_non-3GPP_and_NG-RAN

The leaf indicates options for when a UE is allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RAN.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: 0, 1, 2, 3, 4, 5

0 – Indicates that a UE having an ongoing IMS session, is not allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RAN and that a UE which does not have an ongoing IMS session is allowed to transfer the PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN.

1 – Indicates that a UE having an ongoing IMS session, is allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RAN and that a UE which does not have an ongoing IMS session is allowed to transfer the PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN;

2 – Indicates that a UE is not allowed to transfer a PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN, irrespective of if the UE has an ongoing IMS session or not.

3 – Indicates that a UE roaming in a VPLMN and having an ongoing IMS session, is not allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RANand that a UE which is roaming in a VPLMN and does not have an ongoing IMS session is allowed to transfer the PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN.

4 – Indicates that a UE roaming in a VPLMN and having an ongoing IMS session, is allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RANand that a UE which is roaming in a VPLMN and does not have an ongoing IMS session is allowed to transfer the PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN;

5 – Indicates that a UE roaming in a VPLMN is not allowed to transfer a PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN, irrespective of if the UE has an ongoing IMS session or not.

NOTE 1: If the value of this leaf is set to 2, a UE can select another IP-CAN type in idle mode, e.g. due to UE domain preference using the procedures to re-establish the PDU session providing access to IMS as specified in 3GPP TS 24.229 [5].

NOTE 2: If this MO is configured, it is assumed that the URSP rules are configured consistently with this MO.

5.90 /<X>/Allow_Handover_PDN_connection_non-3GPP_and_NG-RAN

The leaf indicates options for when a UE is allowed to transfer the PDN connection providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RAN.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: 0, 1, 2, 3, 4, 5

0 – Indicates that a UE having an ongoing IMS session, is not allowed to transfer the PDN connection providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RANand that a UE does not have an ongoing IMS session is allowed to transfer the PDN connection providing access to IMS, if any, between EPC via non-3GPP access and 5GCN via NG-RAN.

1 – Indicates that a UE having an ongoing IMS session, is allowed to transfer the PDN connection providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RANand that a UE does not have an ongoing IMS session is allowed to transfer the PDN connection providing access to IMS, if any, between EPC via non-3GPP access and 5GCN via NG-RAN;

2 – Indicates that a UE is not allowed to transfer a PDN connection providing access to IMS, if any, between EPC via non-3GPP access and 5GCN via NG-RAN, irrespective of if the UE has an ongoing IMS session or not.

3 – Indicates that a UE roaming in a VPLMN and having an ongoing IMS session, is not allowed to transfer the PDN connection providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RANand that a UE which is roaming in a VPLMN and does not have an ongoing IMS session is allowed to transfer the PDN connection providing access to IMS, if any, between EPC via non-3GPP access and 5GCN via NG-RAN.

4 – Indicates that a UE roaming in a VPLMN and having an ongoing IMS session, is allowed to transfer the PDN connection providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RANand that a UE which is roaming in a VPLMN and does not have an ongoing IMS session is allowed to transfer the PDN connection providing access to IMS, if any, between EPC via non-3GPP access and 5GCN via NG-RAN;

5 – Indicates that a UE roaming in a VPLMN is not allowed to transfer a PDN connection providing access to IMS, if any, between EPC via non-3GPP access and 5GCN via NG-RAN, irrespective of if the UE has an ongoing IMS session or not.

NOTE 1: If the value of this leaf is set to 2, a UE can select another IP-CAN type in idle mode, e.g. due to UE domain preference using the procedures to re-establish the PDN connection providing access to IMS as specified in 3GPP TS 24.229 [5].

NOTE 2: If this MO is configured, it is assumed that the URSP rules are configured consistently with this MO.

5.91 /<X>/SNPN_Configuration

This interior node contains configuration parameters regarding a UE operating in SNPN access operation mode.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.92 /<X>/SNPN_Configuration/<X>

This interior node acts as a placeholder for a list of:

a) SNPN identity; and

b) configuration parameters.

NOTE: For each of the elements in the list, a) must be present and at least one parameter of b) needs to appear.

A configuration parameter in an /<X>/SNPN_Configuration/<X> node other than the SNPN_identifier, is applicable when the UE selects an entry of "list of subscriber data":

a) with the SNPN identity of the subscribed SNPN which is the same as the SNPN identity in the SNPN_identifier leaf.

– Occurrence: OneOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.93 /<X>/SNPN_Configuration/<X>/SNPN_identifier

This leaf indicates the SNPN identity of the subscribed SNPN for which the list of configuration parameters are applicable.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: <PLMN><NID>

The PLMN and NID are in the format defined by 3GPP TS 23.003 [2], with each digit of the MCC and MNC of the PLMN and each digit of the assignment mode and NID value of the NID encoded as an ASCII character.

5.94 /<X>/SNPN_Configuration/<X>/Timer_T1

The Timer_T1 leaf defines the SIP timer T1 – the RTT estimate.

– Occurrence: One

– Format: int

– Access Types: Get, Replace

– Values: <The round trip time>

EXAMPLE: 2000 (milliseconds)

5.95 /<X>/SNPN_Configuration/<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

– Access Types: Get, Replace

– Values: <The maximum retransmit interval for non-INVITE requests and INVITE responses>

EXAMPLE: 16000 (milliseconds)

5.96 /<X>/SNPN_Configuration/<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

– Access Types: Get, Replace

– Values: <The maximum duration a message will remain in the network>

EXAMPLE: 17000 (milliseconds)

5.97 /<X>/SNPN_Configuration/<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 3GPP TS 24.229 [5].

The format of the private user identity is defined by 3GPP TS 23.003 [2].

EXAMPLE: 234150999999999@ims.mnc015.mcc234.3gppnetwork.org

5.98 /<X>/SNPN_Configuration/<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.

– Occurrence: One

– Format: node

– Access Types: Get

– Values: N/A

5.99 /<X>/SNPN_Configuration/<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.100 /<X>/SNPN_Configuration/<X>/Public_user_identity_List/
<X>/Public_user_identity

The Public_user_identity leaf represents a public user identity.

– 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 3GPP TS 24.229 [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 3GPP TS 24.229 [5].

The format of the public user identity is defined by 3GPP TS 23.003 [2].

EXAMPLE: sip: 234150999999999@ims.mnc015.mcc234.3gppnetwork.org

5.101 /<X>/SNPN_Configuration/<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 3GPP TS 24.229 [5].

The format of the home network domain name is defined by 3GPP TS 23.003 [2].

EXAMPLE: ims.mnc015.mcc234.3gppnetwork.org

5.102 /<X>/SNPN_Configuration/<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.103 /<X>/SNPN_Configuration/<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

– Access Types: Get, Replace

– Values: N/A

5.104 /<X>/SNPN_Configuration/<X>/ICSI_List/<X>/ICSI

The ICSI leaf represents one IMS communication service identifier that is supported by a subscriber’s network for that subscriber.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: <A communication services identifier>

The format of the communication services identifier is defined by 3GPP TS 24.229 [2]

5.105 /<X>/SNPN_Configuration/<X>/ICSI_List/<X>/
ICSI_Resource_Allocation_Mode

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– 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.

5.106 /<X>/SNPN_Configuration/<X>/Resource_Allocation_Mode

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– 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.

5.107 /<X>/SNPN_Configuration/<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, Replace

– Values: N/A

5.108 /<X>/SNPN_Configuration/<X>/
LBO_P-CSCF_Address/<X>

– Occurrence: OneOrMore

– Format: node

– Access Types: Get

– Values: N/A

5.109 /<X>/SNPN_Configuration/<X>/
LBO_P-CSCF_Address/<X>/Address

The Address leaf defines the FQDN, the IPv4 address or the IPv6 address of a P-CSCF.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: <an FQDN>, <an IPv4 address>, <an IPv6 address>

The FQDN, or host name as defined in subclause 25.1 of RFC 3261 [23].

EXAMPLE: pcscf.operator.com

5.110 /<X>/SNPN_Configuration/<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

– Access Types: Get, Replace

– Values: ‘FQDN’, ‘IPv4’, ‘IPv6’

EXAMPLE: ‘FQDN’

5.111 /<X>/SNPN_Configuration/<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

– Access Types: Get, Replace

– 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.

5.112 /<X>/SNPN_Configuration/<X>/
Keep_Alive_Enabled

The Keep_Alive_Enabled leaf indicates whether the UE sends keep alives.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the UE does not send keep alives.

1 – Indicates that the UE is to send keep alives.

3GPP TS 24.229 [5] describes the normative behaviour for the UE sending keep alives when the Keep_Alive_Enabled leaf indicates that sending keep alives is enabled.

5.113 /<X>/SNPN_Configuration/<X>/
RegRetryBaseTime

The RegRetryBaseTime leaf represents the value of the base-time (if all failed) parameter of the algorithm defined in subclause 4.5 of RFC 5626 [18].

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <base-time>

The base-time value shall be given in seconds.

5.114 /<X>/SNPN_Configuration/<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

– Access Types: Get, Replace

– Values: <maximum time>

The maximum time value shall be given in seconds.

5.115 /<X>/SNPN_Configuration/<X>/PhoneContext_List/

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.116 /<X>/SNPN_Configuration/<X>/PhoneContext_List/<X>

This run-time node acts as a placeholder for one or more phone-context parameter values.

– Occurrence: OneOrMore

– Format: node

– Access Types: Get

– Values: N/A

5.117 /<X>/SNPN_Configuration/<X>/PhoneContext_List/<X>/
PhoneContext

The PhoneContext leaf defines the value of the phone-context parameter.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: <phone-context>

5.118 /<X>/SNPN_Configuration/<X>/PhoneContext_List/<X>/
Public_user_identity

The Public_user_identity leaf defines zero or more public user identities to which the phone-context parameter value is associated.

– Occurrence: OneOrMore

– Format: chr

– Access Types: Get, Replace

– Values: <A public user identity>

5.119 /<X>/SNPN_Configuration/<X>/
PS_domain_IMS_SS_control_preference

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the IMS SS setting control for services defined by 3GPP TS 22.173 [19] is to be invoked using XCAP/Ut as defined by 3GPP TS 24.623 [20]

1 – Indicates that the IMS SS setting control for services defined by 3GPP TS 22.173 [19] is to be invoked using SIP-based user configuration as defined by 3GPP TS 24.238 [21]

NOTE: The usage of other methods for controlling the IMS SS setting control are out of the scope of this parameter.

5.120 /<X>/SNPN_Configuration/<X>/
Media_type_restriction_policy

This interior node describes the media type restriction policy.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

The media type restriction policy consists of zero or more media type restriction policy parts. Each media type restriction policy part is described by a child node.

The media type restriction policy does not influence SDP messages exchanged in an IMS emergency call.

5.121 /<X>/SNPN_Configuration/<X>/
Media_type_restriction_policy/<X>/

This interior node describes the media type restriction policy part.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

The media type restriction policy part consists of a mandatory media type in the Media_type child node and zero or more conditions in child nodes other than the Media_type child node.

The media type restriction policy part indicated by this interior node restricts inclusion of a media type in an SDP message if:

a) the media type is indicated in the Media_type child node;

b) the following is true:

1) this node does not have an IP-CAN child node; or

2) the following is true:

A) the SDP message contains an "m=" SDP line of the media type;

B) the "m=" SDP line is associated with a "c=" SDP line;

C) the "c=" SDP line indicates an IP address;

D) the IP address is associated with an IP-CAN bearer; and

E) the IP-CAN bearer is of an IP-CAN indicated in the IP-CAN child node;

c) the following is true:

1) this node does not have an ICSI child node; or

2) the SDP message describes session offered or established by SIP signalling related to an IMS communication service identified in the ICSI child node; and

d) the following is true:

1) this node does not have a Non-subscribed child node; or

NOTE: The Roaming child node in figure 2 has the same role as the Non-subscribed child node.

2) the following is true:

A) this node has a Non-subscribed child node;

B) the SDP message contains an "m=" SDP line of the media type;

C) the "m=" SDP line is associated with a "c=" SDP line;

D) the "c=" SDP line indicates an IP address;

E) the IP address is associated with an IP-CAN bearer; and

F) the UE roams in the IP-CAN of the IP-CAN bearer.

5.122 /<X>/SNPN_Configuration/<X>/
Media_type_restriction_policy/<X>/Media_type

This leaf indicates a restriction applicable for a media type.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: a media type as described in RFC 4566 [rfc4566], subclause 8.2.1

5.123 /<X>/SNPN_Configuration/<X>/
Media_type_restriction_policy/<X>/IP-CAN

This leaf indicates a restriction applicable for an IP-CAN.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: one of the values specified in table 5.x34-1.

Table 5.x34-1: Possible values for the IP-CAN leaf

Value	Description
1	5G core (5GC) via NG-RAN
2	5G core (5GC) via non-3GPP access
3	5G core (5GC) via E-UTRA
4	5G core (5GC) via NR
0, 5-255	Not assigned

5.124 /<X>/SNPN_Configuration/<X>/
Media_type_restriction_policy/<X>/ICSI

This leaf indicates a restriction applicable for an ICSI.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.125 /<X>/SNPN_Configuration/<X>/
Media_type_restriction_policy/<X>/Non-subscribed

This leaf indicates a restriction applicable when media are transported to or from an SNPN where the UE is not subscribed.

NOTE: The Roaming child node in figure 2 has the same role as the Non-subscribed child node.

– Occurrence: ZeroOrOne

– Format: null

– Access Types: Get, Replace

– Values: null

5.126 /<X>/SNPN_Configuration/<X>/Reliable_18x_policy

This interior node describes the reliable 18x policy. In the absence of this node, the UE sends SIP 18x response reliably or not up to the implementation.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.127 /<X>/SNPN_Configuration/<X>/Reliable_18x_policy/<X>/

This interior node describes the reliable 18x policy part.

– Occurrence: OneOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.128 /<X>/SNPN_Configuration/<X>/Reliable_18x_policy/<X>/
ICSI

This leaf indicates an ICSI condition.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

In absence of the parameter, UE applies the reliable 18x policy indicated in the Send_18x_Reliably parameter on all IMS services.

5.129 /<X>/SNPN_Configuration/<X>/Reliable_18x_policy/<X>/
Send_18x_Reliably

This leaf indicates whether the SIP 18x responses (other than SIP 183 response) against an INVITE request subject to the IMS service indicated in the ICSI leaf are to be sent reliably.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the SIP 18x responses (other than SIP 183 response) are to be sent unreliably.

1 – Indicates that the SIP 18x responses (other than SIP 183 response) are to be sent reliably.

5.130 /<X>/SNPN_Configuration/<X>/
Precondition_disabling_policy

This leaf contains the precondition disabling policy.

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– Values: one of the values specified in table 5.x40-1.

Table 5.x40-1: Possible values for the Precondition_disabling_policy leaf

Value	Description
0	the UE is allowed to use the precondition mechanism
1	the UE is not allowed to use the precondition mechanism

The default value is ‘0’.

5.131 /<X>/SNPN_Configuration/<X>/Timer_Emerg-reg

The optional Timer_Emerg-reg leaf defines the operator’s emergency registration request timeout policy.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <The maximum time before the UE consider the emergency REGISTER request or the emergency call attempt as failed.>

5.132 /<X>/SNPN_Configuration/<X>/Policy_on_local_numbers

This interior node describes the policy on local numbers.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.133 /<X>/SNPN_Configuration/<X>/Policy_on_local_numbers/
<X>/

This interior node describes a part of the policy on local numbers.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.134 /<X>/SNPN_Configuration/<X>/Policy_on_local_numbers/
<X>/ICSI

This leaf indicates an ICSI.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.135 /<X>/SNPN_Configuration/<X>/Policy_on_local_numbers/
<X>/Local_number_type

This leaf indicates a local number type.

– Occurrence: One

– Format: int

– Access Types: Get, Replace

– Values: values indicate in table 5.x46-1.

Table 5.x46-1: Possible values for the Local_number_type leaf

Value	Description
1	home-local number
2	geo-local number
0, 3-255	not assigned

5.136 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off

The interior node contains configuration parameters for 3GPP PS data off.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.137 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
SMSoIP_exempt

The leaf indicates whether the SMS over IP is a 3GPP PS data off exempt service.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the SMS over IP is not a 3GPP PS data off exempt service.

1 – Indicates that the SMS over IP is a 3GPP PS data off exempt service.

NOTE: This MO is used when the UE is in a subscribed SNPN, or the SMSoIP_non-subscribed_exempt node is not configured when the UE is in a non-subscribed SNPN.

5.138 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
SMSoIP_non-subscribed_exempt

The leaf indicates whether the SMS over IP is a 3GPP PS data off exempt service when the UE is in a non-subscribed SNPN:

– Occurrence: ZeroOrOne

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

0 – Indicates that the SMS over IP is not a 3GPP PS data off non-subscribed exempt service.

1 – Indicates that the SMS over IP is a 3GPP PS data off non-subscribed exempt service.

NOTE: The SMSoIP_roaming child node in figure 6 has the same role as the non-subscribed child node.

5.139 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
non_3GPP_ICSIs_exempt

The interior node contains IMS communication service identifiers of the IMS communication services not defined by 3GPP which are 3GPP PS data off exempt services.

– Occurrence: One

– Format: node

– Access Types: Get, Replace

– Values: N/A

NOTE: This MO is used when the UE is in a subscribed SNPN, or the non_3GPP_ICSIs_non-subscribed_exempt node is not configured when the UE is in a non-subscribed SNPN.

5.140 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
non_3GPP_ICSIs_non-subscribed_exempt

The interior node contains IMS communication service identifiers of the IMS communication services not defined by 3GPP which are 3GPP PS data off exempt services when the UE is in a non-subscribed SNPN.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

NOTE: The non_3GPP_ICSIs_roaming_exempt child node in figure 6 has the same role as the non-subscribed child node.

5.141 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
non_3GPP_ICSIs_exempt/<X>

The interior node contains an IMS communication service identifier of the IMS communication service not defined by 3GPP which is a 3GPP PS data off exempt service.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.142 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
non_3GPP_ICSIs_non-subscribed_exempt/<X>

The interior node contains an IMS communication service identifier of the IMS communication service not defined by 3GPP which is a 3GPP PS data off exempt service when the UE is in a non-subscribed SNPN.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

NOTE: The non_3GPP_ICSIs_roaming_exempt child node in figure 6 has the same role as the non-subscribed child node.

5.143 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
non_3GPP_ICSIs_exempt/<X>/non_3GPP_ICSI_exempt

The interior node contains an IMS communication service identifier of the IMS communication service not defined by 3GPP which is a 3GPP PS data off exempt service.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.144 /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/
non_3GPP_ICSIs_non-subscribed_exempt/<X>/
non_3GPP_ICSI_non-subscribed_exempt

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

NOTE: The non_3GPP_ICSIs_roaming_exempt child node in figure 6 has the same role as the non-subscribed child node.

5.145 /<X>/SNPN_Configuration/<X>/SMSoIP_usage_policy

The SMSoIP_usage_policy leaf indicates the policy on usage of SMS over IP.

If the SMS_Over_IP_Networks_Indication leaf specified in subclause 5.x25 is set to "0: Indicates that the SMS service is not to be invoked over the IP networks" value, then the SMSoIP_usage_policy leaf has no effect.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: 0, 1, 2

0 – Indicates that SMS over IP is used only if voice over PS is available and only on the PDU session that is used for the transport of SIP signalling associated with voice over PS.

1 – Indicates that SMS over IP is used only if voice over PS is available and on any PDU session.

2 – Indicates that SMS over IP is used irrespective of whether voice over PS is available and on any PDU session.

5.146 /<X>/SNPN_Configuration/<X>/IMS_Registration_Policy

The interior node contains configuration parameters for the IMS registration handling.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.147 /<X>/SNPN_Configuration/<X>/IMS_Registration_Policy/
<X>/

The interior node describes the IMS registration handling policy part.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.148 /<X>/SNPN_Configuration/<X>/IMS_Registration_Policy/
<X>/Stay_Registered_When_VoPS_Not_Supported

The leaf indicates whether the UE stays registered or not from IMS when moving to area where IMS Voice Over PS Session is not supported.

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

1 – Indicates that the UE maintains the registration as required for IMS services;

0 – Indicates that the UE deregisters from IMS as defined in annex B, annex L, annex U and annex W in 3GPP TS 24.229 [5].

5.149 /<X> /SNPN_Configuration/<X>/IMS_Registration_Policy/
<X>/Deregistration_Timer

The Deregistration_Timer leaf indicates the time before deregistration on the UE when moving to area where IMS Voice Over PS Session is not supported.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <The time a UE stays registered when VoPS_Not_Supported is received>

The use of this leaf is as defined in annex B, annex L, annex U and annex W in 3GPP TS 24.229 [5]. The timer value shall be given in seconds. The Deregistration_Timer is a 16 bits unsigned integer.

NOTE 1: Setting the value ‘0’ leads to immediate deregistration

5.150 /<X>/SNPN_Configuration/<X>/Timer_Emerg-request

The optional Timer_Emerg-request leaf defines the operator’s emergency request timeout policy.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <The maximum time between sending of an initial INVITE request for an emergency session and receiving a 18x response to the INVITE request.>

5.151 /<X>/SNPN_Configuration/<X>/
Default_QoS_Flow_usage_restriction_policy

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.152 /<X>/SNPN_Configuration/<X>/
Default_QoS_Flow_usage_restriction_policy/<X>/

This interior node describes the default QoS Flow usage restriction policy part.

– Occurrence: ZeroOrMore

– Format: node

– Access Types: Get, Replace

– Values: N/A

5.153 /<X>/SNPN_Configuration/<X>/
Default_QoS_Flow_usage_restriction_policy/<X>/
Media_type

This leaf indicates a media type condition.

– Occurrence: One

– Format: chr

– Access Types: Get, Replace

– Values: a media type as described in RFC 4566 [24], subclause 8.2.1

5.154 /<X>/SNPN_Configuration/<X>/
Default_QoS_Flow_usage_restriction_policy/<X>/ICSI

This leaf indicates an ICSI condition.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: an IMS communication service identifier as defined by 3GPP TS 24.229 [2].

5.155 /<X>/SNPN_Configuration/<X>/Session_Timer_Policy

The interior node contains configuration parameters for the Session Timer policy.

– Occurrence: ZeroOrOne

– Format: node

– Access Types: Get, Replace

– Values: N/A

In the absence of this node, the Session_Timer policy is up to the implementation.

5.156 /<X>/SNPN_Configuration/<X>/
Session_Timer_Policy/Session_Timer_Support

The leaf indicates whether the UE supports the Session Timer extension as per RFC 4028 [26] and 3GPP TS 24.229 [5].

– Occurrence: One

– Format: bool

– Access Types: Get, Replace

– Values: 0, 1

1 – Indicates that the UE supports the Session Timer extension.

0 – Indicates that the UE does not support the Session Timer extension.

5.157 /<X>/SNPN_Configuration/<X>/Session_Timer_Policy
/Session_Timer_Initial_Interval

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: <Session Timer initial interval value>

The timer value shall be given in seconds. The Session_Timer_Initial_Interval is a 16 bits unsigned integer.

NOTE: The minimum value for the Session_Timer_Initial_Interval is 90 seconds as per RFC 4028 [26].

EXAMPLE: 1800 (seconds)

5.158 /<X>/SNPN_Configuration/<X>/Session_Timer_Policy/
Session_Timer_Initial_MT_Refresher

The leaf indicates the value of the refresher parameter in the Session-Expires header to be used by the terminating UE when adding the refresher parameter for the first time.

– Occurrence: ZeroOrOne

– Format: chr

– Access Types: Get, Replace

– Values: <value for refresher parameter>

Possible values for refresher parameter in Session-Expires header are defined by RFC 4028 [26].

EXAMPLE: uac

5.159 /<X>/SNPN_Configuration/<X>/
Access_Point_Name_Parameter_Reading_Rule

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: 0, 1, 2

0 – Indicates that UE should use APN values provided by UICC as per 3GPP TS 31.102 [10] rules.

1 – Indicates that UE should use values provided by network

2 – Indicates that UE should use the values provided by user via UE settings menu or any other method

In the absence of this node, which source to use for reading APN parameter is implementation specific.

5.160 /<X>/SNPN_Configuration/<X>/
Allow_Handover_PDU_session_non-3GPP_and_NG-RAN

The leaf indicates options for when a UE is allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RAN.

– Occurrence: ZeroOrOne

– Format: int

– Access Types: Get, Replace

– Values: 0, 1, 2, 3, 4, 5

3 – Indicates that a UE in a non-subscribed SNPN having an ongoing IMS session, is not allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RANand that a UE in a non-subscribed SNPN not having an ongoing IMS session is allowed to transfer the PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN.

4 – Indicates that a UE in a non-subscribed SNPN having an ongoing IMS session, is allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RANand that a UE in a non-subscribed SNPN not having an ongoing IMS session is allowed to transfer the PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN;

5 – Indicates that a UE in a non-subscribed SNPN is not allowed to transfer a PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN, irrespective of if the UE has an ongoing IMS session or not.

NOTE 2: If this MO is configured, it is assumed that the URSP rules are configured consistently with this MO.

Annex A (informative):
Management Object DDF

This DDF is the standardized minimal set. A vendor can define its 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"

"http://www.openmobilealliance.org/tech/DTD/DM_DDF-V1_2.dtd">

<Man>–The device manufacturer–</Man>

<Mod>–The device model–</Mod>

<Node>

<Get/>

</AccessType>

<Description>3GPP IMS settings</Description>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The 3GPP IMS Management Object.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>AppID</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The Application ID.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>User displayable name for the node.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>ConRefs</NodeName>

<!– The ConRefs node starts here. –>

<Get/>

</AccessType>

<node/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of network access point objects.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for a network access point object.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>ConRef</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The ConRef (network access point object).</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>PDP_ContextOperPref</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indication of the operator’s preference for a dedicated PDP context for IMS signalling.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>P-CSCF_Address</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The address of the P-CSCF.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_T1</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>RFC 3261, timer T1.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_T2</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>RFC 3261, timer T2.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_T4</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>RFC 3261, timer T4.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Private_user_identity</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The private user identity.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Public_user_identity_List</NodeName>

<!– The Public_user_identity_List node starts here. –>

<Get/>

</AccessType>

<node/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of public user identity objects.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for a public user identity object.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Public_user_identity</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The public user identity.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Home_network_domain_name</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The home network domain name.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<!– The ICSI_List node starts here. –>

<Get/>

</AccessType>

<node/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of IMS communication services identifier objects.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for an IMS communication services identifier object.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The IMS communication services identifier.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>ICSI_Resource_Allocation_Mode</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<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>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>LBO_P-CSCF_Address</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of addresses of the P-CSCF for IMS Local Breakout.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for a P-CSCF address.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Address</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The P-CSCF Address.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>AddressType</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The type of P-CSCF Address.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Resource_Allocation_Mode</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<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>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Voice_Domain_Preference_EUTRAN</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Network operator’s preference for voice domain for E-UTRAN according to 3GPP TS 23.221.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Voice_Domain_Preference_UTRAN</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Network operator’s preference for voice domain for UTRAN according to 3GPP TS 23.221.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>SMS_over_IP_Networks_Indication</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<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>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Keep_Alive_Enabled</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indication whether the sending of keep alives by the UE is enabled.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Mobility_Management_IMS_Voice_Termination</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indicates whether the UE mobility management performs additional procedures as specified in 3GPP TS 24.008 and 3GPP TS 24.301 to support terminating access domain selection by the network.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>RegRetryBaseTime</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Represents the value of the base-time parameter of the algorithm defined in subclause 4.5 of RFC 5626</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>RegRetryMaxTime</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Represents the value of the max-time parameter of the algorithm defined in subclause 4.5 of RFC 5626</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>PhoneContext_List</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of phone-context parameters values with the associated public user identities</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for a phone-context value</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>PhoneContext</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The phone-context parameter value</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Public_user_identity</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The associated Public User identity URIs</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>SS_domain_setting</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Domain or mechanism used to choose the domain for SS setting control</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>PS_domain_IMS_SS_control_preference</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Mechanim used for performing IMS SS setting control over the PS domain for services defined in 3GPP TS 22.173</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Media_type_restriction_policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Media type restriction policy</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Media type restriction policy part</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Media_type</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A media type</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Roaming</NodeName>

<Get/>

</AccessType>

<null/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Roaming</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Default_EPS_bearer_context_usage_restriction_policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Default EPS bearer context usage restriction policy</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Default EPS bearer context usage restriction policy part</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Media_type</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A media type</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Reliable_18x_policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Reliable 18x policy</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Reliable 18x policy part</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Send_18x_Reliably</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>whether the UE sends reliable SIP 18x response against an INVITE request subject to the IMS service indicated in the ICSI leaf.</DFTitle>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>EPS_initial_attach_ConRefs</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The policy on the PDN connection established during the EPS attach procedure.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

</DFType>

</DFProperties>

<Node>

<NodeName>ConRef</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The ConRef (network access point object).</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Precondition_disabling_policy</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The precondition disabling policy.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_Emerg-reg</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Optional timer for emergency registration request timeout.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Policy_on_local_numbers</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The policy on local numbers</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A part of the policy on local numbers.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Local_number_type</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A local number type.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Configuration parameters for 3GPP PS data off.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>SMSoIP_exempt</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Whether the SMSoIP is a 3GPP PS data off exempt service.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>SMSoIP_roaming_exempt</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Whether the SMSoIP is a 3GPP PS data off roaming exempt service.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>non_3GPP_ICSIs_exempt</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifiers of the IMS communication services not defined by 3GPP which are 3GPP PS data off exempt services.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifier of the IMS communication service not defined by 3GPP which is 3GPP PS data off exempt service.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>non_3GPP_ICSI_exempt</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifier of the IMS communication service not defined by 3GPP which is 3GPP PS data off exempt service.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>non_3GPP_ICSIs_roaming_exempt</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifiers of the IMS communication services not defined by 3GPP which are 3GPP PS data off roaming exempt services.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifier of the IMS communication service not defined by 3GPP which is 3GPP PS data off roaming exempt service.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>non_3GPP_ICSI_roaming_exempt</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifier of the IMS communication service not defined by 3GPP which is 3GPP PS data off roaming exempt service.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>SMSoIP_usage_policy</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indicates the policy on usage of SMS over IP.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>IMS_Registration_Policy </NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle> indicates the handling of IMS registration on the UE when moving to area where IMS Voice Over PS Session is not supported</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for a network access point object.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Stay_Registered_When_VoPS_Not_Supported </NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The leaf indicates whether the UE stays registered or not from IMS when moving to area where IMS Voice Over PS Session is not supported </DFTitle>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName> Deregistration_Timer</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The Deregistration_Timer leaf indicates the time before deregistration on the UE when moving to area where IMS Voice Over PS Session is not supported </DFTitle>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_Emerg-request</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The maximum time between sending of an initial INVITE request for an emergency session and receiving an 18x response to the INVITE request.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_Emerg-non3gpp</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The maximum time for searching a 3GPP access usable for establishing an emergency calls before performing the emergency call over the available non-3GPP access.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Allow_Handover_PDN_connection_WLAN_and_EPS</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indicates whether a UE roaming in a VPLMN, is allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Allow_Handover_PDU_session_non-3GPP_and_NG-RAN</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indicates whether a UE is allowed to transfer the PDU session providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RAN.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Allow_Handover_PDN_connection_non-3GPP_and_NG-RAN</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indicates whether a UE is allowed to transfer the PDN connection providing access to IMS via non-3GPP access and 5GCN via NG-RAN.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<!– The Extension node starts here. –>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of all Extension objects.</DFTitle>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Default_QoS_Flow_usage_restriction_policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Default QoS Flow usage restriction policy</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Default QoS Flow usage restriction policy part</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Media_type</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A media type</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Session_Timer_Policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Session Timer policy</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Session_Timer_Support</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Session Timer extension support</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Session_Timer_Initial_Interval</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Session Timer initial interval value</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Session_Timer_Initial_MT_Refresher</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Initial MT Refresher parameter</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Access_Point_Name_Pameter_Reading_Rule</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indicates which input soure should the UE use to read the APN prameters</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>SNPN_Configuration</NodeName>

<!– The SNPN_Configuration node starts here. –>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>SNPN configuration parameters</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Configuration parameters for an SNPN.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>SNPN_identifier</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The SNPN identifier.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_T1</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>RFC 3261, timer T1.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_T2</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>RFC 3261, timer T2.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_T4</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>RFC 3261, timer T4.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Private_user_identity</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The private user identity.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Public_user_identity_List</NodeName>

<!– The Public_user_identity_List node starts here. –>

<Get/>

</AccessType>

<node/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of public user identity objects.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for a public user identity object.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Public_user_identity</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The public user identity.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Home_network_domain_name</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The home network domain name.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<!– The ICSI_List node starts here. –>

<Get/>

</AccessType>

<node/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of IMS communication services identifier objects.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for an IMS communication services identifier object.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The IMS communication services identifier.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>ICSI_Resource_Allocation_Mode</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>LBO_P-CSCF_Address</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of addresses of the P-CSCF for IMS Local Breakout.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for a P-CSCF address.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Address</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The P-CSCF Address.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>AddressType</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The type of P-CSCF Address.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>SMS_over_IP_Networks_Indication</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<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>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Keep_Alive_Enabled</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indication whether the sending of keep alives by the UE is enabled.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>RegRetryBaseTime</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Represents the value of the base-time parameter of the algorithm defined in subclause 4.5 of RFC 5626</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>RegRetryMaxTime</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Represents the value of the max-time parameter of the algorithm defined in subclause 4.5 of RFC 5626</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>PhoneContext_List</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A collection of phone-context parameters values with the associated public user identities</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The "name" node for a phone-context value</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>PhoneContext</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The phone-context parameter value</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Public_user_identity</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The associated Public User identity URIs</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>PS_domain_IMS_SS_control_preference</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Mechanim used for performing IMS SS setting control over the PS domain for services defined in 3GPP TS 22.173</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Media_type_restriction_policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Media type restriction policy</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Media type restriction policy part</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Media_type</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A media type</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Non-subscribed</NodeName>

<Get/>

</AccessType>

<null/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Non-subscribed</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Reliable_18x_policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Reliable 18x policy</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Reliable 18x policy part</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Send_18x_Reliably</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>whether the UE sends reliable SIP 18x response against an INVITE request subject to the IMS service indicated in the ICSI leaf.</DFTitle>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Precondition_disabling_policy</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The precondition disabling policy.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_Emerg-reg</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Optional timer for emergency registration request timeout.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Policy_on_local_numbers</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The policy on local numbers</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A part of the policy on local numbers.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Local_number_type</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A local number type.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Configuration parameters for 3GPP PS data off.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>SMSoIP_exempt</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Whether the SMSoIP is a 3GPP PS data off exempt service.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>SMSoIP_non-subscribed_exempt</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Whether the SMSoIP is a 3GPP PS data off non-subscribed exempt service.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>non_3GPP_ICSIs_exempt</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifiers of the IMS communication services not defined by 3GPP which are 3GPP PS data off exempt services.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifier of the IMS communication service not defined by 3GPP which is 3GPP PS data off exempt service.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>non_3GPP_ICSI_exempt</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifier of the IMS communication service not defined by 3GPP which is 3GPP PS data off exempt service.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>non_3GPP_ICSIs_non-subscribed_exempt</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifiers of the IMS communication services not defined by 3GPP which are 3GPP PS data off non-subscribed exempt services.</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifier of the IMS communication service not defined by 3GPP which is 3GPP PS data off non-subscribed exempt service.</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>non_3GPP_ICSI_non-subscribed_exempt</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>IMS communication service identifier of the IMS communication service not defined by 3GPP which is 3GPP PS data off non-subscribed exempt service.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>SMSoIP_usage_policy</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indicates the policy on usage of SMS over IP.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>IMS_Registration_Policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>indicates the handling of IMS registration on the UE when moving to area where IMS Voice Over PS Session is not supported</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Stay_Registered_When_VoPS_Not_Supported</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The leaf indicates whether the UE stays registered or not from IMS when moving to area where IMS Voice Over PS Session is not supported</DFTitle>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Deregistration_Timer</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The Deregistration_Timer leaf indicates the time before deregistration on the UE when moving to area where IMS Voice Over PS Session is not supported</DFTitle>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Timer_Emerg-request</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>The maximum time between sending of an initial INVITE request for an emergency session and receiving an 18x response to the INVITE request.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Default_QoS_Flow_usage_restriction_policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Default QoS Flow usage restriction policy</DFTitle>

</DFType>

</DFProperties>

<Node>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Default QoS Flow usage restriction policy part</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Media_type</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>A media type</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Session_Timer_Policy</NodeName>

<Get/>

</AccessType>

<node/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Session Timer policy</DFTitle>

</DFType>

</DFProperties>

<Node>

<NodeName>Session_Timer_Support</NodeName>

<Get/>

</AccessType>

<bool/>

</DFFormat>

<One/>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Session Timer extension support</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Session_Timer_Initial_Interval</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Session Timer initial interval value</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Session_Timer_Initial_MT_Refresher</NodeName>

<Get/>

</AccessType>

<chr/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Initial MT Refresher parameter</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Access_Point_Name_Pameter_Reading_Rule</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indicates which input soure should the UE use to read the APN prameters</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

<Node>

<NodeName>Allow_Handover_PDU_session_non-3GPP_and_NG-RAN</NodeName>

<Get/>

</AccessType>

<int/>

</DFFormat>

</Occurrence>

<Scope>

</Scope>

<DFTitle>Indicates whether a UE is allowed to transfer the PDU session providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RAN.</DFTitle>

<MIME>text/plain</MIME>

</DFType>

</DFProperties>

</Node>

</MgmtTree>

Annex B (informative):
3GPP IMS Client Provisioning Application Characteristics (CP AC)