ETSI GS MEC 030 V2.1.1 (2020-04)

Multi-access Edge Computing (MEC); V2X Information Service API

DGS/MEC-0030V2XAPI

General Information

• Status: Not Published
• Technical Committee: MEC - Multi-access Edge Computing
• Current Stage: 12 - Completion
• Due Date: 18-May-2020
• Completion Date: 30-Apr-2020

Standards Content (Sample)

ETSI GS MEC 030 V2.1.1 (2020-04)






GROUP SPECIFICATION
Multi-access Edge Computing (MEC);
V2X Information Service API
Disclaimer
The present document has been produced and approved by the Multi-access Edge Computing (MEC) ETSI Industry
Specification Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

---------------------- Page: 1 ----------------------
2 ETSI GS MEC 030 V2.1.1 (2020-04)



Reference
DGS/MEC-0030V2XAPI
Keywords
API, MEC, service, V2X

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI GS MEC 030 V2.1.1 (2020-04)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 9
4 Overview . 9
5 Description of the service (informative). 10
5.1 Reference scenarios for the VIS service . 10
5.2 Multi-operator scenarios and V2X services . 10
5.3 V2X service continuity in multi-operator operation scenarios . 11
5.3.1 Introduction. 11
5.4 VIS functionalitie s . 12
5.4.1 Overview . 12
5.4.2 Communication between V2X Control Function (3GPP) and VIS (MEC) . 13
5.4.3 Inter-MEC system V2X application communication . 14
5.4.4 Inter-MEC system service exposure . 14
5.4.5 The VIS and its role in producing journey-specific QoS notifications . 14
5.5 Sequence diagrams . 15
5.5.1 Sending a request for provisioning information for V2X communication over Uu unicast . 15
5.5.2 Sending a request for provisioning information for V2X communication over Uu MBMS . 16
5.5.3 Sending a request for provisioning information for V2X communication over PC5 . 16
5.5.4 Sending a request for journey-specific QoS predictions . 17
5.5.5 REST based subscribe-notify model . 17
5.5.5.1 Subscribing to event notifications . 17
5.5.5.2 Receiving notification on expiry of V2X information event subscription . 18
5.5.5.3 Updating subscription for V2X information event notifications . 19
5.5.5.4 Unsubscribing from V2X information event notifications . 19
5.5.6 Receiving V2X information event notifications about the provisioning information changes for V2X
communication over Uu unicast . 20
5.5.7 Receiving V2X information event notifications about the provisioning information changes for V2X
communication over Uu MBMS . 21
5.5.8 Receiving V2X information event notifications about the provisioning information changes for V2X
communication over PC5 . 21
5.5.9 V2X message interoperability. 22
5.5.9.1 V2X message subscribe . 22
5.5.9.2 V2X message publication . 22
5.5.9.3 V2X message notification . 23
5.6 Conclusions on VIS . 23
6 Data model . 23
6.1 Introduction . 23
6.2 Resource data types . 24
6.2.1 Introduction. 24
6.2.2 Type: UuUnicastProvisioningInfo . 24
6.2.3 Type: UuMbmsProvisioningInfo . 24
6.2.4 Type: Pc5ProvisioningInfo . 25
6.2.5 Type: PredictedQos. 25
6.2.6 Type: V2xMsgPublication . 26
ETSI

---------------------- Page: 3 ----------------------
4 ETSI GS MEC 030 V2.1.1 (2020-04)
6.3 Subscription data types . 26
6.3.1 Introduction. 26
6.3.2 Type: ProvChgUuUniSubscription . 26
6.3.3 Type: ProvChgUuMbmsSubscription . 27
6.3.4 Type: ProvChgPc5Subscription . 27
6.3.5 Type: V2xMsgSubscription . 28
6.3.6 Type: SubscriptionLinkList . 29
6.4 Notifications data types . 29
6.4.1 Introduction. 29
6.4.2 Type: ProvChgUuUniNotification . 29
6.4.3 Type: ProvChgUuMbmsNotification . 29
6.4.4 Type: ProvChgPc5Notification . 30
6.4.5 Type: V2xMsgNotification . 30
6.5 Referenced structured data types . 31
6.5.1 Introduction. 31
6.5.2 Type: TimeStamp . 31
6.5.3 Type: LocationInfo . 31
6.5.4 Type: Plmn. 32
6.5.5 Type: Ecgi . 32
6.5.6 Type: FddInfo . 32
6.5.7 Type: TddInfo . 32
6.5.8 Type: V2xApplicationServer . 33
6.5.9 Type: UuUniNeighbourCellInfo . 33
6.5.10 Type: V2xServerUsd . 33
6.5.11 Type: UuMbmsNeighbourCellInfo . 33
6.5.12 Type: Pc5NeighbourCellInfo . 34
6.6 Referenced simple data types and enumerations . 34
6.6.1 Introduction. 34
6.6.2 Type: CellId . 34
6.6.3 Type: Earfcn . 34
6.6.4 Type: TransmissionBandwidth . 35
7 API definition . 35
7.1 Introduction . 35
7.2 Global definitions and resource structure . 35
7.3 Resource: uu_unicast_provisioning_info . 37
7.3.1 Description . 37
7.3.2 Resource definition . 37
7.3.3 Resource methods . 37
7.3.3.1 GET . 37
7.3.3.2 PUT . 38
7.3.3.3 PATCH . 38
7.3.3.4 POST . 38
7.3.3.5 DELETE . 38
7.4 Resource: uu_mbms_provisioning_info . 39
7.4.1 Description . 39
7.4.2 Resource definition . 39
7.4.3 Resource methods . 39
7.4.3.1 GET . 39
7.4.3.2 PUT . 40
7.4.3.3 PATCH . 40
7.4.3.4 POST . 40
7.4.3.5 DELETE . 40
7.5 Resource: pc5_provisioning_info . 41
7.5.1 Description . 41
7.5.2 Resource definition . 41
7.5.3 Resource methods . 41
7.5.3.1 GET . 41
7.5.3.2 PUT . 42
7.5.3.3 PATCH . 42
7.5.3.4 POST . 42
7.5.3.5 DELETE . 42
ETSI

---------------------- Page: 4 ----------------------
5 ETSI GS MEC 030 V2.1.1 (2020-04)
7.6 Resource: provide_predicted_qos . 43
7.6.1 Description . 43
7.6.2 Resource definition . 43
7.6.3 Resource methods . 43
7.6.3.1 GET . 43
7.6.3.2 PUT . 43
7.6.3.3 PATCH . 43
7.6.3.4 POST . 43
7.6.3.5 DELETE . 44
7.7 Resource: publish_v2x_message . 44
7.7.1 Description . 44
7.7.2 Resource definition . 44
7.7.3 Resource methods . 45
7.7.3.1 GET . 45
7.7.3.2 PUT . 45
7.7.3.3 PATCH . 45
7.7.3.4 POST . 45
7.7.3.5 DELETE . 46
7.8 Resource: subscriptions . 46
7.8.1 Description . 46
7.8.2 Resource definition . 46
7.8.3 Resource methods . 47
7.8.3.1 GET . 47
7.8.3.2 PUT . 48
7.8.3.3 PATCH . 48
7.8.3.4 POST . 48
7.8.3.5 DELETE . 50
7.9 Resource: existing subscription . 50
7.9.1 Description . 50
7.9.2 Resource definition . 50
7.9.3 Resource methods . 50
7.9.3.1 GET . 50
7.9.3.2 PUT . 51
7.9.3.3 PATCH . 53
7.9.3.4 POST . 53
7.9.3.5 DELETE . 53
Annex A (informative): Mapping of permissions for RESTful API and topic based alternative
transport . 55
A.1 Overview . 55
A.2 Mapping of permissions - RESTful and topic based alternative transport . 55
Annex B (informative): Complementary material for API utilization . 57
Annex C (informative): Radio access network scenario options for V2X communication . 58
History . 59


ETSI

---------------------- Page: 5 ----------------------
6 ETSI GS MEC 030 V2.1.1 (2020-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Multi-access Edge
Computing (MEC).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

---------------------- Page: 6 ----------------------
7 ETSI GS MEC 030 V2.1.1 (2020-04)
1 Scope
The present document focuses on a MEC Vehicular-to-Everything (V2X) Information Service (VIS), in order to
facilitate V2X interoperability in a multi-vendor, multi-network and multi-access environment. It describes the V2X-
related information
...