ETSI GS MEC 013-2017 Mobile Edge Computing (MEC) Location API (V1 1 1).pdf

1、 ETSI GS MEC 013 V1.1.1 (2017-07) Mobile Edge Computing (MEC); Location API Disclaimer The present document has been produced and approved by the Mobile Edge Computing (MEC) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. It does not ne

2、cessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS MEC 013 V1.1.1 (2017-07) 2 Reference DGS/MEC-0013LocationApi Keywords API, location, MEC, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65

3、 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture 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 i

4、n 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 only prevailing document is the print of

5、the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. 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 http

6、s:/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, el

7、ectronic 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 2017.

8、 All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of

9、its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS MEC 013 V1.1.1 (2017-07) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references

10、7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Overview 7g35 Description of the service (informative). 8g35.1 Introduction 8g35.2 Relation with OMA API for Zonal Presence 8g35.3 Sequence diagrams . 9g35.3.1 Introduction. 9g35.3.2 UE Location Lookup 9g35.3.3 UE In

11、formation Lookup 9g35.3.4 UE Location Subscribe . 10g35.3.5 UE Information Subscribe 10g35.3.6 Subscribe Cancellation . 11g35.3.7 Radio Node Location Lookup . 11g36 Data Model . 12g36.1 Introduction 12g36.2 Resource data types 12g36.2.1 Zonal presence data types . 12g36.2.2 Type: UserInfo 12g36.3 Su

12、bscription data types . 13g36.4 Notifications data types 13g36.5 Referenced structured data types 13g36.6 Mapping of Identifiers 14g36.6.1 accessPointId 14g36.6.2 userId 14g37 API definition . 14g37.1 Introduction 14g37.2 Global definitions and relation with OMA resources . 14g37.3 Mapping of servic

13、es to API functions 15g37.3.1 Introduction. 15g37.3.2 UE Location Lookup 15g37.3.2.1 Definition 15g37.3.2.2 Example: Two steps method to retrieve the geographical coordinates of an access point a specific user is connected to (informative) . 15g37.3.3 UE Information Lookup 16g37.3.3.1 Definition 16g

14、37.3.3.2 Example: Retrieve UE Information for all the users (informative) . 16g37.3.3.3 Example: Retrieve UE Information for the users in a zone (informative). 17g37.3.3.4 Example: Retrieve UE Information for the users in an access point of a zone (informative) . 18g37.3.4 UE Location Subscribe . 18

15、g37.3.4.1 Definition 18g37.3.4.2 Example: create a UE Location subscription (informative) 18g37.3.5 UE Information Subscribe 19g37.3.5.1 Definition 19g3ETSI ETSI GS MEC 013 V1.1.1 (2017-07) 4 7.3.5.2 Example: create a UE Information subscription (informative) . 19g37.3.6 Subscribe Cancellation . 20g

16、37.3.6.1 Definition 20g37.3.6.2 Example: cancelling a UE Location subscription (informative) . 20g37.3.6.3 Example: cancelling a UE Information subscription (informative) 21g37.3.7 Radio Node Location Lookup . 21g37.3.7.1 Definition 21g37.3.7.2 Example: Retrieve a list of radio nodes associated to a

17、 zone (informative) 21g3Annex A (informative): Complementary material for API utilisation 23g3History 24g3ETSI ETSI GS MEC 013 V1.1.1 (2017-07) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to

18、 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. La

19、test 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

20、 Web server) which are, or may be, or may become, essential to the present document. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Mobile Edge Computing (MEC). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “shoul

21、d 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 ETSI GS

22、MEC 013 V1.1.1 (2017-07) 6 1 Scope The present document focuses on the Mobile Edge 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 spec

23、ifies 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 is defined in “RESTful Network API for Zonal Presence“ published by the Open Mobile Alliance 5. 2 References 2.1 Normative references Refe

24、rences 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 d

25、ocuments 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 docume

26、nts are necessary for the application of the present document. 1 ETSI GS MEC 001: “Mobile Edge Computing (MEC); Terminology“. 2 ETSI GS MEC 002: “Mobile Edge Computing (MEC); Technical Requirements“. 3 ETSI GS MEC 003: “Mobile Edge Computing (MEC); Framework and Reference Architecture“. 4 ETSI GS ME

27、C 009: “Mobile Edge Computing (MEC); General principles for Mobile Edge Service APIs“. 5 OMA-TS-REST-NetAPI-ZonalPresence-V1-0-20160308-C: “RESTful Network API for Zonal Presence“. 6 OMA-TS-REST-NetAPI-ACR-V1-0-20151201-C: “RESTful Network API for Anonymous Customer Reference Management“. 7 ETSI TS

28、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 (3GP

29、P TS 29.171)“. 8 IETF RFC 2818: “HTTP Over TLS“. NOTE: Available at https:/tools.ietf.org/html/rfc2818. 9 IETF RFC 5246: “The Transport Layer Security (TLS) Protocol Version 1.2“. NOTE: Available at https:/tools.ietf.org/html/rfc5246. 10 IETF RFC 6749: “The OAuth 2.0 Authorization Framework“. NOTE:

30、Available at https:/tools.ietf.org/html/rfc6749. 11 IETF RFC 6750: “The OAuth 2.0 Authorization Framework: Bearer Token Usage“. NOTE: Available at https:/tools.ietf.org/html/rfc6750. ETSI ETSI GS MEC 013 V1.1.1 (2017-07) 7 2.2 Informative references References are either specific (identified by date

31、 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 va

32、lid 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 b

33、indings“. i.2 SCF 152.07.01: “Small cell services API“. i.3 OpenAPI Specification. NOTE 1: Available at https:/ NOTE 2: OpenAPI Specification version 2.0 is recommended as it is the official release at the time of publication. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the p

34、resent document, the terms and definitions 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 Abbreviations For the purposes of the

35、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

36、 SCF Small Cell Forum UE User EquipmentURI Uniform Resource Identifier URL Uniform Resource Locator 4 Overview The present document specifies the Location Service API to support the requirements defined for Mobile Edge Computing in ETSI GS MEC 002 2. The Location Service (LS) defined in the present

37、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. ETSI ETSI GS MEC 013 V1.1.1 (2017-07) 8 In add

38、ition to referencing the OMA API 5, the present document contains application instructions on how to apply the OMA API 5 in the MEC environment, and application instructions on how the Anonymous Customer Reference (ACR) defined in 6 can be applied to fulfil the ETSI MEC requirement Location-04 on ad

39、dressing user categories defined in ETSI GS MEC 002 2, and application instructions on how the 3GPP Cell Identifiers defined in ETSI TS 129 171 7 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 t

40、o provide the location related information to the Mobile edge platform or authorized applications. With location related information, the Mobile edge platform or applications perform the active device location tracking, location-based service recommendation, etc. see ETSI GS MEC 002 2. The Location

41、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 mechanis

42、m, 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 Lo

43、cation Service supports the following location information: the location information of specific UEs currently served by the radio node(s) associated with the Mobile edge host; the location information of all UEs currently served by the radio node(s) associated with the Mobile edge host; the locatio

44、n information of a certain category of UEs currently served by the radio node(s) associated with the Mobile edge 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 associa

45、ted with the Mobile edge host. The Location Service supports both geolocation, such as a geographical coordinates, and logical location, such as a Cell ID. 5.2 Relation with OMA API for Zonal Presence The Zonal Presence service utilizes the concept of “zone“, defined in OMA API 5. According to the d

46、efinition therein, a zone lends itself to be used to group all the radio nodes that are associated to a Mobile edge host, or a subset of them, according to the desired deployment. The OMA Zonal Presence API provides means to an application to retrieve information about a zone, the access points asso

47、ciated 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

48、 Presence API is used to provide the Mobile edge Location Service. ETSI ETSI GS MEC 013 V1.1.1 (2017-07) 9 5.3 Sequence diagrams 5.3.1 Introduction Clauses 5.3.2 to 5.3.7 describe how the Service Consumers interact with the Location Service over LS API to obtain location information of a UE, a group

49、 of UEs or the radio nodes currently associated with the Mobile edge 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 Mobile edge application and Mobile edge platform can be Service Consumers. Location information can be provided by both Mobile edge platform and Mobile edge application. The Location Service API supports both queries and sub