Apparatus, method and computer program

Abstract

According to the present disclosure, there is provided an apparatus comprising: means for storing at least one flag in a first state at a first time, where the at least one flag is associated with at least one user equipment, and the first state indicates that the at least one user equipment does not require a policy association; means for receiving a request from the network open function at a second time after the first time, the request indicating that the at least one flag should be updated to a second state, where the second state indicates that the at least one user equipment requires a policy association, wherein the policy association is aimed at meeting service requirements of services that have been or would be provided at the at least one user device; and means for updating the flag to the second state in response to receiving the request.

Description

Technical Field

[0001] Various example embodiments of the present disclosure relate to methods, apparatus and computer programs, and particularly, but not exclusively, to policy association in a communication network. Background Art

[0002] A communication system can be viewed as a facility that enables a communication session between two or more entities (such as user terminals, base stations, and / or other nodes) by providing a carrier between various entities involved in a communication path. A communication system can be provided, for example, by a communication network and one or more compatible communication devices. A communication session may include, for example, communication of data for carrying communication, such as voice, video, email (email), text message, multimedia, and / or content data, etc. Non-limiting examples of the services provided include two-way or multi-way calls, data communications or multimedia services, and access to a data network system (such as the Internet). In a wireless communication system, at least a portion of a communication session between at least two stations occurs via a wireless link. Examples of wireless communication systems include public land mobile networks (PLMNs), satellite-based communication systems, and different wireless local networks, such as wireless local area networks (WLANs). Some wireless communication systems may be divided into cells, and are therefore often referred to as cellular systems.

[0003] A user may access the communication system through an appropriate communication device or terminal. The user's communication device may be referred to as User Equipment (UE) or User Device.

[0004] A communication system and associated equipment typically operate in accordance with a given standard or specification that specifies what the various entities associated with the system are allowed to do and how it should be implemented. Communication protocols and / or parameters to be used for the connection are also defined. An example of a communication system is UTRAN (3G radio). Other examples of communication systems are the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology and the so-called 5G or New Radio (NR) networks. NR is being standardized by the Third Generation Partnership Project (3GPP). Other examples of communication systems include 5G-Advanced (NRRe1-18 and beyond) and 6G. Summary of the invention

[0005] Some example embodiments of the present disclosure will be described with respect to certain aspects. These aspects are not intended to indicate the key or essential features of the example embodiments of the present disclosure, nor are they intended to be used to limit their scope. In view of the present disclosure, other features, aspects, and elements will be apparent to those skilled in the art.

[0006] According to a first aspect, a device is provided, comprising: a component for storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user device, and the first state indicates that the at least one user device does not require policy association; a component for receiving a request from a network open function at a second time after the first time, the request indicating that the at least one flag should be updated to a second state, wherein the second state indicates that the at least one user device requires policy association, wherein the purpose of the policy association is to meet the service requirements of a service that has been or will be provided at the at least one user device; and a component for updating the flag to the second state in response to receiving the request.

[0007] According to some examples, the apparatus includes means for storing a request-specific transaction identifier.

[0008] According to some examples, the apparatus includes means for receiving a plurality of requests and a plurality of corresponding transaction identifiers.

[0009] According to some examples, the apparatus includes means for starting a timer in response to updating the flag to the second state, and means for restoring the flag to the first state upon expiration of the timer.

[0010] According to some examples, the apparatus includes: means for causing one or more other entities to update the flag to a second state, the one or more other entities including at least one of: a unified data repository; or an access and mobility management function.

[0011] According to some examples, the policy association includes at least one of: a user device behavior policy; an access management policy; or a session management policy.

[0012] According to some examples, a service that has been or is to be provided at at least one user equipment is configured by an application function.

[0013] According to some examples, the at least one flag includes a first flag, and the apparatus includes means for storing a second flag, wherein the second flag is configured to be updated between a first state and a second state in response to an instruction from the operating and maintaining node.

[0014] According to some examples, the apparatus includes means for: exposing both the first flag and the second flag to the service consumer; or exposing only one of the first flag or the second flag to the service consumer.

[0015] According to some examples, the apparatus includes a unified data management node.

[0016] According to some examples, the apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause execution of the apparatus.

[0017] According to a second aspect, a device is provided, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to at least perform: storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user device, and the first state indicates that the at least one user device does not require policy association; receiving a request from a network open function at a second time after the first time, the request indicating that the at least one flag should be updated to a second state, wherein the second state indicates that the at least one user device requires policy association, wherein the purpose of the policy association is to meet service requirements of a service that has been or will be provided at the at least one user device; and, in response to receiving the request, updating the flag to the second state.

[0018] According to a third aspect, a device is provided, comprising: a circuit system for storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user device and the first state indicates that the at least one user device does not require policy association; a circuit system for receiving a request from a network open function at a second time after the first time, the request indicating that the at least one flag should be updated to a second state, wherein the second state indicates that the at least one user device requires policy association, wherein the purpose of the policy association is to meet the service requirements of a service that has been or will be provided at the at least one user device; and a circuit system for updating the flag to the second state in response to receiving the request.

[0019] According to a fourth aspect, a method performed by a device is provided, the method comprising: at the device, storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user device and the first state indicates that at least one user device does not require policy association; at the device, receiving a request from a network open function at a second time after the first time, the request indicating that at least one flag should be updated to a second state, wherein the second state indicates that at least one user device requires policy association, wherein the purpose of the policy association is to meet service requirements of a service that has been or will be provided at at least one user device; and in response to receiving the request, updating the flag to the second state.

[0020] According to some examples, the method includes storing a request-specific transaction identifier.

[0021] According to some examples, the method includes receiving a plurality of requests and a plurality of corresponding transaction identifiers.

[0022] According to some examples, the method includes starting a timer in response to updating the flag to the second state, and restoring the flag to the first state upon expiration of the timer.

[0023] According to some examples, the method includes causing one or more other entities to update the flag to a second state, the one or more other entities including at least one of: a unified data repository; or an access and mobility management function.

[0024] According to some examples, the policy association includes at least one of: a user device behavior policy; an access management policy; or a session management policy.

[0025] According to some examples, a service that has been or is to be provided at at least one user equipment is configured by an application function.

[0026] According to some examples, the at least one flag includes a first flag, and the method includes storing a second flag, wherein the second flag is configured to be updated between the first state and the second state in response to an instruction from the operating and maintaining node.

[0027] According to some examples, the method includes: exposing both the first flag and the second flag to the service consumer; or exposing only one of the first flag or the second flag to the service consumer.

[0028] According to some examples, the apparatus includes: a unified data management node.

[0029] According to a fifth aspect, a computer program is provided, comprising instructions, which, when executed by an apparatus, cause the apparatus to perform at least the following operations: at the apparatus, storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user device, and the first state indicates that at least one user device does not require policy association; at the apparatus, receiving a request from a network open function at a second time after the first time, the request indicating that at least one flag should be updated to a second state, wherein the second state indicates that at least one user device requires policy association, wherein the purpose of the policy association is to meet service requirements of a service that has been or will be provided at at least one user device; and in response to receiving the request, updating the flag to the second state.

[0030] According to a sixth aspect, a computer program is provided, comprising instructions stored thereon, the instructions being used to perform at least the following operations: storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user device, and the first state indicates that the at least one user device does not require policy association; receiving a request from a network open function at a second time after the first time, the request indicating that the at least one flag should be updated to a second state, wherein the second state indicates that the at least one user device requires policy association, wherein the purpose of the policy association is to meet service requirements of a service that has been or will be provided at the at least one user device; and updating the flag to the second state in response to receiving the request.

[0031] According to a seventh aspect, a non-transitory computer-readable medium is provided, comprising program instructions, which, when executed by an apparatus, cause the apparatus to perform at least the following operations: at the apparatus, storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user device, and the first state indicates that at least one user device does not require policy association; at the apparatus, receiving a request from a network open function at a second time after the first time, the request indicating that at least one flag should be updated to a second state, wherein the second state indicates that at least one user device requires policy association, wherein the purpose of the policy association is to meet service requirements of a service that has been or will be provided at at least one user device; and in response to receiving the request, updating the flag to the second state.

[0032] According to an eighth aspect, a non-transitory computer-readable medium is provided, comprising program instructions stored thereon, the program instructions being used to perform at least the following operations: storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user device, and the first state indicates that at least one user device does not require policy association; receiving a request from a network open function at a second time after the first time, the request indicating that at least one flag should be updated to a second state, wherein the second state indicates that at least one user device requires policy association, wherein the purpose of the policy association is to meet service requirements of a service that has been or will be provided at at least one user device; and updating the flag to the second state in response to receiving the request.

[0033] According to a ninth aspect, a device is provided, comprising: a component for sending a first policy control establishment request for establishing a policy association for at least one user device at a first time, the purpose of the policy association being to meet the service requirements of a service that has been or will be provided at at least one user device; a component for sending an instruction to a unified data management node in response to receiving an erroneous response to the first policy control establishment request, the instruction instructing the unified data management node to update the state of a flag from a first state to a second state, wherein the first state of the flag indicates that at least one user device does not require a policy association, and the second state of the flag indicates that at least one user device requires a policy association; and a component for sending a second policy control establishment request for at least one user device at a second time after the first time.

[0034] According to some examples, the apparatus includes means for receiving an identifier of a policy and charging function in response to the second policy control setup request.

[0035] According to some examples, the apparatus includes: a component for contacting policy and billing functions to create at least one policy association for at least one user device, the at least one policy association including at least one of: a user device behavior policy; an access management policy; or a session management policy.

[0036] According to some examples, the apparatus includes: means for waiting a configured period of time after sending a first policy control setup request before sending a second policy discovery request.

[0037] According to some examples, the apparatus includes means for sending a subscription request in response to receiving an error response and waiting for notification before sending a second policy control setup request.

[0038] According to some examples, the apparatus includes means for sending an error message upon determining that a suitable policy and charging function is not assigned to the at least one user equipment and the at least one user equipment is not registered with the unified data management node.

[0039] According to some examples, the first policy discovery request and the second policy discovery request are sent to a binding support function that acts as an intermediary between the device and the unified data management node.

[0040] According to some examples, the apparatus includes: a network open function node.

[0041] According to some examples, the apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause execution of the apparatus.

[0042] According to the tenth aspect, a device is provided, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, causes the device to at least execute: sending a first policy control establishment request for establishing a policy association for at least one user device at a first time, the purpose of which is to meet the service requirements of a service that has been or will be provided at at least one user device; in response to receiving an error response to the first policy control establishment request, sending an instruction to a unified data management node, the instruction instructing the unified data management node to update the state of a flag from a first state to a second state, wherein the first state of the flag indicates that at least one user device does not require a policy association, and the second state of the flag indicates that at least one user device requires a policy association; and sending a second policy control establishment request for at least one user device at a second time after the first time.

[0043] According to an eleventh aspect, a device is provided, comprising: a circuit system for sending a first policy control establishment request for establishing a policy association for at least one user device at a first time, the purpose of the policy association being to meet the service requirements of a service that has been or will be provided at at least one user device; a circuit system for sending an instruction to a unified data management node in response to receiving an erroneous response to the first policy control establishment request, the instruction instructing the unified data management node to update the state of a flag from a first state to a second state, wherein the first state of the flag indicates that at least one user device does not require a policy association, and the second state of the flag indicates that at least one user device requires a policy association; and a circuit system for sending a second policy control establishment request for at least one user device at a second time after the first time.

[0044] According to the twelfth aspect, a method performed by an apparatus is provided, the method comprising: sending a first policy control establishment request for establishing a policy association for at least one user device at a first time, the purpose of the policy association being to meet the service requirements of a service that has been or will be provided at at least one user device; in response to receiving an error response to the first policy control establishment request, sending an instruction to a unified data management node, the instruction instructing the unified data management node to update the state of a flag from a first state to a second state, wherein the first state of the flag indicates that at least one user device does not require a policy association, and the second state of the flag indicates that at least one user device requires a policy association; and sending a second policy control establishment request for at least one user device at a second time after the first time.

[0045] According to some examples, the method includes receiving an identifier of a policy and charging function in response to the second policy control setup request.

[0046] According to some examples, the method includes: contacting policy and billing functions to create at least one policy association for at least one user device, the at least one policy association including at least one of: a user device behavior policy; an access management policy; or a session management policy.

[0047] According to some examples, the method includes waiting for a configured period of time after sending a first policy control setup request before sending a second policy discovery request.

[0048] According to some examples, the method includes sending a subscription request in response to receiving an error response, and waiting for a notification before sending a second policy control setup request.

[0049] According to some examples, the method includes sending an error message when it is determined that no appropriate policy and charging functions are assigned to the at least one user equipment and the at least one user equipment is not registered with the unified data management node.

[0050] According to some examples, the first policy discovery request and the second policy discovery request are sent to a binding support function that acts as an intermediary between the device and the unified data management node.

[0051] According to some examples, the apparatus includes: a network open function node.

[0052] According to the thirteenth aspect, a computer program is provided, comprising instructions, which, when executed by an apparatus, cause the apparatus to perform at least the following operations: sending a first policy control establishment request for establishing a policy association for at least one user device at a first time, the purpose of the policy association being to meet the service requirements of a service that has been or will be provided at at least one user device; in response to receiving an error response to the first policy control establishment request, sending an instruction to a unified data management node, the instruction instructing the unified data management node to update the state of a flag from a first state to a second state, wherein the first state of the flag indicates that at least one user device does not require a policy association, and the second state of the flag indicates that at least one user device requires a policy association; and sending a second policy control establishment request for at least one user device at a second time after the first time.

[0053] According to the fourteenth aspect, a computer program is provided, comprising instructions stored thereon, the instructions being used to perform at least the following operations: sending a first policy control establishment request for establishing a policy association for at least one user device at a first time, the purpose of the policy association being to meet the service requirements of a service that has been or will be provided at at least one user device; in response to receiving an error response to the first policy control establishment request, sending an instruction to a unified data management node, the instruction instructing the unified data management node to update the state of a flag from a first state to a second state, wherein the first state of the flag indicates that at least one user device does not require a policy association, and the second state of the flag indicates that at least one user device requires a policy association; and sending a second policy control establishment request for at least one user device at a second time after the first time.

[0054] According to the fifteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions, which, when executed by an apparatus, cause the apparatus to perform at least the following operations: sending a first policy control establishment request for establishing a policy association for at least one user device at a first time, the purpose of the policy association being to meet the service requirements of a service that has been or will be provided at at least one user device; in response to receiving an error response to the first policy control establishment request, sending an instruction to a unified data management node, the instruction instructing the unified data management node to update the state of a flag from a first state to a second state, wherein the first state of the flag indicates that at least one user device does not require a policy association, and the second state of the flag indicates that at least one user device requires a policy association; and sending a second policy control establishment request for at least one user device at a second time after the first time.

[0055] According to the sixteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions stored thereon, the program instructions being used to perform at least the following operations: sending a first policy control establishment request for establishing a policy association for at least one user device at a first time, the purpose of the policy association being to meet the service requirements of a service that has been or will be provided at at least one user device; in response to receiving an error response to the first policy control establishment request, sending an instruction to a unified data management node, the instruction instructing the unified data management node to update the state of a flag from a first state to a second state, wherein the first state of the flag indicates that at least one user device does not require a policy association, and the second state of the flag indicates that at least one user device requires a policy association; and sending a second policy control establishment request for at least one user device at a second time after the first time.

[0056] According to the seventeenth aspect, a device is provided, comprising: a component for subscribing to information related to at least one user device to a unified data management node; a component for receiving an indication from the unified data management node that a flag has been updated from a first state to a second state at the unified data management node, wherein the first state indicates that at least one user device does not require a policy association, and the second state indicates that at least one user device requires a policy association; and a component for communicating with a policy control function to establish a policy association for at least one user device in response to receiving an indication that the flag has been updated.

[0057] According to some examples, the apparatus includes: access and mobility management functionality.

[0058] According to some examples, the apparatus includes: session management functionality.

[0059] According to some examples, the apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause execution of the apparatus.

[0060] According to the eighteenth aspect, a device is provided, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to at least perform: subscribing to information related to at least one user device to a unified data management node; receiving an indication from the unified data management node that a flag has been updated from a first state to a second state at the unified data management node, wherein the first state indicates that at least one user device does not require a policy association, and the second state indicates that at least one user device requires a policy association; and, in response to receiving the indication that the flag has been updated, communicating with a policy control function to establish a policy association for at least one user device.

[0061] According to the nineteenth aspect, a device is provided, comprising: a circuit system for subscribing to information related to at least one user device to a unified data management node; a circuit system for receiving an indication from the unified data management node that a flag has been updated from a first state to a second state at the unified data management node, wherein the first state indicates that at least one user device does not require a policy association, and the second state indicates that at least one user device requires a policy association; and a circuit system for communicating with a policy control function to establish a policy association for at least one user device in response to receiving an indication that the flag has been updated.

[0062] According to the twentieth aspect, a method performed by an apparatus is provided, the method comprising: subscribing to information related to at least one user device to a unified data management node; receiving an indication from the unified data management node that a flag has been updated from a first state to a second state at the unified data management node, wherein the first state indicates that at least one user device does not require a policy association, and the second state indicates that at least one user device requires a policy association; and, in response to receiving the indication that the flag has been updated, communicating with a policy control function to establish a policy association for at least one user device.

[0063] According to the twenty-first aspect, a computer program is provided, comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the following operations: subscribing to information related to at least one user device to a unified data management node; receiving an indication from the unified data management node that a flag has been updated from a first state to a second state at the unified data management node, wherein the first state indicates that at least one user device does not require a policy association, and the second state indicates that at least one user device requires a policy association; and, in response to receiving an indication that the flag has been updated, communicating with a policy control function to establish a policy association for at least one user device.

[0064] According to the twenty-second aspect, a computer program is provided, comprising instructions stored thereon, the instructions being used to perform at least the following operations: subscribing to information related to at least one user device to a unified data management node; receiving an indication from the unified data management node that a flag has been updated from a first state to a second state at the unified data management node, wherein the first state indicates that at least one user device does not require a policy association, and the second state indicates that at least one user device requires a policy association; and, in response to receiving an indication that the flag has been updated, communicating with a policy control function to establish a policy association for at least one user device.

[0065] According to the twenty-third aspect, a non-transitory computer-readable medium is provided, comprising program instructions, which, when executed by an apparatus, cause the apparatus to perform at least the following operations: subscribing to information related to at least one user device to a unified data management node; receiving an indication from the unified data management node that a flag has been updated from a first state to a second state at the unified data management node, wherein the first state indicates that at least one user device does not require a policy association, and the second state indicates that at least one user device requires a policy association; and, in response to receiving an indication that the flag has been updated, communicating with a policy control function to establish a policy association for at least one user device.

[0066] According to the twenty-fourth aspect, a non-transitory computer-readable medium is provided, comprising program instructions stored thereon, the program instructions being used to perform at least the following operations: subscribing to information related to at least one user device to a unified data management node; receiving an indication from the unified data management node that a flag has been updated from a first state to a second state at the unified data management node, wherein the first state indicates that at least one user device does not require a policy association, and the second state indicates that at least one user device requires a policy association; and, in response to receiving an indication that the flag has been updated, communicating with a policy control function to establish a policy association for at least one user device. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Some example embodiments will now be described by way of non-limiting and illustrative examples with reference to the accompanying drawings, in which:

[0068] Figure 1 shows a representation of a network system according to some example embodiments;

[0069] Figure 2 is a signaling diagram according to an example embodiment;

[0070] Figure 3 is a signaling diagram according to another example embodiment;

[0071] Figure 4 shows a schematic representation of a control device according to some example embodiments;

[0072] Figure 5 shows a schematic representation of an apparatus according to some example embodiments;

[0073] Figure 6 is a flow chart of a method according to an example embodiment;

[0074] Figure 7 is a flow chart of a method according to an example embodiment;

[0075] Figure 8 is a flow chart of a method according to an example embodiment;

[0076] Fig. 9 A schematic representation of a non-volatile memory medium storing instructions is shown which, when executed by a processor, allow the processor to perform one or more steps of the method of some example embodiments. DETAILED DESCRIPTION

[0077] In the following, various exemplary embodiments are explained with reference to a mobile communication device capable of communicating via a wireless cellular system and a mobile communication system providing services for such mobile communication devices. Figure 1Certain general aspects of wireless communication systems, their access systems, and mobile communication devices are briefly explained to aid understanding of the technology behind the described examples.

[0078] Figure 1 A schematic representation of a 5G system (5GS) is shown, which is provided as a non-limiting and illustrative example of a communication system. The 5GS may include a terminal or user equipment (UE) 100, a 5G radio access network (5GRAN) 102, or a next generation radio access network (NG-RAN), a 5G core network (5GC) 104, one or more application functions (AFs) 106, and one or more data networks.

[0079] 5G-RAN may include one or more gNodeBs (gNBs) connected to one or more gNodeB (gNB) centralized unit functions, or one or more gNodeB (gNB) distributed unit functions.

[0080] 5GC 104 may include the following entities (by way of non-limiting and illustrative examples): network slice selection function (NSSF); network openness function 108; network repository function (NRF); policy control function (PCF); unified data management (UDM) 110; application function (AF) 106; authentication server function (AUSF) 112; access and mobility management function (AMF) 114; session management function (SMF) 116; user plane function 118; and data network (DN) 120. Figure 1 Also shown are various interfaces (N1, N2, etc.) that may be implemented between the various elements of the system.

[0081] It should be noted that although some example embodiments are described with respect to 5G networks, similar principles may be applied with respect to other networks and communication systems (such as 5G-Advanced networks, 6G networks and above).

[0082] In 5GC, different kinds of policies are used. For example, these policies can be provided by PCF to AMF, SMF, or UE. In some examples, PCF determines the policy, and PCF also typically stores the policy and delivers the policy. The policy is also stored on the policy receiver side. The policy receiver side can be, for example, UE (for UE policy), AMF (for AMF policy), and SMF (for SMF policy). Three such policies are:

[0083] UE (User Equipment) policies: are provided to the UE via the AMF when the UE registers and determine the behavior of the UE. For example, these policies can determine the behavior of access network discovery / selection (ANDSP) and UE routing selection (URSP). UE policies can also determine the behavior of V2X, A2X, ProSe settings.

[0084] AM (Access Management) Policies: Requested by the AMF when the UE registers and provided to the AMF. These policies determine access and mobility settings such as RAT / frequency selection (RFSP) and service area restriction (SAR).

[0085] SM (Session Management) Policies: Requested by the SMF at PDU session establishment and provided to the SMF. These policies determine session management settings such as authorized QoS, usage restrictions, charging information, etc.

[0086] According to some 3GPP specifications, all three types of policies can be provided by the PCF to the AMF / SMF only when the AMF / SMF explicitly requests that the PCF apply policy control. Policies are requested by establishing a (UE / AM / SM) policy association with the PCF.

[0087] In an exceptional case, if the UE indicates that it requires a policy association, for example by including a UE policy container, the AMF shall establish a policy association. The AMF and SMF currently determine whether to establish a policy association based on local configuration.

[0088] A proposal in the 3GPP SA2 group suggests adding three flags (one for each type of policy) in the operator-configured UE subscription data in the UDM / UDR. These flags will be retrieved by the AMF / SMF and will indicate to them whether a policy association should be established for the UE or the UE's PDU Session. These flags are referred to as "smPolEnabled" (i.e. enabled session management policy), "amPolEnabled" (i.e. enabled access management policy) and "uePolEnabled" (i.e. enabled UE policy) in the following and are based on the discussion in the 3GPP SA2WID proposal S2-2306435.

[0089] Some AM, UE and SM policy associations may be established and maintained until the UE logs out or the PDU session is terminated. However, there is no policy for this Subscription Permanent Identifier (SUPI) (and / or DNN and S-NSSAI). In addition, the AMF may trigger a request for UE policy without knowing whether the UE requires UE policy. For example, some IoT devices may not require any UE policy. This may affect performance and increase signaling.

[0090] Adding the above flags can help operators provide / configure values ​​that can help AMF / SMF make better decisions to avoid establishing unnecessary policy associations. However, it is not clear when and how to provide these flags. The way to manage and exchange dynamic information related to the requirements to establish (or not establish) policy associations in 5GC is also not defined.

[0091] The present disclosure contemplates the following use cases (by way of non-limiting and illustrative examples). The present disclosure also recognizes that these use cases can be handled in an efficient manner through some additional information and processes that supplement the proposed flags:

[0092] · Use Case 1 : The AF issues an AM impact request for "any UE" based on application usage. The AM impact request can be considered as a request intended to influence access and mobility policies. In some examples, the AF can provide requirements in terms of throughput and coverage, and the PCF converts the requirements into AM policies (e.g., appropriate RFSP and SAR values).

[0093] o NEF AMInfluence API allows the AF to send requests with throughput requirements and coverage requirements (which the 5GC converts into AM policies, e.g., into RFSP and SAR, respectively). These requests can be targeted at any UE using a specific application (e.g., an application managed / handled by this AF).

[0094] This activates the application detection mechanism in the 5GC to determine which UEs will require an AM policy due to such a request. This means that the operator typically does not know for which UEs the "AM policy required" flag should be set in the UDM, because it does not know, for example, which UEs will install an app (e.g., Netflix) and when they are going to use it.

[0095] · Use Case 2 : AF issues a service parameter data configuration request to provide URSP guidance,

[0096] Thereby supporting local breakout (edge ​​computing) for any UE based on application use case.

[0097] o This case is similar to Use Case 1, except that it uses the Service Parameters API of the NEF and it affects the UE policy (URSP) instead of the AM policy. Dynamic changes in the requirements for establishing policy associations for certain UEs (e.g.

[0098] The mechanisms and causes of unpredictable changes are as described above.

[0099] · Use Case 3 : AF issues a request for certain QoS, the target is the UE IP address.

[0100] o The AF can do this by calling the AfSessionWithQoS API of the NEF, with the target being the UE IP address. The problem is that the trigger for such a request from the AF is usually the detection of the start or stop of an application running on the UE, which is performed by the AF itself and not by the 5GC as in use cases 1 and 2. For similar reasons as before, the operator cannot configure the flag with SUPI or IP address until the AF actually determines that this UE is using its application. Note that in many cases the AF is not even expected to know the list of UEs that may be able to use this application. It may only know their IP addresses after they have been assigned their IP addresses and the UE has started using the application.

[0101] · Use Case 4 : The AF makes a request to the NEF to set the payee for the AF session of a specific UE.

[0102] In view of the above, the proposal of the present disclosure is to define or configure criteria that determine the requirements for establishing / terminating (UE, AM or SM) policy associations. The present disclosure also provides processes and mechanisms for exchanging and managing information about these criteria in 5GC. In some examples, these processes include:

[0103] • Procedure for dynamically setting a flag in the UE subscription data or in the UE policy data of the UDR or UDM for the requirement to establish / terminate UE, AM, or SM policy association.

[0104] • These processes are performed by the PCF, NEF or UDR based on analysis of incoming AF requests and / or application detection events that trigger the "activation" of such AF requests.

[0105] Reset or automatic expiration of flags associated with UE, AM and SMF policy associations

[0106] In one example, two flags are defined in the UE's subscription data for each of the UE, AM, or SM policy associations: One flag is set based on the configured operator policy and is applicable only if the second flag is not set. The second flag is set and can be cleared based on an AF request.

[0107] In another example, only one flag is used. If this flag is set to "Policy Association Required" (e.g., due to configured operator policy) and no additional information is stored, the AF request does not trigger the start of an expiration timer or the storage of an AF ID.

[0108] Provide dynamic criteria / flags to AMF and SMF via subscription for new types of policy data in UDR.

[0109] • A procedure that enables a flag to be set by the NEF at the UDM when the NEF finds that no PCF is assigned to the UE (e.g. by querying the Binding Support Function (BSF)).

[0110] When reference is made to a transaction ID, it should be understood that this may mean an identifier of a request or session, such as a unique identifier. For example, a request or session may be at least one of: an ongoing or current session; or a future session. For example, a transaction ID may be associated with a request or session between two NFs, such as a request from an AF / NEF to a PCF for a specific QoS, or a request from a NEF to a UDM to set a flag, etc.

[0111] According to some example embodiments, the UE subscription data type in UDM (as defined in Table 5.2.3.3.1-1 of TS 23.503, relating to a specific UE) is enhanced as follows.

[0112] Access and mobility subscription data:

[0113]

[0114]

[0115] Session management subscription data:

[0116]

[0117]

[0118] refer to Figure 2 , which is a signaling diagram schematically illustrating the communication between an application function (AF) 206, a network exposure function (NEF) 208, a binding support function (BSF) 222, a policy control function (PCF) 224, a unified data management (UDM) 210, an operation and maintenance (OAM) 226, a unified data repository (UDR) 228, an access and mobility management function (AMF) 214, and a session management function (SMF) 216.

[0119] OAM configuration occurs between the UDM 210, OAM 226, and UDR 228 at S201. For example, the OAM configuration may be for at least one UE having a corresponding at least one UE ID. For example, the UE ID may be a unique identifier for the UE. For example, in 5G, the UE ID may be a Subscription Permanent Identifier (SUPI) (inside the 5GC) or a General Public Subscription Identifier (GPSI) (externally). The OAM configuration may also provide an indication of whether at least one UE is to be subject to policy control (i.e., whether at least one UE should be set with a policy control association). In some examples, this may be accomplished using a ReqInd flag that indicates whether an AM policy association (e.g., amReqInd and / or smReqInd) is required. In the case where a policy association is required, the flag may be set to TRUE. In the case where a policy association is not required, the flag may be set to FALSE. In Figure 2 In the use case of , the flag is initially set to FALSE at S201. Then, the UDM 210 stores this flag information. In other words, it can be considered that the UDM 210 stores at least one flag in a first state at a first time, and the flag is associated with at least one user device. Figure 2 In the example of , in the first state, the flag indicates that at least one user equipment does not require policy association (eg, ReqInd=FALSE).

[0120] In some examples, OAM can use business contracts and analysis to determine whether the UE will likely need special policies that require policy associations to be established. For example, OAM can use UE communication analysis provided by NWDAF. If OAM determines that the UE will likely not need special policies that require policy associations to be established, OAM will set the relevant xxReqInd flag to false. In some examples, the flag can take the form of a Boolean indicator that indicates whether a policy association of a specific type (e.g., AM, SM, or UE) needs to be established. For example, "xx" can be "AM" (in the case where an AM policy association needs to be established, (amReqInd)), "SM" (in the case where an SM policy association needs to be established, (smReqInd)), or "UE" (in the case where a UE policy association needs to be established, (ueReqInd)).

[0121] In some examples, when the UE registers with the AMF 214, the AM subscription data is provided by the UDM 210 to the AMF 214. Similarly, when the UE establishes a PDU session, the SMF 216 serving the PDU session of the UE obtains the SM subscription data from the UDM 210. This is schematically illustrated at S202a and S202b.

[0122] In some examples, if the AM subscription data sets the flag amReqInd to TRUE, the AMF 214 should establish an AM policy association with the PCF 224 for the UE.

[0123] In some examples, if the AM subscription data sets the flag ueReqInd to TRUE, the AMF 214 should establish a UE policy association with the PCF 224 for the UE.

[0124] In some examples, if the SM subscription data sets the flag smReqInd to TRUE, the SMF 216 should establish a SM policy association for the UE session.

[0125] At S203, AF 206 sends a request to NEF 208. For example, the request at S203 may require interaction with PCF 224 of one or several UEs, or a group of UEs indicated in the request, for example:

[0126] 1. AF 206 requests affect access and mobility management policies for a single UE

[0127] 2. Request to set up an AF session with the required QoS process

[0128] 3. Request to set the payee

[0129] 4. Application Guidance for URSP Determination

[0130] Then, as shown at S204a, NEF 208 attempts to discover the PCF assigned to the UE for each UE via BSF 222. This can be referred to as a discovery request. Alternatively, the request at S204a can be referred to as a policy control establishment request. Depending on the nature of the request, BSF 222 will search for a PCF that handles the UE (for examples 1 and 4 in the above list) or handles the PDU session (for examples 2 and 3 in the above list). If no SM policy association is established for the UE, the PCF that handles the PDU session will not be assigned. If no UE policy association and / or AM policy association is established for the UE, the PCF that handles the UE will not be assigned.

[0131] exist Figure 2In the example of , at S204b, the NEF 208 is notified by the BSF 222 that no suitable PCF is assigned to one or more UEs. This can be communicated by an error message (e.g., Error: PCF not found). In an alternative example, the NEF 208 subscribes to the BSF 222 instead of sending a discovery request. In the case of a subscription, there is no error response, and the NEF 208 waits for a notification, which will be received later via Nbsf_Management_Notify (rather than a new discovery request sent by the NEF in S214a) after the PCF executes step S212. In the case of a subscription, the configured time shown at S213 (described further below) is not for resending the discovery, but for canceling the subscription and (usually) resuming interaction with the UDM 210.

[0132] In some examples, NEF 208 may receive a request from AF 206 that requires interaction with UDR 228 to provide policy-related information for one or more UEs or a group of UEs indicated in the request. This is shown, for example, in S205a to S206. For example, AF may request at least one of the following:

[0133] AF requests affect access and mobility management policies (see TS 23.502, clause 4.15.6.9.3);

[0134] AF requests service specific parameter configuration (see TS 23.502, clause 4.15.6.7); or

[0135] • The AF requests application guidance for URSP determination (see TS 23.502, clause 4.15.6.10).

[0136] At S205a, the NEF 208 requests the UDM 210 to set a flag that an appropriate policy association needs to be established (e.g., the "amReqInd" flag of the above table is used to establish an AM policy association, the "ueReqInd" flag of the above table is used to establish a UE policy association, and the "smReqInd" flag of the above table is used to establish an SM policy association). In other words, the (multiple) flags set to "false" during OAM configuration can be updated to "true". In some examples, this can be done using a Nudm_ParameterProvision_Create service operation, where the UDM 210 assigns a transaction reference ID to the request. In other words, it can be considered that at a second time (after it initially set the flag to FALSE during OAM configuration), the UDM receives a request indicating that the flag should be updated to a second state. The second state indicates that at least one user device requires a policy association.

[0137] It should be noted that in some examples, there may be more than one entity (e.g., different AFs) that can request to set the flag (amReqInd, ueReqInd, smReqInd). In some examples, a parameter such as "amTriggeringEntities" is proposed to store a list of entities (e.g., different AFs) that have requested to set or update the flag. Therefore, it can be considered that the "transaction ID" here refers to the transaction id of different requests to the UDM 210.

[0138] In some examples, both the "triggering entities" and the "transaction IDs (of these triggering entities)" are included in the "xxTriggeringEnitites" parameters. For example, these parameters may take a form such as: [AF1:tid1, tid2], [AF2:tid3], [PCF:tid4, tid5]}.

[0139] At S205b, the UDM responds to the NEF 208, for example, confirming that the flag has been set to TRUE.

[0140] In the example where UDR interaction is required, there is a step S206 between S205a and S205b, in which the UDM 210 queries the UDR 228 for information (eg, registry information) required to provide a response to the NEF 208.

[0141] Therefore, UDM 210 has updated the flag in its internal memory (to TRUE) such that the flag now indicates that policy association is required or enabled for the UE or UE group associated with the request from S203.

[0142] In some examples, when the flag is set to TRUE in response to an AF / NEF request, then in some examples, the flag is set to TRUE for a predetermined time before being restored to FALSE or cleared. To this end, the UDM can implement a timer, and when the timer expires, the flag will be restored to FALSE or cleared. In some examples, a transaction ID associated with the request can be associated with the timer. Therefore, in some examples, multiple timers may be running at the UDM, which are associated with different requests, each of which can be identified by an associated transaction ID. The start of the timer and the storage of the associated transaction ID are schematically shown at S207.

[0143] In one example, for each type (e.g., AM, SM, or UE) of policy association (xxReqInd), UDM 210 stores both a flag that can be set based on an OAM request (which can be referred to as a first flag) and a flag that can be set based on a request of other NFs (such as NEF 208) (which can be referred to as a second flag). For example, for an AM policy association establishment requirement, UDM can maintain an "amReqInd_NF" flag (which can be switched based on an AF / NEF / PCF request) and an "amReqInd_OAM" flag (which can be switched via OAM, e.g., by the operator itself).

[0144] In one example, the UDM 210 may expose only a single flag to the service consumer (e.g., AMF 214 or SMF 216), which is set if one or both of the flags (e.g., flags "amReqInd_NF" and "amReqInd_OAM") are set. For ease of explanation, the single flag may be considered a "third" flag (to be distinguished from the first and second flags described above). The third flag may be the only flag sent or exposed to the AMF / SMF, and the third flag is set (e.g., based on implementation-specific UDM logic) based on the values ​​of the other two flags (e.g., a first flag based on OAM input and a second flag based on NEF input). In some examples, in practice, the UDM logic may set the value of the third flag to the value of one of the first or second flags.

[0145] In another example, UDM 210 may expose both flags to a service consumer (e.g., AMF 214 or SMF 216), and if either of the flags is set to "true," the service consumer establishes the relevant policy association. For backward compatibility reasons, when the service consumer does not receive any flag, it may decide whether to establish a policy association based on local configuration.

[0146] In another example, the UDM 210 stores a single flag, but uses a process (described in more detail below) such that the flag remains permanently set upon OAM request, but is only temporarily set upon request of other NFs (e.g., NEF 208), such as using a timer. The indication of who set the flag to its "current" value can be part of the UDM internal logic and not part of the subscription data, e.g., it is not exposed. The UDM 210 can use this UDM internal information to determine how to set or unset the flag upon a new event that toggles the flag or attempts to toggle the flag:

[0147] o In one example, if the OAM system 226 sets the flag, the UDM

[0148] 210 stores an indication that the flag is set by the OAM system, and maintains the flag setting based on the indication.

[0149] o In another example, if the flag was not previously set, and a NF other than OAM requests to set the flag, the UDM 210 stores some additional information (e.g., an expiration timer and / or a transaction reference ID, as described above and further below). If the flag is set by the OAM system 226 while the additional information is stored, the UDM 210 removes the additional information. The UDM 210 can use the additional information to determine when to clear the flag, so if the additional information is not stored, the flag may not be cleared.

[0150] In one example, if the flag was not previously set in the UDM 210, the UDM 210 starts a timer. Here (and elsewhere), when a flag is "set," it means that the state of the flag is set to true. After the timer expires, the UDM clears the flag (e.g., sets the flag to false). If the flag was already set (e.g., the flag was already set to true) and the timer is running, the UDM restarts the timer. If the flag is set by the OAM system while the timer is running, the UDM 210 removes the timer. For example, an "amReqExpiry" timer can be used to unset a flag that was previously set by the AF / NF. In some examples, this can be a single timer maintained internally by the UDM 210, which the UDM 210 overrides for each request.

[0151] In one example, the UDM 210 stores a transaction reference ID assigned to a Nudm_ParameterProvision_Create service operation where the setting of a flag has been requested (see "amTriggeringEntities", "smTriggeringEntities" and "ueTriggeringEntities" in the data model). The setting of the flag can be requested by several independent transactions, and then all relevant transaction IDs are stored at the UDM. In the example, each transaction can be terminated independently when requested by the NEF, and then the stored relevant transaction IDs are removed. If the last stored transaction reference ID is removed, the flag is cleared. Each transaction reference ID can also be associated with a timer, which is set when the corresponding Nudm_ParameterProvision_Create service operation is received. After the timer expires, the stored transaction reference ID will also be removed.

[0152] In a real world example (for explanation purposes), if the first AF (AF1) sets the flag to "true" at noon with an expiration time of 24 hours, and then the second AF (AF2) sets the flag to "true" again at midnight with an expiration time of 24 hours, then the UDM should restart the timer such that the value "true" remains there until the next midnight (and is not removed earlier based on AF1's timer). This works for the example where there is a single timer for all transaction ids within the xxTriggeringEntities attribute. In another example, where each transaction has its own timer, the UDM adds and removes transaction ids based on its own timer, and then sets the flag back to false only when the xxTriggeringEntities attribute becomes empty again.

[0153] In some examples, the timer may be a relative value or an absolute time value configured by the AF / NEF / PCF.Each transaction id may be configured with its own timer instance, as described above.

[0154] In some examples, UDM 210 may use UDR 228 as a backend database to store information ( Figure 2 The UDR 228 is queried to authorize the request, and the data is forwarded to the UDR for storage. The data may include the xxReqInd indication and the AF transaction identifier, as shown at S210. In a variant, the above timer is located in the UDR 228 instead of the UDM 210 (e.g., S209 may occur instead of S207).

[0155] In a variation, the UDM 210 indicates in a response to the NEF 208's request to set flag(s) whether the UE is currently registered.

[0156] In an example, when the UE registers, the AMF 214 may subscribe to changes in access and mobility subscription data at the UDM 210. Thus, when a flag indicating whether AM policy association is required is set or cleared, the AMF 214 is notified by the UDM 210. Figure 2 210. Similarly, when a flag indicating whether UE policy association is required is set or cleared, AMF 214 is notified by UDM 210 (this may occur additionally or alternatively at S210). AMF 214 establishes or terminates the corresponding policy association. This enables the PCF (e.g., PCF 224) that handles the UE to be selected and registered at BSF 222. For backward compatibility reasons, in some examples, when AMF 214 does not receive any flag, it will decide whether to establish UE policy association and / or AM policy association based on local configuration.

[0157] In some examples, when the AMF 214 providing services for UE registration registers with the UDM 210, the AMF 214 can obtain AM subscription data from the UDM 210. The AM subscription data may also include new information (e.g., flag status information). As described above, the AMF 214 can subscribe to be notified when any AM subscription data changes. For example, when the data changes (e.g., the flag changes from TRUE to FALSE), the UDM 210 notifies the AMF 214. When the flag is TRUE, the AMF 214 will establish an AM or UE policy association.

[0158] According to some examples, when a PDU session is established, SMF 216 may subscribe to changes in session management subscription data at UDM 210. Thus, when a flag indicating whether SM policy association is required is set or cleared (again, this may be in e.g. Figure 2 ), UDM 210 may notify SMF 216. Then, SMF 216 establishes or terminates the corresponding policy association, which means that a PCF (e.g., PCF 224) that handles the PDU session may be selected and registered at BSF 222. For reasons of backward compatibility, in some examples, SMF 216 may decide whether to establish an SM policy association based on a local configuration when it does not receive any flag.

[0159] In some examples, when the SMF 216 providing services for the PDU session of the UE registers with the UDM 210, the SMF 216 can obtain the SM subscription data from the UDM 210. The SM subscription data can also include new information (e.g., flag status information). As described above, the SMF 216 can also subscribe to be notified when any SM subscription data changes. For example, when the data changes (e.g., the flag changes from TRUE to FALSE), the UDM 210 will notify the SMF 216. When the flag is TRUE, the SMF 216 will establish an SM association.

[0160] S211 schematically shows that the policy association created for the UE ID is sent from the AMF 214 and / or SMF 216 to the PCF 224, and then the information is forwarded to the BSF 222 at S212.

[0161] In some examples, if BSF 222 notifies NEF 208 that no suitable PCF 224 is assigned to the UE (and, in some examples, if UDM 210 also notifies NEF 208 that the UE is currently registered), NEF 208 waits for a grace period after contacting UDM 210. For example, after sending the request at S205a, NEF 208 may wait for a grace period. Figure 2In the embodiment, the waiting grace period is schematically shown at S213. For example, NEF 208 can use a timer to implement the grace period. After the grace period expires, NEF 208 can try to discover PCF via BSF again. As described above, a policy association will be established during this period, and PCF224 will be registered at BSF 222 (e.g., at S212). Then, NEF 208 can interact with PCF224 according to the requirements of existing procedures.

[0162] As an alternative to implementing a timer at the NEF 208 (e.g., as an alternative to S213), if the BSF 222 notifies the NEF 208 that no suitable PCF is assigned to the UE (e.g., at S204b) (and in the example, if the UDM 210 additionally notifies the NEF 208 that the UE is currently registered), the NEF 208 may subscribe to the BSF 222 to be notified when a PCF that provides services for the UE / AM / SM policy association of the UE is registered with the BSF 222 (e.g., a PCF with which the AMF or SMF has established XX policy association, or in other words, a PCF selected by the AMF or SMF and that now processes / determines the corresponding policy). As described above, a policy association may have been established during this period, and the PCF 224 may have been registered at the BSF 222. The BSF 222 will then notify the NEF 208 of the PCF 224 that has been registered. The NEF 208 may then interact with the PCF 224 as needed, for example, according to existing procedures.

[0163] In another example, if BSF 222 notifies NEF 208 that no suitable PCF is assigned to the UE, and if UDM 210 (e.g., S205b in the figure below) notifies NEF 208 that the UE is not currently registered (e.g., UE_registered=FALSE), then NEF 208 may reply to the request from AF 206 for interaction with the PCF with an error response that the requested configuration is not possible for the UE.

[0164] After the configured time period set at S213 has expired (or after NEF 208 learns that the PCF has been registered via a subscription notification), as shown at S214a, the NEF may retry the PCF discovery (or policy control setting) request, as shown at S214a. For example, S214a may be considered to be a retry of the discovery request sent at S204a.

[0165] Then, at S214b (opposite to S204b), the NEF 208 receives a response including the PCF ID from the BSF 222. This enables the NEF 208 to then contact the relevant PCF (e.g., the PCF with the PCF ID) to obtain policy information (e.g., UE policy information, AM policy information, SM policy information) of one or more UEs (e.g., UEs with UE IDs configured from the OAM at S201).

[0166] The NEF 208 may then contact the PCF 224 directly. For example, the NEF 208 may provide input to the PCF 224 that may affect the policy. In some APIs, the NEF 208 provides the content or basic content of the required policy (although typically not all). In other APIs, the NEF 208 simply sends a few requests and lets the PCF determine the policy accordingly. In other words, it can be considered that in the example, the NEF 208 is unaware of the 5G policies and cannot access them, but the NEF can send requests to affect the policy.

[0167] This is schematically shown at S215 .

[0168] The PCF 224 may also send an update to the AMF 214 and / or SMF 216, notifying that the policy association has been made at the PCF 224. This is schematically shown at S216.

[0169] Reference now Figure 3 , which shows an example where BSF does not exist. Therefore, Figure 3 The communication between AF 306, NEF 308, PCF 324, UDM 310, OAM 326, UDR 328, AMF 314 and SMF 316 is schematically shown. Figure 3 Many of the steps in Figure 2 The steps in are similar, so Figure 2 The detailed descriptions of these steps also apply to Figure 3 .

[0170] One difference is that, since the BSF is omitted, in response to the create request at S303, no PCF discovery (or policy control setting) request is sent to the BSF. Instead, the create request is sent directly from the NEF 308 to the UDR 328, as schematically shown at S304. For example, the request may be a Nudr_DM_Create request.

[0171] As can be seen from the above content, the present disclosure introduces some new information elements and other contents in the AM subscription data and SM subscription data in the UDM. Based on the value of the (multiple) flags in the new information elements stored in the UDM (which are provided by the UDM to the AMF or SMF), the AMF can decide whether to perform AM / UE policy association establishment with the PCF, and the SMF can decide whether to perform SM policy association with the PCF.

[0172] Therefore, compared to the current behavior (which is based on local configuration and operator policy, the AMF decides whether to perform AM policy association establishment), the present disclosure introduces a more dynamic behavior.

[0173] In some examples, the AMF may not initially establish any AM / UE policy association with the PCF (e.g., if the flag status is false). When there is an AF request that affects some AM policy or UE policy, and the network determines that there is no PCF serving the UE, the network (e.g., NEF) can cause the newly introduced flags in the AM subscription data in the UDM to be updated. When these flags are updated, the AMF is notified and then establishes a policy association with the PCF.

[0174] Policy association may only be required for a period of time, and therefore according to some examples, logic (eg, a timer) is introduced in the UDM that enables the UDM to clear the flag after a period of time.

[0175] Figure 4 The diagram shows the Figure 1 An example of a control device 400 for the functions of a 5GRAN or 5GC shown above. The control device may include at least one random access memory (RAM) 411a, at least one read-only memory (ROM) 411b, at least one processor 412, 413, and an input / output interface 414. At least one processor 412, 413 may be coupled to the RAM 411a and the ROM 411b. At least one processor 412, 413 may be configured to execute appropriate software code 415. The software code 415 may, for example, allow one or more steps to be executed to perform one or more of the aspects of the present invention. The software code 415 may be stored in the ROM 411b. The control device 400 may be interconnected with another control device 400 that controls another function of the 5GRAN or 5GC. In some example embodiments, each function of the 5GRAN or 5GC includes a control device 400. In an alternative example embodiment, two or more functions of the 5GRAN or 5GC may share a control device. As non-limiting and illustrative examples, functions such as at least one of AF, NEF, PCF, UDM, OAM, UDR, AMF, or SMF may be implemented by Figure 4Device control of the type shown. In some examples, the device can be configured to operate at least one of the following functions: AF, NEF, PCF, UDM, AMF, or SMR.

[0176] Figure 5 An example of a terminal 500 is shown, such as Figure 1 100 shown in FIG. 100. Terminal 500 may be provided by any device capable of sending and receiving radio signals. Non-limiting and illustrative examples include user equipment, mobile stations (MS) or mobile devices (such as mobile phones or so-called "smart phones"), computers provided with wireless interface cards or other wireless interface facilities (such as USB dongles), personal data assistants (PDAs) or tablet computers equipped with wireless communication capabilities, machine type communication (MTC) devices, Internet of Things (IoT) type communication devices, or any combination of these devices or similar devices. Terminal 500 may provide, for example, communication of data for carrying communication. The communication may be one or more of voice, electronic mail (email), text messaging, multimedia, data, machine data, etc.

[0177] The terminal 500 may be equipped with at least one processor 501, at least one memory ROM 502a, at least one RAM 502b and other possible components 503 for software and hardware-assisted execution of the tasks it is designed to perform, including controlling access and communication to access systems and other communication devices. The at least one processor 501 is coupled to the RAM 502b and the ROM 502a. The at least one processor 501 may be configured to execute appropriate software code 508. The software code 508 may, for example, allow one or more aspects of the current aspect to be performed. The software code 508 may be stored in the ROM 502a.

[0178] The processor, memory and other related control devices may be arranged on an appropriate circuit board and / or in a chipset. This feature is indicated by reference numeral 504. The device may optionally have a user interface, such as a keyboard 505, a touch screen or touch pad, a combination thereof, etc. Optionally, at least one of the following may be provided depending on the type of device: a display, a speaker or a microphone.

[0179] The terminal 500 may receive signals over the air or radio interface 507 via appropriate means for receiving, and may transmit signals via appropriate means for transmitting radio signals. Figure 5 In the mobile device, the transceiver arrangement is schematically designated by block 506. The transceiver arrangement 506 may be provided, for example, by a radio component and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0180] Figure 6is a flowchart of a method according to an example embodiment. Figure 6 The flowchart may be viewed from the perspective of the device. For example, the device may include or may carry a unified data management (UDM) node. In some examples, the device may be configured to operate as a UDM node. For example, the device may be configured to perform one or more functions of the UDM.

[0181] As shown at S601, the method includes: at an apparatus, storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user equipment, and the first state indicates that the at least one user equipment does not require policy association.

[0182] As shown at S602, the method includes: at the device, receiving a request from a network open function at a second time after the first time, the request indicating that at least one flag should be updated to a second state, wherein the second state indicates that at least one user device requires a policy association, wherein the purpose of the policy association is to meet the service requirements of a service that has been or will be provided at at least one user device.

[0183] As shown at S603 , the method includes: in response to receiving the request, updating the flag to a second state.

[0184] Figure 7 is a flowchart of a method according to an example embodiment. Figure 7 The flowchart may be viewed from the perspective of the device. For example, the device may include or may carry a network open function (NEF) node. In some examples, the device may be configured to operate as a NEF node. For example, the device may be configured to perform one or more functions of the NEF.

[0185] As shown at S701, the method includes: sending a first policy control establishment request from a device at a first time for establishing a policy association for at least one user equipment, the purpose of the policy association is to meet the service requirements of a service that has been or will be provided at at least one user equipment.

[0186] As shown at S702, the method includes: in response to receiving an error response to a first policy control establishment request at a device, sending an instruction to a unified data management node, the instruction instructing the unified data management node to update the state of a flag from a first state to a second state, wherein the first state of the flag indicates that at least one user device does not require policy association, and the second state of the flag indicates that at least one user device requires policy association.

[0187] As shown at S703, the method includes: sending, from the device, a second policy control setup request for at least one user equipment at a second time after the first time.

[0188] Figure 8 is a flowchart of a method according to an example embodiment. Figure 8 The flowchart can be viewed from the perspective of the device. For example, the device may include or may host AMF or SMF. In some examples, the device may be configured to operate as an AMF node and / or SMF. For example, the device may be configured to perform one or more functions of AMF and / or SMF.

[0189] As shown at S801, the method includes: subscribing to information related to at least one user equipment from a unified data management node.

[0190] As shown at S802, the method includes: receiving an indication from a unified data management node that a flag has been updated from a first state to a second state at the unified data management node, wherein the first state indicates that at least one user device does not require policy association, and the second state indicates that at least one user device requires policy association.

[0191] As shown at S803, the method includes, in response to receiving an indication that the flag has been updated, communicating with a policy control function to establish a policy association for at least one user equipment.

[0192] Fig. 9 Schematic representations of non-volatile memory media 900a (e.g., a computer compact disk (CD) or digital versatile disk (DVD)) and 900b (e.g., a universal serial bus (USB) memory stick) storing instructions and / or parameters 902 that, when executed by a processor, allow the processor to perform Figures 6 to 8 One or more steps of any method of .

[0193] It should be understood that the device may include or be coupled to other units or modules for transmission and / or reception, such as a radio component or a radio head. Although these devices have been described as one entity, different modules and memories may be implemented in one or more physical or logical entities.

[0194] It is worth noting that although some example embodiments have been described with respect to 5G networks, similar principles may be applied with respect to other networks and communication systems (e.g., 6G networks and above). Therefore, although certain example embodiments are described above with reference to certain example architectures of wireless networks, technologies, and standards by way of non-limiting and illustrative examples, the example embodiments may be applied to any other suitable form of communication system in addition to the communication system illustrated and described herein.

[0195] It is also noted herein that while the above describes example embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0196] It should be understood that although the terms "first", "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, the first element

[0197] As used herein, "at least one of: " and "at least one of " and similar expressions, where a list of two or more elements is connected by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements. As used herein, the term "and / or" includes any and all combinations of one or more of the listed items.

[0198] As used herein, unless explicitly stated, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and may include one or more intermediate steps.

[0199] In general, various example embodiments may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects of the disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device, but the disclosure is not limited thereto. Although various aspects of the disclosure may be illustrated and described as block diagrams, flow charts, or illustrated and described using some other graphical representation, it is fully understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0200] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0201] (a) pure hardware circuit implementation (e.g., implementation in analog and / or digital circuitry only) and (b) a combination of hardware circuitry and software, such as (where applicable):

[0202] (i) a combination of analog and / or digital hardware circuits and software / firmware and

[0203] (ii) any portion of hardware processor(s) with software (including digital signal processor(s), software and memory(s) that work together to enable a device, such as a mobile phone or server, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), which requires software (e.g. firmware) to operate, but where software is not required for operation, the software may be absent.

[0204] This definition of circuitry applies to all uses of the term herein, including in any claims. As another example, as used in this application, the term "circuitry" also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (their) accompanying software and / or firmware. For example, when applicable to a particular claim element, the term "circuitry" also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0205] Various example embodiments of the present disclosure may be implemented by computer software executable by a data processor of a mobile device (such as a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products) including software routines, applets and / or macros may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform example embodiments when the program is running. One or more computer executable components may be at least one software code or a portion thereof.

[0206] In addition, in this regard, it should be noted that any block of the logic flow shown in the figure can represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software can be stored on physical media (such as memory chips or memory blocks implemented in processors), magnetic media (such as hard disks or floppy disks), and optical media (such as, for example, DVDs and their data variants CDs). The physical medium can be a non-transient medium.

[0207] The term "non-transitory" as used herein is a limitation of the medium itself (eg, tangible, rather than a signal), rather than a limitation on data storage persistence (eg, RAM versus ROM).

[0208] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0209] Various example embodiments of the present disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert a logic level design into a semiconductor circuit design that is ready to be etched and formed on a semiconductor substrate.

[0210] The scope of protection sought by various exemplary embodiments of the present disclosure is defined by the independent claims.Example embodiments and features described in the present disclosure that do not fall under the scope of the independent claims, if any, should be interpreted as examples that aid in understanding the various embodiments of the present disclosure.

[0211] The foregoing description has provided a complete and informative description of various exemplary embodiments of the present disclosure by way of non-limiting and illustrative examples. However, various modifications and adaptations may become apparent to those skilled in the relevant art in view of the foregoing description when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of the present disclosure will still fall within the scope of the various exemplary embodiments of the present disclosure as set forth in the appended claims. By way of non-limiting and illustrative examples, there are additional exemplary embodiments that include a combination of one or more exemplary embodiments with any other exemplary embodiments previously discussed.

[0212] The following is a non-exhaustive list of acronyms used in this article:

[0213] 5GC – 5G Core

[0214] BSF – Binding Support Function

[0215] AMF – Access and Mobility Management Function

[0216] NEF – Network Open Function

[0217] NF – Network Function

[0218] NWDAF – Network Data Analysis Function

[0219] PCF – Policy Control Function

[0220] RFSP – RAT / Frequency Selection Strategy

[0221] SAR – Service Area Restriction

[0222] SMF – Session Management Function

[0223] UDR – Unified Data Repository

[0224] UE – User Equipment

[0225] URSP – UE Routing Selection Policy

Claims

1. A device for use in a communication network, comprising: means for storing at least one flag in a first state at a first time, wherein the at least one flag is associated with at least one user device and the first state indicates that the at least one user device does not require policy association; means for receiving, at a second time after the first time, a request from a network open function, the request indicating that the at least one flag should be updated to a second state, wherein the second state indicates that the at least one user equipment requires a policy association, wherein the purpose of the policy association is to satisfy a service requirement of a service that has been or is to be provided at the at least one user equipment; as well as Means for updating the flag to the second state in response to receiving the request.

2. The device according to claim 1, wherein the device comprises: Means for storing a transaction identifier specific to the request.

3. The device according to claim 2, wherein the device comprises: Means for receiving a plurality of requests and a plurality of corresponding transaction identifiers.

4. The device according to any one of claims 1 to 3, wherein the device comprises: means for starting a timer in response to updating the flag to the second state; as well as Means for restoring the flag to the first state upon expiration of the timer.

5. A device for use in a communication network, comprising: means for sending, at a first time, a first policy control establishment request for establishing a policy association for at least one user equipment, the policy association being intended to satisfy a service requirement of a service that has been or is to be provided at the at least one user equipment; means for sending an instruction to a unified data management node in response to receiving an error response to the first policy control setup request, the instruction instructing the unified data management node to update a state of a flag from a first state to a second state, wherein the first state of the flag indicates that the at least one user device does not require policy association, and the second state of the flag indicates that the at least one user device requires policy association; as well as Means for sending a second policy control setup request for the at least one user equipment at a second time after the first time.

6. A device for use in a communication network, comprising: A component for subscribing to a unified data management node for information related to at least one user equipment; means for receiving from the unified data management node an indication that a flag has been updated at the unified data management node from a first state to a second state, wherein the first state indicates that at least one user device does not require policy association, and the second state indicates that the at least one user device requires policy association; as well as In response to receiving the indication that the flag has been updated, communicating with a policy control function to establish a policy association for the at least one user equipment.

7. A method performed by an apparatus, the method comprising: storing, at the apparatus, at a first time, at least one flag in a first state, wherein the at least one flag is associated with at least one user device, and the first state indicates that the at least one user device does not require a policy association; receiving, at the apparatus, a request from a network open function at a second time after the first time, the request indicating that the at least one flag should be updated to a second state, wherein the second state indicates that the at least one user equipment requires a policy association, wherein a purpose of the policy association is to satisfy a service requirement of a service that has been or is to be provided at the at least one user equipment; as well as In response to receiving the request, the flag is updated to the second state.

8. A method performed by an apparatus, the method comprising: sending, at a first time, a first policy control establishment request for establishing a policy association for at least one user equipment, the policy association being intended to satisfy a service requirement of a service that has been or will be provided at the at least one user equipment; In response to receiving an error response to the first policy control setup request, sending an instruction to a unified data management node, the instruction instructing the unified data management node to update a state of a flag from a first state to a second state, wherein the first state of the flag indicates that the at least one user device does not require policy association, and the second state of the flag indicates that the at least one user device requires policy association; as well as At a second time after the first time, a second policy control setup request for the at least one user equipment is sent.

9. A method performed by an apparatus, the method comprising: Subscribe information related to at least one user equipment to a unified data management node; receiving, from the unified data management node, an indication that a flag has been updated at the unified data management node from a first state to a second state, wherein the first state indicates that at least one user device does not require policy association, and the second state indicates that at least one user device requires policy association; as well as, In response to receiving the indication that the flag has been updated, communicating with a policy control function to establish a policy association for the at least one user equipment.

10. A computer program product comprising instructions, which, when executed by an apparatus, cause the apparatus to perform at least any one of claims 7 to 9.

Images