Method and system for managing user equipment (UE) policy control signaling in a network

Abstract

The present disclosure relates to a system (108) and a method (400) for managing User Equipment (UE) (104) policy control signaling in a network. The system (108) comprises a receiving unit (212) configured to receive at least one service request associated with one or more UE policy sessions from a Visited Policy Control Function (V-PCF), wherein the sessions are linked to a set of UEs (104). A transmitting unit (214) is configured to transmit a service response comprising a shared data Identifier (ID) related to UE policy data resources to the V-PCF, enabling notification of policy modifications. The processing engine (208) modifies the UE policy data resources based on received service requests. The transmitting unit (214) further sends an update response, allowing the V-PCF to apply modifications to the relevant UEs (104).

Description

METHOD AND SYSTEM FOR MANAGING USER EQUIPMENT (UE) POEICY CONTROE SIGNALING IN A NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.FIELD OF DISCLOSURE

[0002] The present disclosure relates generally to the field of telecommunication networks. The present disclosure relates to a system and a method for managing signaling transactions in a telecommunication network.DEFINITIONS

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used indicates otherwise.

[0004] The term ‘Access and Mobility Management Function (AMF)’ used herein in the specification refers to a network function in a telecommunication network (e.g., a Fifth Generation (5G) core network) that is responsible for managing access to the telecommunication network, session establishment, mobility management, and handling of a User Equipment (UE). The AMF handles signaling related to a UE registration, authentication, and mobility procedures.

[0005] The term ‘Policy Control Function (PCF)’ used herein in the specification refers to a network function in the 5G core network that provides policy decisions related to a UE behavior and resource usage. The PCF isresponsible for a policy enforcement and management, including a subscription management, a Quality of Service (QoS) control, and a network slicing.

[0006] The term ‘Visited Policy Control Function (VPCF)’ used herein in the specification refers to the PCF located in the network of a visited operator, responsible for handling policy decisions for a UE while it is roaming outside its home network. The VPCF interacts with the Home PCF (HPCF) to apply policy rules in the visited network.

[0007] The term ‘Home Policy Control Function (HPCF)’ used herein in the specification refers to the PCF located in the home network of the UE. The HPCF provides policy control and enforcement for the UE when it is in its home network and may interact with the VPCF for roaming scenarios.

[0008] The term ‘N2 interface’ used herein in the specification refers to an interface in the 5G network architecture that connects the access network (e.g., gNB) to the core network (e.g., AMF). It is used for signaling between the gNB and the AMF, including bearer setup and mobility management.

[0009] The term ‘N15 interface’ used herein in the specification refers to an interface for communication between the PCF and the AMF. The N15 interface is used for exchanging policy control information and data between these functions.

[0010] The term ‘N24 interface’ used herein in the specification refers to a standardized service-based interface that enables communication between a Home Policy Control Function (H-PCF) and a Visited Policy Control Function (V-PCF) in the roaming scenario.

[0011] The term ‘PC5 interface’ used herein in the specification refers to a reference to a specific interface within the 5G network architecture used for direct communication between the gNodeB (gNB) and the UE. The PC5 interface facilitates various types of communications, including V2X (Vehicle-to- Everything), ProSe (Proximity Services), and other direct UE-to-UE or UE-to- network interactions. It supports functions such as direct data transfer, proximity-based services, and enhanced connectivity features by allowing UEs to communicate with each other or with the network without necessarily routing the traffic through the core network.

[0012] The term ‘Unstructured Data Storage Function (UDSF)’ used herein in the specification refers to a network function in the 5G core network responsible for storing and retrieving unstructured data, which may include UE policy related data or shared data resources. The UDSF supports the PCF by enabling externalized and persistent storage of UE policy data, thereby allowing the PCF to maintain a stateless design while ensuring continuity of policy enforcement across sessions and instances. Additionally, the UDSF supports the AMF by storing and providing access to subscription-related information and shared policy attributes required during mobility management, session setup, or policy association..

[0013] The term ‘Shared data resources’ used herein in the specification refers to a collection of data that can be shared among multiple UEs, the PCF and the AMF.

[0014] The term ‘Shared data identifier (ID)’ used herein in the specification refers to a unique identifier assigned to a set of shared data resources within the network. The shared data ID is used to refer and manage a corresponding set of shared data resources across different network functions, such as the PCF and the AMF, or the HPCF and the VPCF.

[0015] The term ‘Shared data feature’ used herein in the specification refers to a feature that supports accessing and sharing of common data (i.e., the shared data resources) related to UE policy and charging control. The shared data feature is used to provide a consistent view of UE policy related data (i.e., the shared data resources) across different network functions, such as the AMF and the PCF.

[0016] The term ‘Shared data treatment’ used herein in the specification refers to a feature that includes a set of rules or instructions that defines how the shared data resources should be handled and processed when it is accessed bydifferent network functions, such as the AMF and the PCF. The shared data treatment feature includes shared data treatment instructions that specifies which shared data resources should take precedence when multiple shared data IDs are applicable.

[0017] The term ‘Get service operation’ used herein in the specification refers to a GET request that is sent by the AMF to the PCF (in non-roaming scenario) or by the VPCF to the HPCF (in roaming scenario) for retrieving the shared data resources from the PCF. The AMF can retrieve the shared data resources from the PCF for an individual shared data ID or multiple shared data IDs.

[0018] The term ‘Subscribe service operation’ used herein in the specification refers to a subscription request sent by the AMF to the PCF to receive notifications, i.e., a single notification message from the PCF about changes or updates to a set of shared data resources associated with a specific shared data ID.

[0019] The term ‘Modify subscription service operation’ used herein in the specification refers to a subscription request sent by the AMF to the PCF (in nonroaming scenario) or by the VPCF to the HPCF (in roaming scenario) to modify an existing subscription corresponding to the notifications. This includes changing subscription parameters such as a subscription duration.

[0020] The term ‘Unsubscribe service operation’ used herein in the specification refers to a request sent by the AMF to the PCF (in non-roaming scenario) or by the VPCF to the HPCF (in roaming scenario) to cancel or withdraw the existing subscription to the notifications. Once unsubscribed, the AMF will no longer receive the notifications about changes in the shared data resources from the PCF.

[0021] These definitions are in addition to those expressed in the art.BACKGROUND OF DISCLOSURE

[0022] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0023] The advent of Fifth Generation (5G) and subsequent next-generation network architectures has introduced significant advancements in telecommunications networks. Central to these architectures is the Policy Control Function (PCF), which is tasked with managing and provisioning policies governing network access and behavior of User Equipments (UEs). The PCF interacts with an Access and Mobility Management Function (AMF) to apply user equipment policies and ensure efficient session management.

[0024] Currently, the PCF may update policies based on external triggers such as notifications from a Unified Data Repository (UDR) or internal triggers such as policy counters activation. For instance, external triggers could involve service parameter changes or user subscription updates, while internal triggers might include adjustments in policy limits. Particularly, in scenarios involving bulk subscriber modifications or deletions, the existing methodology necessitates the PCF sending numerous update notifications individually to the AMF for each affected UE-policy session. For example, if policy updates need to be applied to thousands of subscribers simultaneously due to regulatory changes or service adjustments, each subscriber's policy session would generate an individual update notification. This approach results in significant signaling overhead between the PCF and the AMF, potentially causing network congestion, inefficiencies, delayed policy enforcement, and degraded overall network performance.

[0025] The issue becomes further exacerbated in roaming scenarios, involving multiple PCFs such as Home PCF (HPCF) and Visited PCF (VPCF). For example, when subscribers roam between networks operated by different serviceproviders, updates to subscriber policies must be communicated across these distinct PCFs. In such cases, the requirement to transmit a multitude of notifications across these entities further amplifies the signaling load, increasing latency, reducing the reliability of updates, and making the network operations less efficient and prone to performance degradation.

[0026] Existing technological implementations lack efficient mechanisms to aggregate notifications associated with bulk updates, resulting in redundant signaling, increased operational complexity, and slower reaction times to policy changes. For example, service disruptions may occur if policies are not updated promptly and accurately across the network, adversely affecting subscriber experiences. Such inefficiencies not only strain network resources but also limit the scalability and responsiveness of modem telecommunication networks, especially in rapidly evolving use-cases like mass deployment of loT devices, Vehicle-to- Everything (V2X) communications, and large-scale mobile subscriber migrations.

[0027] Therefore, there exists a technical need in the art for an improved system and method capable of optimizing signaling between PCF and AMF (in nonroaming scenario) or between the VPCF and the HPCF (in roaming scenario), particularly during bulk subscriber subscription modifications or deletions. Such improvements would ideally reduce network overhead, ensure timely and reliable policy updates, support efficient scaling, and significantly enhance the overall operational efficiency and subscriber experience in contemporary telecommunication networks.OBJECTIVES OF THE PRESENT DISCLOSURE

[0028] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.

[0029] An objective of the present disclosure is to provide a system and a method for managing signaling transactions in a telecommunication network.

[0030] Another objective of the present disclosure is to provide a system and a method for managing the signaling transactions during roaming scenarios by interacting between a Home PCF (HPCF) and a Visited PCF (VPCF).

[0031] Another objective of the present disclosure is to reduce signaling transactions (also referred as signaling traffic) between a Policy Control Function (PCF) and an Access and Mobility Management Function (AMF) in non-roaming scenario by allowing the PCF to send a single notification message to the AMF for multiple UE policy update sessions instead of individual message for each UE policy update session.

[0032] Another objective of the present disclosure is to improve performance of the telecommunication network by allowing the PCF to send the single notification message to the AMF for the multiple UE policy update sessions.

[0033] Another objective of the present disclosure is to optimize network resources (e.g., routers, switches, firewalls, etc.) utilization by reducing number of notification messages (i.e., a UE policy control update notify message) exchanged between the PCF and the AMF in non-roaming scenarios, and between the H-PCF and the V-PCF in roaming scenarios, thereby reducing the signaling overhead and processing load on each respective network function.

[0034] Another objective of the present disclosure is to provide a streamlined approach for managing the signaling transactions by integrating a shared data feature and a shared data treatment feature within the PCF and the AMF for non-roaming scenarios over the N15 interface, and within the H-PCF and the V-PCF for roaming scenarios over the N24 interface,

[0035] Another objective of the present disclosure is to enhance scalability of the telecommunication network by handling bulk subscriber modifications or deletion requests with a single notification message.

[0036] Another objective of the present disclosure is to provide new service operations, e.g., a GET service operation, a subscribe service operation, a modifysubscription service operation, and an unsubscribe service operation for UE policy control services to enhance the capability of the PCF and the AMF in managing UE policies more effectively.

[0037] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.SUMMARY

[0038] In an exemplary embodiment, a method for managing User Equipment policy control signaling in a network is described. The method comprises receiving, by a Home Policy Control Function, at least one service request corresponding to one or more User Equipment policy sessions from a Visited Policy Control Function, wherein the one or more User Equipment policy sessions are associated with a set of User Equipments. The method comprises transmitting, by the Home Policy Control Function, a service response comprising a shared data Identifier associated with a set of User Equipment policy data resources to the Visited Policy Control Function, in response to receiving the at least one service request, wherein the shared data Identifier is used for notifying the Visited Policy Control Function regarding modification of the set of User Equipment policy data resources associated with the one or more User Equipment policy sessions. The method comprises modifying, by the Home Policy Control Function, the set of User Equipment policy data resources associated with the shared data Identifier based on the at least one service request. The method comprises sending, by the Home Policy Control Function, an update response corresponding to the modification in the set of User Equipment policy data resources associated with the shared data Identifier to the Visited Policy Control Function, wherein the Visited Policy Control Function is configured to apply the modification in the set of User Equipment policy data resources for the set of User Equipments mapped to the shared data Identifier, based on the update response.

[0039] In an embodiment, the Home Policy Control Function is located in a home network and the Visited Policy Control Function is located in a visited network to manage the User Equipment policy control signaling.

[0040] In an embodiment, the at least one service request comprises a User Equipment policy control create request, a User Equipment policy control update request, a User Equipment policy control delete request, and a User Equipment policy control modify request.

[0041] In an embodiment, each User Equipment policy session is associated with at least one User Equipment policy, and the at least one User Equipment policy comprises one or more of an Access Network Discovery and Selection Policy, a User Equipment Route Selection Policy, a Vehicle-to-Everything Policy, an Aircraft-to-Everything Policy, a Proximity Services Policy, and a Ranging and Sidelink Positioning Policy.

[0042] In an embodiment, the shared data Identifier is mapped to the set of User Equipment policy data resources and the set of User Equipments.

[0043] In an embodiment, transmitting the service response further comprises performing, by the Home Policy Control Function, a check to determine whether the Visited Policy Control Function is configured with a shared data feature and a shared data treatment feature, wherein the configuration enables the V-PCF to apply the modification to the set of User Equipment policy data resources for the set of User Equipments based on the shared data Identifier.

[0044] In an embodiment, the Visited Policy Control Function configured with the shared data feature and the shared data treatment feature communicates with the Home Policy Control Function over an N24 interface.

[0045] In an embodiment, modifying the set of User Equipment policy data resources comprises updating, by the Home Policy Control Function, one or more policy control request triggers associated with the shared data Identifier, in response to the at least one service request.

[0046] In an exemplary embodiment, a system for managing User Equipment policy control signaling in a network is disclosed. The system comprises a receiving unit configured to receive, at a Home Policy Control Function, at least one service request corresponding to one or more User Equipment policy sessions from a Visited Policy Control Function, wherein the one or more User Equipment policy sessions are associated with a set of User Equipments. The system comprises a transmitting unit configured to transmit, from the Home Policy Control Function, a service response comprising a shared data Identifier associated with a set of User Equipment policy data resources to the Visited Policy Control Function in response to receiving the at least one service request, wherein the shared data Identifier is configured for notifying the Visited Policy Control Function regarding modification of the set of User Equipment policy data resources associated with the one or more User Equipment policy sessions. The system comprises a processing engine configured to modify, at the Home Policy Control Function, the set of User Equipment policy data resources associated with the shared data Identifier based on the at least one service request. The transmitting unit is further configured to send, from the Home Policy Control Function, an update response corresponding to the modification in the set of User Equipment policy data resources associated with the shared data Identifier to the Visited Policy Control Function, wherein the Visited Policy Control Function is configured to apply the modification in the set of User Equipment policy data resources for the set of User Equipments mapped to the shared data Identifier, based on the update response.

[0047] In yet another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing User Equipment policy control signaling in a network. The method comprises receiving, by a Home Policy Control Function, at least one service request corresponding to one or more User Equipment policy sessions from a Visited Policy Control Function, wherein the one or more User Equipment policy sessions areassociated with a set of User Equipments. The method comprises transmitting, by the Home Policy Control Function, a service response comprising a shared data Identifier associated with a set of User Equipment policy data resources to the Visited Policy Control Function, in response to receiving the at least one service request, wherein the shared data Identifier is used for notifying the Visited Policy Control Function regarding modification of the set of User Equipment policy data resources associated with the one or more User Equipment policy sessions. The method comprises modifying, by the Home Policy Control Function, the set of User Equipment policy data resources associated with the shared data Identifier based on the at least one service request. The method comprises sending, by the Home Policy Control Function, an update response corresponding to the modification in the set of User Equipment policy data resources associated with the shared data Identifier to the Visited Policy Control Function, wherein the Visited Policy Control Function is configured to apply the modification in the set of User Equipment policy data resources for the set of User Equipments mapped to the shared data Identifier, based on the update response.BRIEF DESCRIPTION OF DRAWINGS

[0048] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0049] FIG. 1 illustrates an exemplary network architecture of a system for managing signaling transactions in a telecommunication network, in accordance with an embodiment of the present disclosure.

[0050] FIG. 2 illustrates a block diagram of the system, in accordance with an embodiment of the present disclosure.

[0051] FIG. 3 illustrates an exemplary flow diagram of a method for managing the signaling transactions in the telecommunication network, in accordance with an embodiment of the present disclosure.

[0052] FIG. 4 is a method flow diagram for managing the signaling transactions in the telecommunication network, in accordance with an embodiment of the present disclosure.

[0053] FIG. 5 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented.

[0054] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102-1, 102-2 - Users104-1, 104-2 - User equipments112-1, 112-2 - Base stations106 - Network108 - System202 - Processors204 - Memory206 - Interface(s)208 - Processing engine209 - Other module(s)210 - Database212- Receiving Unit214- Transmitting Unit300 - Flow diagram400 - Method flow diagram500 - Computer system510 - External storage device520 - Bus530 - Main memory540 - Read only memory550 - Mass storage device560 - Communication port(s)570 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0055] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may notaddress all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

[0056] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0057] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0058] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0059] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be constmed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

[0060] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0061] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0062] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment, as well as other embodiments of the disclosure, will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0063] In conventional technologies, a Policy Control Function (PCF) plays a crucial role in managing and delivering user equipment (UE) policies within a telecommunication network, including advanced networks such as Fifth Generation (5G) networks. The PCF is tasked with provisioning various UE policies, such as Access Network Discovery and Selection Policy (ANDSP), UE Route Selection Policy (URSP), Vehicle-to-Everything Policy (V2XP), Aircraft-to-Everything Policy (A2XP), 5G ProSe Policy (ProSeP), and Ranging and Sidelink Positioning Policy (RSLPP) to the UE via the Access and Mobility Management Function (AMF). This process ensures that the policies determined by the PCF are appropriately applied to control access and mobility aspects for users across the network.

[0064] Conventionally, a Visited PCF (VPCF) and a Home PCF (HPCF) are also involved in updating UE policies based on a range of triggers. These triggers can be external, such as notifications received from a Unified Data Repository (UDR) about updated service parameter data, or internal, like the activation of a policy counter through the Network Charging Function (NCHF) spending limit control service. In roaming scenarios, the HPCF may also update various policies, including those related to the V2X, A2X, ProSe, and Ranging / SL communications, based on feature support.

[0065] When the PCF decides to update the UE policies based on these external and internal triggers, the PCF sends individual update notification messages to the AMF for each UE-policy session. When multiple UE-policy sessions are affected by the same changes, the PCF issues separate Update Notify service operations for each session. However, this existing approach can lead to a significant increase in signaling traffic between the PCF and AMF, resulting in a traffic surge that can disrupt network performance and efficiency. Similarly, this issue extends to the H-PCF and V-PCF during roaming scenarios, where the process of sending multiple notifications can create additional signaling overhead.

[0066] The existing approach of handling UE policy updates can become cumbersome and inefficient, especially in scenarios involving bulk subscriber modifications or deletions. When the PCF needs to manage numerous UE policy sessions simultaneously, the PCF sends numerous UE policies update notifications to the AMF. This results in increase in signaling traffic between the PCF and the AMF, potentially leading to a traffic surge in the telecommunication network. Such traffic surges can impact network performance and efficiency, highlighting a need for careful management and optimization of the UE policies update processes to avoid overloading network resources.

[0067] To address the challenges associated with the above-mentioned problems, the present disclosure provides a solution in the way that the PCF handles bulk subscriber modifications or deletions. Instead of sending multiple individual notifications for each affected UE-policy session, the PCF sends a single notification message to the AMF (in a non-roaming scenario). This single notification, which is sent to the AMF, contains comprehensive information about the modifications required.

[0068] Upon receiving the single notification, the AMF processes the update and applies the changes to all relevant UE-policy sessions associated with the provided information. This approach significantly reduces the number of signaling transactions between the PCF and AMF, mitigating the risk of signalingtraffic surges and enhancing overall network performance. By streamlining the update process, the solution ensures that network resources are used more efficiently, thereby improving the responsiveness and stability of the telecommunication network.

[0069] Similarly, in a roaming scenario, the Home Policy Control Function (H-PCF) sends a single notification message to the Visited Policy Control Function (V-PCF) over the N24 interface. This notification includes information about the modifications to the set of UE policy data resources associated with one or more UE policy sessions that reference a shared data identifier (ID). The V-PCF then applies these modifications to the corresponding UE policy sessions in the visited network. By consolidating notifications in this manner, the signaling load between the H-PCF and V-PCF is reduced, synchronization between home and visited networks is maintained, and consistency of UE policy enforcement across roaming scenarios is ensured.

[0070] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0071] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 5.

[0072] FIG. 1 illustrates an exemplary network architecture (100) of a system (108) for managing signaling transactions in a telecommunication network, in accordance with an embodiment of the present disclosure.

[0073] As illustrated in FIG. 1, the network architecture (100) may include one or more user equipment (UE) (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2. . . 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as the UE (104). Although only three UE (104) are depictedin FIG. 1 , however, any number of the UE ( 104) may be included without departing from the scope of the ongoing description.

[0074] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but not limited to, intelligent, multi-sensing, network-connected devices, that may integrate seamlessly with each other and / or with a central server or a cloudcomputing system or any other device that is network-connected.

[0075] Additionally, in some embodiments, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone,a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0076] Referring to FIG. 1, the UE (104) may communicate with a system (108) through a network (telecommunication network) (106) for sending or receiving various types of data. In an embodiment, the network (106) may include at least one ofa 5G network, 6G network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0077] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0078] In an embodiment, the UE (104) is communicatively coupled with the network (106). The network (106) may receive a connection request from theUE (104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request.

[0079] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0080] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) configured for managing User Equipment (UE) (104) policy control signaling in a network, in accordance with an embodiment of the present disclosure.

[0081] The system (108) comprises a plurality of components configured to coordinate and execute UE policy control signaling tasks across home and visited networks. The components include, but may not be limited to, one or more processor(s) (202), a memory (204), interface(s) (206), a processing engine (208), a database (210), a receiving unit (212), and a transmitting unit (214).

[0082] Referring to FIG. 2, in an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer- readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service.

[0083] The memory (204) comprises non-transitory computer-readable storage media, including volatile memory such as random-access memory (RAM) and non-volatile memory such as flash memory, read-only memory (ROM), or erasable programmable read-only memory (EPROM). The memory (204) is configured to store executable instructions, policy data, session information, shared data identifiers (IDs), and related signaling parameters that enable the system to perform policy control signaling for the UE (104).

[0084] The interface(s) (206) are configured to enable input and output communication between internal components and external entities. The interface(s) (206) may include hardware ports, network communication interfaces, or interprocess communication buses. These interfaces enable data exchange among components such as the processing engine (208), receiving unit (212), transmitting unit (214), and external functions such as the Visited Policy Control Function (V- PCF) and the Home Policy Control Function (H-PCF).

[0085] In an embodiment, the system (108) may include a processing engine (208) that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processorexecutable instructions stored on a non-transitory machine -readable storage medium and the hardware for the processing engine (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (208). In such examples, the system may comprise the machine- readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine -readable storage medium may be separate but accessible to the system and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry.

[0086] In one implementation, the receiving unit (212) of the system (108), functionally implemented at the H-PCF, is configured to receive at least one service request from the V -PCF. The at least one service request corresponds to one or more UE policy sessions and may comprise a UE policy control create request, a UE policy control update request, a UE policy control delete request, or a UE policy control modify request. The at least one service request may include, for example, a UE policy control create request, a UE policy control update request, a UE policy control delete request, or a UE policy control modify request, each pertaining to initiation, adjustment, termination, or refinement of policy sessions associated with a set of UEs (104).

[0087] The service requests are generated as part of the UE policy control procedures when the V-PCF determines that policy adjustments, session initialization, deletion, or modifications are required for one or more UEs (104) operating under its domain. These requests are used to manage policies applicable to one or more UEs (104) located in the visited network. Each request type triggers specific operations: for instance, a UE policy control create request initiates the establishment of a new policy session for the UE (104), defining parameters such as service access rules, network behavior, and resource prioritization. A UE policy control update request allows modification of existing policy attributes in response to changing service requirements, network conditions, or user mobility. A delete request terminates the session and removes associated policy bindings. A modify request may selectively change session parameters without fully recreating the policy context. For example, a UE policy control create request may be generated when a UE (104) registers with the network, prompting creation of a new session with associated policy parameters. Such policy parameters may include slice preferences, data flow descriptions, Quality of Service (QoS) rules, and access restrictions. In some embodiments, these requests may correspond to a Protocol Data Unit (PDU) session, which manages user data and network signaling within the 5G architecture. A PDU session is a logical construct that facilitates packetbased connectivity between the UE (104) and the Data Network (DN), and isgoverned by the Session Management Function (SMF) in coordination with the PCF. The policy requests transmitted by the V-PCF to the H-PCF enable consistent enforcement of UE-specific rules across both home and visited network environments, thereby supporting seamless roaming, interoperability, and subscriber policy continuity Service-Based Architecture (SBA) procedures.

[0088] In an embodiment, the Home Policy Control Function (H-PCF) is located in a home network, and the Visited Policy Control Function (V-PCF) is located in a visited network. The H-PCF and V-PCF are configured to jointly manage the UE (104) policy control signaling such that policy enforcement and subscription data modifications occur within the home network under the control of the H-PCF, while the V-PCF coordinates session management and policy applicability within the visited network during roaming conditions. The UE policy control signaling refers to the exchange of signaling messages between network functions, specifically between a Policy Control Function (PCF) and a User Equipment (UE), that are used to establish, modify, update, or delete policy rules applicable to a particular UE. These policies govern various aspects of the UE’s behavior in the network, such as traffic routing, network access selection, service prioritization, roaming preferences, or proximity-based communication.

[0089] In the context of a roaming scenario, the Home PCF (H-PCF) is located in the home network to retain control over the subscriber’s policy data and logic, while the Visited PCF (V-PCF) is located in the visited network and acts as a mediator to enforce those policies locally. The UE policy control signaling in such a scenario involves the V-PCF transmitting service requests (e.g., policy control create / update / delete / modify requests) to the H-PCF over a standardized interface (e.g., N24), and the H-PCF responding with policy decisions or shared data identifiers to ensure that consistent policy control is maintained across networks, without compromising user experience, QoS, or operator policy rules.

[0090] The transmitting unit (214), also functionally implemented at the H- PCF, is configured to transmit a service response to the V-PCF, in response toreceiving the service request. The service response comprises a shared data Identifier (ID), which is associated with a set of UE policy data resources.

[0091] The shared data ID provides an abstract reference to a logically grouped set of reusable policy control data that may be mapped to multiple UEs (104). In one example, the shared data ID ‘SI’ may be associated with a policy profile comprising a Vehicle-to-Everything Policy (V2XP), a UE Route Selection Policy (URSP), and a Proximity Services Policy (ProSeP), applicable to all UEs (104) belonging to a vehicle fleet operating within the visited network. In another example, a shared data ID ‘S2’ may reference a combination of Access Network Discovery and Selection Policy (ANDSP) and Ranging and Sidelink Positioning Policy (RSLPP) configured for a group of UEs (104) deployed in a smart manufacturing environment.

[0092] In one example, the shared data ID maps to a policy bundle comprising a Vehicle-to-Everything Policy (V2XP), a UE Route Selection Policy (URSP), and a Proximity Services Policy (ProSeP), which is applicable to all UEs ( 104) belonging to a vehicle fleet in the visited network. Additional policy resources may include Access Network Discovery and Selection Policy (ANDSP), Aircraft- to-Everything Policy (A2XP), Ranging and Sidelink Positioning Policy (RSLPP), UE Aggregate Maximum Bit Rate (AMBR) values, Radio Frequency Slice Profile (RFSP) indices, service area restrictions, Public Land Mobile Network (PLMN) identifiers, and subscription-specific parameters.

[0093] The Access Network Discovery and Selection Policy (ANDSP) defines rules and preferences that guide the User Equipment (UE) in selecting or discovering suitable access networks when multiple options (e.g., Wi-Fi, 4G, 5G) are available. This policy may include criteria such as network availability, signal strength, operator-defined priorities, or subscription constraints, thereby ensuring optimal network selection based on context, location, or device capability. The Vehicle-to-Everything Policy (V2XP) defines network behavior and data communication rules specific to vehicular use cases, including communication withother vehicles (V2V), infrastructure (V2I), pedestrians (V2P), and networks (V2N). This policy ensures safe and efficient transportation by enabling low-latency and high-reliability exchange of critical data such as positioning, speed, braking, and navigation between road entities.

[0094] The Aircraft-to-Everything Policy (A2XP) governs policy control and communication parameters for aerial platforms such as Unmanned Aerial Vehicles (UAVs) or aircraft. It supports network-based coordination for air traffic control, situational awareness, or air-to-ground data exchange, addressing aspects like altitude-based coverage, mobility management, and flight corridor communication requirements. The Proximity Services Policy (ProSeP) defines how UEs may engage in direct device-to-device (D2D) communication when in close physical proximity, without routing traffic through the core network. This is particularly useful for public safety, mission-critical services, or local content sharing. The policy controls parameters such as proximity detection thresholds, service authorization, and radio resource usage for D2D links. The Ranging and Sidelink Positioning Policy (RSLPP) defines policies related to the use of sidelink communication channels for positioning or distance measurement between UEs. This may be employed in scenarios such as collaborative navigation, indoor localization, or autonomous operations, where precise relative location information is derived using signal measurements like Time-of-Flight (ToF) or Angle-of- Arrival (AoA) across direct wireless links.

[0095] The transmitting unit (214) is configured to ensure that the shared data ID is conveyed in response to the service request only when the V-PCF supports both the shared data and shared data treatment features, as determined by a feature support check at runtime. The shared data ID is mapped to both the set of UE policy data resources and the set of UEs (104) utilizing those policies. The shared data ID serves as a reference key or pointer that links a predefined group of policy data elements to one or more User Equipments (UEs) (104) that are governed by those policy rules. In one example, a shared data ID, designated as SI, may be associated with a policy bundle including, for instance, a UE Route Selection Policy(URSP), a Vehicle-to-Everything Policy (V2XP), and a Proximity Services Policy (ProSeP). These UE policy data resources collectively define traffic routing preferences, vehicular communication protocols, and proximity-based interaction constraints. The shared data ID SI is stored in a data structure (e.g., a database entry, a JSON object, or a policy table) and acts as a unique handle to retrieve the associated policy set. This shared data ID S 1 is then mapped to a specific set of UEs (104), for example, all UEs provisioned for a logistics fleet operating within a defined geographical area. Each UE (104) in this group may have its policy session dynamically or statically linked to the shared data ID SI, enabling policy provisioning to be performed uniformly across the group.

[0096] This mapping allows for efficient updating and notification of policy changes affecting multiple UE policy sessions simultaneously. For example, a group of industrial loT devices deployed in a factory may share a common URSP policy. A change to this policy is updated under a single shared data ID and propagated to all associated UEs (104).

[0097] In an embodiment, the service response transmitted by the Home Policy Control Function (H-PCF) includes a shared data Identifier (ID) that is associated with a logically grouped set of UE policy data resources applicable to one or more UE policy sessions. Each UE policy session represents a binding between a User Equipment (UE) and a defined policy framework governing its behavior in the network. Examples of UE policy data resources associated with such UE policy sessions may include an Access Network Discovery and Selection Policy (ANDSP), which allows the UE to select appropriate access networks based on operator-defined rules; a UE Route Selection Policy (URSP), which directs traffic flows through specific data network names or network slices; and a Vehicle- to-Everything Policy (V2XP), enabling vehicular UEs to communicate with other vehicles, infrastructure, pedestrians, and networks in an intelligent transport ecosystem. Additional examples of such resources include an Aircraft-to- Everything Policy (A2XP) for unmanned aerial systems, a Proximity Services Policy (ProSeP) supporting direct device-to -device communication, and a Rangingand Sidelink Positioning Policy (RSLPP) for enabling UE-based positioning services. These policy data resources are typically instantiated per session and govern UE-specific behaviors such as access control, traffic routing, quality of service enforcement, network selection, and session continuity. By referencing these policy resources under a common shared data ID, the H-PCF enables efficient propagation and synchronization of policy updates across multiple UE policy sessions, while minimizing redundant signaling with the Visited Policy Control Function (V-PCF).

[0098] The processing engine (208) is configured to modify, at the H-PCF, the set of UE policy data resources associated with the shared data ID based on at least one received service request. The modification is based on the nature and content of the received service request. In various embodiments, the service request may be a UE policy control create, update, delete, or modify request, each necessitating an update to existing policy data. For instance, a create request may require the instantiation of a new policy bundle mapped to the shared data ID; an update request may demand alteration of specific policy parameters (e.g., changes in Access Network Discovery and Selection Policy (ANDSP) thresholds, UE Route Selection Policy (URSP) routing rules, or Ranging and Sidelink Positioning Policy (RSLPP) configurations); a delete request may involve dissociating one or more obsolete data fields from the shared data group; while a modify request may include dynamic adjustments based on mobility events, service area changes, or slice availability. The processing engine ensures that the modified policy data remains compliant with network-wide configurations and consistent across all UE policy sessions mapped to the same shared data ID. Upon completion of the modification, the H-PCF generates and transmits an update response to the V-PCF for application across the corresponding UE group.

[0099] Additionally, the processing engine (208) is configured to update one or more policy control request conditions associated with the shared data ID. These conditions may include variations in access technology, session characteristics, slice selection parameters, or signaling path information. Theprocessing engine (208) is further configured to manage signaling transactions between network functions, including between the Access and Mobility Function (AMF) and the Policy Control Function (PCF) in non-roaming scenarios, and between the Home PCF (H-PCF) and the Visited PCF (V-PCF) in roaming scenarios. Each signaling transaction follows a sequence involving reception of a service request, generation of a response with a shared data ID, modification of the associated UE policy data resources, and transmission of an update response.

[0100] In one embodiment, the processing engine (208) is configured to update one or more policy control request triggers associated with the shared data Identifier (ID), in response to the at least one service request received from the Visited Policy Control Function (V-PCF). In the context of the present disclosure, the policy control request triggers refer to a set of predefined conditions or operational parameters that, when met or satisfied, result in the initiation of a policy re-evaluation or enforcement action for the User Equipment (UE) (104). These triggers are associated with the shared data ID such that any modification performed to the policy control parameters mapped to the shared data ID applies uniformly to all UEs (104) linked to the same ID. The policy control request triggers may include, for example, a location change (LOC CH), wherein the trigger activates when a User Equipment (UE) (104) moves across defined geographical boundaries; a Public Land Mobile Network change (PLMN_CH), which is activated when the UE (104) registers with a different operator’s network, particularly in a roaming context; and an access type change (ACCESS TYPE CH), which is activated when the UE (104) switches between different radio access technologies, such as from 5G NR to LTE or from cellular to Wi-Fi.

[0101] In one embodiment, the policy control request triggers may include conditions based on the access network type, such as E-UTRAN, NR (New Radio), or WLAN, where the applicable UE policy behavior may vary depending on whether the UE (104) is connected to a cellular network . In such scenarios, a change in the access technology may invoke the trigger to re-evaluate the UE policy associated with that shared data ID.

[0102] The transmitting unit (214) is further configured to perform a check to determine whether the V-PCF is configured with a shared data feature and a shared data treatment feature. These configurations enables the V-PCF to correctly interpret and apply the shared data ID-based updates. When the V-PCF is confirmed to be configured with both the features, the V-PCF is enabled to correctly interpret the shared data ID received in the service response, retrieve the associated UE policy data resources, and apply any subsequent modifications sent via update responses from the H-PCF. If the V-PCF supports these features, it communicates with the H-PCF over an N24 interface, which is defined for policy control information exchange in roaming scenarios.

[0103] If the V-PCF receives the shared data ID and is unaware of the associated policy data resources, it may send a get request to the H-PCF. The get request includes query parameters such as the shared data ID, a list of known shared data IDs, or identifiers of UEs (104) requiring the data. The H-PCF, through the processing engine (208), responds with the complete set of policy data resources associated with the shared data ID. Upon receiving this data, the V-PCF updates its internal database or cache and subscribes to any future modifications related to that shared data ID.

[0104] Upon completing the update to the UE policy data resources, the transmitting unit (214) is configured to send from the H-PCF, an update response corresponding to the modification in the set of UE policy data resources associated with the shared data ID, to the V-PCF. The update response includes details of the modification in the set of UE policy data resources associated with the shared data ID. Particularly, the update response may include one or more of: updated policy rules or parameters, revised UE policy trigger conditions (e.g., location change (LOC_CH), PLMN change (PLMN_CH), access type change (ACCESS TYPE CH)), updated mappings of the shared data ID to UEs (104), metadata indicating the version or timestamp of the modified data, and references to the affected policy control sessions. The update response serves as a notification mechanism to ensure that the V-PCF applies the updated set of UE policy dataresources to the set of UEs (104) associated with the shared data ID, thereby maintaining synchronization and consistency of policy enforcement in the visited network environment. The set of UEs (104) mapped to the shared data ID refers to a plurality of User Equipment (UEs) (104) that are logically associated with a common identifier, i.e., the shared data ID, indicating that the same set ofUE policy data resources is applicable to them. The mapping enables a centralized and efficient management of policy updates, whereby a single update to the policy data associated with the shared data ID can be propagated to all UEs (104) mapped to it, without the need for issuing separate update commands for each individual UE.

[0105] In an example, a set of UEs (104) is deployed within a smart transportation system, such as a fleet of autonomous vehicles operating within a metropolitan area. These UEs (104) may share a common set of policies, such as a Vehicle-to-Everything Policy (V2XP) for communication with road infrastructure, a UE Route Selection Policy (URSP) optimized for dynamic route updates, and a Proximity Services Policy (ProSeP) for vehicle platooning. These policies are collectively identified and grouped under a shared data ID (e.g., ID Sl). When an update is made to any of these policies, such as changing V2X communication parameters due to a security patch or updated routing rules, the H-PCF sends a single update response referencing the shared data ID (ID Sl), and the V-PCF applies this modification to the entire set of UEs (104) mapped to ID Sl . This mapping eliminates redundancy, reduces signaling overhead, and ensures policy uniformity across the targeted group of UEs.

[0106] The V-PCF is configured to apply these modifications for the set of UEs (104) mapped to the shared data ID. For example, if the URSP policy is updated to redirect traffic from a cellular to a Wi-Fi network for a group of UEs (104), the update response enables the V-PCF to enforce this policy for each mapped UE (104). In some scenarios, the update response may be sent as a single notification message for multiple policy sessions.

[0107] The database (210) is configured to store information such as existing shared data IDs, the UE policy data resources associated with each shared data ID, the mapping between shared data IDs and UEs (104), and historical signaling events. This repository enables efficient retrieval and processing of policy data necessary for H-PCF operations.

[0108] Although FIG. 2 illustrates an exemplary configuration of the system(108), alternate embodiments may include additional or fewer components. Components may also be integrated or restructured while preserving the described functional behavior. For example, the database (210) may be implemented as a distributed data store accessed over the cloud, and the processing engine (208) may be integrated into the receiving unit (212) or transmitting unit (214) in a virtualized deployment.

[0109] The system (108), through its constituent components, is capable of executing the claimed method steps in a coordinated manner. Each component, including the receiving unit (212), transmitting unit (214), processing engine (208), and database (210), directly supports the literal features of the claims for managing UE (104) policy control signaling in a home and visited network architecture.

[0110] In a working deployment scenario, a group of unmanned aerial vehicles (UAVs), each representing a UE (104), operate across multiple geographic regions with roaming support. When a UAV enters a visited network, the Visited Policy Control Function (V-PCF) transmits a UE policy control create request to the H-PCF via the receiving unit (212). This request is associated with a UE policy session corresponding to the UAV. The processing engine (208) receives the request and determines that the UAV shares common Aircraft-to-Everything Policy (A2XP) parameters with a fleet operating under the same mission objective. These parameters are mapped to a shared data ID. The transmitting unit (214) then sends a service response to the V-PCF, including the shared data ID referencing the A2XP parameters.

[0111] Upon a mission update requiring altitude or airspace compliance changes, the processing engine (208) modifies the A2XP parameters associated with the shared data ID. The transmitting unit (214) sends an update response to the V-PCF, which then applies the updated A2XP policy to all UAVs mapped to the shared data ID. This enables seamless policy updates across the entire fleet without individually updating each policy session.

[0112] FIG. 3 illustrates an exemplary flow diagram (300) of a method for managing the signaling transactions in the telecommunication network, in accordance with an embodiment of the present disclosure. Examples of the telecommunication network may include, a Fourth Generation (4G) network, the 5G network, a Sixth-Generation network (6G) network, and the like.

[0113] In FIG. 3, a communication flow between an AMF, in non-roaming scenarios, or a VPCF (302), in roaming scenarios, and a PCF, in non-roaming scenarios, or a HPCF (304), in roaming scenarios for managing signaling transactions is depicted. In order to manage the signaling transactions or to reduce high signaling transactions between the AMF or the VPCF (302) (hereafter referred to as the AMF (302)) and the PCF or the HPCF (304) (hereafter referred to as the PCF (304)), the AMF or the VPCF (302) and the AMF (302) and PCF (304) are configured to support the shared data feature and the shared data treatment feature. The shared data feature refers to a feature that allows the AMF (302) and the PCF (304) to access and share common data (i.e., shared data resources) related to UE policy and charging control. The shared data feature is used to provide a consistent view of UE policy related data (i.e., shared data resources) across the AMF (302) and the PCF (304) or across the VPCF and HPCF in the roaming scenario. In other words, the shared data feature ensures that the same set of UE policy related data is available for decision-making and enforcement across different network functions (e.g., the AMF (302) and the PCF (304)) in the telecommunication network. For example, a V-PCF configured with the shared data feature can receive a shared data ID, such as S2, from the H-PCF and correctly interpret that S2 maps to a bundle of policies including an Access Network Discovery and Selection Policy (ANDSP)and a Ranging and Sidelink Positioning Policy (RSLPP). Without this feature, the V-PCF would lack the ability to resolve the meaning of S2 and would instead require explicit transmission of all individual policies.

[0114] The shared data treatment feature is a feature that defines how the shared data resources should be handled and processed when it is accessed by the different network functions, such as the AMF (302) and the PCF (304).

[0115] The shared data treatment feature includes shared data treatment instructions that specify which shared data resources should take precedence when multiple shared data IDs are applicable. The shared data resources represent a collection of data that can be shared by multiple UEs. For example, the policy control request triggers, the V2X policy, the A2X Policy, the ProSe policy, the RSLPP policy, and the like.

[0116] Initially, at step 306, the AMF (302) sends a NPCF_UE policy control_create request to the PCF (304). The NPCF_UE policy control_create request may correspond to the at least one service request. Other examples of the at least one service request may include aNPCF_UE policy control_update request, a NPCF UE policy control delete request, and a NPCF UE policy control modify request, and the like. The AMF (302) sends the NPCF_UE policy control_create request to perform policy control actions related to UE policies management. Upon receiving the NPCF_UE policy control_create request, the PCF (304) may check whether the shared data feature and the shared data treatment feature is supported by the AMF (302). Based on performing the check, when the shared data feature and the shared data treatment feature are supported by the AMF (302), at step 308, the PCF (304) is configured to send a Npcf_UE Policy Control_create response, i.e., the service response to the AMF (302). The Npcf_UE Policy Control_create response includes a shared policy control request triggers data identifier (ID = SI), which is a unique reference to a set of predefined event triggers used to activate policy enforcement or re-evaluation for a group of UEs. The shared policy control request triggers data ID = SI includes event triggers, such as a location change(LOC CH), a Public Land Mobile Network (PLMN) change (PLMN), and an access type change (ACCESS_TYPE _CH) for a set of UEs (e.g., the UEs (104)) associated with a set of users (e.g., the user (102)). The shared policy control request triggers data ID = S 1 is included in a separate Information Element (IE) to specify which shared data resources (i.e., the set of shared data resources) are available corresponding to the shared policy control request triggers data ID = SI. In an embodiment, the shared policy control request triggers data ID = S 1 may be mapped to the set of shared data resources and the set of UEs.

[0117] Further, at step 310, the AMF (302) performs a self-check to determine whether the shared policy control request triggers data ID = SI received from the PCF (304) is available in the database, i.e., the cache memory associated with the AMF (302). In other words, the AMF (302) performs checks whether the list of existing shared data IDs associated with the AMF (302) includes the shared policy control request triggers data ID = SI. If the shared policy control request triggers data ID = SI is not available at the AMF 302, at step 312, the AMF 302 sends the get request to the PCF (304). The get request includes the set of query parameters associated with the shared policy control request triggers data ID = S 1. The set of query parameters includes the list of existing shared data IDs, the set of shared data resources associated with each existing shared data ID within the list of existing shared data IDs, the query for information (i.e., the set of shared data resources) associated with the shared policy control request triggers data ID = SI received from the PCF (304). The get request is sent by the AMF (302) to the PCF (304) for retrieving the set of shared data resources associated with the shared policy control request triggers data ID = SI that the AMF (302) does not have access to or is missing the database associated with the AMF (302).

[0118] Upon receiving the get request, the PCF (304) processes the get request to retrieve the set of shared data resources corresponding to the shared policy control request triggers data ID = SI from an associated database, e.g., the database (210) or the UDSF. Further, the PCF (304) provides the set of shared data resources as the get response to the AMF (302). Upon receiving the set of shareddata resources associated with the shared policy control request triggers data ID = SI, at step 314, the AMF (302) subscribes for any modification done by the PCF (304) in the set of shared data resources associated with the shared policy control request triggers data ID = S 1 based the at least one service request or future service requests. The AMF (302) may use a subscribe service operation (or a subscribe service request) for subscribing with the PCF (304) for receiving the update response, i.e., the signal notification message. In addition, upon receiving the set of shared data resources associated with the shared policy control request triggers data ID = SI, the AMF (302) updates its database with the set of shared data resources associated with the shared policy control request triggers data ID = SI. Further, based on the subscribe service operation, the AMF (302) may be configured to receive the update response from the PCF (304) for any modifications done by the PCF (304) in the set of shared data resources associated with the shared policy control request triggers data ID = SI for future service requests.

[0119] Further, at step 316, the PCF (304) is configured to modify the set of shared data resources associated with the shared policy control request triggers data ID = S 1 based on the at least one service request. In other words, suppose the at least one service request, i.e., the NPCF_UE policy control_create request includes an addition of an event trigger known as a priority and resource allocation change (PRA CH). In this case, upon receiving the NPCF UE policy control create request, the PCF (304) may be configured to modify the set of shared data resources by adding the event trigger, i.e., the PRA_CH to the event triggers, i.e., the LOC CH, PLMN CH, and ACCESS TYPE CH associated with the shared policy control request triggers data ID = SI. Further, based on the modification, at step 318, the PCF (304) sends a single notification message, i.e., the update response to the AMF (302) regarding the modification done in the set of shared data resources associated with the shared policy control request triggers data ID = SI. By consolidating the update response into the single notification message, the PCF (304) avoids sending multiple notification messages corresponding to the modification to the AMF (302). The above approach enables the AMF (302) toefficiently update the set of UEs mapped to the shared policy control request triggers data ID = SI based on the modification. In other words, the AMF (302) may be configured to apply the modification, i.e., the addition of the PRA CH in the set of shared data resources to the set of UEs mapped to the shared policy control request triggers data ID = S 1.

[0120] Additionally, at step 320, the AMF (302) may be configured to modify the subscription with the PCF (304) for receiving the update response from the PCF (304) based on the modification in the set of shared data resources associated with the shared policy control request triggers data ID = S 1. The AMF (302) may be configured to modify the subscription with the PCF (304) using a modified subscription service operation (i.e., a modify subscription service request). For example, the AMF (302) may modify the time for receiving the update response, i.e., the single notification message from the PCF (304) corresponding to the subscription associated with the shared policy control request triggers data ID = SI. In an embodiment, the AMF (302) may modify (i.e., extend or reduce) an expiry time corresponding to the subscription associated with the shared policy control request triggers data ID = SI. Further, the AMF (302) may anytime unsubscribe from the PCF (304) for receiving the update response of the modification in the set of shared data resources associated with the shared policy control request triggers data ID = SI, as mentioned via step 322. The AMF (302) may unsubscribe with the PCF (304) for receiving the update response corresponding to the modification based on an unsubscribe service operation (i.e., an unsubscribe service request).

[0121] In an embodiment, the shared data ID (e.g., the shared policy control request triggers data ID = SI) may correspond to a unique identifier (also referred to as a Unique Universal Identifier (UUID)). The Shared Data ID may be unique within a context of the signaling transaction between the AMF (302) and the PCF (304). In an embodiment, the shared data ID may be mapped to its associated parameters, i.e., the set of shared data resources. Further, the shared data ID, along with the set of shared data resources, may be provisioned within the PCF (304). Aswill be appreciated, the PCF (304) may include a plurality of shared data IDs with its corresponding set of shared data resources. This information (i.e., the plurality of shared data IDs along with its corresponding set of shared data resources) can be stored either locally within the PCF (304) or in the UDSF associated with the PCF (304). The PCF (304) may retrieve this information as needed upon receiving service requests. Further, when responding to the get request (also referred to as the get service operation), the PCF (304) may provide the AMF (302) with a shared data ID and its corresponding shared data resources as the get response. Further, the AMF (302) may store the shared data ID and the corresponding shared data resources data within the associated database or the UDSF for further processing.

[0122] In an embodiment, the AMF (302) may retrieve the set of shared data resources from the PCF (304) using the get request, unless the set of shared data resources is already cached within the database associated with the AMF (302). This cached data, i.e., the set of shared data resources remains available in the database as long as a consumer Network Function (NF) is serving a UE for which the cached data is relevant.

[0123] In an embodiment, shared data IDs (i.e., the list of existing shared data IDs) which are used for identifying the set of shared data resources available at the AMF (302) are included in the get request that is sent to the PCF (304). If the get request contains an empty array corresponding to a shared data ID received from the PCF (304) for a new service request, then the empty array indicates that no shared data resources corresponding to the shared data IDs are currently available at the AMF (302). In such case, the PCF (304) may send the set of shared data resources identified using the shared data ID as the get response to the AMF (302). If the get request sent by the AMF (302) does not include the set of query parameters, then the PCF (304) may not send the set of shared data resources as the get response to the AMF (302).

[0124] Unless the shared data treatment feature is supported by the AMF (302) and the PCF (304), an individual UE data may take precedence over shareddata resources. Further, if the shared data treatment feature is supported by the AMF (302) and the PCF (304), specific shared data treatment instructions may apply. For instance, if shared data resources identified using a corresponding shared data ID A appears before a shared data ID B in the list of existing shared data IDs, the shared data ID A may take precedence over the shared data ID B. In scenarios where the shared data treatment instructions are not applicable at the AMF (302) and the PCF (304), the individual UE data may take precedence over the shared data resources. For example, if an attribute of a type of an array is present but empty in the individual UE data and is also present (with any cardinality) in the shared data resources and no shared data treatment instructions apply, an empty array from the individual UE data will take precedence.

[0125] In an embodiment, when any shared data resources are modified by the PCF (304) and the AMF (302) is subscribed to receive updates, the PCF (304) may send the single notification message to the AMF (302). Upon receiving the single notification message, the AMF (302) may update the set of shared data resources for all UE policy sessions associated with the same shared data ID.

[0126] In an embodiment, when the single notification message, i.e., the update response is timed out or if a predefined error code is received by the PCF (304) from the AMF (302), the PCF (304) may be configured to retry sending the single notification message after an expiry of a pre-defined time interval. The predefined interval may be configured by network operators based on their requirements. For instance, suppose a network operator may have configured an initial pre-defined interval for retrying the sending of the single notification message to be Tl=l second based on their requirement. In such cases, the network operator may be able to change the pre-defined time interval to a subsequent predefined time interval, e.g., Tl+N seconds, where ‘N’ is 30 seconds for retrying the sending of the single notification message by the PCF (304) to the AMF (302). In such scenario, the single notification message may be sent by the PCF (304) to the AMF (302) after an expiry of 31 seconds.

[0127] FIG. 4 illustrates an exemplary flow chart (400) of a method for managing User Equipment (UE) (104) policy control signaling in a network, in accordance with an embodiment of the present disclosure. The method of FIG. 4 is explained in conjunction with FIG. 2.

[0128] In step (402), the receiving unit (212) of the Home Policy Control Function (H-PCF) receives at least one service request corresponding to one or more UE policy sessions from a Visited Policy Control Function (V-PCF), wherein the one or more UE policy sessions are associated with a set of UEs (104). The service request may comprise a UE policy control create request, a UE policy control update request, a UE policy control delete request, or a UE policy control modify request. Each service request corresponds to a UE policy session initiated in the visited network that requires policy handling or updates from the home network.

[0129] In step (404), in response to receiving the at least one service request, the transmitting unit (214) of the H-PCF transmits a service response to the V-PCF. The service response includes a shared data Identifier (ID) that is associated with a set of UE policy data resources. The shared data ID serves as a logical identifier for a grouped set of UE policy data resources applicable to the set of UEs (104) involved in the policy sessions. The shared data ID may be used to notify the V- PCF about any future modifications made to the associated UE policy data resources. Example policy data resources may include Access Network Discovery and Selection Policy (ANDSP), UE Route Selection Policy (URSP), Vehicle-to- Everything Policy (V2XP), Aircraft-to-Everything Policy (A2XP), Proximity Services Policy (ProSeP), and Ranging and Side link Positioning Policy (RSLPP).

[0130] In step (406), the processing engine (208) of the H-PCF modifies the set of UE policy data resources associated with the shared data ID based on the at least one received service request. The processing engine (208) may update policy control request triggers associated with the shared data ID, such as triggers based on UE mobility, session establishment, or quality of service (QoS) requirements.

[0131] In step (408), following the modification of the policy data resources, the transmitting unit (214) of the H-PCF sends an update response to the V-PCF. The update response corresponds to the modification in the set of UE policy data resources associated with the shared data ID. Upon receiving the update response, the V-PCF is configured to apply the modifications for the set of UEs (104) that are mapped to the shared data ID. This ensures consistent policy enforcement across the visited network for all UEs (104) governed by the shared data ID.

[0132] FIG. 5 illustrates an example computer system (500) for managing User Equipment (UE) (104) policy control signaling in a network, in accordance with the embodiments of the present disclosure. FIG. 5 is explained in conjunction with FIGs 1, 2, 3 and 4.

[0133] As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), a communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (560) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (500) connects.

[0134] In an embodiment, the main memory (530) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for theprocessor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces).

[0135] In an embodiment, the bus (520) may communicatively couple the processor(s) (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system (500).

[0136] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (520) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (500) limit the scope of the present disclosure.

[0137] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the disclosure and not as limitation.TECHNICAL ADVANCEMENTS

[0138] The present disclosure provides a method and a system for managing signaling transactions in a telecommunication network.

[0139] The present disclosure provides an optimized approach for reducing the signaling transactions (also referred as signaling traffic) between a Policy Control Function (PCF) and an Access and Mobility Management Function (AMF) in non-roaming scenario by allowing the PCF to send a single notification message to the AMF for multiple UE policy update sessions instead of an individual notification message for each UE policy update session.

[0140] The present disclosure provides a method and a system that manages the signaling transactions during roaming scenarios by interacting between a Home PCF (HPCF) and a Visited PCF (VPCF).

[0141] The present disclosure provides a method and a system that improves performance of the telecommunication network by allowing the PCF to send a single notification message to the AMF for multiple UE policy update sessions.

[0142] The present disclosure provides a method and a system that optimizes network resources (e.g., routers, switches, firewalls, etc.) utilization by reducing number of notification messages (i.e., the UE policy control update notify message) exchanged between the PCF and the AMF in non-roaming scenarios, and between the H-PCF and the V-PCF in roaming scenarios, thereby reducing the signaling overhead and processing load on each respective network function.

[0143] The present disclosure provides a streamlined approach for managing the signaling transactions by integrating a shared data feature and a shared data treatment feature within the PCF and the AMF for non-roaming scenarios over the N 15 interface, and within the H-PCF and the V -PCF for roaming scenarios over the N24 interface .

[0144] The present disclosure enhances scalability of the telecommunication network by handling bulk subscriber modifications or deletion requests with a single notification message.

[0145] The present disclosure provides new service operations, e.g., a GET service operation, a subscribe service operation, a modify subscription service operation, and an unsubscribe service operation for UE policy control services (i.e., the at least one services) to enhance capability of the PCF and the AMF in managing UE policies more effectively.

Claims

1. CLAIMS1. A method for managing User Equipment (UE) (104) policy control signaling in a network (106), the method comprising: receiving, by a Home Policy Control Function (H-PCF), at least one service request corresponding to one or more UE policy sessions from a Visited Policy Control Function (V-PCF), wherein the one or more UE policy sessions are associated with a set of UEs (104); transmitting, by the H-PCF, a service response comprising a shared data Identifier (ID), associated with a set of UE policy data resources, to the V-PCF, in response to receiving the at least one service request, wherein the shared data ID is used for notifying the V-PCF regarding modification of the set of UE policy data resources, associated with the one or more UE policy sessions; modifying, by the H-PCF, the set of UE policy data resources associated with the shared data ID based on the at least one service request; and sending, by the H-PCF, an update response corresponding to the modification in the set of UE policy data resources, associated with the shared data ID, to the V-PCF, wherein the V-PCF is configured to apply the modification in the set of UE policy data resources for the set of UEs (104) mapped to the shared data ID, based on the updated response.

2. The method as claimed in claim 1, wherein the H-PCF is located in a home network and the V-PCF is located in a visited network to manage the UE policy control signaling.

3. The method as claimed in claim 1, wherein the at least one service request comprises a UE policy control create request, a UE policy control update request, a UE policy control delete request, and a UE policy control modify request.

4. The method as claimed in claim 1, wherein each UE policy session is associated with at least one UE policy, and wherein the at least one UE policy comprises one or more of an Access Network Discovery and Selection Policy (ANDSP), a UE Route Selection Policy (URSP), a Vehicle-to-Everything Policy (V2XP), an Aircraft-to-Everything Policy (A2XP), a Proximity Services Policy (ProSeP), and a Ranging and Sidelink Positioning Policy (RSLPP).

5. The method as claimed in claim 1, wherein the shared data ID is mapped to the set of UE policy data resources and the set of UEs (104).

6. The method as claimed in claim 1 , wherein transmitting the service response comprises: performing, by the H-PCF, a check to determine whether the V-PCF is configured with a shared data feature and a shared data treatment feature, wherein the configuration enables the V-PCF to apply the modification to the set of UE policy data resources for the set of UEs (104) based on the shared data ID.

7. The method as claimed in claim 6, wherein the V-PCF configured with the shared data feature and the shared data treatment feature communicates with the H- PCF over an N24 interface.

8. The method as claimed in claim 1, wherein modifying the set of UE policy data resources comprises: updating, by the H-PCF, one or more policy control request triggers associated with the shared data ID, in response to the at least one service request.

9. A system (108) for managing User Equipment (UE) (104) policy control signaling in a network (106), the system comprising: a receiving unit (212) configured to receive, at a Home Policy Control Function (H-PCF), at least one service request corresponding to one or more UE policy sessions from a Visited Policy Control Function (V-PCF), wherein the one or more UE policy sessions are associated with a set of UEs (104); a transmitting unit (214) configured to transmit, from the H-PCF, a service response comprising a shared data Identifier (ID), associated with a set of UE policy data resources, to the V-PCF in response to receiving the at least one service request, wherein the shared data ID is configured for notifying the V-PCF regarding modification of the set of UE policy data resources, associated with the one or more UE policy sessions; a processing engine (208) configured to modify, at the H-PCF, the set of UE policy data resources associated with the shared data ID based on the at least one service request; and the transmitting unit (214) further configured to send, from the H- PCF, an update response, corresponding to the modification in the set of UE policy data resources, associated with the shared data ID to the V-PCF, wherein the V-PCF is configured to apply the modification in the set of UE policy data resources for the set of UEs (104) mapped to the shared data ID, based on the update response.

10. The system as claimed in claim 9, wherein the H-PCF is located in a home network and the V-PCF is located in a visited network to manage the UE policy control signaling.

11. The system as claimed in claim 9, wherein the at least one service request comprises a UE policy control create request, a UE policy control update request, a UE policy control delete request, and a UE policy control modify request.

12. The system as claimed in claim 9, wherein each UE policy session is associated with at least one UE policy, and wherein the at least one UE policy comprises one or more of an Access Network Discovery and Selection Policy (ANDSP), a UE Route Selection Policy (URSP), a Vehicle-to-Everything Policy(V2XP), an Aircraft-to-Everything Policy (A2XP), a Proximity Services Policy (ProSeP), and a Ranging and Sidelink Positioning Policy (RSLPP).

13. The system as claimed in claim 9, wherein the shared data ID is mapped to the set of UE policy data resources and the set of UEs (104).

14. The system as claimed in claim 9, wherein the transmitting unit (214) is further configured to: perform a check to determine whether the V-PCF is configured with a shared data feature and a shared data treatment feature, wherein the configuration enables the V-PCF to apply the modification to the set of UE policy data resources for the set of UEs (104) based on the shared data ID.

15. The system as claimed in claim 14, wherein the V-PCF configured with the shared data feature and the shared data treatment feature communicates with the H- PCF over an N24 interface.

16. The system as claimed in claim 9, wherein the processing engine (208) is further configured to: update one or more policy control request triggers associated with the shared data ID, in response to the at least one service request.

17. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors (202), cause the one or more processors to perform operations for managing User Equipment (UE) (104) policy control signaling in a network (106), the operations comprising: receiving, by a Home Policy Control Function (H-PCF), at least one service request corresponding to one or more UE policy sessions from a Visited Policy Control Function (V-PCF), wherein the one or more UE policy sessions are associated with a set of UEs (104);transmitting, by the H-PCF, a service response comprising a shared data Identifier (ID), associated with a set of UE policy data resources, to the V-PCF, in response to receiving the at least one service request, wherein the shared data ID is used for notifying the V-PCF regarding modification of the set of UE policy data resources associated with the one or more UE policy sessions; modifying, by the H-PCF, the set of UE policy data resources associated with the shared data ID based on the at least one service request; and sending, by the H-PCF, an update response corresponding to the modification in the set of UE policy data resources associated with the shared data ID, to the V-PCF, wherein the V-PCF is configured to apply the modification in the set of UE policy data resources for the set ofUEs (104), mapped to the shared data ID, based on the update response.

Images