Method and apparatus for providing results for UE policy requests

By explicitly identifying and specifying service parameter requests and responses of different types in the communication network, the problem of unclear notification of service parameter configuration results is solved, the clarity of contracts and service level agreements between operators and application providers is improved, and the signaling process is simplified.

CN123123136APending Publication Date: 2026-11-17NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610659525.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-15
Filing Date
2026-05-13
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In communication networks, it is difficult to accurately notify terminal devices of the results and detailed reasons for service parameter configuration, especially when there are multiple service parameters. This leads to unclear contracts and service level agreements between network operators and application providers, and complicated signaling processes.

Method used

A method and apparatus are provided to send and receive service parameter requests and responses through first and second network entities respectively, specify the identifiers and types, track the authorization status of service parameters, and generate clear configuration results, including the identifiers and types of service parameters, so that the requesting device can know whether the request has been satisfied.

Benefits of technology

It improves the clarity of contracts and service level agreements between network operators and application providers, reduces the complexity of signaling processes, and ensures clear notification of service parameter configuration results.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123136A_ABST
    Figure CN123123136A_ABST
Patent Text Reader

Abstract

Embodiments of this disclosure provide a method and apparatus for providing results for a user equipment (UE) policy request. An apparatus operating as a first network entity may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus operating as the first network entity to at least: send a request for configuring one or more service parameters of a communication network, wherein the request includes an identifier for at least one of the one or more service parameters; receive a response including the configuration result of at least one service parameter; wherein the response includes an identifier indicating the type of at least one service parameter and / or at least one service parameter. According to embodiments of this disclosure, the solution will help requesting devices know whether their requests have been satisfied by the network.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The various example embodiments disclosed herein relate generally to communication technologies, and more specifically to methods and apparatus for providing results for UE policy requests. Background Technology

[0002] In a communication network, service parameters can be configured (e.g., created, updated, deleted) to provide different services to one or more terminal devices (such as user equipment, UE). For example, a requesting device such as an application function (AF) can request / influence such configuration.

[0003] This configuration may succeed or fail for various reasons. However, it is difficult to inform the requesting device of the result of such configuration and / or the related detailed reasons, especially when there are many different service parameters. Summary of the Invention

[0004] This summary is provided to present a simplified version of some aspects, which will be further described in the detailed description below. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0005] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. Various embodiments are presented herein to address one or more problems disclosed herein. Specific methods and apparatus may be provided for providing results for UE policy requests.

[0006] A first aspect of this disclosure provides an apparatus operating as a first network entity, a method performed by a first network node, and / or a computer-readable medium for providing results for a UE policy request. The apparatus operating as a first network node may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus operating as a first network entity to at least: send a request for configuring one or more service parameters of a communication network, wherein the request includes an identifier for at least one of the one or more service parameters; and receive a response including a configuration result of at least one service parameter; wherein the response includes an identifier indicating the type of at least one service parameter and / or at least one service parameter.

[0007] A second aspect of this disclosure provides an apparatus operating as a second network entity, a method performed by a second network node, and / or a computer-readable medium for providing results for a UE policy request. The apparatus operating as a second network node may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus operating as a second network entity to at least perform: receiving a request for configuring one or more service parameters of a communication network, wherein the request includes an identifier for at least one of the one or more service parameters; configuring the one or more service parameters; tracking, for the at least one service parameter, whether the at least one service parameter is authorized, modified, or not authorized by the second network entity; generating a response including the configuration result of the at least one service parameter; wherein the response includes an identifier indicating the at least one service parameter and / or the type of the at least one service parameter.

[0008] Several other aspects are defined in the detailed description and dependent claims.

[0009] According to embodiments of this disclosure, the solution helps requesting devices know whether their requests have been fulfilled by the network. Furthermore, this solution enhances the relevant contracts and service level agreements (SLAs) between network operators and application providers, while also reducing potential signaling between the requesting device and the network to determine the configuration status. Attached Figure Description

[0010] The above and other aspects, features, and benefits of various embodiments of this disclosure will become more apparent by way of example, in conjunction with the following detailed description with reference to the accompanying drawings, in which the same reference numerals or letters are used to denote the same or equivalent elements. The drawings are illustrated to facilitate a better understanding of embodiments of this disclosure and are not necessarily drawn to scale, wherein: Figure 1 This is a block diagram illustrating an exemplary structure of an apparatus operating as a first network entity according to an exemplary embodiment of the present disclosure.

[0011] Figure 2 This is a flowchart illustrating the steps of a method performed by an apparatus operating as a first network entity according to an embodiment of the present disclosure.

[0012] Figure 3 This is a block diagram illustrating an exemplary structure of an apparatus operating as a second network entity according to an exemplary embodiment of the present disclosure.

[0013] Figure 4 This is a flowchart illustrating the steps of a method performed by an apparatus operating as a second network entity according to an embodiment of the present disclosure.

[0014] Figure 5This is a block diagram illustrating an apparatus / computer-readable storage medium according to embodiments of the present disclosure.

[0015] Figure 6 This is a call flow for providing results for a UE policy request according to embodiments of this disclosure. Detailed Implementation

[0016] Embodiments of this disclosure have been described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed for better understanding only and are not intended to limit the scope of this disclosure. The features, advantages, and characteristics of this disclosure described may be combined in any suitable manner in one or more embodiments.

[0017] Generally, all terms used herein should be interpreted according to their ordinary meaning in the relevant art, unless a different meaning is clearly given and / or implied from the context in which it is used. Unless the context explicitly gives and / or implies, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment.

[0018] As used herein, the term "network" or "communication network" refers to a network that conforms to any suitable communication standard, such as that used for the Internet or any wireless network. For example, wireless communication standards may include WLAN (Wireless Local Area Network), New Radio (NR), Long Term Evolution (LTE), LTE-Advanced, 5G NR, 6G, etc. In the following description, the terms "network" and "system" are used interchangeably.

[0019] The term "entity / network entity" refers to any other device (physical or virtual) in a computing device, computing node, computing function, or communication network. For example, a node in a network can include a base station (BS), access point (AP), or any other suitable device in a wireless communication network. A BS can be, for example, a B-node (B node or NB), an evolved B-node (eNodeB or eNB), a next-generation B-node (gNodeB or gNB), a remote radio unit (RRU), a radio header (RH), a remote radio header (RRH), a relay, a low-power node (such as a femtosecond, picosecond), etc. Furthermore, a node can include other core network nodes such as access and mobility management functions, AMF, session management functions, SMF, user plane functions, UPF, mobility management entities, MME or serving gateways, S-GW, etc. The term "terminal device" refers to any terminal device that can access a communication network and receive services from it. By way of example and not limitation, a terminal device refers to a mobile terminal, user equipment (UE), non-AP device (such as a non-AP station (STA)), or other suitable device. Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, wearable devices, in-vehicle wireless terminal equipment, vehicles, etc.

[0020] As an example, a terminal device can refer to a device configured to communicate according to one or more communication standards promulgated by any standards organization, such as the 3rd Generation Partnership Project (3GPP).

[0021] As yet another example, in the Internet of Things (IoT) scenario, a terminal device can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another terminal device and / or network device. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances such as refrigerators, televisions, and personal wearable devices such as watches. In other scenarios, a terminal device can represent a vehicle or other equipment capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0022] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0023] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0024] Figure 1 This is a block diagram illustrating an exemplary structure of an apparatus operating as a first network entity according to an exemplary embodiment of the present disclosure.

[0025] like Figure 1As shown, the apparatus 10 operating as a first network entity includes: at least one processor 102; and at least one memory 104 storing instructions, which, when executed by the at least one processor, cause the apparatus operating as a first network node to perform at least the method according to any of the following embodiments, such as Figure 2 , Figure 6 As shown.

[0026] Figure 2 This is a flowchart illustrating the steps of a method performed by an apparatus operating as a first network entity according to an embodiment of the present disclosure.

[0027] like Figure 2 As shown, method 200 may include: S202, sending a request for configuring one or more service parameters of a communication network; S204, receiving a response including the configuration result of at least one of the one or more service parameters. The response may also include at least one of the following: an identifier indicating at least one service parameter; and / or the type of at least one service parameter.

[0028] According to embodiments of this disclosure, the solution helps requesting devices know whether their requests have been satisfied by the network by responding with a configuration result including at least one of one or more service parameters. Specifically, identifiers and / or type indications can be used to provide a clear mapping between the result and at least one service parameter.

[0029] Furthermore, this solution will enhance the relevant contracts and service level agreements (SLAs) between network operators and application providers, while also reducing potential signaling between requesting devices and the network to determine the configuration status.

[0030] In exemplary embodiments of this disclosure, at least one service parameter may be a separate / independent part used for configuration or for a request. That is, the granularity of the response is considered sufficiently fine when the result can clearly indicate whether the configuration of the separate / independent part was successful.

[0031] Depending on the actual implementation, individual / independent parts may correspond to one or more specific parameter values, rules, strategies, or any other possible configuration methods, as long as they can be successfully configured without depending on other parameters.

[0032] In an exemplary embodiment of this disclosure, at least one service parameter is associated with a policy to be delivered to one or more terminal devices. The type of the at least one service parameter indicates the type of policy. The request includes subscription information for reports or notifications regarding the delivery of the policy. A report or notification is received by a first network entity when at least one of the following is true: the policy was successfully delivered to one or more terminal devices; the policy was unsuccessfully delivered to one or more terminal devices; the policy was partially successfully delivered to one or more terminal devices; or at least one service parameter was not authorized by a second network entity.

[0033] According to embodiments of this disclosure, the event granularity for generating reports on policy delivery can also be improved.

[0034] In an exemplary embodiment of this disclosure, the response is a report or notification received when a policy portion is successfully delivered to one or more terminal devices.

[0035] According to embodiments of this disclosure, even if the delivery of a strategy portion to one or more terminal devices is partially successful, the result can be clearly reported.

[0036] In an exemplary embodiment of this disclosure, the result indicates at least one of the following: at least one service parameter is installed on one or more terminal devices; at least one service parameter is modified by a second network entity and installed on a terminal device; at least one service parameter is rejected by a terminal device; or at least one service parameter is not authorized by a second network entity.

[0037] According to embodiments of this disclosure, even in complex scenarios, such as when modified and then installed, the result of configuring at least one service parameter can be clearly indicated.

[0038] In an exemplary embodiment of this disclosure, the second network entity includes a policy control function (PCF); and / or one or more of the terminal devices include a user equipment (UE).

[0039] According to embodiments of this disclosure, this solution may be applicable when a PCF is requested / triggered to transmit a policy to one or more UEs.

[0040] In exemplary embodiments of this disclosure, the policy is at least one of the following: vehicle-to-everything (V2X), a policy for proximity-based service communication interface 5 (PC5) interface; a V2X policy for Uu interface; a proximity-based service (ProSe) policy; an aircraft-to-everything (A2X) policy for PC5 interface; an A2X policy for Uu interface; or a ranging / sidelink policy.

[0041] According to embodiments of this disclosure, only a few strategies are listed herein as examples for illustrative purposes. However, it should be noted that any other kind of configuration (including strategies) may be applicable. Such strategies may include existing or future strategies. Furthermore, strategies may also include UE routing policies (URSPs).

[0042] In an exemplary embodiment of this disclosure, the identifier is generated by a first network entity based on at least one service parameter and is included in the request; or the identifier is a predefined identifier of at least one service parameter.

[0043] According to embodiments of this disclosure, the identifier can be customized and therefore corresponds to a custom length / number of some service parameters to be configured. Alternatively, the identifier can be fixed when the length / number of some service parameters is fixed.

[0044] In an exemplary embodiment of this disclosure, the first network entity includes an application function (AF). The request is used to create, update, or delete one or more service parameters. The AF sends the request to the Network Open Function (NEF) and receives a response from the NEF.

[0045] According to embodiments of this disclosure, the solution can be applied to AF configuration via NEF request.

[0046] Figure 3 This is a block diagram illustrating an exemplary structure of an apparatus operating as a second network entity according to an exemplary embodiment of the present disclosure.

[0047] like Figure 3 As shown, the apparatus 30 operating as a second network entity includes: at least one processor 302; and at least one memory 304 storing instructions, which, when executed by the at least one processor, cause the apparatus operating as a second network node to perform at least the method according to any of the following embodiments, such as Figure 4 , Figure 6 As shown.

[0048] Figure 4 This is a flowchart illustrating a method performed by a device operating as a second network entity.

[0049] like Figure 4 As shown, method 400 may include: S402, receiving a request for configuring one or more service parameters of a communication network; S404, configuring one or more service parameters; S406, generating a response including a configuration result of at least one of the one or more service parameters. The response may also include at least one of the following: an identifier indicating the at least one service parameter; and / or the type of the at least one service parameter. The method may further include: generating a response including a configuration result of the at least one service parameter.

[0050] According to embodiments of this disclosure, the requested device can configure service parameters and then generate a response based on the results of the configuration process. By providing a response that includes the configuration result of at least one of one or more service parameters, the solution helps the requesting device know whether its request has been satisfied by the network. In particular, identifiers and / or type indications can be used to provide a clear mapping between the result and at least one service parameter.

[0051] In an exemplary embodiment of this disclosure, at least one service parameter is associated with a policy to be delivered to one or more terminal devices. The type of the at least one service parameter indicates the type of policy. Configuring one or more service parameters includes at least one of the following: verification of the at least one service parameter, modification of the at least one service parameter, or delivery of the policy. A second network entity generates a report or notification regarding the delivery of the policy when at least one of the following conditions exists: the policy is successfully delivered to one or more terminal devices; the policy is unsuccessfully delivered to one or more terminal devices; the policy is partially successfully delivered to one or more terminal devices; or at least one service parameter is not authorized by the second network entity.

[0052] In an exemplary embodiment of this disclosure, the response is a report or notification generated when a policy portion is successfully delivered to one or more terminal devices.

[0053] In an exemplary embodiment of this disclosure, a response is generated based on at least one of the following: the result of verification of at least one service parameter; or feedback from the delivery of a policy from one or more terminal devices. The second network entity maps the feedback to at least one service parameter. The result indicates at least one of the following: at least one service parameter is installed on one or more terminal devices; at least one service parameter is modified by the second network entity and installed on a terminal device; at least one service parameter is rejected by a terminal device; or at least one service parameter is not authorized by the second network entity.

[0054] In an exemplary embodiment of this disclosure, the terminal device in one or more terminal devices includes a user equipment (UE).

[0055] In exemplary embodiments of this disclosure, the policy is at least one of the following: vehicle-to-everything (V2X), a policy for proximity-based service communication interface 5 (PC5) interface; a V2X policy for Uu interface; a proximity-based service (ProSe) policy; an aircraft-to-everything (A2X) policy for PC5 interface; an A2X policy for Uu interface; or a ranging / sidelink policy.

[0056] In exemplary embodiments of this disclosure, the identifier is generated by the application function AF based on at least one service parameter and is included in the request; or the identifier is a predefined identifier of at least one service parameter.

[0057] In an exemplary embodiment of this disclosure, the second network entity includes a Policy Control Function (PCF). The PCF receives requests from the Unified Data Repository (UDR) and sends responses to the Network Open Function (NEF).

[0058] Processors 102 and 302 can be any type of processing component, such as one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), application-specific digital logic, etc. Memory 104 and 304 can be any type of storage component, such as read-only memory (ROM), random access memory, cache memory, flash memory, optical storage, etc. Figure 5 This is a block diagram illustrating an apparatus / computer-readable storage medium according to embodiments of the present disclosure.

[0059] like Figure 5 As shown, the computer-readable storage medium 50 stores instructions 51, which, when executed by at least one processor of a device operating as a network node or terminal device, cause the at least one processor of the device to perform a method according to any of the above embodiments, such as Figure 2 , Figure 4 , Figure 6 As shown.

[0060] Furthermore, this disclosure may also provide a carrier containing the computer program / instructions described above. The carrier is an electronic signal, an optical signal, a radio signal, or one of the aforementioned computer-readable storage media. The computer-readable storage medium may be, for example, an optical disc or electronic storage device, such as RAM (Random Access Memory), ROM (Read-Only Memory), flash memory, magnetic tape, CD-ROM, DVD, Blu-ray disc, etc.

[0061] Furthermore, embodiments of this disclosure may provide exemplary device units for a first network entity, which are suitable for performing methods according to embodiments of this disclosure.

[0062] For example, the first network entity may include: a sending unit configured to send a request for configuring one or more service parameters of the communication network; and a receiving unit configured to receive a response including the configuration result of at least one of the one or more service parameters. The response may also include at least one of the following: an identifier indicating at least one service parameter; and / or the type of at least one service parameter.

[0063] In an exemplary embodiment of this disclosure, the first network entity is further configured to perform the method according to any one of the above embodiments, such as Figure 2 , Figure 6 As shown.

[0064] Furthermore, embodiments of this disclosure may provide exemplary device units for a second network entity, which are adapted to perform the methods according to embodiments of this disclosure.

[0065] For example, the second network entity may include: a receiving unit configured to receive a request for configuring one or more service parameters of a communication network; a configuration unit configured to configure one or more service parameters; and a generating unit configured to generate a response including a configuration result comprising at least one of the one or more service parameters. The response may also include at least one of the following: an identifier indicating at least one service parameter; and / or the type of at least one service parameter.

[0066] In an exemplary embodiment of this disclosure, the second network entity is further configured to perform the method according to any one of the above embodiments, such as Figure 4 , Figure 6 As shown.

[0067] The term “unit” can have a conventional meaning in the field of electronic, electrical and / or electronic equipment, and can include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, outputs and / or display functions, such as those described herein.

[0068] As used in this disclosure, the term "circuit" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog and / or digital hardware circuitry with software / firmware, and (ii) Any part of a hardware processor having software (including (multiple) digital signal processors, software, and memory that work together to enable a device such as a mobile phone or server to perform various functions), and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when the software is not required to operate.

[0069] This definition of "circuit" applies to all uses of the term in this disclosure (including in any claim). As another example, as used in this disclosure, the term "circuit system" also encompasses only hardware circuitry or a processor (or multiple processors) or a portion of hardware circuitry or a processor and its accompanying software and / or firmware. The term "circuit" also encompasses, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0070] Utilizing these units, the device may not require a fixed processor or memory, and can deploy any kind of computing and storage resources from at least one node / device / entity / assembly associated with the communication system. Virtualization and network computing technologies (e.g., cloud computing) can be further introduced to improve the efficiency of network resource utilization and network flexibility.

[0071] The techniques described herein can be implemented by various means, such that the means for implementing one or more functions of the corresponding apparatus described in the embodiments includes not only prior art means, but also means for implementing one or more functions of the corresponding apparatus described in the embodiments, and it can include separate means for each individual function, or means that can be configured to perform two or more functions. For example, these techniques can be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules / units), or combinations thereof. For firmware or software, implementation can be achieved by modules (e.g., procedures, functions, etc.) that perform the functions described herein.

[0072] In some embodiments, some or all of the functions described herein may be provided by processing circuitry that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, processing circuitry may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to individual processing circuitry or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by end users and wireless networks.

[0073] As used herein, the term “non-transient” refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0074] Based on the above embodiments, some further detailed solutions can be provided as follows.

[0075] The NEF service parameter application programming interface (API) specified in 3GPP TS (Technical Specification) 29.522 V 19.2.0 (2025-03) enables the AF (Application Function) to request / influence UE policies to be delivered to the UE (User Equipment). UE policies will be expanded in the future and currently include: -V2XP (i.e., vehicle-related or PC5 interface-related, also known as V2X strategy) -ProSeP (Proximity Service Policy) -A2XP (i.e., airborne / drone-related, also known as A2X strategy) -URSP (UE Routing Policy) -RSLPP (Rating / Side Link Positioning Strategy).

[0076] The table 5.11.2.3.2-1 of 3GPP TS 29.522 shown below contains the AF inputs of NEF, which form the corresponding UE policies. Underlined symbols are added to indicate different types of policies. In addition, some parameters are omitted here for simplicity.

[0077] Table 5.11.2.3.2-1: Definition of type ServiceParameterData

[0078]

[0079]

[0080] The above inputs ultimately reach the PCF (Policy Control Function) via the UDR (Unified Data Repository) based on the process described in Clause 5.5.8.1 of 3GPP TS 29.513 V 19.2.0 (2025-03). The PCF uses them, along with potential requests from local configuration / smart and other AFs, to determine UE policies (divided into multiple possible UE policy part identifiers) and deliver them to the UE, as specified in 3GPP TS 29.525 V 19.2.0 (2025-03).

[0081] When a network entity (such as the PCF) receives the UE policy delivery result from the UE, it sends the UE policy delivery result to the AF via the NEF as one of the following values, also specified in TS 29.522: Table 5.11.2.4.3-1: Enumerating Events The Event enumeration represents event notifications related to the results of calls to service parameters provided by AF subscription.

[0082]

[0083] Some success / failure reports exist in other APIs, most notably for PCC (Policy and Charging Control) rule installation between PCF and SMF (Session Management Function). However, this is fundamentally very different because SMF reports failures to PCF, and there are three main differences: 1) The SMF does not interact with the UE or any other entity before reporting the failure to the PCF.

[0084] 2) SMF does not authorize or modify the provided PCC rules.

[0085] 3) The granularity of the problem can be based on the PCC rules, and the possible reasons for failure are very different.

[0086] The problems with the aforementioned mechanism are partly identified in the discussion paper 3GPP C3-245211, and briefly described in the new CT3 (Core Network and Terminal Working Group 3) WID (Work Item Description) "Rel (release)-19 UE Policy Enhancement" (UEP19, with unique identifier 1060025, WI#1060025-UEP19), marked with bullet points: - Completion of fault scenarios for the specified functions.

[0087] - The notification of completion of URSP delivery results.

[0088] The problem is that the granularity of the strategy delivery results does not match the possible success / failure scenarios, for example, when: - Some UE policies affected by the AF request were successfully authorized by the PCF, while other UE policies were not authorized.

[0089] - Some UE policies affected by the AF request were successfully delivered and installed on the UE, while others were unsuccessful.

[0090] - Some UE policies affected by AF requests were successfully delivered and installed, but have been modified or extended by PCF due to local logic and / or requests from other AFs.

[0091] In scenarios such as those described above, the results provided to the AF may be ambiguous, inconsistent across different implementations, and fail to reflect the UE / network state, thus hindering the application of provider-operator contracts and SLAs (Service Level Agreements).

[0092] Embodiments of this disclosure can be proposed and are also applicable to solutions to the described problems by enabling the AF to identify individual / independent UE policy portions in its own requests and in the extended UE policy delivery results based on the following main steps: 1) Provide an identifier for each individual / independent UE policy section: a. For inputs that are arrays of a custom length, i.e., depending on how many rules the AF requests, such as for URSP, the identifier is set by the AF in the request to NEF.

[0093] b. For fixed (and affecting fixed policy types) inputs, predefined standard identifiers can exist (e.g., V2X_PC5_PARAM (parameters), V2X_UU_PARAM, PROSE_DD (direct discovery), PROSE_DC (direct communication), etc., depending on the required granularity), and do not need to be set in the AF request.

[0094] 2) When the PCF retrieves the AF request from the UDR and determines the UE policy (and its corresponding identifier, also known as UPSI (User Equipment Policy Part Identifier)) to be delivered to the UE, it tracks whether the exact content requested by the AF is “authorized,” “modified,” or “unauthorized” by the PCF itself for each AF request part ID (corresponding to each policy part) (before attempting to deliver the UE policy).

[0095] 3) If at least a portion is authorized (even if modified), the PCF performs UE policy delivery and maintains the mapping of AF-request-id to UPSI.

[0096] 4) Upon receiving a detailed UE policy delivery result from the UE as specified in Clause D 2.1.4 of TS 24.501 V 19.2.0 (2025-03), the PCF uses the received information and the above-mentioned bullet point mapping to assign one of the following results to each AF-request-part-id: a. Installed on UE b. Modified by PCF and installed on the UE c. Rejected by UE d. Not authorized by PCF 5) PCF sends extended results to AF, namely AF-Request-Part-id / Detail-Result pairs.

[0097] The following process is for providing a UE policy based on the AF (Service Parameter) input specified in Clause 5.5.8.1 of 3GPP TS 29.513, wherein embodiments of this disclosure propose improvements, in Figure 6 Both text and the text itself have been underlined.

[0098] It should be noted that the following explanation helps in understanding the extensions proposed within the context of the entire process, but the extensions do not need to be captured in 29.513, as 29.513 is referencing 29.522 / 29.519 (3GPP TS 29.519 V 19.2.0 (2025-03)) / 29.523 (3GPP TS 29.523 V 19.0.0 (2025-03)). Applying accordingly to 29.522 / 29.519 / 29.523 may be sufficient.

[0099] Figure 6 This is a call flow for providing results for a UE policy request according to embodiments of this disclosure. Figure 6 Yes Figure 5 Improvement to .5.8.1-1: AF-based service parameter provisioning procedure for HPLMN in 3GPP TS 29.513. The following description is also referenced from 3GPP TS 29.513, wherein embodiments of this disclosure provide improvements in italics.

[0100] 1. In order to provide service-specific parameters to a UE, a group of UEs, or any UE (e.g., for URSP impact, for V2X, for A2X, for 5G ProSe, for ranging / SL (i.e., ranging and sidelink)), the AF invokes the Nnef_ServiceParameter_Create service operation to the NEF by sending an HTTP POST request to the "Service Parameter Subscription" resource.

[0101] To update existing service-specific parameters, AF invokes the Nnef_ServiceParameter_Update service operation by sending an HTTP PUT or PATCH request to the relevant "single service parameter subscription" resource.

[0102] To remove an existing service-specific parameter, AF invokes the Nnef_ServiceParameter_Delete service operation by sending an HTTP DELETE request to the relevant "single service parameter subscription" resource.

[0103] This request may include AF subscription information for reporting the results of the UE policy process.

[0104] Note 1: For further details on the Nnef_ServiceParameter_Create / Update / Delete service operations, see 3GPP TS 29.522

[24] .

[0105] The request can be expanded to include an extended definition of the UrspRuleRequest data type, as shown below. The "afReqId" attribute in the description is used to indicate the individual AF request section.

[0106] 2. Upon receiving an AF request, the NEF authorizes it and then performs a mapping of the information provided by the AF to the associated information required by the 5GC (e.g., GPSI to SUPI), as described in 3GPP TS 23.502[3]. The NEF may also support service-specific authorization as described in Clause 4.4.20 of 3GPP TS 29.522

[24] .

[0107] 3-4. When an Nnef_ServiceParameter_Create request is received, NEF calls the Nudr_DataRepository_Create service operation to store the received service parameters in the UDR by sending an HTTP PUT request to the "Single Service Parameter Data" resource, and the UDR replies with a "201 Created" response (if the request was successfully processed).

[0108] When an Nnef_ServiceParameter_Update request is received, NEF calls the Nudr_DataRepository_Update service operation to request modification of the service parameters in the UDR by sending an HTTPPUT / PATCH request to the relevant "single service parameter data" resource, and the UDR responds with a "200 OK" or "204 No Content" response (if the request is processed successfully).

[0109] When an Nnef_ServiceParameter_Delete request is received, NEF invokes the Nudr_DataRepository_Delete service operation to request the deletion of the service parameter from the UDR by sending an HTTP DELETE request to the relevant "single service parameter data" resource, and the UDR responds with a "204 No Content" response (if the request is processed successfully).

[0110] 5. NEF then sends an HTTP response message back to AF accordingly.

[0111] 6A. If the PCF has previously subscribed to changes in service parameters during the UE policy association establishment process (see Clause 5.6.1), then: 6a. UDR invokes the Nudr_DataRepository_Notify service operation on a PCF that has subscribed to a change in service parameters by sending an HTTP POST request to the associated callback URI “{notificationUri}”; 6b. The PCF sends a "204 No Content" response back to the UDR; 6c. The PCF checks whether the received service parameters (e.g., those related to URSP boot information) are authorized for use in SUPI. If at least some of them are authorized, steps 6d-6g are skipped; if only some are authorized, the PCF tracks which of them are authorized, which of them are authorized after being modified by the PCF, and which are not authorized. The PCF generates a mapping from the AF request portion to local authorization results / actions (i.e., "authorized", "modified", "unauthorized", etc.).

[0112] According to embodiments of this disclosure, the process can still be improved to be more detailed and clear when only some parameters are authorized.

[0113] 6d. If the received service parameter is unauthorized, PCF invokes the Npcf_EventExposure_Notify service operation to notify NEF of the unauthorized service parameter by sending an HTTP POST request to the callback URI "{notifUri}"; 6e. NEF sends a "204 No Content" response to PCF; 6f. When NEF receives Npcf_EventExposure_Notify, NEF executes the information mapping described in 3GPP TS 29.522

[24] and triggers the appropriate Nnef_ServiceParameter_Notify message; 6g. AF sends an HTTP response message back to NEF to confirm the notification; and 6h. The PCF may derive UE policies (e.g., URSP, V2X policy, A2X policy, 5G ProSe policy, ranging / SL policy) based on service parameters received from the UDR, UE subscription data, local operator policies, previously received requested V2X / 5G ProSe / A2X / ranging / SL policies from the AMF, and UE capabilities (e.g., V2X capabilities), and, where applicable, initiate a UE policy association modification process (see Clause 5.6.2.2) to deliver the UE policy to the UE.

[0114] 6B.

[0115] 6B1. During the UE policy association establishment process (see Clause 5.6.1), the PCF retrieves service parameters from the UDR by invoking the Nudr_DataRepository_Query service operation, authorizes the retrieved service parameters for the SUPI, and determines the UE policy (e.g., URSP, V2X policy, A2X policy, 5G ProSe policy, ranging / SL policy) based on the service parameters retrieved from the UDR, UE subscription data, local operator policies, and UE capabilities from the AMF (e.g., V2X capability, A2X capability, and / or 5G ProSe capability). If applicable, the PCF delivers the UE policy (including the determined V2XP, A2XP, 5GProSeP, and / or RSLPP) to the UE and the corresponding V2X N2 PC5, A2X N2 PC5, N2 ProSe PC5, and / or ranging / SL N2 PC5 policies to the NG-RAN. If the service parameters retrieved from the UDR are not authorized, steps 6d-6g are performed to notify the AF of the unauthorized service information.

[0116] 6B2. After registration, when the UE requests V2XP, A2XP, 5G ProSeP and / or RSLPP, the AMF sends a Namf_Communication_N1MessageNotify service operation with the requested V2XP, A2XP, 5G ProSeP and / or RSLPP to the PCF. The PCF retrieves service parameters from the UDR by invoking the Nudr_DataRepository_Query service operation, authorizes the retrieved service parameters for the SUPI, and determines the V2XP, A2XP, 5G ProSeP, and / or RSLPP based on the service parameters retrieved from the UDR, the received requested V2XP, A2XP, 5G ProSeP, and / or RSLPP, UE subscription data, local operator policies, and UE capabilities previously received from the AMF (e.g., V2X capabilities, A2X capabilities, ProSe capabilities, ranging / SL capabilities). It then delivers the V2XP, A2XP, and / or 5G ProSeP to the UE and the corresponding V2X N2 PC5, A2X N2 PC5, ProSe N2 PC5, and / or ranging / SL N2 PC5 policies to the NG-RAN. If the service parameters retrieved from the UDR are not authorized, steps 6d-6g occur to notify the AF of the fault.

[0117] Note 2: For further details regarding the Nudr_DataRepository_Create / Update / Delete / Notify service operations, see 3GPP TS 29.504

[27] and 3GPP TS 29.519

[12] .

[0118] 7. If the AF has subscribed to notifications regarding the results of UE policy delivery (provisioning / updating / removal) due to the provisioning of service-specific parameters, and the PCF has derived the corresponding UE policy, then the PCF uses the information received from the UE and the information regarding the requested service parameters determined in step 6, and invokes the Npcf_EventExposure_Notify service operation to notify the NEF of the results of the service parameters requested by the AF by sending an HTTP POST request to the callback URI "{notifUri}".

[0119] Note 3: The callback URI “{notifUri}” is used for implicit and explicit subscriptions as described in 3GPP TS 29.523

[49] . As described in 3GPP TS 29.519

[12] , the notification URI for an implicit subscription is retrieved from the UDR.

[0120] According to embodiments of this disclosure, new models / content for "results" can be provided, thus allowing for more detailed information. Notify AF. The new model / content for "Results" can also be considered an improvement to TS 29.523 and TS 29.522, as shown below. .

[0121] 8. NEF sends a "204 No Content" response back to PCF.

[0122] 9. When NEF receives Npcf_EventExposure_Notify, NEF performs the information mapping described in 3GPP TS 29.522

[24] and triggers the appropriate Nnef_ServiceParameter_Notify message.

[0123] 10. AF sends an HTTP response message back to NEF to confirm the notification.

[0124] Some data types in TS 29.522 can be extended to implement the above process. The extended portions are indicated by underscores. Such extensions will satisfy the need and possibility of providing partially successfully delivered URSP rules. For example, in Clause D.2.1.4 of TS 24.501, “The UE policy management procedure requested by the network was not accepted by the UE” specifies that if the UE cannot successfully execute all instructions included in the UE policy partial management list (IE), the UE reports the UPSI and indication of the failed instruction associated with the instruction that could not be successfully executed. Instructions not indicated as failed instructions are considered to have been successfully executed by the PCF. However, the exposure of the results of the UE policy provisioning procedure does not take this granularity into account, and newly provided / updated / removed URSP rules are either all reported as successfully delivered or all reported as unsuccessfully delivered. This solution can be improved by embodiments of this disclosure to expose the results of specific URSP rules where applicable.

[0125] This solution uses existing messages and information to send signaling back to the AF to improve network efficiency.

[0126] In addition, for the sake of simplicity, some parameters have been omitted here.

[0127] Table 5.11.2.1-1: Service Parameter API-Specific Data Types

[0128] Table 5.11.2.3.4-1: Definition of type UrspRuleRequest

[0129]

[0130] Table 5.11.2.3.6-1: Definition of type AfNotification

[0131]

[0132] Table XXX: Definition of type DetailedEventInfo

[0133] Table 5.11.2.4.3-1: Enumerating Events The Event enumeration represents event notifications related to the results of calls to service parameters provided by AF subscription.

[0134]

[0135]

[0136] Table XXX: Enumeration RequestedPolicyType The RequestedPolicyType enumeration represents the type of policy affected by AF for a request.

[0137]

[0138] Note: A complete list of RequestedPolicyType values ​​can be further improved.

[0139] Note: The OpenAPI update for the AfNotification_v2 feature can be further improved.

[0140] Table XXX: Enumeration Outcome The enumeration Outcome represents the detailed results of the request for the service parameters provided by AF.

[0141]

[0142] Table 5.11.3-1: Features used by the ServiceParameter API

[0143]

[0144] It should be noted that other specifications can also be extended accordingly, such as TS 29.523 (e.g., in the PcEvent data type, so that the above granularity can be reported from PCF to NEF first).

[0145] According to embodiments of this disclosure, the above solution will help the AF know whether its request has been satisfied by the network, which will improve the relevant contracts and SLAs between the operator and the application provider, while also reducing potential signaling between the AF and the network to determine the status of the UE policy.

[0146] It should be understood that the above embodiments are for illustrative purposes only and not for limitation. This disclosure may be practiced in ways other than those specifically set forth herein without departing from its essential characteristics. All changes to these embodiments without departing from the meaning of the appended claims and their equivalents are intended to be included herein.

[0147] Clause 1. An apparatus operating as a first network entity, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus operating as the first network entity to perform at least: sending a request for configuring one or more service parameters of a communication network, wherein the request includes an identifier for at least one of the one or more service parameters; receiving a response including a result of the configuration of the at least one service parameter; wherein the response includes the identifier indicating the type of the at least one service parameter and / or the at least one service parameter.

[0148] Clause 2. The apparatus according to Clause 1, wherein detailed event information comprises multiple entries, each entry being associated with a corresponding service parameter and including a corresponding result of the corresponding service parameter.

[0149] Clause 3. The apparatus according to Clause 2, wherein the corresponding result for each entry indicates at least one of the following: the corresponding service parameter is installed on the one or more terminal devices; the corresponding service parameter is modified by the Policy Control Function (PCF) and installed on the one or more terminal devices; the corresponding service parameter is rejected by the terminal device; or the corresponding service parameter is not authorized by the PCF.

[0150] Clause 4. The apparatus according to Clause 1, wherein the notification includes a notification-related identifier that links the notification to a subscribed notification.

[0151] Clause 5. The apparatus according to Clause 1, wherein the notification includes a failure reason indicating that one of the one or more terminal devices is temporarily unavailable.

[0152] Clause 6. The apparatus according to Clause 1, wherein for each of the service parameters, the policy control function (PCF) tracks whether the service parameter is authorized, modified, or not authorized by the PCF before attempting to deliver the policy.

[0153] Clause 7. The apparatus according to Clause 1, wherein the first network entity includes an application function (AF); wherein the request is for creating, updating, or deleting the one or more service parameters; and wherein the AF sends the request to a network opening function (NEF) and receives the response from the NEF.

[0154] Clause 8. An apparatus operating as a second network entity, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus operating as the second network entity to perform at least: receiving a request for configuring one or more service parameters of a communication network, wherein the request includes an identifier for at least one of the one or more service parameters; configuring the one or more service parameters; tracking, for the at least one service parameter, whether the at least one service parameter is authorized, modified, or not authorized by the second network entity; generating a response including a result of the configuration of the at least one service parameter; wherein the response includes an indication of the identifier of the at least one service parameter and / or the type of the at least one service parameter.

[0155] Clause 9. The apparatus according to Clause 8, wherein the at least one service parameter is associated with a policy to be delivered to one or more terminal devices; wherein the type of the at least one service parameter indicates the type of the policy; wherein configuring the one or more service parameters includes at least one of: verification of the at least one service parameter, modification of the at least one service parameter, or delivery of the policy; or wherein the second network entity obtains subscription information from a unified data store (UDR) for implicit subscription; and wherein when the policy is successfully, unsuccessfully, or partially successfully delivered to the one or more terminal devices, or when the at least one service parameter is not authorized by the second network entity, the second network entity generates a report or notification regarding the delivery of the policy.

[0156] Clause 10. The apparatus according to Clause 9, wherein the notification includes a notification-related identifier that links the notification to the subscription.

[0157] Clause 11. The apparatus according to Clause 8, wherein the network function service consumer is a network open function (NEF), and the NEF forwards the notification to the application function (AF).

[0158] Clause 12. The apparatus according to Clause 8, wherein the policy control function PCF maintains a mapping between an identifier for the at least one service parameter and a UE policy portion identifier UPSI, the UPSI being associated with a policy portion delivered to the one or more terminal devices.

[0159] Clause 13. The apparatus according to Clause 8, wherein a network function service consumer receives notifications from a home policy control function (H-PCF) to a visited policy control function (V-PCF), and the notifications include a delivery report, the delivery report including a mapping of event notifications, wherein the key of the mapping represents the associated application function.

[0160] Clause 14. A method performed by a policy control function (PCF) comprising: receiving a subscription to a policy control event notification related to service parameters; observing policy control events related to the delivery of a policy to one or more terminal devices; generating a notification including the result of the delivery of the policy; wherein the notification includes detailed event information indicating whether the delivery was successful, unsuccessful, or partially unsuccessful.

[0161] Clause 15. The method according to Clause 14, wherein the detailed event information comprises multiple entries, each associated with a corresponding service parameter and including the corresponding result of the corresponding service parameter.

[0162] Clause 16. The method according to Clause 15, wherein the corresponding result for each entry indicates at least one of the following: the corresponding service parameter is installed on the one or more terminal devices; the corresponding service parameter is modified by the Policy Control Function (PCF) and installed on the one or more terminal devices; the corresponding service parameter is rejected by the terminal device; or the corresponding service parameter is not authorized by the PCF.

[0163] Clause 17. A method performed by an apparatus operating as a first network entity, comprising: sending a request for configuring one or more service parameters of a communication network, wherein the request includes an identifier for at least one of the one or more service parameters; receiving a response including a result of the configuration of the at least one service parameter; wherein the response includes the identifier indicating the type of the at least one service parameter and / or the at least one service parameter.

[0164] Clause 18. The method according to Clause 17, wherein for each of the service parameters, the Policy Control Function (PCF) tracks whether the service parameter is authorized, modified, or not authorized by the PCF before attempting to deliver the policy.

[0165] Clause 19. The method according to Clause 17, wherein the subscription includes an identifier for at least one of the service parameters, and the notification includes the identifier indicating the at least one service parameter.

[0166] Clause 20. The method according to Clause 19, wherein the at least one service parameter is associated with a policy to be delivered to one or more terminal devices; wherein the second network entity maintains a mapping between the identifier for the at least one service parameter and a UE policy portion identifier UPSI associated with a policy portion to be delivered to the one or more terminal devices; and wherein the second network entity uses the mapping to determine the result for the at least one service parameter based on a UE policy delivery result received from the terminal device.

Claims

1. An apparatus for operating as a first network entity, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the means operating as the first network entity to perform at least the following: Send a request for configuring one or more service parameters of a communication network, wherein the request includes an identifier for at least one of the one or more service parameters; Receive a response that includes the configuration result of the at least one service parameter; The response includes an identifier indicating the type of the at least one service parameter and / or the at least one service parameter.

2. The apparatus according to claim 1, The detailed event information includes multiple entries, each of which is associated with a corresponding service parameter and includes the corresponding result of that service parameter.

3. The apparatus according to claim 2, The corresponding result for each entry indicates at least one of the following: The corresponding service parameters are installed on the one or more terminal devices; The corresponding service parameters are modified by the Policy Control Function (PCF) and installed on the one or more terminal devices; The corresponding service parameters were rejected by the terminal device; or The corresponding service parameters were not authorized by the PCF.

4. The apparatus according to claim 1, The notification includes a notification-related identifier that links the notification to the subscription.

5. The apparatus according to claim 1, The notification includes a reason for failure, which indicates that one of the terminal devices is temporarily unavailable.

6. The apparatus according to claim 1, For each of the service parameters, the Policy Control Function (PCF) tracks whether the service parameter is authorized, modified, or not authorized by the PCF before attempting to deliver the policy.

7. The apparatus according to claim 1, The first network entity includes application function AF; The request is used to create, update, or delete one or more service parameters; and The AF sends the request to the Network Open Function (NEF) and receives the response from the NEF.

8. An apparatus for operating as a second network entity, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the means operating as the second network entity to perform at least the following: Receive a request for configuring one or more service parameters of a communication network, wherein the request includes an identifier for at least one of the one or more service parameters; Configure one or more service parameters; For the at least one service parameter, track whether the at least one service parameter has been authorized, modified, or not authorized by the second network entity; Generate a response that includes the configuration result of the at least one of the service parameters; The response includes the identifier indicating the at least one service parameter and / or the type of the at least one service parameter.

9. The apparatus according to claim 8, The at least one service parameter is associated with a policy to be delivered to one or more terminal devices; The type of the at least one service parameter indicates the type of the policy; Configuring the one or more service parameters includes at least one of the following: verification of the at least one service parameter, modification of the at least one service parameter, or delivery of the policy; or wherein the second network entity obtains subscription information from the Unified Data Repository (UDR) for implicit subscription; and When the policy is successfully, unsuccessfully, or partially successfully delivered to the one or more terminal devices, or when at least one service parameter is not authorized by the second network entity, the second network entity generates a report or notification regarding the delivery of the policy.

10. The apparatus according to claim 9, The notification includes a notification-related identifier that links the notification to the subscription.