Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.287  Word version:  17.1.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.4…   6…   6.3…   6.4…   A…

 

4  Architecture model and conceptsWord‑p. 10

4.1  General conceptWord‑p. 10

There are two modes of operation for V2X communication, namely V2X communication over PC5 reference point and V2X communication over Uu reference point. These two operation modes may be used by a UE independently for transmission and reception.
V2X communications over PC5 reference point are supported by LTE and/or NR.
V2X communications over Uu reference point are supported by E-UTRA connected to 5GC and/or NR connected to 5GC. In this release, V2X communication over Uu reference point is only unicast.
An RSU is not an architectural entity, but an implementation option. This is achieved by collocating a V2X application logic/server with some entities of the 3GPP system, as shown in examples in Annex B.
Up

4.2  Architectural reference modelWord‑p. 10

4.2.1  PC5 and Uu based V2X architecture reference modelWord‑p. 10

4.2.1.1  Non-roaming 5G System architecture for V2X communication over PC5 and Uu reference pointsWord‑p. 10

Figure 4.2.1.1-1 shows the high level view of the non-roaming 5G System architecture for V2X communication over PC5 and Uu reference points.
Reproduction of 3GPP TS 23.287, Figure 4.2.1.1-1: Non-roaming 5G System architecture for V2X communication over PC5 and Uu reference points
Up

4.2.1.2  Roaming 5G System architecture for V2X communication over PC5 and Uu reference pointsWord‑p. 11

Figure 4.2.1.2-1 and Figure 4.2.1.2-2 show the high level view of the roaming 5G System architectures for V2X communication over PC5 and Uu reference points. In these Figures, UE A uses a subscription of HPLMN.
Reproduction of 3GPP TS 23.287, Figure 4.2.1.2-1: Roaming 5G System architecture for V2X communication over PC5 and Uu reference points - Local breakout scenario
Up
Reproduction of 3GPP TS 23.287, Figure 4.2.1.2-2: Roaming 5G System architecture for V2X communication over PC5 and Uu reference points - Home routed scenario
Up

4.2.1.3  Inter-PLMN 5G System architecture for V2X communication over PC5 reference pointWord‑p. 12

In the case of inter-PLMN V2X communication over PC5 reference point, the PC5 parameters need to be configured in a consistent way among the UEs within a certain region. The architecture for the Inter-PLMN PC5 case is similar to the one defined in clause 4.2.1.1.

4.2.2  AF-based service parameter provisioning for V2X communicationsWord‑p. 12

The 5G System provides NEF services to enable communication between NFs in the PLMN and V2X Application Server. Figure 4.2.2-1 shows the high level view of AF-based service parameter provisioning for V2X communications. The V2X Application Server may provide V2X service parameters to the PLMN via NEF. The NEF stores the V2X service parameters in the UDR.
Copy of original 3GPP image for 3GPP TS 23.287, Figure 4.2.2-1: 5G System architecture for AF-based service parameter provisioning for V2X communications
Up

4.2.3  Reference pointsWord‑p. 12

V1:
The reference point between the V2X applications in the UE and in the V2X Application Server. This reference point is out of scope of this specification.
V5:
The reference point between the V2X applications in the UEs. This reference point is not specified in this release of the specification.
PC5:
The reference point between the UEs, and it includes the LTE based PC5 and/or NR based PC5.
N1:
In addition to the relevant functions defined in TS 23.501 for N1, in the case of V2X Service it is also used to convey the V2X policy and parameters (including service authorization) from AMF to UE and to convey the UE's V2X Capability and PC5 Capability for V2X information from UE to AMF.
N2:
In addition to the relevant functions defined in TS 23.501 for N2, in the case of V2X Service it is also used to convey the V2X policy and parameters (including service authorization) from AMF to NG-RAN.
Uu:
The reference point between the UE and the NG-RAN.
Up

4.2.4  Service-based interfacesWord‑p. 13

Nudm:
In addition to the relevant services defined in TS 23.501 for Nudm, in the case of V2X Service, services provided by UDM are used to get V2X Service related subscription information to AMF during Initial registration procedure or UE Configuration Update (UCU) procedure to inform AMF subscription information has changed.
Npcf:
In addition to the relevant services defined in TS 23.501 for Npcf, in the case of V2X Service, services provided by H-PCF are used to provide V2X Service related parameters to V-PCF for UE and NG-RAN in the roaming case.
Nudr:
In addition to the relevant services defined in TS 23.501 for Nudr, in the case of V2X Service, services provided by UDR are used to notify the PCF and the UDM of the update of the V2X Service related information.
Nnef:
In addition to the relevant services defined in TS 23.501 for Nnef, in the case of V2X Service, services provided by NEF are used by the V2X Application Server to update V2X Service related information of 5GC.
Namf:
In addition to the relevant services defined in TS 23.501 for Namf, in the case of V2X Service, services provided by AMF are consumed by PCF to provide the V2X Service related parameters for the UE and the NG-RAN to AMF, and to enable the AMF create or update UE context related to V2X service.
Nnrf:
In addition to the relevant services defined in TS 23.501 for Nnrf, in the case of V2X Service, services provided by NRF are used to discover the PCF that supports V2X.

4.3  Architecture reference model for interworking with EPS V2XWord‑p. 13

The interworking between 5GS V2X and EPS V2X does not require any new interface between 5GS V2X and EPS V2X architectures and does not impact existing network function entities in EPC and 5GC. Figure 4.3-1 shows one of the architecture reference models.
Copy of original 3GPP image for 3GPP TS 23.287, Figure 4.3-1: Architecture for interworking with EPS V2X, Local breakout roaming
Up
Legend:
  • The functions and reference points for EPS V2X are defined in TS 23.285.

4.4  Functional entitiesWord‑p. 14

4.4.1  UEWord‑p. 14

In addition to the functions defined in TS 23.501, the UE may support the following functions:
  • Report the V2X Capability and PC5 Capability for V2X to 5GC over N1 reference point.
  • Indicate V2X Policy Provisioning Request in UE Policy Container for UE triggered V2X Policy provisioning.
  • Receive the V2X parameters from 5GC over N1 reference point.
  • Procedures for V2X communication over PC5 reference point.
  • Configuration of parameters for V2X communication (e.g., destination Layer-2 IDs, radio resource parameters, V2X Application Server address information, mapping between V2X service types and V2X frequencies, see clause 5.1). These parameters can be pre-configured in the UE, or, if in coverage, provisioned or updated by signalling over the N1 reference point from the PCF in the HPLMN or over V1 reference point from the V2X Application Server.
Up

4.4.2  PCFWord‑p. 15

In addition to the functions defined in TS 23.501, the PCF includes the function to provision the UE and AMF with necessary parameters in order to use V2X communication:
  • May determine the V2X Policy/Parameter for specific PC5 RAT to provision to the UE based on the received UE's PC5 Capability for V2X.
  • Determines whether to provision V2X Policy/parameters for V2X communication over PC5 reference point and/or V2X communication over Uu reference point to the UE.
  • Provision the UEs with authorization and policy parameters for V2X communication over PC5 reference point.
  • Provision the UEs with policy parameters for V2X communication over Uu reference point.
  • Provision the AMF with PC5 QoS parameters as defined in clause 5.4.2 used by NG-RAN.
  • Retrieve V2X parameters from UDR.
Up

4.4.3  V2X Application ServerWord‑p. 15

The V2X Application Server (V2X AS) includes AF functionality, and may support at least the following capabilities:
For V2X services handling,
  • Receive uplink data from the UE over unicast.
  • Send downlink data to the UE over unicast.
  • Request QoS Sustainability Analytics for potential QoS changes in a geographic area from NWDAF via NEF.
For V2X service parameters provisioning,
  • Provision the 5GC with parameters for V2X communications over PC5 and Uu reference points.
  • Provision the UE with parameters for V2X communications over PC5 reference point and/or Uu reference point.
Up

4.4.4  AMFWord‑p. 15

In addition to the functions defined in TS 23.501, the AMF performs the following functions:
  • Obtain from UDM the subscription information related to V2X and store them as part of the UE context data.
  • Select a PCF supporting V2X Policy/Parameter provisioning and report the PC5 Capability for V2X to the selected PCF.
  • Obtain from PCF the PC5 QoS information related to V2X and store it as part of the UE context data.
  • Provision the NG-RAN with indication about the UE authorization status about V2X communication over PC5 reference point.
  • Provision the NG-RAN with PC5 QoS parameters related to V2X communication.
Up

4.4.5  UDMWord‑p. 15

In addition to the functions defined in TS 23.501, the UDM performs the following functions:
  • Subscription management for V2X communication over PC5 reference point.

4.4.6  UDRWord‑p. 16

In addition to the functions defined in TS 23.501, the UDR performs the following functions:
  • Stores V2X service parameters.

4.4.7  NRFWord‑p. 16

In addition to the functions defined in TS 23.501, the NRF performs the following functions:
  • PCF discovery by considering V2X capability.

4.4.8  NEF |R17|Word‑p. 16

The high-level functions are the same as defined in TS 23.501.
For Application Functions to provide service specific information to the 3GPP network, the NEF supports additional V2X service parameters as specified in clause 6.2.5.

Up   Top   ToC