Page 139 - 5G Basics - Core Network Aspects

Core network aspects 1

− Credentials for authentication to connect to gateway functions (optional).

In order to provide the functions described above, user terminal functions should include the following
function:
− Gateway connect function, which adds LINP IDs or correspondent IDs to end-users' data
frames/packets for specific applications, operating systems (OSs), or VMs in a user terminal. The
function also extracts LINP IDs or correspondent IDs from end-users' data frames/packets and
identifies destination applications, OSs, or VMs in the user terminal.
If the gateway connect function adds an LINP ID to all data frames/packets from applications, OSs, or VMs in
a user terminal, the user terminal is attributed to a single LINP. On the other hand, if gateway connect
function adds a different LINP ID per application, OS, or VM, each application, OS, or VM is attributed to a
different LINP.

The information needed to associate LINP IDs or correspondent IDs with specific applications, OSs, or VMs in
a user terminal may be provided by a service developer to end-users.

17 Federation functions

Federation functions are required if LINPs need to be expanded across multiple administrative domains.
Federation functions allow multiple VMIs for management and control and multiple NNIs for forwarding end-
users' data coming from different administrative domain.
To achieve this, federation functions have to reconcile the differences in specifications of NNIs and/or VMIs
reference points, LINPs, and so on. Followings are the functions used for this purpose:
− Command translation: Each administrative domain may have different commands for LINP creation
and management. In that case, command translation function is required to translate each
administrative domain's commands and parameters into another administrative domain's
commands and parameters;

− State transition mapping: Each administrative domain may have different state transition for LINPs,
virtual node resources and virtual link resources. In that case, state translation function is required
to maintain the difference in state during application programming interface (API) conversion;
− Policy translation: Each administrative domain may have different policies for LINP creation and
management. In that case, policy translation function is required to reconcile the differences;
− LINP definition translation: Each administrative domain may have different formats to define LINP
configurations. In that case, LINP definition translation function is required to convert an LINP
definition of one administrative domain into that of another administrative domain;
− Data plane conversion: Each administrative domain may have different end-users' data packet
formats. In that case, data plane conversion function is required to convert a packet format of one
administrative domain into that of another administrative domain;
− Protocol/resource negotiation: Each administrative domain may have different capabilities in
handling protocols and resources. Federation functions are recommended to include
protocol/resource negotiation function. This function may be used when failures occur or new
resources are detected. In that case, the function is executed before federating LINPs.

18 Reference points
The reference points defined in this Recommendation are given in the following clauses.

18.1 User-to-network interface (UNI)

A UNI reference point resides between gateway functions of a network operator and user terminal functions
of an end-user.

129