Identification in a wireless communication network

The system addresses the challenge of managing multiple user profiles and active users in wireless networks by using User Identity Management Functions and Network Exposure Functions to associate user traffic with appropriate policies, ensuring efficient traffic management and user experience.

WO2024235825A1PCT designated stage Publication Date: 2024-11-21LENOVO (SINGAPORE) PTE LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2024/062867
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-04-04
Filing Date
2024-05-09
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current wireless communication networks face challenges in managing multiple user profiles per subscription and identifying the active user within the network, leading to difficulties in applying appropriate settings and policies for traffic management.

Method used

The implementation of a system that allows users to create multiple profiles linked to a single subscription, with the network identifying and managing active user profiles through User Identity Management Functions (UIMF) and Network Exposure Functions (NEF), enabling the association of user traffic with corresponding policies and settings.

Benefits of technology

This solution ensures that only one user profile is active at a time, allowing for efficient traffic management and policy application, enhancing network efficiency and user experience by accurately identifying and managing user profiles and traffic within the network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024062867_21112024_PF_FP_ABST
    Figure EP2024062867_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure relate to an apparatus for wireless communication. The apparatus comprises at least one memory and at least one processor coupled with the at least one memory and configured to cause the apparatus to: establish a first data connection with a remote unit, the first data connection associated with a mobile subscription in a mobile communication network; receive a first request from the remote unit via the first data connection, the first request including a first identifier identifying a first user; identify whether the first identifier is linked to both an existing user profile and the mobile subscription to determine whether the first identifier is valid; and in response to a determination that the first identifier is valid, send a second request to a first network function, the second request comprising the first identifier.
Need to check novelty before this filing date? Find Prior Art

Description

IDENTIFICATION IN A WIRELESS COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to the field of implementing identification in a wireless communication network. In particular, this document defines apparatuses and methods for wireless communication.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition Bwithout departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] There is provided an apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: establish a first data connection with a remote unit, the first data connection associated with a mobile subscription in a mobile communication network; receive a first request from the remote unit via the first data connection, the first request including a first identifier identifying a first user; identify whether the first identifier is linked to both an existing user profile and the mobile subscription to determine whether the first identifier is valid; and in response to a determination that the first identifier is valid, send a second request to a first network function, the second request comprising the first identifier.

[0005] There is provided an apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive a first request from a remote unit, the first request including a first identifier identifying a first user; receive active user information from a network entity; in response to determining the first identifier is active, retrieve user profile information associated with the first identifier; and send a second request to a second network function, the second request comprising the user profile associated with the first identifier.

[0006] There is provided an apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive a notification of user status relating to a remote unit; identify a Packet Data Unit, PDU, session affected by the user status; and either release the PDU session if the remote unit has not updated the user status in the identified PDU session, or modify the PDU session.

[0007] There is provided an apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive a first identifier identifying a first user and linked to anexisting user profile and a mobile subscription; and send a request to a network entity to store user information of the first user.

[0008] There is provided a method for wireless communication, comprising: establishing a first data connection with a remote unit, the first data connection associated with a mobile subscription in a mobile communication network; receiving a first request from the remote unit via the first data connection, the first request including a first identifier identifying a first user; identifying whether the first identifier is linked to an existing user profile and the mobile subscription to determine whether the first identifier is valid; and, in response to a determination that the first identifier is valid, sending a second request comprising the first identifier to a first network function.

[0009] There is provided a method for wireless communication, comprising: receiving a first request from a remote unit, the first request including a first identifier identifying a first user; receiving active user information from a network entity; in response to determining the first identifier is active, retrieving user profile information associated with the first identifier; and sending a second request to a second network function, the second request comprising the user profile associated with the first identifier.

[0010] There is provided a method for wireless communication, comprising: receiving a notification of user status relating to a remote unit; identifying a Packet Data Unit, PDU, session affected by the user status; and either releasing the PDU session if the remote unit has not updated the user status in the identified PDU session, or modifying the PDU session.

[0011] There is provided a method for wireless communication, comprising: receiving a first identifier identifying a first user and linked to an existing User Profile and a mobile subscription; and sending a request to a network entity to store user information of the first user.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0013] Figure 2 illustrates a sequence diagram showing creation of a user profile and notification to a network.

[0014] Figures 3A and 3B illustrate a sequence diagram, across two pages, showing identification of traffic belonging to a user.

[0015] Figure 4 illustrates a sequence diagram showing a procedure to indicate an active user and an associated user identifier.

[0016] Figures 5A and 5B illustrate a sequence diagram, across two pages, showing identification of an active user during a PDU session request.

[0017] Figure 6 illustrates a sequence diagram showing notification of a change of active user.

[0018] Figure 7 illustrates a sequence diagram showing notification of a change of active user.

[0019] Figure 8 illustrates an example of an apparatus 800 in accordance with aspects of the present disclosure.

[0020] Figure 9 illustrates an example of a processor 900 in accordance with aspects of the present disclosure.

[0021] Figure 10 illustrates a flowchart of a method 1000 performed by an apparatus in accordance with aspects of the present disclosure.

[0022] Figure 11 illustrates a flowchart of a method 1100 performed by an apparatus in accordance with aspects of the present disclosure.

[0023] Figure 12 illustrates a flowchart of a method 1200 performed by an apparatus in accordance with aspects of the present disclosure.

[0024] Figure 13 illustrates a flowchart of a method 1300 performed by an apparatus in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0025] When a mobile device connects to a mobile communication network, the network identifies a subscription associated with the USIM in the device and is configured to offer mobile services based on the provisioned data in this subscription. This creates a one-to-one mapping between subscriptions and provided services. If a mobile user wants to experience different mobile services, e.g. reliable access to corporate applications (for business use) and inexpensive access to social media (for personal use), the user is typically required to buy different subscriptions, each one tailored to providing a different mobile experience and satisfying the needs of a certain use case.

[0026] However, this is about to change. Based on the study on "User Centric Identifiers and Authentication" that was recently completed by SAI (see TS 22.101 and TR 22.904), a mobile subscriber in the future will be able to create different profiles in his / her subscription, each one suitable to providing access to different services and offering a pre-defined user experience. In a first typical case, a mobile subscriber will be able to create a "business" profile that matches his / her business communication needs, a "personal" profile that matches his / her personal communication needs, or even a "children" profile that offers safe Internet access for junior users. In a second typical case, a mobile subscriber will be able to create an "loT" profile that could be used by his / her embedded devices when they establish connectivity via the mobile communication network. Yet, in a third typical case, a mobile subscriber will be able to create a "Netflix" profile that could be used by his / her Netflix application when it establishes connectivity via the mobile communication network. As can be seen from these typical cases, the "user" of a profile can be either a human (as in the first case), or a device (as in the second case), or even an application (as in the third case).

[0027] To enable this new model, the mobile communication network is not only required to support multiple user profiles per subscription, but it is also required to identify the traffic associated with a profile and apply the corresponding settings (including QoS, charging, service chaining, etc.) to this traffic.

[0028] A new "profile" (called User Profile) can be created and linked with a mobile subscription and (b) a mobile data connection (i.e. PDU Session) can be associated with a User Profile and be configured to operate based on the service settings in this User Profile as shown in Figure 2. In Figure 2, aUE 205, Internet 210, UIMF 215, Third Party AS 220, UDR225, UDM 230, and NEF 235 collaborate to carry out a method 200 comprising steps 271 to 275.

[0029] As part of the SAI study in TR 22.904 and the corresponding normative requirements in 3GPP TS 22.101, the following has been defined as part of a User Profile:• 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: a. additional User Identifiers of the user's User Identities and potentially linked 3GPP subscriptions, b. used UEs (identified by their subscription and device identifiers), c. capabilities the used UEs support for authentication, d. information regarding authentication policies required by different services and slices to authenticate a user for access to these services or slices, e. User Identity specific service settings and parameters (those shall include network parameters (e.g., QoS parameters), IMS service (e.g. MMTEL supplementary services) and operator deployed service chain settings), and f. User Identity specific network resources (e.g., network slice); and• Subject to operator policy the 3GPP system shall be able to update User Profile related to a User Identifier, according to the information shared by a trusted 3rdparty.

[0030] There is a method to link a user identity to a 3GPP subscription and a method to store a User Profile that contains association of user identifier to a 3GPP subscription in the core network. There is a method to allow the network to identify how user traffic is associated to a user identified by a User ID and how the network enforces policy control according to the associated user profile.

[0031] The requirement for this solution is to support only one user active (and one user profile active) in the network subscription at any time when the UE is served by this network.The present disclosure tends to improve on existing solutions by specifying the following: how the network is aware which user is active at any time; and how to ensure that one user profile is active at any time.

[0032] Aspects of the present disclosure are described in the context of a wireless communications system.

[0033] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0034] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0035] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example,an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0036] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0037] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0038] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, anNE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access networktransmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0039] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0040] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0041] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures).The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0042] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / t=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / / =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / t=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0043] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0044] Additionally, or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / t=0, / t=l, =2, / z=3, / t=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on anumerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / t =0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0045] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0046] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / / =1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / / =2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., g=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / t=3), which includes 120 kHz subcarrier spacing.

[0047] Examples generally follow one of two types. One type specifies how a network is informed about an active user in the network and a second type specifies how an AMF is aware of the active user and takes corresponding actions.

[0048] In an example, a UE detects a user in the device and includes a user identifier when a PDU session is established. The AMF identifies the user profile (identified by a user profile ID) associated to this user based on the user identifier and provides it to the SMF and PCF. The SMF and PCF in turn retrieve user profile information associated with the user profile id and apply corresponding policies. An example procedure 300 is shown in Figures 3A and 3B. In Figures 3A and 3B, a UE 305 (or Gateway UE), AMF 310, SMF 315, PCF 320, and Operator or third-party AAA server 325 collaborate to perform a method 300 comprising steps 370 to 3714.

[0049] An example procedure 400 is shown in Figure 4. It is based on a new Application Function in a 5G Core (5GC) network, called User Identity Management Function (UIMF). The UIMF 415 is accessible by a device 405 either via the 5GC network or via the Internet 410, i.e. by using any access network other than 5G such as a public WiFi network, wireline residential access, etc. All communication between a device and UIMF takes place in the application layer, e.g. by using an MNO Application that can be downloaded in the device. After downloading the MNO Application, the user creates an account with the UIMF 415 (UIFM account) and confirms his mobile number. At this point, the created account is associated with his / her mobile subscription.

[0050] The user can utilize any device to access UIMF 415, as long as the device has the MNO Application and the user can login to UIMF 415 using the credentials of his / her UIMF 415 account. A device is not required to have a USIM for accessing the UIMF 415.

[0051] Figure 4 shows how the user can utilize the MNO Application and interact with UIMF 415 indicating the active user. 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. The steps of procedure 400 are described below.

[0052] 471a. After the MNO Application is launched, a secure connection is established with the UIMF 415. The IP address of UIMF 415 can be pre-configured in the MNO Application or could be discovered with DNS.

[0053] 471b. The user logs in to UIMF 415 using the credentials of his / her UIMF415 account.

[0054] 471c. Using the UI of the MNO Application, the user indicates the active user by including the user's identifier.

[0055] 47 Id. The UIMF 415 verifies the user id is valid and is linked to an existing user profile (it is assumed a user profile is created).

[0056] 472. The UIMF 415 indicates the active user to a network function in the5GC, e.g. to the Network Exposure Function (NEF 435) in order to store the active user information. The User Info request contains the GPSI of the linked mobile subscription and information about the user (user identifier). There may be more than one active users indicated in the request. For example, a user in the UE 405 and a user with a remote UE accessing the network via a gateway UE where the gateway UE subscriptions include one or more user profiles each including user identifiers used by the Gateway UE and / or the Remote UE.

[0057] 473. The NEF 435 determines the SUPI of the associated mobile subscription, which is needed before storing the active user info in UDR 425.

[0058] 474. The NEF 435 stores active user info in the UDR 425.

[0059] 475. Finally, the NEF 435 responds to UIMF 415 acknowledging the request.

[0060] If a user deregisters from the UE 405, the UE 405 uses the same procedure to indicate to the UIMF 415 de-activation of a user identifier. The UIMF 415 then indicates the network (via the NEF 435) removal of an active user identifier that is also removed from the UDM 430 / UDR 425.

[0061] Additionally, or alternatively, the UE may provide the active user id via NAS message via the core network to the AMF. The AMF stores the active user ID in the UE context. The NAS message may be a Registration Request or a Traffic Area Update message.

[0062] An example procedure 500 shown in Figures 5A and 5B relies on the UE providing a user identity in a request, such as a PDU session request. The request may be a PDU session establishment or a PDU session modification. For simplicity, the procedure 500for PDU Session establishment based on a User Identifier is shown in Figures 5A and 5B, the steps of which are described below.

[0063] 570a. The UE 505 registers to the network based on the Registration procedure described in Section 4.2.2.2 of 3GPP TS 23.502

[0064] 570b. During registration the AMF 510 retrieves from the UDR the subscription data which includes a list of User Profiles (identified by a User Profile Identifier) which contain a list of user identifiers, list of allowed devices, allowed DNNs and subscribed S-NSSAIs.

[0065] 571. If Case A applies a user logs in the device using a user identifier, lb. The UE505 may determine from the User Profile Data that a User Profile is associated with the User Identifier.

[0066] 572. If Case B applies and an application requests a network connection.The UE 505 determines from the User Profile Data that a User Profile is associated with this application.

[0067] 573. If Case C applies, a UE 505 acting as a Gateway UE 505 receives anEAP-Response / Identity message including as NAI a user identifier. The Gateway UE 505 determines from the User Profile Data that a User Profile is associated with the received NAI.

[0068] 574. In step 574a, UE 505 indicates via app layer mechanism the active user identity to the UIMF 515 / AF 515. The AF 515 validates the user id and indicate the active user to the core network via the NEF and stored in the UDR as disclosed in Figure 4.

[0069] Alternative to Step 574a the UE 505 indicates the active user ID via NAS to the AMF 510 and the AMF 510 stores in the UE 505 context.

[0070] 575. The UE 505 sends a PDU session establishment request including theUser Identifier (determined in steps 571 or 572 or 573) in the UL NAS transport message. In addition, the UE 505 includes the User Identifier in the form of an EAP-Response / Identity NAI message within the SM PDU DN Request container included within the SM PDU session establishment request container.

[0071] 576a. The AMF 510 determines, from the list of User Profiles associated to the 3GPP subscription, the user profile associated to the user identifier provided by the UE 505 in the NAS message of the PDU session establishment request.

[0072] 576b. The AMF 510 also determines from the retrieved user profile (e.g. the user specific slice subscription data) if the requested S-NSSAI and / or DNN are allowed for this PDU session, if the user associated with the user id is indicated as active by retrieving information from the UDM / UDR. The AMF 510 may be aware of the active user ID info as described in Figure 4 where the UDM / UDR provides a notification of active user information. The AMF 510 also determines if the user identifier is allowed for this UE 505 or Gateway UE 505 (from the list of allowed PEI). If the user ID is not active the AMF 510 may reject the PDU session request.

[0073] If there is no active user identifier the AMF 510 may ignore the user id provided by the UE 505 and continue the PDU session establishment (or modification) using the default subscription of the UE based on the SUPI of the UE.

[0074] 577a. The AMF 510 selects an SMF 520 and sends a Create SM Context request. The AMF 510 includes in the Create SM Context Request the User Profile Identifier of the retrieved user profile (according to step 575a).

[0075] 577b. The SMF 520 retrieves from the UDR the user specific SessionManagement Subscription Data associated to the User Profile identifier provided by the AMF 510. The SMF 520 uses the User Profile to determine the address of the AAA server 530 (if user authentication is required), authentication type required and the DNN configuration for the S-NSSAI requested

[0076] 578a. The SMF 520 sends a AAA request message to the operator or 3rd party AAA server 530 including the EAP message provided by the UE 505 in the SM PDU DN Request Container

[0077] 578b. An authentication method is derived from the AAA server 530 based on the user identifier provided.

[0078] 579a. The AAA server 530 starts an EAP authentication method with theSMF 520

[0079] 579b. The SMF 520 proxies the EAP authentication to the UE 505 via a PDU session authentication command message (double check). If Case C applies the Gateway UE 505 proxies the EAP message to the UE 505 behind the gateway UE 505.

[0080] 579c. 579d. If Authentication is successful an EAP success message is sent to the UE 505

[0081] 5710a. The SMF 520 selects a PCF 525 and sends an SM Policy ControlCreate Request message including in the request the User Profile identifier of the User Profile associated to the user identifier

[0082] 5710b. The PCF 525 retrieves from the UDRthe user specific PDU session policy control data according to User Profile Identifier and derives policy rules

[0083] 5710c. The PCF 525 provides the Policy rules to the SMF 520 in the SMPolicy Control Create response message.

[0084] 5711. The SMF 520 selects UPF(s) and establish an N4 session.

[0085] 5712, 5713, 5714 The SMF 520 sends a PDU session establishment accept message to the UE 505.

[0086] 5715. If case C applies the Gateway UE 505 assigns a local IP address to the UE505 behind the gateway and routes the PDU session traffic via the local IP address.

[0087] In an example, an AMF 610 may be notified of active user identifier from the UDM / UDR 625. With reference to the procedure 600 shown in Figure 6:

[0088] 671. UE may have already established PDU session for a user where eachPDU session is associated with a user ID.

[0089] 672. A different user or new user, identified by a different user identifier logs in the phone or a user deregisters from the UE 605.

[0090] 673. The UE 605 (or application in the UE 605) indicates the active user, deregistered user or additional active user as shown in Figure 4.

[0091] 674. The AF 635 indicates new active user to the network via NEF 630 as described in Figure 4. More than one active user identifier may be included in the request to NEF 630.

[0092] 675. The UDM / UDR 625 detects change of user or new user identifier as active identifier or a user identifier removed from the active users list and notifies the AMF 610.

[0093] 676. The AMF 610 checks how the change of active user identifiers impacts existing PDU sessions. If a user identifier is removed from the active list and a new user identifier is added the AMF 610 may identify which PDU sessions for the UE 605 were associated with a previous provided user identity and starts a timer in order for the UE 605 to update corresponding PDU sessions.

[0094] 677. The UE 605 may update PDU session with new user identity information and the PDU session request continue as shown in Figures 5A and 5B (from steps 575 onwards).

[0095] If the timer expires and the UE 605 did not update the PDU session the AMF 610 may indicate to release the PDU session and provide a corresponding error code to the UE 605 or may update the PDU session indicating to use default subscriptions (associated with the SUPI of the UE 605).

[0096] An example procedure 700 shown in Figure 7 is an alternative option without relying on the UE 705 to provide any user identity information to the network during PDU session request. It is proposed that after the User Profile is created at the UIMF the UIMF to indicate the active user to the NEF 730 and the UDM / UDR 725 notifying of the new user to each Network Function that have subscribed to receive notification of user change. The procedure 700 is as follows:

[0097] 771. UE 705 may have already established PDU session for a user where each PDU session is associated with a user ID.

[0098] 772. A different user, identified by a different user identifier logs in the phone.

[0099] 773. The UE 705 indicates the active user as shown in Figure 4.

[0100] 774. The AF 735 indicates new active user to the network via NEF 730 as described in Figure 4. The AF 735 may include either the user identifier or a user profile associated to a user identifier (identifier by a user profile reference ID). The request includes UE 705 identifier (e.g. GPSI).

[0101] 775. The UDM / UDR 725 detects change of user. The UDM / UDR 725 notifies all NFs 710, 715, 720 that have subscribed to receive notification of change of user. The UDM / UDR 725 sends a notification request including- User Identifier of the active user or User Profile reference ID associated with the active user (the UDM / UDR 725 may determine which of the User Profiles stored are associated to the user identifier if the AF 735 only included a user identifier in step 4)

[0102] 776. The AMF 710 retrieve the user profile according to the user identifier or user profile reference ID and applies corresponding AM policies (e.g. new RFSP for a user or identify which slices are allowed for a user)

[0103] 777. The SMF 715 retrieves the user profile according to the user identifier or user profile reference ID and applies corresponding Session Management policies.

[0104] 778. The PCF 720 retrieves the user profile according to the user identifier or user profile reference ID and applies corresponding PDU session related policies (e.g. change of QoS).

[0105] Figure 8 illustrates an example of an apparatus 800 in accordance with aspects of the present disclosure. The apparatus may comprise an application function, such as a UIMF, or a network function, such as an AMF, NEF, or SMF. The apparatus 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0106] The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0107] The processor 802 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 802 may be configured to operate the memory 804. In some other implementations, the memory 804 may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in the memory 804 to cause the apparatus 800 to perform various functions of the present disclosure.

[0108] The memory 804 may include volatile or non-volatile memory. The memory 804 may store computer-readable, computer-executable code including instructions when executed by the processor 802 cause the apparatus 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 804 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.

[0109] In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to cause the apparatus 800 to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804). For example, the processor 802 may support wireless communication at the apparatus 800 in accordance with examples as disclosed herein. The apparatus 800 may be configured to support a means for carrying out one or more of methods 1000, 1100, 1200, and 1300 set out below.

[0110] The controller 806 may manage input and output signals for the apparatus 800. The controller 806 may also manage peripherals not integrated into the apparatus 800. In some implementations, the controller 806 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 806 may be implemented as part of the processor 802.[OHl] In some implementations, the apparatus 800 may include at least one transceiver 808. In some other implementations, the apparatus 800 may have more than one transceiver 808. The transceiver 808 may represent a wireless transceiver. The transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0112] A receiver chain 810 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 810 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 810 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 810 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 810 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0113] A transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0114] Figure 9 illustrates an example of a processor 900 in accordance with aspects of the present disclosure. The processor 900 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 900 may include a controller 902 configured to perform various operations in accordance with examples as described herein. The processor 900 may optionally include at least one memory 904, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 900 may optionally include one or more arithmetic-logic units (ALUs) 906. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0115] The processor 900 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 900) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0116] The controller 902 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 900 to cause the processor 900 to support various operations in accordance with examples as described herein. For example, the controller 902 may operate as a control unit of the processor 900, generating control signals that manage the operation of various components of the processor 900. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0117] The controller 902 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 904 and determine subsequent instruction(s) to be executed tocause the processor 900 to support various operations in accordance with examples as described herein. The controller 902 may be configured to track memory address of instructions associated with the memory 904. The controller 902 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 902 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 900 to cause the processor 900 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 902 may be configured to manage flow of data within the processor 900. The controller 902 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 900.

[0118] The memory 904 may include one or more caches (e.g., memory local to or included in the processor 900 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 904 may reside within or on a processor chipset (e.g., local to the processor 900). In some other implementations, the memory 904 may reside external to the processor chipset (e.g., remote to the processor 900).

[0119] The memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 900, cause the processor 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 902 and / or the processor 900 may be configured to execute computer-readable instructions stored in the memory 904 to cause the processor 900 to perform various functions. For example, the processor 900 and / or the controller 902 may be coupled with or to the memory 904, the processor 900, the controller 902, and the memory 904 may be configured to perform various functions described herein. In some examples, the processor 900 may include multiple processors and the memory 904 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0120] The one or more ALUs 906 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 906 may reside within or on a processor chipset (e.g., the processor 900). In some other implementations, the one or more ALUs 906 may reside external to the processor chipset (e.g., the processor 900). One or more ALUs 906 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 906 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 906 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 906 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 906 to handle conditional operations, comparisons, and bitwise operations.

[0121] The processor 900 may support wireless communication in accordance with examples as disclosed herein. The processor 900 may be configured to or operable to support a means for carrying out one or more of methods 1000, 1100, 1200, and 1300 set out below.

[0122] Figure 10 illustrates a flowchart of a method 1000 in accordance with aspects of the present disclosure. The operations of the method may be implemented by an apparatus as described herein. In some implementations, the apparatus may execute a set of instructions to control the function elements of the apparatus to perform the described functions.

[0123] At 1002, the method 1000 may include establishing a first data connection with a remote unit, the first data connection associated with a mobile subscription in a mobile communication network. The operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by an apparatus as described with reference to Figure 8.

[0124] At 1004, the method 1000 may include receiving a first request from the remote unit via the first data connection, the first request including a first identifier identifying a first user. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by an apparatus as described with reference to Figure 8.

[0125] At 1006, the method 1000 may include identifying whether the first identifier is linked to an existing user profile and the mobile subscription to determine whether the first identifier is valid. The operations of 1006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 may be performed an apparatus as described with reference to Figure 8.

[0126] At 1008, the method may include in response to a determination that the first identifier is valid, sending a second request comprising the first identifier to a first network function. The operations of 1008 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1008 may be performed by an apparatus as described with reference to Figure 8.

[0127] It should be noted that the method 1000 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0128] Figure 11 illustrates a flowchart of a method 1100 in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by an apparatus as described herein. In some implementations, the apparatus may execute a set of instructions to control the function elements of the apparatus to perform the described functions.

[0129] At 1102, the method 1100 may include receiving a first request from a remote unit, the first request including a first identifier identifying a first user. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by an apparatus as described with reference to Figure 8.

[0130] At 1104, the method 1100 may include receiving active user information from a network entity. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by an apparatus as described with reference to Figure 8.

[0131] At 1106, the method 1100 may include in response to determining the first identifier is active, retrieving user profile information associated with the first identifier. Theoperations of 1106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1106 may be performed an apparatus as described with reference to Figure 8.

[0132] At 1108, the method 1100 may include sending a second request to a second network function, the second request comprising the user profile associated with the first identifier. The operations of 1108 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1108 may be performed by an apparatus as described with reference to Figure 8.

[0133] Figure 12 illustrates a flowchart of a method 1200 in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by an apparatus as described herein. In some implementations, the apparatus may execute a set of instructions to control the function elements of the apparatus to perform the described functions.

[0134] At 1202, the method 1200 may include receiving a notification of user status relating to a remote unit. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by an apparatus as described with reference to Figure 8.

[0135] At 1204, the method 1200 may include identifying a Packet Data Unit, PDU, session affected by the user status. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by an apparatus as described with reference to Figure 8.

[0136] At 1206, the method 1200 may include either releasing the PDU session if the remote unit has not updated the user status in the identified PDU session, or modifying the PDU session. The operations of 1206 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1206 may be performed an apparatus as described with reference to Figure 8.

[0137] Figure 13 illustrates a flowchart of a method 1300 in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by an apparatus as described herein. In some implementations, the apparatus may execute a set ofinstructions to control the function elements of the apparatus to perform the described functions.

[0138] At 1302, the method 1300 may include receiving a first identifier identifying a first user and linked to an existing User Profile and a mobile subscription. The operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by an apparatus as described with reference to Figure 8.

[0139] At 1304, the method 1300 may include sending a request to a network entity to store user information of the first user. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by an apparatus as described with reference to Figure 8.

[0140] The disclosure herein provides an apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: establish a first data connection with a remote unit, the first data connection associated with a mobile subscription in a mobile communication network; receive a first request from the remote unit via the first data connection, the first request including a first identifier identifying a first user; identify whether the first identifier is linked to both an existing user profile and the mobile subscription to determine whether the first identifier is valid; and in response to a determination that the first identifier is valid, send a second request to a first network function, the second request comprising the first identifier.

[0141] The first data connection may be associated with the mobile subscription after authenticating the remote unit using credentials associated with the mobile subscription. The credentials may comprise at least one of a GPSI and / or a password. The first identifier may comprise a user identifier indicating an active user. The mobile subscription may comprise a 3GPP subscription. The apparatus may comprise an application function. The application function may comprise a User Identity Management Function, UIMF. The first network function may comprise a Network Exposure Function, NEF. The second request maycomprise at least one of the GPSI and / or the password. The second request may comprise information about the user. The second request may indicate more than one active user.

[0142] The disclosure herein provides an apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive a first request from a remote unit, the first request including a first identifier identifying a first user; receive active user information from a network entity; in response to determining the first identifier is active, retrieve user profile information associated with the first identifier; and send a second request to a second network function, the second request comprising the user profile associated with the first identifier.

[0143] The at least one processor may be configured to cause the apparatus to receive, from the remote unit, user credentials to authenticate the first request. The first identifier may comprise a user identifier indicating an active user. The second network function may comprise a Session Management Function. The apparatus may receive the first request via NAS. The first request may be included in a PDU session establishment request. The first identifier may be in the form of an EAP-Response / Identity NAI message. The first identifier may be within a Session Management Packet Data Unit Data Network, SM PDU DN, Request container included within an SM PDU session establishment request container. The apparatus may reject or ignore the request if the first identifier is not active. The apparatus may include in the second request a default subscription if the first identifier is not active.

[0144] The disclosure herein provides an apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive a notification of user status relating to a remote unit; identify a Packet Data Unit, PDU, session affected by the user status; and either release the PDU session if the remote unit has not updated the user status in the identified PDU session, or modify the PDU session.

[0145] The apparatus of claim 12, wherein modifying the PDU session may comprise omitting providing a user profile to at least one of a Session Management Function, SMF, and / or a Policy Control Function, PCF. The at least one processor may be configured to cause the apparatus to receive the notification of active user status from the network entity.

[0146] The disclosure herein provides an apparatus for wireless communication, comprising at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive a first identifier identifying a first user and linked to an existing user profile and a mobile subscription; send a request to a network entity to store user information of the first user.

[0147] The network entity may comprise at least one of a UDM and / or a UDR.

[0148] The first identifier may be received from a UTMF. The apparatus may comprise a Network Function. The Network Function may be a Network Exposure Function. The Network Exposure Function may determine a SUPI of the mobile subscription. The request may comprise the SUPI. The Network Exposure Function may acknowledge the request to the UIMF.

[0149] The disclosure herein provides an apparatus for wireless communication, comprising at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive at least one of a user identifier and / or a user profile reference ID from a network entity; in response to determining the first user identifier is active, retrieve user profile information associated to at least one of the user identifier and / or the user profile reference ID; and apply at least one corresponding access management policy.

[0150] At least one access management policy may comprise a new RFSP for a user. Applying at least one access management policy may comprise identifying which network slices the user is allowed.

[0151] The disclosure herein provides a method for wireless communication, comprising: establishing a first data connection with a remote unit, the first data connection associated with a mobile subscription in a mobile communication network; receiving a first request from the remote unit via the first data connection, the first request including a first identifier identifying a first user; identifying whether the first identifier is linked to an existing user profile and the mobile subscription to determine whether the first identifier is valid; and, in response to a determination that the first identifier is valid, sending a second request comprising the first identifier to a first network function.

[0152] The disclosure herein provides a method for wireless communication, comprising: receiving a first request from a remote unit, the first request including a first identifier identifying a first user; receiving active user information from a network entity; in response to determining the first identifier is active, retrieving user profile information associated with the first identifier; and sending a second request to a second network function, the second request comprising the user profile associated with the first identifier.

[0153] The disclosure herein provides a method for wireless communication, comprising: receiving a notification of user status relating to a remote unit; identifying a Packet Data Unit, PDU, session affected by the user status; and either releasing the PDU session if the remote unit has not updated the user status in the identified PDU session, or modifying the PDU session.

[0154] The disclosure herein provides a method for wireless communication, comprising: receiving a first identifier identifying a first user and linked to an existing User Profile and a mobile subscription; and sending a request to a network entity to store user information of the first user.

[0155] The disclosure herein provides a method for wireless communication, comprising: receiving at least one of a user identifier and / or a user profile reference ID from a network entity; in response to determining the first user identifier is active, retrieving user profile information associated to at least one of the user identifier and / or the user profile reference ID; and applying at least one corresponding access management policy.

[0156] The first network function may comprise a Network Exposure Function. The second network function may comprise a Session Management Function.

[0157] The network entity may comprise at least one of a UDM and / or a UDR.

[0158] In an example, there is provided: a method for the UE to indicate an active user to the core network by interfacing with the AF and the AF in response indicating via the NEF the user identifier associated with the active user. The active user identifier is stored in the UDM / UDR.

[0159] In an example, there is provided a method for the AMF to determine the active user by retrieving the active user identifier from the UDM / UDR.

[0160] In an example, there is provided a method to indicate active user to the core network without any control plane impacts to the UE.

[0161] As part of the FS UIC work in Release 19 the objective is to allow the network to identify traffic belonging to a user accessing a UE. Each user is associated with a User Profile that includes user specific information (e.g., user specific QoS policies). It is part of the objectives of the work that there is only one active user identifier (for the UE) and a solution is needed to allow the network to be informed of the active user and associated user profile.

[0162] The UE indicates an active user to the core network by interfacing with the AF. The AF notifies via the NEF the user identifier associated with the active user. The active user identifier is stored in the UDM / UDR. During a PDU session request the UE includes a user identifier and the AMF determine the active user by retrieving the active user identifier from the UDM / UDR.

[0163] TR 23.700-32 describes solutions on how the UE includes a user identifier information in a registration request or PDU session establishment request. The assumption in this solution is that the UE maintains the active user ID. However, this creates issues at the network as in case multiple user identifiers are provided by the UE the network does not know which correspond to active user.

[0164] In an example, there is provided a method for a UE to indicate an active user to a core network by interfacing with an AF and the AF in response indicating via an NEF a user identifier associated with the active user. The active user identifier is stored in a UDM / UDR.

[0165] In an example, there is provided a method for an AMF to determine an active user by retrieving active user identifier from the UDM / UDR.

[0166] In an example, there is provided a method comprising: establishing a first data connection with a remote unit, the first data connection associated with a mobile subscription in a mobile communication network. The first data connection is associated with a mobilesubscription after authenticating the remote unit using credentials associated with a mobile subscription. The method comprises receiving a first request via the first data connection to indicate an active user identified by a user identifier; determining if the user identity provided is valid by identifying if the provided user ID is linked to an existing User Profile and the 3GPP subscription; sending to a second NF (NEF) a second request including the user identifier associated with the active user; and the NEF sending a third request to a UDM / UDR to store active user information. In this example, method steps may be performed by a UIMF, such as the UIMF of Figure 4.

[0167] In an example, there is provided a method comprising: a first remote device (UE) sending a first request wherein the first request includes a first identifier identifying a first user (User Identifier) and user credentials to authenticate the first request. The first network function (AMF) receives from the UDM / UDR the active user information by receiving a user identifier. In response to determining the first user identifier is active retrieving user profile information associated to the first user identifier and sending a second request to a third network function (SMF) including in the request the user profile associated with the active user identifier. In this example, methods steps may be performed by an AMF.

[0168] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0169] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0170] The following abbreviations are relevant in the field addressed by this document: 5GC / 5GS, 5 Generation Core network / 5 Generation System; 5QI, 5G QoS Identifier; AAA, Authentication, Authorization, and Accounting; AF, Application Function; AIoT, Ambient Internet of Things; AM, Access and Mobility ; AMF, Access and Mobility Management Function; AN, Access network; AS, Application Server; BS, Base Station; CN, Corenetwork; CP, Control plane; EC, Energy Consumption; ECF, Energy Consumption function; ECL , Energy credit limit; eNB, Evolved Node-B; EPCZEPS, Evolved packet core / Evolved packet system; GBR, Guaranteed Bitrate; gNB, 5G Node-B; GPSI, Generic Public Subscription Identifier; ID, Identity; IE, Information Element; LTE, Long Term Evolution; NAS, Non Access Stratum; MM, Mobility Management; MO, Mobile Originated; MRU, Mobility Registration Update; MT, Mobile Terminated; NEF, Network Exposure Function; NF, Network Function; NPN, Non-Public Network; NR, New Radio; NRF, Network Repository Function; NS, Network Slice; NWDAF, Network Data Analytics Function; OAM, Operations, Administration and Management; PCF, Policy Control Function; PDU, Protocol Data Unit; PLMN; HPLMN; VPLMN, Public Land Mobile Network; Home PLMN ; Visited PLMN; RAN, Radio Access Network; RAT, Radio Access Technology / Type; S-NSSAI, Single Network Slice Selection Assistance Information; SM, Session Management ; SMF, Session Management Function; SNPN, Standalone Non-Public Network; SUPI, Subscription Permanent Identifier; TA, Tracking area; TRP, Transmit- Receive Points; UDM, Unified Data Management; UDR, Unified Data Repository; UE, User Equipment; UMTS, Universal Mobile Telecommunication System; UP, User plane; UPF, User Plane Function; USIM, Universal subscriber identity module; and (E)-UTRAN, (Evolved) Universal Terrestrial Radio Access Network.

Claims

CLAIMS1. An apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: establish a first data connection with a remote unit, the first data connection associated with a mobile subscription in a mobile communication network; receive a first request from the remote unit via the first data connection, the first request including a first identifier identifying a first user; identify whether the first identifier is linked to both an existing user profile and the mobile subscription to determine whether the first identifier is valid; and in response to a determination that the first identifier is valid, send a second request to a first network function, the second request comprising the first identifier.

2. The apparatus of claim 1, wherein the first data connection is associated with the mobile subscription after authenticating the remote unit using credentials associated with the mobile subscription.

3. The apparatus of claim 2, wherein the credentials comprise at least one of a Generic Public Subscription Identifier, GPSI, and / or a password.

4. The apparatus of any preceding claim, wherein the first identifier comprises a user identifier indicating an active user.

5. The apparatus of any preceding claim, wherein the mobile subscription comprises a 3GPP subscription.

6. The apparatus of any preceding claim, wherein the apparatus comprises an application function.

7. The apparatus of claim 6, wherein the application function comprises a User Identity Management Function, UIMF.

8. The apparatus of any preceding claim, wherein the first network function comprises a Network Exposure Function, NEF.

9. An apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive a first request from a remote unit, the first request including a first identifier identifying a first user; receive active user information from a network entity; in response to determining the first identifier is active, retrieve user profile information associated with the first identifier; and send a second request to a second network function, the second request comprising the user profile associated with the first identifier.

10. The apparatus of claim 9, wherein the first identifier comprises a user identifier indicating an active user.

11. The apparatus of claim 9 or claim 10, wherein the second network function comprises a Session Management Function.

12. An apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive a notification of user status relating to a remote unit; identify a Packet Data Unit, PDU, session affected by the user status; andeither release the PDU session if the remote unit has not updated the user status in the identified PDU session, or modify the PDU session.

13. The apparatus of claim 12, wherein modifying the PDU session comprises omitting providing a user profile to at least one of a Session Management Function, SMF, and / or a Policy Control Function, PCF.

14. The apparatus of claim 12 or claim 13, wherein the at least one processor is configured to cause the apparatus to receive the notification of active user status from the network entity.

15. An apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the apparatus to: receive a first identifier identifying a first user and linked to an existing user profile and a mobile subscription; and send a request to a network entity to store user information of the first user.

16. The apparatus of any one of claims 9-15, wherein the network entity comprises at least one of a UDM and / or a UDR.

17. A method for wireless communication, comprising: establishing a first data connection with a remote unit, the first data connection associated with a mobile subscription in a mobile communication network; receiving a first request from the remote unit via the first data connection, the first request including a first identifier identifying a first user; identifying whether the first identifier is linked to an existing user profile and the mobile subscription to determine whether the first identifier is valid; and, in response to a determination that the first identifier is valid, sending a second request comprising the first identifier to a first network function.

18. A method for wireless communication, comprising: receiving a first request from a remote unit, the first request including a first identifier identifying a first user; receiving active user information from a network entity; in response to determining the first identifier is active, retrieving user profile information associated with the first identifier; and sending a second request to a second network function, the second request comprising the user profile associated with the first identifier.

19. A method for wireless communication, comprising: receiving a notification of user status relating to a remote unit; identifying a Packet Data Unit, PDU, session affected by the user status; and either releasing the PDU session if the remote unit has not updated the user status in the identified PDU session, or modifying the PDU session.

20. A method for wireless communication, comprising: receiving a first identifier identifying a first user and linked to an existing User Profile and a mobile subscription; and sending a request to a network entity to store user information of the first user.

Citation Information

Patent Citations

  • Accessing a mobile communication network using a user identifier

    US20220345887A1