Content for TR 23.700-32 Word version: 19.0.0

3.1 Terms 3.2 Symbols 3.3 Abbreviations 4.1 Architectural Assumptions 4.2 Architectural Requirements
...

1 Scope p. 10

The present document studies how to enhance the 5G System to allow for the creation and utilization of user-specific identities in order to provide enhanced user experience, optimized performance, and offer services to non-3GPP devices and human users. For example, network settings can be adapted, and services can be offered to users according to users' needs, which may be different from the subscription identifier that is used by the user to establish the connection.

In this study, the user to be identified could be an individual human user using a UE with a certain subscription or a device behind a gateway UE or 5G-RG.

Use cases are discussed in clause 26a of TS 22.101 and include:

an individual human user, using a UE with a certain subscription; and
a device ("thing") behind a gateway UE.

Requirements related to the collection of charging information for users are specified in clause 5.2.17 of TS 22.115.

2 References p. 10

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 22.101: "Service aspects; Service principles".

[3]

TS 22.115: "Service aspects; Charging and billing".

[4]

TS 23.501: "System Architecture for the 5G System (5GS); Stage 2".

[5]

TS 23.502: "Procedures for the 5G System; Stage 2".

[6]

TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".

[7]

TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".

[8]

TR 22.904: "Study on user centric identifiers and authentication (Release 16)".

[9]

TS 33.501: "Security architecture and procedures for 5G System".

[10]

RFC 7542: "The Network Access Identifier".

[11]

Liaison Statement from IEEE 802.11: "Working Group to Wireless Broadband Alliance", https://www.ieee802.org/11/Liaisons/2024-01-04-Liaison%20statement%20from%20IEEE%20802-11%20Working%20Group%20to%20WBA%20re%20P802.11bh.pdf.

[12]

TS 33.535: "Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS)".

[13]

TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2".

[14]

Broadband Forum TR-069: "CPE WAN Management Protocol".

[15]

Broadband Forum TR-369: "The User Services Platform".

[16]

Broadband Forum TR-181: "Device Data Model for CWMP Endpoints and USP Agents".

[17]

TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".

[18]

RFC 6749: "The OAuth 2.0 Authorization Framework".

3 Definitions of terms, symbols and abbreviations p. 11

3.1 Terms p. 11

For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

The terms Gateway UE, User, User Identity, User Identifier, and User Identity Profile are defined in clause 3.1 of TS 22.101.

Identifier Link:

An association between a User Identifier (or User Identity Profile) and a 3GPP Subscription.

3.2 Symbols p. 11

For the purposes of the present document, the following symbols apply:

3.3 Abbreviations p. 11

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

UIP

User Identity Profile

4 Architectural Assumptions and Requirements p. 11

4.1 Architectural Assumptions p. 11

The architecture in this study should be based on the following assumptions:

The architecture, framework and the QoS model as specified in TS 23.501, TS 23.502, and TS 23.503 are regarded as the baseline for this study.
Subscriber/subscription information will not be moved into a user profile and information from the user profile should not be used to override information in a subscription. For example, the slices and DNNs that are available to the UE do not change based on the user of the UE.
The subscription is a 5GS subscription.
When the user identifier applies to a human, only a single user identifier is active with a UE subscription at a given time and it is assumed that the specific user identifier is associated with all of the UE's traffic during the time that specific user identifier is active with the UE's subscription.

NOTE 1:
The identifier of the non-3GPP devices in this study might not be called a "user identifier". A different name may be selected during the study.

NOTE 2:
A user is considered active if the associated user identifier has been authenticated and authorized to use a linked subscription to access the 5GS.

NOTE 3:
It is assumed that the non-3GPP devices do not support 5G-AKA authentication procedures nor separate NAS connections with the 5GC for each non-3GPP device (e.g. like for AUN3 devices).
The User Identifier and any subscription that it links to are assumed to be associated with the same PLMN (e.g. the operator that manages the User Identifier and the operator that manages the subscription is assumed to be the same).
For the case of non-3GPP device(s) behind a UE or 5G-RG, how a user identifier and any associated credentials are provisioned in a non-3GPP device, UE, or application is assumed not in scope of this study (e.g. the credentials need to be provisioned in the non-3GPP device by an operator, human user, or a 3rd party).
Application layer interaction between an application client of the UE and application server is assumed not in scope of this study.

4.2 Architectural Requirements p. 12

Service Requirements for User Identifiers are specified in clause 26a of TS 22.101.

The following architectural requirements are applicable to this study:

The Architecture should enable a subscriber to be able to link and unlink one or more User Identifiers with the subscriber's 3GPP subscription.
The Architecture should be able to take User Identifier specific service settings and parameters (e.g. user specific QoS settings) into account when delivering a service.
The Architecture should be able to store and allow for an update of User Identifier related data.
The Architecture should allow for the creation of a User Identity Profile that is associated with a User Identifier which needs to be linked to subscriber/subscription information before it can be used to access the network.
When the user identifier applies to human, the 5GS should be able to support user authentication for a User Identifier (e.g. when requested by a 3rd party or to identify the current active user for an UE).
The user identifier is at least unique within a PLMN.