Content for  TS 22.101  Word version:  18.6.0

Top   Top   Up   Prev   Next
1…   4…   5…   10…   11…   13…   21…   24…   26a…   28…   30…   A…   A.19…   B…


26a  User Identity |R16|p. 64

26a.1  Introductionp. 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  Requirementsp. 64

26a.2.1  User Identifiers and user authenticationp. 64

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.

26a.2.2  Access to servicesp. 64

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.4  Operator requirementsp. 64

The operator shall be able to enable or disable the use of a User Identifier in his network.

26a.2.5  Privacy requirementsp. 64

The 3GPP system shall protect the privacy of the user by transferring to a service only User Identity information that is necessary to provide the service and for which the user has consented to when registering for the service.

27  User plane congestion management |R13|p. 65

27.1  Introductionp. 65

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  Generalp. 65

  1. 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.
  2. The network shall be able to identify whether or not an active UE is in a RAN user plane congested cell.
  3. The network operator shall be able to configure or provision and enforce policy rules to best deal with RAN user plane congestion.
  4. 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.
  5. The signalling overhead caused by RAN user plane congestion management solutions in the system shall be minimized.
  6. 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 trafficp. 65

  1. 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.
  2. 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 trafficp. 65

  1. 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).
  2. The system shall be able to adjust the communication media parameters of real-time communications so that they consume less bandwidth.


Up   Top   ToC