1、 ETSI GS MEC 015 V1.1.1 (2017-10) Mobile Edge Computing (MEC); Bandwidth Management 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
2、 does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS MEC 015 V1.1.1 (2017-10) 2 Reference DGS/MEC-0015BandMngtAPI Keywords API, bandwidth, management, MEC ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00
3、Fax: +33 4 93 65 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 v
4、ersions 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 only prevailing document
5、is the print of 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 a
6、vailable 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
7、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 m
8、edia. ETSI 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for t
9、he benefit of its Members. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI GS MEC 015 V1.1.1 (2017-10) 3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informati
10、ve references 5g33 Definitions 6g34 Abbreviations . 6g35 Overview 6g36 Description of the service (informative). 7g36.1 Introduction 7g36.2 Sequence diagrams . 7g36.2.1 General 7g36.2.2 Register to Bandwidth Management Service 7g36.2.3 Unregister from Bandwidth Management Service 8g36.2.4 Update req
11、uested bandwidth requirements on Bandwidth Management Service . 8g36.2.5 Get configured bandwidth allocation from Bandwidth Management Service 9g37 Data Model . 9g37.1 Introduction 9g37.2 Resource data types 10g37.2.1 Introduction. 10g37.2.2 Type: BwInfo 10g37.2.3 Type: BwInfoDeltas 10g38 API defini
12、tion . 11g38.1 Introduction 11g38.2 Global definitions and resource structure . 11g38.3 Resource: individual bandwidthAllocation 12g38.3.1 Description 12g38.3.2 Resource definition . 12g38.3.3 Resource Methods 12g38.3.3.1 GET . 12g38.3.3.2 PUT . 13g38.3.3.3 PATCH . 14g38.3.3.4 POST . 15g38.3.3.5 DEL
13、ETE . 15g38.4 Resource: a list of bandwidthAllocations . 16g38.4.1 Description 16g38.4.2 Resource definition . 16g38.4.3 Resource Methods 16g38.4.3.1 GET . 16g38.4.3.2 PUT . 17g38.4.3.3 PATCH . 17g38.4.3.4 POST . 17g38.4.3.5 DELETE . 18g3Annex A (informative): Complementary material for API utilizat
14、ion 19g3History 20g3ETSI ETSI GS MEC 015 V1.1.1 (2017-10) 4 Intellectual Property Rights Essential patents IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI member
15、s 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.o
16、rg/). 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 p
17、resent 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 a
18、nd/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) Mobile Edge Com
19、puting (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“ an
20、d “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI GS MEC 015 V1.1.1 (2017-10) 5 1 Scope The present document focuses on the Bandwidth Management mobile edge service. It describes the related application policy information including authorization and acc
21、ess control, information flows, required information and service aggregation patterns. The present document specifies the necessary API with the data model and data format. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number o
22、r 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
23、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: “Mo
24、bile Edge Computing (MEC) Terminology “. 2 IETF RFC 2818: “HTTP Over TLS“. NOTE: Available at https:/tools.ietf.org/html/rfc2818. 3 IETF RFC 5246: “The Transport Layer Security (TLS) Protocol Version 1.2“. NOTE: Available at https:/tools.ietf.org/html/rfc5246. 4 IETF RFC 6749: “The OAuth 2.0 Authori
25、zation Framework“. NOTE: Available at https:/tools.ietf.org/html/rfc6749. 5 IETF RFC 6750: “The OAuth 2.0 Authorization Framework: Bearer Token Usage“. NOTE: Available at https:/tools.ietf.org/html/rfc6750. 6 ETSI GS MEC 009: “Mobile Edge Computing (MEC); General principles for Mobile Edge Service A
26、PIs“. 7 IETF RFC 7396: “JSON Merge Patch“. 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 o
27、f 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
28、 they assist the user with regard to a particular subject area. i.1 ETSI GS MEC 002: “Mobile Edge Computing (MEC); Technical Requirements“. ETSI ETSI GS MEC 015 V1.1.1 (2017-10) 6 i.2 OpenAPI Specification, Version 2.0, September 8, 2014. NOTE: Available at https:/ 3 Definitions For the purposes of
29、the present document, the terms and definitions given in ETSI GS MEC 001 1 apply. 4 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GS MEC 001 1 and the following apply: API Application Programming Interface BW Bandwidth BWM Bandwidth Management BWMS Bandwidth
30、 Management Service CDN Content Delivery Network HTTP Hypertext Transfer Protocol HTTPS Hypertext Transfer Protocol Secure IETF Internet Engineering Task Force JSON Javascript Object Notation ME Mobile Edge OAI Open API Initiative RAN Radio Access Network REST Representational State Transfer RFC Req
31、uest For Comments RTT Round Trip Time TLS Transport Layer Security URI Uniform Resource Indicator UTC Coordinated Universal Time 5 Overview The present document specifies the Bandwidth Management service (BWMS) API to support the requirements defined for Mobile Edge Computing in ETSI GS MEC 002 i.1.
32、 Clause 6 introduces how BWMS can be used by the mobile edge applications and by the mobile edge platform. It describes the information flows used for BWMS. The information that can be exchanged over the Bandwidth Management (BWM) API is described in clause 7 which provides detailed description on a
33、ll information elements that are used for BWMS. Clause 8 describes the actual BWM API providing detailed information how information elements are mapped into a RESTful API design. Figure 5-1 illustrates the mission of the BWMS, which may optionally run as part of the platform or as an application. D
34、ifferent applications, whether managing a single instance or several sessions (for example CDN), may request specific bandwidth requirements (bandwidth size, bandwidth priority, or both) for the whole application instance or different bandwidth requirements per session. The BWMS may aggregate all th
35、e requests and act in a manner that will help optimize the BW usage. ETSI ETSI GS MEC 015 V1.1.1 (2017-10) 7 Figure 5-1: Bandwidth Management service description 6 Description of the service (informative) 6.1 Introduction Different mobile edge applications running in parallel on the same mobile edge
36、 host may require specific static/dynamic up/downg3bandwidth resources, including bandwidth size and bandwidth priority. In some cases different sessions running in parallel on the same application may each have specific bandwidth requirements. In addition, sessions driven by applications running fr
37、om closer to end user (shorter RTT) may receive unfair advantage over session driven by application running from distant locations (outside the RAN). As all these applications and application sessions are competing over the same shared bandwidth resources, an optional central bandwidth resource allo
38、cator service may exist on the mobile edge platform. The specific session or mobile edge application will be identified using a set of filters within the resource request. 6.2 Sequence diagrams 6.2.1 General The following clauses describe how mobile edge applications can use BWMS to update/receive b
39、andwidth information to/from the ME platform. The sequence diagrams that are relevant for BWMS are presented. The BWM API enables all registered applications to statically and/or dynamically register for specific bandwidth allocation per session/application. This specification of BWM API contains th
40、e HTTP protocol bindings for bandwidth management functionality using the REST architectural style. 6.2.2 Register to Bandwidth Management Service Figure 6.2.2-1 shows a scenario where a Mobile Edge Application registers to BWMS. ETSI ETSI GS MEC 015 V1.1.1 (2017-10) 8 Figure 6.2.2-1: Flow of Mobile
41、 Edge Application registration to BWMS Mobile Edge Application instance registration to BWMS, as illustrated in figure 6.2.2-1, consists of the following steps: 1) Mobile edge application instance sends a request to register to the BWMS with the requested bandwidth requirements (bandwidth size/prior
42、ity). 2) BWMS responds with a registration and initialization approval. 6.2.3 Unregister from Bandwidth Management Service Figure 6.2.3-1 shows a scenario where a Mobile Edge Application Instance unregisters from BWMS. Figure 6.2.3-1: Flow of Mobile Edge Application unregistering BW allocation from
43、BWMS Mobile Edge Application Instance unregistering from BWMS , as illustrated in figure 6.2.3-1, consists of the following steps: 1) Mobile Edge Application Instance sends an unregister request to BWMS. 2) BWMS responds with an unregistration approval. 6.2.4 Update requested bandwidth requirements
44、on Bandwidth Management Service Figure 6.2.4-1 shows a scenario where a Mobile Edge Application Instance updates its requested bandwidth requirements on the BWMS. ETSI ETSI GS MEC 015 V1.1.1 (2017-10) 9 Figure 6.2.4-1: Flow of Mobile Edge application updating its requested bandwidth requirements on
45、BWMS Mobile edge application instance updating its requested bandwidth requirementsg3on BWMS, as illustrated in figure 6.2.4-1, consists of the following steps: 1) Mobile Edge Application Instance sends a request to update a specific bandwidth allocation on the BWMS. 2) BWMS responds with an update
46、approval. 6.2.5 Get configured bandwidth allocation from Bandwidth Management Service Figure 6.2.5-1 shows a scenario where a Mobile Edge Application Instance gets its configured bandwidth allocation from the BWMS. Figure 6.2.5-1: Flow of Mobile Edge Application getting its configured bandwidth allo
47、cation from BWMS Mobile Edge Application Instance gets its configured bandwidth from BWMS, as illustrated in figure 6.2.5-1, consists of the following steps: 1) Mobile Edge Application Instance sends a request to get its configured bandwidth allocation on the BWMS. 2) BWMS responds with the BW alloc
48、ation details. 7 Data Model 7.1 Introduction The following clauses provide the description of the Data Model. ETSI ETSI GS MEC 015 V1.1.1 (2017-10) 10 7.2 Resource data types 7.2.1 Introduction This clause defines data structures to be used in resource representations. 7.2.2 Type: BwInfo Table 7.2.2
49、1: Elements of BwInfo Element Type Cardinality Description timeStamp Structure (inlined) 01 Time stamp seconds Uint32 1 The seconds part of the Time. Time is defined as Unix-time since January 1, 1970, 00:00:00 UTC nanoSeconds Uint32 1 The nanoseconds part of the Time. Time is defined as Unix-time since January 1, 1970, 00:00:00 UTC appInsId String 1 Application instance identifier requestType Enum (inlined) 1 Numeric value (0 - 255) corresponding to specific type of consumer as fol
