Page 262 - 5G Basics - Core Network Aspects

1 Core network aspects

6) Charging rules enforcement (both online and offline);

7) DHCPv4 or v6 services;
8) Mobility anchoring within a single access;
9) Optionally, support deep packet inspection function.
6.3.3 Multi-connection registration functional entity (MR-FE)

The multi-connection registration functional entity manages the status of the access technologies available
to the MUE. It accepts the registration requests from every MUE for all of its valid access technologies. It is
responsible for binding each MUE with its all available access IDs (such as IP address, MSISDN, etc.). It shares
the latest access information to MUEs and is recommended to provide information which would optimize
the multi-connection pre-configuration in MUEs. It also exchanges multi-connection signalling with MUEs by
reference point Rt.

The functions of the MR-FE are as follows:
1) Identify and maintain the binding between different access technologies from each MUE;
2) Remove invalid access network information of MUEs;
3) Push access network policy information to MUEs;
4) Update the available access network information to MUEs;

5) Provide available multi-connection information of MUEs to the MC-FE for making multi-connection
policy decisions;

6) Provide multi-connection authentication and authorization;
7) Allocate and maintain MUE identifiers.
6.3.4 Multi-connection coordination functional entity (MC-FE)

The multi-connection coordination functional entity supports IP-based mobility management depending on
available access technologies The MC-FE is a component of the multi-connection control function.
The functions of MC-FE are as follows:
1) Monitor and update the specific load and/or QoS policy for each access network and assign to MMF;
2) Dynamically collect and maintain traffic load information across the available access technologies;
3) Report abnormal status of the access network;

4) Get user preference about the network selection.
6.3.5 Multi-connection policy control functional entity (MPC-FE)

The multi-connection policy control functional entity assigns policies for each session and guarantees the
QoS of the session by sending the policies to the MC-FE and/or AC-FE. The MC-FE and/or AC-FE would assign
specific policies for each access based on the policies from MPC-FE, such as control routing paths or rate of
IP flows.
The functions of MPC-FE are as follows:
1) Acquire service information from the SCF;

2) Receive and authorize the QoS resource request from the SCF;
3) Store and maintain the rules to make policies defined by the network operator;
4) Obtain subscription profile from the MUP-FE;
5) Make policy decisions based on the above information and provide the decisions to the MC-FE;
6) Support and provide policy mapping between different networks for AC-FEs.

252