Page 340 - 5G Basics - Core Network Aspects

1 Core network aspects

2) In the multi-connection environment, each connection may have its own charging information, and
charging information needs to be aggregated to determine total charging information. Aggregation
of charging information is required in multi-connection.

6.13 UE function in multi-connection
In a multi-connection environment, the following are to be supported by the multi-connection UE.
1) A multi-connection UE is required to maintain multiple simultaneous access network connections.

2) A multi-connection UE is required to map IP flows to different access network connections.
3) A multi-connection UE can optionally receive configuration parameters from each of its access
networks through various mechanisms such as DHCP and PPP. Some of the available parameters are
specific to a specific interface, such as the IP address. Others are specific to the network node, such
as the routing information (e.g., gateway), DNS servers' or IP addresses. Configuration
harmonization in terms of DHCP, PPP, and DNS among others is required to avoid configuration
conflicts.
4) Adjustment of packet rates is required to be provided for the different IP flows belonging to the
same application between different connections when services are decomposed.
5) A multi-connection UE is required to support IPv4 only, IPv6 only, or dual-stacks.

6.14 IPv4/6 consideration

According to IPv6-based NGN defined in [ITU-T Y.2051], IPv6 impacts to NGN cover not only the UE side but
also the network side. In the multi-connection environment, it is required to support IPv4 and IPv6 dual stack
and simultaneous usage thereof.

6.15 Energy efficiency and energy/power management in multi-connection

It is recommended to pursue energy efficiency in the multi-connection network, both in the network
infrastructure and in the UE.
In order to reduce the battery consumption of the multi-connection UEs, the energy/power management
mechanisms (e.g., in idle mode, sleeping mode, and active mode) are required to be supported on each
interface supported by the multi-connection UE.

6.16 Backward compatibility

The multi-connection capability is required to be backward compatible. When deployed in legacy networks,
it is required to interoperate with ordinary network equipment and user equipment (i.e., single-connection
technology).

6.17 Security requirement
Security requirements such as access control, authentication, non-repudiation, data confidentiality,
communication security, data integrity, availability, and privacy are required across all connections.
1) Protection against unauthorized use of multi-connection capability;
2) Mechanisms for data confidentiality among multiple accesses when necessary. The data contains
the user's profile in each connection, e.g., preferences, profiles, presence, availability and location
information;

3) Mechanisms for data integrity in the case that the data of an application is delivered through several
connections;
4) Mechanisms of non-repudiation for preventing one of the connection in a communication from
falsely denying having participated in multi-connection communication;
5) Protection to minimize faked connection registration, and the hostile attack by one of the
connections;

330