Content for TS 22.101 Word version: 19.1.0
26a User Identity
26a.1 Introduction
26a.2 Requirements
26a.2.1 User Identifiers and user authentication
26a.2.2 Access to services
26a.2.3 User Identity Profile and its User Identities
26a.2.4 Operator requirements
26a.2.5 Privacy requirements
27 User plane congestion management
27.1 Introduction
27.2 General
27.3 Prioritizing traffic
27.4 Reducing traffic
...
...
26a User Identity |R16| p. 64
26a.1 Introduction p. 64
Identifying distinguished user identities of the user (provided by some external party or by the operator) in the operator network enables an operator to provide an enhanced user experience and optimized performance as well as to offer services to devices that are not part of a 3GPP network. The user to be identified could be an individual human user, using a UE with a certain subscription, or an application running on or connecting via a UE, or a device ("thing") behind a gateway UE.
Network settings can be adapted and services offered to users according to their needs, independent of the subscription that is used to establish the connection. By acting as an identity provider, the operator can take additional information from the network into account to provide a higher level of security for the authentication of a user.
26a.2 Requirements p. 64
26a.2.1 User Identifiers and user authentication p. 64
The 3GPP system shall be able to provide User Identities with related User Identifiers for a user.
The User Identifier shall be independent of existing identifiers relating to subscription or device (e.g. IMSI, MSISDN, IMPI, IMPU, SUPI, GPSI, IMEI) and of other User Identifiers.
The User Identifier may be provided by some entity within the operator's network or by a 3rd party.
The 3GPP system shall support to interwork with a 3rd party network entity for authentication of the User Identity.
The 3GPP system shall support to perform authentication of a User Identity regardless of the user's access, the user's UE and its HPLMN as well as the provider of the User Identifier.
The 3GPP network shall be able to provide a User Identifier for a non-3GPP device that is connected to the network via a UE that acts as a gateway.
The 3GPP network shall support to perform authentication of a User Identity used by devices that are connected via a UE that acts as a gateway.
The 3GPP system shall be able to take User Identity specific service settings and parameters into account when delivering a service.
A subscriber shall be able to link and unlink one or more user Identities with his 3GPP subscription.
The 3GPP system shall support user authentication with User Identifiers from devices that connect via the internet; the 3GPP system shall support secure provisioning of credentials to those devices to enable them to access the network and its services according to the 3GPP subscription that has been linked with the User Identity.
The 3GPP system shall support secure provisioning of credentials to a non-3GPP device connected via a gateway UE, whose User Identifier has been linked with the 3GPP subscription of the gateway UE, to enable the non-3GPP device to access the network and its services according to the linked 3GPP subscription when connected via non-3GPP access.
The 3GPP system shall be able to assess the level of confidence in the User Identity by taking into account information regarding the used mechanism for obtaining that User Identity (e.g. algorithms, key-length, time since last authentication), information from the network (e.g. UE or device in use, access technology, location).
The operator and the subscriber shall be able to restrict the number of simultaneously active User Identifiers per UE.
26a.2.2 Access to services p. 65
The 3GPP System shall support to authenticate a User Identity to a service with a User Identifier.
The 3GPP system shall be able to provide information to services concerning the level of confidence of the User Identity and authentication process.
A service shall be able to request the 3GPP network to only authenticate users to the service for which the association of the user with a User Identifier has been established according to specified authentication policies of the service.
When a user requests to access a service the 3GPP System shall support authentication of the User Identity with a User Identifier towards the service if the level of confidence for the correct association of a User Identity with a User Identifier complies to specified policies of the service.
The 3GPP network shall be able to take the User Profile into account when assigning a UE to a network slice, moving a UE from one network slice to another, and removing a UE from a network slice.
The 3GPP system shall support to allow a UE access to a slice based on successful User Identity authentication.
The 3GPP system shall support to deny a UE access to a slice based on unsuccessful User Identity authentication.
26a.2.3 User Identity Profile and its User Identities |R19| p. 65
The 3GPP system shall be able to store and update a User Profile for a user.
The User Profile shall include a User Identifier.
The User Profile may include one or more pieces of the following information:
- additional User Identifiers of the user's User Identities and potentially linked 3GPP subscriptions,
- used UEs (identified by their subscription and device identifiers),
- capabilities the used UEs support for authentication,
- information regarding authentication policies required by different services and slices to authenticate a user for access to these services or slices.
- User Identity specific service settings and parameters. Those shall include network parameters (e.g. QoS parameters), IMS service settings (e.g. MMTEL supplementary services), SMS settings, and operator deployed service chain settings.
- User Identity specific network resources (e.g., network slice).
26a.2.4 Operator requirements p. 66
The operator shall be able to enable or disable the use of a User Identifier in his network.
The 3GPP System shall support operators to act as User Identity provider and to authenticate users for accessing operator and non-operator deployed (i.e. external non-3GPP) services
The operator shall be able to set the boundaries within which the user specific settings are taken into account in his network. The operator shall be able to restrict the feature depending of the provider of the User Identifier, the roaming status of the UE, the service and its specific parameters.
The operator shall be able to set restrictions for devices accessing the network and its services via non-3GPP access with their User Identity linked to a 3GPP subscription. The 3GPP system shall support restrictions based on the User Identity provider, the roaming status of the linked 3GPP subscription, and the network service that is accessed.
The 3GPP system shall be able to support automatically suspending an active User Identity after a certain period of time of user inactivity, e.g. up to one hour, as configured by the operator.
The 3GPP system shall be able to support a fast re-activation for a suspended User Identity, based on MNOs' configuration.
The 3GPP system shall enable a user to configure, within the boundaries set by the network operator, which services shall be available on a device where this user logs in using a User Identifier. These services include voice, video, and messaging including SMS.
26a.2.5 Privacy requirements p. 66
The 3GPP system shall protect the privacy of a user by transferring to a service only User Identity information that is necessary to provide the service and for which this user has consented to when registering for the service.
The 3GPP network shall be able to protect the privacy of a user when accessing the 3GPP services from a UE which is shared by multiple users.
27 User plane congestion management |R13| p. 67
27.1 Introduction p. 67
RAN user plane congestion, in the context of this clause, is considered to be downlink congestion that affects the user plane, which may last for a few seconds, a few minutes, or a few hours due to arrival of new active users, increase of communication intensity of existing users, the radio environment changing, the mobile user changing location, and other reasons, thus causing the capacity of RAN resources to transfer user data to be exceeded. A short-duration burst of user plane traffic should not be identified as RAN congestion.
27.2 General p. 67
- The network shall be able to detect RAN user plane congestion onset and abatement. Mechanisms to cope with RAN user plane congestions should be resilient to rapid changes in the level of congestion.
- The network shall be able to identify whether or not an active UE is in a RAN user plane congested cell.
- The network operator shall be able to configure or provision and enforce policy rules to best deal with RAN user plane congestion.
- The system should react in a timely manner to manage a RAN user plane congestion situation, i.e. that the measures taken become effective to promptly help resolve the RAN user plane congestion.
- The signalling overhead caused by RAN user plane congestion management solutions in the system shall be minimized.
- The network shall be able to take into consideration the RAN user plane congestion status and the subscriber's profile when coping with traffic congestion.
27.3 Prioritizing traffic p. 67
- According to operator policy, during RAN user plane congestion the operator shall be able to select the communications which require preferential treatment and allocate sufficient resources for such communications in order to provide these services with appropriate service quality.
- According to operator policy, the network shall be able to select specific users (e.g. heavy users, roaming users, etc.) and adjust the QoS of existing connections/flows and apply relevant policies to new connections/flows depending on the RAN user plane congestion status and the subscriber's profile.
27.4 Reducing traffic p. 67
- Based on RAN congestion status and according to operator policy, the network shall be able to reduce the user plane traffic load (e.g. by compressing images or by adaptation for streaming applications) taking into account UE related information (e.g. UE capabilities, subscription).
- The system shall be able to adjust the communication media parameters of real-time communications so that they consume less bandwidth.
27.5 Void
