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

3 ITU-T Focus Group IMT-2020 Deliverables

8.2.2 Orchestration actions

This section lists the actions that the orchestration system will have to process and gives a high level
description of what each action means. Subsequent sections describe each of these actions and then break
them down into the timeline of sub-actions that must occur in the layers below. Again this is done without
specifying any particular format. For most of these actions it is assumed that a SliceProfile exists that
describes in a high level language the desired properties of a slice.

A SliceProfile at a high level has to describe the radio access technology to be deployed, at what bands, on
what antennas, and then must describe the packet processing functions (vCore) that are required to support
the RAT. The profile must give an indication of the minimum amount of processing required for each
component and any constraints on the various functions as to their delay/placement.
Components such as a CRAN, DC, IDCNetwork, uWave network etc. Have Capabilities which enumerate the
resources they have available for higher level orchestration. All resources have network wide unique names
and where resources in one component connect to another it must be possible to infer the connectivity
through a name match database. For example if a router that is part of a metro network has a port that is
connected to a switch port in a datacenter then the resources in the metro network need to have the same
name for the interconnection as the resources for the datacenter. There are various ways to achieve this
such as juxtaposing the sorted pair of the names of the two end points as discovered through well known in
band adjacency discovery protocols.

Action_connectToCran: This action will bring a new C-RAN under the orchestration control. Auto discovery
is unnecessary and configured secure tunnels is likely sufficient. Capabilities of the CRAN: CranCapabilities
will be propagated into the orchestrator.
Action_connectToDran: This action will bring a new D-RAN under the orchestration control. Auto discovery
is unnecessary and configured secure tunnels is likely sufficient. Capabilities of the DRAN: DranCapabilities
will be propagated into the orchestrator. Not all resources need to be propagated, and it may be desirable
to propagate subsets to different orchestration systems.
Action_connectToIDC: This action will bring a new inter data-center network controller under the
orchestration control. Auto discovery is unnecessary and configured secure tunnels is likely sufficient.
Capabilities of the inter data center IDCCapabilities will be propagated into the orchestrator, the names of
interconnection end points must match to allow end to end orchestration. Not all resources need to be
propagated, and it may be desirable to propagate subsets to different orchestration systems
Action_connectToDC: This action will bring a new metro DC under the orchestration control. Auto discovery
is unnecessary and configured secure tunnels is likely sufficient. Capabilities of the DC: DCCapabilities will be
propagated into the orchestrator. Not all resources need to be propagated, and it may be desirable to
propagate subsets to different orchestration systems.

Action_connectToUWave: This action will bring a new micro or millimetre wave network under the
orchestration control. Auto discovery is unnecessary and configured secure tunnels is likely sufficient.
Capabilities of the network are expressed as uWaveCapabilities and will be propagated into the orchestrator.
Not all resources need to be propagated, and it may be desirable to propagate subsets to different
orchestration systems.

Action_createSlice: This action requests the creation of a new Slice but does not activate it. It will take a
Profile of what the new slice looks like, produce an internal representation (called a Slice) which can be used
to work through the allocation of resources and track the state of resources as they are activated by
subsequent actions. The contents of the Profile are an important aspect of softwarization which needs to be
defined.
Action_computeSliceResources: This action given a Slice will check to see if the slice can actually be
instantiated given the xxxCapabilities of the attached components. If not it would report what other actions
would need to be taken to allow this slice to be activated. This likely involves an optimization over all
resources in all xxxCapabilities to see what the best allocation of resources to this slice would be. An
interesting question is how resources can be stolen by a higher priority Slice from a lower priority Slice
(bumping is the traffic engineering term).

166