Content for TS 23.287 Word version: 18.4.0

1… 4… 4.2.1.2… 4.2.2… 4.3… 5… 5.2… 5.3… 5.4… 5.4.2… 5.5 5.6… 5.7… 5.10… 6… 6.2… 6.3… 6.3.3… 6.4… 6.5… A…

5.1 Authorization and Provisioning for V2X communications 5.1.1 General 5.1.2 Authorization and Provisioning for V2X communications over PC5 reference point 5.1.2.1 Policy/Parameter provisioning 5.1.2.2 Principles for applying parameters for V2X communications over PC5 reference point 5.1.3 Authorization and provisioning for V2X communications over Uu reference point 5.1.3.1 Policy/Parameter provisioning
...

5 High level functionality and features p. 17

5.1 Authorization and Provisioning for V2X communications p. 17

5.1.1 General p. 17

In 5GS, the parameters for V2X communications over PC5 and Uu reference points may be made available to the UE in following ways:

pre-configured in the ME; or
configured in the UICC; or
preconfigured in the ME and configured in the UICC; or
provided/updated by the V2X Application Server via PCF and/or V1 reference point; or
provided/updated by the PCF to the UE.

If the same parameters described in clause 5.1.2.1 and clause 5.1.3.1 are provided by different sources, the UE shall consider them in the following priority order:

provided/updated by the PCF;
provided/updated by the V2X Application Server via V1 reference point;
configured in the UICC;
pre-configured in the ME.

The parameters provided/updated by the V2X Application Server via V1 reference point may need to be complemented with configuration data from other sources listed above.

The basic principles of service authorization and provisioning for V2X communication over PC5 reference point and provisioning for V2X communication over Uu reference point are:

The UE may be authorized to use V2X communication over PC5 reference point on a per PLMN basis by the PCF in the HPLMN.
The PCF in the HPLMN merges authorization information from home and other PLMNs and provides the UE with the final authorization information.
The PCF in the VPLMN or HPLMN may revoke the authorization (via H-PCF when roaming) at any time by using the UE Configuration Update procedure for transparent UE Policy delivery procedure defined in clause 4.2.4.3 of TS 23.502.
The provisioning to UE for V2X communication over PC5 and Uu reference points is controlled by the PCF and may be triggered by UE. The PCF includes the V2X Policy/parameters for V2X communications over PC5 reference point as specified in clause 5.1.2.1 and/or the V2X Policy/parameters for V2X communications over Uu reference point as specified in clause 5.1.3.1 into a Policy Section identified by a Policy Section Identifier (PSI) as specified in clause 6.1.2.2.2 of TS 23.503.

5.1.2 Authorization and Provisioning for V2X communications over PC5 reference point p. 18

5.1.2.1 Policy/Parameter provisioning p. 18

The following sets of information for V2X communications over PC5 reference point is provisioned to the UE:

Authorization policy:
- When the UE is "served by E-UTRA" or "served by NR":
  - PLMNs in which the UE is authorized to perform V2X communications over PC5 reference point when "served by E-UTRA" or "served by NR".
    For each above PLMN:
    - RAT(s) over which the UE is authorized to perform V2X communications over PC5 reference point.
- When the UE is "not served by E-UTRA" and "not served by NR":
  - Indicates whether the UE is authorized to perform V2X communications over PC5 reference point when "not served by E-UTRA" and "not served by NR".
  - RAT(s) over which the UE is authorized to perform V2X communications over PC5 reference point.
NOTE 1:
In this specification, {When the UE is "served by E-UTRA" or "served by NR"} and {When the UE is "not served by E-UTRA" and "not served by NR"} are relevant to V2X communications over PC5 reference point.
Radio parameters when the UE is "not served by E-UTRA" and "not served by NR":
- Includes the radio parameters per PC5 RAT (i.e. LTE PC5, NR PC5) with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". These radio parameters (e.g., frequency bands) are defined in TS 36.331 and TS 38.331. The UE uses the radio parameters to perform V2X communications over PC5 reference point when "not served by E-UTRA" and "not served by NR" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
NOTE 2:
Whether a frequency band is "operator managed" or "non-operator managed" in a given Geographical Area is defined by local regulations.
Policy/parameters for PC5 RAT selection and for PC5 Tx Profile selection:
- the mapping of V2X service types to PC5 RAT(s) (e.g. LTE PC5, NR PC5 or both), and:
  - for LTE PC5, to the corresponding Tx Profiles (see TS 36.300 for further information);
  - for NR PC5, to the corresponding NR Tx Profiles for broadcast and groupcast (see TS 38.300 and TS 38.331 for further information);
  - for NR PC5, to the corresponding NR eTx Profiles for broadcast and groupcast (see TS 38.300 and TS 38.331 for further information);
    
    NOTE 3:
    Configuration related to backward compatibility requirements for V2X service types in the NR eTx Profiles for broadcast and groupcast can be set per geographical area.
  - for NR PC5, to the corresponding NR Tx Profiles for transmitting and receiving initial signalling to establish unicast connection (see TS 38.300 and TS 38.331 for further information).
  NOTE 4:
  The policy/parameter encoding ensures that the UEs of prior to Release 17 that are not able to handle the NR Tx Profile do not use V2X service types with a mapping of NR Tx Profile indicating the transmission mechanism or format specified in Release 17.
  
  NOTE 5:
  The policy/parameter encoding ensures that the UEs of prior to Release 18 that are not able to handle the NR eTx Profile do not use V2X service types with a mapping of NR eTx Profile indicating the transmission mechanism or format specified in Release 18.
Policy/parameters related to privacy:
- The list of V2X service types, with Geographical Area(s) that require privacy support.
- A privacy timer value indicating the duration after which the UE shall change each source Layer-2 ID self-assigned by the UE when privacy is required.
Policy/parameters when LTE PC5 is selected:
Same as specified in clause 4.4.1.1.2 of TS 23.285, item 3) Policy/parameters except for the mapping of V2X service types to Tx Profiles and the list of V2X services with Geographical Area(s) that require privacy support.
Policy/parameters when NR PC5 is selected:
- The mapping of V2X service types to V2X frequencies with Geographical Area(s).
- The mapping of V2X service types to the default mode of communication (i.e. broadcast mode, groupcast mode or unicast mode).
- The mapping of V2X service types to Destination Layer-2 ID(s) for broadcast.
- The mapping of V2X service types to Destination Layer-2 ID(s) for groupcast mode communication.
- The mapping of V2X service types to default Destination Layer-2 ID(s) for initial signalling to establish unicast connection.
  
  NOTE 6:
  The same default Destination Layer-2 ID for unicast initial signalling can be mapped to more than one V2X service types. In the case where different V2X services are mapped to distinct default Destination Layer-2 IDs, when the UE intends to establish a single unicast link that can be used for more than one V2X service types, the UE can select any of the default Destination Layer-2 IDs to use for the initial signalling.
- The mapping of V2X service types to PC5 QoS parameters defined in clause 5.4.2 (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.).
- AS layer configurations (see TS 38.331), e.g. the mapping of PC5 QoS profile(s) to radio bearer(s), when the UE is "not served by E-UTRA" and "not served by NR".
  - The PC5 QoS profile contains PC5 QoS parameters described in clause 5.4.2, and value for the QoS characteristics regarding Priority Level, Averaging Window, Maximum Data Burst Volume if default value is not used as defined in Table 5.4.4-1.
- For broadcast, groupcast and initial signalling to establish unicast connection, PC5 DRX configurations (see TS 38.331), e.g. the mapping of PC5 QoS profile(s) to PC5 DRX cycle(s), default PC5 DRX configuration, when the UE is "not served by E-UTRA" and "not served by NR".
Validity timer indicating the expiration time of the V2X Policy/Parameter.

The above parameter sets from bullet 2) to 6) may be configured in the UE through the V1 reference point by the V2X Application Server.

5.1.2.2 Principles for applying parameters for V2X communications over PC5 reference point p. 20

For V2X communication over PC5 reference point, the operator may pre-configure the UEs with the required provisioning parameters for V2X communication, without the need for the UEs to connect to the 5GC to get this initial configuration. The following apply:

The provisioning parameters for V2X communications over PC5 reference point may be configured in the UICC, in the ME, or in both the UICC and the ME.
The ME provisioning parameters shall not be erased when a USIM is deselected or replaced.
If both the UICC and the ME contain the same set of overlapping provisioning parameters, the set of parameters from the UICC shall take precedence.
The provisioning parameters from the PCF or V2X Application Server via V1 reference point shall take precedence over the pre-configured parameters in the ME and UICC as defined in clause 5.1.1.
The UE shall use radio resources for V2X communications over PC5 reference point as follows:
- While a UE has a serving cell and is camped on a cell and the UE intends to use for V2X service the radio resources (i.e. carrier frequency) operated by this cell, then the UE shall use the radio resource description indicated by this cell the UE is camped on and ignore any radio resource description of the same radio resource provisioned in the ME or the UICC. If the cell does not provide radio resources for V2X service, the UE shall not perform V2X message transmission and reception on radio resources operated by this cell.
- If the UE intends to use "operator-managed" radio resources (i.e. carrier frequency) for V2X service that are not operated by the UE's serving cell, as specified in clause 5.1.2.1, or if the UE is out of coverage, the UE shall search for a cell in any PLMN that is operating the provisioned radio resources (i.e. carrier frequency) as defined in TS 36.300 and TS 36.304 (if LTE based PC5 is selected for the V2X communication) or as defined in TS 38.300 and TS 38.304 (if NR based PC5 is selected for the V2X communication), and:
  - If the UE finds such a cell in the registered PLMN or a PLMN equivalent to the registered PLMN, and authorization for V2X communications over PC5 reference point to this PLMN is confirmed, the UE shall use the radio resource description indicated by that cell. If that cell does not provide radio resources for V2X service, the UE shall not perform V2X message transmission and reception on those radio resources.
  - If the UE finds such a cell but not in the registered PLMN or a PLMN equivalent to the registered PLMN, and that cell belongs to a PLMN authorized for V2X communications over PC5 reference point and provides radio resources for V2X service then the UE shall perform PLMN selection triggered by V2X communications over PC5 reference point as defined in TS 23.122. If the UE has an ongoing emergency session via IMS, it shall not trigger any PLMN selection due to V2X communication over PC5 reference point.
  - If the UE finds such cell but not in a PLMN authorized for V2X communications over PC5 reference point the UE shall not use V2X communications over PC5 reference point.
  - If the UE does not find any such cell in any PLMN, then the UE shall consider itself "not served by NR or E-UTRA" and use radio resources provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize V2X communications over PC5 reference point, then the UE is not authorized to transmit.
- If the UE intends to use "non-operator-managed" radio resources (i.e. carrier frequency) for V2X service, according to TS 36.331 or TS 38.331 and as specified in clause 5.1.2.1, then the UE shall perform V2X communication over PC5 using resource provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize V2X communications over PC5 reference point, then the UE is not authorized to transmit.
The UE provisioning shall support setting Geographical Areas.

NOTE 1:
It is possible for a UE to use other radio resources for V2X service based on the Geographical Area instead of those operated by the serving NG-RAN cell, when provisioned in the UE, even if the UE's serving cell offers normal service and the SIBs for NR sidelink communication or V2X sidelink communication defined in TS 38.331 indicates that the service (V2X communication) is available. This is to cover the scenario when e.g. the radio resources used for V2X communications over PC5 reference point are not owned by the serving network of the UE.

NOTE 2:
When cross-carrier operation is supported, according to TS 36.331 or TS 38.331, a UE can be instructed by its serving cell to perform V2X communication over a different carrier frequency. The UE is still considered as "served by NR or E-UTRA" in this case.

NOTE 3:
The scenario that a cell is detected and the cell does not provide support for V2X communications over PC5 reference point when the UE attempts to use a carrier frequency configured for V2X communications over PC5 reference point, is considered a configuration error. Therefore, the UE does not transmit on that frequency to avoid interference to the network.
The V2X communications over PC5 reference point is only specified for E-UTRA and NR.

NOTE 4:
It is out of scope of the present specification to define how the UE can locate itself in a specific Geographical Area. When the UE is in coverage of a 3GPP RAT, it can for example, use information derived from the serving PLMN. When the UE is not in coverage of a 3GPP RAT, it can use other techniques, e.g. Global Navigation Satellite System (GNSS). User provided location is not a valid input.

5.1.3 Authorization and provisioning for V2X communications over Uu reference point p. 21

5.1.3.1 Policy/Parameter provisioning p. 21

The following set of information may be provisioned to the UE for V2X communications over Uu reference point:

Mapping of the V2X service types to:
- PDU Session Type (i.e. IP type or Unstructured type);
- Transport layer protocol (i.e. UDP or TCP, only applicable for IP PDU Session type);
- SSC Mode;
- S-NSSAI(s);
- DNN(s).
NOTE:
Above listed information elements are optional and used by UE as UE Local Configuration specified in TS 23.503.
Mapping of the V2X service types to MBS session announcement for V2X message reception via MBS.
MBS session announcement for receiving V2X Application Server information via MBS (i.e. for V2X Application Sever discovery using MBS).
Validity timer indicating the expiration time of the V2X Policy/Parameter.

The following sets of information may be provisioned to the UE and is applicable for V2X communications over both LTE-Uu reference point (i.e. for EPS) and Uu reference point (i.e. for 5GS):

Mapping of the V2X service types to V2X Application Server address information (consisting of IP address/FQDN and transport layer port#) for unicast.
List of FQDNs or IP addresses of the V2X Application Servers, associated with served geographical area information and list of PLMNs that the configuration applies to.