Page 217 - ITU-T Focus Group IMT-2020 Deliverables

ITU-T Focus Group IMT-2020 Deliverables 3

• Function Name: Service Monitoring and Monitoring Analysis: The service monitoring and the
monitoring analysis working closely together, will collect and analyse service-level (not just network)
performance indicators.
• Function Name: NFVI Northbound API: The IMT-2020 system must be able to support an API which
exposes the NFV Infrastructure as a service.

• Function Name: Southbound Plugin to use NFVI API: The IMT-2020 system must be able to support
a southbound interface which can request elements of NFV Infrastructure as a service.

• Function Name: Timely alarms for SLA violation: The monitoring system must supply alarms for SLA
violations (or malfunctioning components) in a timely manner depending on the SLA and type of
problem. This means that the failure detection, but also the service platform message bus and
notification system must have real-time capabilities. E.g. VNF unavailability for real- time traffic
must be signaled as fast as possible, while in the case of best-effort traffic alarm signaling can
happen with modest delays. Likewise, urgency of alarms is higher for VNFs with 1000s of users
compared to single-user VNFs in the general case.
• Function Name: Manage update of components: Sequence/ strategy of update using DevOps.
Sequence for validation and migration.

• Function Name: Support different modes of management/control: EPC can be fully managed by the
operator, i.e. EPC fully deployed and managed by the customer (e.g., a MVNO). Or Hybrid were
components are managed by the operator (e.g., SGW) and others by the customer (e.g., HSS). Or
fully managed by the customer.
• Function Name: Support Services with high SLA: vEPC is a service that is operates under a 5 nines
SLA, it can not allow service degradation when scaling / healing / updating / migrating.
• Function Name: Support “state-full” services: vEPC is a “state-full service” - all its components are
state-full, they can not loss their state when scaling / healing / updating /migrating.
• Function Name: Integration with OSS: vEPC service operation involves integration with OSS system,
IMT-2020 should expose relevant APIs.

• Function Name: Distributed NFVI: ISP and Network Operators architecture requires a geographical
distribution of PoP (Point of Presence) where instantiate multiples VNFs as close as possible to user
or based on the service demand. One example is when a security attack happens it is preferred to
react as close as possible of the source of the attack. As a consequence IMT-2020 orchestration layer
should support multiples NFVI and VIM in distributed networks case .
• Function Name: Open interfaces towards NFV: NFV components like VIM, NFVI or NFVO could be
deployed with multiples providers. Indeed the number of NFV solutions is growing day by day. IMT-
2020 orchestration framework must support open or standards interfaces (southbound towards
NFVI) to ensure the smooth integration of different NFV providers.

• Function Name: VNF Real-time Monitoring: In order to detect and react to security incidents, VNFs
will generate in real time information useful for Monitoring and response. IMT-2020 framework
must be able to collect, store, process and report in valid time windows to be useful to the ISP.
• Function Name: VNF reporting to BSS/OSS and subscriber: In order to detect and react to security
incidents, VNFs will generate in real time information useful for Monitoring and response. IMT-2020
framework must be able to collect, store, process and report in valid time windows to be useful to
the ISP.
• Function Name: Legacy support: Any ISP or Network Operators or corporations has today deployed
security networks solutions in virtualized or bare metal appliances. The most relevant example is a
Firewall device. If IMT-2020 has the aim to offer complex solutions and integrate with existing
network environment, then IMT-2020 need to interact and manage with not only VNFs.

• Function Name: Quality of service monitoring: One of the key method to detect security problems
are the deterioration in the QoS. Metrics generation and degradation detection of network traffic,
i.e. caused by a overloaded NFVI node or a attack, should be supported and reported case.

211