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

ITU-T Focus Group IMT-2020 Deliverables 3

c) Messages related with the “Read”

These messages are prepared to read (including get the notification) the status, value of parameters
or characteristics of virtual resources.
One example of this message is “Virtual Resource Status Request” message. To manage the
utilization of virtual resource of PRC, SEC sends this message to PRC to request informing virtual
resource status of PRC. For the response of this message, “Virtual Resource Status” message is
prepared. The PRC sends SEC this message to inform the status of virtual resource.

d) Message related with the “Delete”
These messages are prepared to delete the created virtual resource level services which are
described in “a)” of this subsection.

One example of this message is “Virtual Resource Release” message According to the request from
orchestrator, SEC sends this message to PRC to release the virtual resource of PRC. For the response
of this message, “Virtual Resource Release Complete” message is prepared. The PRC sends SEC this
message to inform the result of virtual resource release message.
For the life cycle management of network slicing, a lot of scenarios may be considered. The following is one
of them. When the allocated resource has to be changed the value (for example bandwidth), there are two
scenarios as follows. The key point is “continuously existing or once deleted”.
Scenario 1: Once the present slice is deleted, the new one is set up with the new value.
Scenario 2: The slice continues to exist; only the value or parameters of resource are changed.

For the Scenario 1, the messages related with the “delete” and “create” will be used. For the Scenario 2, the
messages related with the “update” will be used.

7.1.2.2 Expected additional functionalities and related document at the reference point.

In the above messages, only a few examples are introduced. The other related things for these four categories
have been considered by the other SDOs as described in the transport SDN API document [Ref.7.1-4].

Related document (Transport SDN)
The APIs in the document and categories considered by the authors of this clause are shown in Appendix of
this clause.

Additional Functionalities
They must be useful to consider the set of the messages on the proposed reference point. However, some of
the functionalities should be added. They will be obtained from the gap analysis between the Phase 1 report
and related documents [Ref.7.1-4].

(a) Functionalities for the low power operation
It seems that the transport SDN do not include the function to operate with the low power modes.
The functionalities should be prepared that the Orchestrator can read the information of the
capabilities for the low power modes [Ref.7.1-5] from the Physical Resource Controller if the modes
are implemented. In this case, information which the Orchestrator can consider the trade-off to use
the modes also should be included.
(b) Functionalities for updating the resource allocation using statistical traffic information
The transport SDN includes the function to allocate the resources with utilization ratio of the
(allocated resource / physical link resources); however it seems that it does not include the functions
to allocate/update the resources using statistical traffic information. For example, if these functions
increase the allocated resource automatically when the traffic is increased, the functions can
prevent the overflow by an unexpected traffic increase. This functionality must work well especially
in the case when a set of the some virtual paths share a resource.

145