ETSI GS NGP 001 V1.2.1 (2017-05)

Next Generation Protocol (NGP); Scenario Definitions

RGS/NGP-001v121

General Information

• Status: Published
• Publication Date: 08-May-2017
• Technical Committee: NGP - Next Generation Protocols
• Current Stage: 12 - Completion
• Due Date: 20-Apr-2017
• Completion Date: 09-May-2017

Standards Content (Sample)

GROUP SPECIFICATION
Next Generation Protocols (NGP);
Scenario Definitions
2 ETSI GS NGP 001 V1.2.1 (2017-05)

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 2017.
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.2.1 (2017-05)
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 . 10
3.1 Definitions . 10
3.2 Abbreviations . 17
4 Overview . 20
5 Issues to be addressed by the Scenarios . 22
6 Model References . 24
6.0 Introduction . 24
6.1 LTE Mobile Network Model . 24
6.2 L2 and L3 VPN services . 26
6.2.0 Introduction. 26
6.2.1 MPLS/BGP Layer 3 Virtual Private Networks . 27
6.2.2 VPLS, Virtual Private Line Services and Ethernet-VPN . 28
6.3 All IP Core Network Model . 30
6.4 NFV Reference Model . 32
6.5 MEC Reference Model . 33
7 Referenced Use Cases . 33
8 Scenarios . 34
8.1 Addressing . 34
8.1.0 Introduction. 34
8.1.1 Model Architecture . 35
8.1.2 Scenario Description . 36
8.1.2.0 Introduction . 36
8.1.2.1 Scenarios for mobile communication . 36
8.1.2.2 Scenarios for multi-homing and load balancing . 37
8.1.3 Applicable Issues . 38
8.1.4 Applicable Use Cases . 38
8.1.4.1 Case 1: UE communicates with a fixed device; UE is moving within a same P-GW domain . 38
8.1.4.2 Case 2: UE communicates with a fixed device; UE is moving across different P-GW domain . 39
8.1.4.3 Case 3: UE communicates with a fixed device; UE is moving across heterogeneous access
network . 39
8.1.4.4 Case 4: UE communicates with another UE; UE is moving within a same P-GW domain . 40
8.1.4.5 Case 5: UE communicates with another UE; UE is moving across different P-GW domain. 40
8.1.4.6 Case 6: UE communicates with another UE; UE is moving across heterogeneous access network . 41
8.1.4.7 Case 7: Multi-homing host connected to different ISP for link protection or load balance . 41
8.1.4.8 Case 8: Customer network with multi-homing site connected to different ISP for link protection
or load balancing . 41
8.1.5 Scenario Targets . 42
8.2 Security . 43
8.2.1 Model Architecture/Protocol Stacks . 43
8.2.2 Scenario Description . 43
8.2.2.1 Scenario summary . 43
8.2.2.2 Security approach . 43
8.2.2.3 Description of new security challenges . 44
8.2.3 Applicable Issues . 44
8.2.4 Applicable Use Cases . 48
ETSI
4 ETSI GS NGP 001 V1.2.1 (2017-05)
8.2.5 Scenario Targets . 48
8.3 Mobility . 50
8.3.1 Model Architecture . 50
8.3.2 Scenario Description . 52
8.3.3 Applicable Issues . 53
8.3.4 Applicable Use Cases . 55
8.3.4.0 Introduction . 55
8.3.4.1 Case 1: Multi-Access, Session & Bearer connection, Same Macro . 55
8.3.4.2 Case 2: Multi-Access, Session & Bearer connection, with Macro HO . 55
8.3.4.3 Case 3: Single Access, Session & Bearer, Same Macro . 55
8.3.4.4 Case 4: Single Access, Multi-Session, Multi-Bearer, Same Macro . 55
8.3.4.5 Case 5: Fast, Single Access, Multi-Session, Multi-Bearer, with Macro HO . 56
8.3.4.6 Case 6: Fast, Multi-Access, Session & Bearer connection, with Macro HO . 56
8.3.4.7 Case 7: Fast, Multi-Access, Session & Bearer connection, with Macro HO . 56
8.3.5 Scenario Targets . 56
8.4 Multi-Access Support (including FMC) . 56
8.4.1 Model Architecture . 56
8.4.2 Scenarios . 57
8.4.3 Scenario Description . 58
8.4.4 Applicable Issues . 58
8.5 Context Awareness . 59
8.5.1 Model Architecture/Protocol Stacks . 59
8.5.2 Scenario Description . 60
8.5.3 Applicable Issues . 63
8.5.4 Applicable Use Cases (from Annex A). 64
8.5.5 Scenario Targets . 64
8.6 Performance Improvement & Content Enablement . 65
8.6.1 Model Architecture . 65
8.6.2 Scenario Descriptions . 67
8.6.2.0 Introduction . 67
8.6.2.1 Scenario #1 - Adaptive video streaming . 68
8.6.2.2 Scenario #2 - 8K Video Streaming . 68
8.6.2.3 Scenario #3 - Live Virtual Reality . 69
8.6.2.4 Scenario #4 - URLLC For Time-Critical IoT . 69
8.6.3 Issues with TCP Congestion Control . 69
8.6.3.1 An appraisal of Congestion Management . 69
8.6.3.2 An Introduction to Current TCP Congestion Mechanisms . 70
8.6.4 Applicable Issues and Recommendations . 71
8.6.5 Applicable Use Cases (from Annex A). 73
8.6.5.0 Introduction . 73
8.6.5.1 Case 1: New Transport Protocol . 73
8.6.5.2 Case 2: Use Case for Flexible Application Traffic Routing . 73
8.6.5.3 Case 3: In-Network Caching . 73
8.6.5.4 Case 4: Deterministic Network Reporting/Profiling . 73
8.6.6 Scenario Targets . 73
8.7 Network Virtualisation . 74
8.7.0 Introduction. 74
8.7.1 Model Architecture . 75
8.7.2 Scenario Description . 79
8.7.2.1 Scenario #1: Network Virtualisation in EPS . 79
8.7.2.2 Scenario #2: Virtualised RAN. 80
8.7.3 Applicable Issues . 81
8.7.4 Applicable Use Cases . 84
8.7.4.1 Case 1: Network Slicing . 84
8.7.4.2 Case 2: Network Slicing: With Simultaneous access to different instances of Virtualised core . 85
8.7.4.3 Case 3: MEC and Network Virtualisation . 85
8.7.4.4 Case 4: Cloud interconnect (Mobile/Fixed networks) . 86
8.7.4.5 Case 5: C-RAN Enhanced Computational Flexibility . 86
8.7.4.6 Case 6: Heterogeneity of RAT . 87
8.7.4.7 Case 7: Performance Enhancement of Low-power RRU . 87
8.7.5 Scenario Targets . 87
8.8 IoT Scenario . 89
ETSI
5 ETSI GS NGP 001 V1.2.1 (2017-05)
8.8.1 Model Architecture/Protocol Stacks . 89
8.8.2 Scenario Descriptions . 89
8.8.2.0 Introduction . 89
8.8.2.1 Active Assisted Living (AAL) . 90
8.8.2.2 Cooperation between factories and remote applications . 90
8.8.2.3 Smart glasses in industrial applications . 90
8.8.3 Applicable Issues . 90
8.8.4 Applicable Use Cases (from Annex A). 92
8.9 Energy Efficiency . 92
8.10 eCommerce. 93
8.11 Mobile Edge Computing (MEC) . 93
8.11.0 Introduction. 93
8.11.1 Model Architecture . 94
8.11.2 Applicable Issues and Recommendations . 95
8.11.3 Applicable Use Cases . 96
8.11.3.0 Introduction . 96
8.11.3.1 Case 1: Video Stream Analysis service . 96
8.11.3.2 Case 2: Augmented and Virtual Reality service . 97
8.11.3.3 Case 3: Assistance for intensive computation service . 97
8.11.3.4 Case 4: IoT Gateway service . 97
8.11.3.5 Use Case 5: Connected Vehicles service scenario . 98
8.11.4 Scenario Targets . 99
8.12 Mission Critical Services: PSC and PUC . 99
8.12.0 Introduction. 99
8.13 Drones, Autonomous and Connected Vehicles . 99
8.13.0 Introduction. 99
8.13.1 Model . 99
8.13.2 Scenarios . 100
8.13.3 Applicable Issues and Recommendations . 101
8.13.4 Applicable Use Cases . 103
8.13.4.0 Introduction . 103
8.13.4.1 Hazardous operations . 103
8.13.4.2 Driverless vehicles . 104
8.13.4.3 Automated Convoys ('platooning') . 104
8.13.4.4 Connected vehicles. 104
8.14 URLLC: Ultra-Reliable and Low Latency Communications . 104
8.14.0 Introduction. 104
8.14.1 Model architecture . 105
8.14.2 Scenario description . 106
8.14.2.0 Scenarios Introduction . 106
8.14.2.1 Handover interruption caused by UE's mobility . 106
8.14.2.2 Interruption Latency caused by mobility of application . 107
8.14.2.3 E2E latency enlarged by Indeterminate processing delay in network nodes . 107
8.14.2.4 Conflict between high reliability and low latency under wireless packet loss . 108
8.14.3 Applicable Issues and Recommendations . 108
8.14.4 Use cases . 108
8.13.4.1 Case 1 ：Local UAV Collaboration . 108
8.14.4.2 Case 2 ：Industrial Factory Automation. 109
8.14.4.3 Case 3 ：V2X . 109
8.14.4.4 Scenario Targets . 109
Annex A (informative): Use Cases & Parameterization . 110
Annex B (informative): Authors & contributors . 125
History . 126

ETSI
6 ETSI GS NGP 001 V1.2.1 (2017-05)
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.2.1 (2017-05)
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.2.1 (2017-05)
[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".
[27] ETSI TS 123 401: "LTE; General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access (3GPP TS 23.401 Release 13)".
rd
[28] 3GPP TS 22.261: "3 Generation Partnership Project; Technical Specification Group Services and
System Aspects; Service requirements for the 5G system; Stage 1 (Release 15)".
[29] ETSI TS 122 280: "LTE; Mission Critical Services Common Requirements (3GPP TS 22.280
Release 14)".
[30] Society of Automotive Engineers, J3016.
NOTE: This reference is available at http://standards.sae.org/j3016_201401/.
[31] IETF RFC 3246: "An Expedited Forwarding PHB (Per-Hop Behavior)".
rd
[32] 3GPP TS 23.501: "3 Generation Partnership Project; Technical Specification Group Services and
System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)".
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.
rd
[i.1] 3GPP TR 22.891: "3 Generation Partnership Project; Technical Specification Group Services and
System Aspects; Feasibility Study on New Services and Markets Technology Enablers; Stage 1"
(SMARTER).
TM
NOTE: 3GPP specifications are available at http://www.3gpp.org/specifications/specifications.
ETSI
9 ETSI GS NGP 001 V1.2.1 (2017-05)
rd
[i.2] 3GPP TR 23.799: "3 Generation Partnership Project; Technical Specification Group Services and
System Aspects; 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.
[i.9] "Elements of the Topology of Plane Sets of Points", Newman, M, 1964.
[i.10] Stallings, William; "High-Speed Networks and Internets", 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] Digital Equipment Corporation Technical Report No. DEC-TR-510: "Congestion Avoidance in
Computer Networks with A Connectionless Network Layer: Part IV: A Selective Binary Feedback
Scheme for General Topologies", August 1987, 43 pp., K. Ramakrishnan and Raj Jain.
[i.14] Void.
[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".
rd
[i.17] 3GPP TR 23.863: "3 Generation Partnership Project; Technical Specification Group Services and
System Aspects; Support of Short Message Service (SMS) in IP Multimedia Subsystem (IMS)
without Mobile Station International ISDN Number (MSISDN); Stage 2".
rd
[i.18] 3GPP TR 22.864: "3 Generation Partnership Project; Technical Specification Group Services and
System Aspects; Feasibility Study on New Services and Markets Technology Enablers - Network
Operation; Stage 1".
[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.
ETSI
10 ETSI GS NGP 001 V1.2.1 (2017-05)
[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".
[i.28] 3GPP TR 38.801: "Study on New Radio Access Technology: Radio Access Architecture and
Interfaces".
[i.29] 3GPP TR 36.881: "Study on latency reduction techniques for LTE".
[i.30] Ericsson Research AB, "Service Mobility in Mobile Networks", 2015 IEEE 8th International
Conference on Cloud Computing .
[i.31] Nokia: "W01-Third Workshop on 5G Architecture (5GArch 2016) ",Mobility Management
Enhancements for 5G Low Latency Services.
[i.32] K. De Schepper, I. Tsang, Bell Labs, B. Briscoe, Ed., "Identifying Modified Explicit Congestion
Notification (ECN) Semantics for Ultra-Low Queuing Delay draft-briscoe-tsvwg-ecn-l4s-id-00",
Simula Research Lab.
[i.33] Void.
[i.34] 3GPP TR 22.862: "Feasibility Study on New Services and Markets Technology Enablers for
Critical Communications; Stage 1" (Release 14).
[i.35] National Highway Traffic Safety Administration's "Preliminary statement of policy concerning
automated vehicles" (2013).
NOTE: This reference is available at
http://www.nhtsa.gov/staticfiles/rulemaking/pdf/Automated_Vehicles_Policy.pdf.
[i.36] 5GPPP "5G Automotive Vision" white paper.
NOTE: 5GPPP specifications are available at: https://5g-ppp.eu/white-papers/.
[i.37] 3GPP TR 22.886: "Study on enhancement of 3GPP Support for 5G V2X Services (Release 15)".
[i.38] SAE Mobulus: "Taxonomy and Definitions for Terms Related to On-Road Motor Vehicle
Automated Driving Systems".
NOTE: This reference is available at http://standards.sae.org/j3016_201401/.
[i.39] Driverless Future.
NOTE: Available at http://www.driverless-future.com/?page_id=774#ethical-judgements.
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] and the following 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
11 ETSI GS NGP 001 V1.2.1 (2017-05)
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
NOTE: 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].
autonomous: entity capable of piloting itself based on sensory input and pre-defined behaviours, including collision
avoidance, speed limits and geographical constraints
NOTE 1: Used in the context of communications pertaining to an autonomous drone or vehicle in the present
document.
NOTE 2: However, a remote piloting capability may be provided via a network to which the vehicle is able to
communicate with.
autonomous drone: autonomous vehicle with no human operator on-board
NOTE: The distinction between a 'drone' and an 'autonomous drone' is that in the case of an 'autonomnous drone',
the vehicle is piloted through on-board sensor processing, and optionally, and less frequently remote
control 'managed by' a human operator. Where: the term 'managed by' indicates that the human operator
may be actively monitoring the vehicle's progress, and taking control manually on an event triggered
basis, as necessary; or delegating the remote control to a computing process.
autonomous vehicle: vehicle capable of piloting itself, that also has a human operator on-board
NOTE 1: The distinction between an 'autonomous vehicle' and an 'autonomous drone' is the presence of a human
operator in the vehicle.
NOTE 2: The 'autonomouse vehicle' is piloted through a combination of on-vehicle sensor readings, which are
processed to determine action, and optional interjection from a human operator. An example of this kind
of situation is when there is a 'self-driving car' with a human passenger on-board who is capable of
piloting the car.
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].
ETSI
12 ETSI GS NGP 001 V1.2.1 (2017-05)
centralized mobility management: Makes use of centrally deployed mobility anchors.
NOTE Please see IETF RFC 7333 [13].
compound connection: connection that includes logical connectivity to more than one access network at a time
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 (o
...