Page 301 - Big data - Concept and application for telecommunications

Big data - Concept and application for telecommunications 5

catalogue can contain/reference all relevant technical information (including relevant templates) required to
deploy, provision and run a CL service and/or its components.
NOTE – The term "CL service" as used in this Recommendation refers to a service provided by either the
base CL services functional component or a profiled CL services functional component (see clause 7.2.3).
These two components consist of the necessary software required to implement CL services, either base
CL services or profiled CL services.

The CL-MSO functional component also provides the capabilities for managing a particular CL service, it
manages the scaling and performance related to a CL service: the CL-MSO functional component obtains
monitoring information in order to measure and record KPIs of each CL service and the amount of resources
allocated for a CL service based on these KPIs.
The orchestration of the SDN-CL by the CL-MSO functional component may involve relevant policies (e.g., a
placement rule which aims to avoid a single point of failure).
The CL-MSO functional component also keeps track of the overall state of allocated and available resources
in the SDN-CL. The comparison of allocated resources in the SDN-CL against CL service's performance KPIs
can assist in the identification of current or potential bottlenecks.
The CL-MSO functional component provides capabilities for connecting different SDN domains in order to
make inter-domain operations where an SDN domain is a collection of SDN-RL entities under logically one
SDN-CL entity. In such cases, it is responsible for establishing the communication path(s) required, and for
passing appropriate identity and credentials with requests made to other SDN domains. The details of these
operations are beyond the scope of this Recommendation.
If delegated by MMF, some management tasks can be performed by the SDN-CL, in particular tasks that are
tightly coupled with control operations and can be jointly optimized for resource usage, or for performance.

7.2.3 Control layer services functional component
The CL services functional component provides a set of programmable control and optionally management
functions (if delegated by MMF) covering e.g., physical and virtual network topologies, network element
configuration, and traffic forwarding management. The CL services functional component includes the
following:
– base CL services functional component that is obligatory in all SDN instantiations, that is,
connectivity. It includes common functions used in all SDN deployments e.g., topology discovery,
monitoring of resources, and on-demand path computation and monitoring;

– profiled CL services functional component (shown in Figure 7-3 and representing use case specific
CL services), which will be defined in separate Recommendations. In a given implementation it is
allowed to combine many of such profile-dependent services, e.g., mobility management for mobile
networks.
Base CL services and different profiled CL services functional components may be instantiated depending on
the targeted SDN functional profile. More explanation on functional profiles is given in clause 8.
7.2.4 Control layer resource abstraction functional component

The main purpose of the CL-RA functional component is to support unified programmability of resources in
the SDN-RL. Information and data models of underlying network resources are means to provide an
abstracted and unified view of these resources to the SDN-CL, so that the developers of CL services and/or
functions can simplify their program logics without the need for a detailed knowledge of the underlying
network resource technologies. These models provide a detailed, abstracted view of both, physical or
virtualized network resources. The CL-RA functional component provides capabilities to create multiple
virtual resources by using a single physical resource or can create a composite virtual resource as an
aggregation of several virtual or physical resources.

Network and infrastructure 293