1、 ETSI GS NGP 007 V1.1.1 (2017-05) Next Generation Protocols (NGP); NGP Reference Model 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 ISG.
2、 It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS NGP 007 V1.1.1 (2017-05)2 Reference DGS/NGP-007 Keywords architecture, model, protocol ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 9
3、3 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 versions and/
4、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 is the print
5、 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 available at
6、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 by any means
7、, 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. Europe
8、an 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 Organizational Partner
9、s. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS NGP 007 V1.1.1 (2017-05)3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normati
10、ve references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 NGP Reference Model . 6g34.1 Introduction 6g34.2 Model Components 6g34.3 Protocol Model . 8g34.3.1 Identification . 8g34.3.2 Protocol Layers . 8g34.3.3 Addressing 9g34.4
11、Example Cases using the NGP Reference Model . 9g34.4.1 Introduction. 9g34.4.2 Case(Single Network Equipment, Physical Network Connectivity). 9g34.4.3 Case(Network Equipment, Protocol Connectivity) . 10g34.4.3.1 Protocol Connectivity Introduction . 10g34.4.3.2 Virtual Connection 11g34.4.3.3 Flow 13g3
12、4.4.3.4 Connecting Protocols of Different Types 13g34.4.4 Case(Mobile Device to Access Point) 13g34.4.5 Case(TCP/IPv4/v6 representation) . 16g3Annex A (informative): Authors Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Sec
13、retariat. 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
14、 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 document “shall“, “shall not“,
15、“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 citatio
16、n. ETSI ETSI GS NGP 007 V1.1.1 (2017-05)5 1 Scope The present document defines the NGP Reference Model for protocols and protocol architectures. The model provides a common reference that is to be used to specify and inform about enhancements to existing protocols and new protocol designs, across th
17、e scope of both NGP contributions and approved documented output. 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-specifi
18、c 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
19、 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 NGP 001: “Next Generation Protocol (NGP); Scenario Definitions“. 2 ISO/IEC 7498-1:1994: “Information technology - Open
20、Systems Interconnection - Basic Reference Model: The Basic Model“. 3 IEEE 802.3TM: “IEEE Standard for Ethernet“. 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 ci
21、ted 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 docum
22、ents 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 TR 121 905: “Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Vocabulary for 3GPP Specifi
23、cations (3GPP TR 21.905)“. i.2 3GPP TR 23.799: “Study on Architecture for Next Generation System“ (NexGen). 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TR 121 905 i.1, 3GPP TR 23.799 i.2, ETSI GS NGP 001 1, ISO/IEC
24、 7498-1 2 and the following apply: application protocol: entity that resides inside an application that specifies and handles the protocol type to which it is communicating ETSI ETSI GS NGP 007 V1.1.1 (2017-05)6 3.2 Abbreviations For the purposes of the present document, the abbreviations given in E
25、TSI TR 121 905 i.1 and the following apply: NEt( ) Network Equipment NEy( ) Network Entity PoA Point of Attachment 4 NGP Reference Model 4.1 Introduction The NGP Reference Model is a generic protocol model that should be used to describe proposed NGP protocols and protocol architectures. 4.2 Model C
26、omponents The NGP Reference Model includes the following component parts, as illustrated in Table 1. Table 1: Model Components Model Component Description Graphical Description Illustration Network Equipment A logical collection of compute entities. The Network Equipment is represented as a rounded
27、corner rectangular object, with grey fill and a dotted black outline. The Network Equipment should be named with a text label and if there are more than one of these equipments in the illustration then it should include a numeric reference too. Compute Entity An entity that can support one or more N
28、etwork Entities. The Compute Entity is represented as a square corner rectangular object, with coloured fill and a dotted solid black outline. The entity should be named with a text label and if there are more than one of these entities in the illustration then it should include a numeric reference
29、too. Network Entity An entity that represents one or more network functions and includes protocols with which it communicates to other protocol peers at other Network Entities. Addresses can be carried in protocols, but are assigned to network entities. Addresses are unambiguous within a layer. (als
30、o known as a Network Function in a virtualised 3GPP environment.) The Network Entity is represented as a rounded corner rectangular object, with coloured fill. The Network Entity has a dotted solid black outline. The entity should be named with a text label and a reference to a valid address. Layer
31、A collection of two or more network entities that share state using one or more protocols. Where: Network Entity is a NEy as defined in the present document NGP Reference Protocol Model definition. Oblong dotted green outline encompassing the protocol scope of the layer. ETSI ETSI GS NGP 007 V1.1.1
32、(2017-05)7 Model Component Description Graphical Description Illustration Protocol Node The container of protocol instances within a network entity, which interpret and operate on the header of a particular protocol type. If the header is empty then there are other cases that may operate as follows:
33、 i) It is assumed that there is either a default local port-id connected that this entity automatically passes the packet to. ii) There is only one port-id and application connected for the protocol node to pass per flow. iii) The packet is passed to a particular port-id by some other aspect of the
34、communication such as time or frequency. Represented as a zero fill circle object with a green coloured solid outline. The text label should include an abbreviation of the name of the protocol. It contains zero or more protocol instances inside. Protocol Instance An instantiation of a protocol node
35、(an individual protocol machine). One end of a Connection operating within a Protocol Node and handling its communications state. Identified by a CEPI, unambiguous within the scope of the network-entity. For an NGP compliant protocol there is a one to one mapping between a Port-Id and a Protocol Ins
36、tance. Represented as a solid fill circle object with a green coloured dashed outline The text label should include the CEPI. Port The binding between an instance of an application or an instance of a protocol and an instance of this protocol. A Port is identified by a Port-ID unambiguous within the
37、 scope of the network-entity. An application or (N+1)-network-entity can have one or more Port-IDs. See note. Represented as a zero fill circle object with a purple coloured solid outline. The text label should include the Port-ID. Application An entity that performs one or more functions and connec
38、ts to a protocol node via a port. An application may be i) performing part of the tasks of a network entity and therefore be part of it or ii) managing the network entity (configuration, monitoring) or iii) just using the communication services provided by a network entity via a port-id. Represented
39、 as a zero fill circle object with a turquoise coloured solid outline. The text label should include the Application Name. User An entity (such as a human) that uses an application. Represented as a zero fill circle object with a cyan coloured solid outline. ETSI ETSI GS NGP 007 V1.1.1 (2017-05)8 Mo
40、del Component Description Graphical Description Illustration Point of Attachment (PoA) A Port that binds this protocol to a physical interface. A PoA is identified by a Port-ID . Represented as a zero fill circle object with a purple coloured solid outline. The text label should include the Port-ID.
41、 Each PoA has a text label as follows: i) P for Point of Attachment. ii) A letter to indicate which interface technology; this and the outline colour should be as below: - Electrical: e, red. - Optical: o, orange. - LTE (Radio): L, black. - Wi-FiTM(Radio): W, purple. - 5G new radio: 5, green. iii) T
42、he Port-ID in brackets. Flow An instance of a communications service provided by a layer to an application or protocol node. A port-id locally identifies a specific flow within a Network Equipment. A dotted line between Port-IDs. Virtual Connection The shared state between two data transfer Protocol
43、 Instances that supports a flow. Identified by a connection-id (CID) unambiguous within the scope of the communicating network-entities. It is generally formed by concatenating the CEP-ids associated with the communicating protocol-instances. A dashed line between Protocol Instances. Physical Connec
44、tion A physical connection between two PoA. A solid line between PoA of colour matching that of the PoA type. Internal software communication Illustration of intra-NEy communication between model parts. NOTE: Some legacy protocols enable multiple applications to be connected to the same Port via mul
45、tiple local bindings. In this case: - NGP Port (bound to single App(x) instance and identified by NGP Port-ID) = Legacy protocol Port + Local Binding(s). - In this manner managed application multiplexing on to a single NGP Port is able to be modelled in the NGP reference model. 4.3 Protocol Model 4.
46、3.1 Identification Each component shall have an identifier which identifies it uniquely within a defined scope. In the case of a component that is contained within another component, the scope may be the containing component. 4.3.2 Protocol Layers Multiple Network-Entities may be used to model a lay
47、ered architecture. ETSI ETSI GS NGP 007 V1.1.1 (2017-05)9 4.3.3 Addressing Each Network-Entity has an address that is distinct for the scope of the layer. 4.4 Example Cases using the NGP Reference Model 4.4.1 Introduction This clause introduces common cases that occur in communications systems. 4.4.
48、2 Case(Single Network Equipment, Physical Network Connectivity) The basic NGP protocol model structure is illustrated in Figure 1. Figure 1: Single Network Equipment, Physical Network Connectivity Figure 1 introduces the basics of the generic NGP protocol reference model, by showing how it represent
49、s two physically separate Network Equipment instances or NEt( )s. Several different application options are illustrated in Figure 1, as follows: App(a) is a local function that is part of the NEy(1) that manages protocol node P(1) e.g. 3GPP CM or PM. App(b) is a communicating function in NEy(1) that uses P(1) to communicate with another peer. E.g. a mobility manager in a cellular core NEy. App(c) is an application that uses NEy(1) to communicate via its implementation of P(1) with another peer. E.g. a browser. Inside each physical Network
