hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.44.2.2 MT control plane data transfer in S&F operation mode | The call flow below illustrates how MT data is transmitted to UE in S&F mode.
Figure 6.44.2.2-1: High-level procedure for MT data transport in S&F mode
Precondition: the SAT eNodeB is in the S&F Monitoring List and has obtained the UE related context or needs to obtain it in step 3 from MME, e.g. AS security (if is use... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.44.2.3 MO control plane data transfer in S&F operation mode | The call flow below illustrates how MO data is transmitted from the UE in S&F mode.
Figure 6.44.2.3-1: High-level procedure for MO data transport in S&F mode
Precondition: the SAT eNodeB is in the S&F Monitoring List and has obtained the UE related context or needs to obtain it in step 3 from MME, e.g. AS security (if ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.44.2.4 Negotiation of S&F Monitoring List | The call flow below illustrates the S&F Monitoring List negotiation procedure in S&F operation mode.
Figure 6.44.2.4-1: High-level procedure for S&F Monitoring List negotiation
Precondition: When the S1-AP connection between eNodeB and MME is established, the eNodeB sends its remaining storage space size to the MME.
1.... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.44.3 Impacts on services, entities and interfaces | MME:
- Determines UE's S&F Monitoring List for power saving and S&F data quota reservation during Attach/TAU procedure.
- Activates S&F mode base on UE's subscription.
- Sends UE context and NAS PDU Data to RAN before UE is reachable.
RAN:
- Determines target RAN based on ephemeris and UE location.
- Generates a next a... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.45 Solution#45: Support SMS in S&F satellite operation | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.45.1 Introduction | This solution corresponds to KI#2 to enable SMS services with store and forward satellite operation. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.45.2 Description | In this solution, the SMS delivery over satellite which support store and forward feature is supported based on the enhanced architecture of SMS in MME described in Annex C of TS 23.272 [18], and based on the enhanced procedures of short message transfer described in Figure 17 a) of TS 23.040 [19]. The enhanced archite... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.45.3 Procedures | Editor's note: MO SMS Delivery procedure and support for multiple satellites are FFS. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.45.3.1 MT SMS Delivery via SMS-GMSC on satellite | Based on Figure 17a) of TS 23.040 [19], the MT SMS message is delivered as described in Figure 6.45.3.1-1 with following differences:
- The SMS-GMSC is located both in the ground and in the satellite.
- The MS SMS message and the Delivery Report of MT SMS are stored in SMS-GMSC until the service link or the feeder link... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.45.3 Impacts on Existing Nodes and Functionality | The following impacts are foreseen by this solution:
MME:
- The MME checks the service link connectivity, and determines and provides the requested retransmission time to SMS-GMSC (SAT).
- The MME checks the feeder link connectivity, and determines and provides the available time for feeder link to SMS-GMSC (SAT).
SMS-... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 7 Overall Evaluation | Editor's note: This clause will provide evaluation of different solutions. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 7.1 Solution grouping for Key Issue #1: Support of Regenerative-based satellite access | There are 14 candidate solutions (solutions #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #34, #35, #36, #42) for this KI, they can be divided into two categories based on the architecture impact:
- Cat 1: solutions without any IWK/AMF agent/Proxy over NG/S1 interface (#1, #2, #3, #4, #5, #6, #7, #8, #34, #35, and #36)
- Ca... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 7.2 Key Issue #2 Principles for evaluation | It is proposed to evaluate the support of Store & Forward Satellite operation (key issue#2) following the principles below:
1. Support of single and multi-satellites.
2. Support of Roaming (the definition of roaming in S&F Satellite operation shall be clarified).
3. Support of MO/MT SMS service, CIoT CP/UP.
4. UE locat... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 8 Conclusions | Editor's note: This clause will list conclusions that have been agreed during the course of the study item activities. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 8.1 Conclusion for KI#1: Support of Regenerative-based satellite access | The conclusion for supporting gNB/eNB on-board the satellite is based on the following principles:
- When the eNB/gNB leaves the service area of an AMF/MME (e.g. when setting over the horizon) any new procedures or updates to existing procedures to handle the N2/S1 connection will be defined by RAN WG3. SA WG2 will ali... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 8.2 Conclusion for KI #2: Support of Store and Forward Satellite operation | NOTE 1: Whether to have a full CN onboard the satellite or Split MME architecture is up to the operation deployment.
NOTE 2: The security issues (if any) of these conclusions are in the scope of SA WG3.
NOTE 3: The LI issues (if any) of these conclusions are in the scope SA WG3-LI.
NOTE 4: The deployments are subject t... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 8.3 Conclusion for KI#3: Support of UE-Sat-UE communication | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 8.3.1 General | The following bullet points summarize the principles for the way forward to support UE-Sat-UE communication in regenerative architecture:
- Only IMS voice/video services are considered in this release.
- Both UEs are served by the same HPLMN.
- A ground UPF is selected and acts as an PSA UPF during the IMS PDU session,... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 8.3.2 Ground Fallback Option | When, e.g. due to the change of the satellite serving one of the two UEs involved in a UE-Satellite-UE Communication, the IMS PDU Session and IMS call needs to be reconfigured, as an option: - the UE-SAT-UE communication is disabled and ground-based PSA UPF and AGW are used. - the P-CSCF is notified to reselect the AGW... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 1 Scope | 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 o... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 2 References | 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.
- Fo... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 3 Definitions of terms, symbols and abbreviations | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1] 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 [1].
The terms Gateway UE, User, User Identity, User Identifier, and User Identity Profile are defined in... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] 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 [1].
UIP User Identity Profile |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 4 Architectural Assumptions and Requirements | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 4.1 Architectural Assumptions | 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 [4], TS 23.502 [5], and TS 23.503 [6] are regarded as the baseline for this study.
- Subscriber/subscription information will not be moved into a user profile and inform... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 4.2 Architectural Requirements | Service Requirements for User Identifiers are specified in clause 26a of TS 22.101 [2].
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 Architect... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 5 Key Issues | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 5.1 Key Issue #1: Identifying the Human User of a Subscription | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 5.1.1 Description | This key issue focuses on how to support identifying the human user of a UE's 3GPP subscription when the human user access services via the 5GS using a user identifier. Solutions to this key issue will address:
- whether and how the 5GC supports identifying the User Identifier that is associated with a UE's traffic,
- ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 5.2 Key Issue #2: Authentication and Authorization of Users and Restrictions on Users | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 5.2.1 Description | This key issue builds on the identifying human user case of key issue #1 and focuses on how users are authenticated and authorized and how the network restricts User Identifiers. Solutions to this key issue will address:
- how are users authenticated and how and for what are users authorized;
- how the network restrict... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 5.3 Key Issue #3: Exposure of User Identity Profile Information | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 5.3.1 Description | This key issue builds on the identifying human user case of key issue #1 and focuses on how User Identifier related functionality and information is exposed. Solutions to this key issue will address:
- what and how User Identity Profile information and functionality are exposed (e.g. exposure of the content of the User... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 5.4 Key Issue #4: Identifying non-3GPP Devices Connecting behind a UE or 5G-RG | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 5.4.1 Description | This key issue will study whether and how 5GC identifies individual non-3GPP devices connecting behind a UE or 5G-RG and whether and how to provide policy control for the traffic associated with individual non-3GPP devices.
The use case that is associated with this key issue is the case where non-3GPP devices behind a ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6 Solutions | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Solutions
<Key Issue #1>
<Key Issue #2>
<Key Issue #3>
<Key Issue #4>
#1
X
X
X
#2
X
#3
X
X
#4
X
#5
X
X
#6
X
#7
X
#8
X
#9
X
#10
X
X
#11
X
X
#12
X
X
#13
X
#14
X
#15
X
#16
X
#17
X
X
X
#18
X
#19
X
X
X
#20
X
#21
X
#22
X
#23
X
X
#24
X
X
X
#25
X
#26
X
X
#27
X
#28
X
#29
X
#30
X
#... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.1 Solution #1: Identifying traffic corresponding to a human user during PDU session establishment | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.1.1 Key Issue mapping | The solution addresses Key Issue 1 aspects of Key Issue 2 and 3. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.1.2 Description | The solution assumes that there is User Profile information stored in the UDR
User Profile information is available in AM subscription, SM subscription data and Policy control subscription data and includes one or more of the following:
- A User Profile Reference ID that uniquely identifies the User Profile among all U... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.1.3 Procedures | The procedure is shown below:
Figure 6.1.3-1: User specific PDU establishment request
0a. The UE registers to the network based on the Registration procedure described in clause 4.2.2.2 of TS 23.502 [5].
0b. During registration the AMF retrieves from the UDM the subscription data which includes a list of User Profiles ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.1.4 Impacts on services, entities and interfaces | - UE includes during PDU session establishment request user identifier information
- During PDU session establishment request:
- AMF retrieves from UDM during PDU session est., user profile associated with user identifier and determines if user/device is allowed.
- SMF retrieve from UDM/UDR authentication data to authe... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.2 Solution #2: Support of User Identification in 5GS | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.2.1 Key Issue mapping | This is a solution for KI#1. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.2.2 Description | This solution meets the following architecture assumptions outlined in clause 4.1:
- 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 wit... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.2.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.2.3.1 PDU Session Establishment procedure for specific user identifier | Figure 6.2.3.1-1 provides a high-level procedure of PDU session establishment for specific UID to support identifying the human user of a UE's 3GPP subscription when the human user access services via the 5GS using a User Identifier (UID).
Figure 6.2.3.1-1: High-level procedures to support identifying the human user of... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.2.3.2 User State | A user may be considered active if the associated user identifier has been authenticated and authorized to use a linked subscription to access the 5GS. To better use 5G network resources, it is beneficial to have some procedures to determine user states.
The UDR may include a new Data Subset "User State Data". Associat... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.2.3.3 Linking and Unlinking | Figure 6.2.3.3-1: Registration to begin Association of a User to a Subscription
1. The AF sends a Link Request to the NEF. The request includes a User Identifier, a subscription identifier (e.g. a SUPI or External ID), and an indication of whether the request is to "link" or "unlink".
2. The NEF invokes the Nudm_UIP_Mo... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.2.4 Impacts on services, entities and interfaces | UE:
- Detect UID state change.
- Handle UID during PDU session procedures.
SMF:
- Handle UID during PDU session procedures.
- Determine UID state.
AMF:
- Determine UID state based on UE report and UE context.
PCF:
- Handle UID specific rules and policies.
UDM/UDR:
- Handling of User Identity Profile, including storage ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.3 Solution #3: Identifying the Human User of UE based on User Identity Profile stored in the UDM | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.3.1 Key Issue mapping | This solution addresses Key Issue #1 and Key Issue #2. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.3.2 Description | In this solution, it is assumed that a User Identifier is unique at least within the operator's network.
The User Identity Profile contains following information:
- A User Identifier.
- credentials for authentication of the User Identifier.
- Specific service settings and parameters.
- Linked 3GPP subscription (SUPI).
... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.3.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.3.3.1 Procedures for provisioning of User Identity Profile | Figure 6.3.3.1-1: Provisioning of User Identity Profile
1. If the AF wants to create/update/delete User Identity Profile, the AF provides User Identity Profile together with GPSI of linked 3GPP subscription by triggering Nnef_PrameterProvision_Create/Update/Delete service operation.
2. If the AF is authorized by the NE... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.3.3.2 Procedures for Activation of User Identifier | Figure 6.3.3.2-1: Activation of User Identifier
1. The UE is registered and established PDU Sessions without User Identifier. The procedure follows existing procedures.
2. The UE sends NAS message e.g. Registration Request by including User Identifier of the user.
NOTE 1: If Registration Request message is used and the... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.3.4 Impacts on services, entities and interfaces | UE:
- support handling of User Identifier during the Registration procedure.
AMF:
- support receiving User Identifier from the UE and triggers authentication.
- support registering the activated User Identifier.
SMF:
- support receiving User Identifier from the AMF and registering the PDU Session.
PCF:
- support receiv... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.4 Solution #4: Registration for a UE and a user | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.4.1 Key Issue mapping | The solution applies to Key Issue #1: Identifying the Human User of a Subscription. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.4.2 Functional Description | Assumptions:
- It is assumed that a UE and the UE's subscription may be used by multiple users. Such an UE is provided with an User Profile in the UDM linked to the UE's subscription profile. The User Profile can be provided in the UDM by the Operator or alternatively by a 3rd party Service Provider via the NEF. The Us... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.4.3 Procedures | Figure 6.4.3-1: Registration for a UE and a user
1. The User Profile is provided to the UDM by the operator or by the Service Provider via the NEF and linked to the UE's subscription information.
2. A user (e.g. user identifier-x) initiates registration procedure. In the Registration Request message the UE includes the... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.4.4 Impacts on existing services, entities and interfaces | UE, AMF:
- New parameters in the Registration Request and Registration Accept message.
AMF, UDM:
- User Profile handling. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.5 Solution #5: Authenticating a Human User and User Profile Storage in the UDM | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.5.1 Key Issue mapping | This solution addresses key issue #1, " Identifying the Human User of a Subscription" and key issue #2, " Authentication and Authorization of Users and Restrictions on Users ". |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.5.2 Description | According to the KI#1, the User Identity has its own profile, which may include a User Identifier, associated security credentials, associated devices, user specific QoS settings and so on. These parameters defined in the user profile will impact the PDU session control, e.g. the QoS control. When the human user access... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.5.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.5.3.1 User Identity authenticated by Secondary authentication procedure | This procedure describes the User Identity being authenticated by the Secondary authentication mechanism with enhancement for User Identity. When the authentication method indicates Secondary authentication, the User Identity is authenticated by DN-AAA.
Figure 6.5.3.1-1: User Identity authentication by secondary authen... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.5.3.2 User Identity authenticated by AUSF/UDM | This procedure describes the User Identity being authenticated by AUSF/UDM. When the authentication method indicates AUSF/UDM authentication, the User ID is authenticated by AUSF/UDM based on the credential defined in the user profile.
Figure 6.5.3.2-1: User Identity authentication by AUSF/UDM
1-4. The UE registers to ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.5.3.3 User Identity authorized without authentication procedure | This procedure describes the User Identity being authorized by UDM without authentication procedure when there is no security information in the user profile.
Figure 6.5.3.3-1: User Identity authorization without authentication procedure
1-4. The UE registers to the 5GC and triggers the PDU session establishment proced... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.5.4 Impacts on services, entities and interfaces | The solution has impact on the UE and some NFs, as follows.
UDM/UDR:
- Supports the User Identity Profile and enhancement of UE Subscription data for User Identity.
AUSF:
- Supports the authentication for User ID.
AMF:
- Supports SMF selection for User ID, and optionally checks if the User ID is allowed or not.
SMF:
- ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.6 Solution #6: Support of SMS over NAS for the active User Identifier | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.6.1 Key Issue mapping | This is a solution for key issue #1 "Identifying the Human User of a Subscription". |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.6.2 Description | In this solution, it is assumed that the User Identifier intending to use any allowed UE is authenticated and authorized by using other solutions for KI#2.
Editor's note: The required security mechanisms, e.g., user consent, verification and authorization of GPSI that subjects to SMS redirection require coordination wi... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.6.3 Procedures | Figure 6.6.3-1: Support of SMS over NAS for the active User Identifier
1. The UE performs registration procedure as specified in clause 4.13.3.1 of TS 23.502 [5]. Therefore, during the registration procedure, the UE includes an "SMS supported" indication in Registration Request to enable SMS over NAS transport and the ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.6.4 Impacts on services, entities and interfaces | AMF:
- Support to activate SMS activation for a user of a User Identifier using a UE.
SMSF:
- Support to register to UDM for a User Identifier using a UE.
- Support to retrieve SMS Management Subscription data for a User Identifier using a UE.
UDM:
- Support to store User Identity Profile.
- Support to provide SMS Mana... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.7 Solution #7: Solution for linking User identifier with a UE subscription via the authenticated UE channel | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.7.1 Key Issue mapping | This solution addresses KI#1 (linking of User ID). |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.7.2 Description | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.7.2.1 Overall scenario | Figure 6.7.2.1-1: Overall scenario
The figure illustrates a high level architecture for this solution. In this architecture, the service provider is assumed to support the existing OAUTH2 framework for User ID provider. The service provider pre-configures to the MNO with the OAUTH2's endpoint address for checking the U... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.7.3 Procedure | Figure 6.7.3-1: Procedure for UE linking with a User ID
0. A user using a particular application (on a UE already subscribed with the operator), The signalling between application and UE is out of scope.
1. Application server want to link its own User ID with the UE currently used by the particular User. It provides th... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.7.4 Impacts on services, entities and interfaces | UE impacts:
- Sending NAS message along with User ID and authentication token received from the application.
AMF/AUSF impacts:
- Receiving linking request from UE and invoking AMF to verify the linking request
UDM impacts:
- Storage of linked user id with a SUPI
UIDF:
- new core network function. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.8 Solution #8: User specific authentication | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.8.1 Key Issue mapping | The solution applies to Key Issue #2: Authentication and Authorization of Users and Restrictions on Users. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.8.2 Functional Description | Assumptions:
- It is assumed that a UE and the UE's subscription may be used by multiple users. Each User Profile may have attributes such as: List of S-NSSAI(s) - one or more S-NSSAI(s) which can be used by the user; QoS - allowed QoS level for the user; Secondary authentication - whether the user requires secondary u... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.8.3 Procedures | Figure 6.8.3-1: User specific authentication
1. After the standard UE authentication during the registration procedure, the AMF may trigger an user specific authentication when one or more users require user specific authentication with an AAA Server (AAA-S) which may be hosted by the HPLMN operator or a third party wh... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.8.4 Impacts on existing services, entities and interfaces | UE:
- Supports an EAP Authentication procedure between the user and AAA-S. The procedure is similar to the Network Slice-Specific Authentication and Authorization procedure of TS 23.502 [5] clause 4.2.9.2.
AMF:
- Supports an EAP Authentication procedure between the user and AAA-S. The procedure is similar to the Networ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.9 Solution #9: Solution for AMF based User ID authentication | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.9.1 Key Issue mapping | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.9.2 Description | The solution has the following assumptions:
- One SUPI is corresponding to one or more User IDs. The value of User IDs has been negotiated and preconfigured in UE, Core network, and AAA-Server.
- It is assumed each node performs the following functions for User-ID based authentication:
- UE: Peer.
- AMF: Authenticator.... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.9.3 Procedures | (Steps/Parameters for potential impact is in Italic)
Figure-6.9.3-1: User ID based authentication after initial registration
0. User-A switch on a UE and the UE performs initial registration
1. UE send initial registration including SUPI (Concealed as SUCI) and capability of User-Id based authentication
2. AUSF trigger... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.9.4 Impacts on services, entities and interfaces | UE:
- Send capability of User-Id authentication in registration request
- Support EAP peer and send EAP message via NAS
AMF:
- Support EAP authenticator
- Support determination of performing User-id authentication, sending EAP message via NAS
UDM:
- SUPI's Subscription indicates whether User-Id authentication is requir... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.10 Solution #10: Unique User Identifier for a Human User and how it is used in 3GPP procedures to associate the Human User with a UE | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.10.1 Introduction | This solution addresses and KI#2 "Authentication and Authorization of Users and Restrictions on Users".
The solution introduces a new unique User Identifier and specifies how the unique User Identifier is used in 3GPP procedures to associate a Human User with a UE dynamically. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.10.2 Functional Description | This solution is based on dedicated User profiles for the human Users and a UE Subscription profile for the UE (containing a USIM card). It is assumed that the potential human Users and the User owning the UE have individual contracts with a single MNO to ensure that the User profiles and the UE Subscription belongs to... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.10.3 Procedures | The dynamic association of a human User profile with a UE Subscription requires to extend the existing procedures defined in TS 23.502 [5] by adding the new user identification User Identifier (UserID) to the procedures. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.10.3.1 Registration procedure | In a first step, it is proposed to adapt the Registration procedure as specified in TS 23.502 [5], Figure 4.2.2.2.2-1 to perform the association of the UE subscription with the User profile. The adapted Registration procedure builds then the basis to generate the temporary merged Subscription data containing UE Subscri... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.10.3.2 Registration procedure supporting SMS over NAS | The AMF may run the procedure in Figure 4.13.3.1-1 of TS 23.502 [5]: Registration procedure supporting SMS over NAS. To support multiple Human Users of a UE this procedure is modified as shown in Figure 6.10.3.2-1.
Figure 6.10.3.2-1: Registration procedure supporting SMS over NAS for Human Users using a UE
1-2. Follows... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.10.3.3 Further procedures | Editor's note: The new User Identifier parameter identifying a Human User of a UE may be needed in other procedures e.g., PDU Session Establishment/Modification as well. The identification of these procedures is FFS. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.