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

3 ITU-T Focus Group IMT-2020 Deliverables

After that, some detail parameters such as performance (e.g., bandwidth/latency), capacity, preferred
deployment location of NF, life cycle management policy and reliability policy can be configured based on
basic template. Different kind of complete templates can be created based on different network slice
configurations, e.g. different eMBB network slice instances with various latency and numbers of subscribers.

A Network slice template is composed of the following information elements:
– Topology: It describes a set of network functions consisting of a network slice, network connections
between these network functions and these functions’ resource requirements (e.g., computing
resource, storage resource and network resource).
– Configuration: It includes the configuration information of resources and functions which compose
a network slice instance.
• Resources configuration: It describes the configuration information of computing resources,
storage resources and network resources of a specific network slice instance, e.g. IP
connections between network functions, service-level and resource-level lifecycle management
rules.

• Functions configuration: It describes some function-specific configurations that consisting of a
network slice, e.g., IP address pool for UEs.

– Work Flows: It describes the process of instantiating the network functions in a network slice, e.g.,
the deployment sequence of network functions or dependence between them.
NOTE 1 – [Ref.9.4-1] can be a candidate implementation on configuration.

NOTE 2 – Slice template model can be recursive, as described in Section 8.2. It can be used to support flexible
and efficient slice template management.

Scenario 2: Network slice deployment
Slice Management and Orchestration can select the generated template, instantiate network function and
establish network connection according to the requirement of network slice complete template. Based on
the template, resource states, and operator policy, it can also allocate and reserve appropriate resources for
the slice.

Scenario 3: Network slice monitor
Slice Management and Orchestration can monitor the operating states of one network slice such as number
of connected subscribers and service traffic of the whole network slice.
References

[9.4-1] GENI configuration model (RSPEC), http://groups.geni.net/geni/wiki/GENIExperimenter/RSpecs.

9.5 Scenario 5: Satellite integration in the 5G Ecosystem
The application of NFV and “Cloud RAN” aspects to the satellite component paves the way towards the full
virtualisation of satellite head-ends, gateways/hubs and even satellite terminals, thus entirely transforming
the satellite infrastructure, enabling novel services and optimising resource usage. In this context, several
enhancements/adaptations of current SDN/NFV technologies (e.g., extensions of the OpenFlow protocol) are
envisaged, in order to be fully applicable to the satellite component domain and exploit satellite-specific
capabilities.
Satellite network architecture can be designed to enable virtualisation and SDN-based control of the network
components supporting advanced service delivery, including through hybrid satellite / terrestrial
infrastructure.

NFV will facilitate the management and deployment of virtualised functions of the satellite network, and
SDN-based control can be achieved through programmable interfaces for satellite resources.
NFV / SDN integration in satellite networks will allow for the smoother integration of satellite infrastructure
into the 5G ecosystem, the provision of innovative services, and ease the evolution of services where
deployed.

180