Content for TS 23.286 Word version: 18.4.0

0… 4… 6… 7… 9… 9.2… 9.3… 9.4… 9.5… 9.6… 9.7… 9.8… 9.9… 9.10… 9.11… 9.12… 9.13… 9.14… 9.15… 9.16… 9.17… 9.18 9.19… 9.20… 9.21… 9.22… 10… 10.2.8… A B… C… D…

7.1 General 7.2 Deployment of VAE server 7.2.1 Centralized deployments 7.2.2 Distributed deployment 8.1 V2X user identity (V2X user ID) 8.2 V2X UE identity (V2X UE ID) 8.3 V2X service identity (V2X service ID) 8.4 V2X group identity (V2X group ID) 8.5 Geographical area identity (GEO ID)
...

7 Deployment models p. 24

7.1 General p. 24

This clause describes deployments of the functional model specified in clause 6. The reference points utilized from underlying 3GPP network as specified in clause 6.5 is represented as 3GPP interfaces in the deployment models.

7.2 Deployment of VAE server p. 24

The VAE server deployments can be centralized and distributed.

7.2.1 Centralized deployments p. 25

A centralized deployment is where a single VAE server offers the VAE capabilities to one or more V2X application specific server. The VAE server and the V2X application specific server may be co-located in a single physical entity. The VAE server may be deployed either in the PLMN operator domain or deployed in the V2X service provider domain. The VAE server connects with the 3GPP network systems (EPS, 5GS) in one or more PLMN operator domain. When VAE server and V2X application specific server are co-located in a single physical entity, the Vs reference point between the VAE server and the V2X application enabler server may not be used.

Figure 7.2.1-1 illustrates a deployment of the VAE server and the V2X application specific server in a single physical entity and deployed in V2X service provider domain. The VAE server may be deployed in a separate physical entity from the V2X application specific server in the V2X service provider domain. In such deployments, the Vs reference point is used for the communication between the VAE server and the V2X application specific server.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 7.2.1-1: VAE server co-located with V2X application specific server in a single physical entity

Figure 7.2.1-1: VAE server co-located with V2X application specific server in a single physical entity
(⇒ copy of original 3GPP image)

Figure 7.2.1-2 illustrates a deployment of the VAE server in the PLMN operator domain and the V2X application specific server in the V2X service provider domain. The Vs reference point is used for the communication between V2X application specific server and the VAE server. The VAE server may support multiple V2X application specific servers.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 7.2.1-2: VAE server deployed in the PLMN operator domain

Figure 7.2.1-2: VAE server deployed in the PLMN operator domain
(⇒ copy of original 3GPP image)

Figure 7.2.1-3 illustrates a deployment of the VAE server which connects to the 3GPP network systems (EPS, 5GS) in multiple PLMN operator domain. The VAE server may be co-located with the V2X application specific server in a single physical entity or deployed in different physical entities.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 7.2.1-3: Deployment of VAE server with connections to 3GPP network systems in multiple PLMN operator domains

Figure 7.2.1-3: Deployment of VAE server with connections to 3GPP network systems in multiple PLMN operator domains
(⇒ copy of original 3GPP image)

Figure 7.2.1-4 illustrates a deployment of the VAE server which provides VAE capabilities to multiple V2X application specific servers over Vs reference point and connects to the 3GPP network systems (EPS, 5GS) in multiple PLMN operator domain.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 7.2.1-4: Deployment of VAE server with connections to multiple V2X application specific servers

Figure 7.2.1-4: Deployment of VAE server with connections to multiple V2X application specific servers
(⇒ copy of original 3GPP image)

7.2.2 Distributed deployment p. 26

The distributed deployment is where multiple VAE servers are deployed either in the V2X service provider domain or in the PLMN operator domain. The distributed deployment of the VAE servers provide geographical coverage or support multiple PLMN operator domains in a geographical location. The VAE servers interconnect via VAE-E and the Vs reference point is used for interaction between V2X application specific server and the VAE server.

Figure 7.2.2-1 illustrates the deployment of VAE servers in multiple PLMN operator domain and provides VAE capabilities to the V2X application specific server deployed in the V2X service provider domain. The V2X application specific server connects via Vs to the VAE servers.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 7.2.2-1: Distributed deployment of VAE servers in multiple PLMN operator domain without interconnection between VAE servers

Figure 7.2.2-1: Distributed deployment of VAE servers in multiple PLMN operator domain without interconnection between VAE servers
(⇒ copy of original 3GPP image)

Figure 7.2.2-2 illustrates the deployment of multiple VAE servers deployed in multiple PLMN operator domains. The V2X application specific server connects via Vs to the VAE server. The interconnection between VAE servers is via VAE-E and supports the V2X applications for the V2X UEs connected to the VAE servers in multiple PLMN operator domains.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 7.2.2-2: Distributed deployment of VAE servers in multiple PLMN operator domain with interconnection between VAE servers

Figure 7.2.2-2: Distributed deployment of VAE servers in multiple PLMN operator domain with interconnection between VAE servers
(⇒ copy of original 3GPP image)

Figure 7.2.2-3 illustrates the deployment of multiple VAE servers in PLMN operator domain based on geographical coverage. The V2X application specific server connects via Vs to the VAE server 1. The VAE servers interconnect via VAE-E and support the V2X communications to the V2X UEs connected to the VAE servers.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 7.2.2-3: Distributed deployment of VAE servers in PLMN operator domain

Figure 7.2.2-3: Distributed deployment of VAE servers in PLMN operator domain
(⇒ copy of original 3GPP image)

Figure 7.2.2-4 illustrates the deployment of multiple VAE servers in the V2X service provider domain where VAE server 1 and VAE server 2 connect with 3GPP network system of PLMN operator domain 1 and PLMN operator domain 2 respectively. The PLMN operator domains provide coverage to different geographical areas. The V2X application specific server connects via Vs to the VAE server 1. The VAE servers interconnect via VAE-E and support the V2X applications for the V2X UEs connected via both the PLMN operator domains.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 7.2.2-4: Distributed deployment of VAE servers in V2X service provider domain

Figure 7.2.2-4: Distributed deployment of VAE servers in V2X service provider domain
(⇒ copy of original 3GPP image)

8 Identities p. 28

8.1 V2X user identity (V2X user ID) p. 28

The V2X user ID can be an instance of the VAL user ID as specified in TS 23.434. The V2X user ID is a globally unique identifier within the V2X service that represents the V2X user. The V2X user ID shall be a URI. The V2X user ID is used for authentication and authorization purposes for providing the V2X service towards the V2X user via the V2X UE. The V2X user ID also indicates the V2X service provider with whom the V2X user has a V2X service agreement. The V2X user may have V2X service agreement with several V2X service providers and thus will have obtained unique V2X user ID per V2X service provider.

Based on the service agreement, each V2X user ID is mapped to a V2X UE ID.

8.2 V2X UE identity (V2X UE ID) p. 29

The V2X UE ID can be an instance of the VAL UE ID as specified in TS 23.434. The V2X UE ID is a unique identifier within the V2X service that represents the V2X UE. The V2X UE ID is mapped to an application specific UE identity (e.g. StationID as specified in ETSI TS 102 894-2 [16] or GPSI as specified in TS 23.003). Due to privacy considerations, the V2X UE ID may be changed. The V2X UE ID is used to address the V2X UE in order to send V2X messages.

8.3 V2X service identity (V2X service ID) p. 29

The V2X service ID can be an instance of the VAL service ID as specified in TS 23.434. The V2X service ID is a globally unique identifier that represents the V2X service. A V2X application server provides a list of V2X services towards the V2X UE. Each V2X service is uniquely identified by a V2X service ID, which is an identifier of the V2X application. The V2X service ID can be used for policy mapping, QoS handling for V2X communication and V2X message distribution, as specified in TS 23.285. An identifier of a V2X service, e.g. ITS-AID or PSID specified in ETSI TS 102 965 [17] and ISO TS 17419 [18], can be used as a V2X service ID.

8.4 V2X group identity (V2X group ID) p. 29

The V2X group ID is a globally unique identifier within the V2X service that represents a set of V2X users and the corresponding V2X UE. The set of V2X users may belong to the same or different V2X service provider. It indicates the V2X application server where the group is defined.

8.5 Geographical area identity (GEO ID) p. 29

The V2X service provider defined identity of a geographical area. The GEO ID supports different representations of geographical area (e.g. geo-fence, tile identifiers). The VAE server maintains the mapping of the GEO ID with the location corresponding to one or more V2X UE IDs.

The GEO ID may support the format of a URI.