ETSI GR NGP 003-2017 NGP Next Generation Protocol Packet Routing Technologies (V1 1 1)《NGP下一代协议 分组路由技术(V1 1 1)》.pdf

《ETSI GR NGP 003-2017 NGP Next Generation Protocol Packet Routing Technologies (V1 1 1)《NGP下一代协议 分组路由技术(V1 1 1)》.pdf》由会员分享，可在线阅读，更多相关《ETSI GR NGP 003-2017 NGP Next Generation Protocol Packet Routing Technologies (V1 1 1)《NGP下一代协议 分组路由技术(V1 1 1)》.pdf（56页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GR NGP 003 V1.1.1 (2017-03) NGP Next Generation Protocol; Packet Routing Technologies 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

2、 ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP REPORT ETSI ETSI GR NGP 003 V1.1.1 (2017-03) 2 Reference DGR/NGP-003 Keywords flexilink, M2CNP, Next Generation Protocol, RINA ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94

3、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-search The present document may be made available in electr

4、onic 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 only prevailing doc

5、ument 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 document

6、s 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 Notification No part may be reproduced or utilized in any fo

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

8、 all media. European Telecommunications Standards Institute 2017. 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 Orga

9、nizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GR NGP 003 V1.1.1 (2017-03) 3 Contents Intellectual Property Rights 6g3Foreword . 6g3Modal verbs terminology 6g3Executive summary 6g3Introduction 7g31 Scope 8g32 References 8g32.1 Normati

10、ve references . 8g32.2 Informative references 8g33 Definitions and abbreviations . 10g33.1 Definitions 10g33.2 Abbreviations . 10g34 RINA (Recursive InterNetwork Architecture) . 12g34.1 Overview 12g34.1.0 Introduction to RINA 12g34.1.1 The DIF service definition 13g34.1.2 The nature of layers (DIFs)

11、 . 14g34.1.3 Internals of a DIF: only two protocols required 14g34.1.4 Naming and addressing . 15g34.1.5 Consistent QoS model across layers . 15g34.1.6 Consistent security model across layers 16g34.1.7 Network Management . 16g34.2 Data transfer: protocol, functions and procedures 17g34.2.0 General 1

12、7g34.2.1 DTP PDU Format . 17g34.2.2 DTCP PDU Formats . 18g34.2.3 Overview of data-transfer procedures . 18g34.3 Layer management: protocol, functions and procedures 19g34.3.1 Common layer management machinery . 19g34.3.2 Layer management functions: enrolment 20g34.3.3 Layer management functions: nam

13、espace management . 20g34.3.4 Layer management functions: flow allocation 21g34.3.5 Layer management functions: resource allocation 21g34.3.6 Layer management functions: routing 22g34.3.7 Layer management functions: security coordination 22g34.4 Support for mobility . 22g34.5 Support for security 23

14、g34.6 Addressing and scalability 24g34.7 Interworking and migration 24g34.8 Assessment against NGP key issues . 25g35 Flexilink . 26g35.1 Overview 26g35.1.1 Background . 26g35.1.2 Main differences from IP 27g35.1.3 Flows, and separation of control and forwarding 27g35.1.4 Services . 27g35.1.5 Choice

15、 of service for data transport 28g35.2 Packet formats 29g35.2.1 General 29g35.2.2 AV packets 29g35.2.3 IT packets 29g35.3 Control plane procedures 30g3ETSI ETSI GR NGP 003 V1.1.1 (2017-03) 4 5.3.1 Message format . 30g35.3.2 Identifiers 30g35.3.2.1 Equipment identifiers 30g35.3.2.2 Call, route, and f

16、low identifiers . 30g35.3.2.3 Addressing 30g35.3.3 Setting up routes . 31g35.3.3.1 Procedure for connection-oriented model . 31g35.3.3.2 Connectionless service 31g35.3.3.3 Additional information in FindRoute messages 31g35.3.4 Synchronization of AV flows . 31g35.3.4.1 Slots. 31g35.3.4.2 Frame alignm

17、ent . 32g35.4 Support for mobility . 32g35.5 Support for security 32g35.5.1 Authentication . 32g35.5.2 Denial of service . 32g35.6 Addressing and scalability 33g35.7 Interworking and migration 33g35.7.1 Definitions 33g35.7.2 Connecting islands via other technologies 33g35.7.3 Tunnelling other techno

18、logies across islands 34g35.7.4 Other gateway functions . 34g35.8 Assessment against NGP key issues . 35g36 Multi-access, Mobility-aware, Context-aware-Networking Protocol (M2CNP) . 37g36.1 Overview 37g36.2 System Architecture . 37g36.2.1 Introduction. 37g36.2.2 M2CNP Protocol Management Entities 38

19、g36.2.2.1 Access EndPoint . 38g36.2.2.2 Access Point 39g36.2.2.3 Packet Processing Entity . 39g36.2.2.4 Cluster Controller Functional Entity . 39g36.2.2.5 Cluster Member Functional Entity 40g36.2.2.6 Access Agent Functional Entity 40g36.2.2.7 Network Subscriber Location Database 40g36.2.2.8 Cluster

20、Content Routing Database 40g36.3 Protocol Stack 41g36.4 Access Agent Functionalities and Benefits 43g36.4.0 Preview . 43g36.4.1 User Plane Functionality . 43g36.4.1.0 General 43g36.4.1.1 Network Service Request Handling 43g36.4.1.1.0 Types of service . 43g36.4.1.1.1 HTTP Request Handling . 43g36.4.1

21、.1.2 Voice Request Handling 44g36.4.1.2 Context-Driven Intelligent Content Management . 44g36.4.2 Control Functionality 45g36.4.2.1 User Association . 45g36.4.2.2 User Authentication 45g36.4.2.3 Address Translation 45g36.4.2.4 Intra-Cluster Mobility . 45g36.4.2.5 Inter-Cluster Mobility . 45g36.5 Pro

22、tocol Field Structure/Addressing 45g36.6 Security 46g36.7 Routing . 47g36.8 Message Sets 47g36.8.0 General 47g36.8.1 Network Services 48g36.9 M2CNP assessment against criteria . 49g3Annex A: Assessment against NGP requirements. 52g3ETSI ETSI GR NGP 003 V1.1.1 (2017-03) 5 Annex B: Authors Essential,

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

24、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. Foreword This Group Report (GR) has been produced by ETSI Industry Specification Group (

25、ISG) Next Generation Protocols (NGP). Modal verbs terminology In the present document “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“

26、and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. Executive summary Three technologies are described in the present document. RINA embodies a theory which is informally known as the Inter-Process Communication (IPC) model. It is structured around a single type

27、of layer - called Distributed IPC Facility or DIF - that repeats as many times as needed. In RINA, all layers are distributed applications that provide the same service (communication flows between distributed applications) and have the same internal structure, divided into data transfer (delimiting

28、, addressing, sequencing, relaying, multiplexing, lifetime termination, error check, encryption), data transfer control (flow and retransmission control), and layer management (enrolment, routing, flow allocation, namespace management, resource allocation, security management). Flexilink is designed

29、 for implementation in 21stcentury digital systems, in which packet forwarding is implemented in hardware and memory is much more plentiful than when Internet Protocol was developed. The information needed to route packets is carried separately from the packets themselves; this reduces the size of t

30、he packet header by an order of magnitude, simplifies the forwarding hardware, and allows different addressing mechanisms to be used without changing the packet format. It supports ultra-low latency live streams; these are needed for some of the new services that 5G is to support, and also provide a

31、 better service for audio and video. They can also be used for file transfer, eliminating the need for the kind of empirical throughput testing that is a feature of TCP. M2CNP envisages a packet based routed protocol architecture with the ability to embed protocol control messaging to provide basic

32、protocol management functions for: security, context-awareness, transmission management, and mobility. Applications and/or services, running at access network connected devices, communicate using IPC interfaces towards the M2CNP communications network. Devices may be connected via one or more access

33、 technologies at a time and are capable of mobility from one access point or Temporary Access Points Group (for multiple access) to another. The M2CNP network consists of M2CNP Packet Processing Entities, which are M2CNP routing entities that are selectively enabled with various protocol management

34、capabilities of M2CNP and may be deployed in terms of scope in a similar manner to CE, PE, P scope routers as commonly understood in the legacy IP world. ETSI ETSI GR NGP 003 V1.1.1 (2017-03) 7 Introduction ETSI ISG NGP is tasked with reviewing networking technologies, architectures, and protocols f

35、or the next generation of communication systems. The present document describes some technologies of which ISG NGP is aware, which could be evaluated against the requirements listed in ETSI GS NGP 001 i.1 (Scenarios) and 3GPP TR 23.799 i.3. Ideally, ISG NGP would issue a Call for Technology and wait

36、 for responses before drafting the present document. However, new radio interfaces are now being developed for 5G, and if something other than TCP/IP is to be used with them the developers of the radio technology need to have an indication, early in the process, of the kind of shape the new protocol

37、s might have. Therefore, a first version of the present document is being produced covering technologies that have been researched by the current members of ISP NGP. It is intended that further versions will be produced, containing additional architectures. ETSI ETSI GR NGP 003 V1.1.1 (2017-03) 8 1

38、Scope The present document describes packet routing technologies that might be used in 5G radio networks and in the core of future mobile networks, and would also be suitable for use in the Internet. The description of each technology includes: overview of routing approach; key fields in user plane

39、packets; procedures for setting up routes, etc.; support for mobility; support for security; addressing, including scalability issues. 2 References 2.1 Normative references Normative references are not applicable in the present document. 2.2 Informative references References are either specific (ide

40、ntified 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

41、 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 ETSI GS NGP 001 (V1.1.1): “Next Gener

42、ation Protocol (NGP); Scenario Definitions“. i.2 ISO/IEC 62379-5-2:2014: “Common control interface for networked digital audio and video products - Part 5-2: Transmission over networks - Signalling“. i.3 3GPP TR 23.799: “Study on Architecture for Next Generation System“. i.4 J. Day: “Patterns in Net

43、work Architecture: A return to fundamentals“. Prentice Hall, 2008. i.5 J. Day, I. Matta, and K. Mattar. 2008: “Networking is IPC: a guiding principle to a better Internet“. In Proceedings of the 2008 ACM CoNEXT Conference (CoNEXT 08). i.6 J. Day, E. Grasa: “About layers: more or less“. NOTE: PSOC Tu

44、torial, available online at http:/pouzinsociety.org. i.7 J. Day: “How naming, addressing and routing are supposed to work“. NOTE: PSOC Tutorial, available online at http:/pouzinsociety.org. i.8 G. Gursun, I. Matta, and K. Mattar: “On the Performance and Robustness of Managing Reliable Transport Conn

45、ections“. In Proceedings of the 8thInternational Workshop on Protocols for Future, Large-Scale and Diverse Network Transports (PFLDNeT), Lancester, PA, November 2010. ETSI ETSI GR NGP 003 V1.1.1 (2017-03) 9 i.9 Boddapati, G.; Day, J.; Matta, I.; Chitkushev, L.: “Assessing the security of a clean-sla

46、te Internet architecture“. Network Protocols (ICNP), 2012 20thIEEE International Conference on. i.10 V. Maffione, F. Salvestrini, E. Grasa, L. Bergesio, M. Tarzan: “A Software Development Kit to exploit RINA programmability“. IEEE ICC 2016, Next Generation Networking and Internet Symposium. i.11 J.

47、Day, E. Grasa: “Mobility made simple“. NOTE: PSOC Tutorial, available online at http:/pouzinsociety.org. i.12 J. Day, E. Trouva, E. Grasa, P. Phelan, M.P. de Leon, S. Bunch, I. Matta, L.T. Chitkushev, L. Pouzin: “Bounding the router table size in an ISP network using RINA“. Network of the Future (NO

48、F), 2011. i.13 V. Ishakian, J. Akinwumi, F. Esposito, and I. Matta: “On supporting mobility and multihoming in recursive internet architectures“. Comput. Commun. 35, 13 (July 2012), 1561-1573. i.14 J. Small: “Threat analysis of Recursive InterNetwork Architecture Distributed IPC Facilities“. BU Tech

49、nical Report, 2011. i.15 E. Grasa, O. Rysavy, O. Lichtner, H. Asgari, J. Day, L. Chitkushev: “From protecting protocols to protecting layers: designing, implementing and experimenting with security policies in RINA“. IEEE ICC 2016, Communications and Information Systems Security Symposium. i.16 J. Small: “Patterns in Network Security: An analysis of architectural complexity in securing Recursive Inter-Network Architecture Networks“. Master Thesis, 2012. i.17 S. Len, J. Perell, D. Careglio, E. Grasa, D. Lopez, Pedro A. A