1、 ETSI GS NGP 001 V1.1.1 (2016-10) Next Generation Protocols (NGP); Scenarios Definitions Disclaimer The present document has been produced and approved by the Next Generation Protocols (NGP) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this IS
2、G. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS NGP 001 V1.1.1 (2016-10)2 Reference DGS/NGP-001 Keywords core network, cyber security, IoT, mobility, network, QoE, reliability, security, service, use case ETSI 650 Route des Lucioles F-06
3、921 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-searc
4、h 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
5、such versions and/or in print, the only prevailing document 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
6、 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 Notifi
7、cation 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 a
8、nd the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. 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 register
9、ed for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS NGP 001 V1.1.1 (2016-10)3 Contents Intellectual Property Rights 6g3Foreword . 6g3Modal verbs terminology 6g31 Scope 7g32 Reference
10、s 7g32.1 Normative references . 7g32.2 Informative references 8g33 Definitions and abbreviations . 9g33.1 Definitions 9g33.2 Abbreviations . 15g34 Overview 18g35 Issues to be addressed by the Scenarios . 19g36 Model References . 21g36.0 Introduction 21g36.1 LTE Mobile Network Model 21g36.2 L2 and L3
11、 VPN services 24g36.2.0 Introduction. 24g36.2.1 MPLS/BGP Layer 3 Virtual Private Networks . 24g36.2.2 VPLS, Virtual Private Line Services and Ethernet-VPN. . 25g36.3 All IP Core Network Model . 27g36.4 NFV Reference Model . 29g36.5 MEC Reference Model . 30g37 Referenced Use Cases 31g38 Scenarios 32g
12、38.1 Addressing 32g38.1.0 Introduction. 32g38.1.1 Model Architecture . 33g38.1.2 Scenario Description . 34g38.1.2.0 Introduction . 34g38.1.2.1 Scenarios for mobile communication 34g38.1.2.2 Scenarios for multi-homing and load balancing 35g38.1.3 Applicable Issues 36g38.1.4 Applicable Use Cases . 36g
13、38.1.4.1 Case 1: UE communicates with a fixed device; UE is moving within a same P-GW domain 36g38.1.4.2 Case 2: UE communicates with a fixed device; UE is moving across different P-GW domain . 37g38.1.4.3 Case 3: UE communicates with a fixed device; UE is moving across heterogeneous access network
14、. 37g38.1.4.4 Case 4: UE communicates with another UE; UE is moving within a same P-GW domain 38g38.1.4.5 Case 5: UE communicates with another UE; UE is moving across different P-GW domain 38g38.1.4.6 Case 6: UE communicates with another UE; UE is moving across heterogeneous access network . 39g38.1
15、.4.7 Case 7: Multi-homing host connected to different ISP for link protection or load balance 39g38.1.4.8 Case 8: Customer network with multi-homing site connected to different ISP for link protection or load balancing . 39g38.1.5 Scenario Targets . 40g38.2 Security 41g38.2.1 Model Architecture/Prot
16、ocol Stacks . 41g38.2.2 Scenario Description . 41g38.2.2.1 Scenario summary . 41g38.2.2.2 Security approach 41g38.2.2.3 Description of new security challenges 42g38.2.3 Applicable Issues 42g38.2.4 Applicable Use Cases . 46g3ETSI ETSI GS NGP 001 V1.1.1 (2016-10)4 8.2.5 Scenario Targets . 46g38.3 Mobi
17、lity 48g38.3.1 Model Architecture . 48g38.3.2 Scenario Description . 50g38.3.3 Applicable Issues 51g38.3.4 Applicable Use Cases . 53g38.3.4.0 Introduction . 53g38.3.4.1 Case 1: Multi-Access, Session Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is av
18、ailable 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 S
19、R 000 314 (or the updates on the ETSI 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) Next Generation Protocols (NGP). Modal verbs terminology In the present docume
20、nt “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 wh
21、en used in direct citation. ETSI ETSI GS NGP 001 V1.1.1 (2016-10)7 1 Scope The scope of the present document is to specify the minimum set of key scenarios for the Next Generation Protocols (NGP), Industry Specific Group (ISG). 2 References 2.1 Normative references References are either specific (id
22、entified 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 t
23、o 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 app
24、lication of the present document. 1 NGMN: “5G Whitepaper“. NOTE: NGMN specifications are available at https:/www.ngmn.org/uploads/. 2 Recommendation ITU-T Y.2091: “Terms and definitions for next generation networks“. 3 Recommendation ITU-T Y.2720: “NGN identity management framework“. 4 IETF RFC 6830
25、: “ The Locator/ID Separation Protocol (LISP)“. 5 IETF RFC 760: “DoD standard Internet Protocol“. 6 ISO/IEC 7498-1:1994: “Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model“. 7 World Geodetic System 1984. 8 ETSI GS NFV 002: “Network Functions Virtualisatio
26、n (NFV); Architectural Framework“. 9 ETSI GS NFV 003: “Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV“. 10 IETF RFC 4364: “BGP/MPLS IP Virtual Private Networks (VPNs)“. 11 IETF RFC 4761: “Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling“. 12
27、 IETF RFC 3753: “Mobility Related Terminology“. 13 IETF RFC 7333: “Requirements for Distributed Mobility Management“. 14 IETF draft-ietf-lisp-lcaf-14 (LISP): “LISP Canonical Address Format (LCAF)“. 15 IETF draft-farinacci-lisp-eid-anonymity-00 (LISP): “LISP EID Anonymity“. 16 ETSI GS NFV 001 (V1.1.1
28、): “Network Functions Virtualisation (NFV); Use Cases“. NOTE: ETSI NFV references are available at http:/www.etsi.org/deliver/etsi_gs/NFV/. 17 ETSI GS NFV-MAN 001 (V1.1.1): “Network Functions Virtualisation (NFV); Management and Orchestration“. ETSI ETSI GS NGP 001 V1.1.1 (2016-10)8 18 ETSI GS NFV-S
29、EC 003 (V1.1.1): “Network Functions Virtualisation (NFV); NFV Security; Security and Trust Guidance“. 19 ETSI GS MEC 001 (V1.1.1): “Mobile Edge Computing (MEC) Terminology“. NOTE: MEC references are available at http:/www.etsi.org/deliver/etsi_gs/MEC/. 20 ETSI GS MEC 003 (V1.1.1): “Mobile Edge Compu
30、ting (MEC); Framework and Reference Architecture“. 21 ETSI GS MEC-IEG 004 (V1.1.1): “Mobile-Edge Computing (MEC); Service Scenarios“. 22 ETSI TS 103 307: “CYBER; Security Aspects for LI and RD Interfaces“. 23 ETSI GS NFV-SEC 009 (V1.1.1): “Network Functions Virtualisation (NFV); NFV Security; Report
31、 on use cases and technical approaches for multi-layer host administration“. NOTE: ONF references are available at https:/www.opennetworking.org/about/onf-overview. 24 ETSI TS 132 500: “Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Self-Organizing Networks (SO
32、N); Concepts and requirements (3GPP TS 32.500)“. 25 MEC White-paper: “Mobile Edge Computing: A key technology towards 5G“, 2015. NOTE: ETSI whitepapers are available at http:/www.etsi.org/technologies-clusters/white-papers-and-brochures/etsi-white-papers. 26 IEEE 802.1ah : “ Provider Backbone Bridge
33、s“. 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 an
34、y 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
35、particular subject area. i.1 3GPP TR 22.891: “Feasibility Study on New Services and Markets Technology Enablers; Stage 1“ (SMARTER). NOTE: 3GPP specifications are available at http:/www.3gpp.org/specifications/specifications. i.2 3GPP TR 23.799: “Study on Architecture for Next Generation System“ (Ne
36、xGen). i.3 ETSI TR 121 905: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Vocabulary for 3GPP Specifications (3GPP TR 21.905)“. i.4 5GPPP Whitepaper on Automotive Vertical Sector. NOTE: 5GPPP specifications are available at: https:/5g
37、-ppp.eu/white-papers/. i.5 5GPPP Whitepaper on Energy Vertical Sector. i.6 5GPPP Whitepaper on Factories of the Future. i.7 5GPPP Whitepaper on E-Health. i.8 Elements of Mathematics: “General Topology“, Berlin, Springer- Verlag, 1990, Bourbaki, N. 1971. ETSI ETSI GS NGP 001 V1.1.1 (2016-10)9 i.9 “El
38、ements of the Topology of Plane Sets of Points“, Newman, M, 1964. i.10 “High-Speed Networks and Internets“, Stallings, William; Prentice-Hall, 2002. i.11 Risk Nexus: “Overcome by cyber risks? Economic benefits and costs of alternate cyber futures“. NOTE: Available at http:/www.cse.wustl.edu/jain/pap
39、ers/. i.12 “A Binary Feedback Scheme for Congestion Avoidance in Computer Networks with Connectionless Network Layer,“ ACM Transactions on Computer Systems, Vol. 8, No. 2, May 1990, pp. 158-181, K. Ramakrishnan and Raj Jain. NOTE: Available at http:/www.cse.wustl.edu/jain/papers/. i.13 “Congestion A
40、voidance in Computer Networks with A Connectionless Network Layer: Part IV: A Selective Binary Feedback Scheme for General Topologies,“ Digital Equipment Corporation Technical Report No. DEC-TR-510, August 1987, 43 pp., K. Ramakrishnan and Raj Jain. i.14 “Timer-Based Mechanisms in Reliable Transport
41、 Protocol Connection Management“ Computer Networks 5, 1981: 47-56, Watson, R. i.15 IETF RFC 4762: “Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling“. i.16 IETF RFC 4984: “Report from the IAB Workshop on Routing and Addressing“. i.17 3GPP TR 23.863: “Support of Sho
42、rt Message Service (SMS) in IP Multimedia Subsystem (IMS) without Mobile Station International ISDN Number (MSISDN); Stage 2“. i.18 3GPP TR 22.864: “FS-SMARTER - Network Operation“. i.19 IETF RFC 6582: “The NewReno Modification to TCPs Fast Recovery Algorithm“. i.20 IETF RFC 2018: “TCP Selective Ack
43、nowledgment Options“. i.21 ETSI GS MEC 002: “Mobile Edge Computing (MEC); Technical Requirements“. i.22 ETSI GS MEC-IEG 005: “Mobile-Edge Computing (MEC); Proof of Concept Framework“. i.23 IETF RFC 7041: “Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Back
44、bone Bridging“. i.24 5G Manifesto for timely deployment of 5G. i.25 3GPP TR 38.913: “Study on Scenarios and Requirements for Next Generation Access Technologies“. i.26 IETF Charter of IETF DMM documents. NOTE: IETF DMM Charter references are available at https:/datatracker.ietf.org/wg/dmm/charter/.
45、i.27 Broadband Forum TR-069: “CPE WAN Management Protocol“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions applying to scenarios that include mobile network architectures given in ETSI TR 121 905 i.3 and 3GPP TR 23.799 i.2 apply. a
46、ccess point: point of access to a network, which in this generic NGP context may be a traditional Wi-Fi access point, 3GPP cellular network base station, RRU supporting a cell or sector or part thereof if the cell is configured as a multi-point access cell ETSI ETSI GS NGP 001 V1.1.1 (2016-10)10 add
47、ress: identifier for a specific termination point and is used for routing to this termination point NOTE: See Recommendation ITU-T Y.2091 2. application process: instantiation of a program executing in a processing system intended to accomplish some purpose. An application contains one or more appli
48、cation protocol machines application process name: name of an application process application protocol: protocol characterized by modifying state external to the protocol by performing remote operations on an object model NOTE: The minimal set of operations are create/ delete, start/ stop, and read/
49、 write. application protocol name: name of an application protocol asymmetric link: link with transmission characteristics which are different depending upon the relative position or design characteristics of the transmitter and the receiver of data on the link NOTE: For instance, the range of one transmitter may be much higher than the range of another transmitter on the same medium see IETF RFC 3753 12. backhaul: transmission system between a bas
