Method and system for reducing policy control signalling load in networks using shared policy identifiers

Abstract

The disclosure provides method (500) for policy control in telecommunication network. The method (500) includes receiving service request associated with Session Management (SM) policy and / or Access and Mobility (AM) policy from network function. The network function includes a Session Management Function (SMF) (402) when received service request is associated with SM policy and Access and Mobility Management Function (AMF) (302) when received service request is associated with AM policy. The method (500) includes transmitting service response including shared data Identifier associated with policy data resources to network function. The method (500) includes modifying policy data resources associated with shared data ID. The method (500) includes sending update response corresponding to modification in policy data resources associated with shared data ID to network function. The network function is configured to apply the modifications in policy data resources to the communication sessions associated with UEs (104) mapped to shared data ID.

Description

METHOD AND SYSTEM FOR REDUCING POLICY CONTROL SIGNALLING LOAD IN NETWORKS USING SHARED POLICY IDENTIFIERSRESERVATION 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 (JPL) 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.TECHNICAL FIELD

[0002] The present disclosure relates to a telecommunications network. In particular, the present disclosure relates to a method and a system for managing signalling transactions in a telecommunication network.DEFINITION

[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 to indicate 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 signalling related to the 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 behaviour and resource usage. The PCF is responsible for policy enforcement and management, including subscription management, Quality of Service (QoS) control, and network slicing.

[0006] The term ‘Session Management Function (SMF)’ 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 session management, including session establishment, modification, and release.

[0007] The term ‘N15 interface’ used herein in the specification refers to an interface defined in 3rd Generation Partnership Project (3GPP) standards for communication between the PCF, an Application Function (AF), and the AMF. The N15 interface is used for exchanging policy control information and data between these functions.

[0008] The term ‘N7 interface’ used herein in the specification refers to an interface defined in 3rd Generation Partnership Project (3GPP) standards for communication between the SMF and the PCF. The N7 interface is used for policy control and enforcement related to session management.

[0009] The term ‘Network Policy Control Function (NPCF)’ used herein in the specification refers to a network function in the 5G core network that is responsible for defining, managing, and enforcing network policies. The NPCF ensures optimal resource allocation, QoS control, and adherence to Service Level Agreements (SLAs) by making policy decisions based on network conditions and user requirements.

[0010] The term ‘Network Charging Function (NCHF)’ used herein in the specification refers to a network function in the 5G core network that is responsible for managing and processing charging-related tasks. The NCHF handles thecollection, computation, and reporting of usage data for billing purposes, ensuring accurate and timely charging based on network usage and service policies.

[0011] 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 Access and Mobility (AM) policy-related data or shared data resources. The UDSF supports the PCF, the SMF, and the AMF by providing access to this data.

[0012] The term ‘Protocol Data Unit (PDU) sessions’ used herein in the specification refers to communication sessions in the telecommunication network (i.e., the 5G core network) that establish a data path between the UE and the telecommunication network, allowing for data exchange. Each PDU session is associated with a specific type of data traffic and includes details on the QoS, security, and data routing.

[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, the SMF, 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 to and manage a corresponding set of shared data resources across different network functions, such as the PCF, the SMF, and the AMF. Examples of the Shared Data ID include values such as SharedQoS IDl representing a common Quality of Service (QoS) profile shared across multiple PDU sessions, or SharedAMPolicy_ID2 representing a set of Access and Mobility triggers such as location change, slice restriction applicable to multiple UEs.

[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 SM policy, AM policy and charging control. The shared datafeature is used to provide a consistent view of SM policy and AM policy-related data (i.e., the shared data resources) across different network functions, such as the AMF, the SMF, 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 define how the shared data resources should be handled and processed when it is accessed by different network functions, such as the AMF, the SMF, and the PCF. 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.

[0017] The term ‘Get service operation’ used herein in the specification refers to a get request that is sent by the AMF and the SMF to the PCF for retrieving the shared data resources from the PCF. The AMF and the SMF 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 and the SMF 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 and the SMF to the PCF to modify an existing subscription corresponding to the notifications. This includes changing subscription parameters, such as subscription duration.

[0020] The term ‘Unsubscribe service operation’ used herein in the specification refers to a request sent by the AMF and the SMF to the PCF to cancel or withdraw the existing subscription to the notifications. Once unsubscribed, the AMF and the SMF 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

[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] In a Fifth Generation (5G) telecommunication network, policy control and management functions play a vital role in ensuring efficient operation, optimized resource utilization, and seamless user experience. Two critical entities involved in the process are the Policy Control Function (PCF) and the consumer functions, such as a Session Management Function (SMF) and an Access and Mobility Management Function (AMF). The PCF is responsible for making control decisions corresponding to Session Management (SM) policies and Access and Mobility (AM) policies. In the case of SM policies, the PCF manages flow-based charging functionalities, while the SMF is tasked with managing the setup, modification, and release of Protocol Data Unit (PDU) sessions. Similarly, for mobility-related functions, the AMF applies AM policies provided by the PCF to regulate access and mobility aspects for User Equipment (UE) operating in the network. The PCF interacts with both the SMF and the AMF to enforce policies and handle the lifecycle of sessions and mobility operations in the telecommunication network.

[0024] In conventional approaches, the PCF is capable of autonomously updating SM or AM policies without an explicit request from the SMF or AMF. Such updates may be triggered by external triggers, including information from reference points such as Rx or N5, notifications from the NPCF AM policy authorization service, or updates from a Unified Data Repository (UDR) related to Application Function requirements. Further, updates may be driven by internaltriggers, such as the activation of a pending policy counter via a Network Charging Function (NCHF) spending limit control service. Upon such triggers, the PCF may communicate the updated SM or AM policies to the SMF or AMF through an HTTP POST request to a designated Uniform Resource Identifier (URI). The request informs the SMF or AMF about necessary modifications, deletions, or provisioning of policies that need to be applied to corresponding PDU sessions or AM policy associations.

[0025] However, in scenarios involving bulk subscriber subscription modifications or deletions, the above approach introduces significant inefficiencies. The PCF initiates multiple update notification messages, one for each PDU session or AM policy session, resulting in a sudden surge of signalling traffic between the PCF and the SMF or AMF. Such repetitive transmissions increase network load, cause signalling storms, and may lead to higher latency, reduced responsiveness, and degradation in overall network performance. The lack of a consolidated mechanism for handling shared or common policy data across multiple sessions further aggravates the problem, making policy update processes complex, disruptive, and resource-intensive.

[0026] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.SUMMARY OF THE DISCLOSURE

[0027] In an exemplary embodiment, a method for policy control in a telecommunication network is described. The method includes receiving, by a Policy Control Function (PCF), at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function includes one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of ProtocolData Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs). Further, the method includes transmitting, by the PCF, a service response including a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. The method further includes modifying, by the PCF, the set of policy data resources associated with the shared data ID based on the at least one service request. Further, the method includes sending, by the PCF, an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function. The network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response.

[0028] In an embodiment, the at least one service request comprises an AM policy control create request, update request, delete request, or modify request.

[0029] In another embodiment, the at least one AM policy includes an access type change trigger policy, a location change reporting policy, an access and mobility restriction policy, a network slice access control policy, a registration area update policy, or a mobility restriction enforcement policy.

[0030] In another embodiment, transmitting the service response, the method includes performing, by the PCF, a check to determine whether the AMF supports a shared data feature and a set of shared data treatment features. Such support is required to apply the modifications to the AM policy data resources for the set of UEs based on the shared data ID.

[0031] In another embodiment, the shared data ID is mapped to a set of policy data resources comprising AM policy data resources and to the associated set of UEs.

[0032] In another embodiment, the at least one service request comprises an SM policy control create request, update request, delete request, or modify request.

[0033] In another embodiment, the method includes controlling policy control signalling by reducing transactions between the PCF and SMF over an N7 interface.

[0034] In another embodiment, the shared data ID is mapped to a set of policy data resources comprising SM policy data resources and to the associated set of UEs.

[0035] In another embodiment, the at least one SM policy includes a Quality of Service (QoS) policy, a resource allocation policy, a charging policy, a session establishment policy, an emergency service policy, or a data offloading policy.

[0036] In another exemplary embodiment, a system for managing policy control in a telecommunication network is described. The system includes a Policy Control Function (PCF). The PCF is configured to receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function includes one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs). Further, the PCF is configured to transmit a service response including a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. Further, the PCF is configured to modify the set of policy data resources associated with the shared data ID based on the at least one service request. The PCF is further configured to send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function. The network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response.

[0037] In another embodiment, a non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a Policy Control Function (PCF) in a telecommunication network, cause the one or more processors to receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function includes one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs). Further, the PCF cause the one or more processors to transmit a service response including a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. The PCF cause the one or more processors to modify the set of policy data resources associated with the shared data ID based on the at least one service request. Further, the PCF cause the one or more processors to send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function. The network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response.

[0038] In yet another embodiment, a User Equipment (UE) communicatively coupled to a system, said coupling includes steps of receiving a connection request. Further, the coupling include step of sending an acknowledgment of the connection request to the system. The coupling includes step of transmitting data from the UE to the system. The system is configured for managing policy control signalling in a telecommunication network. The system may include a Policy Control Function (PCF) configured to receive at least one service request associated with at least oneof a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function includes one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs). Further, the PCF is configured to transmit a service response including a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. Further, the PCF is configured to modify the set of policy data resources associated with the shared data ID based on the at least one service request. The PCF is further configured to send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function. The network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response.OBJECTIVES OF THE PRESENT DISCLOSURE

[0039] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

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

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

[0042] Another object of the present disclosure is to reduce signalling transactions (also referred to as signalling traffic) between a Policy Control Function (PCF) and a Session Management Function (SMF) by enabling the PCF to consolidate multiple Protocol Data Unit (PDU) session updates corresponding to a Session Management (SM) policy update into a single notification message. The consolidated single notification message is then sent by the PCF to the SMF, thereby avoiding the need to send an individual message for each PDU session.

[0043] 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 and the SMF for the multiple AM policy update sessions and the multiple PDU sessions.

[0044] 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., an AM policy control update notify message) exchanged between the PCF and the AMF, hence reducing load on the PCF and the AMF.

[0045] Another objective of the present disclosure is to provide a streamlined approach for managing the signalling transactions between the PCF and the AMF by integrating a shared data feature and a shared data treatment feature within the PCF and the AMF over an N15 interface.

[0046] Another object of the present disclosure is to provide a streamlined approach for optimizing the signalling transactions between the PCF and the SMF by integrating a shared data feature and a shared data treatment feature within the PCF and the SMF over an N7 interface.

[0047] 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.

[0048] Another objective of the present disclosure is to provide new service operations, e.g., a get service operation, a subscribe service operation, a modify subscription service operation, and an unsubscribe service operation for AM policy control services to enhance the capability of the PCF and the AMF in managing AM policies more effectively and SM policy control services to enhance the capability of the PCF and the SMF in managing SM policies more effectively.

[0049] 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.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

[0050] 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.

[0051] FIG. 1 illustrates an exemplary network architecture of a system configured for policy control in a telecommunication network, in accordance with an embodiment of the present disclosure.

[0052] FIG. 2 illustrates an exemplary block diagram of the system configured for policy control in the telecommunication network, in accordance with an embodiment of the present disclosure.

[0053] FIG. 3 illustrates an exemplary process flow for policy control between an Access and Mobility Management Function (AMF) and a Policy Control Function (PCF) in the telecommunication network, in accordance with an embodiment of the present disclosure.

[0054] FIG. 4 illustrates an exemplary process flow for policy control between a Session Management Function (SMF) and the PCF in the telecommunication network, in accordance with an embodiment of the present disclosure.

[0055] FIG. 5 illustrates a flow chart of a method for policy control in the telecommunication network, in accordance with an embodiment of the present disclosure.

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

[0057] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 -User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory206 -Interface(s)208 - Policy Control Function (PCF)210 - Database300 - Process flow302 - Access and Mobility Management Function (AMF)400 - Process flow402 - Session Management Function (SMF)500 - Method600 - A computer system610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

[0058] 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 specificdetails. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any 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. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0059] 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.

[0060] 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.

[0061] Also, it is noted that individual embodiments may be described as a process that 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 additionalsteps 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.

[0062] 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 construed 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 like the term “comprising” as an open transition word without precluding any additional or other elements.

[0063] 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.

[0064] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context 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 notpreclude 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 combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0065] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device is capable of receiving and / or transmitting one or parameters, performing function / s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but is not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general -purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0066] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general -purpose processor, aspecial purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signalling Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0067] 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.

[0068] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth-generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The sixth-generation (6G) technology promises to build upon these advancements, pushing theboundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way to connect and interact with technology.

[0069] In a 5G network architecture, a Policy Control Function (PCF) serves as a central policy decision point, responsible for making control decisions related to SM policies and AM policies. A Session Management Function (SMF) manages the lifecycle of Protocol Data Unit (PDU) sessions, while an Access and Mobility Management Function (AMF) oversees access and mobility functions for User Equipment (UE). Both the SMF and the AMF rely on policy updates from the PCF to enforce network rules, optimize resource allocation, and ensure consistent service quality.

[0070] Conventional interfaces such as N7 for PCF-SMF and N15 for PCF- AMF allow the PCF to autonomously update policies without explicit requests from the SMF or AMF. Such updates may be triggered by external inputs, such as notifications from reference points (Rx, N5) or updates from a Unified Data Repository (UDR), or internal triggers, such as policy counters managed through a Network Charging Function (NCHF). When updates are required, the PCF communicates with consumer functions using an HTTP POST request (e.g., "{notificationUriJ / update") to deliver policy modifications. While effective for individual sessions, conventional techniques exhibit serious limitations in bulk update scenarios. Specifically, when the PCF receives a subscriber-wide modification or deletion request, it initiates multiple update notify messages, one for each PDU session or AM policy session. The conventional techniques result in a surge of signalling traffic between the PCF and the SMF / AMF, often leading to network congestion, high latency, inefficient use of the PCF and NF resources, and reduced scalability. Additionally, Conventional techniques may define the signalling flows for AMPolicyControl and SMPolicyControl services, but do not provide mechanisms for consolidated handling of shared policy data across multiplesessions. As a result, the conventional techniques are inadequate for managing bulk subscriber modifications or deletions in real-world network environments.

[0071] The present disclosure introduces a framework for SharedData and SharedDataTreatment support in policy control operations over N7 and N15 interfaces. The SharedData is a mechanism where common policy information (e.g., QoS rules, mobility restrictions) is grouped under a single identifier and reused across multiple sessions / UEs. Further, the SharedDataTreatment defines how conflicts are resolved between shared data and UE-specific data, ensuring the correct policy takes precedence. Further, the SharedData and SharedDataTreatment support reduce redundant signalling, enable bulk updates with one notification, and improve efficiency in 5G policy control. The N& interface is reference point between the PCF and the SMF. The N7 interface is used to exchange Session Management (SM) policy control information, such as QoS rules, charging rules, and session-related updates. Further, the N15 interface is reference point between the PCF and the AMF. The N15 interface is used to exchange Access and Mobility (AM) policy control information, such as mobility restrictions, access rules, and registration policies. Instead of generating multiple per-session notification messages, the PCF associates common policy attributes with a Shared Data Identifier (ID) that maps to a set of UEs or sessions. In an embodiment, mapping a Shared Data ID with a set of UEs or sessions means linking a unique identifier to common policy data applicable to multiple users. Instead of handling policies individually, the PCF assigns a Shared Data ID to group policies, which the SMF / AMF caches. The mapping is performed during policy creation / update, where the PCF provides the Shared Data ID in its response, allowing bulk application and efficient synchronization across all linked UEs or sessions.

[0072] When a modification or deletion request is triggered, the PCF updates the shared policy data associated with the Shared Data ID and transmits a single update notification to the SMF or AMF. The consumer function, upon receiving the notification, applies the updated shared data across all mapped sessions or policy associations. To support the framework, the present disclosure defines enhancedservice operations such as Get, Subscribe, ModifySubscription, and Unsubscribe, allowing consumer functions to retrieve, subscribe, and manage shared policy data updates dynamically. The Get service operation allows the consumer function (SMF / AMF) to retrieve SharedData resources from the PCF. If the consumer does not already have the required shared data cached, it sends a Get request with parameters (e.g., shared IDs). The PCF responds with the associated shared policy data. Further, the Subscribe service operation enables the SMF / AMF to subscribe for notifications of changes in SharedData resources. Once subscribed, the PCF may automatically notify the consumer whenever the shared data is updated, ensuring real-time synchronization. The ModifySubscription operation allows the SMF / AMF to change existing subscription parameters, such as extending expiry time or altering the scope of subscribed SharedData. Further, the unsubscribe operation enables the SMF / AMF to cancel an existing subscription for SharedData updates. After unsubscribing, the PCF may no longer send notifications about changes for the specified SharedData resources, reducing unnecessary signalling.

[0073] Additionally, the SharedDataTreatment mechanism provides precedence rules to resolve conflicts between UE-specific policies and shared policies, ensuring accurate enforcement across heterogeneous subscriber groups. By consolidating updates and enabling shared policy treatment, the present disclosure significantly reduces signalling overhead, prevents traffic storms, improves scalability, and ensures synchronized enforcement of policies across large subscriber bases. The present disclosure provide more efficient, reliable, and futureproof policy control mechanism for advanced 5G network deployments.

[0074] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings. The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 6.

[0075] FIG. 1 illustrates an exemplary network architecture 100 of a system 108 configured for policy control in a telecommunication network, in accordancewith an embodiment of the present disclosure. In particular, the system 108 may for managing the signalling transaction (also referred to as the signalling traffic) between the PCF and the AMF and / or the SMF. As illustrated in FIG. 1, the network architecture 100 may include one or more User Equipments (UEs) 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 be 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 or the UEs 104. Although only three UE 104 are depicted in FIG. 1, however, any number of the UE 104 may be included without departing from the scope of the ongoing description.

[0076] 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 are not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical, a thermal, an electrical, a magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, a smart television (TV), computers, a smart security system, a 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.

[0077] Additionally, in some embodiments, the UE 104 may include, but 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 headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptopcomputer, 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, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, 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 an entity such as a touchpad, a touch-enabled screen, an 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.

[0078] In FIG. 1, the UE 104 may communicate with the system 108 through a network 106 for sending or receiving various types of data. In an embodiment, the network 106 may include at least one of a 5G network, a Sixth Generation (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.

[0079] 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 106may also include, by way of example but not limitation, 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.

[0080] In an embodiment, the UE 104 is communicatively coupled with the network 106. The network 106 may receive a connection request from the UE 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.

[0081] In an embodiment, the system 108 may include a Policy Control Function (PCF) configured to receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function includes one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs). The PCF may further be configured to transmit a service response comprising a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. Further, the PCF may be configured to modify the set of policy data resources associated with the shared data ID based on the at least one service request. The PCF may be configured to send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function. The network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response.

[0082] 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.

[0083] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 configured for control in the telecommunication network, in accordance with an embodiment of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0084] 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. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0085] In an embodiment, the one or more processor 202 that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the one or more processor 202. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, theprogramming for the one or more processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the one or more processor 202 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 one or more processor 202. In such examples, the system 108 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 108 and the processing resource. In other examples, the one or more processor 202 may be implemented by electronic circuitry. In an embodiment, the system 108 may include the PCF 208. The PCF 208 may be configured to communicate with the one or more processor 202, the AMF and the SMF. The AMF and the SMF may be present within the one or more processor of another system that is in communication with the system 108. In some embodiments, the PCF 208, the SMF, and the AMF may be present within the one or more processor 202 of the system 108.

[0086] In an embodiment, the system 108 may include an interface(s) 206. The interface(s) 206 may include a variety of interfaces, for example, interfaces for data input and output devices (VO), storage devices, and the like. The interface(s) 206 may facilitate communication through the system 108. The interface(s) 206 may also provide a communication pathway for one or more components of the system 108.

[0087] In an embodiment, the PCF 208 may be configured to receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function includes one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set ofcommunication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs).

[0088] The at least one service request include an AM policy control create request, update request, delete request, or modify request. The at least one AM policy includes an access type change trigger policy, a location change reporting policy, an access and mobility restriction policy, a network slice access control policy, a registration area update policy, or a mobility restriction enforcement policy. The at least one service request may be received corresponding to an Access and Mobility (AM) policy session. Examples of the at least one service request may include, but are not limited to, an AM policy control create request, an AM policy control update request, an AM policy control delete request, and an AM policy control modify request. In some embodiments, the at least one service request may be received corresponding to a Protocol Data Unit (PDU) session. The PDU session is a session in the telecommunication network (e.g., the 5G network) that handles an exchange of data between a User Equipment (UE) and the telecommunication network. The PDU session manages the transport of user data and network control messages, ensuring efficient and secure connectivity.

[0089] The at least one service request includes an SM policy control create request, update request, delete request, or modify request. The at least one SM policy includes a Quality of Service (QoS) policy, a resource allocation policy, a charging policy, a session establishment policy, an emergency service policy, or a data offloading policy. The at least one service request is received corresponding to a set of PDU sessions associated with a set of UEs. A PDU session is a session in the telecommunication network (e.g., a Fifth Generation (5G) network) that handles an exchange of data between a User Equipment (UE) and the telecommunication network. The PDU session manages the transport of user data and network control messages, ensuring efficient and secure connectivity. Further, the at least one service request may be associated with a Session Management (SM) policy. Examples of the SM policy may include, but are not limited to, a Quality of Service(QoS) policy, a resource allocation policy, a charging policy, a session establishment policy, an emergency service policy, and a data offloading policy. Further, examples of the at least one service request may include, but are not limited to, an SM policy control create request, an SM policy control update request, an SM policy control delete request, and an SM policy control modify request.

[0090] In an embodiment, the PCF 208 may be configured to transmit a service response including a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. Upon receiving the at least one service request, the PCF 208 is configured to send a service response based on the at least one service request to the AMF. The service response includes a shared data ID associated with a set of shared data resources (also referred to as a set of shared data parameters). The set of shared data resources represents a collection of data that can be shared by multiple UEs. For example, service area restrictions, a Radio Frequency Slice Profile Index (RFSP) index, a UE Aggregate Maximum Bit Rat (AMBR) value, event triggers, a slice, a presence reporting area information, a Public Land Mobile Network (PLMN), a Globally Unique AMF Identifier (GUAMI ), subscription data (Custom fields), and the like.

[0091] In an embodiment, the shared data ID may be mapped to the set of shared data resources and a set of UEs. The service response including the shared data ID may be sent when a shared data feature and a shared data treatment feature are supported by the AMF and the PCF 208. As will be appreciated, the support for the shared data feature and the shared data treatment feature are made available to the AMF and the PCF 208 over an N15 interface.

[0092] In another embodiment, the PCF 208 is configured to send a service response based on the at least one service request, to the SMF. The service response include a shared data ID associated with a set of shared data resources (also referred to as a set of shared data parameters). The set of shared data resources represents a collection of data that can be shared by multiple UEs. For example, event triggers,a slice, a presence reporting area information, a set of SM policies, a Public Land Mobile Network (PLMN) subscription data (Custom fields), a session Aggregate Maximum Bit Rat (AMBR) value, a default QoS, and the like. In an embodiment, the shared data ID may be mapped to the set of shared data resources and the set of UEs. The service response including the shared data ID may be sent when a shared data feature and a shared data treatment feature are supported by the SMF and the PCF 208. As will be appreciated, the support for the shared data feature and the shared data treatment feature are made available to the SMF and the PCF 208 over an N7 interface.

[0093] The PCF 208 may perform a check to determine whether the AMF supports a shared data feature and a set of shared data treatment features. Such support is used to apply the modifications to the AM policy data resources for the set of UEs based on the shared data ID. Further, the shared data ID is mapped to a set of policy data resources, including AM policy data resources and to the associated set of UEs. In other words, the AMF may be configured to perform the check to determine if the set of shared resources associated with the shared data ID is present in a database (or a cache memory) associated with the AMF. In one embodiment, if the AMF is not aware of the set of shared resources associated with the shared data ID, the AMF is configured to send a get request (also referred to as a get service operation) to the PCF 208. The get request may include a set of query parameters associated with the shared data ID. The set of query parameters may include, a list of existing shared data IDs, a set of shared data resources associated with each existing shared data ID within the list of existing shared data IDs, a query for information (i.e., the set of shared data resources) associated with the shared data ID received from the PCF 208, etc. Further, in response to sending the get request to the PCF 208, the AMF may be configured to receive a get response including the set of shared data resources associated with the shared data ID. Upon receiving the set of shared data resources for the shared data ID, the AMF may be subscribed to the modification done by the PCF 208 in the set of shared data resources associated with the shared data ID based on at least one service request.In addition, upon receiving the set of shared data resources for the shared data ID, the AMF may update the associated data, i.e., the cache memory based on the set of shared data resources with the associated shared data ID. Once the AMF is subscribed to the modification, the AMF may be configured to receive an update response, i.e., an update notification message (also referred to as a single notification message) from the PCF 208. The update response may include details of the modification done in the set of shared data resources belonging to the shared data ID based on the at least one service request.

[0094] In another embodiment, when the AMF is aware of the set of shared resources associated with the shared data ID, the AMF may be configured to receive the update response, i.e., the update notification message from the PCF 208 corresponding to the modification done in the set of shared data resources belonging to the shared data ID based on the at least one service request. In particular, after transmitting the service response corresponding to the at least one service request, the PCF 208 may be configured to modify the shared data resources associated with the shared data ID based on the at least one service request.

[0095] The PCF 208 may control the policy control signalling by reducing transactions between the PCF 208 and SMF over an N7 interface. Further, the shared data ID is mapped to a set of policy data resources, including SM policy data resources and to the associated set of UEs. The SMF may be configured to perform a check to determine if the SMF is aware of the set of shared resources associated with the shared data ID. In other words, the SMF may be configured to perform the check to determine if the set of shared resources associated with the shared data ID is present within a database (or a cache memory) associated with the SMF. In one embodiment, if the SMF is not aware of the set of shared resources associated with the shared data ID, the SMF is configured to send a get request (also referred to as a get service operation) to the PCF 208. The get request may include a set of query parameters associated with the shared data ID. The set of query parameters may include a list of existing shared data IDs, a set of shared data resources associated with each existing shared data ID within the list of existing shared data IDs, a queryfor information (i.e., the set of shared data resources) associated with the shared data ID received from the PCF 208, etc.

[0096] Further, in response to sending the get request to the PCF 208, the SMF may be configured to receive a get response including the set of shared data resources associated with the shared data ID. Upon receiving the set of shared data resources for the shared data ID, the SMF may be subscribed for the modification done by the PCF 208 in the set of shared data resources associated with the shared data ID based on the at least one service request. In addition, upon receiving the set of shared data resources for the shared data ID, the SMF may update the associated database, i.e., the cache memory based on the set of shared data resources with the associated shared data ID. Once the SMF is subscribed for the modification, the SMF may be configured to receive an update response, i.e., the update notification message (also referred to as the single notification message) from the PCF 208. The update response may include details of the modification done in the set of shared data resources belonging to the shared data ID based on the at least one service request.

[0097] In another embodiment, when the SMF is aware of the set of shared resources associated with the shared data ID, the SMF may be configured to receive the update response, i.e., the update notification message from the PCF 208 corresponding to the modification done in the set of shared data resources belonging to the shared data ID based on the at least one service request. In particular, after transmitting the service response corresponding to the at least one service request, the PCF 208 may be configured to modify the shared data resources associated with the shared data ID based on the at least one service request.

[0098] In an embodiment, the PCF 208 may be configured to send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function. The network function apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared dataID, based on the update response. Based on the modification, the PCF 208 may be configured to send the update response corresponding to the modification in the shared data resources associated with the shared data ID, to the AMF. In an embodiment, the PCF 208 may send a single notification message corresponding to the modification done in the set of shared data resources associated with the shared data ID for multiple AM policy sessions. The AMF may be configured to apply the modifications in the shared data resources to the set of UEs mapped to the shared data ID. The complete method of managing the signalling transactions between the PCF 208 and the AMF in the telecommunication network is further explained in detail in conjunction with FIG. 3.

[0099] In another embodiment, based on the modification, the PCF 208 may be configured to send the update response corresponding to the modification in the shared data resources associated with the shared data ID, to the SMF. In an embodiment, the PCF 208 may send the single notification message corresponding to the modification done in the set of shared data resources associated with the shared data ID for multiple PDU sessions. Further, upon receiving the update response, the SMF may be configured to apply the modification done in the shared data resources to each of the set of PDU sessions associated with the set of UEs mapped to the shared data ID. The complete method of managing the signalling transactions between the PCF 208 and the SMF in the telecommunication network is further explained in detail in conjunction with FIG. 4.

[0100] In an embodiment, the system 108 may include a database 210 that includes data (e.g., a list of existing shared data IDs, the set of shared data resources associated with each shared data ID in the list of existing shared data IDs, etc.) that may be either stored or generated as a result of functionalities implemented by any of the components of the processor 202.

[0101] FIG. 3 illustrates an exemplary process flow 300 for policy control between the AMF and the PCF 208 in the telecommunication network, in accordance with an embodiment of the present disclosure. The process flow 300may be implemented by the processor 202 implemented within or with the PCF 208 and the AMF 302. FIG. 3 is explained in conjunction with FIGS. 1 and 2.

[0102] In FIG. 3, a communication flow between an AMF 302 and the PCF 208 for managing signalling transactions is depicted. In order to manage the signalling transactions or to reduce high signalling transactions between the AMF 302 and the PCF 208, the AMF 302 and the PCF 208 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 208 to access and share common data (i.e., shared data resources) related to AM policy and charging control. The shared data feature is used to provide a consistent view of AM policy related data (i.e., shared data resources) across the AMF 302 and the PCF 208. In other words, the shared data feature ensures that the same set of AM policy related data is available for decision-making and enforcement across different network functions (e.g., the AMF 302 and the PCF 208) in the telecommunication network. 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 208. 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 service area restrictions, the RFSP index, the UE AMBR value, the event triggers, the slice, the presence area reporting information, the PLMN, the GUAMI, the subscription data (custom fields), and the like.

[0103] Initially, at step 304, the AMF 302 sends a NPCF_AM policy control create request to the PCF 208. The NPCF AM policy control create request may correspond to the at least one service request. Other examples of the at least one service request may include a NPCF AM policy control update request, a NPCF_AM policy control_delete request, and a NPCF_AM policy control modify request, and the like. The NPCF AM policy control update requestis sent from the AMF 302 to the PCF 208 when an existing AM policy association requires updates. The update may involve changes in triggers (e.g., location change), mobility restrictions, or access rules. Further, the NPCF AM Policy Control Delete Request is used when an AM policy association is no longer required, for example, during deregistration or termination of a UE’s connection. The AMF sends the delete request to the PCF, which then removes the corresponding AM policy association and stops enforcing the related policy rules. The NPCF_AM Policy Control_Modify Request allows the AMF 302 to partially modify specific attributes of an existing AM policy association without creating a new one. The modifications may include updating subscription data, adjusting policy counters, or altering service restrictions.

[0104] The AMF 302 sends the NPCF_AM policy control_create request to perform policy control actions related to AM policies management. Upon receiving the NPCF AM policy control create request, the PCF 208 may check whether the shared data feature and the shared data treatment feature are 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 306, the PCF 208 is configured to send a Npcf_AM policy control_create response, i.e., the service response to the AMF 302. The Npcf_AM policy control_create response includes a shared policy control request trigger data ID=S1, i.e., the shared data ID. In “ID = SI”, the “S” typically denotes SharedData, and the “1” is simply a unique sequence number or identifier assigned to that specific shared data resource. In an example, SI may represent a shared data resource for event triggers (e.g., location change, access type change), S2 may represent another shared data resource for QoS parameters, and S3 may represent a mobility restriction policy.

[0105] The shared policy control request trigger data ID=S1 includes event triggers, such as a location change, a PLMN change, and an access type change (LOC CH, PLMN CH, 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 LOC CH refers to a location change event trigger. The LOC CH indicates that the UE 104 has moved to adifferent location area, tracking area, or registration area, prompting the network to re-evaluate and possibly update mobility or access policies. The PLMN CH may refer to a PLMN change event trigger. A PLMN is the network operated by a specific mobile operator. When a UE switches from one PLMN to another (e.g., due to roaming), the PCF and AMF need to apply updated policies. Further, the ACCESS TYPE CH may refer to an access type change event trigger. The ACCESS TYPE CH occurs when a LE changes its access type, such as moving from 3GPP access (5G NR, LTE) to non-3GPP access (Wi-Fi, trusted / untrusted WLAN), or vice versa.

[0106] The shared policy control request trigger data ID=S1 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 trigger data ID=SL In an embodiment, the shared policy control request trigger data ID=S1 may be mapped to the set of shared data resources and the set of UEs 104.

[0107] Further, at step 308, the AMF 302 performs a self-check to determine whether the shared policy control request trigger data ID=S 1 received from the PCF 208 is available in the database 210, 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 trigger data ID=S1. If the shared policy control request trigger data ID=S1 is not available at the AMF 302, at step 310, the AMF 302 sends the get request to the PCF 208. The get request includes the set of query parameters associated with the shared policy control request trigger data ID=SL 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 trigger data ID=S1 received from the PCF 208, etc. The get request is sent by the AMF 302 to the PCF 208 for retrieving the set of shared data resources associated with the shared policy control request trigger dataID=S1 that the AMF 302 does not have access to or is missing the database associated with the AMF 302.

[0108] Upon receiving the get request, the PCF 208 processes the get request to retrieve the set of shared data resources corresponding to the shared policy control request trigger data ID=S1 from an associated database, e.g., the database 210 or the UDSF. Further, the PCF 208 provides the set of shared data resources as the get response to the AMF 302. Upon receiving the set of shared data resources associated with the shared policy control request trigger data ID=S1, at step 312, the AMF 302 subscribes for any modification done by the PCF 208 in the set of shared data resources associated with the shared policy control request trigger data ID=S1 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 208 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 trigger data ID=S1, the AMF 302 updates its database with the set of shared data resources associated with the shared policy control request trigger data ID=S1. Further, based on the subscribe service operation, the AMF 302 may be configured to receive the update response from the PCF 208 for any modifications done by the PCF 208 in the set of shared data resources associated with the shared policy control request trigger data ID=S1 for future service requests.

[0109] Further, at step 314, the PCF 208 is configured to modify the set of shared data resources associated with the shared policy control request trigger data ID=S1 based on the at least one service request. In other words, suppose the at least one service request, i.e., the NPCF AM policy control create request includes an addition of an event trigger known as a slice replacement management (SLICE REPLACE MGMT). In this case, upon receiving the NPCF AM policy control create request, the PCF 208 may be configured to modify the set of shared data resources by adding the event trigger, i.e., the SLICE REPLACE MGMT to the event triggers, i.e., the LOC CH, PLMN CH, and ACCESS TYPE CHassociated with the shared policy control request trigger data ID=S 1. Further, based on the modification, at step 316, the PCF 208 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 trigger data ID=S1. The single notification message sent by the PCF 208 to the AMF 302 is represented as NPCF AM policy control update notify. By consolidating the update response into the single notification message, the PCF 208 avoids sending multiple notification messages corresponding to the modification to the AMF 302. The above approach enables the AMF 302 to efficiently update the set of UEs 104 mapped to the shared policy control request trigger data ID=S1 based on the modification. In other words, the AMF 302 may be configured to apply the modification, i.e., the addition of the SLICE REPLACE MGMT in the set of shared data resources to the set of UEs 104 mapped to the shared policy control request trigger data ID=S 1.

[0110] At step 318, the AMF 302 may be configured to modify the subscription with the PCF 208 for receiving the update response from the PCF 208 based on the modification in the set of shared data resources associated with the shared policy control request trigger data ID=S1. The AMF 302 may be configured to modify the subscription with the PCF 208 using a modified subscription service operation (i.e., a modify subscription service request). For example, the AMF 302 may modify a time for receiving the update response, i.e., the single notification message from the PCF 208 corresponding to the subscription associated with the shared policy control request trigger data ID=S1. 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 trigger data ID=S1. Further, the AMF 302 may anytime unsubscribe from the PCF 208 for receiving the update response of the modification in the set of shared data resources associated with the shared policy control request trigger data ID=S1, as mentioned at step 320. The AMF 302 may unsubscribe with the PCF 208 for receiving the update response corresponding tothe modification based on an unsubscribe service operation (i.e., an unsubscribe service request).[OHl] In an embodiment, the shared data ID (e.g., the shared policy control request trigger data ID=S1) may correspond to a unique identifier (also referred to as a Unique Universal Identifier (UUID)). The Shared Data ID may be unique within the context of the signalling transaction between the AMF 302 and the PCF 208. 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 208. As will be appreciated, the PCF 208 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 208 or in the UDSF associated with the PCF 208. The PCF 208 may retrieve the information as needed upon receiving service requests. Further, when responding to the get request (also referred to as the get service operation), the PCF 208 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.

[0112] In an embodiment, the AMF 302 may retrieve the set of shared data resources from the PCF 208 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), i.e., the AMF 302, is serving a UE 104 for which the cached data is relevant.

[0113] 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 208. If the get request contains an empty array corresponding to a shared data ID received fromthe PCF 208 for a new service request, then the empty array indicates that no shared data resources corresponding to the shared data IDs is currently available at the AMF 302. In such case, the PCF 208 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 208 may not send the set of shared data resources as the get response to the AMF 302.

[0114] In aspects, unless the shared data treatment feature is supported by the AMF 302 and the PCF 208, individual UE data may take precedence over shared data resources. Further, if the shared data treatment feature is supported by the AMF 302 and the PCF 208, 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 208, 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.

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

[0116] 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 208 from the AMF 302, the PCF 208 may be configured to retry sending the single notification message after an expiry of a pre-defined time interval. The pre-definedinterval 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 pre-defined time interval, e.g., Tl+N seconds, where ‘N’ is 30 seconds for retrying the sending of the single notification message by the PCF 208 to the AMF 302. In such a scenario, the single notification message may be sent by the PCF 208 to the AMF 302 after an expiry of 31 seconds.

[0117] FIG. 4 illustrates an exemplary process flow 400 for policy control between the SMF 402 and the PCF 208 in the telecommunication network, in accordance with an embodiment of the present disclosure. The process flow 400 may be implemented by the processor 202 implemented within or with the PCF 208 and the SMF 402. FIG. 4 is explained in conjunction with FIGS. 1, 2 and 3.

[0118] In FIG. 4, a communication flow between the SMF 402 and a PCF 208 for managing the signalling transactions is depicted. In order to manage the signalling transactions or to reduce high signalling transactions between the SMF 402 and the PCF 208, the SMF 402 and the PCF 208 are configured to support the shared data feature and the shared data treatment feature. The shared data feature refers to the feature that allows the SMF 402 and the PCF 208 to access and share common data (i.e., shared data resources) related to the SM policies. Examples of the SM policy may include, but are not limited to, the QoS policy, the resource allocation policy, the charging policy, the session establishment policy, the emergency service policy, and the data offloading policy. The shared data feature is used to provide a consistent view of the SM policy related data (i.e., the shared data resources) across the SMF 402 and the PCF 208. In other words, the shared data feature ensures that the same set of SM policy related data is available for decision-making and enforcement across different network functions (e.g., the SMF 402 and the PCF 208) in the telecommunication network. The shared data treatment feature is a feature that defines how the shared data resources should be handledand processed when the shared data resources are accessed by the different network functions, such as the SMF 402 and the PCF 208. 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 the collection of data that can be shared by multiple UEs 104. For example, the shared data resources include the event triggers, the slice, the presence reporting area information, the set of SM policies, the PLMN subscription data (Custom fields), the session AMBR value, the default QoS, and the like.

[0119] Initially, at step 404, the SMF 402 sends a NPCF_SM policy control create request to the PCF 208. The NPCF SM policy control create request may correspond to the at least one service request. In an embodiment, the at least one service request may be received corresponding the set of PDU sessions associated with the set of UEs 104. In correspondence to the above NPCF SM policy control create request, other examples of the at least one service request may include a NPCF_SM policy control_update request, a NPCF_SM policy control delete request, and a NPCF SM policy control modify request, and the like. The SMF 402 sends the NPCF SM policy control create request to perform policy control actions related to SM policies management.

[0120] Upon receiving the NPCF SM policy control create request, the PCF 208 may check whether the shared data feature and the shared data treatment feature are supported by the SMF 402. Based on performing the check, when the shared data feature and the shared data treatment feature are supported by the SMF 402, at step 406, the PCF 208 is configured to send a NPCF SM policy control create response, i.e., the service response to the SMF 402. The NPCF_SM policy control create response includes a shared policy control request trigger data ID=S1, i.e., the shared data ID. The shared policy control request trigger data ID=S1 includes event triggers, such as a Radio Access Technology (RAT) type change (RAT TY CH), a PLMN change (PLMN CH), and a Presence Reporting Area (PRA) (PRA CH) for a set of UEs (e.g., the UEs 104) associated with a set of users(e.g., the user 102). The RAT TY CH may be an event trigger indicating that the UE has changed its Radio Access Technology, e.g., moving from 5G NR to LTE, or LTE to Wi-Fi. This may require new QoS, charging, or mobility policies. Further, the PLMN CH may be an event trigger that occurs when the UE switches from one PLMN (operator’s network) to another, such as while roaming. Policy updates are needed to align with the new operator’s rules. Further, the PRA CH may be an event trigger for when the UE enters or leaves a configured PRA, which is a defined geographic region monitored by the network 106. The shared policy control request trigger data ID=S1 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 trigger data ID=S1. In an embodiment, the shared policy control request trigger data ID=S1 may be mapped to the set of shared data resources and the set of UEs 104.

[0121] Further, at step 408, the SMF 402 performs a self-check to determine whether the shared policy control request trigger data ID=S 1 received from the PCF 208 is available in the database, i.e., the cache memory associated with the SMF 402. In other words, the SMF 402 checks whether the list of existing shared data IDs associated with the SMF 402 includes the shared policy control request trigger data ID=S1. If the shared policy control request trigger data ID=S1 is not available at the SMF 402, at step 410, the SMF 402 sends the get request to the PCF 208. The get request includes the set of query parameters associated with the shared policy control request trigger data ID=S1. 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 trigger data ID=S1 received from the PCF 208, etc. The get request is sent by the SMF 402 to the PCF 208 for retrieving the set of shared data resources associated with the shared policy control request trigger data ID=S1 that the SMF 402 does not have access to or is missing in the database associated with the SMF 402.

[0122] Upon receiving the get request, the PCF 208 processes the get request to retrieve the set of shared data resources corresponding to the shared policy control request trigger data ID=S1 from an associated database, e.g., the database 210 or the UDSF. Further, the PCF 208 provides the set of shared data resources as the get response to the SMF 402. Upon receiving the set of shared data resources associated with the shared policy control request trigger data ID=S1, at step 412, the SMF 402 subscribes for any modification done by the PCF 208 in the set of shared data resources associated with the shared policy control request trigger data ID=S1 based the at least one service request or future service requests. The SMF 402 may use a subscribe service operation (or a subscribe service request) for subscribing with the PCF 208 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 trigger data ID=S1, the SMF 402 updates its associated database with the set of shared data resources associated with the shared policy control request trigger data ID=S 1. Further, based on the subscribe service operation, the SMF 402 may be configured to receive the update response from the PCF 208 for any modifications done by the PCF 208 in the set of shared data resources associated with the shared policy control request trigger data ID=S1 for future service requests.

[0123] Further, at step 414, the PCF 208 is configured to modify the set of shared data resources associated with the shared policy control request trigger data ID=S1 based on the at least one service request. In other words, suppose the at least one service request, i.e., the NPCF SM policy control create request includes an addition of an event trigger known as an Evolved Packet System (EPS) fallback (EPS fallback). In this case, upon receiving the the NPCF SM policy control create request, the PCF 208 may be configured to modify the set of shared data resources by adding the event trigger, i.e., the EPS fallback to the event triggers, i.e., the RAT TY CH, PLMN CH, and PRA CH associated with the shared policy control request trigger data ID=S1. Further, based on the modification, at step 416, the PCF 208 sends a single notification message, i.e., theupdate response to the SMF 402 regarding the modification done in the set of shared data resources associated with the shared policy control request trigger data ID=S 1. The single notification message sent by the PCF 208 to the SMF 402 is represented as NPCF SM policy control update notify. By consolidating the update response into the single notification message, the PCF 208 avoids sending multiple update notification messages corresponding to the modification to the SMF 402. The above approach enables the SMF 402 to efficiently update the set of PDU sessions corresponding to the set of UEs 104 mapped to the shared policy control request trigger data ID=S1 based on the modification. In other words, the SMF 402 may be configured to apply the modification, i.e., the addition of the EPS fallback in the set of shared data resources, to the set of PDU sessions associated with the set of UEs 104 mapped to the shared policy control request trigger data ID=S1.

[0124] At step 418, the SMF 402 may be configured to modify the subscription with the PCF 208 for receiving the update response from the PCF 208 based on the modification in the set of shared data resources associated with the shared policy control request trigger data ID=S1. The SMF 402 may be configured to modify the subscription with the PCF 208 using a modified subscription service operation (i.e., a modify subscription service request). For example, the SMF 402 may modify a time for receiving the update response, i.e., the single notification message from the PCF 208 corresponding to the subscription associated with the shared policy control request trigger data ID=S1. In an embodiment, the SMF 402 may modify (i.e., extend or reduce) an expiry time corresponding to the subscription associated with the shared policy control request trigger data ID=S1. Further, the SMF 402 may anytime unsubscribe from the PCF 208 for receiving the update response of the modification in the set of shared data resources associated with the shared policy control request trigger data ID=S1, as mentioned at step 420. The SMF 402 may unsubscribe with the PCF 208 for receiving the update response corresponding to the modification based on an unsubscribe service operation (i.e., an unsubscribe service request).

[0125] In an embodiment, the shared data ID (e.g., the shared policy control request trigger data ID=S1) may correspond to a unique identifier (also referred to as a Unique Universal Identifier (UUID)). The Shared Data ID may be unique within the context of the signaling transactions between the SMF 402 and the PCF 208. 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 208. As will be appreciated, the PCF 208 may include a plurality of shared data IDs with its corresponding set of shared data resources. The information (i.e., the plurality of shared data IDs along with its corresponding set of shared data resources) may be stored either locally within the PCF 208 or in the UDSF associated with the PCF 208. The PCF 208 may retrieve the information as needed upon receiving service requests. Further, when responding to the get request (also referred to as the get service operation), the PCF 208 may provide the SMF 402 with a shared data ID and its corresponding shared data resources as the get response. Further, the SMF 402 may store the shared data ID and the corresponding shared data resources data within the associated database or the UDSF for further processing.

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

[0127] 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 SMF 402, are included in the get request that is sent to the PCF 208. If the get request contains an empty array corresponding to a shared data ID received from the PCF 208 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 SMF 402. In such a case, the PCF 208 may send the set of shared data resourcesidentified using the shared data ID as the get response to the SMF 402. In an embodiment, if the get request sent by the SMF 402 does not include the set of query parameters, then the PCF 208 may not send the set of shared data resources as the get response to the SMF 402.

[0128] In addition, unless the shared data treatment feature is supported by the SMF 402 and the PCF 208, individual UE data may take precedence over the shared data resources. Further, if the shared data treatment feature is supported by the SMF 402 and the PCF 208, 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 SMF 402 and the PCF 208, 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.

[0129] In an embodiment, when any shared data resources are modified by the PCF 208 and the SMF 402 is subscribed to receive updates, the PCF 208 may send the single notification message to the SMF 402. Upon receiving the single notification message, the SMF 402 will update the set of shared data resources for all PDU sessions (i.e., the set of PDU sessions) corresponding to the set of UEs associated with the same shared data ID.

[0130] 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 208 from the SMF 402, the PCF 208 may be configured to retry sending the single notification message after an expiry of a pre-defined time interval. The pre-defined interval may be configured by network operators based on their requirements. For instance, suppose a network operator may have configured an initial pre-definedinterval 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 pre-defined time interval, e.g., Tl+N seconds, where ‘N’ is 30 seconds for retrying the sending of the single notification message by the PCF 208 to the SMF 402. In such a scenario, the single notification message may be sent by the PCF 208 to the SMF 402 after an expiry of 31 seconds.

[0131] FIG. 5 illustrates a flow chart of a method for policy control in the telecommunication network, in accordance with an embodiment of the present disclosure. The method 500 may be implemented by the processor 202 implemented within or with the PCF 208 and the AMF 302 or the SMF 402. FIG. 5 is explained in conjunction with FIGS. 1, 2, 3, and 4.

[0132] At step 502, the PCF may receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function may include one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy. The at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies and a set of AM policy sessions in case of AM policies, associated with a set of the UEs.

[0133] In an embodiment, the at least one service request include an AM policy control create request, update request, delete request, or modify request. The at least one AM policy includes an access type change trigger policy, a location change reporting policy, an access and mobility restriction policy, a network slice access control policy, a registration area update policy, or a mobility restriction enforcement policy.

[0134] In another embodiment, the at least one service request includes an SM policy control create request, update request, delete request, or modify request. Theat least one SM policy includes a Quality of Service (QoS) policy, a resource allocation policy, a charging policy, a session establishment policy, an emergency service policy, or a data offloading policy.

[0135] At step 504, the PCF may transmit a service response including a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. The shared data ID uniquely identifies a group of commonly applicable policies that may be mapped across multiple UEs or multiple sessions, avoiding per-session duplication.

[0136] In an embodiment, the PCF may perform a check to determine whether the AMF supports a shared data feature and a set of shared data treatment features. Such support is required to apply the modifications to the AM policy data resources for the set of UEs based on the shared data ID. Further, the shared data ID is mapped to a set of policy data resources including AM policy data resources and to the associated set of UEs. when the request involves AM policies, the PCF determines whether the AMF supports SharedData and SharedDataTreatment features. The features allow the AMF to apply shared policy modifications across multiple UEs using a single Shared Data ID reference.

[0137] In another embodiment, the PCF may control the policy control signalling by reducing transactions between the PCF and SMF over an N7 interface, reduces redundant policy control transactions by consolidating updates. Further, the shared data ID is mapped to a set of policy data resources including SM policy data resources and to the associated set of UEs.

[0138] At step 506, the PCF may modify the set of policy data resources associated with the shared data ID based on the at least one service request. In an example, if a new QoS rule or event trigger is applied, the PCF updates the relevant shared policy data accordingly.

[0139] At step 508, the PCF may send an update response corresponding to the modification in the set of policy data resources associated with the shared data IDto the network function. The network function apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response. The PCF may enable synchronized, bulk updates with minimal signalling overhead, ensuring that all affected sessions are updated efficiently and consistently across the network.

[0140] In an exemplary embodiment, in a 5G telecommunication network where a mobile operator needs to update the Quality of Service (QoS) profile for a large group of enterprise users belonging to the same organization. Each of the users operates the UE that has an active PDU session managed by the Session Management Function (SMF). Conventionally, when the PCF receives a bulk modification request to adjust the QoS profiles, the PCF may generate an individual update notify message for each active PDU session. For hundreds or thousands of UEs, this results in a massive surge of signalling traffic over the N7 interface between the PCF and SMF, creating network inefficiencies and potential delays in enforcement. The PCF may associate the updated QoS profile with a Shared Data Identifier (ID) (e.g., SharedQoS IDl) that maps to the set of common QoS parameters applicable to all enterprise users. The Shared Data ID is already cached at the SMF for all PDU sessions belonging to that enterprise group. Upon receiving the bulk modification request, the PCF modifies the policy data resources corresponding to SharedQoS IDl and generates a single update response referencing the Shared Data ID. Further, the update response is transmitted to the SMF.

[0141] FIG. 6 illustrates an exemplary computer system 600 in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 6, the computer system 600 may include an external storage device 610, a bus 620, a main memory 630, a read-only memory 640, a mass storage device 650, communication port(s) 660, and a processor 670. A person skilled in the art will appreciate that the computer system 600 may include more than one processor and communication ports. The processor 670 may include various modules associatedwith embodiments of the present disclosure. The communication port(s) 660 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 port(s) 660 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 600 connects.

[0142] The main memory 630 may be a Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 640 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor 670. The mass storage device 650 may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device 650 includes, but is 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), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks.

[0143] The bus 620 communicatively couples the processor 670 with the other memory, storage, and communication blocks. The bus 620 may be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCLX) 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 670 to the computer system 600.

[0144] Optionally, operator and administrative interfaces, e.g. a display, keyboardjoystick, and a cursor control device, may also be coupled to the bus 620 to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 660. Components described above are meantonly to exemplify various possibilities. In no way should the aforementioned exemplary computer system 600 limit the scope of the present disclosure.

[0145] In an embodiment, the disclosure provides a system for policy control in a telecommunication network. The system includes a Policy Control Function (PCF). The PCF may be configured to receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function includes one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs). Further, the PCF is configured to transmit a service response including a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. The PCF may be configured to modify the set of policy data resources associated with the shared data ID based on the at least one service request. Further, the PCF is configured to send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function. The network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs 104 mapped to the shared data ID, based on the update response.

[0146] In another embodiment, a non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a Policy Control Function (PCF) in a telecommunication network, cause the one or more processors to receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function includes one of a Session Management Function (SMF) when the received service request is associated withSM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs). Further, the PCF, cause the one or more processors to, transmit a service response including a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. The PCF may further cause the one or more processors to modify the set of policy data resources associated with the shared data ID based on the at least one service request. Further, the PCF, cause the one or more processors to send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function. The network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs 104 mapped to the shared data ID, based on the update response.

[0147] In yet another embodiment, a User Equipment (UE) communicatively coupled to a system, said coupling includes steps of receiving a connection request. Further, the coupling include step of sending an acknowledgment of the connection request to the system. The coupling include step of transmitting data from the UE to the system. The system is configured for managing policy control signalling in a telecommunication network. The system may include a Policy Control Function (PCF) configured to receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function. The network function includes one of a Session Management Function (SMF) or an Access and Mobility Management Function (AMF), and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs). Further, the PCF is configured to transmit a serviceresponse including a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request. Further, the PCF is configured to modify the set of policy data resources associated with the shared data ID based on the at least one service request. The PCF is further configured to send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function. The network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response.

[0148] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0149] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0150] 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 is to be implemented merely as illustrative of the disclosure and not as a limitation.

[0151] The present disclosure offers significant technical advancements in optimizing policy control signalling within next-generation 5G core networks. Conventional policy control mechanisms for AMPolicyControl and SMPolicyControl rely on repetitive and session-specific update notifications between the Policy Control Function (PCF) and consumer functions such as the Access and Mobility Management Function (AMF) or the Session Management Function (SMF). In scenarios involving bulk subscription modifications or deletions, the conventional method generate a flood of notification messages, leading to signalling storms, network congestion, and inefficient utilization of resources. Conventional solutions lack mechanisms for shared handling of policy data across multiple sessions or UEs, failing to scale efficiently under dense subscriber environments. To overcome the limitations, the present disclosure introduces the shared data and shared data treatment feature support across the N15 and N7 interfaces. The present disclosure enables the PCF to send a single aggregated notification message for bulk policy modifications or deletions, rather than multiple session-specific updates, shared data resources, representing collections of commonly applicable policy parameters (e.g., event triggers, QoS rules, service area restrictions, RFSP index, subscription data), are uniquely identified by shared data IDs and cached at consumer functions. Upon a change in shared data, the PCF transmits one update message referencing the shared data ID, allowing the AMF or SMF to seamlessly update multiple active policy associations or PDU sessions in real-time.

[0152] By incorporating new service operations such as Get, Subscribe, modify subscription, unsubscribe for AM / SM policy control services, the present disclosure enables dynamic subscription management, efficient retrieval of shared policy data, and flexible update propagation. The design significantly reduces redundant signalling traffic, enhances scalability, and ensures consistent policy enforcement across a large user base. Furthermore, the shared data treatment instructions provide granular precedence rules between UE-specific data and shared data, ensuring accuracy and flexibility in policy application.TECHNICAL ADVANCEMENTS

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

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

[0155] The present disclosure provides an optimized approach for reducing the signalling transactions between the PCF and a Session Management Function (SMF) by enabling the PCF to consolidate multiple Protocol Data Unit (PDU) session updates corresponding to a Session Management (SM) policy update into a single notification message. The consolidated single notification message is then sent to the SMF, thereby avoiding the need to send individual update message for each PDU session.

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

[0157] 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 AM policy control update notify message) exchanged between the PCF and the AMF, reducing load on the PCF and the AMF.

[0158] The present disclosure provides a streamlined approach for managing the signalling transactions between the PCF and the AMF by integration of a shared data feature and a shared data treatment feature within the PCF and the AMF over an N15 interface.

[0159] The present disclosure provides a streamlined approach for optimizing the signalling transactions between the PCF and the SMF by integrating a shared data feature and a shared data treatment feature within the PCF and the SMF over an N7 interface.

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

[0161] 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 AM policy control services and SM policy control services to enhance capability of the PCF and the AMF and / or the SMF in managing AM policies and SM policies more effectively.

Claims

1. Claims1. A method for policy control in a telecommunication network, the method comprising: receiving, by a Policy Control Function (PCF), at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function, wherein the network function comprises one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs); transmitting, by the PCF, a service response comprising a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request; modifying, by the PCF, the set of policy data resources associated with the shared data ID based on the at least one service request; and sending, by the PCF, an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function, wherein the network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response.

2. The method as claimed in claim 1, wherein the at least one service request comprises an AM policy control create request, update request, delete request, or modify request.

3. The method as claimed in claim 1, wherein the at least one AM policy comprises an access type change trigger policy, a location change reporting policy, an access and mobility restriction policy, a network slice access control policy, a registration area update policy, or a mobility restriction enforcement policy.

4. The method as claimed in claim 1, wherein transmitting the service response comprises: performing, by the PCF, a check to determine whether the AMF supports a shared data feature and a set of shared data treatment features, wherein such support is required to apply the modifications to the AM policy data resources for the set of UEs based on the shared data ID.

5. The method as claimed in claim 1, wherein the shared data ID is mapped to a set of policy data resources comprising AM policy data resources and to the associated set of UEs.

6. The method as claimed in claim 1, wherein the at least one service request comprises an SM policy control create request, update request, delete request, or modify request.

7. The method as claimed in claim 1, further comprising: controlling policy control signalling by reducing transactions between the PCF and SMF over an N7 interface.

8. The method as claimed in claim 1, wherein the shared data ID is mapped to a set of policy data resources comprising SM policy data resources and to the associated set of UEs.

9. The method as claimed in claim 1, wherein the at least one SM policy comprises a Quality of Service (QoS) policy, a resource allocation policy, a charging policy, a session establishment policy, an emergency service policy, or a data offloading policy.

10. A system for policy control in a telecommunication network, the system comprising: a Policy Control Function (PCF) configured to: receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function, wherein the network function comprises one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs); transmit a service response comprising a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request; modify the set of policy data resources associated with the shared data ID based on the at least one service request; and send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function, wherein the network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response.

11. The system as claimed in claim 10, wherein the at least one service request comprises an AM policy control create request, update request, delete request, or modify request.

12. The system as claimed in claim 10, wherein the at least one AM policy comprises an access type change trigger policy, a location change reporting policy, an access and mobility restriction policy, a network slice access control policy, a registration area update policy, or a mobility restriction enforcement policy.

13. The system as claimed in claim 10, wherein the PCF is further configured to perform a check to determine whether the AMF supports a shared data feature and a set of shared data treatment features, wherein such support is required to apply the modifications to the AM policy data resources for the set of UEs based on the shared data ID.

14. The system as claimed in claim 10, wherein the shared data ID is mapped to a set of policy data resources comprising AM policy data resources and to the associated set of UEs.

15. The system as claimed in claim 10, wherein the at least one service request comprises an SM policy control create request, update request, delete request, or modify request.

16. The system as claimed in claim 10, wherein the PCF is further configured to control policy control signalling by reducing transactions between the PCF and SMF over an N7 interface.

17. The system as claimed in claim 10, wherein the shared data ID is mapped to a set of policy data resources comprising SM policy data resources and to the associated set of UEs.

18. The system as claimed in claim 10, wherein the at least one SM policy comprises a Quality of Service (QoS) policy, a resource allocation policy, a charging policy, a session establishment policy, an emergency service policy, or a data offloading policy.

19. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a Policy Control Function (PCF) in a telecommunication network, cause the one or more processors to: receive at least one service request associated with at least one of a Session Management (SM) policy and an Access and Mobility (AM) policy from a network function, wherein the network function comprises one of a Session Management Function (SMF) when the received service request is associated with SM policy and an Access and Mobility Management Function (AMF) when the received service request is associated with AM policy, and the at least one service request corresponds to a set of communication sessions, including a set of Protocol Data Unit (PDU) sessions in case of SM policies or a set of AM policy sessions in case of AM policies, associated with a set of User Equipments (UEs); transmit a service response comprising a shared data Identifier (ID) associated with a set of policy data resources to the network function in response to receiving the at least one service request; modify the set of policy data resources associated with the shared data ID based on the at least one service request; and send an update response corresponding to the modification in the set of policy data resources associated with the shared data ID to the network function, wherein the network function is configured to apply the modifications in the set of policy data resources to each of the set of communication sessions associated with the set of UEs mapped to the shared data ID, based on the update response.

20. A User Equipment (UE) (104) communicatively coupled to a system (108), said coupling comprises steps of: receiving a connection request; sending an acknowledgment of the connection request to the system (108); andtransmitting data from the UE (104) to the system (108), wherein the system (108) is configured for managing policy control signalling in a telecommunication network as claimed in claim 10.

Images