Policy creation in wireless communication networks

Abstract

Aspects of the present disclosure relate to an apparatus for wireless communication. The apparatus includes at least one memory and at least one processor coupled with the at least one memory. The at least one processor is configured to cause the apparatus to receive, from an access and mobility management function, a first request message for policy association establishment, transmit, to a network entity, a second request message to retrieve user profile information, receive, from the network entity, a first response message containing at least one of the user profile information and / or policy control subscription information, and transmit, to the access and mobility management function, a second response message comprising information based at least in part on the first response message.

Description

Technical Field

[0001] The topics disclosed in this document broadly relate to the field of policy creation in wireless communication networks. Specifically, this document defines a device, processor, and method for wireless communication. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, that support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, the wireless communication system can support wireless communication across a variety of radio access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)). Summary of the Invention

[0003] The article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, the word “or,” as used in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “one or two”) indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, without departing from the scope of this disclosure, an example step described as “based on condition A” may be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, the word “group” may comprise one or more elements.

[0004] A device for wireless communication is provided, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the device: receives a first request message for policy association establishment from an Access and Mobility Management Function (AMF); transmits a second request message for retrieving user profile information to a network entity; receives a first response message from the network entity, the first response message containing at least one of the user profile information and / or policy control subscription information; and transmits a second response message to the AMF, the second response message including information at least partially based on the first response message.

[0005] A processor for wireless communication is provided, comprising: at least one controller coupled to at least one memory and configured to: receive a first request message for policy association establishment from an Access and Mobility Management Function (AMF); transmit a second request message for retrieving user profile information to a network entity; receive a first response message from the network entity, the first response message containing at least one of the user profile information and / or policy control subscription information; and transmit a second response message to the AMF, the second response message including information at least partially based on the first response message.

[0006] A method for wireless communication is provided, the method comprising: receiving a first request message for policy association establishment from an Access and Mobility Management Function (AMF); transmitting a second request message for retrieving user profile information to a network entity; receiving a first response message from the network entity, the first response message containing at least one of the user profile information and / or policy control subscription information; and transmitting a second response message to the AMF, the second response message including information at least partially based on the first response message. Attached Figure Description

[0007] Figure 1 Examples of wireless communication systems according to aspects of this disclosure are described.

[0008] Figure 2 This describes the UE subscription data and user profile stored in the UDR (or UDM).

[0009] Figure 3 This describes information stored in a UDR (or UDM) according to aspects of this disclosure, such as user profile data and content.

[0010] Figure 4 This is a sequence diagram illustrating examples of communication and processing according to aspects of this disclosure.

[0011] Figure 5This is a sequence diagram illustrating examples of communication and processing according to aspects of this disclosure.

[0012] Figure 6 An example of device 600 according to aspects of this disclosure is described.

[0013] Figure 7 An example of processor 700 according to aspects of this disclosure is described.

[0014] Figure 8 A flowchart illustrating a method 800 performed by a device according to aspects of this disclosure. Detailed Implementation

[0015] There may be situations where it is necessary to change the UE policy based on the currently active user ID. This disclosure addresses at least the following issues:

[0016] 1. How can the UE's policy control information be modified or adjusted based on the current / active user ID? Policy control information can include AM policies, UE policies, or SM policies. In other words, AM policies and UE policies are not affected by user profiles. The policies may include the user's eligibility or authorization to use (or not use) one or more services such as V2X, A2X, ProSe, ranging, SMS, IMS, etc., and may also include the user's consent to various features.

[0017] 2. What and how user identifier profile information and functionality are made available (e.g., the content of the user identifier profile, authorization / authentication results, authenticated users, and associating user identifiers with 3GPP subscriptions).

[0018] TR 23.700-32 describes how the AMF or SMF retrieves user profile information from the UDM / UDR, and how the SM-PCF retrieves user profiles for a PDU session. However, it does not disclose how AM policies and UE policies can be affected by user profiles.

[0019] The proposed user profile may include parameters and / or policies that allow and / or restrict the service use of a user ID. This is especially applicable when the user is a human and is a single user ID at a given time.

[0020] Aspects of this disclosure are described in the context of wireless communication systems.

[0021] Figure 1This section describes an example of a wireless communication system 100 according to aspects of this disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A network. In some other embodiments, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-A network, or a 5G Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0022] One or more NEs 102 may be distributed across a geographical area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0023] NE 102 can provide a geographic coverage area within which it can support services for one or more UEs 104. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some embodiments, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas associated with the same or different radio access technologies may overlap, but different geographic coverage areas may be associated with different NEs 102.

[0024] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, and other instances thereof.

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

[0026] NE 102 may support communication with CN 106 or with another NE 102 or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some embodiments, NE 102 may communicate directly with each other. In some other embodiments, NE 102 may communicate with each other or indirectly (e.g., via CN 106). In some embodiments, one or more NE 102 may include sub-components, such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transmitting entities (which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs)).

[0027] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) that manage access and mobility, and user plane entities (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) that route packets or interconnect to external networks. In some implementations, the control plane entities may manage non-access stratum (NAS) functions of one or more UEs 104 served by one or more NEs 102 associated with CN 106, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.).

[0028] CN 106 can communicate with the packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may contain an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session (e.g., a Protocol Data Unit (PDU) session, etc.) with CN 106 via NE 102. CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. A PDU session may be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0029] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 may support different resource structures. For example, NE 102 and UE 104 may support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 may support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 may support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 may support various frame structures based on one or more parameter sets.

[0030] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. In some embodiments, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.

[0031] Time intervals for resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, for example, 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0032] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may contain a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot for the regular cyclic prefix and the extended cyclic prefix, the number of time slots per subframe, and the number of time slots per frame may depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and time slots.

[0033] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, NE 102 and UE 104 may perform wireless communication on one or more of the operating frequency bands. In some embodiments, FR1 may be used by NE 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other equipment or devices, for short-range, high data rate capabilities.

[0034] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set containing a 15 kHz subcarrier spacing (e.g., μ=0); a second parameter set containing a 30 kHz subcarrier spacing (e.g., μ=1); and a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2). FR2 may be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 may be associated with a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2); and a fourth parameter set containing a 120 kHz subcarrier spacing (e.g., μ=3).

[0035] Wireless communication systems (also known as wireless networks), such as 5G systems (5GS), provide communication services to subscribers. The communication device that implements a subscription profile is called a user equipment (UE). The UE registers with the network using a subscription identifier, and the network can assign resources corresponding to the subscribed service to the UE.

[0036] Recently, the 3rd Generation Partnership Project (3GPP) has begun working on 5G system enhancements to allow the use of user-specific identifiers, which network operators can use to provide enhanced user experiences. Furthermore, the network can adapt the communication services provided to the UE based on the user ID currently active on the UE or requesting services.

[0037] The user to be identified may be an individual human user using a UE with a specific subscription, an application running on or connected to the UE, or a device (e.g., PINE) located behind the UE as a gateway (e.g., PEGC).

[0038] One or more users (i.e., humans) may share a single UE. In this use case, a user ID identifies a human. It is assumed that a single user ID is active (or in use) at a given time.

[0039] One or more applications may be installed on the UE. In this use case, each application may have its own user ID. It is assumed that multiple applications can run simultaneously, and therefore, multiple user IDs may be active (or used) on the UE at the same time.

[0040] One or more users (i.e., remote devices) can connect to the UE, in which case the UE can act as a gateway UE. It is assumed that multiple remote devices can connect to the UE simultaneously, and therefore, multiple user IDs can be active (or used) on the UE at the same time.

[0041] Network operators may wish to leverage user-specific settings within the network to allow them to provide differentiated services and / or differentiated billing based on user IDs. Service differentiation can also mean allowing or disallowing certain services for a specific user ID.

[0042] Figure 2 This demonstrates the possible structure of data stored in a UDR 200 or UDM 200. This data may contain some or all of the following:

[0043] 1. UE subscription data / information 205, as specified in Clause 5.2.3.3 of 3GPP TS 23.502, v18.4.0, 2023-12, “Procedures for the 5G System,” has enhancements to include a list of one or more user IDs or user profile IDs associated with the UE subscription data. The UE subscription data / information may belong to the USIM or the UE.

[0044] 2. Data structures referred to as "user profiles" 215 and 220, which can be identified by a user profile ID or by a user ID. Furthermore, user profiles 215 and 220 may contain other information as security credentials / information for user ID authentication or service-specific parameters (e.g., QoS parameters) to be applied. When delivering services to a user ID, service-specific settings and parameters (e.g., user-specific QoS settings) may be applied.

[0045] Figure 2The UE subscription data 205 may include, for example, three different user IDs, referred to as user ID "A", user ID "B", and user ID "C". User ID "A" and user ID "B" may share a common user profile 215 with user profile ID 1. User ID "C" may use a separate user profile 220 with user profile ID 2. The user IDs may have unique values ​​within the home operator's network (e.g., HPLMN).

[0046] Depending on the currently active user, the following use cases may require modification of UE policies or Access and Mobility (AM) policies: Network operators may wish to change the DNN of a PDU session based on the user using the device. For example, the default DNN might be referred to as "Internet," allowing access without special control, while a DNN referred to as "Internet-Kids" might be applied when a child is using the UE to enforce specific filtering for parental controls. Existing features existing in the network, known as "DNN replacement," can be enabled with a specific user ID; and SFC in the SM-PCF can be activated for parental controls.

[0047] AM policy may refer to access and mobility-related policy information. SM policy may refer to session management policy control information. UE policy may refer to one or more of the following:

[0048] 1. Vehicle-to-Everything (V2X) Policy (V2XP): This policy provides the UE with configuration parameters for V2X communication via the PC5 reference point, the Uu reference point, or both. The V2X policy is defined in Clauses 5.1.2.1 and 5.1.3.1 of TS 23.287.

[0049] 2. Proximity Service (ProSe) Policy (ProSeP): This policy provides the UE with configuration parameters for the ProSe features as defined in Clause 5.1 of TS 23.304.

[0050] 3. Ranging / Sidelink Positioning Policy (RSLPP): This policy provides the UE with configuration parameters used for ranging / sidelink positioning control. The ranging / sidelink positioning policy is defined in Clause 5.1 of TS 23.586.

[0051] 4. Aerial-to-Everything (A2XP) Policy: This policy provides the UE with configuration parameters for A2X communication via the PC5 reference point, the Uu reference point, or both. The A2X policy is defined in clauses 6.2.1.2.1 and 6.2.1.3.1 of TS 23.256.

[0052] Figure 3 This describes how data associated with the UE and user is stored in the UDR 300 or UDM 300. The UE subscription data 305 and policy data 310 fields display UE subscription data and policy data (e.g., as currently known according to the 5GS standard). User profile fields 315 and 320 display possible user profile data. In one instance, the content of the user profile is structured similarly to the data structure in the UDR. Furthermore, the content of the user profile may contain user profile information that can be used in other embodiments. The user profile information may include the following parameters:

[0053] 1. A list of one or more device IDs (e.g., Permanent Equipment Identifiers) that are allowed to be used by a user. In other words, if the current device ID (i.e., PEI) is part of the list of allowed device IDs, then the user profile can be used / applied.

[0054] 2. An indication of whether a user profile is for a human user, a remote device connecting to the UE, or an application installed on the UE. This indication may be used in the consumer NF (e.g., UDR, UDM, AMF, SMF, or PCF) to determine whether any restrictions on the use of user profiles can be applied. For example, if the user ID identifies a human, then a single user profile is allowed to be active. If the user ID identifies a remote device, then multiple profiles may be considered at once, for example, for different PDU sessions.

[0055] 3. A list of one or more services for which a user ID is restricted. This list may be represented as follows: Figure 4 The service restriction parameters used in the description. Alternatively or additionally, the list may indicate one or more services that are allowed (enabled or authorized) for a user ID. The advantage of introducing a service list is that the user profile can disallow (disable or unauthorize) services subscribed to by the UE; and conversely, the user profile can allow (or enable) services that the UE has not subscribed to. For example, UE subscription data may contain information about subscribed services SMS, ProSe, and V2X; however, a particular (e.g., human) user of this UE may not be allowed to use ProSe and V2X services, but may be allowed to use SMS services. The following service list shows which services can be included in the user profile (as services allowed or disallowed for a user ID):

[0056] 1) Enable / disable LCS privacy or LCS mobile initiation. For example, a location privacy indicator (LPI) from a user profile may have a higher priority than an LPI stored in the UE subscription data.

[0057] 2) V2X service.

[0058] 3) ProSe service.

[0059] 4) MBS service.

[0060] 5) A2X service.

[0061] 6) Ranging / sidelink positioning service.

[0062] 4. User consent, such as for UE data collection and analysis, sensing operations, or other consents. For example, user ID "A" may have consented to a specific function / service in the network, while user ID "B" has not yet consented to the same function / service. UE subscription data can store user consent for functions / services, and if the user profile information of the currently active user ID also contains user consent for the same function / service, then user consent requested from the user profile information will have higher priority. In other words, user consent from user profile information will be considered as being used in the consumer NF (e.g., AMF or UDM). In one instance, the UDM may obtain information from the user profile and indicate user consent from the user profile to the NF consumer (e.g., AMF, NWDAF), rather than user consent from the UE subscription data.

[0063] 5. Various types of user policy data, which can be structured as user context policy control subscription information, PDU session policy control subscription information, access and mobility policy control subscription information, or usage subscription information (e.g., the description of policy control subscription information in Clause 6.2.1.3 of 3GPP TR 23.503, v18.4.0, 2023-12, "Policy and charging control framework for the 5G System (5GS)"). In other words, policy data in user profile information may contain the same or similar structure or parameters (i.e., information name) as the policy control subscription information stored in the UDR, which will allow for easier merging of: a) traditional policy control subscription information (e.g., from...). Figure 2 (a) UE subscription data frame; and (b) policy-related data that forms the user profile information of the active user ID.

[0064] 6. SM-related data (e.g., PDU session policy control subscription information) may contain a list of authorized service function chains (SFCs), where each SFC is identified based on a service function chain identifier (SFC ID).

[0065] 7. CHF address or billing policy specific to a specific user ID. Specifically, the AM policy section, SM policy section, or user section of the user profile information may contain CHF addresses, including a primary CHF address and a secondary CHF address, which are specific to the user ID.

[0066] Data stored in user profile information can be structured in the following way:

[0067] 1. AM-related data,

[0068] 2. SM-related data,

[0069] 3. Policy-related data. This data may have the same or similar structure as the policy data stored in the UDR for subscribers. For example, it may contain a list of one or more services restricted for a user ID; or its structure may contain UE context policy control subscription information, PDU session policy control subscription information, access and mobility policy control subscription information, or usage subscription information, as described above. Policy-related data may also contain billing information per user ID.

[0070] 4. Application-Related Data. Application-related data may include Packet Flow Descriptions (PFDs) used for application detection. a) General application-related data stored in the UDR and b) the application-related data portion of the user profile information may involve the same application descriptor (or filter). In this case, during policy rule creation in the PCF, the application-related data portion of the user profile information may take precedence over the general application-related data in the PCF.

[0071] 5. Structured data for disclosure. This data may have the same or similar structure as the structured data for disclosure stored in the UDR for subscribers. Structured data for disclosure stored in the user profile will only be disclosed to the AF for disclosure requests or subscriptions specific to the user ID. This provides a solution to the problem of the content and manner in which user identification profile information and functionality are disclosed.

[0072] Any combination of data types is possible; for example, AM-related data can be combined with SM-related data types. This structuring will make it easier to process user profile data when it is exposed to consumer NFs, which receive and process the user profiles. In one instance, the UDM processes the user profile data; that is, the UDM receives UE subscription data corresponding to the active user ID and the user profile, and the UDM determines which subscription information is sent to consumer NFs such as AMF, SMF, PCF, etc.

[0073] In one instance, user profiles are stored in the UDR. When the UDM requests a user profile, for example, associated with a user ID, the UDR can send AM and / or SM-related data to the UDM. When the PCF requests a user profile, the UDR can send policy-related or application-related data to the PCF (depending on the PCF's request or the type of PCF request).

[0074] In one instance, even if at least one user ID exists associated with the UE subscription data (e.g., at least one user ID and user profile are stored in the UDR / UDM), the UE may not provide the user ID. If the UE does not provide the user ID to the network, the UE subscription data can be applied without considering any user profile. In other words, the UDM can only receive and consider the UE subscription data when creating subscription data to be sent to the consumer NF (e.g., AMF or SMF). If the UE provides the user ID to the network, the network (e.g., the UDM) can consider the corresponding user profile.

[0075] It is possible to deploy, store, and process one or more specific UDRs or UDMs for user profiles. When processing a specific UDR or UDM for a user profile, different examples of a specific UDR or UDM can be distinguished by the domain portion or routing ID portion of the user ID. In other words, the user ID may contain information (e.g., a routing ID) that instructs the consumer NF how to discover the specific UDM or UDR processing the user profile associated with that user ID. It can be assumed that the user ID has a NAI format, for example, ID#A.routingID@domain.com, where ID#A is the user's personal identifier, and the routing ID indicates a specific UDM or UDM network function example. The characteristics of an instance are described below:

[0076] 1) A method in which the PCF retrieves policy-related data from a user profile and determines the UE's policy (e.g., AM policy, UE policy, or SM policy) using both general / UE subscription data and user profile data:

[0077] a. The PCF receives the user profile ID or user ID from the policy consumer NF (e.g., AMF or SMF). The PCD retrieves the user profile from the UDR. The PCF determines the AM / SM / user policy based on subscription data and the user profile.

[0078] b. For date processing in PCF, when merging corresponding parameters, user profile data may have a higher priority than general / UE subscription data stored in UDR.

[0079] c. When a user ID (or user profile ID) changes, the PCF may subscribe to notifications from one of the AMF, UDM, or UDR. When a new user ID is notified to the PCF, the PCF attempts to download policy control information from the user profile corresponding to the new user ID.

[0080] 2) User profile data can be stored in a structured manner in a UDR (or UDM), allowing specific portions of the user profile (user profile data only related to the consumer NF) to be sent to the NF consumer. For example, AM-related data or SM-related data can be sent to the UDM, but policy-related data can be sent to the PCF.

[0081] 3) The UDM is enhanced to process UE subscription data and user profile data / information. That is, the UDM can create AM subscription data to be sent to the AMF or SM subscription data to be sent to the SMF, wherein the UDM merges the corresponding parts of the UE subscription data and the user profile data.

[0082] a. In other words, the user profile information is not sent to the AMF or SMF, but instead the UDM processes both i) UE subscription data and ii) user profile information; and the UDM merges overlapping parameters to create (AM / SM) subscription information that will be sent to the AMF and / or SMF.

[0083] 4) The UDR is enhanced to create access and mobility policy control subscription information, PDU session policy control subscription information, or UE context policy control subscription information, which can be a merging of UE subscription information and user profile information.

[0084] Figure 4 The diagram illustrates a signaling flow 400 used to configure UE policies or AM policies for UE 410. The diagram shows that user 405 (which can be a human user, application, or removal device) can be implemented as an upper layer of UE 410. The user (or upper layer) indicates the current user ID to UE 410, enabling the NAS layer of UE 410 to use the user ID.

[0085] Figure 4 The detailed description is as follows:

[0086] 470a. UDR 435 may store one or more user profiles, each of which is associated with one or more user IDs (e.g., for user "A", user "B").

[0087] 470b. Assume that an upper layer in the UE indicates a user ID to the UE. As described in other embodiments, a single user ID is used at a given time when the user is human. The user (or upper layer) indicates the current user ID to the UE so that the UE's NAS layer can use the user ID. User ID verification is performed in the network. The network (e.g., UDM 430 or AMF 420) may store the state of "active" user IDs. If the state is active, then the network applies user profile information corresponding to the user ID.

[0088] 471. During the registration procedure or the identification request / response procedure, the UE will transmit the user ID as notified by the upper layer to the AMF 420. Additionally, the UE may transmit its PEI to the AMF 420.

[0089] 472. If not previously executed, AMF 420 may register itself as a service AMF 420 for the UE. AMF420 can use the NUDM_UECM_Registration service operation.

[0090] 473. AMF 420 can retrieve UE subscription data. In addition to SUPI, AMF 420 also includes PEI and user ID in the subscription retrieval request message. AMF 420 can use the NUDM_SDM_Get service operation to retrieve UE subscription information and / or user profile information. AMF 420 can select a UDM 430 capable of processing (i.e., including retrieving, storing, and managing) user profile information. When using NRF services for UDM 430 discovery and selection, AMF 420 can include new parameters in the UDM 430 selection request message sent to NRF, indicating that the UDM 430 should be able to perform user profile processing (or user ID processing). Alternatively, if multiple UDM 430 examples exist that have been discovered by AMF 420 (or locally configured in AMF 420), the UDM 430 selection functionality in AMF 420 can allow the UE to select a UDM 430 example capable of processing user profile information.

[0091] 474a. UDM 430 retrieves subscription data and user profiles from UDR 435. UDM 430 can operate using the NUDR_DM_Query service, and in addition to SUPI, UDM 430 may also contain user IDs. The user IDs indicate to UDR 435 that the corresponding user profile is to be broadcast to UDM 430.

[0092] 474b. UDR 435 sends a response message to UDM 430, the response message containing both: UE subscription information and user profile information. The user profile information corresponds to the user ID received in step 474a. For example, the user profile information may contain, for example,... Figure 2 The data described herein. User profile information may contain one or more of the following parameters or datasets corresponding to UE subscription data sent to AMF 420:

[0093] Parameters affecting the exported AM subscription information include: subscribed UE-AMBR (aggregated maximum bit rate), subscribed UE-slice-MBR (maximum bit rate) list, subscribed S-NSSAI list, service area restrictions, and subscribed DNN list.

[0094] Slice selection of subscription data or SMF selection of subscription data (SMF selects the required data), user consent data, service-related data: SMS management subscription data, V2X (vehicle-to-everything) subscription data, A2X (air-to-everything) subscription data, ProSe subscription data, MBS subscription data. It should be understood that the terms "data" and "dataset" can refer to multiple information elements and / or parameters.

[0095] 475a. After successful user ID verification, UDM 430 determines the UE subscription data to be sent to AMF 420 (e.g., exported subscription data sent to AMF 420). Some parameters or data (subsets) from the UE subscription data and from user profile information may overlap. In one instance, the user profile may indicate a single allowed S-NSSAI for the user ID, while the UE subscription data may contain two subscribed S-NSSAIs. In another instance, the UE-AMBR from the UE subscription data may have a value X, while the UE-AMBR from the user profile may have a value Y, where X may be greater than Y. In such instances, UDM 430 may combine overlapping parameters (or data subsets), and UDM 430 may include or combine values ​​from user profile information (i.e., restriction parameters) in the exported subscription data sent to AMF 420. Generally, UDM 430 will process parameters from the user profile with higher priority than corresponding parameters from the UE subscription data.

[0096] In an example, if the UE subscription data contains a UE-AMBR parameter value of 150 Mbit / s and the user profile indicates a UE-AMBR parameter value of 64 Mbit / s, then the UDM 430 may decide to use the UE-AMBR parameter value of 64 Mbit / s from the user profile (and send it to the AMF 420).

[0097] Alternatively, the UDM 430 may determine (or may be configured by a management system, such as an OAM system) to provide different sets of information to the AMF 420. In one example, one set of information may include UE subscription data, and another set may include the AM portion of the user profile (e.g., a portion of the user profile that may influence decisions at the AMF 420 when determining the AM configuration of a UE transmitted to the UE via the NAS protocol). In this example, the AMF 420 may receive both the UE subscription data and the portion of the user profile data corresponding to the UE subscription data separately.

[0098] 475b. UDM 430 sends an SDM notification message to AMF 420 in response to step 473. The notification message may contain at least one of the following: exported subscription data sent to AMF 420 (as determined in step 475a), the status of the user profile ID, or a user ID verification indication. The exported subscription data sent to AMF 420 may contain AM subscription information modified by taking into account user profile information (e.g., subscribed S-NSSAI, UE-AMBR, UE-slice-MBR, etc.), and service subscriptions (e.g., SMS, V2X, ProSe, etc.). In the case of an 'active' user ID, UDM 430 may send the user profile ID to AMF 420. AMF 420 may use this indication in other signaling to other NFs in the core network to indicate that the user profile applies to this UE. The status of the user ID verification parameter indicates whether the user ID has been successfully verified in the network. For example, when verification is successful, the status can be 'Active' (or 'Verified'), and when verification fails, the status can be 'Inactive' (or 'Failed').

[0099] In embodiments where UDM 430 provides user profile data and UE subscription data to AMF 420 separately (i.e., in different groups of information), AMF 420 can receive and store the two groups of information. AMF 420 can merge overlapping parameters from the user profile data and UE subscription data. Compared to corresponding parameters from the UE subscription data, AMF 420 can process parameters from the user profile data with higher priority. AMF 420 can create a UE context that stores the merged user profile data and UE subscription data.

[0100] 476. AMF 420 determines the possible registration areas to be applied to the UE and the corresponding allowed NSSAI (and configured NSSA, if necessary). These parameters for UE registration are derived based on the exported subscription data received in step 475a and sent to AMF 420.

[0101] 477. AMF 420 and PCF 440 (e.g., AM-PCF or PCF for UE) perform AM policy association establishment / modification procedures. AMF 420 may use the NPCF_AMPolicyControl service operation and may include at least one of the following in the request message: SUPI, service restriction parameters, user profile ID, and / or user ID. The service restriction parameters may indicate to PCF 440 that some services that can be subscribed to by UE 410, such as those in the subscription policy (e.g., access and mobility policy control subscription information) stored in UDR 435, may be additionally restricted by the received service restriction parameters.

[0102] In this example, UE subscription data may indicate ProSe subscription and / or IMS / SMS subscription parameters; however, the user profile may indicate that ProSe and IMS / SMS services are not allowed for a specific user ID. In this case, the service restriction parameters may be constraints or restrictions on the use of ProSe and IMS / SMS services derived from the user profile.

[0103] Receiving a user profile ID or user ID parameter in PCF 440 will trigger PCF 440 to retrieve the user profile from UDR 435.

[0104] 478a. PCF 440 sends a request message to UDR 435 to retrieve user profile information. PCF 440 may use the service operation NUDR_DM_Query, and in addition to the request indication for access and mobility policy control subscription information, it includes a user profile ID or user ID parameter. The user profile ID or user ID parameter indicates to UDR 435 that it also needs to consider any stored user profile information identified by the user profile ID or user ID, more specifically, the AM policy portion of the user profile information. In an example, PCF 440 may send separate request messages to UDR 435, such as a request message to retrieve access and mobility policy control subscription information (containing SUPI) and another request message to retrieve the AM policy portion of the user profile information (containing user ID (or user profile ID)).

[0105] 478b. UDR 435 sends a response message to PCF 440, the response message containing at least one of the following: an AM policy portion of Access and Mobility Policy Control Subscription Information and User Profile Information. The AM policy portion of the User Profile Information may contain an indication that policy decisions depend on the status of policy counters maintained at CHF 445 (and optionally a list of policy counter identifiers). The AM policy portion of the User Profile Information may also contain the address of CHF 445, including a primary CHF 445 address and a secondary CHF 445 address, which are specific to the user ID.

[0106] 479a. PCF 440 (e.g., AM-PCF or PCF for UE) determines AM policy control information based on the AM policy portion of the received access and mobility policy control subscription information and user profile information. PCF 440 may combine corresponding overlapping parameters (if present) from the AM policy portions of the access and mobility policy control subscription information and user profile information. Parameters from the AM policy portion of the user profile information may have a higher priority than corresponding parameters from the access and mobility policy control subscription information. Furthermore, if subscription parameters are received in step 477, PCF 440 may also consider the subscription parameters. Therefore, PCF 440 creates derived AM-related policy information. The created AM-related policy control information is customized for the currently active user ID (i.e., affected). The AM-related policy control information may include at least one of the following: service area restrictions, so-called SMF selection management related policy information (e.g., for controlling DNN replacement), UE-AMBR, UE-slice-MBR, selected RFSP index (“RAT / Frequency Selection Priority”), management of 5G access layer time distribution, etc. Furthermore, CHF 445 can store a separate policy counter for each user ID to maintain separate spending limits for each user ID. In this case, PCF 440 can initiate an initial spending limit report retrieval to CHF 445, including the user ID as an additional parameter (i.e., in addition to the subscriber identifier (e.g., SUPI)). If a policy counter status report has been established for the subscriber, PCF 440 can determine the status of additional policy counters required due to a change in the active user ID or the creation of a new active user ID. PCF 440 can send an NCHF_SpendingLimitControl_Subscribe request to CHF 445, including the user ID as an additional parameter. Alternatively or additionally, PCF 440 can initiate an intermediate spending limit report retrieval procedure when a new active user ID is notified to PCF 440.

[0107] 479b. PCF 440 sends an AM policy association establishment response / update message to AMF 420. PCF 440 may contain at least one of the following parameters: SUPI, exported AM-related policy information. The exported AM-related policy information may include policies for DNN replacement, ProSe / V2X / A2X services, allowed SMS, allowed IMS, and updated RFSP. SMF selection management related policy control requirements. The policy framework can provide the following functionality for SMF selection management of PDU sessions:

[0108] 1. PCF 440 can provide SMF selection management related policies to AMF 420;

[0109] 2. The PCF 440 can provide the strategy to the AMF 420 to contact the PCF 440 to perform DNN replacement for a specific DNN;

[0110] 3. PCF 440 may provide policies to AMF 420 to contact PCF 440 to perform DNN replacement for unsupported DNNs. When a user ID (or user profile ID) changes, PCF 440 may subscribe to notifications from one of AMF 420, UDM 430, or UDR 435. When a new user ID is notified to PCF 440, PCF 440 attempts to retrieve policy control information from the user profile corresponding to the new user ID. Retrieving policy control information from the user profile is as described in steps 478a and 478b. Alternatively, when AMF 420 determines that the active user ID (or user profile ID) has changed, AMF 420 may be configured to trigger an AM policy association modification procedure with PCF 440 for established AM policy associations. AMF 420 includes the new user profile ID and / or user ID in the AM policy association modification request message.

[0111] 4710. AMF 420 can discover and select CHF 445 for online or offline billing of 5G connectivity and mobility, managing subscribers and / or active user IDs. In one instance, the CHF 445 address can be sent from PCF 440 to AMF 420 in step 479b. AMF 420 initiates association establishment with CHF 445 for 5G connectivity and mobility domain billing. AMF 420 notifies CHF 445 of the active user ID. AMF 420 is able to collect billing information for each UE and each active user ID, such as for 5GS registration, for N2 connectivity between 5G-AN and AMF 420, for CAG identifiers, for network identifiers, etc.

[0112] 4711. AMF 420 sends a registration acceptance message to UE 410. The registration acceptance message may contain information about the applied policy restrictions based on the active user ID.

[0113] 4712. AMF 420 may send a request message to PCF 450 (e.g., UE-PCF) to establish a UE policy association. Note that this PCF 450 may be the same as the PCF 440 included in steps 477 through 479, but it may also be a separate PCF 450 entity (e.g., UE-PCF). AMF 420 may use the service operation NPCF_UEPolicyControl_Create, and AMF 420 may include at least one of the following: service restriction parameter subscription information (e.g., as received in step 475b), user ID, and / or user profile ID. Furthermore, once the user ID is active (i.e., used by network authentication or authorization), AMF 420 may include the user ID in signaling to other NFs in the core network, for example, during the initiation of various procedures for the UE, in signaling to the Location Management Function (LMF), PCF, SMF, SMSF, or other NFs.

[0114] 4713. PCF 450 (e.g., UE-PCF or PCF for UE) may retrieve UE-related policies from UDR 435 in a manner substantially similar to that in steps 478a and 478b. PCF 450 may use the service operation NUDR_DM_Query and include a user profile ID or user ID parameter in addition to a request indication for UE context policy control subscription information. In one embodiment, PCF 450 may send separate request messages to UDR 435, for example, a request message for retrieving UE policy control subscription information (containing SUPI) and another request message for retrieving user context policy control subscription information (containing user ID (or user profile ID)). UDR 435 sends a response message to PCF 450, the response message containing at least one of the following: the user policy portion of the UE context policy control subscription information and the user profile information.

[0115] 4714. PCF 450 (e.g., UE-PCF or PCF for a UE) may require the creation of UE policies, for example, by merging UE context policies. This involves creating specific UE policy information, which may include at least one of the following policies: V2X policy information, ProSe policy information, ranging / sidelink positioning policy information, and A2X policy information. These service policies are influenced by user profile data, such as... Figure 3As described in the description. The PCF 450 can trigger a UE configuration update procedure to send UE policies to the UE via the AMF420. This procedure is initiated when the PCF 450 wants to update the UE policy information (i.e., UE policy) in the UE configuration.

[0116] Figure 4 The solution described herein can be applied to public networks, i.e., PLMNs, or to private networks. Private networks can be PNI-NPNs or standalone NPNs (SNPNs).

[0117] The above text is about Figure 4 In the described embodiments, the user profile is structured in a manner that allows different NFs (e.g., UDM, AMF, and one or more PCFs) to retrieve and process relevant portions of the user profile information. Based on the user profile information, the UDM is able to derive subscription information, the AMF is able to derive AM restrictions, and the PCF is able to derive policy information.

[0118] Figure 5 The diagram illustrates signaling flow 500 for determining PDU session policies and configurations (specifically, SFC configurations stored in the user profile information). The diagram shows that user 505 (which can be a human user, an application, or a removal device) can be implemented as an upper layer of UE 510. Reference Figure 5 :

[0119] 570 to 571. These steps are similar to... Figure 4 The steps in the process involve the UE 510 registering with the network and receiving corresponding policies that can be exported based on the user profile.

[0120] 572. UE 510 initiates a PDU session establishment procedure. UE 510 may send a NAS transport message containing S-NSSAI, DNN, PDU session ID, and N1 container (which may contain a PDU session establishment request message).

[0121] 573. AMF 520 selects SMF 520 and initiates a session creation procedure for SMF 520. AMF 520 can use the NSMF_SM creation operation which includes at least one of the following parameters: SUPI, user ID, or user profile ID.

[0122] 574a. SMF 520 retrieves SM subscription data from UDM 530 using the Nudm_SDM_Get service operation. SMF 520 may contain at least one of the following: SUPI, PEI, or user profile ID parameter.

[0123] 574b. If UDM 530 does not yet have SM subscription data, then UDM 530 may retrieve the SM subscription data from UDR. UDM 530 may use the Nudr_DM_Query service operation, and may include at least one of the following parameters: SUPI, User ID.

[0124] 574c. UDR 535 sends a response message that may contain UE SM subscription data and user profile.

[0125] 574d. UDM 530 can apply the merging of UE SM subscription data and user profiles, similar to... Figure 3 The step 5a described in the section on merging AM subscription information differs from UDM 530 in that it merges SM-related parameters.

[0126] Alternatively, UDM 530 may determine (or may be configured to) provide different sets of information to SMF 520. For example, one set of information includes SM subscription data (e.g., as known from the present art), and another set of information includes the SM portion of the user profile (e.g., the portion of the user profile that may influence decisions at SMF 520 when determining the UE's PDU session configuration).

[0127] UDM 530 sends a response message to SMF 520. For example, in an alternative embodiment, UDM 530 may use the SDM notification service to operate and include (1) the created (merged) SM subscription data or (2) a first set and a second set of data.

[0128] 575. SMF 520 initiates the establishment of an SM policy association with PCF 540 (e.g., SM-PCF or PCF 540 for PDU sessions). SMF 520 may contain relevant UE subscription parameters and user profile ID (or user ID).

[0129] 576a. PCF 540 retrieves PDU session policy control subscription information from the UDR. PCF 540 can use the Nudr_DM_Query service operation and may include at least one of the following parameters: SUPI, S-NSSAI, DNN, and user profile ID (or user ID).

[0130] 576b. If UDR 535 stores a user profile corresponding to a user profile ID (or user ID), then UDR 535 can check whether information related to PDU session policy control subscription information and associated with S-NSSAI and DNN exists. Please refer to [reference needed]. Figure 2 This allows the use of policy-related data or SM-related data stored in the UDR 535.

[0131] UDR 535 sends a response message to PCF 540, the response message containing (1) SM policy data from a user profile associated with a user ID and (2) PDU session policy control subscription information associated with SUPI. The SM policy data from the user profile may contain one or more Service Function Chain (SFC) IDs. For example, an SFC ID may indicate a specific route for user plane data in the N6 reference interface, which may involve a firewall or similar packet inspection entity to ensure, for example, parental control processing of user plane data.

[0132] 577a. If PCF 540 receives both (1) SM policy data from the user profile and (2) PDU session policy control subscription information, then PCF 540 may apply the merging of the two datasets. The merging process may be similar to... Figure 3 The process described in step 5a for merging AM subscription information. For example, PCF 540 may apply higher priority to parameters received from the user profile compared to corresponding parameters from the PDU session policy control subscription information. If some parameters from the user profile are not present in the PDU session policy control subscription information, then PCF 540 may add those parameters to the SM policy to be sent to SMF 520.

[0133] The PCF 540 determines the SM policy to be sent to the SMF 520. For example, the SM policy may contain one or more SFC IDs based on user profile parameters.

[0134] In an alternative embodiment, PCF 540 may determine (or may be configured by a management system, such as an OAM system) to provide different sets of SM policy information to SMF 520. For example, one set of SM policy information is based on PDU session policy control subscription information (e.g., as known from the prior art), and another set of SM policy information includes the PDU policy portion of the user profile (e.g., the portion of the user profile related to S-NSSAI and DNN information to influence PDU session establishment).

[0135] 577b. PCF 540, for example, sends the determined SM policy to SMF 520 by establishing a response / update message using the SM policy. The message may contain at least one of the following parameters: SUPI, the SM policy as derived in step 7a (e.g., containing the SFC ID).

[0136] 578. SMF 520 uses the SM subscription data from step 4d and the SM policy received in step 7b to continue the PDU session establishment. SMF 520 selects and configures one or more UPFs.

[0137] The SMF 520 transmits the N2 SM container to the (R) AN 515 node and the N1 SM container to the UE. The AMF 520 encapsulates the N1 SM container in a NAS downlink transport message and sends it to the UE.

[0138] Figure 6 Example of device 600 according to aspects of this disclosure is described. Device 600 may include processor 602, memory 604, controller 606, and transceiver 608. Processor 602, memory 604, controller 606, or transceiver 608, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively ground, communicative ground, functional ground, electronic ground, electrical ground).

[0139] Processor 602, memory 604, controller 606, or transceiver 608, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may be a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured to or otherwise support components for performing the functions described in this disclosure.

[0140] Processor 602 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 602 may be configured to operate memory 604. In some other embodiments, memory 604 may be integrated into processor 602. Processor 602 may be configured to execute computer-readable instructions stored in memory 604 to cause device 600 to perform various functions of this disclosure.

[0141] Memory 604 may comprise volatile or non-volatile memory. Memory 604 may store computer-readable, computer-executable code containing instructions that, when executed by processor 602, cause device 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 604 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0142] In some implementations, processor 602 and memory 604 coupled to processor 602 may be configured to cause device 600 to perform one or more of the functions described herein (e.g., processor 602 executing instructions stored in memory 604). For example, processor 602 may support wireless communication at device 600 according to examples disclosed herein. Device 600 may be configured to support components for: receiving a first request message from an Access and Mobility Management Function (AMF) for policy association establishment; transmitting a second request message to a network entity for retrieving user profile information; receiving a first response message from the network entity, the first response message containing at least one of user profile information and / or policy control subscription information; and transmitting a second response message to the AMF, the second response message including information at least partially based on the first response message.

[0143] Controller 606 manages the input and output signals of device 600. Controller 606 can also manage peripheral devices not integrated into device 600. In some embodiments, controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 606 may be implemented as part of processor 602.

[0144] In some embodiments, device 600 may include at least one transceiver 608. In other embodiments, device 600 may have more than one transceiver 608. Transceiver 608 may represent a wireless transceiver. Transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

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

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

[0147] Figure 7 An example of a processor 700 according to aspects of this disclosure is described. Processor 700 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 700 may include a controller 702 configured to perform various operations according to the examples described herein. Processor 700 may optionally include at least one memory 704, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 700 may optionally include one or more arithmetic logic units (ALUs) 706. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0148] Processor 700 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, transmit, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to the processor chipset (e.g., processor 700) or contained within the processor chipset (e.g., processor 700)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), and others).

[0149] Controller 702 can be configured to manage and coordinate various operations of processor 700 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 700 to support various operations according to the examples described herein. For example, controller 702 can operate as a control unit of processor 700, generating control signals that manage the operation of various components of processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0150] Controller 702 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 704 and determine subsequent instructions to be executed to enable processor 700 to support various operations according to the examples described herein. Controller 702 may be configured to track the memory addresses of instructions associated with memory 704. Controller 702 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 702 may be configured to interpret instructions and determine control signals to be output to other components of processor 700 to enable processor 700 to support various operations according to the examples described herein. Additionally or alternatively, controller 702 may be configured to manage data flow within processor 700. Controller 702 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 700.

[0151] Memory 704 may include one or more caches (e.g., memory local to processor 700 or included in processor 700) or other memories, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some embodiments, memory 704 may reside within or on the processor chipset (e.g., local to processor 700). In some other embodiments, memory 704 may reside outside the processor chipset (e.g., remote from processor 700).

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

[0153] One or more ALU 706s may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALU 706s may reside within or on a processor chipset (e.g., processor 700). In some other embodiments, one or more ALU 706s may reside outside the processor chipset (e.g., processor 700). One or more ALU 706s may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 706s may receive input operands and an opcode that determines the operation to be performed. One or more ALU 706s may be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 706s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 706s to handle conditional operations, comparisons, and bitwise operations.

[0154] Processor 700 may support wireless communications according to examples disclosed herein. Processor 700 may be configured or operable to support components for: receiving a first request message for policy association establishment from an Access and Mobility Management Function (AMF); transmitting a second request message for retrieving user profile information to a network entity; receiving a first response message from the network entity, the first response message containing at least one of user profile information and / or policy control subscription information; and transmitting a second response message to the AMF, the second response message including information at least partially based on the first response message.

[0155] Figure 8A flowchart illustrating method 800 according to an aspect of this disclosure is provided. The operation of the method may be implemented by a device (e.g., a network entity or network node) as described herein. In some embodiments, the device may execute a set of instructions to control functional elements of the device to perform the described functions.

[0156] In step 802, method 800 may include receiving a first request message from the Access and Mobility Management Function (AMF) for policy association establishment. The operation of 802 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 802 may be as described in references... Figure 6 The device described is used to perform this action.

[0157] In step 804, method 800 may include sending a second request message to a network entity to retrieve user profile information. The operation of 804 may be performed according to examples as described herein. In some implementations, aspects of the operation of 804 may be as described in references... Figure 6 The device described is used to perform this action.

[0158] In 806, method 800 may include receiving a first response message from a network entity, the first response message containing at least one of user profile information and / or policy control subscription information. Operation of 806 may be performed according to the examples described herein. In some embodiments, aspects of operation of 806 may be as described in references... Figure 6 The device described is used to perform this action.

[0159] At 808, the method may include transmitting a second response message to the AMF, the second response message including information at least partially based on the first response message. Operation of 808 may be performed according to examples as described herein. In some embodiments, aspects of operation of 808 may be as referenced... Figure 6 The device described is used to perform this action.

[0160] It should be noted that the method 800 described herein describes possible implementations, and the operation and steps may be rearranged or otherwise modified, and other implementations are possible.

[0161] The disclosure herein provides an apparatus for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the apparatus: receives a first request message from an Access and Mobility Management Function (AMF) for policy association establishment; transmits a second request message for retrieving user profile information to a network entity; receives a first response message from the network entity, the first response message containing at least one of user profile information and / or policy control subscription information; and transmits a second response message to the AMF, the second response message including information at least partially based on the first response message.

[0162] At least one processor may be configured to enable the device to derive information from at least the first response message.

[0163] The first request message may include a user profile identifier, a user identifier, and / or at least one of one or more service restriction parameters.

[0164] The second request message may include at least one of a subscription identifier, a user profile identifier, and / or a user identifier.

[0165] The subscription identifier may include the subscription permanence identifier SUPI.

[0166] The device may include a PCF.

[0167] The exported information may include exported access and mobility AM policies.

[0168] At least one processor may be configured to enable the device to derive the derived AM policy based on AM policy-related information and UE policy-related information received in the first response message.

[0169] Policy control subscription information may include at least one of AM policy control subscription information and / or user equipment (UE) policy-related information.

[0170] The user profile information in the first response message may include the AM policy portion of the user profile information.

[0171] At least one processor may be configured to enable the device to combine corresponding overlapping parameters from the AM policy portion of AM policy control subscription information and user profile information received in the first response message.

[0172] The AM policy section of the user profile information may include indications that policy decisions depend on the state of one or more policy counters maintained at CHF.

[0173] The AM policy section of the user profile information may include one or more CHF addresses, including at least one of the primary CHF address and / or secondary CHF address.

[0174] At least one processor may be configured to send a third request message indicating a user identifier to the Charging Function (CHF). The user identifier may belong to an active user and / or device. One or more addresses of the CHF may be specific to the user identifier.

[0175] At least one processor may be configured to enable the device to retrieve expenditure restriction data. Prior to retrieving the expenditure restriction data, at least one processor may be configured to enable the device to receive an indication of a user identifier. The identifier may belong to a new active user. The retrieval may include initiating an intermediate expenditure restriction report retrieval procedure. The device may execute the initiation when a new active user identifier is notified to the device. The procedure may be initiated by the CHF. The initiation may include at least one of the user identifier and / or subscriber identifier as parameters. The device may include a UDM.

[0176] The information in the second response message may include at least one of AM subscription data and / or SM subscription data.

[0177] At least one processor can be configured to enable the device to merge UE subscription data with corresponding user profile data to obtain subscription information.

[0178] At least one processor may be configured to enable the device to receive at least one of UE subscription data and / or corresponding user profile data from a network entity.

[0179] The second response message may include the status of the user profile identifier or user identifier verification information.

[0180] Network entities may include a unified data repository (UDR).

[0181] The disclosure herein provides a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured such that the processor: receives a first request message for policy association establishment from an Access and Mobility Management Function (AMF); transmits a second request message for retrieving user profile information to a network entity; receives a first response message from the network entity, the first response message containing at least one of user profile information and / or policy control subscription information; and transmits a second response message to the AMF, the second response message including information at least partially based on the first response message.

[0182] The disclosure herein provides a method for wireless communication, the method comprising: receiving a first request message for policy association establishment from an Access and Mobility Management Function (AMF); transmitting a second request message for retrieving user profile information to a network entity; receiving a first response message from the network entity, the first response message containing at least one of user profile information and / or policy control subscription information; and transmitting a second response message to the AMF, the second response message including information at least partially based on the first response message.

[0183] The method may include deriving information from at least a first response message.

[0184] The disclosure herein provides a PCF capable of performing the following: receiving a request message for policy association establishment, the request message containing parameters indicating at least the following: a user profile ID (or user ID) and service restriction parameters; retrieving a user profile (e.g., from a UDR) using the user profile ID (e.g., user ID); determining an AM policy or a UE policy based on the user profile or service restriction parameters; indicating an active user ID to the CHF; and collecting billing information associated with the user ID.

[0185] The disclosure herein provides a UDM capable of performing the following: retrieving a user profile based on an verified user ID (e.g., from a UDR); receiving a user profile containing AM subscription data and SM subscription data; and transmitting a response message indicating the derived AM / SM subscription data (e.g., to an AMF or SMF) by merging the UE subscription data with the corresponding user profile data.

[0186] The disclosure herein provides a method for a network entity (e.g., PCF) in a communication network, comprising: receiving a first request message for policy association establishment (e.g., from an AMF), wherein the request message indicates at least: a user profile ID (or user ID) and service restriction parameters; transmitting a second request message for retrieving a user profile (e.g., transmitted to a UDR); receiving a first response message containing a user profile associated with the second request message; and transmitting a second response message associated with the first request message indicating the derived policy (e.g., transmitted to the AMF).

[0187] After receiving the first response message, the PCF can determine the AM policy or UE policy based on the user profile or service limitation parameters (e.g., received in the first request message).

[0188] The user profile received in the first response message may contain AM policy-related information or UE policy-related information.

[0189] The method may further send a request message indicating the user identifier of the active user to the billing function.

[0190] The disclosure herein provides a method for a network entity (e.g., UDM) in a communication network, comprising: receiving a first request message for policy association establishment (e.g., from AMF), wherein the request message indicates at least: a user profile ID (or user ID) and service restriction parameters; transmitting a second request message for retrieving a user profile (e.g., transmitted to a UDR); receiving a first response message containing the user profile associated with the second request message; and transmitting a second response message associated with the first request message indicating derived subscription information (e.g., transmitted to the AMF).

[0191] The exported subscription information in the second response message may be at least one of the following: AM subscription data and SM subscription data.

[0192] The exported subscription information in the second response message is obtained by merging UE subscription data with the corresponding user profile data.

[0193] It should be noted that the methods described herein describe implementation schemes, and the operations and steps may be rearranged or otherwise modified, and other implementation schemes are possible.

[0194] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

[0195] The following abbreviations are relevant to the areas covered in this document: 5GC / 5GS, 5th Generation Core Network / 5th Generation System; 5QI, 5G QoS Identifier; AAA, Authentication, Authorization and Accounting; AF, Application Function; AIoT, Ambient Internet of Things; AM, Access and Mobility; AMF, Access and Mobility Management Function; AN, Access Network; AS, Application Server; BS, Base Station; CN, Core Network; CP, Control Plane; EC, Energy Consumption; ECF, Energy Consumption Function; ECL, Energy Credit Limit; eNB, Evolved Node B; EPC / EPS, Evolved Packet Core / Evolved Packet System; GBR, Guaranteed Bit Rate; gNB, 5G Node B; ID, Identifier; IE, Information Element; LTE, Long Term Evolution; NAS, Non-Access Stratum; MM, Mobility Management; MO, Mobile Initiated; MRU, Mobility Registration Update; MT, Mobile Termination; NEF, Network Open Function; NF, Network Function; NPN, Non-Public Network; NR, New Radio; NRF, Network Repository Function; NS, Network Slice; NWDAF, Network Data Analysis Function; OAM, Operation, Management and Maintenance; PCF, Policy Control Function; PDU, Protocol Data Unit; PLMN; HPLMN; VPLMN, Public Land Mobile Network; Home PLMN; Visited PLMN; RAN, Radio Access Network; RAT, Radio Access Technology / Type; S-NSSAI, Single Network Slice Selection Auxiliary Information; SM, Session Management; SMF, Session Management Function; SNPN, Standalone Non-Public Network; SUPI, Subscription Permanent Identifier; TA, Tracking Area; TRP, Transmitter-Receiver Point; UDM, Unified Data Management; UDR, Unified Data Repository; UE, User Equipment; UMTS, Universal Mobile Telecommunications System; UP, User Plane; UPF, User Plane Functions; USIM, Universal Subscriber Identification Module; and (E)-UTRAN, (Evolved) Universal Terrestrial Radio Access Network.

Claims

1. A device for wireless communication, comprising: At least one memory; and At least one processor, coupled to and configured to enable the device to: Receives a first request message from the Access and Mobility Management Function (AMF) for policy association establishment; A second request message to retrieve user profile information is sent to the network entity; Receive a first response message from the network entity, the first response message containing at least one of the user profile information and / or policy control subscription information; and A second response message is sent to the AMF, the second response message including information at least in part based on the first response message.

2. The device according to claim 1, wherein the first request message includes at least one of a user profile identifier, a user identifier, and / or one or more service restriction parameters.

3. The device according to claim 1 or claim 2, wherein the second request message includes at least one of the subscription identifier, the user profile identifier, and / or the user identifier.

4. The device according to any of the preceding claims, wherein the derived information includes the derived access and mobility AM policy.

5. The device of claim 4, wherein the at least one processor is configured to cause the device to derive the derived AM policy based on AM policy-related information and UE policy-related information received in the first response message.

6. The device according to any of the preceding claims, wherein the policy control subscription information includes at least one of AM policy control subscription information and / or user equipment (UE) policy-related information.

7. The device according to any of the preceding claims, wherein the user profile information in the first response message includes the AM policy portion of the user profile information.

8. The device of claim 7, wherein the at least one processor is configured to cause the device to combine corresponding overlapping parameters from the AM policy control subscription information and the user profile information received in the first response message.

9. The device of claim 7 or claim 8, wherein the AM policy portion of the user profile information includes an indication that policy decisions depend on the state of one or more policy counters maintained at CHF.

10. The device according to any one of claims 7 to 9, wherein the AM policy portion of the user profile information includes one or more CHF addresses, including at least one of a primary CHF address and / or a secondary CHF address.

11. The device according to any of the preceding claims, wherein the at least one processor is configured to send a third request message indicating a user identifier to the billing function CHF.

12. The device of claim 11, wherein one or more addresses of CHF are specific to a user identifier.

13. The device according to any of the preceding claims, wherein the at least one processor is configured to enable the device to retrieve expenditure restriction data.

14. The device according to any of the preceding claims, wherein the information in the second response message includes at least one of AM subscription data and / or SM subscription data.

15. The device according to any of the preceding claims, wherein the at least one processor is configured to cause the device to merge UE subscription data with corresponding user profile data to obtain the subscription information.

16. The device of claim 15, wherein the at least one processor is configured to enable the device to receive at least one of the UE subscription data and / or the corresponding user profile data from the network entity.

17. The device according to any of the preceding claims, wherein the second response message includes the status of a user profile identifier or user identifier verification information.

18. The device according to any of the preceding claims, wherein the network entity includes a unified data repository (UDR).

19. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory and configured to enable the processor to: Receives a first request message from the Access and Mobility Management Function (AMF) for policy association establishment; A second request message to retrieve user profile information is sent to the network entity; Receive a first response message from the network entity, the first response message containing at least one of the user profile information and / or policy control subscription information; and A second response message is sent to the AMF, the second response message including information at least in part based on the first response message.

20. A method for wireless communication, the method comprising: Receives a first request message from the Access and Mobility Management Function (AMF) for policy association establishment; A second request message to retrieve user profile information is sent to the network entity; Receive a first response message from the network entity, the first response message containing at least one of the user profile information and / or policy control subscription information; and A second response message is sent to the AMF, the second response message including information at least in part based on the first response message.

Images