Method and apparatus for user identifiers in network systems

Abstract

A method for supporting User Identifiers (UIDs) in a network system, executed by a User Equipment (UE), includes: determining human user login; constructing a network UID format based on an Enhanced Subscription Permanent Identifier (eSUPI) with a UID format and / or a Network Access Identifier (NAI) format with a network UID; and sending the network UID format to a first core network element via a registration request message.

Description

Technical Field

[0001] This application relates to the field of communication systems, and more specifically, to methods and apparatus for user identifiers (UIDs) in network systems. Background Technology

[0002] A Subscription Permanent Identifier (SUPI) is a technology used to uniquely identify subscribers within a network system, ensuring seamless service continuity and personalized connectivity across multiple access networks and devices. SUPI is used for authentication, authorization, and subscriber-specific service provision. Its standard format is based on the International Mobile Subscriber Identifier (IMSI), which includes the Mobile Country Code (MCC), Mobile Network Code (MNC), and Mobile Subscription Identification Number (MSIN), forming an MCC-MNC-MSIN structure to ensure global uniqueness and interoperability. Furthermore, for non-3GPP access scenarios, SUPI can adopt a network access identifier (NAI) format similar to an email address to accommodate situations where IMSI-based identifiers are not applicable. However, the current SUPI format has limitations in meeting the growing demand for personalized identities in 5G networks. As the 5G ecosystem evolves, there is an increasing need to support dynamic network configuration and services tailored to user-specific needs, including non-3GPP devices and diverse user profiles. The existing SUPI format is primarily designed for identifying subscriptions and is insufficient to fully meet the dynamic and personalized service needs of advanced network environments. Therefore, further technological advancements are needed to achieve more flexible, user-centric identity management solutions that can meet the diverse application requirements of modern network systems.

[0003] Therefore, a method and apparatus for user identifiers (UIDs) are needed in network systems to address problems in related technologies and other issues. Summary of the Invention

[0004] The purpose of this application is to provide a method and apparatus for using UIDs in a network system to solve problems and other issues in the related art.

[0005] In a first aspect of this application, a method for supporting UIDs in a network system, performed by user equipment (UE), includes: determining human user login; constructing a network UID format based on an enhanced subscription permanent identifier (eSUPI) and / or a network access identifier (NAI) format having a UID format; and sending the network UID format to a first core network element via a registration request message.

[0006] In a second aspect of this application, a UE includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The UE is configured to provide the method described above.

[0007] In a third aspect of this application, a method for supporting UIDs in a network system executed by a network includes: determining a network UID format based on an eSUPI having a UID format and / or a NAI format of the network UID; and receiving the network UID format from a UE by a first core network element of the network via a registration request message.

[0008] In a fourth aspect of this application, a network includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The network is configured to provide the methods described above.

[0009] In a fifth aspect of this application, a non-transitory machine-readable storage medium stores instructions that, when executed by a computer, cause the computer to perform the method described above.

[0010] In a sixth aspect of this application, a chip includes a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is mounted to perform the methods described above.

[0011] In a seventh aspect of this application, a computer-readable storage medium is provided, wherein a computer program is stored to cause a computer to perform the above-described method.

[0012] In an eighth aspect of this application, a computer program product includes a computer program that causes a computer to perform the methods described above.

[0013] In a ninth aspect of this application, a computer program causes a computer to perform the above-described method.

[0014] In a tenth aspect of this application, a UE includes a determiner and a transmitter. The determiner is configured to determine human user login by constructing a network UID format based on an eSUPI having a UID format and / or a NAI format of a network UID. The transmitter is configured to send the network UID format to a first core network element via a registration request message.

[0015] In the eleventh aspect of this application, a network includes a determiner and a receiver. The determiner is configured to determine a network UID format based on an eSUPI having a UID format and / or a NAI format of the network UID. The receiver is configured to receive the network UID format from a UE via a registration request message. Attached Figure Description

[0016] To more clearly illustrate the embodiments of this application or related technologies, the following drawings will be described in conjunction with a brief description of the embodiments. Obviously, these drawings are only some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any additional effort.

[0017] Figure 1A This is a block diagram of a UE and a network in a communication network system according to an embodiment of this application.

[0018] Figure 1B This is a block diagram of a UE according to an embodiment of this application.

[0019] Figure 1C This is a block diagram of a network according to an embodiment of this application.

[0020] Figure 2 This is a flowchart of a method for supporting UID in a network system, executed by a UE according to an embodiment of this application.

[0021] Figure 3 This is a flowchart of a method for supporting UIDs in a network system, executed by a network according to an embodiment of this application.

[0022] Figure 4 This is a schematic diagram of a process according to an embodiment of the present application, wherein the UE always sends a subscription concealed identifier (SUCI), which is a privacy-protected identifier that includes a concealed subscription permanent identifier (SUPI).

[0023] Figure 5 This is a flowchart illustrating registration using an eSUPI with a UID, according to an embodiment of this application.

[0024] Figure 6 This is a flowchart of an advanced process that supports the identification of a UE's 3GPP subscription when a human user accesses a service via a network using a UID, according to an embodiment of this application.

[0025] Figure 7 This is a flowchart illustrating a user state change according to an embodiment of this application.

[0026] Figure 8 This is an example block diagram of a computing device according to an embodiment of this application.

[0027] Figure 9 This is a block diagram of a communication system according to an embodiment of this application. Detailed Implementation

[0028] The embodiments of this application will be described in detail below with reference to the accompanying drawings, including technical content, structural features, implementation objectives, and effects. Specifically, the terminology used in the embodiments of this application is only used to describe the purpose of specific embodiments and is not intended to limit this application.

[0029] The technical solutions of this application embodiment can be applied to various communication systems, such as Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Advanced Long Term Evolution (LTE-A) systems, New Radio (NR) systems, evolution systems of NR systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, Universal Mobile Telecommunication System (UMTS), Global Interoperability for Microwave Access (WiMAX) communication systems, and Wireless Local Area Networks (WLANs). Area network (WLAN), wireless fidelity (Wi-Fi), the future 5th generation (5G) system (also known as NR system), or other communication systems.

[0030] Optionally, the communication system in this application embodiment can be applied to unlicensed spectrum, which can also be regarded as shared spectrum; or the communication system in this application embodiment can be applied to licensed spectrum, which can also be regarded as non-shared spectrum.

[0031] A subscription permanent identifier (SUPI) is a unique identifier for a user profile within a network, enabling seamless service continuity and personalized connectivity across different access networks and devices. The SUPI is a crucial component of the authentication, authorization, and user-specific service delivery processes. The SUPI format is carefully defined and constructed to ensure global uniqueness and interoperability across different networks and geographic regions.

[0032] SUPI based on IMSI: The common form of SUPI is derived from the International Mobile Subscriber Identifier (IMSI). This format includes the Mobile Country Code (MCC), Mobile Network Code (MNC), and Mobile Subscription Identification Number (MSIN), and is usually presented in the format of MCC-MNC-MSIN.

[0033] SUPI based on Network Access Identifier (NAI): For non-3GPP access scenarios, SUPI can be in the form of NAI. This format is user-friendly, similar to an email address, and therefore suitable for situations where IMSI-based SUPI cannot be used.

[0034] To further enhance user experience, optimize performance, and extend services to non-3GPP devices and diverse user profiles, 5G systems may support the creation and use of personalized identities. For example, network settings can be modified to provide services tailored to specific user needs, which may differ from those associated with subscription identifiers (such as SUPIs). While SUPIs are effective at identifying subscriptions, they do not fully meet the dynamic and personalized services and settings required by modern adaptive network environments. This limitation underscores the need for more flexible identity management solutions in 5G networks.

[0035] In some embodiments, an enhanced subscription permanent identifier (eSUPI) including a user identity (UID) is proposed to support multiple user identifiers in the same user equipment (UE) subscription.

[0036] In other embodiments, various methods and apparatuses are proposed to identify a human user associated with a UE's 3GPP subscription when the user accesses services via a 5G system (5GS) using a user identifier. It should be noted that these methods are applicable regardless of whether the eSUPI with a UID described in some embodiments is used.

[0037] In addition, in some embodiments, a method is proposed to associate user route selection policy (URSP) rules with user identifiers in 5GS.

[0038] Figure 1A The illustration shows a UE 10 and a communication network 20 in a communication network system 30 (e.g., an NR system) according to embodiments of this application in some embodiments. The communication network system 30 includes the UE 10 and the network 20. The UE 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. The network 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and the transceiver 23. The processor 11 or 21 may be configured to implement the functions, procedures, and / or methods described herein. Layers of the wireless interface protocol may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled to the processor 11 or 21 and stores various information to operate the processor 11 or 21. The transceiver 13 or 23 is operatively coupled to the processor 11 or 21 and transmits and / or receives wireless signals.

[0039] Processor 11 or 21 may include application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. Memory 12 or 22 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. Transceiver 13 or 23 may include baseband circuitry for processing radio frequency signals. When these embodiments are implemented in software, the techniques described herein can be implemented by modules (e.g., processes, functions, etc.) that perform the functions described herein. These modules may be stored in memory 12 or 22 and executed by processor 11 or 21. Memory 12 or 22 may be built into processor 11 or 21 or may be external to processor 11 or 21, in which case they may be communicatively coupled to processor 11 or 21 in various ways known in the art.

[0040] In some embodiments, processor 11 is configured to determine human user login, construct a network UID format based on eSUPI with UID format and / or NAI format of network UID, and transceiver 13 is configured to send the network UID format to the first core network element of network 20 via a registration request message. This can solve problems in related technologies and other issues.

[0041] In some embodiments, processor 21 is configured to determine the network UID format based on the eSUPI having a UID format and / or the NAI format of the network UID, and transceiver 23 is configured to receive the network UID format from UE 10 via a registration request message. This can solve problems in related technologies and other issues.

[0042] Figure 1B An example of a UE 10B according to an embodiment of this application is shown. The UE 10B is configured to implement some embodiments of this application. Some embodiments of this application can be implemented in the UE 10B using any appropriately configured hardware and / or software. The UE 10B includes a determiner 101B and a transmitter 102B. The determiner 101B is configured to determine human user login by constructing a network UID format based on an eSUPI with a UID format and / or a NAI format of a network UID. The transmitter 102B is configured to send the network UID format to a first core network element via a registration request message. This can solve problems in related technologies and other issues.

[0043] Figure 1C An example of a network 20C according to an embodiment of this application is shown. The network 20C is configured to implement some embodiments of this application. Some embodiments of this application can be implemented in the network 20C using any appropriately configured hardware and / or software. The network 20C includes a determiner 201C and a receiver 202C. The determiner 201C is configured to determine the network UID format based on an eSUPI having a UID format and / or the NAI format of the network UID. The receiver 202C is configured to receive the network UID format from the UE via a registration request message. This can solve problems in related technologies and other issues.

[0044] Figure 2This is an example of a method 200 for supporting UIDs in a network system, executed by a UE, according to an embodiment of this application. The method 200 for supporting UIDs in a network system, executed by a UE, is configured to implement some embodiments of this application. Some embodiments of this application can be implemented in the method 200 for supporting UIDs in a network system, executed by a UE, using any appropriately configured hardware and / or software. In some embodiments, the method 200 for supporting UIDs in a network system, executed by a UE, includes: operation 202, determining a human user login, constructing a network UID format based on an eSUPI having a UID format and / or a NAI format of the network UID; and operation 204, sending the network UID format to a first core network element via a registration request message. This can solve problems in related technologies and other issues.

[0045] In some embodiments, the network UID format includes the 5GS UID format, and the network UID includes the 5GS UID. In some embodiments, the first core network element includes an access and mobility management function (AMF). In some embodiments, the method further includes performing authentication and authorization using a 5G authentication scheme or a secondary authentication scheme, involving the first core network element, unified data management (UDM), authentication server function (AUSF), or identity management function (IMF). In some embodiments, the network UID format is sent to the first core network element via a registration request message, enabling the UDM or IMF to parse the network UID from the eSUPI with the UID format or the NAI format of the network UID. In some embodiments, the eSUPI with the UID format is configured to extend the current SUPI format by including a UID component, and the eSUPI with the UID format is defined as a new SUPI type different from the current SUPI type. In some embodiments, the eSUPI with the UID format is formed by concatenating the current SUPI format with the network UID, and there is a separator between the current SUPI format and the network UID. In some embodiments, the current SUPI format includes: SUPI type value 0, representing the International Mobile Subscriber Identifier (IMSI); SUPI type value 1, representing the Network Specific Identifier (NSI); SUPI type value 2, representing the Global Line Identifier (GLI); and / or SUPI type value 3, representing the Global Cable Identifier (GCI).

[0046] In some embodiments, the SUPI type value is assigned to 4 to support eSUPIs with a UID format. In some embodiments, eSUPIs with a UID format are configured to include UID information in a structured format. This structured format may follow the pattern: subscriber_name <separator>5G_UID<UID information> @realm. In some embodiments, in standalone non-public network (SNPN) scenarios, eSUPIs with UID format follow the same pattern, and if a realm part is available, the realm part also includes the SNPN's network identifier (NID). In some embodiments, the NID format of the network UID includes a non-empty string as a unique identifier, a mobile network code, and / or a mobile country code. For example, the NID format of the network UID follows the following format:<network_UID> @5gc-uid.mnc <mnc>.mcc <mcc>.3gppnetwork.org, where network_UID is a non-empty string that serves as a unique identifier for human users; <mnc>The mobile network code indicates the user's public land mobile network (PLMN). <mcc>The code indicates the country of movement and also identifies the PLMN; the PLMN includes a home PLMN (HPLMN) or a visited PLMN (VPLMN). In some embodiments, the NAI format of the network UID still applies in the SNPN scenario, wherein, if the domain portion is available, the domain portion also includes the SNPN's NID.

[0047] In some embodiments, the network UID format is constructed by including specific tags in the domain portion. In some embodiments, the user identity profile is associated with the UE's network subscription. For example, the user identity profile associated with the UE's network subscription is stored in a unified data repository (UDR). In some embodiments, the logic for processing the user identity profile is performed by a unified data management (UDM) function or a dedicated IMF. In some embodiments, the packet data unit (PDU) session flow is configured to associate the UID with PDU sessions, policy and charging control (PCC) rules and / or policies. In some embodiments, a subset of data marked as user profile subscription data is associated with a specific subscription identified by a SUPI. Each user profile is associated with one or more user identities, and the user profile subscription data for each user identity includes at least one of the following information: UID; user identity-specific service settings and parameters; UID service category; UID-specific network resources, based on the subscription associated with the UID; quality of service (QoS) information, including a default 5G QoS indicator (5QI); additional user identifiers for the user's identity and linked network subscriptions; or linked subscriptions identified by a SUPI or linked UEs identified by a UE identifier. For example, the subset of data marked as user profile subscription data is stored in a UDR.

[0048] In some embodiments, a UID is associated with one or more subscriber category identifiers, each subscriber category identifier being associated with an operator-defined policy that applies to UIDs belonging to the corresponding category. In some embodiments, the UDM or IMF includes supporting the processing of user identity profiles by performing at least one of the following functions: managing user identity profiles, including storing and maintaining a user identity profile for each subscriber in the 5G system; configuring subscription-related user identity profiles by the operator; or allowing the operator to update subscription data in the user identity profile by associating or deassociating a UID with a specific subscription in an operator-controlled manner. In some embodiments, a subset of data marked as user identifier-specific control data is associated with a specific subscription identified by a SUPI, and user identifier-specific policy control information is per SUPI and / or per UID. For example, user identifier-specific policy control information is stored in a UDR and updated by the PCF during PDU session establishment or modification procedures using Nudr services. For example, a subset of data marked as user identifier-specific control data may be stored in a UDR. In some embodiments, user identifier-specific policy control information includes at least one of the following: a user inactivity timer value indicating a threshold duration after which the user is considered inactive; or the maximum user data rate for the uplink or downlink.

[0049] In some embodiments, a subset of data labeled as user state data is associated with a specific subscription and UID, and user state information is associated with a data key SUPI and / or UID, the data key SUPI and / or UID being used for one or more UIDs in a specific SUPI. For example, the subset of data labeled as user state data may be stored in a UDR. For example, user state information may be stored by a UDR. In some embodiments, user state data is updated by the NEF. In some embodiments, user state data includes user state information, including active, inactive, and / or suspended states. In some embodiments, a UID associated with a specific subscription is in a state including active, deactivated, or suspended states, and the device automatically suspends the UID if the user is inactive on the device or UE for a certain duration. In some embodiments, during the session management process, user state information is stored or updated in the local configuration by the SMF according to the home operator's policy. In some embodiments, changes in user state are sent to the subscribed NF via the Nsmf_EventExposure_Subscribe function. In some embodiments, user state information is maintained or updated by the AMF in the local configuration reported by the UE.

[0050] In some embodiments, during the PDU session establishment procedure for the UID, the UE registers with the network using its subscription and establishes a NAS security context with the AMF, and the UID associated with the subscription has been authenticated and authorized. In some embodiments, if the UE supports the UID, when the user is active, the UE indicates the current UID in the N1 SM container during the PDU session establishment procedure. In some embodiments, during the PDU session establishment process, the UE supports the first core network element or SMF to perform at least one of the following operations: The first core network element selects an SMF to manage the PDU session associated with the UID provided by the UE; if there is no association between the first core network element and the SMF for the PDU session ID associated with the UID, the first core network element calls Nsmf_PDUSession_CreateSMContextRequest using the PDU session ID, UID, and related parameters to create an SM context; if there is an association between the first core network element and the SMF for the PDU session ID associated with the UID, the first core network element calls Nsmf_PDUSession_CreateSMContextRequest using the same parameters to update the SM context; the SMF checks whether the UE's request conforms to the user identity profile; if the user identity profile subscription data is unavailable, the SMF obtains the user identity profile subscription using Nudm_SDM_Get or through a dedicated IMF procedure, and the subscription receives modification notifications through the UDM or IMF; the UDM or IMF obtains information from the UDR using Nudr_DM_Query; the SMF and policy control functions (policy The SMF (Service Class Function) executes the User Identifier Policy Association (PCF) establishment process to obtain the default PCC rules for the PDU session associated with the UID. If the request type indicates an existing PDU session, the SMF provides information about the policy control request triggering conditions, which have been met through the user identifier policy association or modification process initiated by the SMF. If the service class identifier is associated with the UID, the policy defined by the operator for this service class is applied to the UID. Alternatively, the SMF continues to execute the PDU session establishment request process.

[0051] In some embodiments, during the user state update procedure, the UE detects user activity with a UID and identifies a state change. In some embodiments, the UE requests an update to the user state in the user identity profile by sending a NAS message. In some embodiments, during the user state update procedure, the UE supports a first core network element or SMF to perform at least one of the following operations: the first core network element uses the UE's report and its local UE context data to determine the UID state change, wherein, if the user state changes, the first core network element sends an event report and timestamp to the associated notification endpoint of the NEF via a Namf_EventExposure_Notify message, and / or the NEF uses the Nudr_DM_Create or Nudr_DM_Update service operation to store the information and timestamp together in the UDR; in the session management procedure, the SMF monitors user activity and determines whether the UID state has changed; or the SMF sends a user state change event report and timestamp to the associated notification endpoint of the NEF via a Nsmf_EventExposure_Notify message, and / or the NEF uses the Nudr_DM_Create or Nudr_DM_Update service operation to store the information and timestamp together in the UDR. In some embodiments, the UID associated with the UE's traffic is enabled by using a traffic descriptor and a UID descriptor in the URSP rule.

[0052] Figure 3 This is an example of a method 300 for supporting UIDs in a network system, performed by a network, according to an embodiment of this application. The method 300 for supporting UIDs in a network system, performed by a network, is configured to implement some embodiments of this application. Some embodiments of this application can be implemented in the method 300 for supporting UIDs in a network system, performed by a network, using any appropriately configured hardware and / or software. In some embodiments, the method 300 for supporting UIDs in a network system, performed by a network, includes: operation 302, determining a network UID format based on an eSUPI having a UID format and / or a NAI format of the network UID; and operation 304, a first core network element of the network receiving the network UID format from the UE via a registration request message. This can solve problems in related technologies and other issues.

[0053] In some embodiments, the network UID format includes a 5GS UID format, and the network UID contains a 5GS UID. In some embodiments, the first core network element includes an AMF. In some embodiments, the method further includes determining authentication and authorization using a 5G authentication scheme or a secondary authentication scheme, involving the first core network element, UDM, AUSF, or IMF. In some embodiments, the first core network element receives the network UID format via a registration request message, enabling the UDM or IMF to parse the network UID from the eSUPI with the UID format and / or the NAI format of the network UID. In some embodiments, the eSUPI with the UID format is configured to extend the current SUPI format by incorporating a UID component, and the eSUPI with the UID format is defined as a new SUPI type different from the current SUPI type. In some embodiments, the eSUPI with the UID format is formed by concatenating the current SUPI format with the network UID, and a separator exists between the current SUPI format and the network UID. In some embodiments, the current SUPI format includes: SUPI type value 0, representing IMSI; SUPI type value 1, representing NSI; SUPI type value 2, representing GLI; and / or SUPI type value 3, representing Global Cable Identifier (GCI).

[0054] In some embodiments, the SUPI type value is assigned to 4 to support eSUPIs with a UID format. In some embodiments, eSUPIs with a UID format are configured to include UID information in a structured format. This structured format may follow the pattern: subscriber_name <separator>5G_UID<UID information> @realm. In some embodiments, in SNPN scenarios, eSUPIs with a UID format follow the same pattern, and if a domain portion is available, the domain portion also includes the SNPN's NID. In some embodiments, the NAI format of the network UID includes a non-empty string as a unique identifier, a mobile network code, and / or a mobile country code. For example, the NAI format of the network UID follows the format below:<network_UID> @5gc-uid.mnc <mnc>.mcc <mcc>.3gppnetwork.org, where network_UID is a non-empty string that serves as a unique identifier for human users; <mnc>The mobile network code indicates the user's Public Land Mobile Network (PLMN). <mcc>The mobile country code is indicated, and the PLMN is also identified; the PLMN includes a home PLMN (HPLMN) or a visited PLMN (VPLMN). In some embodiments, the NAI format of the network UID still applies in SNPN scenarios, where, if the domain portion is available, the domain portion also includes the SNPN's NID. In some embodiments, the network UID format is constructed by including specific tags in the domain portion. In some embodiments, the user identity profile is associated with the UE's network subscription. For example, the user identity profile associated with the UE's network subscription is stored in the UDR.

[0055] In some embodiments, the logic for processing user identity profiles is executed by a UDM function or a dedicated IMF. In some embodiments, the PDU session flow is configured to associate a UID with a PDU session, PCC rules, and / or policies. In some embodiments, a subset of data marked as user identity profile subscription data is associated with a specific subscription identified by a SUPI, each user identity profile is associated with one or more user identities, and the user identity profile subscription data for each user identity contains at least one of the following information: UID; user identity-specific service settings and parameters; UID service category; UID-specific network resources based on the subscription associated with the UID; QoS information, including the default 5QI; additional user identifiers for the user's user identity and linked network subscriptions; or linked subscriptions identified by a SUPI or linked UEs identified by a UE identifier. For example, the subset of data marked as user identity profile subscription data is stored in a UDR. In some embodiments, a UID is associated with one or more subscriber category identifiers, each subscriber category identifier is associated with an operator-defined policy, and the operator-defined policy applies to UIDs belonging to the corresponding category. In some embodiments, the UDM or IMF includes supporting the processing of user profiles by performing at least one of the following functions: managing user profiles, including storing and maintaining user profiles for each subscriber in the 5G system; pre-configuring user profiles associated with subscriptions by the operator; or allowing the operator to update user profile subscription data in an operator-controlled manner by associating or deassociating UIDs with specific subscriptions.

[0056] In some embodiments, a subset of data labeled as user identifier-specific control data is associated with a specific subscription identified by a SUPI, and the user identifier-specific policy control information is partitioned by SUPI and / or UID. For example, user identifier-specific policy control information is stored in a UDR and updated by the PCF during the PDU session establishment or modification process using the Nudr service. For example, the subset of data labeled as user identifier-specific control data may be stored in a UDR. In some embodiments, the user identifier-specific policy control information includes at least one of the following: a user inactivity timer value indicating a threshold duration after which the user is considered inactive; or the maximum user data rate for the uplink or downlink. In some embodiments, a subset of data labeled as user state data is associated with a specific subscription and a UID, and the user state information is associated with a data key SUPI and / or a UID, the data key SUPI and / or UID being used for one or more UIDs in a specific SUPI. For example, the subset of data labeled as user state data may be stored in a UDR. For example, user state information may exist in a UDR. In some embodiments, user state data is updated by the NEF. In some embodiments, user state data includes user state information, which includes active, inactive, and / or suspended states. In some embodiments, a UID associated with a specific subscription is in a state including active, deactivated, or suspended states. If a user is inactive on the device or UE for a certain duration, the device automatically suspends the UID. In some embodiments, during the session management process, user state information is stored or updated locally by the SMF according to the home operator's policy. In some embodiments, changes in user state are sent to subscribed NFs via the Nsmf_EventExposure_Subscribe function. In some embodiments, user state information is maintained or updated by the AMF in the local configuration.

[0057] In some embodiments, during the PDU session establishment process for the UID, the first core network element and the UE determine the subscription and the NAS security context, and the UID associated with the subscription has been authenticated and authorized. In some embodiments, if the UE supports the UID, when the user is active during the PDU session establishment process, the first core network element determines the current UID in the N1 SM container. In some embodiments, during the PDU session establishment process, the first core network element or SMF of the network performs at least one of the following operations: wherein the first core network element selects an SMF to manage the PDU session associated with the UID provided by the UE; if there is no association between the first core network element and the SMF for the PDU session ID associated with the UID, the first core network element calls Nsmf_PDUSession_CreateSMContextRequest using the PDU session ID, UID, and related parameters to create an SM context; if there is an association between the first core network element and the SMF for the PDU session ID associated with the UID, the first core network element calls Nsmf_PDUSession_CreateSMContextRequest using the same parameters to update the SM context; the SMF checks whether the UE's request is compliant. User identity profile; if user identity profile subscription data is unavailable, the SMF obtains the user identity profile subscription data using Nudm_SDM_Get or through a dedicated IMF process, and subscribes to receive modification notifications through the UDM or IMF. The UDM or IMF uses Nudr_DM_Query to obtain information from the UDR; the SMF and PCF execute the user identifier policy association establishment process to obtain the default PCC rules for the PDU session associated with the UID; if the request type indicates an existing PDU session, the SMF provides information on the policy control request triggering conditions, which have been met through the user identifier policy association or modification process initiated by the SMF; if the service category identifier is associated with the UID, the policy defined by the operator for this service category is applied to the UID; or the SMF continues to execute the PDU session establishment request process.

[0058] In some embodiments, during the user state update procedure, the first core network element determines the user activity and state changes with a UID. In some embodiments, the first core network element updates the user state in the user identity profile. In some embodiments, during the user state update procedure, the first core network element or the SMF performs at least one of the following operations: the first core network element uses the UE's report and its local UE context data to determine the UID state change, wherein, if the user state changes, the first core network element sends an event report and timestamp to the associated notification endpoint of the NEF via a Namf_EventExposure_Notify message, and / or the NEF uses the Nudr_DM_Create or Nudr_DM_Update service operation to store the information and timestamp together in the UDR; in the session management procedure, the SMF monitors user activity and determines whether the UID state has changed; or the SMF sends a user state change event report and timestamp to the associated notification endpoint of the NEF via a Nsmf_EventExposure_Notify message, and / or the NEF uses the Nudr_DM_Create or Nudr_DM_Update service operation to store the information and timestamp together in the UDR. In some embodiments, the UID associated with the UE's traffic is enabled by using a traffic descriptor and a UID descriptor in the URSP rule.

[0059] eSUPI with UID: Figure 4 A process according to an embodiment of this application is illustrated, wherein the UE consistently sends a subscription concealed identifier (SUCI), which is a privacy-protected identifier containing a concealed subscription permanent identifier (SUPI). This process ensures the protection of user identity during communication. For clarity and as a reference, Figure 4 Adapted from TS 23.003 Figure 2 .2B-1.

[0060] SUPI is a globally unique identifier assigned to each subscriber in a 5G system, as defined in Clause 5.9.2 of 3GPP TS 23.501. Enhanced SUPI (eSUPI) extends the existing SUPI format by incorporating a UID component. According to TS 23.003, eSUPI containing a human UID is formatted as NAI. In addition to the standard NAI format (username@realm), eSUPI with a UID introduces a separator between "username" and "UID". Possible separators include exclamation marks (!), underscores (_), and other characters. Therefore, eSUPI with a UID follows the format "username!UID@realm", where "!" represents the separator, but other separators may also be used. Figure 4 As shown, in some embodiments, the UE may always send SUCI, which is a privacy-protected identifier that contains a hidden SUPI.

[0061] Figure 4 As shown, in some embodiments, the SUPI type is represented by a value ranging from 0 to 7, which identifies the SUPI type hidden within the SUCI. The currently defined values ​​are as follows: 0: IMSI.

[0062] 1: NSI.

[0063] 2: GLI.

[0064] 3: GCI.

[0065] 5 to 7: Reserved for future use.

[0066] With the introduction of eSUPI containing a human UID, the SUPI type can be assigned a new value: 4: eSUPI with a human UID.

[0067] When eSUPI is specified as a human user identifier, the corresponding SUCI can be formatted as NAI. This user identifier contains a UID, separated from other elements by delimiters such as exclamation marks (!), underscores (_), or other characters.

[0068] For example, if the human user identifier "Alex" is registered in a 5GS network and associated with IMSI 234150999999999 (MCC=234, MNC=15, MSISDN=0999999999), while the routing indicator (RID) is 678 and the home network public key identifier (HN Key) is 27, then the SUCI NAI format will be constructed as follows: For an empty scheme: type4.rid678.schid0.userid0999999999!Alex@5gc.mnc015.mcc234.3gppnetwork.org.

[0069] Here, type4 in the username section indicates the new eSUPI type.

[0070] For the archives Protection scheme: type4.rid678.schid1.hnkey27.ecckey!Alex<ECCephemeral public key> .cip<encryption of 0999999999> .mac<MAC tag value> @5gc.mnc015.mcc234.3gppnetwork.org.

[0071] Similarly, type4 in the username section refers to the new eSUPI type.

[0072] In these formats, "Alex" represents the UID, and the exclamation mark (!) serves as a separator. This separator integrates the human-readable identifier (UID) with the technical IMSI component within the NAI structure. Other separators may be used depending on implementation requirements.

[0073] Figure 5 An example of a registration process using an eSUPI with a UID, according to an embodiment of this application, is shown. Figure 5 As shown, in some embodiments, the UE determines the login credentials of the human user and constructs an eSUPI with a UID according to the format described in some embodiments. The UE then sends the eSUPI with the UID to the AMF in the format of a SUCI in the registration request. The UDM function parses the privacy-preserving subscription identifier (SUCI). Once the SUPI type is identified as an eSUPI with a UID, the UDM creates a user profile based on the human UID.

[0074] 5GS's standard user identifier: This embodiment describes an alternative to using an eSUPI with a UID. It proposes a method for identifying a human user of a UE's 3GPP subscription when accessing services via 5GS using a regular user identifier. This identifier can be in NAI format or even an email address.

[0075] The user identifier is independent of existing subscription-related identifiers (such as IMSI, MSISDN, IMPI, IMPU, SPI, GPSI). This user identifier should be issued by the network operator or a trusted third party.

[0076] The user identity profile associated with the UE's 5GS subscription is stored in the UDR.

[0077] The logic for processing user identity profiles can be implemented in a UDM or a dedicated IMF.

[0078] User profiles include a UID, which is unique within a specific 5G subscription.

[0079] PDU session flow can associate UID with PDU session, PCC rules and other policies.

[0080] User profile subscription data: The "Subscription Data" dataset in the UDR may contain a subset of "User Profile Subscription Data". For a specific subscription (i.e., SUPI), there may be one or more user identities in the user profile. The "User Profile Subscription Data" for each UID may include: UID, user-specific service settings and parameters, UID service category, UID-specific network resources (such as network slices) corresponding to the subscription, QoS information (such as default 5QI), additional user identifiers associated with the 5GS subscription linked and associated with the user identity, and the linked subscription (identified by SUPI) or UE (identified by UE identifier).

[0081] This data can be pre-provided by the operator and stored in the UDR. The UDM or IMF should use the user identity profile subscription data stored in the UDR to process service operations related to the user identity profile.

[0082] UIDs can also be associated with service category identifiers (such as Gold, Silver, and Premium cards), with each identifier linking operator-defined policies to the UID belonging to that category.

[0083] The UDM / IMF capable of processing user identity profiles resides in the HPLMN of the human users it serves and accesses UDR information within the same PLMN.

[0084] UDM / IMF capabilities: UDM / IMF can support at least one of the following functions: managing and storing user identity profiles for each user in a 5G system, pre-configuring user identity profiles by the operator, associating or deassociating UIDs with specific subscriptions (i.e., SUPIs) in an operator-controlled manner, and policy data.

[0085] The "Policy Data" dataset in the UDR may contain a subset of "User Identifier-Specific Control Data." This data is associated with a specific subscription (i.e., SUPI) and UID and is stored in the UDR. The PCF updates this data when a PDU session is established or modified using the Nudr service. Policy control information may include: user inactivity timer values: the threshold duration before a user is considered inactive, the maximum user data rate for uplink (UL) and downlink (DL), and / or exposure data.

[0086] The "Exposure Data" dataset in the UDR may contain a subset of "User State Data." This data is associated with a specific subscription and UID and is stored in the UDR using data keys (SUPI and / or UID). The network exposure function (NEF) can update this data, which may include: user state information, such as active, inactive, or suspended, and / or the UID associated with the subscription may be in an active, deactivated, or suspended state. If a user remains inactive on the UE for a certain duration, the device may automatically suspend the UID. The duration of inactivity is determined by the home operator's policy.

[0087] In the session management process, the SMF can store and update user state information in its local configuration according to the operator's policies. Changes in user state are transmitted to subscribed network functions via the Nsmf_EventExposure_Subscribe function. Furthermore, the AMF can maintain and update user state information in its local configuration based on reports from the UE.

[0088] Figure 6 An advanced process according to an embodiment of this disclosure is illustrated for supporting the identification of a human user's 3GPP subscription when a human user accesses a service via a network using a UID. Figure 6 As shown, in some embodiments, the UE uses its subscription to register with the network and establishes a NAS security context with the AMF. The UID associated with the subscription has been authenticated and authorized.

[0089] If the UE supports UID, then when the user is active, the UE must indicate the current UID in the N1SM container during the PDU session establishment process.

[0090] AMF should be selected from SMF.

[0091] If there is no existing association between the AMF and SMF for the PDU session ID associated with the UID sent by the UE (e.g., when the request type is "initial request"), the AMF calls Nsmf_PDUSession_CreateSMContextRequest with the PDU session ID, UID and other relevant parameters to create the SM context.

[0092] If there is an association between the AMF and SMF for the PDU session ID associated with the UID provided by the UE (for example, when the request type indicates "existing PDU session"), the AMF calls Nsmf_PDUSession_UpdateSMContextRequest with the PDU session ID, UID and other relevant parameters to update the SM context.

[0093] SMF is responsible for verifying whether the UE's request matches the user identity profile.

[0094] If the corresponding user profile subscription data is unavailable, the SMF uses Nudm_SDM_Get(SUPI, UID) or a dedicated IMF procedure to retrieve the data. The SMF can also subscribe to notifications of changes to user profile subscription data. The UDM or IMF uses Nudr_DM_Query to obtain this information from the UDR.

[0095] SMF can execute the user identifier policy association establishment process to associate the user identifier policy with PCF and obtain the default PCC rules for the PDU session associated with the UID.

[0096] If the request type is for an existing PDU session, the SMF can provide information about the policy control request triggering conditions that have been met in the user identifier policy association or modification process initiated by the SMF.

[0097] If a service category identifier is associated with a UID, then during this operation, the operator-defined policy for that service category is applied to that UID.

[0098] SMF continues to execute the PDU session establishment request process as described in Clause 4.3.2.2.2 of TS 23.502.

[0099] Figure 7 An example of a user state change according to an embodiment of this application is shown. Figure 7 This indicates that, in some embodiments, the UE detects user activity associated with the UID and identifies state changes.

[0100] The UE requests an update to the user status in the user identity profile by sending a NAS message.

[0101] In some operations, the AMF uses the UE's report and its local UE context data to determine if a UID state change has occurred. If a user state change is detected, the AMF sends an event report and timestamp to the NEF's associated notification endpoint via the Namf_EventExposure_Notify message. The NEF can then use the Nudr_DM_Create or Nudr_DM_Update service operations, depending on the situation, to store this information, including the timestamp, in the UDR.

[0102] In some operations, within the session management flow, the SMF may monitor user activity and determine if a UID state change has occurred. For example, a state change is triggered if a PDU session associated with a specific UID has not transmitted any data for a duration exceeding the user inactivity timer value specified in the user identity control data.

[0103] SMF sends a user state change event report and timestamp together with the associated notification endpoint of NEF via the Nsmf_EventExposure_Notify message. NEF can then store this information (including the timestamp) in the UDR, depending on the situation, using the Nudr_DM_Create or Nudr_DM_Update service operation.

[0104] URSP rules for user identifiers in 5GS: In some embodiments, a new traffic descriptor (called a UID descriptor) in a user route selection policy (URSP) rule can be used to enable a user identifier associated with traffic of the UE. The UID descriptor allows the UE to direct traffic associated with a specific UID to use predefined resources, such as a specific slice, PDU session, etc. For each newly detected UID, the UE evaluates URSP rules in order of rule priority to determine whether the UID matches the traffic descriptor of any URSP rule. When an URSP rule applicable to a given UID is identified, the UE selects a route selection descriptor within that URSP rule based on its priority.

[0105] When a valid routing descriptor is identified, the UE determines whether an existing PDU session exists that matches all components of the selected routing descriptor. The UE compares the components of the selected routing descriptor with the components of an existing PDU session.

[0106] The techniques disclosed herein enhance the identification of human users associated with a UE's 3GPP subscription when accessing services via a 5G network using a specific user identifier. The proposed methods and apparatus offer at least one of the following benefits and improvements: User identifier identification in 5G core network (5GC): Enables 5GC to identify and recognize user identifiers linked to traffic from UE.

[0107] User profile management: Supports identifying the components of a user profile, such as user identifiers, associated security credentials, linked devices, and user-specific QoS settings. This includes the processes of creating, retrieving, storing, and updating these profiles.

[0108] User identifier association and deassociation: Under the control of the network operator, a process is provided to associate and deassociate user identifiers with 3GPP subscriptions (i.e., link and unlink).

[0109] User-specific policies: Incorporate user-specific policies, such as QoS settings, into 5GS to facilitate differentiated and customized services for individual users.

[0110] These enhancements enable more efficient and personalized network resource management, improving service quality and user experience.

[0111] Some embodiments offer the following commercial benefits: 1. Solving problems in related technologies and other issues. 2. Providing identification of user identifiers in 5GC. 3. Supporting the identification of components in user identity profiles. 4. Providing linking and unlinking of user identifiers. 5. Providing policies for specific users. 6. Providing good communication performance. 7. Providing high reliability. Some embodiments of this application can be used in a variety of applications. Some embodiments of this application are adopted by chipset suppliers, video system development suppliers, automobile manufacturers (including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc.), drones (unmanned aerial vehicles), smartphone manufacturers, communication equipment for public safety purposes, and AR / VR / MR device manufacturers (e.g., for gaming, conferences / seminars, educational purposes). Some embodiments of this application are combinations of "technologies / processes" that can be adopted in video standards to create a final product. Some embodiments of this application propose technical mechanisms. At least one solution, method, system, and apparatus proposed in some embodiments of this application can be used in current and / or new / future communication system standards, such as UEs, base stations, and / or communication systems. Compatible products follow at least one solution, method, system, and apparatus proposed in some embodiments of this application. The proposed solutions, methods, systems, and apparatuses are widely used in UEs, base stations, and / or communication systems. With the implementation of at least one solution, method, system, and apparatus proposed in some embodiments of this application, at least one modification is considered to the feeder link switching methods and apparatuses in non-terrestrial network (NTN) communication environments to achieve standardization.

[0112] Figure 8 This is an example of a computing device 1100 according to an embodiment of this application. Any suitable computing device can be used to perform the operations described herein. For example, Figure 8 An example of a computing device 1100 is shown, which can be implemented using any appropriately configured hardware and / or software. Figures 1A to 7 Some embodiments are described herein. In some embodiments, computing device 1100 may include processor 1112, which is communicatively coupled to memory 1114 for executing computer-executable program code and / or accessing information stored in memory 1114. Processor 1112 may include a microprocessor, ASIC, state machine, or other processing device. Processor 1112 may include any of a variety of processing devices, including one. Such processors may include or be communicatable with a computer-readable medium storing instructions that, when executed by processor 1112, perform the operations described herein.

[0113] Memory 1114 may contain any suitable non-transitory computer-readable medium. Computer-readable medium may include any electronic, optical, magnetic, or other storage device capable of providing computer-readable instructions or other program code to a processor. Non-limiting examples of computer-readable media include disks, memory chips, ROM, RAM, ASICs, configuration processors, optical storage devices, magnetic tape or other magnetic storage devices, or any other medium from which a computer processor can read instructions. Instructions may include processor-specific instructions generated by a compiler and / or interpreter from code written in any suitable computer programming language, such as C, C++, C#, Visual Basic, Java, Python, Perl, JavaScript, and ActionScript.

[0114] The computing device 1100 may also include a bus 1116. The bus 1116 may communicatively couple one or more components of the computing device 1100. The computing device 1100 may also include multiple external or internal devices, such as input or output devices. For example, the computing device 1100 is shown having an input / output (I / O) interface 1118 that can receive input from one or more input devices 1120 or provide output to one or more output devices 1122. One or more input devices 1120 and one or more output devices 1122 may be communicatively coupled to the I / O interface 1118. This communicative coupling can be achieved in any suitable manner (e.g., via a printed circuit board connection, via a cable connection, via wireless communication, etc.). Non-limiting examples of input devices 1120 include touchscreens (e.g., one or more cameras for imaging a touch area, or a pressure sensor for detecting pressure changes caused by a touch), mice, keyboards, or any other device that can be used to generate input events in response to a user's physical actions on the computing device. Non-limiting examples of output device 1122 include a liquid crystal display (LCD) screen, an external monitor, a speaker, or any other device that can be used to display or otherwise present the output generated by the computing device.

[0115] The computing device 1100 can execute program code that configures the processor 1112 to perform the above-mentioned combined... Figures 1A to 7 One or more operations are described in some embodiments. The program code may reside in memory 1114 or any suitable computer-readable medium and may be executed by processor 1112 or any other suitable processor.

[0116] The computing device 1100 may also include at least one network interface device 1124. The network interface device 1124 may include any device or group of devices suitable for establishing a wired or wireless data connection to one or more data networks 1128. Non-limiting examples of the network interface device 1124 include Ethernet adapters, modems, etc. The computing device 1100 may transmit messages in the form of electronic or optical signals via the network interface device 1124.

[0117] Figure 9 This is an example block diagram of a communication system 1200 according to an embodiment of this application. The embodiments described herein can be implemented in the communication system 1200 using any appropriately configured hardware and / or software. Figure 9 A communication system 1200 is shown, which includes a radio frequency (RF) circuit 1210, a baseband circuit 1220, an application circuit 1230, a memory / storage unit 1240, a display 1250, a camera 1260, a sensor 1270, and an I / O interface 1280, which are interconnected at least as shown in the figure.

[0118] Application circuitry 1230 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. These processors may include any combination of general-purpose processors and special-purpose processors (such as graphics processors, application processors). The processor may be coupled to memory / reservoir and configured to execute instructions stored in memory / reservoir to enable various applications and / or operating systems to run on the system. Communication system 1200 can execute program code that configures application circuitry 1230 to perform the aforementioned... Figures 1A to 7 One or more operations are described in some embodiments. The program code may reside in application circuit 1230 or any suitable computer-readable medium and may be executed by application circuit 1230 or any other suitable processor.

[0119] The baseband circuit 1220 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. These processors may include baseband processors. The baseband circuitry can handle various wireless control functions that enable communication with one or more wireless networks via RF circuitry. Wireless control functions may include, but are not limited to, signal modulation, encoding, decoding, and radio frequency shifting. In some embodiments, the baseband circuitry can provide communication compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry can support communication with the evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), and wireless personal area networks (WPAN). Embodiments where the baseband circuitry is configured to support wireless communication using more than one wireless protocol may be referred to as multimode baseband circuitry.

[0120] In various embodiments, baseband circuitry 1220 may include circuitry for processing signals that are not strictly considered to be at baseband frequencies. For example, in some embodiments, baseband circuitry may include circuitry for processing signals having an intermediate frequency (between baseband and radio frequency). RF circuitry 1210 can communicate with a wireless network using modulated electromagnetic radiation via a non-solid-state medium. In various embodiments, RF circuitry may include switches, filters, amplifiers, etc., to facilitate communication with a wireless network. In various embodiments, RF circuitry 1210 may include circuitry for processing signals that are not strictly considered to be at radio frequency. For example, in some embodiments, RF circuitry may include circuitry for processing signals having an intermediate frequency (between baseband and radio frequency).

[0121] In various embodiments, the above-mentioned text is combined with Figures 1A to 7 The transmitter circuitry, control circuitry, or receiver circuitry described in some embodiments may be wholly or partially embodied in one or more of the RF circuitry, baseband circuitry, and / or application circuitry. As used herein, "circuit" may refer to, or include, a portion of, an ASIC, electronic circuitry, a processor (shared, dedicated, or grouped), and / or a memory (shared, dedicated, or grouped) executing one or more software or firmware programs, combinational logic circuitry, and / or other suitable hardware components providing the described functionality. In some embodiments, electronic device circuitry may be implemented by one or more software or firmware modules, or the functionality associated with the circuitry may be implemented by one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuitry, application circuitry, and / or memory / memory may be implemented together on a system on a chip (SOC). Memory / memory 1240 may be used to load and store data and / or instructions, for example, for a system. In one embodiment, memory / memory may include a combination of any suitable volatile memory (such as dynamic random access memory, DRAM) and / or non-volatile memory (such as flash memory).

[0122] In various embodiments, I / O interface 1280 may include one or more user interfaces designed to enable users to interact with the system, and / or peripheral component interfaces designed to enable peripheral components to interact with the system. User interfaces may include, but are not limited to, physical keyboards or keypads, touchpads, speakers, microphones, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, and power interfaces. In various embodiments, sensor 1270 may include one or more sensing devices to determine environmental conditions and / or location information relevant to the system. In some embodiments, sensors may include, but are not limited to, gyroscope sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. Positioning units may also be part of, or interact with, baseband and / or RF circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

[0123] In various embodiments, the display 1250 may include a liquid crystal display (LCD) and a touchscreen display, etc. In various embodiments, the communication system 1200 may be a mobile computing device, such as, but not limited to, a laptop, tablet, netbook, ultrabook, smartphone, AR / VR glasses, etc. In various embodiments, the system may contain more or fewer components and / or employ different architectures. Where appropriate, the methods described herein may be implemented as a computer program. This computer program may be stored on a storage medium such as a non-transitory storage medium.

[0124] Those skilled in the art will understand that each unit, algorithm, and step described and disclosed in the embodiments of this application is implemented through electronic hardware or a combination of computer software and electronic hardware. Whether a function runs in hardware or software depends on the application conditions and design requirements of the technical solution. Those skilled in the art can implement functions in different ways according to each specific application, and these implementation methods should not exceed the scope of this application. Those skilled in the art will understand that since the working processes of the above systems, devices, and units are basically the same, they can refer to the working processes of the systems, devices, and units in the above embodiments. For ease of description and simplification, these working processes will not be described in detail here.

[0125] It is understood that the systems, apparatuses, and methods disclosed in the embodiments of this application can be implemented in other ways. The above embodiments are merely examples. The division of units is based solely on logical function, and other division methods may exist during implementation. Multiple units or components may be combined or integrated into another system. Certain features may also be omitted or skipped. On the other hand, the mutual coupling, direct coupling, or communication coupling shown or discussed is indirectly or communicatively implemented through certain ports, devices, or units in an electrical, mechanical, or other form.

[0126] The units used as explanatory components may or may not be physically separated. The units used for display may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Depending on the purpose of the embodiment, some or all of the units may be used. Furthermore, each functional unit in each embodiment may be integrated into a processing unit, physically independent, or integrated into a processing unit with two or more units.

[0127] If a software functional unit is implemented, used, and sold as a product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions proposed in this application can be implemented substantially or partially in the form of a software product. Alternatively, a portion of the technical solution that is beneficial to conventional technology can be implemented in the form of a software product. Software products in a computer are stored in storage media and include multiple commands for a computing device (such as a personal computer, server, or network device) to execute all or part of the steps disclosed in the embodiments of this application. Storage media include USB flash drives, external hard drives, ROM, RAM, floppy disks, or other media capable of storing program code.

[0128] While the contents of this application are described in conjunction with embodiments considered to be most practical and preferred, it should be understood that the contents of this application are not limited to the disclosed embodiments, but are intended to cover various arrangements made without departing from the broadest interpretation of the appended claims.< / mcc> < / mnc> < / mcc> < / mnc> < / separator> < / mcc> < / mnc> < / mcc> < / mnc> < / separator>

Claims

1. A method for supporting User Identifier (UID) in a network system, the method being executed by User Equipment (UE), the method comprising: To determine human user login, construct the network UID format based on the enhanced subscription persistent identifier eSUPI with UID format and / or the network access identifier NAI format with network UID; The network UID format is sent to the first core network element via a registration request message.

2. The method according to claim 1, wherein, The network UID format includes the 5G system 5GS UID format, and the network UID includes 5GS UID.

3. The method according to claim 1, wherein, The first core network element includes Access and Mobility Management Function (AMF).

4. The method according to claim 1, further comprising: The authentication and authorization are performed using a 5G authentication scheme or a secondary authentication scheme, involving the first core network element, the unified data management UDM, the authentication server function AUSF, or the identity management function IMF.

5. The method according to claim 1, wherein, The network UID format is sent to the first core network element through the registration request message, enabling the UDM or IMF to parse the network UID from the eSUPI with the UID format or the NAI format of the network UID.

6. The method according to any one of claims 1 to 5, wherein, The eSUPI with UID format is configured to extend the current SUPI format by incorporating a UID component, and the eSUPI with UID format is defined as a new SUPI type that is different from the current SUPI type.

7. The method according to any one of claims 1 to 6, wherein, The eSUPI with UID format is formed by concatenating the current SUPI format with the network UID, and there is a separator between the current SUPI format and the network UID.

8. The method according to claim 7, wherein, The current SUPI format includes: SUPI type value 0, representing International Mobile Subscriber Identity (IMSI); SUPI type value 1, representing Network Specific Identifier (NSI); SUPI type value 2, representing Global Line Identifier (GLI); and / or SUPI type value 3, representing Global Line Identifier (GCI).

9. The method according to any one of claims 1 to 8, wherein, The SUPI type value is assigned to 4 to support the eSUPI with UID format.

10. The method according to any one of claims 1 to 9, wherein, The eSUPI with UID format is configured to contain UID information in a structured format.

11. The method according to claim 10, wherein, In the standalone non-public network (SNPN) scenario, the eSUPI with UID format follows the same pattern, and if the domain portion is available, the domain portion also includes the SNPN's network identifier (NID).

12. The method according to any one of claims 1 to 11, wherein, The NAI format of the network UID includes a non-empty string as a unique identifier, a mobile network code, and / or a mobile country code.

13. The method according to claim 12, wherein, The NAI format of the network UID still applies in the SNPN scenario, wherein, if the domain portion is available, the domain portion also includes the NID of the SNPN.

14. The method according to any one of claims 1 to 13, wherein, The network UID format is constructed by including specific tags in the domain portion.

15. The method according to any one of claims 1 to 14, wherein, The user identity profile is associated with the UE's network subscription.

16. The method according to claim 15, wherein, The logic for processing the user identity profile is executed by the Unified Data Management (UDM) function or a dedicated IMF.

17. The method according to claim 15 or 16, wherein, The Packet Data Unit (PDU) session flow is configured to associate the UID with the PDU session, policy, and charging control (PCC) rules and / or policies.

18. The method according to any one of claims 15 to 17, wherein, A subset of data marked as user profile subscription data is associated with a specific subscription identified by the subscription permanent identifier SUPI. Each user profile is associated with one or more user identities, and the user profile subscription data for each user identity includes at least one of the following information: UID; User-specific service settings and parameters; UID service categories; UID-specific network resources, subscriptions associated with the UID; Quality of Service (QoS) information, including the default 5G QoS indicator 5QI; The user's identity and the additional user identifier of the linked network subscription; or Linked subscriptions identified by SUPI or linked UEs identified by UE identifiers.

19. The method according to any one of claims 15 to 18, wherein, The UID is associated with one or more subscriber category identifiers, each subscriber category identifier is associated with an operator-defined policy, which is applied to UIDs belonging to the corresponding category.

20. The method according to any one of claims 16 to 19, wherein, The UDM or IMF includes support for processing user identity profiles by performing at least one of the following functions: Managing user identity profiles, including storing and maintaining each subscriber's user identity profile in the 5G system; User identity profiles pre-configured by the operator and related to subscriptions; or The operator is allowed to update user profile subscription data in an operator-controlled manner by associating or unassociating a UID with a specific subscription.

21. The method according to any one of claims 15 to 20, wherein, A subset of data marked as user identifier-specific control data is associated with a specific subscription identified by the subscription permanent identifier SUPI. User identifier-specific policy control information is per SUPI and / or per UID.

22. The method according to claim 21, wherein, The user identifier-specific policy control information includes at least one of the following: A user inactivity timer value indicates a threshold duration after which the user is considered inactive; or Maximum user data rate for uplink or downlink.

23. The method according to any one of claims 15 to 22, wherein, A subset of data labeled as user state data is associated with a specific subscription and UID. User state information is associated with a data key SUPI and / or a UID, which is used for one or more UIDs in a specific SUPI.

24. The method according to claim 23, wherein, The user status data is updated by NEF.

25. The method according to claim 23 or 24, wherein, The user status data includes user status information, which includes active, inactive, and / or suspended status.

26. The method according to any one of claims 23 to 25, wherein, The UID associated with a specific subscription is in a state including active, deactivated, or suspended. If a user is inactive on the device or UE for a certain period of time, the device automatically suspends the UID.

27. The method according to claim 25 or 26, wherein, In the session management process, the user status information is stored or updated locally by the SMF according to the home operator's policy.

28. The method according to claim 27, wherein, Changes in user state are sent to subscribed NFs via the Nsmf_EventExposure_Subscribe function.

29. The method according to claim 27 or 28, wherein, The user status information is maintained or updated by the AMF in the local configuration reported by the UE.

30. The method according to any one of claims 1 to 29, wherein, In the PDU session establishment process for UID, the UE registers with the network using its subscription and establishes a NAS security context with the AMF. The UID associated with the subscription has been authenticated and authorized.

31. The method according to claim 30, wherein, If the UE supports the UID, when the user is in an active state, the UE indicates the current UID in the N1 SM container during the PDU session establishment process.

32. The method according to claim 31, wherein, During the PDU session establishment process, the UE supports the first core network element or SMF to perform at least one of the following operations: The first core network element selects an SMF to manage the PDU session associated with the UID provided by the UE. If there is no association between the first core network element and the SMF for the PDU session ID associated with the UID, the first core network element uses the PDU session ID, UID and related parameters to call Nsmf_PDUSession_CreateSMContextRequest to create an SM context. If there is an association between the first core network element and the SMF for the PDU session ID associated with the UID, the first core network element calls Nsmf_PDUSession_UpdateSMContextRequest with the same parameters to update the SM context; The SMF checks whether the UE's request matches the user identity profile; If the user profile subscription data is unavailable, the SMF uses Nudm_SDM_Get or obtains the user profile subscription data through a dedicated IMF process, and subscribes to receive modification notifications through the UDM or IMF. The UDM or IMF uses Nudr_DM_Query to obtain information from the UDR. The SMF and the Policy Control Function (PCF) execute the User Identifier Policy Association Establishment Process to obtain the default PCC rules for the PDU session associated with the UID. If the request type indicates an existing PDU session, the SMF provides information about the policy control request triggering conditions, which have been met through a user identifier policy association or modification process initiated by the SMF. If a service category identifier is associated with the UID, then the policy defined by the operator for this service category is applied to the UID; or The SMF continues to execute the PDU session establishment request process.

33. The method according to any one of claims 1 to 32, wherein, In the user status update process, the UE detects user activity with a UID and identifies status changes.

34. The method according to claim 33, wherein, The UE requests an update to the user status in the user identity file by sending a NAS message.

35. The method according to claim 33 or 34, wherein, During the user status update process, the UE supports the first core network element or SMF to perform at least one of the following operations: The first core network element uses the UE's report and its local UE context data to determine the UID state change. If the user state changes, the first core network element sends an event report and a timestamp to the associated notification endpoint of the NEF via a Namf_EventExposure_Notify message, and / or the NEF uses the Nudr_DM_Create or Nudr_DM_Update service operation to store the information and the timestamp together in the UDR. In the session management process, the SMF monitors user activity and determines whether the UID state has changed; or The SMF sends a user state change event report and a timestamp to the associated notification endpoint of the NEF via the Nsmf_EventExposure_Notify message, and / or the NEF uses the Nudr_DM_Create or Nudr_DM_Update service operation to store the information and the timestamp together in the UDR.

36. The method according to any one of claims 1 to 35, wherein, The UID associated with the traffic of the UE is enabled by using a traffic descriptor and a UID descriptor in the URSP rule.

37. A method for supporting User Identifiers (UIDs) in a network system, the method being performed by the network, the method comprising: The network UID format is determined based on the enhanced subscription persistent identifier eSUPI with UID format and / or the network access identifier NAI format with network UID; The first core network element in the network receives the network UID format from the user equipment (UE) via a registration request message.

38. The method according to claim 37, wherein, The network UID format includes the 5G system 5GS UID format, and the network UID includes 5GS UID.

39. The method according to claim 37, wherein, The first core network element includes Access and Mobility Management Function (AMF).

40. The method of claim 37, further comprising: The authentication and authorization are determined using a 5G authentication scheme or a secondary authentication scheme, involving the first core network element, the unified data management UDM, the authentication server function AUSF, or the identity management function IMF.

41. The method according to claim 37, wherein, The first core network element receives the network UID format through the registration request message, enabling the UDM or IMF to parse the network UID from the eSUPI with the UID format or the NAI format of the network UID.

42. The method according to any one of claims 37 to 41, wherein, The eSUPI with UID format is configured to extend the current SUPI format by incorporating a UID component, and the eSUPI with UID format is defined as a new SUPI type that is different from the current SUPI type.

43. The method according to any one of claims 37 to 42, wherein, The eSUPI with UID format is formed by concatenating the current SUPI format with the network UID, and there is a separator between the current SUPI format and the network UID.

44. The method according to claim 43, wherein, The current SUPI format includes: SUPI type value 0, representing International Mobile Subscriber Identity (IMSI); SUPI type value 1, representing Network Specific Identifier (NSI); SUPI type value 2, representing Global Line Identifier (GLI); and / or SUPI type value 3, representing Global Line Identifier (GCI).

45. The method according to any one of claims 37 to 44, wherein, The SUPI type value is assigned to 4 to support the eSUPI with UID format.

46. ​​The method according to any one of claims 37 to 45, wherein, The eSUPI with UID format is configured to contain UID information in a structured format.

47. The method according to claim 46, wherein, In the standalone non-public network (SNPN) scenario, the eSUPI with UID format follows the same pattern, and if the domain portion is available, the domain portion also includes the SNPN's network identifier (NID).

48. The method according to any one of claims 37 to 47, wherein, The NAI format of the network UID includes a non-empty string as a unique identifier, a mobile network code, and / or a mobile country code.

49. The method according to claim 48, wherein, The NAI format of the network UID still applies in the SNPN scenario, wherein, if the domain portion is available, the domain portion also includes the NID of the SNPN.

50. The method according to any one of claims 37 to 49, wherein, The network UID format is constructed by including specific tags in the domain portion.

51. The method according to any one of claims 37 to 50, wherein, The user identity profile is associated with the UE's network subscription.

52. The method according to claim 51, wherein, The logic for processing the user identity profile is executed by the Unified Data Management (UDM) function or a dedicated IMF.

53. The method according to claim 51 or 52, wherein, The Packet Data Unit (PDU) session flow is configured to associate the UID with the PDU session, policy, and charging control (PCC) rules and / or policies.

54. The method according to any one of claims 51 to 53, wherein, A subset of data marked as user profile subscription data is associated with a specific subscription identified by the subscription permanent identifier SUPI, each user profile is associated with one or more user profiles, and the user profile subscription data for each user profile contains at least one of the following information: UID; User-specific service settings and parameters; UID service categories; UID-specific network resources, subscriptions associated with the UID; Quality of Service (QoS) information, including the default 5G QoS indicator 5QI; The user's identity and the additional user identifier of the linked network subscription; or Linked subscriptions identified by SUPI or linked UEs identified by UE identifiers.

55. The method according to any one of claims 51 to 54, wherein, The UID is associated with one or more subscriber category identifiers, each subscriber category identifier is associated with an operator-defined policy, which is applied to UIDs belonging to the corresponding category.

56. The method according to any one of claims 52 to 55, wherein, The UDM or IMF includes support for processing user identity profiles by performing at least one of the following functions: Managing user identity profiles, including storing and maintaining each subscriber's user identity profile in the 5G system; User identity profiles pre-configured by the operator and related to subscriptions; or The operator is allowed to update user profile subscription data in an operator-controlled manner by associating or unassociating a UID with a specific subscription.

57. The method according to any one of claims 51 to 56, wherein, A subset of data marked as user identifier-specific control data is associated with a specific subscription identified by the subscription permanent identifier SUPI. User identifier-specific policy control information is per SUPI and / or per UID.

58. The method according to claim 57, wherein, The user identifier-specific policy control information includes at least one of the following: A user inactivity timer value indicates a threshold duration after which the user is considered inactive; or Maximum user data rate for uplink or downlink.

59. The method according to any one of claims 51 to 58, wherein, A subset of data labeled as user state data is associated with a specific subscription and UID. User state information is associated with a data key SUPI and / or a UID, which is used for one or more UIDs in a specific SUPI.

60. The method according to claim 59, wherein, The user status data is updated by NEF.

61. The method according to claim 59 or 60, wherein, The user status data includes user status information, which includes active, inactive, and / or suspended status.

62. The method according to any one of claims 59 to 61, wherein, The UID associated with a specific subscription is in a state including active, deactivated, or suspended. If a user is inactive on the device or UE for a certain period of time, the device automatically suspends the UID.

63. The method according to claim 61 or 62, wherein, In the session management process, the user status information is stored or updated locally by the SMF according to the home operator's policy.

64. The method according to claim 63, wherein, Changes in user state are sent to subscribed NFs via the Nsmf_EventExposure_Subscribe function.

65. The method according to claim 63 or 64, wherein, The user status information is maintained or updated by the AMF in the local configuration.

66. The method according to any one of claims 37 to 65, wherein, In the PDU session establishment process for UID, the first core network element and UE determine the UE subscription and NAS security context, and the UID associated with the subscription has been authenticated and authorized.

67. The method according to claim 66, wherein, If the UE supports the UID, when the user is active in the PDU session establishment process, the first core network element determines the current UID in the N1 SM container.

68. The method according to claim 67, wherein, During the PDU session establishment process, the first core network element or SMF of the network performs at least one of the following operations: The first core network element selects an SMF to manage the PDU session associated with the UID provided by the UE. If there is no association between the first core network element and the SMF for the PDU session ID associated with the UID, the first core network element uses the PDU session ID, UID and related parameters to call Nsmf_PDUSession_CreateSMContextRequest to create an SM context. If there is an association between the first core network element and the SMF for the PDU session ID associated with the UID, the first core network element calls Nsmf_PDUSession_UpdateSMContextRequest with the same parameters to update the SM context; The SMF checks whether the UE's request matches the user identity profile; If the user profile subscription data is unavailable, the SMF uses Nudm_SDM_Get or obtains the user profile subscription data through a dedicated IMF process, and subscribes to receive modification notifications through the UDM or IMF. The UDM or IMF uses Nudr_DM_Query to obtain information from the UDR. The SMF and the Policy Control Function (PCF) execute the User Identifier Policy Association Establishment Process to obtain the default PCC rules for the PDU session associated with the UID. If the request type indicates an existing PDU session, the SMF provides information about the policy control request triggering conditions, which have been met through a user identifier policy association or modification process initiated by the SMF. If a service category identifier is associated with the UID, then the policy defined by the operator for this service category is applied to the UID; or The SMF continues to execute the PDU session establishment request process.

69. The method according to any one of claims 37 to 68, wherein, In the user status update process, the first core network element determines the user activities and status changes with a UID.

70. The method according to claim 69, wherein, The first core network element updates the user status in the user identity file.

71. The method according to claim 69 or 70, wherein, During the user state update process, the first core network element or SMF of the network performs at least one of the following operations: The first core network element uses the UE's report and its local UE context data to determine the UID state change. If the user state changes, the first core network element sends an event report and a timestamp to the associated notification endpoint of the NEF via a Namf_EventExposure_Notify message, and / or the NEF uses the Nudr_DM_Create or Nudr_DM_Update service operation to store the information and the timestamp together in the UDR. In the session management process, the SMF monitors user activity and determines whether the UID state has changed; or The SMF sends a user state change event report and a timestamp to the associated notification endpoint of the NEF via the Nsmf_EventExposure_Notify message, and / or the NEF uses the Nudr_DM_Create or Nudr_DM_Update service operation to store the information and the timestamp together in the UDR.

72. The method according to any one of claims 37 to 71, wherein, The UID associated with the traffic of the UE is enabled by using a traffic descriptor and a UID descriptor in the URSP rule.

73. A user equipment (UE), comprising: Memory; transceiver; and A processor coupled to the memory and the transceiver; The UE is configured to perform the method according to any one of claims 1 to 36.

74. A network comprising: Memory; transceiver; and A processor coupled to the memory and the transceiver; The network is configured to perform the method of any one of claims 37 to 72.

75. A non-transitory machine-readable storage medium having instructions stored thereon, wherein when a computer executes the instructions, the computer performs the method of any one of claims 1 to 72.

76. A chip, comprising: The processor is configured to invoke and run a computer program stored in memory to cause a device on which the chip is mounted to perform the method of any one of claims 1 to 72.

77. A computer-readable storage medium storing a computer program that causes a computer to perform the method of any one of claims 1 to 72.

78. A computer program product comprising a computer program that causes a computer to perform the method of any one of claims 1 to 72.

79. A computer program that causes a computer to perform the method of any one of claims 1 to 72.

80. A user equipment (UE), comprising: The determiner is configured to determine human user login by constructing the network UID format based on the enhanced subscription persistent identifier eSUPI with user identifier UID format and / or network access identifier NAI format with network UID. and The transmitter is configured to send the network UID format to the first core network element via a registration request message.

81. A network comprising: The determiner is configured to determine the network UID format based on the enhanced subscription persistent identifier eSUPI and / or the network access identifier NAI format having a user identifier UID format; and The receiver is configured to receive the network UID format from the user equipment (UE) via a registration request message.

Images