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

2 ITU-T Focus Group IMT-2020 Deliverables

dedicated to different types of services. Different types of network slices can be composed of not only
standardized network functions but also some proprietary functions which are provided by different
operators or 3rd parties.
9.1.2 Requirements

[REQ] The network architecture for IMT-2020 is required to provide softwarization capabilities with enhanced
performance for wired and wireless (i.e. WLAN, satellite) networks.
[REQ] The network architecture for IMT-2020 is recommended to provide softwarization capabilities with
enhanced performance for mobile access networks (i.e., newly-defined RATs for IMT-2020, evolved
IMT-advanced RATs).

NOTE – The softwarization has been initially designed for wired networks and it may not be optimized for
wireless (e.g. WLAN, satellite) and mobile networks. The mobile network optimized softwarization should be
studied considering the best use of existing features to overcome the performance issues which may arise in
some of SDN solutions.

[REQ] The network architecture for IMT-2020 is required to support programmability of network functions
in data plane for easier provisioning of new emerging services.
NOTE – The requirements in data plane in an IMT-2020 network will be depending on the various service
characteristics of new emerging services such as ICN. In-network data processing and service provisioning
are the capabilities to cope with the diverse requirements in data plane. However, the capabilities have not
studied from mobile network perspective. This also applies to a satellite network segment. The capabilities
to support the easier provisioning of new emerging services in IMT-2020 network architecture should be
studied.

[REQ] The network architecture for IMT-2020 is required to support the separation of control and data plane
functions in network.

[REQ] The network architecture for IMT-2020 is required to create, operate and manage network slice.
NOTE – Network slice can be created dynamically to form a complete and fully operational network
customized to cater for different diverse market scenarios. The operator should be able to compose network
slices, i.e. sets of network functions (e.g. potentially from different vendors), resources to run these network
functions and policies and configurations, e.g. for hosting multiple enterprises or MVNOs etc.
[REQ] The network architecture for IMT-2020 is required to protect negative impact in one network slice
offered by other network slices.
NOTE – Dynamic control of slice resources (bandwidth, CPU, etc.) may need to be considered based on
priority of slices.
[REQ] The network architecture for IMT-2020 is recommended to maintain the established QoS of the
network slice after creation regardless of the status of other network slices.
NOTE – The isolation between different network slices should be considered in order to prevent data
communication in one slice to negatively impact services offered by other slices.
[REQ] The network architecture for IMT-2020 is required to support elasticity of network slice in term of
capacity with no negative impact on the services of this slice or other slice.
rd
[REQ] The network architecture for IMT-2020 is required to support that the 3 parties can create and
manage a network slice configuration via suitable APIs, within the limits set by the network operator.

[REQ] The network architecture for IMT-2020 is required to be guaranteed the overall QoS of a network slice
instance served for both operators and third parties (MVNOs, enterprises, service providers, content
providers, etc.) on shared infrastructure.
[REQ] The network architecture for IMT-2020 is required to identify certain terminals and subscribers to be
associated with a particular network slice.

22