Tech-invite  3GPPspecs  RELs  Glossaries  SIP
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TS 23.286  SA6 ★
Application Layer support for V2X Services –
Functional Architecture and Information Flows

3GPP‑Page   full‑ToC
use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V16.2.0 (Wzip)  2019/12  62 p.
WI Acronym:  V2XAPP
Rapporteur:  Mr. Amogh, Niranth  Huawei Technologies Co. Ltd.
The present document specifies the functional architecture, procedures and information flows for V2X application enabler layer. This specification includes the capabilities of the application layer support for V2X services that are necessary to ensure efficient use and deployment of V2X services over 3GPP systems. The VAE capabilities applies to EPS.

full Table of Contents for  TS 23.286  Word version:   16.2.0

Here   Top
1 Scope  2 References  3 Definitions and abbreviations  4 Architectural requirements  5 Involved business relationships  6 Functional model  7 Deployment models  8 Identities  9 Procedures and information flows  9.1 Usage of SEAL services  9.2 V2X UE registration  9.3 Application level location tracking  9.4 V2X message delivery  9.5 File Distribution  9.6 Provisioning 3GPP system information by VAE server  9.7 Network monitoring by the V2X UE  9.8 Switching modes of operations for V2V communications  9.9 V2X service discovery  9.10 V2X service continuity  9.11 V2X application resource management  9.12 Dynamic group management  9.13 Network situation and QoS monitoring and reporting  9.14 Service negotiation with underlying 3GPP network  10 VAE layer APIs  A Detailed V2X application layer functional model  B Functionalities with SA2 dependency  C [N] V2X application enabler related configuration data  C.1 General  C.2 VAE client configuration data  C.3 VAE server configuration data  D Change history 

 

1  Scope  Word-p. 9
2  References
3  Definitions and abbreviations  Word-p. 10
3.1  Definitions
3.2  Abbreviations
4  Architectural requirements
4.1  General
4.1.1  Description
4.1.2  Requirements  Word-p. 11
4.2  V2X group communication
4.2.1  Description  Up
4.2.2  Requirements
4.3  V2X dynamic groups
4.3.1  Description
4.3.2  Requirements
4.4  File distribution capability  Word-p. 12
4.4.1  Description
4.4.2  Requirements
4.5  V2X application message distribution
4.5.1  Description
4.5.2  Requirements  Up
4.6  Service continuity
4.6.1  Description
4.6.2  Requirements
5  Involved business relationships
6  Functional model  Word-p. 13
6.1  General
6.2  Functional model description
6.3  Functional entities description  Word-p. 15
6.3.1  General
6.3.2  V2X application specific client  Word-p. 16
6.3.3  V2X application specific server
6.3.4  VAE client
6.3.5  VAE server
6.3.6  SEAL client  Word-p. 17
6.3.7  SEAL server
6.4  Reference points description
6.4.1  General
6.4.2  V1-AE
6.4.3  V1-APP
6.4.4  V5-AE  Word-p. 18
6.4.5  V5-APP
6.4.6  Vs
6.4.7  Vc
6.4.8  SEAL-C
6.4.9  SEAL-S
6.4.10  SEAL-PC5
6.4.11  SEAL-UU  Word-p. 19
6.4.12  VAE-E
6.5  External reference points
6.5.1  General  Up
6.5.2  V2
6.5.3  Rx
6.5.4  MB2-C
6.5.5  MB2-U
6.5.6  xMB-C  Word-p. 20
6.5.7  xMB-U
6.5.8  T8
7  Deployment models
7.1  General
7.2  Deployment of VAE server  Up
7.2.1  Centralized deployments
7.2.2  Distributed deployment  Word-p. 22
8  Identities  Word-p. 24
8.1  V2X user identity (V2X user ID)
8.2  V2X UE identity (V2X UE ID)  Word-p. 25
8.3  V2X service identity (V2X service ID)
8.4  V2X group identity (V2X group ID)
8.5  Geographical area identity (GEO ID)
9  Procedures and information flows
9.1  Usage of SEAL services  Up
9.1.1  Group management service
9.1.1.1  General
9.1.1.2  Information flows
9.1.1.3  Procedures  Word-p. 27
9.1.2  Configuration management service
9.1.2.1  General
9.1.2.2  Information flows
9.1.2.3  Procedures  Word-p. 28
9.1.3  Location management service
9.1.3.1  General  Up
9.1.3.2  Information flows
9.1.3.3  Procedures
9.1.4  Identity management service  Word-p. 29
9.1.4.1  General
9.1.4.2  Information flows
9.1.4.3  Procedures
9.1.5  Key management service
9.1.5.1  General
9.1.5.2  Information flows
9.1.5.3  Procedures  Up
9.1.6  Network resource management service
9.1.6.1  General
9.1.6.2  Information flows  Word-p. 30
9.1.6.3  Procedures
9.2  V2X UE registration
9.2.1  General
9.2.2  Information flows
9.2.2.1  Registration request
9.2.2.2  Registration response  Word-p. 31
9.2.2.3  Deregistration request  Up
9.2.2.4  Deregistration response
9.2.3  V2X UE registration for receiving V2X messages
9.2.3.1  General
9.2.3.2  Procedure
9.2.4  V2X UE deregistration from receiving V2X messages  Word-p. 32
9.2.4.1  General
9.2.4.2  Procedure
9.3  Application level location tracking
9.3.1  General
9.3.2  Information flows  Up
9.3.2.1  Subscription request
9.3.2.2  Subscription response
9.3.2.3  Unsubscription request  Word-p. 33
9.3.2.4  Unsubscription response
9.3.3  Tracking geographical location at the VAE server
9.3.3.1  General
9.3.3.2  Procedure
9.4  V2X message delivery  Word-p. 34
9.4.1  General
9.4.2  Information flows  Up
9.4.2.1  V2X message
9.4.2.2  V2X message reception report  Word-p. 35
9.4.2.3  V2X group message
9.4.2.4  V2X uplink message
9.4.2.5  V2X uplink message reception report
9.4.2.6  Subscribe V2X message delivery request  Word-p. 36
9.4.2.7  Subscribe V2X message delivery response
9.4.2.8  Unsubscribe V2X message delivery request
9.4.2.9  Unsubscribe V2X message delivery response
9.4.3  Message delivery to target geographical areas from the VAE server  Word-p. 37
9.4.3.1  General
9.4.3.2  Procedure
9.4.4  V2X group message distribution
9.4.4.1  General
9.4.4.2  Procedure
9.4.5  Uplink V2X message delivery  Word-p. 38
9.4.5.1  General
9.4.5.2  Procedure for uplink message delivery
9.4.6  Procedure for subscription to message delivery  Word-p. 39
9.5  File Distribution  Up
9.5.1  General
9.5.2  Use of MBMS "files" session type
9.6  Provisioning 3GPP system information by VAE server  Word-p. 40
9.6.1  General
9.6.2  Information flows
9.6.2.1  V2X USD announcement
9.6.2.2  Set PC5 parameters request
9.6.2.3  Set PC5 parameters response
9.6.3  V2X USD provisioning  Word-p. 41
9.6.3.1  General  Up
9.6.3.2  Procedure
9.6.4  PC5 parameters provisioning  Word-p. 42
9.6.4.1  General
9.6.4.2  Procedure
9.7  Network monitoring by the V2X UE
9.7.1  General
9.7.2  Information flows
9.7.2.1  Network monitoring information subscription request
9.7.2.2  Network monitoring information subscription response  Word-p. 43
9.7.2.3  Network monitoring information notification  Up
9.7.3  V2X UE subscription for network monitoring information
9.7.3.1  General
9.7.3.2  Procedure
9.7.4  Notifications for network monitoring information  Word-p. 44
9.7.4.1  General
9.7.4.2  Procedure
9.8  Switching modes of operations for V2V communications  Word-p. 45
9.9  V2X service discovery
9.9.1  General
9.9.2  Information flows  Up
9.9.2.1  Get V2X UE service discovery request
9.9.2.2  Get V2X UE service discovery response  Word-p. 46
9.9.3  V2X UE service discovery
9.9.3.1  General
9.9.3.2  Procedure
9.10  V2X service continuity  Word-p. 47
9.10.1  General
9.10.2  Information flows
9.10.2.1  Service continuity request
9.10.2.2  Service continuity response  Up
9.10.2.3  Local service information request
9.10.2.4  Local service information response
9.10.3  V2X service continuity management  Word-p. 48
9.10.3.1  General
9.10.3.2  Procedure
9.10.4  Dynamic local service information
9.10.4.1  General
9.10.4.2  Procedure  Word-p. 49
9.11  V2X application resource management
9.11.1  General  Up
9.11.2  Information flows  Word-p. 50
9.11.2.1  V2X application requirement request
9.11.2.2  V2X application requirement response
9.11.2.3  V2X application requirement notification
9.11.3  V2X application resource adaptation
9.11.3.1  General
9.11.3.2  Procedure
9.12  Dynamic group management  Word-p. 51
9.12.1  General
9.12.2  Information flows  Up
9.12.2.1  Push Layer-2 group ID mapping
9.12.2.2  Configure dynamic group  Word-p. 52
9.12.3  On-network dynamic group creation
9.12.3.1  General
9.12.3.2  Procedure
9.12.4  Off-network dynamic group creation  Word-p. 53
9.12.4.1  General
9.12.4.2  Procedure
9.13  Network situation and QoS monitoring and reporting  Word-p. 54
9.13.1  General  Up
9.13.2  Information flows
9.13.2.1  Monitoring request
9.13.2.2  Monitoring response
9.13.2.3  Monitoring report
9.13.3  Procedure
9.14  Service negotiation with underlying 3GPP network
9.14.1  General
9.14.2  Information flows  Word-p. 55
9.14.2.1  On-demand QoS request
9.14.2.2  On-demand QoS response  Up
9.14.2.3  Background data transfer request
9.14.2.4  Background data transfer response
9.14.2.5  Network Status Request
9.14.2.6  Network Status Response
9.14.2.7  Network Status Report
9.14.2.8  Network Status Acknowledgment
9.14.3  Communication of service requirements from the VAE server
9.14.4  Notification generation by the SCEF function
10  VAE layer APIs  Word-p. 56
10.1  General  Up
10.2  VAE server APIs
10.2.1  General
10.2.2  VAE_MessageDelivery API
10.2.2.1  General
10.2.2.2  Deliver_DL_Message operation
10.2.2.3  Deliver_UL_Message operation  Word-p. 57
10.2.2.4  V2X_MessageDelivery_Subscribe operation
10.2.2.5  V2X_MessageDelivery_Unsubscribe operation
10.2.3  VAE_FileDistribution API
10.2.3.1  General  Up
10.2.3.2  Distribute_File operation
10.2.4  VAE_ApplicationRequirement API  Word-p. 58
10.2.4.1  General
10.2.4.2  Reserve_NetworkResource operation
10.2.5  VAE_DynamicGroup API
10.2.5.1  General
10.2.5.2  Configure_DynamicGroup operation
A  Detailed V2X application layer functional model
B  Functionalities with SA2 dependency  Word-p. 59
B.1  Service negotiation with underlying 3GPP network  Up
B.1.1  General
B.1.2  Information flows
B.1.2.1  Supporting information request
B.1.2.2  Supporting information response  Word-p. 60
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
C.1  General
C.2  VAE client configuration data
C.3  VAE server configuration data  Word-p. 61
D  Change history  Word-p. 62

Up   Top