|
GROUP SPECIFICATION
Multi-access Edge Computing (MEC);
Support for regulatory requirements
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 026 V2.1.1 (2019-01)
Reference
DGS/MEC-0026LI
Keywords
Lawful Interception, MEC, Retained Data
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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:
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
If you find errors in the present document, please send your comment to one of the following services:
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 2019.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
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 026 V2.1.1 (2019-01)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 6
4 LI & RD in MEC . 6
5 LI support in different MEC deployment scenarios (informative) . 7
5.1 Introduction . 7
5.2 MEC deployed over S1 interface . 7
5.3 MEC deployed over SGi interface . 8
6 Enabling support for regulatory requirements (informative) . 9
6.1 Introduction . 9
6.2 Sequence diagrams . 10
6.2.1 General . 10
6.2.2 Configure LI & RD support ON in LI & RD Mediation Function . 11
6.2.3 Configure LI & RD support OFF in LI & RD Mediation Function . 11
7 Data model & Data format . 12
7.1 Introduction . 12
7.2 Resource data types . 12
7.2.1 Introduction. 12
7.2.2 Type: LiRdSupportInfo . 12
7.3 Subscription types . 12
7.4 Notifications types . 12
7.5 Referenced structured data types . 12
7.6 Referenced simple data types . 12
8 API definition . 12
8.1 Introduction . 12
8.2 Global definitions and resource structure . 13
8.3 Resource: liRdSupportInfo . 13
8.3.1 Description . 13
8.3.2 Resource definition . 13
8.3.3 Resource Methods . 14
8.3.3.1 GET . 14
8.3.3.2 PUT . 14
8.3.3.3 PATCH . 15
8.3.3.4 POST . 15
8.3.3.5 DELETE . 15
Annex A (informative): Example LI support for MEC deployment over S1 without CUPS . 16
Annex B (informative): Bibliography . 17
History . 18
ETSI
---------------------- Page: 3 ----------------------
4 ETSI GS MEC 026 V2.1.1 (2019-01)
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: 4 ----------------------
5 ETSI GS MEC 026 V2.1.1 (2019-01)
1 Scope
The present document focuses on the support of regulatory requirements for Lawful Interception (LI) and Retained Data
(RD) when implementing MEC into the network. It describes the problems, constraints, interfaces and additional
capabilities needed for the different deployment scenarios, to ensure full support of LI & RD regulatory requirements
when implementing MEC.
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 009: "Multi-access Edge Computing (MEC); General principles for MEC Service
APIs".
[4] IETF RFC 2818: "HTTP Over TLS".
NOTE: Available at https://tools.ietf.org/html/rfc2818.
[5] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2".
NOTE: Available at https://tools.ietf.org/html/rfc5246.
[6] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
NOTE: Available at https://tools.ietf.org/html/rfc6749.
[7] IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
NOTE: Available at https://tools.ietf.org/html/rfc6750.
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.
ETSI
---------------------- Page: 5 ----------------------
6 ETSI GS MEC 026 V2.1.1 (2019-01)
[i.1] ETSI TS 133 107: "Universal Mobile Telecommunications System (UMTS); LTE; Digital cellular
telecommunications system (Phase 2+) (GSM); 3G security; Lawful interception architecture and
functions (3GPP TS 33.107)".
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] apply.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS MEC 001 [1] and the following apply:
API Application Programing Interface
CN Core Network
CUPS Control and User Plane Separation
EPC Evolved Packet Core
HTTP Hypertext Transfer Protocol
HTTPS HTTP Secure
IMSI International Mobile Subscriber Identity
IP Internet Protocol
LEMF Law Enforcement Monitoring Facility
LI Lawful Interception
LIG LI Gateway
MEC Multi-access Edge Computing
MSISDN Mobile Station International Subscriber Directory Number
RD Retained Data
TLS Transport Layer Security
UE User Equipement
URI Uniform Resource Indicator
4 LI & RD in MEC
In the current mobile networks, LI solutions (including RD) are part of the network topology. All data that pass through
the mobile core network (e.g. EPC) is supported by these LI solutions. When implementing MEC, some traffic may be
generated or manipulated inside the MEC system or may come from a local breakout connection, thus not passing
through the core network and not supported by the existing LI solution in the network.
The deployment scenario of MEC on the SGi is standardized by 3GPP, for which the LI & RD support does not need to
be handled by MEC standard.
However, the deployment scenario of MEC on the S1 (either by the eNB or at aggregation points) may require an
alternative solution to ensure full LI and RD support when implementing MEC in the network.
Clause 5 refers to the different supported MEC deployments and presents a short analysis on the need for additional
support from MEC for each of these deployments.
Clause 6 presents what is needed from MEC to comply with the regulatory require
...