Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 24.167  Word version:  18.1.0

Top   Top   Up   Prev   Next
1…   4   5…   5.20…   5.40…   5.50…   5.60…   5.70…   5.80…   5.90…   5.100…   5.110…   5.120…   5.130…   5.140…   5.147…   5.154…   A   B…

 

5.20  /<X>/ ICSI_List/ <X> |R7|p. 19

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 |R7|p. 19

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

5.21A  /<X>/ ICSI_List/ <X>/ ICSI_Resource_Allocation_Mode |R8|p. 19

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

5.22  /<X>/ LBO_P-CSCF_Address/ |R8|p. 20

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> |R8|p. 20

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 |R8|p. 20

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 Section 25.1 of RFC 3261.
EXAMPLE:
pcscf.operator.com

5.25  /<X>/ LBO_P-CSCF_Address/ <X>/ AddressType |R8|p. 20

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

5.26  /<X>/ Resource_Allocation_Mode |R8|p. 21

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

5.27  /<X>/ Voice_Domain_Preference_E_UTRAN |R8|p. 21

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 TS 23.221.
    2
    Indicates that the UE preferably attempts to use the CS domain to originate voice sessions. In addition, a UE, in accordance with TS 24.292, upon receiving a request for a session including voice, preferably attempts to use the CS domain for the audio media stream. This value equates to "CS Voice preferred, IMS PS Voice as secondary" as described in TS 23.221.
    3
    Indicates that the UE preferably attempts to use the IM CN Subsystem using an E-UTRAN bearer to originate sessions including voice. In addition, a UE, in accordance with TS 24.292, upon receiving a request for a session including voice, preferably attempts to use an E-UTRAN bearer for the audio media stream. This value equates to "IMS PS Voice preferred, CS Voice as secondary" as described in TS 23.221.
    4
    Indicates that the UE attempts to initiate voice sessions over IM CN Subsystem using an E-UTRAN bearer. In addition, a UE, upon receiving a request for a session including voice, attempts to use an E-UTRAN bearer for all the the audio media stream(s). This value equates to "IMS PS Voice only" as described in TS 23.221.
Up

5.28  /<X>/ SMS_Over_IP_Networks_Indication |R8|p. 22

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 |R8|p. 22

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 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 |R8|p. 22

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 TS 23.221.
    2
    Indicates that the UE preferably attempts to use the CS domain to originate voice sessions. In addition, a UE, in accordance with TS 24.292, upon receiving a request for a session including voice, preferably attempts to use the CS domain for the audio media stream. This value equates to "CS Voice preferred, IMS PS Voice as secondary" as described in TS 23.221.
    3
    Indicates that the UE preferably attempts to use the IM CN Subsystem using an UTRAN PS bearer to originate sessions including voice. In addition, a UE, in accordance with TS 24.292, upon receiving a request for a session including voice, preferably attempts to use an UTRAN PS bearer for the audio media stream. This value equates to "IMS PS Voice preferred, CS Voice as secondary" as described in TS 23.221.
Up

5.31  /<X>/ Mobility_Management_IMS_Voice_Termination |R9|p. 23

This leaf applies if a UE utilises the services provided by EPS or GPRS to provide packet-mode communication between the UE and the IM CN subsystem.
The Mobility_Management_IMS_Voice_Termination leaf indicates whether the UE mobility management performs additional procedures as specified in TS 24.008 and TS 24.301 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.
Up

5.32Void

5.33Void

5.34Void

5.35  /<X>/ RegRetryBaseTime |R10|p. 24

The RegRetryBaseTime leaf represents the value of the base-time (if all failed) parameter of the algorithm defined in Section 4.5 of RFC 5626.
  • Occurrence: ZeroOrOne
  • Format: int
  • Access Types: Get, Replace
  • Values: <base-time>
The base-time value shall be given in seconds.

5.36  /<X>/ RegRetryMaxTime |R10|p. 24

The RegRetryMaxTime leaf represents the value of the max-time parameter of the algorithm defined in Section 4.5 of RFC 5626.
  • 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/ |R10|p. 24

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 TS 24.229.
  • Occurrence: ZeroOrOne
  • Format: node
  • Access Types: Get, Replace
  • Values: N/A

5.38  /<X>/ PhoneContext_List/ <X> |R10|p. 24

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 |R10|p. 25

The PhoneContext leaf defines the value of the phone-context parameter.
  • Occurrence: One
  • Format: chr
  • Access Types: Get, Replace
  • Values: <phone-context>

Up   Top   ToC