Page 117 - 5G Basics - Core Network Aspects

Core network aspects 1

– The service management is required to provide virtual resource related information to an LINP
operator in order to assist the LINP operator for service provisioning procedures: installation,
booting up, updating, termination and deletion of application programs or application processes
over an LINP.

– The service management is recommended to provide programing capability regarding service
provisioning procedures.

7.5 Authentication, authorization and accounting

To prevent malicious or unexpected access to physical and/or virtual resources, authentication, authorization
and accounting (AAA) are essential.
The requirement for the AAA is as follows:
– Each management entity is recommended to provide an AAA mechanism. The mechanism is
recommended to be executed before a physical and/or virtual and/or LINP management entity or
LINP operator accesses another management entity.

7.6 LINP federation
LINP federation coordinates a single federated LINP from multiple LINPs built by individual distinct
administrative domains. The federation should allow the LINP operator to build and to use the integrated
LINP as a single LINP.

When a network service is provided to users, there are often two or more administrative domains among all
users. In this case, a federated LINP is required to combine two or more LINPs for users to communicate with
each other, while each LINP is individually managed by a different network service provider. Therefore, LINP
operators should be able to build LINPs over the multiple administrative domains, regardless of the physical
and/or virtual resources and/or management policies of these administrative domains.
The requirements for the LINP federation are as follows:
– The LINP federation is recommended to provide negotiation capability between different
administrative domains for exchanging capability information about physical and virtual resources.
– The LINP federation is recommended to allow LINP operators to build LINPs over the different
administrative domains, regardless of the physical resource types or management policies of these
administrative domains.

– The LINP federation is recommended to avoid inconsistent use of resources and inconsistent
configurations in an integrated LINP built over different administrative domains.

– An administrative domain is recommended to provide a set of standard interfaces for the other
administrative domains in order to describe the different types of physical resources of each domain
in a standard form.
– The standard interfaces between the administrative domains are recommended to allow for varying
levels of resource abstraction.
– The standard interfaces are recommended to allow the administrative domains to coordinate the
types of AAA procedures, such as, exchanging the LINPs operators' AAA information, delegating AAA
procedures to the other administrative domain, etc.
– It is recommended that the identification of physical resources in one administrative domain is not
restricted by the identification used in other domains.

7.7 Service mobility

In virtual networks, a significant number of services will be created by composing diverse software
components. Some services may be provided within a single LINP and other services may employ multiple
LINPs. As network virtualization enables LINP operators to easily acquire the virtual resources needed to
compose the LINPs, LINP operators may require that the software components be dynamically moved when,
due to end-user mobility, an attachment point to which the end-user connects in a single LINP is changed.

107