Methods, devices, and computer program products for wireless communication

Abstract

A method of wireless communication is disclosed. The method includes sending, by a network node, a subscription request to a data management node in response to receiving a user identifier indication from the data management node, the request for subscription to user identifier events corresponding to a subscription identifier.

Description

Technical Field

[0001] This document primarily deals with wireless communication, particularly fifth-generation (5G) or sixth-generation (6G) communication. Background Technology

[0002] Subscription Persistent Identifier (SUPI) is used to distinguish the identity of a User Equipment (UE). However, in some cases, multiple users (including individuals, devices, etc.) may share a single UE. In such cases, SUPI alone may not be sufficient to identify all users. Summary of the Invention

[0003] This document relates to methods, systems, and computer program products for wireless communication.

[0004] One aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: in response to receiving a user identifier indication from a data management node, a network node sending a subscription request to the data management node, the request being for subscribing to a user identifier event corresponding to a subscribed identifier.

[0005] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: a wireless communication terminal sending a user identifier support indication to a network node, indicating that the wireless communication terminal supports user identifier operation.

[0006] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: in response to sending a user identifier indication to a network node, a data management node receiving a subscription request from the network node, the request being for subscribing to a user identifier event corresponding to a subscription identifier.

[0007] Another aspect of this disclosure relates to a network node. In one embodiment, the network node includes a communication unit and a processor. The processor is configured to: in response to receiving a user identifier indication from a data management node, send a subscription request via the communication unit to the data management node, the request being for subscribing to a user identifier event corresponding to the subscribed identifier.

[0008] Another aspect of this disclosure relates to a wireless communication terminal. In one embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to send a user identifier support indication to a network node via the communication unit, indicating that the wireless communication terminal supports user identifier operation.

[0009] Another aspect of this disclosure relates to a data management node. In one embodiment, the data management node includes a communication unit and a processor. The processor is configured to receive a subscription request from the network node in response to sending a user identifier indication to the network node, the request being for subscribing to a user identifier event corresponding to the subscription identifier.

[0010] Various embodiments may preferably achieve the following features: Preferably, the user identifier event includes at least one of the following: The user identifier corresponding to the contract identifier is active; The user identifier corresponding to the contract identifier is disabled; or Replace the first active user identifier corresponding to the contract identifier with the second active user identifier corresponding to the contract identifier.

[0011] Preferably, the network node receives a notification of a user identifier event from the data management node, and the notification includes the user identifier corresponding to the user identifier event.

[0012] Preferably, the notification also includes at least one of the following: The user profile identifier corresponding to the user identifier event; Information about the user identifier event; or User profile information corresponding to the user identifier.

[0013] Preferably, in response to the notification, the network node retrieves first information from the data management node, the first information including: user profile information corresponding to the user identifier.

[0014] Preferably, the network node sends a first message to the policy control node, session management node, or access management node, the first message including at least one of the following: The user identifier corresponding to the user identifier event; The user profile identifier corresponding to the user identifier event; Information about the user identifier event; or User profile information corresponding to the user identifier.

[0015] Preferably, the network node receives a first message from a policy control node, a session management node, or an access management node, the first message including at least one of the following: The user identifier corresponding to the user identifier event; The user profile identifier corresponding to the user identifier event; Information about the user identifier event; or User profile information corresponding to the user identifier.

[0016] Preferably, the network node retrieves the first information from the data management node in response to at least one of the following: The network node receives the first message from the session management node; The network node receives the first message from the policy control node; or The network node receives the first message from the access management node.

[0017] Preferably, the first message is sent via a message associated with modifying the session management policy or via a message associated with modifying the Protocol Data Unit (PDU) session.

[0018] Preferably, the network node sends a second message to the wireless communication terminal to indicate at least one of the user identifier, user identifier status, or protocol data unit (PDU) session status corresponding to the user identifier event.

[0019] Preferably, the second message is sent via a command for modifying the PDU session.

[0020] Preferably, the user identifier is received in the contract data.

[0021] Preferably, the network node performs at least one of the following operations: Receive user identifier support indication from wireless communication terminal; or In response to receiving a user identifier support indication, a message including the user identifier support indication is sent to the data management node.

[0022] Preferably, the network node sends a message to the wireless communication terminal including a user identifier permission indication.

[0023] Preferably, the network node sends a message including a user identifier indication to the policy control node or receives a message from the session management node.

[0024] Preferably, the message including the user identifier is sent via a message used to establish a session management policy association.

[0025] Preferably, the wireless communication terminal receives a user identifier permission indication from the network node.

[0026] Preferably, the wireless communication terminal receives a message indicating at least one of the user identifier, user identifier status, or protocol data unit (PDU) session status corresponding to the user identifier event.

[0027] Preferably, the data management node sends a notification of a user identifier event to the network node, and the notification includes the user identifier corresponding to the user identifier event.

[0028] Preferably, in response to receiving a user identifier support indication, the data management node receives a message including the user identifier support indication from the network node.

[0029] This disclosure relates to a computer program product including computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the aforementioned wireless communication methods.

[0030] The exemplary embodiments disclosed herein are intended to provide features that will become apparent from the following description and in conjunction with the accompanying drawings. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications to the disclosed embodiments will be apparent to those skilled in the art who read this disclosure while remaining within the scope of this disclosure.

[0031] Therefore, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps or operations in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps or operations in the disclosed methods or processes may be rearranged while remaining within the scope of this disclosure. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or operations in an exemplary order, and unless otherwise expressly stated, this disclosure is not limited to the specific order or hierarchy presented.

[0032] The above and other aspects and their implementations are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0033] Figure 1 A schematic diagram of a network according to an embodiment of the present disclosure is shown.

[0034] Figure 2 A schematic diagram of a network according to an embodiment of the present disclosure is shown.

[0035] Figure 3 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0036] Figure 4 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0037] Figure 5 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0038] Figure 6 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0039] Figure 7A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0040] Figure 8 An example of a schematic diagram of a wireless communication terminal according to an embodiment of the present disclosure is shown.

[0041] Figure 9 An example of a schematic diagram of a wireless communication node according to an embodiment of the present disclosure is shown.

[0042] Figures 10 to 12 A flowchart of a wireless communication method according to some embodiments of the present disclosure is shown. Detailed Implementation

[0043] In some embodiments of this disclosure, one or more users (e.g., people, devices, etc.) share a single UE. Operators may wish to provide optimized performance and services to users using the UE. For example, network settings may be adjusted, and services may be provided to users based on their needs.

[0044] In some embodiments of this disclosure, the network may need to know the current user using the UE. The current user is identified by a user identifier. When a user identifier is authenticated and authorized to use the UE by the 5G core (5GC) network, that user identifier is considered the current user or the active user.

[0045] Some embodiments of this disclosure provide a method that, when a user identifier is authenticated and authorized by a 5GC, allows network functions (NFs) (e.g., Session Management Function (SMF), Policy Control Function (PCF)) to know the current user identifier or activate the user identifier.

[0046] Some embodiments of this disclosure relate to a method that enables a 5GC NF to know the current / active user ID (user identifier) ​​of the UE in use.

[0047] Figure 1 A schematic diagram of a 5G architecture according to an embodiment of this disclosure is shown. Note that some features may not be shown.

[0048] 1) The UE is accessing the 5G system (5GS) and obtaining services via NG-RAN, and interacting with the access and mobility management functions (AMF) of the core network via non-access stratum (NAS) signaling.

[0049] 2) NG-RAN (i.e., 5G Radio Access Network). NG-RAN is responsible for the scheduling of air interface resources and the management of air interface connections for UE access networks.

[0050] 3) AMF (Access and Mobility Management Function). This function includes the following: registration management, connection management, reachability management, and mobility management. It also performs access authentication and access authorization. The AMF is a NAS security endpoint that relays SM (Session Management) NAS between the UE and the SMF.

[0051] 4) SMF (Session Management Function). This function includes the following: session management (e.g., session establishment, modification, and release), UE IP address allocation and management, selection and control of user plane (UP) functions, downlink data notification, etc.

[0052] 5) UPF (User Plane Functions). This function includes the following features: anchor points for mobility within / between RATs, packet routing and forwarding, traffic usage reporting, user plane QoS processing, downlink packet buffering, and downlink data notification triggering.

[0053] 6) UDM (Unified Data Management). It manages the UE's subscription profiles. Subscriptions include data used for mobility management and session management. AMF and SMF obtain subscriptions from UDM.

[0054] 7) PCF (Policy Control Function). The Policy Control Function (PCF) includes the following functions: supporting a unified policy framework to manage network behavior, and providing policy rules to control plane functions for policy enforcement.

[0055] 8) Optional deployment of NEF (Network Exposure Function) for exchanging information between 5GC and external third parties.

[0056] 9) UDR (Unified Data Repository). It supports the following functions: UDM for storing and retrieving contracted data; PCF for storing and retrieving policy data; and / or for storing and retrieving structured data used for exposure.

[0057] 10) AF / AS (Application Functionality / Application Server). It provides services via 5GS.

[0058] Each UE has an identifier (e.g., SUPI) that is contained in the Universal Subscriber Identity Module (USIM) card within the UE. On the network side, the UE subscription data is identified by the SUPI. In other words, the SUPI can be an identifier of the UE's identity between the UE and the network.

[0059] In some embodiments, a relationship exists between a user (e.g., a person, device, etc.) and a UE. One or more users (e.g., a person, device, etc.) share a UE, while a user (e.g., a person, device, etc.) uses multiple UEs. In this disclosure, the term "user" refers to a person, a specific device, a specific application, etc. A user can be identified by a user identifier.

[0060] Figure 2 A schematic diagram of a network according to an embodiment of this disclosure is shown. Figure 2 In the example, users A and B share UE-1, while users A and C share UE-2.

[0061] In some embodiments, user identity information is located in a user profile stored in the UDM / UDR. It may contain user identity information such as user identifier, credentials, SUPI, Quality of Service (QoS) parameters, and service information for the user identifier (e.g., including application identifier, IP address information (e.g., including IP address or FQDN, IP port), DNN, and / or S-NSSAI). During user identifier authentication, the UDM knows which user identifier is active for the UE / SUPI.

[0062] In some embodiments, a user profile can be identified by a user profile ID. When a user identifier is authenticated and authorized to use the UE by the 5GC, the user identifier is considered the current user or the active user. During user identifier authentication and authorization, the AMF and UDM can determine which user identifier is active for SUPI (i.e., the corresponding user is using the UE).

[0063] Some embodiments of this disclosure provide a method that allows an NF (e.g., SMF, PCF) to know the current user identifier or activate the user identifier when a user identifier is authenticated and authorized by a 5GC.

[0064] In some embodiments, "network" refers to a mobile network, which may be a 4G (Evolved Packet System), 5G, or 6G network. For ease of understanding, a 5G system is used as an example, but 4G and 6G networks may also be applicable.

[0065] Aspect 1: In some embodiments, a user identifier indication (e.g., a user identity indication) is present in the UE subscription (also known as UE subscription data) in the UDM / UDR. In some embodiments, the user identifier indication may be located in UE access and mobility subscription data, session management subscription data, and policy data subscription data.

[0066] In some embodiments, when an NF (e.g., AMF, SMF, PCF) obtains UE subscription data (e.g., during PDU session establishment, UE registration, SM policy association establishment, etc.), the NF can find a user identifier indication in the UE subscription data. In response to the user identifier indication, the NF subscribes to user identifier events (e.g., user identifier information) from the UDM / UDR.

[0067] In some embodiments, the user identifier event includes at least one of the following: the user identifier corresponding to the subscription identifier (e.g., SUPI) is active; the user identifier corresponding to the subscription identifier is deactivated; or the first active user identifier corresponding to the subscription identifier is replaced with a second active user identifier corresponding to the subscription identifier.

[0068] Figure 3 An AMF subscription during a UE registration process according to an embodiment of this disclosure is illustrated. In some embodiments, during UE registration, when the AMF detects a user identifier indication in the UE subscription data, the AMF subscribes to user identifier events (e.g., user identifier information) from the UDM / UDR. In some embodiments, this process may include at least one of the following operations. For simplicity, irrelevant operations may be omitted.

[0069] 301. An indication of a user identifier (also referred to herein as a user identifier indication) exists in the UDM / UDR (e.g., in the UE subscription data). In some embodiments, the user identifier indication may be located in the UE access and mobility subscription data.

[0070] 302. The UE sends a message (e.g., a registration message) to the AMF. In some embodiments, the SUPI and user identifier support indication (e.g., an indication that the wireless communication terminal supports user identifier operation) are carried in the message (e.g., the registration message).

[0071] 303. The AMF sends a message (e.g., a registration message) to the UDM / UDR. In some embodiments, the AMF may invoke a service operation (e.g., Nudm_UECM_Registration) to send a message (e.g., a registration message). In some embodiments, a user identifier support indication may be sent to the UDM / UDR via a message. In some embodiments, in response to receiving a user identifier support indication, the AMF sends a message including the user identifier support indication to the UDM / UDR.

[0072] 304. UDM / UDR sends a response to AMF (e.g., a registration response).

[0073] 305. The AMF sends a request to the UDM / UDR. In some embodiments, this request is to obtain UE access and mobility subscription data. In some embodiments, the AMF may invoke a service operation (e.g., Nudm_SDM_Get) to send the request.

[0074] 306. UDM / UDR responds to this request by sending UE subscription data to AMF. In some embodiments, AMF detects an indication (e.g., a user identifier indication) in the UE subscription data.

[0075] 307. The AMF sends a request to subscribe to the user identifier event corresponding to the SUPI. In some embodiments, the request includes the SUPI. In some embodiments, the AMF may invoke a service operation (e.g., Nudm_SDM_Subscribe) to subscribe to the user identifier event.

[0076] 308. The AMF sends a message to the UE (e.g., a registration acceptance message). In some embodiments, this message sends a user identifier permission indication to the UE.

[0077] Aspect 2: Figure 4 An SMF / PCF subscription during the PDU session establishment process according to an embodiment of this disclosure is illustrated. In some embodiments, during PDU session establishment, when the SMF or PCF detects an indication (e.g., a user identifier indication) in the UE subscription data, they subscribe to user identifier events (e.g., user identifier information) from the UDM / UDR. In some embodiments, this process may include at least one of the following operations. Irrelevant operations are omitted for simplicity.

[0078] 401. An indication for user identification (also referred to herein as a user identifier indication) exists in the UDM / UDR (e.g., in the UE subscription data). In some embodiments, the user identifier indication may be located in the UE access and mobility subscription data.

[0079] 402. The UE sends a message (e.g., a PDU session establishment message) to the SMF via the AMF. In some embodiments, this message is used to establish a PDU session. In some embodiments, the message carries a user identifier support indication.

[0080] 403. The SMF sends a request to the UDM / UDR. In some embodiments, this request is for obtaining UE subscription data. In some embodiments, the SMF may invoke a service operation (e.g., Nudm_SDM_Get) to send the request. In some embodiments, a User Identifier Support Indicator (UIDI) may be carried in the message. In some embodiments, in response to receiving the UIDI Support Indicator, the SMF sends a message including the UIDI Support Indicator to the UDM / UDR.

[0081] 404. UDM / UDR responds to this request by sending UE subscription data to the SMF. In some embodiments, the SMF discovers an indication (e.g., a user identifier indication) in the UE subscription data.

[0082] 405. The SMF sends a request to subscribe to the user identifier event corresponding to the UE's SUPI from the UDM / UDR. In some embodiments, the SMF may invoke a service operation (e.g., Nudm_SDM_Subscribe) to subscribe to the user identifier event.

[0083] 406. The SMF sends a message to the PCF (e.g., an SM policy association establishment message). In some embodiments, this message is used to establish an SM policy association. In some embodiments, the SMF may invoke a service operation (e.g., Npcf_SMPolicyControl_Create) to send the message to the PCF. In some embodiments, a user identifier indication may be carried in the message sent from the SMF to the PCF.

[0084] 407. The PCF sends a request to the UDM / UDR. In some embodiments, this request is for obtaining UE subscription data. In some embodiments, the PCF may invoke a service operation (e.g., Nudm_SDM_Get) to send the request. In some embodiments, a user identifier support indication may be carried in the message. In some embodiments, the UDM / UDR responds to the request by sending the UE subscription data to the PCF.

[0085] 408. If the PCF detects a user identifier indication in the UE's subscription data, the PCF sends a request to the UDM / UDR to subscribe to the user identifier event corresponding to the UE's SUPI from the UDM / UDR. In some embodiments, the PCF may invoke a service operation (e.g., Nudm_SDM_Subscribe) to subscribe to the user identifier event.

[0086] 409. The PCF sends a response to the SMF (e.g., an SM policy association establishment response).

[0087] 410. The SMF sends a message to the UE (e.g., a PDU session establishment accept message). In some embodiments, during operation 402, this message responds to a message from the UE to the SMF. In some embodiments, the message indicates that the PDU session establishment request has been accepted. In some embodiments, a user identifier permission indication is sent to the UE in the message (e.g., the PDU session establishment accept message).

[0088] Aspect 3: Figures 5 to 7 The diagram illustrates that when the UDM determines that a user identifier event has occurred (e.g., the user identifier corresponding to the SUPI is active, deactivated (e.g., the user identified by the user identifier stops using the UE), or the active user identifier corresponding to the SUPI has been replaced (e.g., a new active user identifier replaces an old active user identifier)), the UDM notifies the subscriber NF (the NF subscribes to user identifier events (e.g., AMF in aspect 1 and SMF and PCF in aspect 2)) of the latest active user identifier and optional event information (e.g., event code / ID). The UDM may additionally notify the subscriber NF of user profile information.

[0089] Figure 5 A schematic diagram of a process according to an embodiment of this disclosure is shown. In some embodiments, the SMF has subscribed to user identifier events from the UDM / UDR. The UDM / UDR notifies the SMF of user identifier events (e.g., user identifier status). In some embodiments, the process may include at least one of the following operations. Irrelevant operations are omitted for simplicity.

[0090] 501. The SMF has subscribed to the SUPI user identifier events from the UDM / UDR. In some embodiments, the SMF subscribes to the user identifier events corresponding to the SUPI from the UDM / UDR. In some embodiments, the SMF may invoke a service operation (e.g., Nudm_SDM_Subscribe).

[0091] 502. UDM / UDR detected that a SUPI user identifier event has occurred (e.g., the user identifier is active, is deactivated (e.g., the user identified by the user identifier stops using the UE), or the active user identifier is replaced (e.g., a new active user identifier will replace the old active user identifier corresponding to the SUPI)).

[0092] 503. UDM / UDR notifies SMF (e.g., via notification) about a user identifier event. In some embodiments, the notification includes a user identifier and an optional user profile ID, as well as information about the user identifier event (e.g., the event that occurred (e.g., user identifier activation, deactivation, replacement, etc.)) (also referred to as an event indication). In some embodiments, the notification may optionally include user profile information corresponding to the user identifier. In some embodiments, the notification includes at least one of the following: a user identifier corresponding to the user identifier event (e.g., an activated user identifier or a deactivated user identifier); a user profile identifier corresponding to the user identifier event (e.g., an activated user profile ID or a deactivated user profile ID); information about the user identifier event; and / or user profile information corresponding to the user identifier.

[0093] 504. The SMF retrieves user profile information (e.g., a user profile) from the UDM / UDR. In some embodiments, the SMF provides the UDM / UDR with at least one of a SUPI, a user identifier (e.g., a user identifier received in a notification), and / or a user profile ID (e.g., a user identifier received in a notification). The UDM / UDR returns user profile information in response to the SMF, which corresponds to at least one of the SUPI, user identifier, and / or user profile ID received from the SMF. The SMF may invoke a service operation (e.g., Nudm_SDM_Get) and use some other service operation to achieve this. In some embodiments, the retrieval of user profile information is performed in response to this notification.

[0094] 505. The SMF sends a message to the PCF (e.g., an SM policy association modification message). In some embodiments, this message is used to modify session management policy associations. In some embodiments, the SMF may invoke a service operation (e.g., Npcf_SMPolicyControl_Modify). In some embodiments, the user identifier and event indication (e.g., user identifier activation, deactivation, replacement, etc.) and the user profile information corresponding to the user identifier may be carried in this message.

[0095] In some embodiments, the message includes at least one of the following: a user identifier corresponding to a user identifier event (e.g., an active user identifier or a deactivated user identifier); a user profile identifier corresponding to a user identifier event (e.g., an active user profile ID or a deactivated user profile ID); information about the user identifier event; or user profile information corresponding to the user identifier.

[0096] 506. If the PCF does not have user profile information corresponding to the user identifier, the PCF retrieves user profile information (e.g., user profile) from the UDM / UDR (details of which can be determined with reference to operation 504). In some embodiments, the retrieval of user profile information is performed in response to a message received from the SMF.

[0097] 507. The PCF creates Policy and Charging Control (PCC) rules based on the service and / or QoS settings in the user profile information and sends the PCCs to the SMF.

[0098] 508. Based on the service and / or QoS settings in the user profile information and the PCC rules received from the PCF, the SMF / UPF performs subsequent processing, such as applying QoS rules to existing QoS flows and creating QoS flows for specific services. In some embodiments, the SMF (e.g., via the AMF) sends a message (e.g., a PDU session modification command) to the UE. In some embodiments, this message is a command for modifying the PDU session. In some embodiments, the message includes at least one of a user identifier, a user identifier state (e.g., active or deactivated), or a PDU session state corresponding to a user identifier event. In some embodiments, the message may indicate the activation of the user identifier state and the PDU session state (e.g., user state, active user identifier, current user not allowed PDU session (e.g., current user not allowed DNN / S-NSSAI for this PDU session), or current user in the current area not allowed PDU session, etc.).

[0099] Aspect 4: Figure 6 A schematic diagram of a process according to an embodiment of this disclosure is shown. In some embodiments, the PCF has subscribed to user identifier events from the UDM / UDR. In some embodiments, the UDM / UDR notifies the PCF of the user identifier events. In some embodiments, the process may include at least one of the following operations. Irrelevant operations are omitted for simplicity.

[0100] 601. The PCF has subscribed to the SUPI user identifier event from the UDM / UDR. If the PCF finds an indication (e.g., a user identifier indication) in the UE subscription data, the PCF subscribes to the user identifier event corresponding to the SUPI from the UDM / UDR. In some embodiments, the PCF may invoke a service operation (e.g., Nudm_SDM_Subscribe).

[0101] 602.UDM detects that a SUPI user identifier event has occurred (e.g., the user identifier is active, is deactivated (e.g., the user identified by the user identifier stops using the UE), or the active user identifier is replaced (e.g., a new active user identifier will replace the old active user identifier corresponding to the SUPI)).

[0102] 603. UDM notifies PCF (e.g., via notification) about a user identifier event. In some embodiments, the notification includes a user identifier and an optional user profile ID, as well as information about the user identifier event (e.g., user identifier activation, deactivation, replacement, etc.). In some embodiments, optionally, the notification may include user profile information corresponding to the user identifier. In some embodiments, the notification includes at least one of the following: a user identifier corresponding to the user identifier event (e.g., an activated user identifier or a deactivated user identifier); a user profile identifier corresponding to the user identifier event (e.g., an activated user profile ID or a deactivated user profile ID); information about the user identifier event; and / or user profile information corresponding to the user identifier.

[0103] 604. The PCF retrieves user profile information (e.g., a user profile) from the UDM / UDR. In some embodiments, the PCF provides at least one of a SUPI, a user identifier (e.g., a user identifier received in a notification), and / or a user profile ID (e.g., a user identifier received in a notification). In some embodiments, the UDM / UDR returns user profile information in response to the PCF, which corresponds to at least one of the SUPI, user identifier, and / or user profile ID received from the PCF. In some embodiments, the PCF may invoke a service operation (e.g., Nudm_SDM_Get) and use some other service operation to achieve this. Based on the service and / or QoS settings in the user profile information, the PCF creates PCC rules. In some embodiments, the retrieval of user profile information is performed in response to this notification.

[0104] 605. The PCF sends a message to the SMF (e.g., an SM policy association modification message). In some embodiments, this message is used to modify session management policy associations. In some embodiments, the PCF may invoke a service operation (e.g., Npcf_SMPolicyControl_Modify). PCC rules, user identifiers, and event indications (e.g., user identifier activation, deactivation, replacement, etc.) and / or user profile information corresponding to the user identifier may be carried in this message.

[0105] In some embodiments, the message includes at least one of the following: a user identifier corresponding to a user identifier event (e.g., an active user identifier or a deactivated user identifier); a user profile identifier corresponding to a user identifier event (e.g., an active user profile ID or a deactivated user profile ID); information about the user identifier event; or user profile information corresponding to the user identifier.

[0106] 606. If the SMF does not have user profile information corresponding to the user identifier, the SMF retrieves user profile information (e.g., user profile) from the UDM / UDR (details of which can be determined with reference to operation 604). In some embodiments, the retrieval of user profile information is performed in response to a message received from the SMF.

[0107] 607. Based on the service and / or QoS settings in the user profile information and the PCC rules received from the PCF, the SMF / UPF performs subsequent processing, such as applying QoS rules to existing QoS flows and creating QoS flows for specific services. In some embodiments, the SMF (e.g., via the AMF) sends a message (e.g., a PDU session modification command) to the UE. In some embodiments, this message is a command for modifying the PDU session. In some embodiments, the message includes at least one of a user identifier, a user identifier state (e.g., activated or deactivated), or a PDU session state corresponding to a user identifier event. In some embodiments, the message may indicate the activation of the user identifier state and the PDU session state (e.g., user state, activated user identifier, current user not allowed PDU session (e.g., current user not allowed DNN / S-NSSAI for this PDU session), or current user in the current area not allowed PDU session, etc.).

[0108] Aspect 5: Figure 7 A schematic diagram of a process according to an embodiment of this disclosure is shown. In some embodiments, the AMF has subscribed to user identifier events from the UDM / UDR. In some embodiments, the UDM / UDR notifies the AMF of the user identifier events. In some embodiments, the process may include at least one of the following operations. Irrelevant operations are omitted for simplicity.

[0109] 701. The AMF has subscribed to user identifier events for the SUPI with UDM / UDR. The AMF subscribes to the user identifier events corresponding to the SUPI from the UDM / UDR. In some embodiments, the AMF may invoke a service operation (e.g., Nudm_SDM_Subscribe).

[0110] 702.UDM detects that a SUPI user identifier event has occurred (e.g., the user identifier is active, is deactivated (e.g., the user identified by the user identifier stops using the UE), or the active user identifier is replaced (e.g., a new active user identifier will replace the old active user identifier corresponding to the SUPI)).

[0111] 703. UDM notifies AMF (e.g., via notification) about user identifier events. In some embodiments, the notification includes the user identifier and an optional user profile ID, as well as information about the user identifier event (e.g., user identifier activation, deactivation, replacement, etc.). In some embodiments, the notification may optionally include user profile information corresponding to the user identifier.

[0112] In some embodiments, the notification includes at least one of the following: a user identifier corresponding to the user identifier event (e.g., an active user identifier or a deactivated user identifier); a user profile identifier corresponding to the user identifier event (e.g., an active user profile ID or a deactivated user profile ID); information about the user identifier event; and / or user profile information corresponding to the user identifier.

[0113] 704. The AMF sends a message (e.g., a PDU session modification message) to the SMF. In some embodiments, this message is used to modify the PDU session. In some embodiments, this message is carried in at least one of the parameters received from the UDM / UDR in operation 703.

[0114] 705. When the SMF receives a user identifier event, the SMF and PCF perform subsequent operations that are substantially the same as operations 504 to 507 in aspect 3.

[0115] 706. Based on the service and / or QoS settings in the user profile information and the PCC rules received from the PCF, the SMF / UPF performs subsequent processing, such as applying QoS rules to existing QoS flows and creating QoS flows for specific services. In some embodiments, the SMF (e.g., via the AMF) sends a message (e.g., a PDU session modification command) to the UE. In some embodiments, this message is a command for modifying the PDU session. In some embodiments, the message includes at least one of a user identifier, a user identifier state (e.g., activated or deactivated), or a PDU session state corresponding to a user identifier event. In some embodiments, the message may indicate the activation of the user identifier state and the PDU session state (e.g., user state, activated user identifier, current user not allowed PDU session (e.g., current user not allowed DNN / S-NSSAI for this PDU session), or current user in the current area not allowed PDU session, etc.).

[0116] In some embodiments of this disclosure, a user identifier indication is present in the UE subscription data in the UDM / UDR. In some embodiments, the user identifier indication may be located in the UE access and mobility subscription data, session management subscription data, and policy data subscription data.

[0117] In some embodiments of this disclosure, during registration or PDU session establishment, the AMF, SMF, and PCF obtain UE subscription data from the UDM / UDR. In some embodiments, when the AMF, SMF, or PCF finds a user identifier indication in the UE subscription data, the AMF, SMF, or PCF subscribes to user identifier events (e.g., user identifier information) from the UDM / UDR.

[0118] In some embodiments of this disclosure, during registration or PDU session establishment, the UE indicates its ability to support user identifier operations (e.g., via a user identifier support indication), and the AMF / SMF sends a user identifier permission indication to the UE.

[0119] In some embodiments of this disclosure, when the UDM determines that a SUPI user identifier is active, deactivated (e.g., the user identified by the user identifier stops using the UE), or the active user identifier is replaced (e.g., a new user identifier is activated to replace the old active user identifier), the UDM notifies the subscriber NF (e.g., AMF, SMF, or PCF) of the latest active user identifier and optional event code / ID.

[0120] In some embodiments of this disclosure, the UDM may additionally notify the subscriber NF of user profile information.

[0121] In some embodiments of this disclosure, when the AMF receives a notification from the UDM / UDR, the AMF sends the notification to the SMF.

[0122] In some embodiments of this disclosure, when the SMF receives a notification from the UDM / UDR, the SMF retrieves the user profile and sends the user ID to the PCF to obtain the PCC rules. In some embodiments, the SMF sends the user ID and PDU session state to the UE.

[0123] In some embodiments of this disclosure, when the PCF receives a notification from the UDM / UDR, the PCF retrieves the user profile and sends the PCC rules to the SMF.

[0124] Figure 8This is a schematic diagram relating to a wireless communication terminal 30 according to an embodiment of the present disclosure. The wireless communication terminal 30 may be a tag, mobile phone, laptop computer, tablet computer, e-book reader, or portable computer system, and is not limited thereto. The wireless communication terminal 30 may be used to implement the UE described in this disclosure. The wireless communication terminal 30 may include a processor 300 such as a microprocessor or application-specific integrated circuit (ASIC), a storage unit 310, and a communication unit 320. The storage unit 310 may be any data storage device storing program code 312 accessed and executed by the processor 300. Embodiments of the storage unit 310 include, but are not limited to, a subscriber identity module (SIM), read-only memory (ROM), flash memory, random access memory (RAM), hard disk, and optical data storage devices. The communication unit 320 may be a transceiver for sending and receiving signals (e.g., messages or packets) based on the processing results of the processor 300. In one embodiment, the communication unit 320 sends and receives signals via at least one antenna 322 or via wiring.

[0125] In one embodiment, storage unit 310 and program code 312 may be omitted, and processor 300 may include storage unit containing stored program code.

[0126] The processor 300 may, for example, implement any of the steps or operations in the exemplary embodiment on the wireless communication terminal 30 by executing program code 312.

[0127] The communication unit 320 may be a transceiver. Alternatively or as a supplement, the communication unit 320 may be combined with a transmitting unit and a receiving unit configured to transmit signals to and receive signals from the wireless communication node, respectively.

[0128] In some embodiments, the wireless communication terminal 30 can be used to perform the operations of the UE described in this disclosure. In some embodiments, the processor 300 and the communication unit 320 cooperate to perform the operations described in this disclosure. For example, the processor 300 performs operations and sends or receives signals, messages and / or information through the communication unit 320.

[0129] Figure 9This diagram relates to a wireless communication node 40 according to an embodiment of the present disclosure. The wireless communication node 40 may be a satellite, base station (BS), gNB, network entity, Domain Name System (DNS) server, Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), Radio Access Network (RAN), Next Generation RAN (NG-RAN), data network, core network, a communication node in the core network, or Radio Network Controller (RNC), and is not limited thereto. Furthermore, the wireless communication node 40 may include (execute) at least one network function, such as Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Application Function (AF), etc. The wireless communication node 40 may be used to implement the AMF, SMF, UPF, PCF, UDM, and UDR described in this disclosure. The wireless communication node 40 may include a processor 400, such as a microprocessor or ASIC, a storage unit 410, and a communication unit 420. The storage unit 410 may be any data storage device storing program code 412 accessed and executed by the processor 400. Examples of storage unit 410 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. Communication unit 420 may be a transceiver for sending and receiving signals (e.g., messages or packets) based on the processing results of processor 400. In one embodiment, communication unit 420 sends and receives signals via at least one antenna 422 or via wiring.

[0130] In one embodiment, storage unit 410 and program code 412 may be omitted. Processor 400 may include storage unit containing stored program code.

[0131] The processor 400 may, for example, implement any of the steps or operations in the exemplary embodiment on the wireless communication node 40 by executing program code 412.

[0132] The communication unit 420 may be a transceiver. Alternatively or as a supplement, the communication unit 420 may be a combination of a transmitting unit and a receiving unit configured to transmit signals to and receive signals from a wireless communication node (or wireless communication terminal), respectively.

[0133] In some embodiments, the wireless communication node 40 can be used to perform the gNB described in this disclosure. In some embodiments, the processor 400 and the communication unit 420 cooperate to perform the operations described in this disclosure. For example, the processor 400 performs operations and transmits or receives signals through the communication unit 420.

[0134] According to embodiments of this disclosure, a wireless communication method is also provided. In one embodiment, the wireless communication method can be performed using a network node (e.g., AMF, SMF, PCF). In one embodiment, the network node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0135] See Figure 10 In one embodiment, the wireless communication method includes: in response to receiving a user identifier indication from a data management node, a network node sending a subscription request to the data management node, the request being used to subscribe to a user identifier event corresponding to a subscribed identifier.

[0136] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0137] According to embodiments of this disclosure, another wireless communication method is also provided. In one embodiment, the wireless communication method can be performed using a wireless communication terminal (e.g., a UE). In one embodiment, the wireless communication terminal can be implemented using the wireless communication terminal 30 described in this disclosure, but is not limited thereto.

[0138] See Figure 11 In one embodiment, the wireless communication method includes: sending a user identifier support indication from a wireless communication terminal to a network node, indicating that the wireless communication terminal supports user identifier operation.

[0139] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0140] According to embodiments of this disclosure, another wireless communication method is also provided. In one embodiment, the wireless communication method can be performed using a data management node (e.g., UDM or UDR). In one embodiment, the data management node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0141] See Figure 12 In one embodiment, the wireless communication method includes: in response to sending a user identifier indication to a network node, a data management node receiving a subscription request from the network node, the request being for subscribing to a user identifier event corresponding to a subscription identifier.

[0142] In some embodiments, the wireless communication terminal used in this disclosure may instruct the aforementioned UE.

[0143] In some embodiments, the network node used in this disclosure may indicate the AMF, SMF, or PCF described above. For example, the network node may indicate the AMF in aspect 1 or 5 described above, the SMF in any of aspects 2 to 5 described above, or the PCF in any of aspects 2 to 5 described above.

[0144] In some embodiments, the data management node used in this disclosure may instruct the aforementioned UDM or UDR.

[0145] In some embodiments, the contract identifier used in this disclosure may indicate the aforementioned SUPI.

[0146] In some embodiments, the session management node used in this disclosure may instruct the aforementioned SMF.

[0147] In some embodiments, the policy control node used in this disclosure may instruct the aforementioned PCF.

[0148] In some embodiments, the access management node used in this disclosure may instruct the aforementioned AMF.

[0149] While various embodiments of this disclosure have been described above, it should be understood that they are by way of example only and not as limiting. Similarly, various figures may depict exemplary architectures or configurations provided to enable those skilled in the art to understand the exemplary features and functionality of this disclosure. However, those skilled in the art will understand that this disclosure is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0150] It should be understood that in this disclosure, the term "and / or" or the symbol " / " can include any and all combinations of one or more of the related listed items. For example, A and / or B and / or C includes any and all combinations of one or more of A, B, and C, including combinations of A, B, C, A and B, A and C, B and C, and A and B and C. Similarly, A / B / C includes any and all combinations of one or more of A, B, and C, including combinations of A, B, C, A and B, A and C, B and C, and A and B and C.

[0151] It should also be understood that any reference to elements using names such as "first," "second," etc., in this document generally does not restrict the number or order of these elements. Rather, these names can be used as a convenient means of distinguishing two or more elements or instances of elements in this document. Therefore, mentioning the first and second elements does not imply that only two elements can be used, nor does it imply that the first element must precede the second element in some way.

[0152] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0153] Those skilled in the art will further understand that any of the various illustrative logic blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software unit" for convenience), or any combination of these technologies.

[0154] To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, operations, and steps have been generally described above according to their functions. Whether this function is implemented as hardware, firmware, software, or a combination of these technologies depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., can be configured to perform one or more functions described herein. The terms “configured to” or “configured for” used herein with respect to a specified operation or function refer to the physical construction, programming, and / or arrangement to perform a specified operation or function of a processor, device, component, circuit, structure, machine, unit, etc.

[0155] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, cells, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, cells, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but may also be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein. If implemented in software, these functions may be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps or operations of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium.

[0156] Computer-readable media include computer storage media and communication media, including any medium capable of transferring computer programs or code from one place to another. Storage media can be any available medium that is accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer.

[0157] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Furthermore, for the purposes of discussion, various units are described as discrete units; however, as will be apparent to those skilled in the art, two or more units may be combined to form a single unit performing the relevant functions according to embodiments of this disclosure.

[0158] Furthermore, embodiments of this disclosure may also employ memory or other storage devices and communication components. It should be understood that, for clarity, the above description is illustrated with reference to different functional units and processors. However, it will be apparent that any suitable allocation of functions among different functional units, processing logic elements, or domains can be employed without departing from the spirit of this disclosure. For example, functions performed by separate processing logic elements or controllers as shown in the figures may also be performed by the same processing logic element or controller. Therefore, references to specific functional units refer only to suitable means of implementing the functions and do not imply any strict logical or physical structure or organization.

[0159] Various modifications to the implementations described herein will be apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of the claims. Therefore, this disclosure is not limited to the implementations shown herein, but should be given the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the appended claims.

Claims

1. A wireless communication method, comprising: In response to receiving a user identifier indication from the data management node, the network node sends a subscription request to the data management node, the subscription request being used to subscribe to the user identifier event corresponding to the subscribed identifier.

2. The wireless communication method according to claim 1, wherein, The user identifier event includes at least one of the following: The user identifier corresponding to the aforementioned contract identifier is active; The user identifier corresponding to the aforementioned subscription identifier is disabled; or Replace the first active user identifier corresponding to the contract identifier with the second active user identifier corresponding to the contract identifier.

3. The wireless communication method according to claim 1 or 2, wherein, The network node receives a notification of the user identifier event from the data management node, and the notification includes the user identifier corresponding to the user identifier event.

4. The wireless communication method according to claim 3, wherein, The notification also includes at least one of the following: The user profile identifier corresponding to the user identifier event; Information about the user identifier event; or User configuration file information corresponding to the user identifier.

5. The wireless communication method according to claim 3 or 4, wherein, In response to the notification, the network node retrieves first information from the data management node, the first information including: user profile information corresponding to the user identifier.

6. The wireless communication method according to any one of claims 1 to 5, wherein, The network node sends a first message to the policy control node, session management node, or access management node, the first message including at least one of the following: The user identifier corresponding to the user identifier event; The user profile identifier corresponding to the user identifier event; Information about the user identifier event; or User configuration file information corresponding to the user identifier.

7. The wireless communication method according to claim 1 or 2, wherein, The network node receives a first message from a policy control node, a session management node, or an access management node, the first message including at least one of the following: The user identifier corresponding to the user identifier event; The user profile identifier corresponding to the user identifier event; Information about the user identifier event; or User configuration file information corresponding to the user identifier.

8. The wireless communication method according to claim 7, wherein, The network node retrieves first information from the data management node in response to at least one of the following: The network node receives the first message from the session management node; The network node receives the first message from the policy control node; or The network node receives the first message from the access management node.

9. The wireless communication method according to claim 8, wherein, The first message is sent via a message associated with modifying the session management policy or via a message associated with modifying the Protocol Data Unit (PDU) session.

10. The wireless communication method according to any one of claims 1 to 9, wherein, The network node sends a second message to the wireless communication terminal to indicate at least one of the user identifier, user identifier status, or protocol data unit (PDU) session status corresponding to the user identifier event.

11. The wireless communication method according to claim 10, wherein, The second message is sent via a command used to modify the PDU session.

12. The wireless communication method according to any one of claims 1 to 11, wherein, The user identifier indicates that it is received in the subscription data.

13. The wireless communication method according to any one of claims 1 to 12, wherein, The network node performs at least one of the following operations: Receive user identifier support indication from wireless communication terminal; or In response to receiving a user identifier support indication, a message including the user identifier support indication is sent to the data management node.

14. The wireless communication method according to any one of claims 1 to 13, wherein, The network node sends a message to the wireless communication terminal, including a user identifier permission indication.

15. The wireless communication method according to any one of claims 1 to 14, wherein, The network node sends a message including the user identifier indication to the policy control node or receives a message from the session management node.

16. The wireless communication method according to claim 15, wherein, The message including the user identifier is sent via a message used to establish a session management policy association.

17. A wireless communication method, comprising: The wireless communication terminal sends a user identifier support indication to the network node, indicating that the wireless communication terminal supports user identifier operation.

18. The wireless communication method according to claim 17, wherein, The wireless communication terminal receives a user identifier permission indication from the network node.

19. The wireless communication method according to claim 17 or 18, wherein, The wireless communication terminal receives a message indicating at least one of the user identifier, user identifier status, or protocol data unit (PDU) session status corresponding to the user identifier event.

20. A wireless communication method, comprising: In response to sending a user identifier indication to a network node, a data management node receives a subscription request from the network node, the subscription request being used to subscribe to a user identifier event corresponding to the subscription identifier.

21. The wireless communication method according to claim 20, wherein, The user identifier event includes at least one of the following: The user identifier corresponding to the aforementioned contract identifier is active; The user identifier corresponding to the aforementioned subscription identifier is disabled; or Replace the first active user identifier corresponding to the contract identifier with the second active user identifier corresponding to the contract identifier.

22. The wireless communication method according to claim 20 or 21, wherein, The data management node sends a notification of the user identifier event to the network node, and the notification includes the user identifier corresponding to the user identifier event.

23. The wireless communication method according to claim 22, wherein, The notification also includes at least one of the following: The user profile identifier corresponding to the user identifier event; Information about the user identifier event; or User configuration file information corresponding to the user identifier.

24. The wireless communication method according to claim 22 or 23, wherein, In response to the notification, the network node retrieves first information from the data management node, the first information including: user profile information corresponding to the user identifier.

25. The wireless communication method according to any one of claims 20 to 24, wherein, In response to receiving the user identifier support indication, the data management node receives a message including the user identifier support indication from the network node.

26. A network node, comprising: Communication unit; as well as The processor is configured to: in response to receiving a user identifier indication from a data management node, send a subscription request to the data management node via the communication unit, the subscription request being used to subscribe to a user identifier event corresponding to a subscribed identifier.

27. The network node according to claim 26, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 2 to 16.

28. A wireless communication terminal, comprising: Communication unit; as well as The processor is configured to send a user identifier support indication to a network node via the communication unit, indicating that the wireless communication terminal supports user identifier operation.

29. The wireless communication terminal according to claim 28, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 18 to 19.

30. A data management node, comprising: Communication unit; as well as The processor is configured to receive a subscription request from the network node via the communication unit in response to sending a user identifier indication to the network node, the subscription request being used to subscribe to a user identifier event corresponding to a subscription identifier.

31. The data management node according to claim 30, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 21 to 25.

32. A computer program product comprising computer-readable program medium code stored thereon, the code causing the processor to implement the wireless communication method of any one of claims 1 to 25 when executed by the processor.

Images