9.2 V2X UE registration

23.2863GPPApplication layer support for Vehicle-to-Everything (V2X) servicesFunctional architecture and information flowsRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

9.2.1 General

The VAE capabilities provide support for registering V2X UEs at the VAE server. The VAE server uses the registration information to distribute V2X messages to the appropriate V2X UEs.

9.2.2 Information flows

9.2.2.1 Registration request

Table 9.2.2.1-1 describes the information flow for a VAE client to register for specific V2X messages at the VAE server.

Table 9.2.2.1-1: Registration request

Information element	Status	Description
V2X UE ID	M	Identifier of the V2X UE (e.g. StationID specified in ETSI TS 102 894-2 [16])
V2X service ID	M	V2X service ID, the V2X UE is interested in receiving (e.g. PSID or ITS AID of ETSI ITS DENM, ETSI ITS CAM)
Supported RAT types	O	RAT types (e.g. NR, E-UTRA) supported by the V2X UE

9.2.2.2 Registration response

Table 9.2.2.2-1 describes the information flow for VAE server to respond for registration request from the VAE client.

Table 9.2.2.2-1: Registration response

Information element	Status	Description
Result	M	Result from the VAE server in response to registration request indicating success or failure

9.2.2.3 Deregistration request

Table 9.2.2.3-1 describes the information flow for a VAE client to deregister from receiving specific V2X messages from the VAE server.

Table 9.2.2.3-1: Deregistration request

Information element	Status	Description
V2X UE ID	M	Identifier of the V2X UE
V2X service ID	M	V2X service ID the V2X UE is no longer interested in receiving (e.g. PSID or ITS AID of ETSI ITS DENM, ETSI ITS CAM)

9.2.2.4 Deregistration response

Table 9.2.2.4-1 describes the information flow for VAE server to respond for deregistration request from the VAE client.

Table 9.2.2.4-1: Deregistration response

Information element	Status	Description
Result	M	Result from the VAE server in response to the deregistration request

9.2.3 V2X UE registration for receiving V2X messages

9.2.3.1 General

This subclause describes the procedures for V2X UE to register for receiving V2X messages from the V2X AS. The process is triggered by the V2X UE who is interested in receiving certain V2X messages.

9.2.3.2 Procedure

Pre-condition:

– The VAE client has discovered the VAE server and is aware of the address of the VAE server (e.g. FDQN).

Figure 9.2.3.2-1: Procedure for registering the VAE client at the VAE server

1. The VAE client sends a registration request to the VAE server.

2. The VAE server sends an acknowledgement to the VAE client.

9.2.4 V2X UE deregistration from receiving V2X messages

9.2.4.1 General

This subclause describes the procedures for V2X UE to deregister from receiving V2X messages from the V2X AS. The process is triggered by the V2X UE who is no longer interested in receiving certain V2X messages.

9.2.4.2 Procedure

Pre-condition:

– The VAE client has already registered with the VAE server as described in subclause 9.2.3.

Figure 9.2.4.2-1: Procedure for deregistering the VAE client at the VAE server

1. The VAE client sends a deregistration request to the VAE server.

2. The VAE server sends a deregistration response to the VAE client.