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.100  /<X>/ SNPN_Configuration/ <X>/ Public_user_identity_List/ <X>/ Public_user_identity |R17|p. 44

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:
sip: 234150999999999@ims.mnc015.mcc234.3gppnetwork.org
Up

5.101  /<X>/ SNPN_Configuration/ <X>/ Home_network_domain_name |R17|p. 45

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:
ims.mnc015.mcc234.3gppnetwork.org

5.102  /<X>/ SNPN_Configuration/ <X>/ ICSI_List/ |R17|p. 45

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> |R17|p. 45

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 |R17|p. 45

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.105  /<X>/ SNPN_Configuration/ <X>/ ICSI_List/ <X>/ ICSI_Resource_Allocation_Mode |R17|p. 46

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.106  /<X>/ SNPN_Configuration/ <X>/ Resource_Allocation_Mode |R17|p. 46

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.107  /<X>/ SNPN_Configuration/ <X>/ LBO_P-CSCF_Address/ |R17|p. 46

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> |R17|p. 47

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.109  /<X>/ SNPN_Configuration/ <X>/ LBO_P-CSCF_Address/ <X>/ Address |R17|p. 47

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

Up   Top   ToC