ETSI GS MEC 013 V2.2.1 (2022-01)

Multi-access Edge Computing (MEC); Location API

RGS/MEC-0013v221LocationApi

General Information

• Status: Not Published
• Technical Committee: MEC - Multi-access Edge Computing
• Current Stage: 12 - Completion
• Due Date: 08-Feb-2022
• Completion Date: 28-Jan-2022

Standards Content (Sample)

GROUP SPECIFICATION
Multi-access Edge Computing (MEC);
Location 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.

2 ETSI GS MEC 013 V2.2.1 (2022-01)

Reference
RGS/MEC-0013v221LocationApi
Keywords
API, location, MEC, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

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
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2022.
All rights reserved.
ETSI
3 ETSI GS MEC 013 V2.2.1 (2022-01)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 8
4 Overview . 8
5 Description of the service (informative). 8
5.1 Introduction . 8
5.2 Relation with OMA APIs . 9
5.2.1 Relation with OMA API for Zonal Presence . 9
5.2.2 Relation with OMA API for Terminal Location . 9
5.3 Sequence diagrams . 9
5.3.1 Introduction. 9
5.3.2 UE Location Lookup . 10
5.3.3 UE Information Lookup . 10
5.3.4 UE Location Subscribe . 11
5.3.5 UE Information Subscribe . 11
5.3.6 Subscribe Cancellation . 12
5.3.7 Radio Node Location Lookup . 12
5.3.8 UE Tracking Subscribe . 13
5.3.9 UE Distance Lookup . 13
5.3.10 UE Distance Subscribe . 14
5.3.11 UE Area Subscribe. 15
6 Data Model . 15
6.1 Introduction . 15
6.2 Resource data types . 15
6.2.1 Zonal presence data types . 15
6.2.1A Terminal location data types . 16
6.2.2 Type: UserInfo . 16
6.3 Subscription data types . 17
6.3.1 Zonal presence data types . 17
6.3.2 Terminal Location data types. 17
6.3.3 Type: NotificationSubscriptionList . 17
6.4 Notifications data types . 18
6.4.1 Zonal presence data types . 18
6.4.2 Terminal location data types . 18
6.5 Referenced structured data types . 18
6.5.1 Introduction. 18
6.5.2 Type: TimeStamp . 18
6.5.3 Type: LocationInfo . 19
6.6 Mapping of Identifiers . 20
6.6.1 accessPointId . 20
6.6.2 userId . 20
7 API definition . 20
7.1 Introduction . 20
7.2 Global definitions and relation with OMA resources . 20
ETSI
4 ETSI GS MEC 013 V2.2.1 (2022-01)
7.3 Mapping of services to API functions . 22
7.3.1 Introduction. 22
7.3.2 UE Location Lookup . 22
7.3.2.1 Definition . 22
7.3.2.2 Example: Two steps method to retrieve the geographical coordinates of an access point a specific
user is connected to (informative) . 23
7.3.3 UE Information Lookup . 24
7.3.3.1 Definition . 24
7.3.3.2 Example: Retrieve UE Information for all the users (informative) . 24
7.3.3.3 Example: Retrieve UE Information for the users in a zone (informative). 25
7.3.3.4 Example: Retrieve UE Information for the users in an access point of a zone (informative) . 26
7.3.4 UE Location Subscribe . 26
7.3.4.1 Definition . 26
7.3.4.2 Example: Create a UE Location subscription (informative) . 27
7.3.4.3 Example: Client notification about UE Location change (informative) . 27
7.3.5 UE Information Subscribe . 28
7.3.5.1 Definition . 28
7.3.5.2 Example: Create a UE Information subscription (informative) . 28
7.3.5.3 Example: Client notification about UE Information change (informative) . 29
7.3.6 Subscribe Cancellation . 29
7.3.6.1 Definition . 29
7.3.6.2 Example: Cancelling a UE Location subscription (informative) . 30
7.3.6.3 Example: Cancelling a UE Information subscription (informative). 30
7.3.6.4 Example: Cancelling a UE Tracking subscription (informative) . 30
7.3.6.5 Example: Cancelling a UE Distance subscription (informative) . 31
7.3.6.6 Example: Cancelling a UE Area subscription (informative) . 31
7.3.7 Radio Node Location Lookup . 31
7.3.7.1 Definition . 31
7.3.7.2 Example: Retrieve a list of radio nodes associated to a zone (informative) . 31
7.3.8 UE Tracking Subscribe . 32
7.3.8.1 Definition . 32
7.3.8.2 Example: Create a UE Tracking subscription (informative) . 33
7.3.8.3 Example: Client notification about UE Tracking change (informative) . 33
7.3.9 UE Distance Lookup . 34
7.3.9.1 Definition . 34
7.3.9.2 Example: Distance between a terminal and a location (informative) . 34
7.3.9.3 Example: Distance between two terminals (informative) . 35
7.3.10 UE Distance Subscribe . 35
7.3.10.1 Definition . 35
7.3.10.2 Example: Create a UE Distance subscription (informative) . 35
7.3.10.3 Example: Client notification about UE Tracking change (informative) . 36
7.3.11 UE Area Subscribe. 37
7.3.11.1 Definition . 37
7.3.11.2 Example: Create a UE Area subscription (informative) . 37
7.3.11.3 Example: Client notification about UE Area change (informative) . 38
Annex A (informative): Complementary material for API utilisation . 39
History . 40

ETSI
5 ETSI GS MEC 013 V2.2.1 (2022-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
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.
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
6 ETSI GS MEC 013 V2.2.1 (2022-01)
1 Scope
The present document focuses on the MEC Location Service. It describes the related application policy information
including authorization and access control, information flows, required information and service aggregation patterns.
The present document specifies the necessary API with the data model and data format.
It is to be noted that the actual data model and data format which is functional for the present API re-uses the definitions
in "RESTful Network API for Zonal Presence" [5] and "RESTful Network API for Terminal Location" [6] published by
the Open Mobile Alliance.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI GS MEC 001: "Multi-access Edge Computing (MEC); Terminology".
[2] ETSI GS MEC 002: "Multi-access Edge Computing (MEC); Phase 2: Use Cases and
Requirements".
[3] ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference
Architecture".
[4] ETSI GS MEC 009 (V2.1.1): "Multi-access Edge Computing (MEC); General principles for MEC
Service APIs".
[5] OMA-TS-REST-NetAPI-ZonalPresence-V1-0-20160308-C: "RESTful Network API for Zonal
Presence".
[6] OMA-TS-REST-NetAPI-TerminalLocation-V1-0-1-20151029-A: "RESTful Network API for
Terminal Location".
[7] OMA-TS-REST-NetAPI-ACR-V1-0-20151201-C: "RESTful Network API for Anonymous
Customer Reference Management".
[8] ETSI TS 129 171: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; Location Services (LCS); LCS Application
Protocol (LCS-AP) between the Mobile Management Entity (MME) and Evolved Serving Mobile
Location Centre (E-SMLC); SLs interface (3GPP TS 29.171)".
[9] Void.
[10] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2".
NOTE: Available at https://tools.ietf.org/html/rfc5246.
[11] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
NOTE: Available at https://tools.ietf.org/html/rfc6749.
ETSI
7 ETSI GS MEC 013 V2.2.1 (2022-01)
[12] IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
NOTE: Available at https://tools.ietf.org/html/rfc6750.
[13] National Geospatial-Intelligence Agency (NGA) Standardization Document: "World Geodetic
System 1984, Its Definition and Relationships with Local Geodetic Systems",
NGA.STND.0036-1.0.0-WGS84, 2014-07-08, Version 1.0.0.
NOTE: Available at https://earth-info.nga.mil/php/download.php?file=coord-wgs84.
[14] ETSI TS 123 032: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); Universal Geographical Area Description (GAD)
(3GPP TS 23.032)".
[15] IETF RFC 6225: "Dynamic Host Configuration Protocol Options for Coordinate-Based Location
Configuration Information".
NOTE: Available at https://tools.ietf.org/html/rfc6225.
[16] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3".
NOTE: Available at https://tools.ietf.org/html/rfc8446.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] SCF 084.07.01: "Small cell zone services - RESTful bindings".
[i.2] SCF 152.07.01: "Small cell services API".
[i.3] OpenAPI™ Specification.
NOTE: Available at https://github.com/OAI/OpenAPI-Specification.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI GS MEC 001 [1] and the following apply:
Anonymous Customer Reference (ACR): Uniform Resource Identifier (URI) scheme describing an anonymous
reference that can be mapped to a resource or user/user group
3.2 Symbols
Void.
ETSI
8 ETSI GS MEC 013 V2.2.1 (2022-01)
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS MEC 001 [1] and the following apply:
ACR Anonymous Customer Reference
API Application Programming Interface
E-SMLC Evolved Serving Mobile Location Centre
ID IDentifier
LS Location Service
OMA Open Mobile Alliance
REST REpresentational State Transfer
SCF Small Cell Forum
UE User Equipment
URI Uniform Resource Identifier
URL Uniform Resource Locator
WGS World Geodetic System
4 Overview
The present document specifies the Location Service API to support the requirements defined for Multi-access Edge
Computing in ETSI GS MEC 002 [2]. The Location Service (LS) defined in the present document leverages the Zonal
Presence service described in SCF 084.07.01 [i.1] and in SCF 152.07.01 [i.2]. The Location Service is accessible
through the API defined in the Open Mobile Alliance (OMA) specification "RESTful Network API for Zonal
Presence" [5]. In addition, the LS offers capabilities of the API defined by the OMA specification "RESTful Network
API for Terminal Location" [6].
In addition to referencing the OMA APIs [5] and [6], the present document contains application instructions on how to
apply these OMA APIs in the MEC environment, and application instructions on how the Anonymous Customer
Reference (ACR) defined in [7] can be applied to fulfil the ETSI MEC requirement [Location-04] on addressing user
categories defined in ETSI GS MEC 002 [2], and application instructions on how the 3GPP Cell Identifiers defined in
ETSI TS 129 171 [8] can be mapped to the Access Point identifier of the OMA API [5].
5 Description of the service (informative)
5.1 Introduction
Location Service is a service to provide the location related information to the MEC platform or authorized
applications. With location related information, the MEC platform or applications perform the active device location
tracking, location-based service recommendation, etc., see ETSI GS MEC 002 [2]. The Location Service is registered
and discovered over the Mp1 reference point defined in ETSI GS MEC 003 [3].
The Location Service supports the location retrieval mechanism, i.e. the location is reported only once for each location
information request.
The Location Service supports the location subscribe mechanism, i.e. the location is able to be reported multiple times
for each location request, periodically or based on specific events, such as location change.
The Location Service supports the anonymous location report, i.e. without the related UE ID information, e.g. for the
statistics collection.
The Location Service supports the following location information:
• the location information of specific UEs currently served by the radio node(s) associated with the MEC host;
• the location information of all UEs currently served by the radio node(s) associated with the MEC host;
• the distance between specified UEs currently served by the radio node(s) associated with the MEC host;
ETSI
9 ETSI GS MEC 013 V2.2.1 (2022-01)
• the distance between a specified location and a UE currently served by the radio node(s) associated with the
MEC host;
• the location information of a certain category of UEs currently served by the radio node(s) associated with the
MEC host;
• a list of UEs in a particular location area;
• the specific UEs which move in or out of a particular location area;
• information about the location of all radio nodes currently associated with the MEC host;
• subscriptions to location information are also offered, including periodic location information updates, updates
on changes in distance and location updates relating to UEs in a particular location area.
The Location Service supports both geolocation, such as a geographical coordinates, and logical location, such as a Cell
ID.
5.2 Relation with OMA APIs
5.2.1 Relation with OMA API for Zonal Presence
The Zonal Presence service utilizes the concept of "zone", defined in OMA API [5]. According to the definition therein,
a zone lends itself to be used to group all the radio nodes that are associated to a MEC host, or a subset of them,
according to the desired deployment.
The OMA Zonal Presence API provides means for an application to retrieve information about a zone, the access points
associated to the zones and the users that are connected to the access points. In addition, the OMA Zonal Presence API
allows authorized application to subscribe to a notification mechanism, reporting about user activities within a zone.
In the present document, clauses 6 and 7 define how the OMA Zonal Presence API is used in providing the MEC
Location Service.
5.2.2 Relation with OMA API for Terminal Location
The OMA Terminal Location API [6] provides means for an application to retrieve information about the location of a
terminal or group of terminals, as well as the distance between terminals, or distance of a terminal from a given
location. In addition, the OMA Terminal Location API allows authorized application to subscribe to a notification
mechanism, reporting about terminal location activities.
In the present document, clauses 6 and 7 define how the OMA Terminal Location API is used in providing the MEC
Location Service.
5.3 Sequence diagrams
5.3.1 Introduction
Clauses 5.3.2 to 5.3.11 describe how the Service Consumers interact with the Location Service over LS API to obtain
location information of a UE, a group of UEs or the radio nodes currently associated with the MEC host. The sequence
diagrams that are relevant for the Location Service are presented.
The Service Consumers communicate with the Location Service over the LS API. Both the MEC application and MEC
platform can be Service Consumers. Location information can be provided by both MEC platform and MEC
application.
The Location Service API supports both queries and subscriptions (pub/sub mechanism) that can be used over RESTful
API as per the mechanism in OMA APIs [5] and [6].
ETSI
10 ETSI GS MEC 013 V2.2.1 (2022-01)
5.3.2 UE Location Lookup
The UE Location Lookup is the procedure for applications acquiring the current location information of a specific UE
or a group of UEs. In this procedure, the MEC Application will query the UE information firstly and the procedure may
stop if the UE information in response message contains the location information. Otherwise, the MEC Application will
query the location of the access point by the zone ID and access point ID which are contained in the UE information.
The UE Location Lookup procedure is illustrated in figure 5.3.2-1.

Figure 5.3.2-1: Flow of UE Location Lookup
Steps 1) and 2) are defined in clause 5.3.3 of the present document. If the UserInfo element in the response contains any
of the locationInfo or contextLocationInfo sub-elements, then the procedure may stop, otherwise steps 3) and 4) may be
issued.
3) The MEC application looks up access point information by sending a request to the resource AccessPointInfo.
The URI of the resource consists of zone ID and access point ID which are obtained in the message received in
step 2).
4) The Location Service returns a response with a message body including the access point information in which
the location information is contained.
5.3.3 UE Information Lookup
The UE Information Lookup is the procedure for applications acquiring information pertaining to one or more UEs in a
particular location. In this procedure, the Location Service will report the lookup result once on each request.
The UE Information Lookup procedure is illustrated in figure 5.3.3-1.

Figure 5.3.3-1: Flow of UE Information Lookup
ETSI
11 ETSI GS MEC 013 V2.2.1 (2022-01)
1) The MEC application looks up UE information in a particular area by sending a request to the resource
representing the UE Information, which includes location area information. The request may optionally
include one or more query parameters specifying the sub-region of interest, the Access Point identifier and
requirements on reporting timeliness and accuracy.
2) The Location Service returns a response with a message body including the UE information of the UE(s)
according to the query parameters in the location area, if the UE information lookup is accepted.
5.3.4 UE Location Subscribe
The UE Location Subscribe is the procedure for applications to request to receive notifications about location
information changes of a specific UE or a group of UEs, which for instance may help the applications to regularly track
the UE(s) location. In this procedure, the Location Service will continue to report the subscribed information until the
subscription is cancelled, or an optional specified time limit.
The UE Location Subscribe procedure is illustrated in figure 5.3.4-1.

Figure 5.3.4-1: Flow of UE Location Subscribe
1) The MEC application subscribes to UE location notification by requesting the creation of a resource
containing the subscription details, which includes UE(s) identifier, e.g. UE IP address, and a callbackURL for
receiving the UE location.
2) The Location Service returns a response with resource URI containing the subscriptionId.
3) The Location Service reports the up-to-data subscribed information to the MEC application by sending a
message with the message body containing the UE Location notification to the callbackURL, which includes
location information.
4) The MEC application returns a response with the code 204.
5.3.5 UE Information Subscribe
The UE Information Subscribe is the procedure for applications to receive notifications of UE Information updates for
the list of UEs in a particular location. Notifications can be to update status changes of UE information, e.g. UE
entering the specified area. In this procedure, the Location Service will continue to report the subscribed information
until the subscription is cancelled.
The UE Information Subscribe procedure is illustrated in figure 5.3.5-1.
ETSI
12 ETSI GS MEC 013 V2.2.1 (2022-01)

Figure 5.3.5-1: Flow of UE Information Subscribe
1) The MEC application subscribes to the UE information notification for a particular area by requesting the
creation of a resource containing all subscription details, which includes location area information and a
callbackURL for receiving the UE information.
2) The Location Service returns a response with resource URI containing the subscriptionId.
3) The Location Service reports the subscribed information to the MEC application by sending a message with
the request body containing the UE Information notification to the callbackURL, which includes the UE
information for each UE in the location area.
4) The MEC application returns a response with the code 204.
5.3.6 Subscribe Cancellation
The Subscribe Cancellation is the procedure for applications to cancel the subscription, with which the Location Service
stop reporting the subscribed information to the application.
The Subscribe Cancellation procedure is illustrated in figure 5.3.6-1.

Figure 5.3.6-1: Flow of Location Subscribe Cancellation
1) The MEC application unsubscribes to notifications by sending a request to delete the resource URI containing
the subscriptionId.
2) The Location Service returns a successful response if the subscription cancellation is accepted.
5.3.7 Radio Node Location Lookup
The Radio Node Location Lookup procedure enables an application to make a location enquiry about the radio nodes
currently associated with the MEC host. The Radio Node Location Lookup procedure is illustrated in figure 5.3.7-1.
ETSI
13 ETSI GS MEC 013 V2.2.1 (2022-01)

Figure 5.3.7-1: Radio Node Location Lookup
1) The MEC application makes an enquiry about the radio nodes currently associated with the MEC host by
sending a request to the resource representing radio node information, e.g. E-CGI as per ETSI TS 129 171 [8].
2) The Location Service returns a response with message body including the list of radio nodes currently
associated with the MEC host and the location of each radio node.
5.3.8 UE Tracking Subscribe
The UE Tracking Subscribe is the procedure for applications to receive notifications of UE information updates for a
specified UE. The UE information updates can be triggered by status changes, e.g. the UE handing over between cells.
In this procedure, the Location Service will continue to report the subscribed information until the subscription is
cancelled.
The UE Tracking Subscribe procedure is illustrated in figure 5.3.8-1.

Figure 5.3.8-1: Flow of UE Tracking Subscribe
1) The MEC application subscribes to the UE Tracking notification by requesting the creation of a resource
containing all subscription details, which includes the UE identifier, e.g. UE IP address, and a callbackURL
for receiving the UE location.
2) The Location Service returns a response with resource URI containing the subscriptionId.
3) The Location Service reports the subscribed information to the MEC application by sending a message with
the request body containing the UE Tracking notification to the callbackURL, which includes the UE location
information.
4) The MEC application returns a response with the code 204.
5.3.9 UE Distance Lookup
The UE Distance Lookup is the procedure for applications acquiring the current distance of a specific UE to a
geographical location, or another UE.
ETSI
14 ETSI GS MEC 013 V2.2.1 (2022-01)
The UE Distance Lookup procedure is illustrated in figure 5.3.9-1.

Figure 5.3.9-1: Flow of UE Distance Lookup
1) The MEC application looks up an UE distance by sending a request to the resource representing the UE
distance, which includes the two UE identities, e.g. UE IP address, or a single UE identifier plus the
coordinates of the location to measure from.
2) The Location Service returns a response with a message body including the distance information if the UE
location lookup is accepted.
5.3.10 UE Distance Subscribe
The UE Distance Subscribe is the procedure for applications acquiring up-to-data distance of a specific UE to a
geographical location, or another UE. In this procedure, the Location Service will continue to report the subscribed
information until the subscription is cancelled.
The UE Distance Subscribe procedure is illustrated in figure 5.3.10-1.

Figure 5.3.10-1: Flow of UE Distance Subscribe
1) The MEC application subscribes to UE distance notification by requesting the creation of a resource
containing the subscription details, with a callbackURL for receiving the UE distance. It also includes the UE
identities, e.g. UE IP address, between which to calculate the distances, the required accuracy and the
minimum interval between notifications.
2) The Location Service returns a response with resource URI containing the subscriptionId.
3) The Location Service reports the up-to-data subscribed information to the MEC application by sending a
message with the message body containing the UE Distance notification to the callbackURL, which includes
distance information.
4) The MEC application returns a response with the code 204.
ETSI
15 ETSI GS MEC 013 V2.2.1 (2022-01)
5.3.11 UE Area Subscribe
The UE Area Subscribe is the procedure for applications acquiring UE movement notifications in relation to a
geographic area. In this procedure, the Location Service will continue to report the subscribed information until the
subscription is cancelled.
The UE Area Subscribe procedure is illustrated in figure 5.3.11-1.

Figure 5.3.11-1: Flow of UE Area Subscribe
1) The MEC application subscribes to UE Area notifications by requesting the creation of a resource containing
the subscription details, which includes the UE identities, e.g. UE IP address, and a callbackURL for receiving
the UE Area notification. Also included is the area definition, the required accuracy, the minimum interval
between notifications and whether notifications should be generated on entering, or leaving the area, or both.
2) The Location Service returns a response with resource URI containing the subscriptionId.
3) The Location Service reports the up-to-data subscribed information to the MEC application by sending a
message with the message body containing the UE Area notification to the callbackURL, which includes area
information.
4) The MEC application returns a response with the code 204.
6 Data Model
6.1 Introduction
Data types from the APIs defined in [5] and in [6] are reused. The following application instructions describe the
mapping between the terminology used in the OMA specifications and the terminologies used in ETSI MEC and ETSI
TS 129 171 [8].
The elements specified in OMA APIs' data models in [5] and [6] shall be represented as a JSON object. Moreover, the
elements therein with upperbound cardinality greater than 1, e.g. "0. N", "1. N" etc., shall be represented as a JSON
array.
6.2 Resource data types
6.2.1 Zonal presence data types
The data structures to be used in resource representations for the Location Service API consist in the following data
types defined in [5], clause 5:
• ZoneList
A type containing list of zones' information;
ETSI
16 ETSI GS MEC 013 V2.2.1 (2022-01)
• ZoneInfo
A type containing zone information;
• AccessPointList
A type containing list of access points' information;
• AccessPointInfo
A type containing access point information;
• UserList
A type containing list of users' information;
• UserInfo
A type containing user information, expanded by the present document to optionally include location
information.
6.2.1A Terminal location data types
In addition, further data types as defined in [6], clause 5, are offered:
• TerminalLocation
A type containing device address, retrieval
...