Index
Note: Page numbers followed by “f” and “t” refer to figures and tables, respectively.
A
Abstract Syntax Notation One (ASN.1),
92
Access to interrupt controller (APIC),
172
Advanced Vector eXtensions (AVX),
194
Application
Architectural diagram reference points, interpretations from,
134
B
Baseband radio-processing unit (BBU),
61
Birds of Feather (BoF) meeting,
77
Branching service chain,
20,
21f
Broadband network gateway (BNG),
25,
25f
Broadband Residential Access Server (BRAS),
37
Brownfield partnership, reimagining OSS/BSS,
131–132
“Brownfield” of dreams,
44–45
Business Support Systems (BSS),
55
interpretations from architectural diagram reference points,
134
reimagining OSS/BSS—Brownfield partnership,
131–132
reimagining OSS—opportunities in SA,
132–133
C
Capital expense (CAPEX),
2,
4
Cat with the prosthetic unicorn horn,
xxi
Central Office Re-architected as Datacenter (CORD),
117
Command line interface (CLI),
25,
91
Commercial off-the-shelf (COTS),
1,
23,
155
Configuration complexity,
27
application versioning,
164
UML and container hybrid,
166f
Context header format,
83f
Context switch/data copy reduction,
172
Conventional thread scheduling,
208–209
Corporate/enterprise/IT applications,
19
Intel Sandy Bridge microarchitecture,
192,
193f
run-to-completion and pipeline execution models,
195f
virtualization mechanism,
194
Customer Premise Equipment (CPE),
37
D
Data center-oriented draft,
84
Data plane I/O and COTS evolution,
9–11
Data Plane Management,
183
Decomposition, varying approaches to,
32–35
IMS “merged” decomposition proposition,
34f
PCSCF function split decomposition,
34f
Denial of Service (DoS),
167
Digesting ETSI output
big blocks and reference points,
55–58,
56f
domains of Orchestration and SDN controller products,
57f
high level ETSI NFV architecture,
54f
virtualization
in mobility applications,
61f
Direct cache access (DCA),
170,
200
Distributed Management Task Force (DMTF25),
65
Distribution management scheme,
164
Document Type Definition (DTD),
92
Domain Name Service (DNS) servers,
7
E
Ethernet Private Line (EPL),
136
digesting ETSI output,
52–68
organizational structure,
51f
European Standard (EN),
49
European Telecommunications Standards Institute (ETSI),
19,
49,
49–50
Evolution and Ecosystem Working Group (EVE),
72
Extended Message Signaled Interrupts (MSI-X),
200
Extended Page Tables (EPTs),
174
heterogeneous compute challenges,
208–209
F
Fault Management, Configuration Management, Accounting Management, Performance Management, and Security Management (FCAPS),
127
Feature velocity friction,
26
Fiber to the home (FTTH),
61
Fiber-to-the-cabinet (FTTC),
62
Field programmable gate array (FPGA) technology,
191,
203
memory and logical/computation cells,
204
routing channels over fabric,
204f
“First-generation” of service,
41
Fixed Access Network Virtualization,
62
Flow classification function,
39
G
NFV architecture mapping,
66f
NFV Security and Trust Guidance document,
67
General-purpose programming model (GPGPU),
205
high-level view of GPU architecture,
207f
Group Based Policy (GBP),
109
Group Specification (GS),
49
H
Intel Sandy Bridge microarchitecture,
192,
193f
run-to-completion and pipeline execution models,
195f
virtualization mechanism,
194
heterogeneous compute challenges,
208–209
Sandy Bridge architecture,
193f
Head of line (HOL) blocking,
201
HEAT Orchestration Template (HOT),
143
Heterogeneous compute challenges,
208–209
Hierarchical caching,
90,
90f
I
Industry Study Group (ISG),
49
Infrastructure-focused purchasing,
224
Institute of Electrical and Electronics Engineers (IEEE),
96–97
Instruction set architecture (ISA),
195
Instruction-level parallelism (ILP),
194
configuration of soft forwarder,
176f
DPDK-enabled Open vSwitch,
176f
Intel VT-c and VT-d,
174f
user space vhost implementation,
177f
Virtio-based solutions,
174
Sandy Bridge microarchitecture,
192,
193f
Intellectual Property Rights (IPR),
50
Interfaces and Architecture (IFA),
72
Internet Engineering Task Force (IETF),
19,
77
relationship to NFV Standards,
77
“Internet of Things”,
222
Intrusion Detection System (IDS),
29
K
L
Last level cache (LLC),
197
Layered controller model,
114f
Library operating systems (libOS),
165
Life Cycle Management,
141
Linux Branded Zones (LXz),
163
Linux Secure Module (LSM) framework,
168f
Logical limits
anonymized propagation delay of real network,
43f
“brownfield” of dreams,
44–45
granularity and extra vSwitch or network transitions,
43–44
standardization above network layer,
44
subset of fiber map of United States,
42f
configuration changes,
27
configuration complexity,
27
Gi-LAN of wireless network service center,
26f
overlay/tunnel technology,
29
proprietary/internal methodology,
27
M
generic resource and policy management for Network Services,
137–138
Network Service descriptors,
135–136
Network Service graph,
135f
VNFM demarcation point,
138
interpretations from architectural diagram reference points,
134
reimagining OSS/BSS—Brownfield partnership,
131–132
reimagining OSS—opportunities in SA,
132–133
external memory access,
196
memory bandwidth effect,
196
multithreaded microcode,
196f
NUMA-unaware assignment,
199
performance-impacting cache behavior,
198
in three-level cache,
197
typical/generic three-level cache structure for IA,
197f
Memory Management Unit (MMU),
157
Meta Data Type (MD Type),
82
Minimization of context switching,
13
Model-driven approach,
113
Model-Driven Service Abstraction Layer (MD-SAL),
115
Multilevel virtualization,
166
Multiple systolic arrays,
204
N
software packet handling bottom line,
180
Network Configuration (NETCONF) Protocol,
91,
93–94
layered controller model,
114f
analysts predicting big growth for,
15f
architecture mapping,
66f
data plane I/O and COTS evolution,
9–11
enabling new consumption model,
15–16
hypothetical vRouter,
10f
innovations make NFV compelling,
2f
generic resource and policy management for Network Services,
137–138
Network Service descriptors,
135–136
Network Service graph,
135f
VNFM demarcation point,
138
Performance & Portability Best Practises document,
63
redrawing NFV and missing pieces,
3–4
SDN–NFV–Merchant cycle,
16f
Security and Trust Guidance document,
67
services through microservices and PaaS,
122f
standardizing NFV architecture,
11
standards and open systems,
222
economic model for NFV,
223
“value-added” functionality,
223
strengthening “NFV as SDN use case”,
8
improving virtualization,
8–9
taxonomy for virtualizing services,
9f
2013 depiction of drivers,
3f
Network Function Virtualization Infrastructure (NFVI),
53,
103,
104,
127
layered controller model,
114f
AKKA-based clustering,
115
and OpenStack collaboration,
116–117
fork or not fork open source distributions,
111
IaaS building blocks,
106f
infrastructure networking,
105f
ML2 plugin architecture,
108f
Nova and Neutron interaction in VM creation,
109f
OPNFV picture of OpenStack multisite use case,
110f
performance measurement,
210
network packet processing,
201f
public Github Yang repository,
96–98
Yang data modeling language,
92–93
Network Operators Council (NOC),
50
Network Platform Context,
83,
84
Network Processing Units (NPUs),
196
generic resource and policy management for,
137–138
Network Service Chaining (NSC),
23
Network Service Descriptors,
150–151
data center-oriented draft,
84
Fixed Context Header block detail,
84f
SFC example using NSH,
86f
SFF NSH mapping example,
86f
MD Type 2 Variable Length Context Header,
85,
85f
using metadata to enhancing reliability,
88
Network Platform Context,
84
Network Shared Context,
84
NSH Data Center context header allocation,
84f
Service Platform Context,
84
Service Shared Context,
84
SFF NSH mapping example,
85f
Network Shared Context,
83,
84
“Network underlay” domains,
51
Network Virtualization Overlays (NVO3),
77
Next Generation OSS (NGOSS),
132
NFV Infrastructure as a Service (NFVIaaS),
59,
60f
NFV Orchestrator (NFVO),
56,
127
Nonuniform memory access (NUMA),
161
Northbound interfaces,
129
O
Open Daylight controller, Tacker integration with,
144–145
Open Network Platform (ONP),
180
integration with Open Daylight,
144–145
and service function chaining,
144
Tacker/Openstack system,
144f
TOSCA templates and parser,
142–143
TOSCA/HEAT translator,
143f
VNF auto-configuration,
141
Open Virtualization Format (OVF),
65
“Open Virtualization Profile”,
180
“Open-washing” of products,
3–4
AKKA-based clustering,
115
and OpenStack collaboration,
116–117
fork or not fork open source distributions,
111
IaaS building blocks,
106f
infrastructure networking,
105f
ML2 plugin architecture,
108f
Nova and Neutron interaction in VM creation,
109f
OPNFV picture of OpenStack multisite use case,
110f
OpenStack Foundation,
105
Operations and Management (OAM),
52,
82
Operations Support System (OSS),
4,
55,
127
interpretations from architectural diagram reference points,
134
orchestration-focused consumption,
224
Overlay/tunnel technology,
29
P
Packet Gateway (PGW),
26–27
application processing,
171
context switch/data copy reduction,
172
first generation VNF,
171t
scalar
vs. vectorization,
173
Physical network functions (PNFs),
220
Platform as a Service (PaaS),
44,
120,
120
NFV services through microservices and PaaS,
122f
Policy and charging rules function (PCRF),
35
Poll-mode drivers (PMDs),
167
Portability
Proprietary/internal methodology,
27
Protocol agnosticism,
112
Public Github Yang repository,
96–98
Public Yang Repo,
97,
97f
Q
QEMU hardware emulator,
156
QuickData Technology,
200
R
Radio access network (RAN),
52
Receive Side Coalescing (RSC),
200
Receive-Side scaling (RSS),
200
Remote procedure calls (RPCs),
92
Rendered Service Path (RSP),
80
Reorder buffer (ROB),
194
Repatriation/ISG2. 0,
71–73
Representational State Transfer (REST),
96
Residential Gateway (RGW),
61
Resiliency/resilience,
82
Resource oversubscription,
194
Run-to-completion and pipeline execution models,
195,
195f
S
drivers of NFV use case,
3f
SDN–NFV–Merchant cycle,
16f
strengthening “NFV as SDN use case”,
8–9
Se-Ma reference point,
134
Second-generation functions,
41
Secure Sockets Layer (SSL),
93
Secure Transport layer,
93
Segment Routing for IPv6 (SRv6),
88,
91
header extension format,
88f
hierarchical caching application using,
90f
Service assurance (SA),
64,
130
integration and virtualization,
23f
loosely coupled solution,
26–29
tightly integrated service solutions,
24–26
Service Delivery Gateway (SDG),
27
architecture document,
79–82
dedicated BNG functionality,
37f
dynamic and elastic nature,
41
fledgling deployments,
40
flow classification function,
39
high availability of stateful service functions,
32f
network edge environment,
36
providing NAT for legacy IPv4 devices in IPv6 network,
39f
second-generation functions,
41
service chains with separate paths,
30f
step-wise deployment/expansion of service offering into new market,
40f
TeraStream CloudVPN,
38,
38f
Service Function Forwarder (SFF),
80–81,
80f
Service Function Path (SFP),
80
Service functions (SFs),
19,
78
Service Instance,
20f,
21
Service Level Agreement (SLA),
41–42
Service path ID (SPI),
81,
83
Service Platform Context,
83,
84
Service Shared Context,
83,
84
Shallow L2 port-in-port-out tests,
211
Simple Modified Access Control Kernel (SMACK),
168
Simple Network Management Protocol (SNMP),
92
Single Instruction Multiple Data (SIMD),
194
Software Architecture (SWA),
13,
51
hypervisor maps physical resources,
158f
KVM execution and QEMU emulation,
157f
QEMU hardware emulator,
156
security—lowest common denominator,
169–170
UML and container hybrid,
166f
Software packet handling bottom line,
180
Split decomposition,
33,
34f
Standardization above network layer,
44
Standards and open systems,
222
economic model for NFV,
223
“value-added” functionality,
223
Streaming multiprocessors (SMs),
206
Structure of Management Information (SMI),
92
T
integration with Open Daylight,
144–145
and service function chaining,
144
Tacker/Openstack system,
144f
TOSCA/HEAT translator,
143f
VNF
Task Priority Register (TPR),
172
Technical Steering Committee (TSC),
51
TeraStream CloudVPN,
38,
38f
Terms of Reference (ToR),
72
Testing, Experimentation, and Open Source Working Group (TST),
72
Third Generation Partnership Project (3GPP),
50
feature velocity friction,
26
internal connectivity,
25
revenue opportunities,
24
Topology and Orchestration Specification for Cloud Applications (TOSCA),
65,
136
TOSCA/HEAT translator,
143f
Total cost of ownership (TCO),
219
Translation Look-aside Buffer (TLB),
157
“Transport Derived SFF”,
82
Transport Layer Security (TLS) Protocol,
96
Transport manager (TM),
180
Transport-tied solutions,
79
U
and container hybrid,
166f
kernel across multiple customers,
167
Universal resource identifier (URI),
96
V
Vector Packet Processor (VPP),
182
plug-in architecture,
183f
software packet handling bottom line,
180
user space vhost implementation,
177f
Virtio-based solutions,
174
Virtual Cache use case,
62
Virtual Evolved Packet Core (vEPC),
53
Virtual firewall (vFW),
38
Virtual Machine Extensions (VMX),
157
Virtual machine manager (VMM),
156
ETSI NFV architecture,
158
Virtual Network Function Component (VNFC),
53
Virtual Network Function Manager (VNFM),
56,
127
Virtual network functions (VNFs),
51,
53,
218
Virtual Network Functions as a Service (VNFaaS),
59
Virtual service creation,
29–35
connectivity techniques,
180
current packet handling,
170
application processing,
171
context switch/data copy reduction,
172
first generation VNF,
171t
scalar
vs. vectorization,
173
hypervisor maps physical resources,
158f
KVM execution and QEMU emulation,
157f
QEMU hardware emulator,
156
security—lowest common denominator,
169–170
UML and container hybrid,
166f
of Mobile Core Network and IMS,
59
NFV Performance & Portability Best Practises document,
63
orchestration and management,
64
portability requirements,
63
resiliency requirements,
63
security and maintenance sections,
64
service
Virtualization Deployment Units (VDUs),
140
Virtualized residential service CPE (vCPE),
61
VLAN
VNF Descriptions (VNFDs),
140
VNF Platform as a Service (VNFPaaS),
59,
60
vPE termination (VPN),
38
W
Y
Yet Another Next Generation data modeling language,
92–93,
115
Z