Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

D (Normative)  UE policy delivery serviceWord‑p. 845

D.1  GeneralWord‑p. 845

D.1.1  OverviewWord‑p. 845

The PCF may provide the UE with one or more UE policies using the network-requested UE policy management procedure. The UE provides the PCF with a list of one or more stored UE policy section identifiers (UPSIs), and the PCF provides each UE policy using one or more UE policy sections, each identified by a UPSI. The UPSI is composed of two parts:
  1. a PLMN ID part containing:
    1. the PLMN ID for the PLMN; or
    2. the PLMN ID part of the SNPN identity for the SNPN;
    of the PCF which provides the UE policies; and
  2. a UE policy section code (UPSC) containing a value assigned by the PCF.
The UE processes the UE policy sections, each identified by the UPSI, received from the PCF and informs the PCF of the result.
The UE provides the PCF with the UE policy related capabilities such as the UE's support for ANDSP and the UE's OS Id.
The UE can also request the PCF to provide V2XP as specified in TS 24.587.
The UE can also request the PCF to provide ProSeP as specified in TS 24.555 [19F].
Up

D.1.2  Principles of PTI handling for UE policy delivery service proceduresWord‑p. 845

When the PCF or the UE initiates a procedure, it shall include a valid PTI value in the message header of the command message or the request message. When the UE initiates a procedure, the UE shall use a PTI value in range between 01H and 77H. When the PCF initiates a procedure, the PCF shall use a PTI value in range between 80H and FEH.
When the PCF initiates a transaction related procedure (i.e. a procedure consisting of more than one message and the messages are related), it shall include a valid PTI value in the message header of the command message.
If a response message is sent as result of a received command or request message, the UE or the PCF shall include in the response message the PTI value received within the received command or request message (see examples in Figure D.1.2.1, Figure D.1.2.2 and Figure D.1.2.3).
If a command message is sent as result of a received request message, the PCF shall include in the command message the PTI value received with the request message (see examples in Figure D.1.2.3).
Reproduction of 3GPP TS 24.501, Figure D.1.2.1: Network-requested transaction related procedure
Up
Reproduction of 3GPP TS 24.501, Figure D.1.2.2: UE-requested transaction related procedure rejected by the network
Up
Reproduction of 3GPP TS 24.501, Figure D.1.2.3: UE-requested transaction related procedure triggering a network-requested transaction related procedure
Up

D.2  ProceduresWord‑p. 847

D.2.1  Network-requested UE policy management procedureWord‑p. 847

D.2.1.1  GeneralWord‑p. 847

The purpose of the network-requested UE policy management procedure is to enable the network to:
  1. add one or more new UE policy sections to the UE;
  2. modify one or more UE policy sections stored at the UE; or
  3. delete one or more UE policy sections stored at the UE.

D.2.1.2  Network-requested UE policy management procedure initiationWord‑p. 847

In order to initiate the network-requested UE policy management procedure, the PCF shall:
  1. allocate a PTI value currently not used and set the PTI IE to the allocated PTI value;
  2. encode the information about the UE policy sections to be added, modified or deleted in a UE policy section management list IE as specified in subclause D.6.2 and include it in a MANAGE UE POLICY COMMAND message;
  3. send the MANAGE UE POLICY COMMAND message to the UE via the AMF as specified in TS 23.502; and
  4. start timer T3501 (see example in Figure D.2.1.2.1).
Reproduction of 3GPP TS 24.501, Figure D.2.1.2.1: Network-requested UE policy management procedure
Up
Upon receipt of the MANAGE UE POLICY COMMAND message with a PTI value currently not used, for each instruction included in the UE policy section management list IE, the UE shall:
  1. store the received UE policy section of the instruction, if the UE has no stored UE policy section associated with the same UPSI as the UPSI associated with the instruction;
  2. replace the stored UE policy section with the received UE policy section of the instruction, if the UE has a stored UE policy section associated with the same UPSI as the UPSI associated with the instruction; or
  3. delete the stored UE policy section, if the UE has a stored UE policy section associated with the same UPSI as the UPSI associated with the instruction and the UE policy section contents of the instruction is empty.
The UE may continue storing a received UE policy section for a PLMN or SNPN when the UE registers in another PLMN or SNPN. If necessary, the UE may delete UE policy sections stored for a PLMN or SNPN other than the RPLMN and the HPLMN or the registered SNPN, before storing the new received UE policy sections.
When storing a UE policy sections received from an SNPN, the UE shall associate the NID of that SNPN with the UPSI of the stored UE policy section.
Up

D.2.1.3  Network-requested UE policy management procedure accepted by the UEWord‑p. 848

If all instructions included in the UE policy section management list IE were executed successfully by the UE, the UE shall:
  1. create a MANAGE UE POLICY COMPLETE message including the PTI value received within the MANAGE UE POLICY COMMAND message; and
  2. transport the MANAGE UE POLICY COMPLETE message using the NAS transport procedure as specified in subclause 5.4.5.
Upon receipt of the MANAGE UE POLICY COMPLETE message, the PCF shall stop timer T3501. The PCF should ensure that the PTI value assigned to this procedure is not released immediately.
Up

D.2.1.4  Network-requested UE policy management procedure not accepted by the UEWord‑p. 848

If the UE could not execute all instructions included in the UE policy section management list IE successfully, the UE shall:
  1. set the PTI IE to the PTI value received within the MANAGE UE POLICY COMMAND message and encode the UPSI associated with the instructions which could not be executed successfully and the associated UE policy delivery service cause indicating the cause of the failure in a UE policy section management result IE as specified in subclause D.5.3 and include it in a MANAGE UE POLICY COMMAND REJECT message, and
  2. transport the MANAGE UE POLICY COMMAND REJECT message using the NAS transport procedure as specified in subclause 5.4.5.
Upon receipt of the MANAGE UE POLICY COMMAND REJECT message, the PCF shall stop timer T3501. Any instruction that was included in the UE policy section management list IE and whose associated UPSI is not included in a UE policy section management result IE of the received MANAGE UE POLICY COMMAND REJECT message is considered as successfully executed.
The PCF should ensure that the PTI value assigned to this procedure is not released immediately.
Upon receipt of the notification from the AMF that the UE is not reachable, the PCF shall stop the T3501.
Up

D.2.1.5  Abnormal cases on the network sideWord‑p. 849

The following abnormal cases can be identified:
  1. T3501 expired.
    The PCF shall, on the first expiry of the timer T3501, retransmit the MANAGE UE POLICY COMMAND message and shall reset and start timer T3501. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3501, the PCF shall abort the procedure and release the allocated PTI.

D.2.1.6  Abnormal cases in the UEWord‑p. 849

The following abnormal cases can be identified:
  1. Receipt of an instruction associated with a UPSI which has a PLMN ID part that is not equal to the PLMN ID of the UE's HPLMN and the instruction contains a UE policy part with a UE policy part type set to "URSP" for a UE not operating in SNPN access operation mode, or receipt of an instruction associated with a UPSI which has a PLMN ID part that is not equal to the PLMN ID part of the selected SNPN and the instruction contains a UE policy part with a UE policy part type set to "URSP" for a UE operating in SNPN access operation mode.
    The UE shall set the UE policy delivery service cause to #111 (Protocol error, unspecified) for the instruction in the UE policy section management result IE of the MANAGE UE POLICY COMMAND REJECT message.
  2. Receipt of an instruction associated with a UPSI which has a PLMN ID part that is not equal to the PLMN ID of the UE's HPLMN or the UE's RPLMN and the instruction contains a UE policy part with a UE policy part type set to "ANDSP" for a UE not operating in SNPN access operation mode.
    The UE shall set the UE policy delivery service cause to #111 (Protocol error, unspecified) for the instruction in the UE policy section management result IE of the MANAGE UE POLICY COMMAND REJECT message.
  3. Transmission failure of the MANAGE UE POLICY COMPLETE message indication from lower layers.
    The UE shall not diagnose an error and consider the network-initiated UE policy delivery procedure complete.
  4. Transmission failure of the MANAGE UE POLICY COMMAND REJECT message indication from lower layers.
    The UE shall not diagnose an error and consider the network-initiated UE policy delivery procedure complete.
  5. Receipt of a MANAGE UE POLICY COMMAND message with a PTI set to the same value as the PTI of a previously received MANAGE UE POLICY COMMAND message.
    The UE shall discard the message and retransmit the MANAGE UE POLICY COMMAND COMPLETE or MANAGE UE POLICY COMMAND REJECT message transmitted in response to the previously received MANAGE UE POLICY COMMAND message.
Up

D.2.2  UE-initiated UE state indication procedureWord‑p. 850

D.2.2.1  GeneralWord‑p. 850

The purpose of the UE-initiated UE state indication procedure is:
  1. to deliver the UPSI(s) of the UE policy section(s) which are:
    • identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN; and
    • stored in the UE;
    to the PCF if the UE has one or more stored UE policy sections identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN; and
  2. to indicate whether UE supports ANDSP; and
  3. to deliver the UE's one or more OS IDs.

D.2.2.2  UE-initiated UE state indication procedure initiationWord‑p. 850

In order to initiate the UE-initiated UE state indication procedure, the UE shall create a UE STATE INDICATION message. The UE:
  1. shall allocate a PTI value currently not used and set the PTI IE to the allocated PTI value;
  2. if not operating in SNPN access operation mode, shall include the UPSI(s) of the UE policy section(s) which are identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN available in the UE in the UPSI list IE;
  3. if operating in SNPN access operation mode, shall include UPSI(s) of the UE policy section(s) which are identified by a UPSI:
    • with the PLMN ID part indicating the MCC and MNC of the selected SNPN; and
    • associated with the NID of the selected SNPN;
    available in the UE in the UPSI list IE;
  4. shall specify whether the UE supports ANDSP in the UE policy classmark IE; and
  5. may include the UE's one or more OS IDs in the UE OS Id IE.
The UE shall send the UE STATE INDICATION message (see example in Figure D.2.2.2.1). The UE shall transport the created UE STATE INDICATION message using the registration procedure (see subclause 5.5.1).
Reproduction of 3GPP TS 24.501, Figure D.2.2.2.1: UE-initiated UE state indication procedure
Up

D.2.2.3  UE-initiated UE state indication procedure accepted by the networkWord‑p. 850

Upon receipt of the UE STATE INDICATION message, the PCF shall operate as described in TS 23.502 and TS 29.525.

D.2.2.4  Abnormal cases on the network sideWord‑p. 851

Apart from the case described in subclause D.2.2.3, no abnormal cases have been identified.

D.3  UE policy re-assembly at the UEWord‑p. 851

When the UE needs to apply ANDSP as specified in TS 24.502, the UE shall consider all UE policy parts with ANDSP contents currently stored at the UE.
When the UE needs to apply URSP as specified in TS 24.526, the UE shall consider all UE policy parts with URSP contents currently stored at the UE.
When the UE needs to apply V2XP as specified in TS 24.588, the UE shall consider all UE policy parts with V2XP contents currently stored at the UE.
When the UE needs to apply ProSeP as specified in TS 24.555 [19F], the UE shall consider all UE policy parts with ProSeP contents currently stored at the UE.
Up

D.4Void

D.5  Message functional definition and contentsWord‑p. 851

D.5.1  Manage UE policy commandWord‑p. 851

D.5.1.1  Message definitionWord‑p. 851

The MANAGE UE POLICY COMMAND message is sent by the PCF to the UE to request the UE to manage UE policy sections, see Table D.5.1.1.1.
Message type:
MANAGE UE POLICY COMMAND
Significance:
dual
Direction:
network to UE
IEI Information Element Type/Reference Presence Format Length
PTIProcedure transaction identity
9.6
MV1
MANAGE UE POLICY COMMAND message identityUE policy delivery service message type
D.6.1
MV1
UE policy section management listUE policy section management list
D.6.2
MLV-E11-65533
NOTE:
The total length of the MANAGE UE POLICY COMMAND message content cannot exceed 65535 octets (see Payload container contents maximum length as specified in subclause 9.11.3.39).
Up

D.5.2  Manage UE policy completeWord‑p. 851

D.5.2.1  Message definitionWord‑p. 851

The MANAGE UE POLICY COMPLETE message is sent by the UE to the PCF to report that all received instructions have been successfully executed at the UE, see Table D.5.2.1.1.
Message type:
MANAGE UE POLICY COMPLETE
Significance:
dual
Direction:
UE to network
IEI Information Element Type/Reference Presence Format Length
PTIProcedure transaction identity
9.6
MV1
MANAGE UE POLICY COMPLETE message identityUE policy delivery service message type
D.6.1
MV1
Up

D.5.3  Manage UE policy command rejectWord‑p. 852

D.5.3.1  Message definitionWord‑p. 852

The MANAGE UE POLICY COMMAND REJECT message is sent by the UE to the PCF to report that one or more instructions could not be successfully executed at the UE, see Table D.5.3.1.1.
Message type:
MANAGE UE POLICY COMMAND REJECT
Significance:
dual
Direction:
UE to network
IEI Information Element Type/Reference Presence Format Length
PTIProcedure transaction identity
9.6
MV1
MANAGE UE POLICY COMMAND REJECT message identityUE policy delivery service message type
D.6.1
MV1
UE policy section management resultUE policy section management result
D.6.3
MLV-E11-65533
NOTE:
The total length of the MANAGE UE POLICY COMMAND REJECT message content cannot exceed 65535 octets (see Payload container contents maximum length as specified in subclause 9.11.3.39).
Up

D.5.4  UE state indicationWord‑p. 852

D.5.4.1  Message definitionWord‑p. 852

The UE STATE INDICATION message is sent by the UE to the PCF:
  1. to deliver the UPSI(s) of the UE policy section(s) stored in the UE;
  2. to indicate whether the UE supports ANDSP; and
  3. to deliver the UE's one or more OS IDs;
see Table D.5.4.1.1.
Message type:
UE STATE INDICATION
Significance:
dual
Direction:
UE to network
IEI Information Element Type/Reference Presence Format Length
PTIProcedure transaction identity
9.6
MV1
UE STATE INDICATION message identityUE policy delivery service message type
D.6.1
MV1
UPSI listUPSI list
D.6.4
MLV-E9-65531
UE policy classmarkUE policy classmark
D.6.5
MLV2-4
41UE OS IdOS Id
D.6.6
OTLV18-242
NOTE:
The total length of the UE STATE INDICATION message content cannot exceed 65535 octets (see Payload container contents maximum length as specified in subclause 9.11.3.39).
Up

Up   Top   ToC