ETSI GS NGP 001 V1.1.1 (2016-10)

Next Generation Protocol (NGP); Scenario Definitions

DGS/NGP-001

General Information

• Status: Published
• Publication Date: 04-Oct-2016
• Technical Committee: NGP - Next Generation Protocols
• Current Stage: 12 - Completion
• Due Date: 14-Oct-2016
• Completion Date: 05-Oct-2016

Standards Content (Sample)

GROUP SPECIFICATION
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 ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GS NGP 001 V1.1.1 (2016-10)

Reference
DGS/NGP-001
Keywords
core network, cyber security, IoT, mobility,
network, QoE, reliability, security, service,
use case
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone] Fax: [phone]

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:
http://www.etsi.org/standards-search
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 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 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 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.

© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered 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
3 ETSI GS NGP 001 V1.1.1 (2016-10)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 15
4 Overview . 18
5 Issues to be addressed by the Scenarios . 19
6 Model References . 21
6.0 Introduction . 21
6.1 LTE Mobile Network Model . 21
6.2 L2 and L3 VPN services . 24
6.2.0 Introduction. 24
6.2.1 MPLS/BGP Layer 3 Virtual Private Networks . 24
6.2.2 VPLS, Virtual Private Line Services and Ethernet-VPN. . 25
6.3 All IP Core Network Model . 27
6.4 NFV Reference Model . 29
6.5 MEC Reference Model . 30
7 Referenced Use Cases . 31
8 Scenarios . 32
8.1 Addressing . 32
8.1.0 Introduction. 32
8.1.1 Model Architecture . 33
8.1.2 Scenario Description . 34
8.1.2.0 Introduction . 34
8.1.2.1 Scenarios for mobile communication . 34
8.1.2.2 Scenarios for multi-homing and load balancing . 35
8.1.3 Applicable Issues . 36
8.1.4 Applicable Use Cases . 36
8.1.4.1 Case 1: UE communicates with a fixed device; UE is moving within a same P-GW domain . 36
8.1.4.2 Case 2: UE communicates with a fixed device; UE is moving across different P-GW domain . 37
8.1.4.3 Case 3: UE communicates with a fixed device; UE is moving across heterogeneous access
network . 37
8.1.4.4 Case 4: UE communicates with another UE; UE is moving within a same P-GW domain . 38
8.1.4.5 Case 5: UE communicates with another UE; UE is moving across different P-GW domain. 38
8.1.4.6 Case 6: UE communicates with another UE; UE is moving across heterogeneous access network . 39
8.1.4.7 Case 7: Multi-homing host connected to different ISP for link protection or load balance . 39
8.1.4.8 Case 8: Customer network with multi-homing site connected to different ISP for link protection
or load balancing . 39
8.1.5 Scenario Targets . 40
8.2 Security . 41
8.2.1 Model Architecture/Protocol Stacks . 41
8.2.2 Scenario Description . 41
8.2.2.1 Scenario summary . 41
8.2.2.2 Security approach . 41
8.2.2.3 Description of new security challenges . 42
8.2.3 Applicable Issues . 42
8.2.4 Applicable Use Cases . 46
ETSI
4 ETSI GS NGP 001 V1.1.1 (2016-10)
8.2.5 Scenario Targets . 46
8.3 Mobility . 48
8.3.1 Model Architecture . 48
8.3.2 Scenario Description . 50
8.3.3 Applicable Issues . 51
8.3.4 Applicable Use Cases . 53
8.3.4.0 Introduction . 53
8.3.4.1 Case 1: Multi-Access, Session & Bearer connection, Same Macro . 53
8.3.4.2 Case 2: Multi-Access, Session & Bearer connection, with Macro HO . 53
8.3.4.3 Case 3: Single Access, Session & Bearer, Same Macro . 53
8.3.4.4 Case 4: Single Access, Multi-Session, Multi-Bearer, Same Macro . 53
8.3.4.5 Case 5: Fast, Single Access, Multi-Session, Multi-Bearer, with Macro HO . 54
8.3.4.6 Case 6: Fast, Multi-Access, Session & Bearer connection, with Macro HO . 54
8.3.4.7 Case 7: Fast, Multi-Access, Session & Bearer connection, with Macro HO . 54
8.3.5 Scenario Targets . 54
8.4 Multi-Access Support (including FMC) . 54
8.4.1 Model Architecture . 54
8.4.2 Scenarios . 55
8.4.3 Scenario Description . 56
8.4.4 Applicable Issues . 56
8.5 Context Awareness . 57
8.5.1 Model Architecture/ Protocol Stacks . 57
8.5.2 Scenario Description . 58
8.5.3 Applicable Issues . 61
8.5.4 Applicable Use Cases (from Annex A). 62
8.5.5 Scenario Targets . 62
8.6 Performance Improvement & Content Enablement . 63
8.6.1 Model Architecture . 63
8.6.2 Scenario Descriptions . 65
8.6.2.0 Introduction . 65
8.6.2.1 Scenario #1 - Adaptive video streaming . 66
8.6.2.2 Scenario #2 - 8K Video Streaming . 66
8.6.2.3 Scenario #3 - Live Virtual Reality . 67
8.6.2.4 Scenario #4 - URLLC For Time-Critical IoT . 67
8.6.3 Issues with TCP Congestion Control . 67
8.6.3.1 An appraisal of Congestion Management . 67
8.6.3.2 An Introduction to Current TCP Congestion Mechanisms . 68
8.6.4 Applicable Issues and Recommendations . 69
8.6.5 Applicable Use Cases (from Annex A). 71
8.6.5.0 Introduction . 71
8.6.5.1 Case 1: New Transport Protocol . 71
8.6.5.2 Case 2: Use Case for Flexible Application Traffic Routing . 71
8.6.5.3 Case 3: In-Network Caching . 71
8.6.5.4 Case 4: Deterministic Network Reporting/ Profiling . 71
8.6.6 Scenario Targets . 71
8.7 Network Virtualisation . 72
8.7.0 Introduction. 72
8.7.1 Model Architecture . 73
8.7.2 Scenario Description . 77
8.7.2.1 Scenario #1: Network Virtualisation in EPS . 77
8.7.2.2 Scenario #2: Virtualised RAN. 78
8.7.3 Applicable Issues . 79
8.7.4 Applicable Use Cases . 81
8.7.4.1 Case 1: Network Slicing . 81
8.7.4.2 Case 2: Network Slicing: With Simultaneous access to different instances of Virtualised core . 83
8.7.4.3 Case 3: MEC and Network Virtualisation . 83
8.7.4.4 Case 4: Cloud interconnect (Mobile/Fixed networks) . 83
8.7.4.5 Case 5: C-RAN Enhanced Computational Flexibility . 84
8.7.4.6 Case 6: Heterogeneity of RAT . 85
8.7.4.7 Case 7: Performance Enhancement of Low-power RRU . 85
8.7.5 Scenario Targets . 85
8.8 IoT Scenario . 87
ETSI
5 ETSI GS NGP 001 V1.1.1 (2016-10)
8.8.1 Model Architecture/ Protocol Stacks . 87
8.8.2 Scenario Descriptions . 87
8.8.2.0 Introduction . 87
8.8.2.1 Active Assisted Living (AAL) . 88
8.8.2.2 Cooperation between factories and remote applications . 88
8.8.2.3 Smart glasses in industrial applications . 88
8.8.3 Applicable Issues . 88
8.8.4 Applicable Use Cases (from Annex A). 90
8.9 Energy Efficiency . 90
8.10 eCommerce. 91
8.11 Mobile Edge Computing (MEC) . 91
8.11.0 Introduction. 91
8.11.1 Model Architecture . 91
8.11.2 Applicable Issues and Recommendations . 93
8.11.3 Applicable Use Cases . 93
8.11.3.0 Introduction . 93
8.11.3.1 Case 1: Video Stream Analysis service . 94
8.11.3.2 Case 2: Augmented and Virtual Reality service . 94
8.11.3.3 Case 3: Assistance for intensive computation service . 95
8.11.3.4 Case 4: IoT Gateway service . 95
8.11.3.5 Use Case 5: Connected Vehicles service scenario . 95
8.11.4 Scenario Targets . 96
Annex A (informative): Use Cases & Parameterization . 97
Annex B (informative): Authors & contributors . 112
History . 113

ETSI
6 ETSI GS NGP 001 V1.1.1 (2016-10)
Intellectual Property Rights
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 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.
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", "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
7 ETSI GS NGP 001 V1.1.1 (2016-10)
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 (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] 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: " 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 Virtualisation (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] 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): "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
8 ETSI GS NGP 001 V1.1.1 (2016-10)
[18] ETSI GS NFV-SEC 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 Computing (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 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 (SON); 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 Bridges".
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.
[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" (NexGen).
[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-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
9 ETSI GS NGP 001 V1.1.1 (2016-10)
[i.9] "Elements 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/papers/.
[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 Avoidance 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 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 Short 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 TCP's Fast Recovery Algorithm".
[i.20] IETF RFC 2018: "TCP Selective Acknowledgment 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 Backbone 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/.
[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.
access 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
10 ETSI GS NGP 001 V1.1.1 (2016-10)
address: 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 application 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/ 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 base station entity and the cellular core network or Non-Access Stratum
binding a name to an object: function, Fn(M , that defines the mapping of elements of NS(namespace) to elements
NS)
of M(object)
NOTE 1: The result of this function is called a binding. e.g. In LISP, the binding operation is called mapping.
NOTE 2: For example is the mapping of ID1="identity1" to RLOC1="an ip address or any other
form of addressing".
care-of-address: IP address associated with a mobile node while visiting a foreign link; the subnet prefix of this IP
address is a foreign subnet prefix
NOTE: A packet addressed to the mobile node which arrives at the mobile node's home network when the mobile
node is away from home and has registered a Care-of Address will be forwarded to that address by the
Home Agent in the home network see IETF RFC 3753 [12].
centralized mobility management: makes use of centrally deployed mobility anchors
NOTE Please see IETF RFC 7333 [13].
congestion avoidance: mechanism that operates the network at the knee of the congestion or response time (or delay)
curve to optimize the trade-off between response time and throughput
congestion 'cliff': congestion point of the response time (or delay) curve at which a session collapses
congestion control: Addresses the "social" problem of having various logical links in the network cooperate in order to
avoid and/ or recover from congestion of the intermediate nodes that they share. This scheme operates by constantly
testing the cliff of congestion collapse which implicitly introduces packet loss in order to seek to reduce the load during
periods of congestion, so that the network can recover to an uncongested state.
congestion 'knee': congestion point of the response time (or delay) curve at which as session begins to notably
deteriorate
compound connection: connection that includes logical connectivity to more than one access network at a time
connection: shared state between EFCPM-instances, see ISO/IEC 7498-1 [6]
C-RAN: cloud RAN where the physical radio part of a base station termed the RRU has been remoted from its base
band equipment termed the BBU via 'fronthaul' transmission and the BBU part connects the composite RAN equipment
to the cellular core via 'backhaul'
NOTE: Often multiple RRU communicate with a single BBU to effect RAN optimization at the BBU level across
a number of Cells provided by the RRH.
ETSI
11 ETSI GS NGP 001 V1.1.1 (2016-10)
dual connectivity: mechanism whereby a device can access multiple cells/access points at the same time to bond
multiple single cell/access point capabilities together to increase available throughput
data transfer protocol:, machine dtp(m): half of the EFCP that performs tightly bound mechanisms, such as ordering,
and fragmentation/reassembly
NOTE: One instantiation is created for each flow allocated, see ISO/IEC 7498-1 [6].
Data Transfer Control Protocol, Machine DTCP(M): half of the EFCP that performs loosely bound (feedback)
mechanisms, such as retransmission and flow control
NOTE: This protocol maintains state, which is discarded after long periods of no traffic (2MPL). One
instantiation is created for each flow requiring either flow control or retransmission control. See
ISO/IEC 7498-1 [6].
distance vector: characteristic of some routing protocols in which, for each desired destination, a node maintains
information about the distance to that destination, and a vector (next hop) towards that destination
NOTE: See IETF RFC 3753 [12].
distributed application: collection of cooperating APs that exchange information using IPC and maintain shared state
distributed mobility management: not centralized, so that traffic does not need to traverse centrally deployed mobility
anchors far from the optimal route
NOTE: See IETF RFC 7333 [13].
D-RAN: traditional RAN where the physical radio part of a base station and its base band equipment are co-located at
the base station cell site and connected to the rest of the cellular network with 'backhaul' transmission
EID: Endpoint ID In LISP is the binding operation and is called a mapping.
NOTE: For example is the mapping of ID1="identity1" to RLOC1="an IP address or any other
form of addressing", see IETF RFC 6830 [4], [14] and [15].
Error and Flow Control Protocol (EFCP): data transfer protocol required to maintain an instance of IPC within a
layer characterized by modifying state internal to the protocol
NOTE: The functions of this protocol may ensure reliability, order, and flow control as required.
Error and Flow Control Protocol Machine (EFCPM): task that instantiates an instance of the EFCP for a single flow
or connection
NOTE: An EFCPM consists of two state machines loosely coupled through a single state vector: one that
performs the tightly bound mechanisms, referred to as the Data Transfer PM; and the other that performs
the loosely coupled mechanisms, referred to as the Data Transfer Control PM, see ISO/IEC 7498-1 [6].
flooding: process of delivering data or control messages to every node within the network under consideration
NOTE: See IETF RFC 3753 [12].
flow control: Flow Control is often referred to as ETE Flow control, see definition in ETSI TR 121 905 [i.3].
front-haul: transmission between separated component parts of a traditional base station when it has been functionally
split into at least 2 parts and those parts are remote from each other
function chaining: virtual inter-connection of VNFs to form a NS
graph: ordered pair G = (V, E) comprising a set V of vertices or nodes or points together with a set E of edges or arcs
or lines, which are 2-element subsets of V
NOTE: i.e. an edge is related with two vertices, and the relation is represented as an unordered pair of the vertices
with respect to the particular edge).
grouping service slice: service chain built to render support for a virtual service offering according to a defined
subscriber grouping
ETSI
12 ETSI GS NGP 001 V1.1.1 (2016-10)
NOTE: See 3GPP TR 23.799 [i.2] for further information on the 3GPP ongoing definition of Network Slicing.
handover: process by which an active Mobile Node (in the Active State) changes its point of attachment to the
network, or when such a change is attempted
NOTE: The access network may provide features to minimize the interruption to sessions in progress. This
procedure is also called hand-off. IETF RFC 3753 [12].
home address: IP address assigned to a mobile node, used as the permanent address of the mobile node
NOTE: This address is within the mobile node's home link. Standard IP routing mechanisms will deliver packets
destined for a mobile node's home address to its home link. IETF RFC 3753 [12].
Hybrid RAN (H-RAN): optimized form of RAN using concepts from both C-RAN and D-RAN
identifier: series of digits, characters and symbols or any other form of data used to identify subscriber(s), user(s),
network element(s), function(s), network entity(ies) providing services/applications, or other entities (e.g. physical or
logical objects)
NOTE See Recommendation ITU-T Y.2720 [3].
identity: information about an entity that is sufficient to identify that entity in a particular context
NOTE: See Recommendation ITU-T Y.2720 [3].
Instance Identifier (ID): instance ID is used to define extended forms of EID as a multi-tuple value
NOTE: Where (IID, EID) is one example of an extended EID, see IETF RFC 6830 [4].
IoT(mobileS): mobile capable IoT device with one or more sensors
IoT(mobileSA): mobile capable IoT device with one or more sensors and one or more actuators
IoT(staticS): static capable IoT device with one or more sensors
IoT(staticS): static capable IoT device with one or more sensors and one or more actuators
(IP) address: shorthand for Internet Protocol address
NOTE: See IETF RFC 760 [5].
IPC-process: AP that is a member of (N)-layer and implements locally the functionality to support IPC using multiple
subtasks
NOTE: Specific for a layer (N).
link: communication facility or physical medium that can sustain data communications between multiple network
nodes, such as an Ethernet simple or bridged)
NOTE: A link is the layer immediately below IP. In a layered network stack model, the Link Layer (Layer 2) is
normally below the Network (IP) Layer (Layer 3), and above the Physical Layer (Layer 1), see IETF
RFC 3753 [12]
local broadcast: delivery of data to every node within range of the transmitter
NOTE: See IETF RFC 3753 [12].
(2D Geographic) Location: specifies the physical location of a 2D point on the earth using two coordinates: i) latitude
and ii) longitude
NOTE: As referenced in World Geodetic System 1984 [7].
(3D Geographic) Location: 2D location specified with an accompanying altitude expressed as metres above sea level
or (ASL)
ETSI
13 ETSI GS NGP 001 V1.1.1 (2016-10)
mobility management: solutions that lie at the centre of the wireless Internet and enable mobile devices to partake in
IP networks anytime and anywhere
NOTE: See IETF Charter of IETF DMM WG [i.26]. Includes the setup, maintenance(handover) and release of
various physical radio resources when the mobility management is operated with at least one end of a
group of communicating peers are attached to the network via an air interface.
(N)-address: identifier that is a synonym for the IPC-Process-Instance, which is a member of a (N)-layer.
NOTE 1: An address is only unambiguous within the (N)-layer (and assigned by the (N)-layer).
NOTE 2 This identifier may be assigned to facilitate the operation of the (N)-layer, i.e. location-dependence for
routing, see ISO/IEC 7498-1 [6].
(N)-API-primitive: library or system call for a (N)-layer used
...