Content for TS 23.286 Word version: 18.0.0
9.2 V2X UE registration
9.2.1 General
9.2.2 Information flows
9.2.3 V2X UE registration for receiving V2X messages
9.2.4 V2X UE deregistration from receiving V2X messages
9.3 Application level location tracking
9.3.1 General
9.3.2 Information flows
9.3.3 Tracking geographical location at the VAE server
...
...
9.2 V2X UE registration p. 35
9.2.1 General p. 35
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 p. 35
9.2.2.1 Registration request p. 35
Table 9.2.2.1-1 describes the information flow for a VAE client to register for specific V2X messages at the VAE server.
| 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 p. 35
Table 9.2.2.2-1 describes the information flow for VAE server to respond for registration request from the VAE client.
| 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 p. 36
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.
| 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 p. 36
Table 9.2.2.4-1 describes the information flow for VAE server to respond for deregistration request from the VAE client.
| 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 p. 36
9.2.3.1 General p. 36
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 p. 36
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
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
9.2.4 V2X UE deregistration from receiving V2X messages p. 36
9.2.4.1 General p. 36
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 p. 37
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
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
9.3 Application level location tracking p. 37
9.3.1 General p. 37
The VAE capabilities provide support for location tracking of the VAE client(s) as per the geographical information provided by the V2X application specific layer.
9.3.2 Information flows p. 37
9.3.2.1 Subscription request p. 37
Table 9.3.2.1-1 describes the information flow for a VAE client to subscribe to a geographical area at the VAE server.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | M | Identifier of the V2X UE |
| GEO ID | M | Geographical area identifier (e.g. URI, tile identifier, geo-fence tile identifier) |
9.3.2.2 Subscription response p. 37
Table 9.3.2.2-1 describes the information flow for VAE server to respond for geographical area subscription request from the VAE client.
| Information Element | Status | Description |
|---|---|---|
| Result | M | Result from the VAE server in response to subscription request indicating success or failure |
9.3.2.3 Unsubscription request p. 37
Table 9.3.2.3-1 describes the information flow for a VAE client to unsubscribe from a geographical area at the VAE server.
| Information Element | Status | Description |
|---|---|---|
| V2X UE ID | M | Identifier of the V2X UE |
| GEO ID | M | Geographical area identifier (e.g. URI, tile identifier, geo-fence tile identifier) |
9.3.2.4 Unsubscription response p. 38
Table 9.3.2.4-1 describes the information flow for VAE server to respond for geographical area unsubscription request from the VAE client.
| Information Element | Status | Description |
|---|---|---|
| Result | M | Result from the VAE server in response to unsubscription request |
9.3.3 Tracking geographical location at the VAE server p. 38
9.3.3.1 General p. 38
This subclause describes the procedures for tracking V2X UEs geographical location at the VAE server. The V2X UE provides geographical area information to the VAE server upon moving to a new geographical area. This information is used by the VAE server to create and update the mapping between the geographical location and the identification of the V2X UE.
9.3.3.2 Procedure p. 38
Pre-conditions:
- The VAE client is provisioned with GEO ID information;
- The VAE client has registered with the VAE server as described in subclause 9.2.3; and
- The VAE client has subscribed to a certain geographical area identifier (GEO ID A) in order to receive V2X messages for this area.
Figure 9.3.3.2-1: Procedure for tracking the client geographical area at the VAE server
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Step 1.
Upon entering a new geographical area, the client subscribes to the geographic area Geo ID B.
Step 2.
The VAE server sends a subscription response to the VAE client.
Step 3.
The VAE server stores the new geographical area information GEO ID B with the client identification information V2X UE ID.
Step 4.
The client unsubscribes from the old geographical area GEO ID A.
Step 5.
The VAE server sends an unsubscription response to the VAE client.
Step 6.
The VAE server removes the old geographical area information GEO ID A associated with the client identification information V2X UE ID.
