Content for  TS 24.167  Word version:  18.1.0

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

• Occurrence: ZeroOrMore
• Format: node
• Access Types: Get, Replace
• Values: N/A

This leaf indicates a media type condition.

• Occurrence: One
• Format: chr
• Access Types: Get, Replace
• Values: a media type as described in Section 8.2.1 of RFC 4566

This leaf indicates an ICSI condition.

• Occurrence: ZeroOrOne
• Format: chr
• Access Types: Get, Replace
• Values: an IMS communication service identifier as defined by TS 24.229.

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 TS 24.229. The timer configurable value is between 5 and 20 seconds as defined in subclause 7.8 of TS 24.229.

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.

The leaf indicates whether the UE supports the Session Timer extension as per RFC 4028 and TS 24.229.

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

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

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

The UE can get the APN name from multiple sources. For example UICC via EFACL 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 TS 31.102 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.

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.