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

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 TS 24.229.

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>

The Name leaf is a name for the 3GPP_IMS settings.

• Occurrence: ZeroOrOne
• Format: chr
• Access Types: Get
• Values: <User displayable name>

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

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

The ConRef leaf represents a network access point object.

• Occurrence: One
• Format: chr
• Access Types: Get, Replace
• Values: <A network access point object>

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. TS 24.229 describes the normative options and the procedures for establishment of a dedicated PDP context for SIP signalling.

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 TS 23.221. The FQDN, or host name as defined in Section 25.1 of RFC 3261. EXAMPLE:

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 TS 24.229. The Timer_T1 is a 32 bits unsigned integer. EXAMPLE:

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 TS 24.229. The Timer_T2 is a 32 bits unsigned integer. EXAMPLE:

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 TS 24.229. The Timer_T4 is a 32 bits unsigned integer. EXAMPLE:

The Private_user_identity leaf represents the private user identity.

• Occurrence: One
• Format: chr
• Access Types: Get
• Values: <A private user identity>

The format of the private user identity is defined by TS 23.003. EXAMPLE:

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

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

The Public_user_identity leaf represents a public user identity.

• Occurrence: One
• Format: chr
• Access Types: Get
• Values: <A public user identity>

The temporary public user identity if derived is populated and stored as the topmost element in the Public_user_identity_List as specified in TS 24.229. The format of the public user identity is defined by TS 23.003. EXAMPLE:

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>

The format of the home network domain name is defined by TS 23.003. EXAMPLE:

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

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