Content for TS 23.286 Word version: 17.3.0
A Detailed V2X application layer functional model
B Functionalities with SA2 dependency
B.1 Service negotiation with underlying 3GPP network
C V2X application enabler related configuration data
C.1 General
C.2 VAE client configuration data
C.3 VAE server configuration data
$ Change history
A Detailed V2X application layer functional model Word‑p. 102
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.
B Functionalities with SA2 dependency Word‑p. 102
B.1 Service negotiation with underlying 3GPP network Word‑p. 102
B.1.1 General Word‑p. 102
The following information flows for service negotiation with the 3GPP network are not supported in TS 23.682.
B.1.2 Information flows Word‑p. 102
B.1.2.1 Supporting information request Word‑p. 102
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.
| 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 Word‑p. 103
Table B.1.2.2-1 describes the information flow for a network to provide a response associated to a supporting information request.
| Information Element | Status | Description |
|---|---|---|
| Result | M | Response from the network if supporting information is supported by the 3GPP network |
B.1.2.3 Void
B.1.2.4 Void
B.1.3 Void
B.1.4 Void
B.2 Void
C (Normative) V2X application enabler related configuration data Word‑p. 103
C.1 General Word‑p. 103
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 Word‑p. 103
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.
| 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 Word‑p. 104
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.
| 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 |
$ Change history Word‑p. 105
