Content for TS 23.286 Word version: 19.0.0

0… 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… A…

A Detailed V2X application layer functional model p. 114

Figure A-1 illustrates the detailed V2X application layer functional model including all the functional entities of the VAE layer and the functional entities of the SEAL as specified in TS 23.434.

Reproduction of 3GPP TS 23.286, Fig. A-1: Detailed V2X application layer functional model

Figure A-1: Detailed V2X application layer functional model

B Functionalities with SA2 dependency p. 115

B.1 Service negotiation with underlying 3GPP network p. 115

B.1.1 General p. 115

The following information flows for service negotiation with the 3GPP network are not supported in TS 23.682.

B.1.2 Information flows p. 115

B.1.2.1 Supporting information request p. 115

Table B.1.2.1-1 describes the information flow for a VAE server to provide the network with supporting information for service negotitation with the 3GPP network.

Table B.1.2.1-1: Supporting information request

Information element	Status	Description
Supporting Information	O	Indicating supporting information by the VAE server to increase the network awareness related to the service. Example of supporting information is planned/expected UE trajectory, which can be provided in the form of waypoints (GPS coordinates) and associated timestamps.

B.1.2.2 Supporting information response p. 116

Table B.1.2.2-1 describes the information flow for a network to provide a response associated to a supporting information request.

Table B.1.2.2-1: Supporting information response

Information element	Status	Description
Result	M	Response from the network if supporting information is supported by the 3GPP network.

C (Normative) V2X application enabler related configuration data p. 117

C.1 General p. 117

This Annex provides information about the static data needed for configuration for the V2X application enabler service, which belongs to one of the following categories:

VAE client configuration data (see subclause C.2); and
VAE server configuration data (see subclause C.3).

C.2 VAE client configuration data p. 117

The procedure of VAE client related configuration are specified in TS 23.434. Data in Table C.2-1 has to be known by the VAE client.

Data in Table C.2-1 can be configured using the CM-UU reference point as specified in TS 23.434.

Table C.2-1: VAE client related configuration data

Reference	Parameter description
Clause 8.1 and clause 9.1.2.2	V2X user/UE identity.
Clause 9.1.2.2	V2X service ID.
Clause 9.1.2.2	V2X server USD.
Clause 9.2.3 and clause 9.1.2.3	IP address and port information of the initial VAE server serving the VAE client.
Clause 9.3.3	GEO ID information.

C.3 VAE server configuration data p. 117

The procedure of VAE server related configuration are specified in TS 23.434. Data in Table C.3-1 has to be known by the VAE server.

Data in Table C.3-1 can be configured using the CM-S reference point as specified in TS 23.434.

Table C.3-1: VAE server related configuration data

Reference	Parameter description
Clause 8.1	List of V2X user identities.
Clause 9.7.4.2	IP address of the EPS entity SCEF.
Clause 9.10.3.2	List of IP addresses of the neighboring VAE servers.
Clause 9.11.3.2	IP address of the NRM server.
Clause 9.12.3.2	Unique pool of ProSe Layer-2 Group IDs.
Clause 9.5.2	BM-SC information.

D (Normative) Utilization of edge computing |R18| p. 119

The application architecture for supporting edge applications are specified in TS 23.558. The V2X application layer functional model as specified in clause 6 may be deployed in edge computing environment.

Figure D-1 illustrates a V2X application layer deployment in edge computing environments.

Reproduction of 3GPP TS 23.286, Fig. D-1: Utilization of edge computing

Figure D-1: Utilization of edge computing

Figure D-1 illustrates the utilization of edge computing for V2X application layer based on edge enabler layer specified in TS 23.558.

At UE side, V2X Application Specific client(s) and VAE client interact with the Edge Enabler Client (EEC) via EDGE-5 reference point. In an Edge Data Network (EDN), V2X Application Specific Server and VAE server assume the role of EAS (Edge Application Server) and interacts with the Edge Enabler Server (EES) via EDGE-3 reference point, for instance, to register its profile into the EES. Upon service provisioning, the EEC interacts with the EES via EDGE-1 reference point, for instance, to discover V2X Application Specific Server(s) and VAE Server and further the EEC provides the discovered V2X Application Specific Server(s) and VAE server to the V2X Application Specific client and VAE client respectively. The interactions between the entities and 5GS are not shown for the sake of simplicity.

In an EDN, there could be several EES(s) provided by the same or different ECSP. The V2X application specific server(s), VAE server(s) and SEAL servers (e.g. GMS, NRMS, ADAES) shall be able to discover and register into an appropriate EES. If CAPIF is used, this can be done by utilizing the AEF serving area and/or the AEF location as described in TS 23.222; otherwise, local configuration of the EES endpoint may be used.

The services provided by EES over EDGE-3 are not re-exposed by the VAE server or SEAL servers to the V2X application specific server but are directly consumed by the SEAL servers, VAE server and V2X application specific server(s).