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…

9.21 Support for VRU zone configuration and operation 9.21.1 General 9.21.2 Information flows 9.21.2.1 VRU zone management subscription request 9.21.2.2 VRU zone management subscription response 9.21.2.3 VRU zone info notification 9.21.2.4 Enter/Leave Notification 9.21.3 Procedure on VAL server - triggered VRU zone configuration
...

9.21 Support for VRU zone configuration and operation |R18| p. 97

9.21.1 General p. 97

This capability supports the configuration and provisioning of the VRU high risk zone at the VAE layer based on a request from the V2X application specific server (VASS).

9.21.2 Information flows p. 97

9.21.2.1 VRU zone management subscription request p. 97

Table 9.21.2.1-1 describes information elements for the VRU zone management subscription request from the VASS to the VAE server.

Table 9.21.2.1-1: VRU zone management subscription request

Information element	Status	Description
Requestor ID	M	The identifier of the service requestor (VASS, VAL server, App ID)
VRU zone ID	O	The identifier of the VRU zone which may be provided by the requestor.
VRU zone information	M	This information identifies, based on the VRUP scenario, which type of UEs (V2X UEs, pedestrian UEs) are to be considered. Also, whether it is a static or dynamic zone can be identified.
VRU application requirements	M	This includes requirements include the types of supported messages and requirements (e.g. requirements for VAM messages), and application QoS requirement dedicated for the VRU zone (e.g. URLLC like).
List of VAL UE IDs	O	The identifiers of the VAL UEs for which the VRU zone is applicable
Area of Interest	O	The geographical or service area for which the subscription request applies
Time validity	O	The time validity of the request

9.21.2.2 VRU zone management subscription response p. 97

Table 9.21.2.2-1 describes information elements for the VRU zone management subscription response from the VAE server to VASS.

Table 9.21.2.2-1: VRU zone management subscription response

Information element	Status	Description
Result	M	The result of the VRU zone management subscription request (positive or negative acknowledgement)

9.21.2.3 VRU zone info notification p. 97

Table 9.21.2.3-1 describes information elements for the VRU zone info notification from the VAE server to the VAE clients.

Table 9.21.2.3-1: VRU zone info notification

Information element	Status	Description
VRU zone ID	M	The identifier of the VRU zone
VRU zone information	M	This information identifies based on the VRUP scenario, which type of UEs (V2X UEs, pedestrians) are to be considered. Also, whether it is a static or dynamic zone.
VRU zone area	M	The geographical (coordinates) or topological area for the zone (cell IDs, TAs)
QoS requirements	M	The application QoS requirements for the services within the zone
VRU zone configuration parameters	M	These parameters include: The list of value-add VAE services required within the zone (e.g. location tracking, V2X message bundling), the supported transmission modes (unicast, groupcast, broadcast) within the applications within the zone, the allowed interface selection within the zone (Uu, PC5), the use of application relaying or not
VRU zone adaptation assistance info	O	If the VRU zone is dynamic, this IE provides assistance info on the configuration adaptation triggers or to provide the planning (e.g. based on a school bus route) to allow the network to adapt the configuration.

9.21.2.4 Enter/Leave Notification p. 98

Table 9.21.2.4-1 describes information elements for the Enter/Leave Notification from the VAE server to the VASS or the VAE client(s) within the zone.

Table 9.21.2.4-1: Enter/Leave Notification

Information element	Status	Description
VAL UE ID	M (NOTE)	The identity of the UE of interest (GPSI, or external ID)
VAL group ID	M (NOTE)	The group UE identity (if this applies to a group of UEs).
VRU zone ID	M	The identifier of the VRU zone
VRU zone information	M	This information identifies based on the VRUP scenario, which type of UEs (V2X UEs, pedestrians) are to be considered. Also, whether it is a static or dynamic zone.
Enter/Leave timing info	M	The timing info for the UE enter / leave the zone. This includes for entering a start time of VRUP and an expected duration, and for leaving an expected leave time (if the UE is approaching the VRU zone boundaries)
UE/group mobility info	O	The expected mobility/speed/direction of the UE or group of interest
NOTE: One of these shall be present.

9.21.3 Procedure on VAL server - triggered VRU zone configuration p. 98

Figure 9.21.3-1 illustrates the procedure where the VAE server configures the VRU zone based on application requirement; and supports the run-time operation based on an expected UE entrance to the zone.

Pre-conditions:

V2X application specific server or client has subscribed to VAE layer to provide support for V2P communication.

Copy of original 3GPP image for 3GPP TS 23.286, Fig. 9.21.3-1: VAL server - triggered VRU zone configuration

Figure 9.21.3-1: VAL server - triggered VRU zone configuration
(⇒ copy of original 3GPP image)

Step 1.

The V2X application specific server sends a subscription request to manage the configuration of a new high-risk area zone and requires the VAE server support to translate it to a network-related zone configuration and provisioning to the UEs within the requested area.

Step 2.

The VAE server processes the request and stores the subscription. The processing includes the translation of the zone requirement of step 1 and determines a set of network-related zone parameters which indicates the configuration parameters.

Step 3.

The VAE sever sends a VRU zone management subscription response to VASS.

Step 4.

The VAE server initiates the SEAL LMS service for location tracking both for static location and dynamically changing location for all UEs within the VRU zone area. VAE server obtains and initiates tracking the V2X UEs location from the location management server 1 as specified in clause 9.3.12 of TS 23.434 or, for static area, it obtains location area monitoring information based on clause 9.3.10 of TS 23.434.

Step 5.

The VAE server sends a notification message including the VRU zone configuration parameters. Parameters can be based on the parameters provided in step 2. This configuration will be provided to the V2X-UEs (and pedestrians) within the area that will be covered by the VRU zone.

Step 6.

The VAE server keeps monitoring the VRU zone area based on monitoring SEAL LMS events. This includes events on whether a UE (e.g. UE1) is moving in or out a target area of interest.

The VAE server translates the UE1 mobility event to an expected entrance to a VRU high risk zone, and based on the configuration of the zone, it identifies whether to generate and send a notification to the VASS on the expected entrance / leave of UE1.

Step 7.

The VAE server alerts the VASS that the UE1 is expected to move to the VRU zone area in a given time horizon and provides also information on its mobility as well as the UE1 capabilities (e.g. VRU capable).

Step 8.

The VAE server may also alert the VAE client (if deployed at the UE1) that it is expected to enter the VRU zone and requests the confirmation for allowing the push of VRU messages within the zone.