Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  18.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.6.8   D.7…

 

D (Normative)  UE policy delivery servicep. 1082

D.1  Generalp. 1082

D.1.1  Overviewp. 1082

The UE provides the PCF with a list of one or more stored UE policy section identifiers (UPSIs) during the UE-initiated UE state indication procedure. 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.
During the UE-initiated UE state indication procedure, the UE also provides the PCF with the UE policy related capabilities such as the UE's support for ANDSP, the UE's support for URSP provisioning in EPS, and the UE's OS Id.
During the network-requested UE policy management procedure, the PCF provides the UE with one or more UE policy sections containing UE policies. The UE processes the received UE policy sections, each identified by the UPSI, received from the PCF and informs the PCF of the result.
In the present annex, the condition that the PLMN ID part of the UPSI is referring to the HPLMN shall be considered as fulfilled only if the PLMN ID is equal to the HPLMN code derived from the IMSI.
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.554.
The UE can also request the PCF to provide A2XP as specified in TS 24.577 [60].
The UE can also request the PCF to provide RSLPP as specified in TS 24.514 [62].
Up

D.1.2  Principles of PTI handling for UE policy delivery service proceduresp. 1082

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, Fig. D.1.2.1: Network-requested transaction related procedure
Up
Reproduction of 3GPP TS 24.501, Fig. D.1.2.2: UE-requested transaction related procedure rejected by the network
Up
Reproduction of 3GPP TS 24.501, Fig. D.1.2.3: UE-requested transaction related procedure triggering a network-requested transaction related procedure
Up

D.2  Proceduresp. 1084

D.2.1  Network-requested UE policy management procedurep. 1084

D.2.1.1  Generalp. 1084

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;
and optionally to enable the HPLMN or the subscribed SNPN to provide a UE accessing the subscribed SNPN or the HPLMN with a non-subscribed SNPN signalled URSP handling indication indicating whether the UE is allowed to accept URSP signalled by non-subscribed SNPNs.
Up

D.2.1.2  Network-requested UE policy management procedure initiationp. 1084

In order to initiate the network-requested UE policy management procedure, the PCF shall:
a)
if the network-requested UE policy management procedure is triggered by the UE-requested V2X policy provisioning procedure as specified in TS 24.587, the UE-requested ProSe policy provisioning procedure as specified in TS 24.554 or the UE-requested A2X policy provisioning procedure as specified in TS 24.577 [60], then set the PTI IE to the PTI value of the received UE POLICY PROVISIONING REQUEST message of the UE-requested V2X policy provisioning procedure, the UE-requested ProSe policy provisioning procedure or the UE-requested A2X policy provisioning procedure, otherwise allocate a PTI value currently not used and set the PTI IE to the allocated PTI value;
b)
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;
c)
if the PCF is a PCF of the HPLMN or the subscribed SNPN, optionally include the UE policy network classmark IE in a MANAGE UE POLICY COMMAND message and set the non-subscribed SNPN signalled URSP handling indication of the UE policy network classmark IE to "UE is not allowed to accept URSP signalled by non-subscribed SNPNs", or "UE is allowed to accept URSP signalled by non-subscribed SNPNs";
c1)
if the UE supports VPS URSP, optionally encode the information about entries of VPS URSP configuration to be added, modified or deleted in the VPS URSP configuration IE as specified in subclause D.6.8 and include it in a MANAGE UE POLICY COMMAND message;
d)
send the MANAGE UE POLICY COMMAND message to the UE via the AMF as specified in TS 23.502; and
e)
start timer T3501 (see example in Figure D.2.1.2.1).
Reproduction of 3GPP TS 24.501, Fig. 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 by a network-requested UE policy management procedure, 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 of the instruction is empty;
additionally, if the UE policy network classmark IE is included in the MANAGE UE POLICY COMMAND message, and
  1. the UE has an empty EHPLMN list or the EHPLMN list is not present, and the UE's RPLMN is the HPLMN;
  2. the UE has a non-empty EHPLMN list, and the UE's RPLMN is an EHPLMN; or
  3. the UE's RSNPN is the subscribed SNPN,
the UE shall delete the non-subscribed SNPN signalled URSP handling indication stored for the selected entry of "list of subscriber data" or the selected PLMN subscription, if any, and store the non-subscribed SNPN signalled URSP handling indication received in the UE policy network classmark IE, for the selected entry of "list of subscriber data" or the selected PLMN subscription.
If the UE supports the VPS URSP, and the VPS URSP configuration is included in the MANAGE UE POLICY COMMAND message:
  1. if the replacement type field of the received VPS URSP configuration indicates "full list of tuples", the UE shall delete the stored VPS URSP configuration, if any; and
  2. if the received VPS URSP configuration contains one or more tuples:
    1. if the UE does not have the stored VPS URSP configuration, the UE shall store the received VPS URSP configuration except zero or more tuples with no UPSCs; or
    2. otherwise:
      1. for each tuple with a tuple ID in the stored VPS URSP configuration:
        1. if a tuple with the tuple ID is in the received VPS URSP configuration and contains:
          • no UPSCs, the UE shall delete the tuple with the tuple ID from the stored VPS URSP configuration; or
          • one or more UPSCs, the UE shall replace the tuple with the tuple ID in the stored VPS URSP configuration with the tuple with the tuple ID from the received VPS URSP configuration; or
        2. if no tuple with the tuple ID is in the received VPS URSP configuration, the UE shall keep the tuple with the tuple ID in the stored VPS URSP configuration; and
      2. for each tuple with a tuple ID in the received VPS URSP configuration, if no tuple with the tuple ID is in the stored VPS URSP configuration and:
        1. the tuple with the tuple ID in the received VPS URSP configuration contains no UPSCs, the UE shall ignore the tuple with the tuple ID in the received VPS URSP configuration; or
        2. the tuple with the tuple ID in the received VPS URSP configuration contains one or more UPSCs, the UE shall add the tuple with the tuple ID from the received VPS URSP configuration to the stored VPS URSP configuration.
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 other than the RPLMN and the HPLMN or for an SNPN other than the registered SNPN and the subscribed SNPN, before storing the new received UE policy sections.
When storing a UE policy section 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 UEp. 1086

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 UEp. 1086

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 results by including:
    1. the UPSI associated with the instructions which could not be executed successfully;
    2. the failed instruction order set to order of the instruction in the UE policy section management sublist of the received UE policy section management list IE which could not be executed successfully; and
    3. the cause of the failure,
    in the 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 but not indicated in the UE policy section management result IE of the received MANAGE UE POLICY COMMAND REJECT message, shall be 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 sidep. 1087

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 UEp. 1087

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 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 subscribed SNPN or the UE's RSNPN and the instruction contains a UE policy part with a UE policy part type set to "ANDSP" 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.
  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-requested UE policy management procedure is 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-requested UE policy management procedure is 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.
  6. Receipt of an instruction associated with a UPSI which has a PLMN ID part that is equal to the PLMN ID part of the selected SNPN, the instruction contains a UE policy part with a UE policy part type set to "URSP", UE's RSNPN is a non-subscribed SNPN and:
    1. the UE has a stored non-subscribed SNPN signalled URSP handling indication for the selected entry of "list of subscriber data" or the selected PLMN subscription indicating that the UE is not allowed to accept URSP signalled by non-subscribed SNPNs; or
    2. the UE does not have a stored non-subscribed SNPN signalled URSP handling indication for the selected entry of "list of subscriber data" or the selected PLMN subscription, and the non-subscribed SNPN signalled URSP handling indication preconfigured in the selected entry of "list of subscriber data" or the selected PLMN subscription indicates that the UE is not allowed to accept URSP signalled by non-subscribed SNPNs;
    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.
Up

D.2.2  UE-initiated UE state indication procedurep. 1088

D.2.2.1  Generalp. 1088

The purpose of the UE-initiated UE state indication procedure is:
a)
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, if any; or
  • identified by a UPSI with the PLMN ID part indicating the PLMN ID part of the SNPN identity of the selected SNPN and associated with the NID of the selected SNPN, and stored in the UE, if any;
b)
to indicate whether UE supports ANDSP;
c)
to indicate whether UE supports URSP provisioning in EPS;
c1)
to indicate whether UE supports VPS URSP;
d)
to indicate whether UE supports reporting URSP rule enforcement; and
e)
to deliver the UE's one or more OS IDs;
to the PCF.
Up

D.2.2.2  UE-initiated UE state indication procedure initiationp. 1089

In order to initiate the UE-initiated UE state indication procedure, the UE shall create a UE STATE INDICATION message. The UE:
a)
shall allocate a PTI value currently not used and set the PTI IE to the allocated PTI value;
b)
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, if any;
c)
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, if any;
d)
shall specify whether the UE supports ANDSP in the UE policy classmark IE;
e)
shall specify whether the UE supports URSP provisioning in EPS in the UE policy classmark IE;
e1)
if the UE supports VPS URSP, shall set the SVPSU bit to "VPS URSP supported by the UE" in the UE policy classmark IE;
f)
if the UE supports reporting URSP rule enforcement, shall set the SupportRURE bit to "Reporting URSP rule enforcement supported by the UE"; and
g)
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, Fig. 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 networkp. 1089

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 sidep. 1090

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 UEp. 1090

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.
  1. if the UE supports VPS URSP then:
    1. the UE shall consider as VPS URSP of the RPLMN all UE policy parts with URSP contents currently stored at the UE, which are a part of one or more UE policy sections identified by a UPSI:
      1. with the PLMN ID part indicating the HPLMN; and
      2. with UPSC indicated in a tuple of the stored VPS URSP configuration, such that the tuple contains the network descriptor with a network descriptor entry containing:
        1. the network descriptor entry type field set to "one or more VPLMNs" and the network descriptor entry value field containing PLMN ID of the RPLMN of an access, if the UE is registered via one or both accesses and the RPLMN of each access is a VPLMN;
        2. the network descriptor entry type field set to "one or more MCCs" and the network descriptor entry value field containing MCC of the PLMN ID of the RPLMN of an access, if the UE is registered via one or both accesses and the RPLMN of each access is a VPLMN; or
        3. the network descriptor entry type field set to "any VPLMN", if the UE is registered via one or both accesses and the RPLMN of each access is a VPLMN;
    2. the UE shall consider as VPS URSP of the equivalent PLMN of the RPLMN all UE policy parts with URSP contents currently stored at the UE, which are a part of one or more UE policy sections identified by a UPSI:
      1. with the PLMN ID part indicating the HPLMN; and
      2. with UPSC indicated in a tuple of the stored VPS URSP configuration, such that the tuple contains the network descriptor with a network descriptor entry containing:
        1. the network descriptor entry type field set to "one or more VPLMNs" and the network descriptor entry value field containing PLMN ID of an equivalent PLMN, if the UE is registered via one or both accesses, the RPLMN of each access is a VPLMN and the equivalent PLMN is a VPLMN;
        2. the network descriptor entry type field set to "one or more MCCs" and the network descriptor entry value field containing MCC of the PLMN ID of an equivalent PLMN, if the UE is registered via one or both accesses, the RPLMN of each access is a VPLMN and the equivalent PLMN is a VPLMN; or
        3. the network descriptor entry type field set to "any VPLMN", if the UE is registered via one or both accesses, the RPLMN of each access is a VPLMN and an equivalent PLMN is a VPLMN; and
    3. the UE shall consider as PG URSP all UE policy parts with URSP contents currently stored at the UE except zero or more UE policy parts, if any, which are a part of one or more UE policy sections identified by a UPSI:
      1. with the PLMN ID part indicating the HPLMN; and
      2. with UPSC indicated in any tuple of the stored VPS URSP configuration; and
  2. the UE shall consider all UE policy parts with URSP contents currently stored at the UE as the signalled URSP.
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, the UE shall consider all UE policy parts with ProSeP contents currently stored at the UE.
When the UE needs to apply A2XP as specified in TS 24.578 [61], the UE shall consider all UE policy parts with A2XP contents currently stored at the UE.
When the UE needs to apply RSLPP as specified in TS 24.514 [62], the UE shall consider all UE policy parts with RSLPP contents currently stored at the UE.
Up

D.4Void

D.5  Message functional definition and contentsp. 1091

D.5.1  Manage UE policy commandp. 1091

D.5.1.1  Message definitionp. 1091

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
42UE policy network classmarkUE policy network classmark
D.6.7
OTLV3-5
70VPS URSP configurationVPS URSP configuration
D.6.8
OTLV-E3-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.1.2  UE policy network classmark |R17|p. 1091

The UE policy network classmark is included when the PCF of a PLMN or an SNPN intends to provide the UE with information about the policy aspects of the network.

D.5.1.3  VPS URSP configuration |R18|p. 1091

The VPS URSP configuration IE is included when the PCF of a PLMN intends to provide the UE with the VPS URSP configuration.

D.5.2  Manage UE policy completep. 1092

D.5.2.1  Message definitionp. 1092

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 rejectp. 1092

D.5.3.1  Message definitionp. 1092

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 indicationp. 1092

D.5.4.1  Message definitionp. 1092

The UE STATE INDICATION message is sent by the UE to the PCF:
a)
to deliver the UPSI(s) of the UE policy section(s) stored in the UE;
b)
to indicate whether the UE supports ANDSP;
c)
to indicate whether the UE supports URSP provisioning in EPS in the UE policy classmark IE;
c1)
to indicate whether the UE supports VPS URSP;
c2)
to indicate whether the UE supports reporting URSP rule enforcement; and
d)
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-E2-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