9.1 Usage of SEAL services

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.1.1 Group management service

9.1.1.1 General

The VAE capabilities (VAE client and VAE server) utilize the group management service procedures (e.g. creation, join, leave) of SEAL based on the group configuration information (e.g. group join policy, group leader) provided by the V2X application specific layer. The decisions and corresponding triggers (e.g. group creation, join, leave) for group management are responsibility of the V2X application specific layer and the details of the group management are abstracted by the VAE capabilities. The group management service of SEAL provides support for platooning groups and pre-arranged groups for V2X communications.

9.1.1.2 Information flows

The following information flows of group management service of SEAL as specified in 3GPP TS 23.434 [6] are applicable for the V2X applications:

– Group creation request specified in subclause 10.3.2.1;

– Group creation response specified in subclause 10.3.2.2;

– Group creation notification specified in subclause 10.3.2.3;

– Group information query request specified in subclause 10.3.2.4;

– Group information query response specified in subclause 10.3.2.5;

– Group membership update request specified in subclause 10.3.2.6;

– Group membership update response specified in subclause 10.3.2.7;

– Group membership notification specified in subclause 10.3.2.8;

– Group deletion request specified in subclause 10.3.2.9;

– Group deletion response specified in subclause 10.3.2.10;

– Group deletion notification specified in subclause 10.3.2.11;

– Group information request specified in subclause 10.3.2.12;

– Group information response specified in subclause 10.3.2.13;

– Group information subscribe request specified in subclause 10.3.2.14;

– Group information subscribe response specified in subclause 10.3.2.15;

– Group information notify request specified in subclause 10.3.2.16;

– Group information notify response specified in subclause 10.3.2.17;

– Store group configuration request specified in subclause 10.3.2.18;

– Store group configuration response specified in subclause 10.3.2.19;

– Get group configuration request specified in subclause 10.3.2.20;

– Get group configuration response specified in subclause 10.3.2.21;

– Subscribe group configuration request specified in subclause 10.3.2.22;

– Subscribe group configuration response specified in subclause 10.3.2.23;

– Notify group configuration request specified in subclause 10.3.2.24;

– Notify group configuration response specified in subclause 10.3.2.25;

– Configure VAL group request specified in subclause 10.3.2.26;

– Configure VAL group response specified in subclause 10.3.2.27;

– Group announcement specified in subclause 10.3.2.28;

– Group registration request specified in subclause 10.3.2.29;

– Group registration response specified in subclause 10.3.2.30;

– Identity list notification specified in subclause 10.3.2.31;

– Group de-registration request specified in subclause 10.3.2.32;

– Group de-registration response specified in subclause 10.3.2.33;

– Location-based group creation request specified in clause 10.3.2.34;

The usage of the above information flows are clarified as below:

– The identity list is the list of V2X UE IDs.

— During group creation the identity list contains the list of V2X UE IDs that are part of the group to be created. If the group member list is empty, an empty group is created; and

– The VAL service ID list is the list of V2X service IDs whose service communications are to be enabled on the group.

– Table 9.1.1.2.1-1 describes the VAL service specific information corresponding to the V2X applications.

Table 9.1.1.2.1-1: V2X service specific information for group creation request

Information element	Status	Description
V2X group ID	O	The group ID to be used for the V2X group. If group ID is not provided then the group ID should be allocated by group management server.
Group join policy	O (NOTE)	The policy information to be enforced by the group management server for members joining the group.
Group leader ID	O (NOTE)	The identity information of the V2X user to be used for user controlled group join.
NOTE: If the information elements, identity list specified in 3GPP TS 23.434 [6] is empty and group leader ID is not included, then group join policy information element must be included.

– The VAL group ID is the V2X group ID.

– The identity is the V2X UE ID;

– The VAL server is the VAE server;

– The VAL group configuration information is the V2X group configuration information;

– The VAL group configuration data is the V2X group configuration information;

– The VAL group information reference is the V2X group information reference; and

– The VAL services requested is the V2X service IDs.

9.1.1.3 Procedures

The following procedures of group management service of SEAL as specified in 3GPP TS 23.434 [6] are applicable for the V2X applications:

– Group creation specified in subclause 10.3.3;

— Group creation support is provided for the V2X applications (e.g. platooning and cooperative short distance grouping) to provide a dedicated group for the V2X UEs to communicate with each other. The group creation supports group without any group members to enable group member joining.

– Group information query specified in subclause 10.3.4;

– Group membership specified in subclause 10.3.5;

– Group configuration management specified in subclause 10.3.6;

– Location-based group creation specified in clause 10.3.7;

– Group announcement and join specified in subclause 10.3.8;

– Group member leave specified in clause 10.3.9;

– Temporary groups specified in clause 10.3.10;

9.1.2 Configuration management service

9.1.2.1 General

The VAE capabilities (VAE client and VAE server) utilize configuration management service procedures of SEAL to support V2X services for unicast and multicast delivery over LTE-Uu. The configuration management service of SEAL is utilized for offline configuration (before the V2X UE is receiving the V2X service from the V2X application specific server) and online configuration (during the V2X UE is receiving the V2X service from the V2X application specific server).

9.1.2.2 Information flows

The following information flows of configuration management service are applicable for the V2X applications:

– Get VAL UE configuration request specified in subclause 11.3.2.1 of 3GPP TS 23.434 [6];

– Get VAL UE configuration response specified in subclause 11.3.2.2 of 3GPP TS 23.434 [6];

The usage of the above information flows are clarified as below:

– The VAL UE ID is the V2X UE ID;

– VAL service ID is the V2X service ID; and

– VAL UE configuration data is the V2X UE configuration data. The V2X UE configuration data includes:

— V2X server USD information as specified in 3GPP TS 23.285 [5]; and

— V2X application server address information as specified in 3GPP TS 23.285 [5] and transport port for unicast.

9.1.2.3 Procedures

The following procedures of configuration management service are applicable for the V2X applications:

– VAL UE configuration data specified in subclause 11.3.3 of 3GPP TS 23.434 [6].

— Once the V2X UEs are connected to the serving PLMN, the V2X UE is configured with configuration data (e.g. local service information) for receiving V2X services.

9.1.3 Location management service

9.1.3.1 General

The VAE capabilities (VAE client and VAE server) utilize location management (e.g. network location of UEs) service procedures of SEAL to support V2X services.

9.1.3.2 Information flows

The following information flows of location management service of SEAL as specified in 3GPP TS 23.434 [6] are applicable for the V2X applications:

– Location reporting configuration request specified in subclause 9.3.2.0;

– Location reporting configuration response specified in subclause 9.3.2.1;

– Location information report specified in subclause 9.3.2.2;

– Location information request specified in subclause 9.3.2.3;

– Location reporting trigger specified in subclause 9.3.2.4;

– Location information subscription request specified in subclause 9.3.2.5;

– Location information subscription response specified in subclause 9.3.2.6;

– Location information notification specified in subclause 9.3.2.7;

– Location reporting configuration cancel request specified in clause 9.3.2.8;

– Get UE(s) information request specified in clause 9.3.2.9;

– Get UE(s) information response specified in clause 9.3.2.10;

The usage of the above information flows are clarified as below:

– The identity is the V2X UE ID or V2X group ID;

– The set of identities is the V2X UE ID;

– The identity list or identities list is the list of V2X UE IDs; and

– The VAL server is the VAE server.

9.1.3.3 Procedures

The following procedures of location management service of SEAL as specified in 3GPP TS 23.434 [6] are applicable for the V2X applications:

– Event-triggered location reporting procedure specified in subclause 9.3.3;

– On-demand location reporting procedure specified in subclause 9.3.4;

– Client-triggered or VAL server-triggered location reporting procedure specified in clause 9.3.5;

– Location reporting event triggers configuration cancel specified in subclause 9.3.6;

– Location information subscription procedure specified in subclause 9.3.7;

– Event-trigger location information notification procedure specified in subclause 9.3.8;

– On-demand usage of location information procedure specified in subclause 9.3.9;

– Obtaining UE(s) information at a location specified in clause 9.3.10;

9.1.4 Identity management service

9.1.4.1 General

The VAE capabilities (VAE client and VAE server) utilizes identity management service procedures (e.g. authentication and authorization of UEs) of SEAL to support V2X services.

9.1.4.2 Information flows

The information flows of identity management service are specified in subclause 12.3.2 of 3GPP TS 23.434 [6] and are applicable for the V2X applications.

9.1.4.3 Procedures

The following procedures of identity management service are applicable for the V2X applications:

– General user authentication and authorization for VAL services specified in subclause 12.3.3 of 3GPP TS 23.434 [6].

9.1.5 Key management service

9.1.5.1 General

The VAE capabilities (VAE client and VAE server) utilizes key management service procedures of SEAL to support V2X services.

9.1.5.2 Information flows

The information flows of key management service are specified in subclause 13.3 of 3GPP TS 23.434 [6] and are applicable for the V2X applications.

9.1.5.3 Procedures

The procedures of key management service are specified in subclause 13.3 of 3GPP TS 23.434 [6] and are applicable for the V2X applications.

9.1.6 Network resource management service

9.1.6.1 General

The VAE capabilities (VAE client and VAE server) utilizes network resource management service procedures of SEAL to support V2X services.

9.1.6.2 Information flows

The following information flows of network resource management service of SEAL specified in 3GPP TS 23.434 [6] are applicable for the V2X applications:

– Network resource adaptation request specified in subclause 14.3.2.1;

– Network resource adaptation response specified in subclause 14.3.2.2;

– MBMS bearer announcement specified in subclause 14.3.2.3;

– MBMS listening status report specified in subclause 14.3.2.4;

– MBMS suspension reporting instruction specified in subclause 14.3.2.5;

– Resource request specified in subclause 14.3.2.6;

– Resource response specified in subclause 14.3.2.7;

– Resource modification request specified in subclause 14.3.2.8;

– Resource modification response specified in subclause 14.3.2.9;

– MBMS bearers request specified in subclause 14.3.2.10;

– MBMS bearers response specified in subclause 14.3.2.11; and

– User plane delivery mode specified in subclause 14.3.2.12;

9.1.6.3 Procedures

The following procedures of network resource management service of SEAL specified 3GPP TS 23.434 [6] are applicable for the V2X applications:

– Request for unicast resources at VAL service communication establishment specified in subclause 14.3.3.2.1;

– Request for modification of unicast resources specified in subclause 14.3.3.2.2;

– Network resource adaptation specified in subclause 14.3.3.3.1;

– Request for unicast resources at VAL service communication establishment specified in subclause 14.3.3.3.2;

– Request for modification of unicast resources specified in subclause 14.3.3.3.3;

– Use of pre-established MBMS bearers specified in subclause 14.3.4.2;

– Use of dynamic MBMS bearer establishment specified in subclause 14.3.4.3;

– MBMS bearer announcement over MBMS bearer specified in subclause 14.3.4.4;

– MBMS bearer quality detection specified in subclause 14.3.4.5;

– Service continuity in MBMS scenarios specified in subclause 14.3.4.6;

– MBMS suspension notification specified in subclause 14.3.4.7;

– MBMS bearer event notification specified in subclause 14.3.4.8; and

– Switching between MBMS bearer and unicast bearer specified in subclause 14.3.4.9.