hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.10.4 Impacts on services, entities, and interfaces | UE:
- Distinguish human Users and provide User Identifier of active human User in procedures.
- Receive merged Subscription data results (result code information) and inform human User.
AMF:
- Receive and forward User Identifier of active human User in procedures.
- Initiate Authentication/Security for UE and User Iden... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.11 Solution #11: Exposing user authentication result to 3rd parties | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.11.1 Key Issue mapping | This solution maps to KI#2 (Authentication of users) and KI#3 (Exposure of user identity functionality). |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.11.2 Description | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.11.2.1 Scenario and use cases | The following solution discusses the scenario as per the use case 5.2 as mentioned in TR 22.904 [8].
Use case involves a 3rd party entity (e.g. a bank) requesting for an authentication service (or second-factor authentication) via operator.
Using traditional SMS-OTP for second factor authentication provided security ri... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.11.2.2 Entities | User Information Database Function (UIDF): This NF can store the specific aspects related to a User ID. The user profile for a particular User ID also store a reference to the UE subscription(s) (i.e. SUPI(s)) that are linked to the particular User ID. It is essential that the User profile is stored separately from the... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.11.2.3 Solution summary | Consider the case when a user is (using a UE) is using 3rd party application (e.g. Bank) which requires 2nd factor authentication.
In order to get verification, for the corresponding user identified by the User ID; 3rd party request the Operator (via NEF) to start user authentication and verify whether an actual human ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.11.3 Procedures | Figure 6.11.3-1: 3rd party application requesting User authentication
1. A User which has credentials for UID-1 and has access to the particular UE (which is identified by IMSI-A to the operator). The user logs-in to the application using bank id and password. The bank application requests for secondary authentication,... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.11.4 Impacts on services, entities and interfaces | NEF:
- impacts on new service for verification for user authentication
UDM:
- impacts handling NEF request for User authentication at a particular UE and triggering the authentication for a User ID at the particular UE.
UE:
- impacts for providing the credentials related to a particular User ID to the network and perfo... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.12 Solution #12: User Identity Profile Server based control | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.12.1 Key Issue mapping | This solution addresses KI#2 and KI#3. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.12.2 Description | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.12.2.1 User Identity Profile | The User Identity Profiles (UIPs) are stored in a UIP Server. The principles for the UIP Server are as follows:
1. The UIPs can be managed, e.g. created, updated, and removed, by the PLMN operator.
2. The UIPs can be managed, e.g. created, updated, and removed by trusted server (Portal) or by the UE/user, and in such c... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.12.2.2 Architecture | The architecture below shows an architecture for roaming (Figure 6.12.2.2-1) and one for non-roaming (Figure 6.12.2.2-2).
The interface between the UE and the Portal is assumed to be an application layer interface out of scope of 3GPP.
The Xuips interface between the UIP Client and the UIP Server is assumed to be on ap... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.12.2.3 Authentication and Authorization | The UIP management procedures are performed from an authorized and authenticated entity.
The User Identifier associated with the UIP is authenticated at the UIP management procedures e.g. for creating, removing an Identifier Link (link and unlink), and activating an Identifier Link.
NOTE: Security requirements are to b... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.12.3 Procedures | Editor's note: The high-level procedures and information flows for the solution is FFS. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.12.4 Impacts on services, entities and interfaces | Editor's note: Further impacts is FFS including which NFs are to receive UIP information.
UIP Server:
- A new server containing the User Identity Profiles, outside the 5GC.
5GC NF/NEF:
- Impacts to (new or existing) service operations to transfer User Identity Profile information from the UIP server to the 5GC.
UE:
- S... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.13 Solution #13: Authentication & Authorization of Users in 5GC in Control or User Plane | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.13.1 Description | This solution proposes to introduce two network functions into 3GPP Packet Core architecture:
- User Information Database Function (UIDF): This NF holds user's profile information, authentication information etc. and is responsible for authenticating the user. This entity is independent from the UDR/UDM, which hold UE ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.13.2 Procedures | A) Control-Plane:
Following is the high-level sequence of events with this method.
Figure 6.13.2-1
1. UE is already Registered with the network.
2. A User (e.g. a human user) triggers the device access using implementation specific methods (e.g., by tapping on an option in an App).
3. UE sends a User Authentication and... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.13.3 Impacts on Existing Nodes and Functionality | This solution may have the following impacts to existing entities and interfaces:
SMF:
For control plane procedure:
- Support new NAS message and/or changes to PDU Session Establishment/Modification Messages.
- Selection of UAF.
- UE subscription validation against User Identities (optional).
- Providing User Identity ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.14 Solution #14: Restriction on the usage of user identifier | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.14.1 Description | In the scenario when human user access the 5G services by using identifier there is a need for 5GC to ensure that at any point of time, only one human user is availing the service through a single subscription. Also, there will be some use cases like in some location, roaming where the user identifiers all not allowed ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.14.2 Procedures | The procedure for restriction on the usage of user identifiers.
Figure 6.14.2-1
0. UDM already has been provisioned with user identifier information associated with the subscription.
1. UE send Registration Request with capability indication of supporting User Identifier.
2. AMF gets the subscriber data from UDM along ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.14.3 Impacts on Existing Nodes and Functionality | This solution may have the following impacts to existing entities and interfaces:
UE:
- will send its capability indication of supporting User Identifier.
- will enforce by deactivating user plane packets and not triggering any new SM request when outside of the service area where a particular user identifier is not al... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.15 Solution #15: User Identity profile information verification and authentication results exposure | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.15.1 Key Issue mapping | This solution addresses KI#3 "Exposure of User Identity Profile Information". |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.15.2 Description | This solution assumes the following:
- The procedures for configuring and provisioning User Identifiers to UE are out of SA WG2 scope (for example, obtaining Blinded tokens through application layer, provisioning though USIM Application).
- How the user instructs UE to use a particular User Identifier is up to UE imple... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.15.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.15.3.1 Verification of User Identifier associated with a subscription | An AF requests NEF to verify contents of User Identity Profile and NEF would respond with a 'Verified Successfully' or 'Not Verified' answer.
Pre-conditions: A user has registered a User Identifier with a UE subscription in 5GC. The UDM has marked the User Identifier as the active User Identifier for the UE subscriptio... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.15.3.2 Exposure of Authentication Results | In addition to the procedure described in clause 6.15.3.1, the authentication results may be exposed by using existing Nnef_EventExposure service operations as described in this clause.
Figure 6.15.3.2-1
1. AF subscribes to the following event notifications, and provides the associated notification endpoint of the AF b... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.15.4 Impacts on services, entities and interfaces | NEF:
Provides a service to:
- Verify whether a User Identifier or components of User Identity Profile is linked to 3GPP subscription of the UE (identified by a UE IP address or GPSI).
- monitor authentication results of a User Identifier with the given UE.
- Subscribes to notifications about the authentication, authori... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.16 Solution #16: Exposure services for User Identifiers | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.16.1 Key Issue mapping | This solution addresses exposure of User Identifier related functionality and information, and the problem statement is further described as part of KI#3. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.16.2 Description | When the User Identifiers use the 5GS through the UE, they access various services. These users use the services after they are authenticated and authorized.
As defined in KI#3, User Identifier information is required to be exposed. 5GS should support exposure of content of the User Identity Profile, authorization/auth... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.16.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.16.3.1 Exposure of User Identifier profile details | As per the above parameters detailed in clause 6.16.2, this clause describes further on how an AF requests and receives information related to User Identifier details.
Assumption here is that UDM stores the User Profile details along with UE Subscription data. It could be possible that UE Subscription and User Profile ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.16.3.2 Exposure of Authentication and Authorization historical Results | As per the above parameters detailed in clause 6.16.2, this clause describes further on how an AF requests and receives information related to Authentication and Authorization details.
The AF uses the Nnef UIA Service Get of the NEF, and the NEF in turn invokes Nnwdaf_DataManagementService Fetch towards NWDAF.
The quer... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.16.4 Impacts on services, entities, and interfaces | UDM:
- Signalling changes.
- Support of User Identifier exposure aspects.
NEF:
- Signalling changes.
- User Identifier exposure services corresponding to Profile and Authentication / Authorization results.
NWDAF/ADRF:
- Signalling changes.
- Storage of Authentication and Authorization results.
- Exposure of UIA results... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.17 Solution #17: Identifying the User of UE based on User Identity Profile stored in the UDM | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.17.1 Key Issue mapping | This solution addresses Key Issue #1, #2 and #3. Especially to focus the following bulletins in the above Key issues.
For the Key issue #1:
- requirements related to the User Identifiers e.g. scope of uniqueness and how they are assigned,
- what information is stored as part of the User Identity Profile (e.g. a User Id... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.17.2 Functional Description | In this solution, it is assumed that:
- a User Identifier is unique at least within the operator's network.
- When the user identifier applies to a User, only a single user identifier is active with a UE subscription at a given time.
- A user is considered active if the associated user identifier has been authenticated... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.17.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.17.3.1 AF provisioning | Figure 6.17.3.1-1 provides a high-level procedure of User Identifier information Provisioning.
Figure 6.17.3-1: Provisioning of User Identity Profile
In this procedure, the AF provisioning create the linkage between the User ID with SUPI.
Editor's note: Whether AF provisioning and Link/unlink need to be separated is FF... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.17.3.2 User identifier activation. | Figure 6.17.3.2-1 provides a high-level procedure of User Identifier activation.
Figure 6.17.3-2: User ID activation
1. The UE is registered with 5GS.
2. The User determine to use a User ID.
This step is up to implementation.
3. The UE sends User ID Activation request with User Identifier. This request may be carried i... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.17.3.3 Notifying the PDU session | Figure 6.17.3.3-1 provides a high-level procedure on how to notify the SMF of existing PDU session and future PDU session.
Figure 6.17.3-3: Notify the User ID to SMF
1. The UE initiates a PDU session establishment according to clause 4.3.2.2.1 of TS 23.502 [5].
2. The SMF find that there is UserID indication in the SM ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.17.4 Impacts on existing services, entities and interfaces | UE:
- support User Identifier activation during the Registration (or other NAS procedure).
AMF:
- support authentication procedure of the User identifier.
UDM/UDR:
- create/update the User Identity Profile, Link with UE subscription.
- enforce only one active UE for one SUPI.
- store of User Identity Profile to UDR.
SM... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.18 Solution #18: Supporting user identifier of human in 5G system with User Profile Server | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.18.1 Key Issue mapping | This is a Key Issue #1 solution. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.18.2 Description | This solution resolves Key Issue #1 Identifying the Human User of a Subscription. In this solution it is assumed that human user obtains the unique User Identifier via application registration to a dedicated User Profile AF/AS owned by operation or third party. During the application registration, the necessary paramet... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.18.3 Procedures | Depicted in Figure 6.18.3-1 is the high-level procedures for User Identity Profile creation and link with UE subscription.
Figure 6.18.3-1: High-level procedures for User Identity Profile creation and link with UE subscription
1. User performs application registration to dedicated User Profile Server to provide necessa... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.18.4 Impacts on services, entities and interfaces | UDM/UDR:
- Support creating the User Identity Profile. Support link/unlink the User Identifier with UE subscription.
User Profile AF/AS:
- Support application registration for User to create User Identity Profile
- Support provisioning the parameters of User Identity Profile to 5GC to create User Identity Profile in UD... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.19 Solution #19: User Profile creation within an operator's realm | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.19.1 Key Issue mapping | The solution addresses Key Issue #1 and aspects of Key Issue #2 and #3. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.19.2 Description | The procedure to create a User Profile associated with a 3GPP (mobile) subscription is as follows. It is based by introducing a new function in a 5G Core (5GC) network, called User Identity Management Function (UIMF). The UIMF is accessible by a device either via the 5GC network or via the Internet, i.e. by using any a... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.19.3 Procedures | The figure below shows how the user can utilize the MNO Application and interact with UIMF for creating a new User Profile that is linked with his/her mobile subscription. The device shown in the figure could be a typical smartphone equipped with a USIM module, or any USIM-less device, such as tablet, laptop, PC, etc.
... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.19.4 Impacts on services, entities and interfaces | New function to create user profiles and associate profile to a 3GPP subscription
Potentially new NEF service to receive information about user profiles
UDR:
- Storing user profile information |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.20 Solution #20: Policy Enhancement for user ID | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.20.1 Key Issue mapping | This solution is related to KI#1:
- What information is stored as part of the User Identity Profile (e.g. a User Identifier, associated security credentials, associated devices, user specific QoS settings). Including how User Identity Profiles are created/acquired, stored, and updated.
- Whether and how user specific p... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.20.2 Description | The user ID is used to identify the user and the user ID may be taken into account by the 5GS in order to provide service differentiation.
In this solution, two policy enhancement are introduced:
- When the user ID in UE is activated, the UE updates the user ID to PCF via either control plane (by UL NAS message to AMF ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.20.3 Procedure of Policy enhance for user ID | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.20.3.1 Procedure 1: URSP rule enhancement procedure | The procedure is the same as in section 4.16.11.1 of TS 23.502 [5] with the following changes:
1. The AMF receives the updated user ID reported by UE and establishes UE Policy Association with the PCF including the user ID. The user ID is the ID that currently used or log in UE.
2-5. The same procedure as in step 2-5 i... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.20.3.2 Procedure 2: SM policy generation based on user ID | The procedure is the same as in section 4.16.4 of TS 23.502 [5] with the following changes:
1. The SMF requests to establish an SM Policy Association with the PCF by invoking Npcf_SMPolicyControl_Create operation, including information about the PDU Session as specified in clause 5.2.5.4.2 and the user ID that UE curre... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.20.4 Impacts on services, entities and interfaces | UE:
- Report the activated user ID to 5GC.
PCF:
- Generate and provide the user ID specific URSP rules or PCC rules according to the user ID reported from UE.
UDR:
- Stores the policy data related to user ID.
AMF, SMF:
- Reports the active user ID in UE to PCF and request the policy related to this user ID.
No RAN impa... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.21 Solution #21: Transition of states when different User(s) or UE Subscription uses the UE for Network Access. | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.21.1 Key Issue mapping | This solution addresses KI #1 related to WT #1. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.21.2 Description | The principles related to secure fetch of User Identities from the UE, Authentication and Authorization remains same as detailed in Solution 10. Hence below sections do not repeat these aspects, for better readability and clarity and thus confines to the problem statement that the solution is addressing.
Brief of the s... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.21.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.21.3.1 Access by different User Identities (or UE Subscription) | Figure 6.21.3-1: Procedure for transitioning from one User Identity or UE Subscription to Other User Identity or UE Subscription
1-2. UE Subscription registers to the network with or without the User Identity. AMF maintains the corresponding UE Subscription or User Identity as ACTIVE.
3. The AMF and UE may maintain the... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.21.4 Impacts on services, entities, and interfaces | UE:
- UE implements receiving of DEREGISTER LITE indication when the registration of a new User Identity Profile is done.
AMF:
- Maintaining of ACTIVE or INACTIVE state of the UE and User Identity Profiles.
- Switching from one User Identity Profile to another. (or to from a UE Subscription alone).
- When UE re-logs in... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.22 Solution #22: Solution for Unlinking User Identifier with UE | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.22.1 Key Issue mapping | The solution addresses Key Issuse #1. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.22.2 Description | The solution to KI#1 will address:
- whether and how the 5GC supports identifying the User Identifier that is associated with a UE's traffic, and
- whether and how User Identifiers are linked and unlinked (i.e. associated) with 3GPP subscriptions in an operator-controlled manner.
In this study is assumed that only one ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.22.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.22.3.1 General | In this solution, separate procedures are provided for the two different scenarios. Clause 6.22.3.2 describes the procedure for new user logs in, while clause 6.22.3.3 describes the procedure for current user identifier's de-registration. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.22.3.2 Procedure for Activation of new user ID with UE | This procedure takes place when a new User identifier is linked to the UE.
Figure 6.22.3.2-1: Procedure for activation of new user ID with a UE
0. The User with User ID#1 requests to be linked to the UE. The authentication and authorization procedure is performed. When the User ID#1 is authenticated and authorized succ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.22.3.3 Procedure for current user ID deactivation of User ID from a UE | This procedure takes place when a user request to unlink a User Identifier with the UE (e.g. log out the user identifier).
Figure 6.22.3.2-1: Procedure for current user ID deactivation of User ID from a UE
1. The User may perform unlinking with the UE (e.g. User performs log out). This step is outside the 3GPP scope.
2... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.22.4 Impacts on services, entities and interfaces | UE:
- Trigger the user ID deactivation from a UE procedure by sending the NAS message including indication of User Unlink and User ID.
AMF:
- Trigger the PDU Session release procedure after identifying an activation of a new User ID with a UE or a current User ID is deactivated with a UE. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.23 Solution #23: AF based human User Identity management | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.23.1 Key Issue mapping | This solution addresses KI #1 and KI #2. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.23.2 Description | This solution assumes one or more User Identity Application Server (UIAS) is deployed by mobile operator or third party service provider for the management of human User Identity. If the UIAS is deployed by the third party service provider, a NEF may be applied for the interworking with 5GC.
The creation/modification/d... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.23.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.23.3.1 Creation/Modification/Deletion of human user identity | Figure 6.23.3.1-1: Human user identity creation/updating/deletion procedures
0. The human user interacts with UIAS via application layer (e.g., Web page, UE applications) for the creation/updating/deletion of User Identity. How the human user interacts with UIAS for the User Identity configuration and corresponding use... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.23.3.2 Activation/Deactivation of User Identity with UE | Figure 6.23.3.2-1: Procedures of User Identity activation/deactivation in a UE
0a. NF (e.g., AMF, SMF, PCF) subscribes to UDM notifications of UE Subscription data updates.
0b. A secure application session is established between the UE application and UIAS.
During the establishment of application session, UE derives an... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.23.4 Impacts on services, entities and interfaces | UDM impact:
- Receive the request of Create/Update/Delete User profile from UIAS or NEF;
- Create/Update/Delete User profile in the user subscription data;
- Receive the request of User Identifier activation/deactivation in a UE;
- Update the UE subscription for activation/deactivation of User Identifier;
- Subscribe/n... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.24 Solution #24: UID <-> SUPI association | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.24.1 Key Issue mapping | KI#1-3. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.24.2 Description | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.24.2.1 general | In 5GC, everything related to a UE/User is identified using a SUPI. If SUPI is not used to identify the current user, but some other identity, there are incalculable consequences to all existing features. By re-using SUPI all existing features of 5GC will work. For example, event exposure related to a UE, charging, sub... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.24.2.2 Sort of virtual SUPI | The main principle of this method is that the UID is linked to a SUPI (sort of a virtual SUPI). Thus, more or less existing data structures for subscriptions in UDM can be re-used.
Figure 6.24.2.2-1: subscription association
To start with, the user needs to get a UID. This can be e.g. via an operator portal where the u... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.24.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.24.3.1 Association of SUPIs | In the procedure below, user B is the owner of the UE, and user A is the user which will use a UID to login to 5GC. SUPI-B belongs to user B and SUPI-A belongs to user A. Before the user B can use his/her UID, the 5GC (UDR), and UID server needs to be populated with the data of user A (SUPI, subscription data) as descr... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.24.4 Impacts on services, entities and interfaces | UE:
- support of allowing another user (than the owner) to access the ME
- support connection to the authentication server
- separation of data associated to different users
- support download of SUPI of another user
SMF:
- authenticate the UID based on secondary authentication, if NAS signalling is used
UDM for method... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.25 Solution #25: Format of Operator Assigned and 3rd Party Assigned User Identifiers | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.25.1 Key Issue mapping | This solution addresses Key Issue #1 "Identifying the Human User of a Subscription". |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.25.2 Description | This solution describes how the user identifier can be formatted such that an NF can determine the identity of the user profile that is associated with the user identifier or determine the identity of the NF that stores the user profile.
Per the assumption in clause 4.1: "The User Identifier and any subscription that i... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.25.3 Procedures | Network Functions can be locally configured with information that can be used to resolve a User Identity Profile or can use the NRF to determine the User Identity Profile.
For example, when the user identifier is operator assigned, the Nnrf_NFDiscovery_Request service operation inputs can include the field from the NAI... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.25.4 Impacts on services, entities and interfaces | An NF that needs to resolve a User Identity Profile:
- are locally configured with information that is used to resolve the User Identity Profile; or
- can use the NRF to determine the User Identity Profile. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.26 Solution #26: User identity profile influence on AM, SM and UE policy | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.26.1 Key Issue mapping | The solution addresses the following requirements from the Key Issue #1:
- what information is stored as part of the User Identity Profile (e.g. a User Identifier, associated security credentials, associated devices, user specific QoS settings). Including how User Identity Profiles are created/acquired, stored, and upd... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.