System and method for managing a subscriber profile update in a network

Abstract

The present disclosure provides a system (108) and a method (500) for managing a subscriber profile update in a network (106). External resources (110) coupled with the system (108) notify a gateway (302) (e.g., PWG) of any changes made to the subscriber profile pertaining to at least one user equipment (UE) policy. Upon receipt of this notification, the gateway (302) subsequently communicates these changes to a first network function (NF) (304) (e.g., PCF) via a database stream. Once the first NF (304) receives the notification of the updated subscriber profile, the first NF (304) may retrieve and compare relevant data stored in a predetermined custom field associated with the UE (104) to ensure whether any modifications have occurred within the subscriber profile. Based on the comparison, the first NF (304) initiates the N1N2 message transfer request towards a second NF (306) (e.g., AMF).

Description

SYSTEM AND METHOD FOR MANAGING A SUBSCRIBER PROFILE UPDATE IN A NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (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 generally to the field of telecommunications. In particular, the present disclosure relates to a system and a method for managing a subscriber profile update in a network.DEFINITIONS

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

[0004] The term “Network Function (NF)” used hereinafter in the specification refers to a component within the 5G network architecture that performs specific roles and services. The design of NFs in 5G allows for greater flexibility, scalability, and efficiency compared to previous generations of mobile networks. Each NF operates independently but can interconnect with other NFs to support a wide range of services. Examples of the NFs may include, but are not limited to, User Plane Function (UPF), the Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Exposure Function (NEF), and Policy Control Function (PCF).

[0005] The term “Provisioning Gateway (PGW)” used hereinafter in the specification refers to a component that enables the configuration and management of subscriber profiles within the network infrastructure. The PGW is an intermediary entity that facilitates seamless interactions between the network service provider and the end-user equipment, ensuring that the necessary settings and parameters are appropriately applied to optimize user experience.

[0006] The term “Access and Mobility Management Function (AMF)” used hereinafter in the specification refers to a network function responsible for handling user registration, authentication, connection management, and mobility management procedures. The AMF plays an important role in ensuring that subscribers maintain continuous connectivity while transitioning across different network domains.

[0007] The term “Policy Control Function (PCF)” used hereinafter in the specification refers to a network function responsible for the formulation, decision, and enforcement of policy rules governing control plane behavior. The PCF is integral to managing network policies concerning access permissions, quality of service parameters, and allocation of network resources, thus ensuring optimal service delivery and compliance with operational standards.

[0008] The phrase “Subscriber Profile” used hereinafter in the specification refers to a collection of data and configuration parameters associated with a subscriber. Such data may include, but is not limited to, subscriber identification information, device characteristics, subscribed service plans, network access preferences, policy parameters, historical usage information, and billing attributes. The subscriber profile enables tailored service delivery and facilitates effective network and policy management.

[0009] The term “Fulfillment Management System (FMS)” used hereinafter in the specification refers to an external system that is responsible for the oversight andexecution of provisioning requests directed towards various network functions. The FMS plays a crucial role in monitoring the fulfillment process and transmitting provisioning requests, including detailed specifications related to the offered network service plans, thereby facilitating efficient service provisioning.

[0010] The expression “Predetermined Custom Field” used hereinafter in the specification refers to a user-defined field that is not inherently included in the default schema of a standard system, application, or database. Custom fields allow users to extend the system's capabilities by incorporating additional data that aligns with their specific requirements or use cases, thereby enhancing the overall functionality of the system.

[0011] The term “Custom Field 5” used hereinafter in the specification refers to a particular customizable field or parameter designated for storing subscriber policies to be implemented within a User Equipment (UE). This allows for tailored policy applications based on individual subscriber needs.

[0012] The expression “Subscriber Permanent Identifier (SUPI)” used hereinafter in the specification refers to a unique identifier that is permanently assigned to a subscriber within the network framework. The SUPI remains unchanged for the subscriber, facilitating consistent identification across various services and sessions. The SUPI is crucial for effective subscriber management and network operations, ensuring that each subscriber can be distinctly recognized and authenticated, thereby streamlining access to services and maintaining security protocols within the system.

[0013] The term “N1N2 Message Transfer Request” used hereinafter in the specification refers to a signaling procedure that enables the NF, such as the PCF, to deliver N1 and / or N2 messages to the UE through the AMF. The N1 message represents a Non-Access Stratum (NAS) message destined for the UE, whereas the N2 message represents an Access Stratum (AS) message intended for delivery to the RadioAccess Network (RAN). The N1N2 message transfer request operation allows an originating network function to trigger transmission of configuration updates, policy changes, or other control information to the UE via the AMF, ensuring consistent policy enforcement and session continuity.

[0014] The term “Data Repository” used hereinafter in the specification refers to a persistent storage system or database configured to maintain subscriber-related information, such as subscriber profiles, policy parameters, and service data. The data repository may be implemented as a relational database (e.g., structured query language (SQL) database) or a non-relational database (e.g., a distributed Not Only SQL (NoSQL) database accessible by multiple network functions, depending on scalability and performance requirements. The data repository ensures durability, consistency, and accessibility of subscriber data across network functions such as the PCF and the AMF.

[0015] The term “Local Cache” used hereinafter in the specification refers to a temporary or in-memory data storage maintained by the NF for rapid access to subscriber session information or policy data. The local cache stores recently accessed or active session details, such as the SUPI, session ID, and policy parameters, to minimize repeated database lookups and reduce signaling latency. The local cache enables a first network function (e.g., the PCF) to determine whether a session associated with a specific subscriber identifier is currently active and to perform comparisons between cached data and updated information retrieved from the data repository.

[0016] These definitions are in addition to those expressed in the art.BACKGROUND

[0017] 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 presentdisclosure. 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.

[0018] In a modern network, the network service providers offer a wide range of service plans to subscribers based on the requirements of the subscriber. Each service plan includes details of the specific services, features, and pricing associated with the services. Implementing a service plan is crucial for both the subscriber and network service providers, as the policies of each service plan differ from another plan. The network service provider assigns the service plans through a policy control function (PCF). The PCF routes the policies related to the service plan to the user. The network service provider encounters difficulty while the subscriber modifies the service plan, as the policies would change according to the newly adopted plan.

[0019] In the conventional methods, the service plan-related changes are recorded by an Online Charging System (OCS) in a network. The OCS sends a notification to a charging function (CHF) regarding the service plan changes, along with the policy changes. The CHF sends a Spending Limit Notification Request (SNR) to the PCF using a Sy interface. The Sy interface acts as a reference point between the PCF and the CHF. The SNR request is used by the CHF to report the change of status or to notify the status of one or more changes in the service plan of the subscriber. The change in the service plan involves sending and receiving a plurality of requests between various network functions, such as the PCF, the CHF, the OCS, a Unified Data Repository (UDR), a Session Management Function (SMF), a User Plane Function (UPF), etc. The conventional methods for modifying the service plan add significant cost to the network as the modification process involves unnecessary signaling and requests between various network functions. At times, the PCF is flooded with lots of request messages that lead to network load.

[0020] Further, the network service providers employ multiple subscriber managers to manage, control, and modify the service plans and network loads in the network. The multiple subscriber managers monitor and handle the network load. However, the monitoring and handling consume more time and effort and pave the way for network disruptions.

[0021] Therefore, there is a need for a system and a method that overcomes the limitations of the prior art.OBJECTIVES OF THE DISCLOSURE

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

[0023] An objective of the present disclosure is to provide a system and a method for managing a subscriber profile update in a network.

[0024] Another objective of the present disclosure is to provide a system and a method that uses a database stream-based notification mechanism that enables realtime propagation of subscriber profile updates from a Provisioning Gateway (PGW) to one or more Network Functions (NFs), such as a Policy Control Function (PCF).

[0025] Another objective of the present disclosure is to provide a system and a method for detecting and evaluating changes in a predetermined custom field (for example, Custom Field 5) of the subscriber profile to determine whether the associated User Equipment (UE) policy requires modification.

[0026] Another objective of the present disclosure is to provide a system and a method for updating the UE policy based on the subscriber profile.

[0027] Another objective of the present disclosure is to provide a system and a method that eliminates intermediate signaling dependencies between a ChargingFunction (CHF) and an Online Charging System (OCS) by enabling direct notification from the PGW to the PCF through a database stream, thereby reducing network cost and signaling overhead.

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

[0029] In an exemplary embodiment, a method for managing a subscriber profile update in a network is described. The method includes receiving, by a provisioning gateway (PGW), an update request for a subscriber profile from one or more external sources. The method further includes updating, by the PGW, the subscriber profile in a data repository based on the update request and modifying a predetermined custom field of the subscriber profile in the data repository. The method also includes broadcasting, by the PGW, via a database stream, a notification comprising at least one subscriber identifier associated with the updated subscriber profile. The method further includes determining, by a first network function (NF), whether a session associated with the at least one subscriber identifier exists in a local cache upon receiving the broadcasted notification.

[0030] In an embodiment, if the session exists in the local cache, the first NF retrieves the updated subscriber profile from the data repository and compares the predetermined custom field in the retrieved subscriber profile with a corresponding cached value stored to detect whether the predetermined custom field has changed relative to the cached value.

[0031] In an embodiment, upon detecting a change in the predetermined custom field, the first NF performs at least one operation to manage the subscriber profile in the data repository.

[0032] In an embodiment, if the session does not exist in the local cache, the first NF foregoes initiation of the at least one operation. The at least one operation includes initiating a network signaling procedure to update a subscriber policy at a second network function. The network signaling procedure includes initiating, by the first NF, an N1N2 message transfer request towards a second NF to apply an updated subscriber policy. The first NF (304) triggers the N1N2 message transfer request upon detecting the change in the predetermined custom field.

[0033] In an embodiment, the database stream includes a publish-subscribe communication channel configured to transmit real-time update events.

[0034] In an embodiment, the local cache stores active session context data.

[0035] In an embodiment, the method further includes monitoring, by the firstNF, the database stream at predefined configurable intervals for the notification broadcasted by the PGW. The first NF (304) is configured to subscribe to the database stream to receive push notifications.

[0036] In another exemplary embodiment, a system for managing a subscriber profile update in a network is disclosed. The system includes a data repository and a provisioning gateway (PGW) coupled to the data repository. The PGW is configured to receive an update request for a subscriber profile from one or more external sources, update the subscriber profile in the data repository based on the update request, modify a predetermined custom field of the subscriber profile in the data repository, and broadcast, via a database stream, a notification comprising at least one subscriber identifier associated with the updated subscriber profile. The system further includes a first network function (NF) configured to receive the broadcasted notification from the PGW and determine whether a session associated with the at least one subscriber identifier exists in a local cache.

[0037] In another exemplary embodiment, a user equipment (UE) communicatively coupled with a system in a network is disclosed. The coupling includes receiving, by the system, a connection request; sending, by the system, an acknowledgment of the connection request to the user equipment; and transmitting a plurality of signals in response to the connection request. The system is configured for managing a subscriber profile update as described in the aforementioned embodiments.

[0038] In yet another exemplary embodiment, a computer program product is disclosed. The computer program product includes a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing a subscriber profile update in a network. The method includes receiving, by a processing entity, an update request for a subscriber profile from one or more external sources, updating the subscriber profile in a data repository based on the update request, modifying a predetermined custom field of the subscriber profile in the data repository, broadcasting, by the processing entity, via a database stream, a notification comprising at least one subscriber identifier associated with the updated subscriber profile, and determining, by a first network function (NF), whether a session associated with the at least one subscriber identifier exists in a local cache upon receiving the broadcasted notification.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0039] 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 is 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 appreciatedby those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.

[0040] FIG. 1 illustrates an exemplary network architecture of a system for managing a subscriber profile update in a network, in accordance with an embodiment of the present disclosure.

[0041] FIG. 2 illustrates an exemplary block diagram of the system configured for managing the subscriber profile update in the network, in accordance with an embodiment of the present disclosure.

[0042] FIG. 3 illustrates an exemplary system architecture for managing the subscriber profile update in the network, in accordance with an embodiment of the present disclosure.

[0043] FIG. 4 illustrates an exemplary flow diagram of a method for managing the subscriber profile update in the network, in accordance with an embodiment of the present disclosure.

[0044] FIG. 5 illustrates another exemplary flow diagram of a method for managing the subscriber profile update in the network, in accordance with an embodiment of the present disclosure.

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

[0046] 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 - Network 108 - System110 - External resources200 - Block diagram202 - Processor(s)204 - Memory 206 - Interface(s)208 - Provisioning gateway (PGW)210 - Data repository300 - Exemplary system architecture302 - Gateway 304 - First network function306 - Second network function400 - Flow Diagram500 - Method600 - Computer system610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

[0047] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may 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.

[0048] 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 theart 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.

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

[0050] 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 additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

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

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

[0053] 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 not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any 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 otherequivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

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

[0055] 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 the 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. Further, 6G successor to 5G is expected to provide significantly high data speed with reduced latency, which may offer improved connectivity for a vast number of devices concurrently. The capabilities of 6G enable new types of applications and services, such as advanced augmented reality (AR) and virtual reality (VR), holographic communications, and more immersive digital experiences. 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 the boundaries 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 of connecting and interacting with technology.

[0056] In telecommunications, the network service providers offer a wide variety of service plans to their subscribers. The service plans refer to structured offerings provided by the network service providers that outline the specific services, features, and pricing available to subscribers. These service plans typically include various options for voice, data, messaging, and additional services such as streaming, gaming, or cloud storage. The service plans are designed to cater to different user needs and preferences, allowing subscribers to choose packages that align with their usage patterns and budget. The network service providers customize these service plans based on subscriber needs to enhance both network performance and user experience. By utilizing service plans, the network service providers can effectively manage subscriber profiles and interactions, allowing for more accurate tracking of usage and billing. However, when subscribers wish to modify their service plans, providers often encounter challenges in implementing these changes. The modification process can become complex due to the numerous requests and signaling required among various network functions, which may include the Policy Control Function (PCF), Charging Function (CHF), Online Charging System (OCS), Unified Data Repository (UDR), Session Management Function (SMF), and User Plane Function (UPF).

[0057] In conventional methods, any changes to the service plans are documented by the OCS within the network. The OCS notifies the CHF about these service plans and policy changes. In turn, the CHF generates a Spending Limit Notification Request (SNR) to the PCF using a Sy interface, which acts as a communication link between the two functions. The SNR is employed by the CHF toreport status changes or to inform the PCF of updates regarding the subscriber's service plan.

[0058] The conventional process of modifying service plans may lead to significant costs for the network due to unnecessary signaling and requests exchanged between various functions. Additionally, the PCF may become overwhelmed with a high volume of request messages, increasing the overall network load. Managing these excess requests often requires manual intervention, consuming valuable time and resources. Moreover, the surge of requests may result in network disruptions and disturbances.

[0059] Hence, there is a need to provide a method and a system that can address the shortcomings of existing solutions.

[0060] In modern network architectures, the subscriber profile for each user is established by the Access and Mobility Management Function (AMF). The subscriber profile encompasses one or more User Equipment (UE) policies that are directly linked to the service plan selected by the subscriber. Each UE policy is assigned to the corresponding UE via the Policy Control Function (PCF).

[0061] For example, a UE policy may be designed to monitor the network usage of the UE, ensuring that billing is conducted fairly based on actual consumption. The process of assigning a UE policy is initiated by the AMF, which sends a UE policy create request to the PCF. Upon successful creation of the policy, the PCF responds by issuing an N1N2 Message subscribe request to the AMF. Following a successful subscription process, the PCF may subsequently send an N1N2 Message transfer request to the AMF, facilitating the effective communication and implementation of the assigned UE policies. This structured interaction between the AMF and PCF ensures that subscriber profiles are accurately managed and that policies areappropriately applied, thereby optimizing the user experience and ensuring compliance with service agreements.

[0062] The present disclosure relates to a method and a system for managing a subscriber profile update in the network. A Fulfillment Management System (FMS) is configured to notify a Provisioning Gateway (PGW) of any changes made to the subscriber profile pertaining to at least one user equipment (UE) policy. Upon receipt of this notification, the PGW subsequently communicates these changes to the PCF via an established database stream. Once the PCF receives the notification of the updated subscriber profile, it is configured to retrieve and compare relevant data stored in a custom field associated with the UE to ensure whether any modifications have occurred within the subscriber profile. Based on the comparison, the PCF initiates the N1N2 message transfer request towards the AMF. This action ensures that the revised policy is effectively transmitted to the UE, thereby facilitating the application of the updated subscriber profile in real-time.

[0063] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1- 6.

[0064] FIG. 1 illustrates an exemplary network architecture (100) of a system (108) for managing a subscriber profile update, in accordance with an embodiment of the present disclosure.

[0065] 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 collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as the UE (104). Although only three UEs (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.

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

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

[0068] Referring to FIG. 1, the UE (104) is communicatively coupled with the system (108) through a network (wireless communication network) (106) for sending or receiving various types of data. The coupling comprises steps of receiving, by the system (108), a connection request, sending, by the system (108), an acknowledgment of the connection request to the UE (104), and transmitting a plurality of signals in response to the connection request. The system (108) is configured to manage the subscriber profile update to update the UE policy based on the subscriber profile.

[0069] In an embodiment, the network (106) may include at least one of a fifth generation (5G) network, 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.

[0070] 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 orcurrent levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0071] In an embodiment, the system (108) is further coupled with one or more external resources (110). In an example, the one or more external resources (110) may include, but are not limited to, a Fulfillment Management System (FMS), and a Network Management System (NMS). In an aspect, the FMS may be configured to monitor the fulfillment process and transmit requests, including details regarding the network plans to provide efficient network service. The FMS adapts the changes according to the network service changes to avoid unnecessary network disruption. In another aspect, the NMS is used to monitor, manage and optimize network resources and performance. The NMS may be configured to track the performance to provide an enhanced network service.

[0072] In an aspect, the external resources (110) support functions like network inventory, service provisioning, network configuration and fault management. The external resources (110) may set up and configure multiple telecommunication services, such as a data plan, a voice plan, a game plan, or other communication service plans for the subscriber or user. The external resources (110) may initiate a service provisioning process in the network. The service provisioning process involves preparing and equipping the network to enable the subscribed telecommunication services to the users (subscribers). For example, the user (subscriber) subscribes to a data service plan for the UE (104). The subscriber profile of the user may be updated according to the subscribed data service plan. The external resources (110) may receive the subscriber profile updates from a network service provider. For example, when theuser recharges for a voice-calling plan. The network service provider may need to implement the plan in the subscriber profile of the user (102). The network service provider may send the update regarding the subscriber profile to the external system (110). Upon receiving the updated subscriber profile, the external resources (110) may initiate a subscriber profile update request and transmit the initiated the subscriber profile update request to a gateway. In an example, the gateway may be a provisioning gateway (PGW). In an aspect, the system (108) may be embedded in the PGW. The PGW may initialize management of an update in the subscriber profile and update the UE policy based on the subscriber profile update. In another example, when the user recharges for the voice calling service plan, the external resources (110) receives the update that the user has subscribed to the voice calling service plan. The external resources (110) may forward the subscriber profile of the user to the PGW to update the UE policy based on the updated subscriber profile.

[0073] 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).

[0074] FIG. 2 illustrates an exemplary block diagram (200) of the system (108), in accordance with an embodiment of the present disclosure.

[0075] Referring to FIG. 2, in an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the oneor 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 random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.

[0076] 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). Examples of such components include, but are not limited to, a provisioning gateway (PGW) (208) and a database (210).

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

[0078] In an embodiment, the PGW (208) may be configured to manage the subscriber profile update in the network (106). The PGW (208) may be embedded within a network function or may be associated with the network function. The network function may include a first network function (NF) (e.g., a policy control function (PCF)), and a second NF (e.g., an access and mobility management function (AMF)). While the embodiments describe the interaction between the PCF and the AMF, the disclosure is not limited to these two network functions. In other embodiments, the first and second Network Functions (NFs) may correspond to or interoperate with other control-plane or service-based functions, such as the Session Management Function (SMF), Network Exposure Function (NEF), Network Data Analytics Function (NWDAF), or other network entities that require subscriber policy synchronization or session management. The architecture supports deployment of these NFs in clustered, containerized, or cloud- native configurations for enhanced scalability and redundancy.

[0079] In an embodiment, the PGW (208) may be configured to receive an update request for a subscriber profile from one or more external systems (110). The one or more external systems (110) may include, but are not limited to, a Fulfillment Management System (FMS) and a Network Management System (NMS). In an embodiment, the FMS may be configured to monitor the fulfillment process and transmit requests, including details regarding the network plans to provide efficient network service. The FMS adapts the changes according to the network service changes to avoid unnecessary network disruption. In an alternative embodiment, the NMS is used to monitor, manage and optimize network resources and performance. TheNMS may be configured to track the performance to provide an enhanced network service.

[0080] Although examples reference external systems such as the FMS and the NMS, the present disclosure is not restricted to these resources alone. In other implementations, the PGW (208) may interface with a variety of external orchestration, provisioning, or business support systems (OSS / BSS), including but not limited to Customer Relationship Management (CRM) platforms, Service Exposure Platforms (SEPs), or third-party policy orchestration systems. The described framework is therefore extensible to diverse network management environments, ensuring seamless integration with existing and future 5G and 6G architectures.

[0081] The update request for the subscriber profile may include, but is not limited to, profile information containing subscriber identification, contact information, and service plan details associated with the user’s subscription. For example, when a user modifies or subscribes to a new service plan, such as a gaming, voice, or data package, it becomes necessary to enable this plan on the UE (104). The FMS (110) may receive notifications regarding the user's subscription from the network service provider through the network (106). Subsequently, the FMS (110) transmits the updated subscriber profile to the PGW (208) to manage and update the subscriber profile.

[0082] The PGW (208) may be configured to extract one or more information from the update request by employing a parsing process to identify the type of update and the corresponding subscriber attributes to be modified. The parsing process involves systematically analyzing and interpreting the subscriber profile update request to identify and extract relevant details necessary for updating the subscriber profile. The extracted one or more information may encompass various components, including a subscriber profile, a source of the request, a type of update being made, a timestampindicating when the request was generated, and a log record documenting the history of changes of plans and policies.

[0083] In an embodiment, the PGW (208) may be configured to update the subscriber profile based on the received update request. The update operation may include changing general subscriber information such as service plan identifiers, plan validity periods, contact information, billing identifiers, or subscription states (e.g., active, suspended, or expired). These updates ensure that the subscriber profile maintained in the data repository (210) reflects the latest provisioning and service configuration parameters received from one or more external sources, such as the FMS or the NMS. The update process may include maintaining transaction logs or version control to ensure data integrity and consistency across multiple systems.

[0084] In an embodiment, the PGW (208) may be configured to modify a predetermined custom field associated with the subscriber profile in the data repository (210). In an exemplary aspect, the subscriber profile may include one or more custom fields, such as a subscriber identity, a subscriber name, a service plan, a location, a subscription date, and the like. The predetermined custom field may correspond to a user-defined field that may be used to add additional data specific to the user. For example, the PGW (208) may analyze the subscriber profile to categorize the one or more custom fields. In an example, among the one or more custom fields, a custom field 5 may be designated to store the UE policy related to the user-subscribed service plan, such as a data service plan, a voice service plan, a video service plan, etc. Upon receiving the update request for the subscriber profile, the PGW (208) may store the updated UE policy in the custom field 5, ensuring that the subscriber profile reflects the most current information related to the user’s selected service plan, enabling network functions to accurately enforce policy updates.

[0085] The predetermined custom field may include information such as a Quality of Service (QoS) Class Identifier (5QI), plan version number, priority level,1 bandwidth allocation, or access restriction list. In an aspect, the QoS Class Identifier (5QI) defines the packet forwarding treatment associated with the subscriber’s data flows, including parameters such as delay tolerance, priority, and packet error rate, allowing the network to deliver differentiated service quality based on the subscriber’s plan. The plan version number represents a sequential or incremental identifier used to distinguish between different revisions of the subscriber’s service plan or policy configuration, enabling the network to detect when a new version of a plan becomes active. The priority level indicates the relative importance or scheduling precedence assigned to a subscriber’s data traffic, ensuring that high-priority users or applications receive appropriate resource allocation under congested network conditions. The bandwidth allocation parameter specifies the maximum and minimum data throughput permitted for the subscriber, defining rate limits and guaranteed bit rates (GBR) in accordance with the subscriber’s policy. The access restriction list defines allowed or restricted access categories, such as permitted PLMNs, network slices, or service types, thereby controlling where and how the subscriber may connect within the network.

[0086] The predetermined custom field may be implemented in a structured format such as a key-value pair or a JavaScript Object Notation (JSON) object, allowing flexible representation of policy parameters and efficient parsing by network functions. The field may further include a timestamp or a version counter to track the timing and sequence of updates. The timestamp records the precise time at which the subscriber profile was last modified, whereas the version counter serves as a monotonically increasing value used by network functions, such as the PCF, to determine whether a newer configuration has superseded a previously cached one. These metadata attributes enable accurate change detection and synchronization across distributed network functions.

[0087] In an alternative embodiment, the PGW (208) may be configured to update the subscriber profile in the data repository (210) by writing the modified valuesof the subscriber profile attributes, such as the predetermined custom field, into the corresponding record in the data repository (210). The updating may be performed through a database write operation or a transactional update API that replaces or merges the existing record with the new values while maintaining consistency and integrity of the data. In an aspect, the data repository (210) may support version-controlled record management, where each subscriber profile update is assigned a version number or timestamp to ensure traceability of changes. The PGW (208) may commit the transaction only after verifying that the modified fields have been successfully updated.

[0088] In an embodiment, the PGW (208) may be configured to store the updated subscriber profile in the data repository (210). The data repository (210) may represent a persistent database or a structured storage system configured to maintain subscriber-related data such as service plans, custom fields, etc. In an example, the subscriber profile may be stored as a file in the data repository (210). The file may be a text file, an Excel file, or a comma-separated values (CSV) file. For example, if the subscriber profile is stored as the Excel file, the Excel file may contain the one or more custom fields that provide additional context and details about the subscriber. This structured storage approach allows efficient data management, retrieval, and updates, facilitating seamless access to subscriber information for various network functions.

[0089] Upon updating the subscriber profile and modifying the predetermined custom field, such as the custom field 5, the PGW (208) may be configured to broadcast or publish a notification via the database stream. In an aspect, the broadcasted notification may include a subscriber identifier. In an example, the subscriber identifier is a Subscriber Permanent Identifier (SUPI) of the updated subscriber profile. In an aspect, the SUPI is a unique and permanent identifier used to identify the subscriber within the network (106). For example, the notification may be a push notification, a service notification, or an event-driven network notification published over the database stream. The identified subscriber profile, along with the informationcontained in the custom field 5, may be broadcast to a plurality of PCFs using the database stream to trigger subsequent evaluation or policy re-synchronization.

[0090] In an exemplary aspect, the database stream may include a publish- subscribe (pub-sub) communication channel configured to transmit real-time update events between the PGW (208) and subscribed network functions, such as the PCFs (304). Each update event transmitted through the database stream may include, but is not limited to, a subscriber identifier (for example, the SUPI), an updated field name (such as Custom Field 5 or any other modified parameter), and a timestamp indicating the precise time of modification. These data elements collectively enable receiving network functions to identify which subscriber profile has changed, what specific field was updated, and when the change occurred.

[0091] In an exemplary aspect, the database stream may be implemented using a change-data-capture (CDC) mechanism, publish-subscribe message bus, or event- driven streaming interface that automatically propagates updates made in the data repository (210) to all subscribed network functions. By utilizing the database stream, the PGW (208) ensures that the updated subscriber profile is transmitted efficiently and in near real time to the PCFs, thereby facilitating timely policy synchronization and enhancing the overall responsiveness and manageability of the network. This streaming-based approach eliminates the need for periodic polling or direct signaling between network functions, significantly reducing update latency and signaling overhead while maintaining consistency of subscriber information across the network nodes.

[0092] In an alternative embodiment, the PGW (208) may employ a flag to indicate the status of updates on the database stream. The PGW (208) may set the flag to “TRUE” when the subscriber profile is updated and the notification has been broadcast via the database stream. Based on the status of this flag, the PCF may be configured to check for the updated subscriber profile. When the flag is set to “TRUE”,the PCF interprets that a valid update is available for retrieval. If the flag is set to “FALSE”, it indicates that no update is pending.

[0093] In an embodiment, the NF, such as the PCF, may be configured to either monitor or subscribe to the database stream for notification broadcasted by the PGW (208). The monitoring may occur at predefined configurable intervals or may be implemented through a subscription-based push mechanism. In the subscription mode, the PCF may be configured to subscribe to the database stream to receive push notifications automatically whenever an update event is published by the PGW (208). This dual-mode configuration ensures flexibility, allowing the NF to operate in event- driven (push) or polling (pull) mode depending on network requirements and resource availability. In an example, the predefined configurable interval may be set to a few seconds (e.g., 5-10 seconds) for near real-time policy synchronization in high-priority service environments, such as enterprise-grade or low-latency applications. In another example, for regular consumer services or networks with large subscriber volumes, the interval may be configured to one or more minutes (e.g., 60-300 seconds) to balance responsiveness with system load. The interval value may be dynamically adjusted based on network conditions, processing load, or configuration policies defined by the operator. The PCF may store these configurable parameters in a local configuration file or centralized orchestration system, allowing network administrators to tune monitoring or subscription behavior according to operational requirements and network scale.

[0094] In an embodiment, the monitoring may be implemented using one or more of the following mechanisms:

[0095] Subscription-based monitoring: The PCF may act as a subscriber to the database stream, which operates as a publish-subscribe (pub-sub) mechanism. In this mode, the PCF registers its interest in a specific topic or key pattern (for example, all updates corresponding to a given SUPI). When the PGW (208) publishes an updateevent, the database stream automatically pushes the notification to all subscribed PCFs without explicit polling. This push-based approach ensures real-time synchronization and minimizes latency.

[0096] Change-Data- Capture (CDC) event monitoring: In certain implementations, the data repository (210) may support a CDC mechanism that logs incremental data modifications, such as insert, update, or delete operations. The PCF may monitor these CDC event logs to identify changes specifically related to custom field 5 or other relevant attributes of subscriber profiles. The PCF may use lightweight connectors or stream processors to continuously read new CDC records.

[0097] Interval-based polling (configurable): Alternatively, or in addition to event-based subscriptions, the PCF may perform interval-based polling of the database stream at predefined configurable intervals. During each interval, the PCF queries the metadata of the data repository to check for recent changes or a flag set to “TRUE.” The polling frequency may be configurable based on system load and desired synchronization latency. For example, a shorter interval (e.g., every few seconds) ensures near real-time updates, while a longer interval reduces network load in low- priority scenarios.

[0098] This periodic checking ensures that the PCF remains informed of any updates to the subscriber profile, allowing it to implement the latest policies and maintain optimal service delivery. By utilizing this mechanism, the system (108) enhances responsiveness and ensures that subscriber information is accurately reflected across the network functions.

[0099] Upon receiving the broadcasted notification (or detecting that the flag has been set to “TRUE”) via the database stream, the PCF determines whether a session associated with at least one subscriber identifier (e.g., SUPI) included in the notification exists in a memory (e.g., a local cache) of the PCF. The local cache maymaintain a plurality of session context records, each representing an active subscriber session within the network (106). Each session context record may include data elements such as the SUPI, a session identifier (Session ID), a Quality of Service (QoS) parameter set, the last applied policy configuration, and a session status flag (for example, “active,” “idle,” or “terminated”).

[0100] In an aspect, the SUPI uniquely identifies a subscriber within the 5G core network and serves as the primary key for correlating subscriber-related information across network functions. It enables the PCF to map each notification received via the database stream to the correct subscriber session stored in the local cache. The Session Identifier (Session ID) represents a unique session handle assigned to each active user session, such as a Protocol Data Unit (PDU) session. The Session ID allows the PCF to differentiate between multiple concurrent sessions belonging to the same subscriber, ensuring that policy decisions are applied to the correct session instance. The Quality of Service (QoS) parameter set contains a collection of networklevel service attributes that define the data forwarding behavior for a given session. This may include the QoS Class Identifier (5QI), allocation and retention priority (ARP), guaranteed bit rate (GBR), and maximum bit rate (MBR). These parameters enable the PCF to ensure that user traffic conforms to the contractual service quality associated with the subscriber’s plan. Further, the last applied policy configuration represents the most recent set of policy rules that were enforced for the subscriber session. This may include flow-based traffic rules, service data flow filters, access control parameters, or data rate restrictions. The PCF uses this stored configuration to perform comparison against the newly retrieved subscriber profile, enabling it to detect any deviations in the policy or QoS attributes that warrant re-evaluation or reapplication of the policy through the N1N2 message transfer procedure.

[0101] In certain implementations, the local cache may also store additional metadata such as the session creation timestamp, associated AMF identifier, and lastpolicy version number to provide full traceability of the subscriber’s current session state. This determination allows the PCF to selectively act only on those subscribers who have active sessions within the network (106), thereby optimizing signaling and computational resources.

[0102] To verify session presence, the PCF may perform a lookup in the local cache using the SUPI or Session ID contained in the received notification. If a matching record is found and the session status flag is set to “active,” the PCF determines that an active session exists for the corresponding subscriber. This verification allows the PCF to selectively act only on those subscribers who have active sessions within the network, thereby optimizing signaling overhead and reducing unnecessary policy evaluations for inactive or detached users.

[0103] For example, the broadcast notification received via the database stream may include the subscriber ID, a message content, a notification type, and a time stamp. To determine whether a session exists, the PCF may check the SUPI or session ID included in the notification. In an aspect, the session may may correspond to a protocol data unit (PDU) session, a network slice, and a transmission control protocol (TCP) session. If the PCF identifies that the session exists in the local cache, the PCF may retrieve the updated subscriber profile from the data repository (210). Further, the PCF may compare the predetermined custom field in the retrieved subscriber profile with a corresponding cached value stored in the local cache to detect a change in the custom field 5 to detect a change in the custom field 5 and determine whether the predetermined custom field has changed relative to the cached value.

[0104] The cached value may represent the last applied policy configuration that were stored in the local cache of the PCF when the subscriber’s session was first established or last updated. Such policy configuration may include, but are not limited to, QoS profiles (e.g., bandwidth limits, priority levels, latency targets), access or mobility restrictions (e.g., allowed PLMN lists or roaming permissions), application-level control rules (e.g., traffic filtering or throttling parameters), or UE policy version identifiers used to track the currently active policy at the UE (104). By comparing the updated value of the predetermined custom field, such as custom field 5 in the retrieved subscriber profile, with the cached value representing the previously applied policy configuration, the PCF may accurately detect whether a change in subscriber policy has occurred, ensuring that the subscriber’s current profile accurately reflects the latest updates and that appropriate policies are enforced.

[0105] In an embodiment, upon detecting a change in the predetermined custom field, the PCF performs at least one operation to manage the subscriber profile in the data repository (210). The at least one operation includes initiating a N1N2 message transfer request towards a second NF (AMF) to apply an updated subscriber policy to the UE (104) in real time. In an embodiment, the PCF may trigger the N1N2 message transfer request only when the change is detected in the predetermined custom field.

[0106] In an embodiment, the N1N2 message transfer request is a signaling procedure that allows a control-plane network function, such as the PCF, to deliver N1 (Non-Access Stratum (NAS)) and / or N2 (Access Stratum (AS)) messages to the UE (104) via the AMF. The AMF acts as the relay and coordination point, encapsulating the received N1N2 messages and forwarding them to the UE over the appropriate signaling path. In the context of the present disclosure, the N1N2 message includes policy update information including one or more modified Quality of Service (QoS) rules, updated flow-based traffic filters, revised access control parameters, and other session management configurations relevant to the subscriber profile. For example, the N1N2 message may include updated parameters such as the 5QI value, bandwidth allocation, or priority class to ensure that the UE immediately adopts the most recent network policy. The network signaling mechanism enables the PCF to directly update or reconfigure UE policy settings, QoS rules, or session management parameterswithout requiring a new registration or PDU session establishment. By using the N1N2 message transfer procedure, the network (106) ensures immediate synchronization of policy updates with the UE (104), minimizes signaling latency, and maintains consistent policy enforcement across the control plane.

[0107] In an alternative embodiment, if the UE (104) is unreachable, in an idle state, or if the N1N2 message transfer procedure fails due to temporary signaling errors or network congestion, the PCF may defer the policy update by logging the notification in a pending-update queue. The pending-update queue serves as a temporary storage structure that retains undelivered update events until successful transmission conditions are restored. Each entry in the queue may include metadata such as the SUPI, the policy update payload, a retry counter, a timestamp, and an error cause code (for example, “UE unreachable” or “AMF timeout”). The PCF may periodically attempt to resend the N1N2 message at predefined retry intervals, which may be configured based on operator policy or network conditions. In one example, the PCF may attempt three successive retries with exponentially increasing back-off intervals before flagging the event for manual review.

[0108] Once the PCF receives an acknowledgment from the AMF confirming successful policy delivery to the UE, the corresponding entry is removed from the pending-update queue. This queuing and retry mechanism ensures reliable policy delivery, fault tolerance, and graceful recovery from transient failures in signaling or UE availability. In scenarios where the UE remains unreachable for an extended duration, the PCF may archive the pending entry and mark the policy for re-evaluation during the next session establishment or registration event.

[0109] In an operative aspect, the PCF may retrieve the subscriber profile associated with the SUPI from the data repository (210). Simultaneously, the PCF fetches the subscriber profile corresponding to the same SUPI from the memory (local cache) associated with the PCF. The PCF compares the custom field 5 of the subscriberprofile to identify the modification in the UE policy. For example, initially, the user may subscribe to a service plan related to a voice calling plan. A network service provider may implement the subscribed voice plan using the PCF. Further, the user (102) may modify the voice calling plan to a game plan. The subscriber profile may include the custom field 5, which indicates a change in the UE policy from the voice calling plan to the gaming plan. To determine a change in the policy, the PCF compares the UE policies stored in the custom field 5 of the subscriber profile retrieved from the data repository (210) with the profile fetched from the memory associated with the PCF. If a modification is detected, the PCF is configured to initiate a message transfer request (N1N2 message transfer request) to the AMF. This request facilitates the updating of the UE policy in the UE (104) to reflect the new gaming plan. By doing so, the PCF ensures that the subscriber's preferences are accurately implemented within the network (106), enhancing the user experience and maintaining service alignment.

[0110] In another example, consider a user who initially subscribes to a data service plan that provides a specified amount of monthly data allowance for internet access. The network service provider implements this plan through the PCF. Subsequently, the user decides to modify his subscription from the data service plan to a video streaming plan that offers higher data allowances specifically optimized for video content consumption. The subscriber profile reflects this change, with the custom field 5 indicating that the UE policy has transitioned from the data service plan to the video streaming plan. Upon receiving the broadcast notification regarding this update, the PCF retrieves the subscriber profile associated with the SUPI from the data repository (210) and simultaneously fetches the corresponding profile from its memory. The PCF then compares the UE policies in the custom field 5 of both profiles to identify the change.

[0111] If the comparison reveals that the policy has changed to the video streaming plan, the PCF initiates the message transfer request to the AMF. This request,by the AMF, updates the UE policy in the UE (104) to ensure that the user now benefits from the optimized settings and data management associated with the new video streaming plan.

[0112] In an embodiment, if the session associated with the subscriber identifier does not exist in the local cache, the PCF foregoes initiation of the at least one operation, such as triggering of the N1N2 message transfer request. In this case, the PCF identifies that the subscriber is not currently registered or does not have an active policy association within the network (106), and therefore, no policy update action is required. The PCF may temporarily log or record the notification for deferred action in a pending-update queue. The pending-update queue serves as a temporary data structure that stores policy update notifications corresponding to subscribers who are currently offline, detached, or in idle state. Each entry in the pending-update queue may contain metadata such as the SUPI, the timestamp of the notification, the policy update payload (for example, the modified Custom Field 5 value or associated policy rules), and a status indicator (for example, “awaiting session establishment” or “pending delivery”). When the subscriber subsequently registers with the network or initiates a new Protocol Data Unit (PDU) session, the PCF retrieves the corresponding entry from the queue and executes the deferred policy update procedure, including initiation of the N1N2 message transfer request toward the Access and Mobility Management Function (AMF).

[0113] The pending-update queue may be periodically purged or synchronized with the data repository (210) to remove stale or expired entries, ensuring optimal memory utilization and consistency. This deferred handling mechanism enables the PCF to maintain policy synchronization for subscribers who are temporarily inactive, while preventing unnecessary signaling exchanges for those without active sessions. By intelligently queuing and deferring updates, the system (108) ensures networkefficiency, policy consistency, and reliable update delivery once connectivity is restored.

[0114] In an embodiment, the data repository (210) includes data (e.g., service plan details, subscriber information, provisioning details, error logs, network configuration parameters, historical subscription data, etc.) that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the PGW (208). In an aspect, the system (108) may include one or more databases forming a database cluster. For example, the database cluster is a set of databases that work together to handle the requests. The database cluster may provide high availability, manage the loads of the NFs, and enable fault tolerance. In an exemplary implementation, the data repository (210) supports transactional consistency and version control for subscriber profiles. Each subscriber profile update is executed as an atomic transaction, ensuring that partial or conflicting writes do not occur even under concurrent update requests. The repository may also maintain version identifiers or revision timestamps for each subscriber record, allowing network functions such as the PCF to identify the most recent policy configuration. In certain embodiments, the repository may employ database triggers or change-data-capture (CDC) mechanisms that automatically generate and stream update events to the database stream upon detecting modifications to a subscriber record. This ensures that the PGW can publish consistent, ordered, and versioned updates to the network functions, maintaining data integrity and real-time synchronization across the network.

[0115] Although the embodiments described herein reference two primary data storage components, the data repository (210) and the local cache, it will be appreciated that the system (108) is not limited thereto. The system (208) can be scaled horizontally to support multiple data repositories, distributed database clusters, or cache layers in large-scale deployments. Each database instance may operate as part of a replicated orsharded cluster, ensuring fault tolerance, load balancing, and high availability of subscriber data.

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

[0117] FIG. 3 illustrates an exemplary system architecture (300) for managing the subscriber profile update in the network (106), in accordance with an embodiment of the present disclosure.

[0118] In an embodiment, the system architecture (300) may include the gateway (302), a first network function (304), and a second network function (306). In an example, the gateway (302) is a Provisioning Gateway (PGW), the first network function (304) is the PCF, and the second network function (306) is the AMF. In an aspect, the gateway (302) may be used interchangeably as the PGW (208). The first network function (304) may be used interchangeably as the PCF. The second network function (306) may be used interchangeably as the AMF.

[0119] The PGW may be coupled with each of the plurality of PCF via the database stream, which operates as an asynchronous, event-driven, push-based communication interface. The database stream allows the PGW to publish update notifications in real time whenever a subscriber profile or its predetermined custom field is modified in the data repository. The PCF, acting as a subscriber to the stream, maintains an active subscription session with the message broker or stream controller and automatically receives push notifications as soon as the PGW publishes an event.This eliminates the need for polling or synchronous queries and enables near- instantaneous propagation of subscriber profile updates to all subscribed PCFs.

[0120] In one implementation, the stream may be realized through a publish- subscribe middleware, such as an event bus or message queue (for example, Kafka, NATS, or RabbitMQ), which guarantees message delivery order and persistence. Each notification message may be tagged with a topic identifier corresponding to the affected subscriber or custom field (for example, “SUPI / CustomField5”). The PCF interface to the database stream may include a subscription client component configured to manage stream connections, handle message acknowledgments, and forward received update events to the internal policy evaluation module for further processing. Through this interface, the PCF is able to process only relevant updates, maintain low signaling latency, and ensure reliable synchronization with the subscriber data managed by the PGW.

[0121] The plurality of AMF may be coupled with the plurality of PCF. Each UE (104) may be assigned to at least one of the plurality of PCF to update the UE policy based on the updated subscriber profile. For example, the PCF may be specifically assigned to configure the UE policy for the UE (104-1) within the network (106). This assignment enables the PCF to effectively update the UE policy in accordance with the changes reflected in the subscriber profile, thereby ensuring that the UE (104-1) operates under the correct parameters and receives the appropriate service based on the user’s current subscription plan. This architecture enhances the overall flexibility and responsiveness of the network in managing subscriber services and maintaining optimal performance.

[0122] In an embodiment, the PGW may be configured to manage and configure the UE (104) in the network (106). The PGW serves as a central hub for deploying, updating, and maintaining UE settings and policies, ensuring that each UE operates under optimal conditions tailored to the subscriber's needs. The PGW mayretrieve the appropriate configuration settings and policies from the database (210). For example, consider a scenario where a user subscribes to a premium data service plan that includes enhanced data speeds and priority access during peak usage times. The PGW is responsible for retrieving the appropriate configuration settings and policies from the database (210), which stores detailed information about the various service plans available to subscribers.

[0123] In an embodiment, the PCF may be configured to monitor the behavior of the network (106). The PCF manages policies regulating various network aspects (106). These policies include a wide range of functions, including quality of service (QoS), network resource allocation, authentication, mobility, and security.

[0124] In an embodiment, the AMF may be configured to manage access and mobility of the UE (104). The AMF enforces network policies such as QoS and charging policies. The AMF ensures that the network resources are allocated appropriately, and the UE (104) is charged correctly for the services based on the usage.

[0125] In an embodiment, the FMS (110) may be configured to initiate the subscriber profile update request (also referred to as request). The PGW may be configured to receive the subscriber profile update request from the FMS (110). For example, the update subscriber profile request may be a service request, a configuration request, a status request, and a policy enforcement request. The PGW may be configured to receive the request and initiate one or more actions. The one or more actions include updating the subscriber profile in the database (210), detecting the modification in the subscriber profile, modifying the custom field 5 in associated with the SUPI, and notifying the PCF. In an exemplary aspect, the PGW may be configured to store the updated subscriber profile in the database (210). The updated subscriber profile may be stored in a table form. The table may include one or more custom fields. The one or more may include a subscriber ID, a subscriber name, an Internet Protocol(IP) address, etc. For example, the custom field 5 may be used to store the updated UE policy for the UE (104) of the user (102).

[0126] In an embodiment, the PGW may be configured to notify the PCF about the updated subscriber profile through a database stream. The PCF may be subscribed to the database stream to receive real-time notifications whenever any modification occurs in the subscriber profile stored in the data repository. In an aspect, the database stream may be implemented using a Change Data Capture (CDC) mechanism, a publish-subscribe (pub-sub) event stream, or other equivalent data streaming platforms, enabling asynchronous, event-driven communication between the PGW and the PCF. The database stream facilitates the continuous and reliable propagation of update events corresponding to the subscriber profile changes without requiring direct API calls or synchronous signaling. For example, when a subscriber’s policy or service plan is updated, the PGW may publish an event containing metadata such as the Subscriber Permanent Identifier (SUPI), timestamp, and the identifier of the modified field (e.g., Custom Field 5) to the database stream. The PCF, upon receiving this event, parses the notification to identify the modified parameters, such as a change in the service plan, UE policy, or configuration setting, and determines whether the change impacts an active session. The parsing process may involve comparing the new value of the modified custom field against the corresponding cached value to detect any variation requiring policy re-evaluation or N1N2 message initiation.

[0127] In an embodiment, the PCF may be configured to enforce network policies and rules in the network (106). The PCF may enforce policies related to the subscriber profile in the network (106). For example, the updated subscriber profile may have the details of a service plan, such as an internet plan, a voice calling plan, and a gaming plan. The user may have subscribed to one or more service plans, which may lead to a change in the UE policy. The UE policy may be stored in the custom field of the subscriber profile. In an aspect, the data repository (210) may store theexisting subscriber profile with the SUPI. The PCF may be configured to receive the updated subscriber profile from the PGW using the database stream and store the updated subscriber profile in the memory associated with the PCF. The PCF may receive the SUPI of the updated subscriber profile.

[0128] Based on the received SUPI, the PCF may be configured to match the existing subscriber profile in the database. The PCF may be configured to compare the updated subscriber profile with the existing subscriber profile. The PCF compares the custom fields between the existing and updated subscriber profiles. For example, the PCF compares the custom field 5 of the existing and updated subscriber profile. The custom field 5 may store the UE policy related to the service plan, such as a videocalling plan. Custom Field 5 may be re-evaluated by the PCF to detect modifications in the UE policy. If the user changes from one service plan to another service plan, the UE policy corresponding to the service plan may also be changed. Upon changes in the custom field 5, the PCF may initiate a message transfer request to the AMF. For example, the message request may be an N1N2 message transfer request. In an embodiment, the PCF may invoke the Namf_Communication_NlN2MessageTransfer service operation provided by the AMF. The message includes a SUPI and a UE Policy Container. The SUPI may be a unique identifier used to identify the UE (104) in the network (106). The UE policy container may comprise the UE policy to be updated.

[0129] In an embodiment, the AMF may be configured to manage user access to the network (106). The AMF may be configured to authenticate the plurality of users requesting to access the network (106). The PCF may communicate using an interface with the AMF. For example, the interface may be an N15 reference point. The N15 reference point may be used to transmit and remove access and mobility policies between the PCF and the AMF. In an aspect, the AMF may receive the message transfer request from the PCF using the interface.

[0130] In an embodiment, the message transfer request may be an N1N2 message transfer request. The N1N2 message transfer request is used by an NF Service consumer to transfer N1 and / or N2 information to the UE or the network (106) through the AMF. The NF service consumer may be the PCF. For example, the PCF may send a POST request to transfer N1 and N2 information. The PCF may include a N1N2 Message Transfer Notification Uniform Resource Identifier (URI) to the AMF in the request message. Upon successful acceptance of the request from the PCF, the AMF may transfer the N1 / N2 message to the UE (104). Further, the AMF may respond to the PCF with a "200 OK" status code.

[0131] In an overall aspect, the present disclosure is configured to send a subscriber profile update request to PGW node (e.g., PGW). Further, the PGW writes the updated subscriber profile with the modified custom field 5 (CustomField5) parameter in the data repository (210). Further, the PGW puts the SUPI of the updated subscriber profile in the database stream. All PCFs connected to that database (data repository 210) periodically check the stream for any notification sent by the PGW. PCFs, upon receiving this notification, may be configured to check if the UE session associated with that subscriber is present in their memory (local cache) or not. The PCF, having that UE Session, may read that subscriber profile from the data repository and compare it with the cached subscriber profile. If there is any change in CustomField5 then PCF may initiate the N1N2 message transfer service operation towards the AMF. The N1N2 message transfer service operation is used by an NF service consumer to transfer N1 and / or N2 information to the UE through the AMF.

[0132] FIG. 4 illustrates an exemplary flow diagram of a method (400) for managing the subscriber profile update in the network, in accordance with an embodiment of the present disclosure.

[0133] As shown in FIG. 4, the method (400) may be performed by operations executed by the PGW (208) or gateway (302) within the control plane, and operationsexecuted by the first NF (304) (e.g., PCF) following receipt of a broadcast notification from the PGW (208). The operations performed by the PGW from steps 402 to 406, illustrate PGW-side processes such as receiving the subscriber profile update request, updating the subscriber profile in the data repository, and notifying the PCF through the database stream. The operations performed by the PCF from steps 410 to 426, illustrate PCF-side operations, including reading notifications from the database stream, verifying session presence in the local cache, comparing updated subscriber information, and initiating the N1N2 message transfer procedure when policy changes are detected.

[0134] At step 402, the PGW (208) may receive one or more subscriber profile update requests from the FMS (110). When a subscriber changes his service plan, such as upgrading from a basic plan to a premium plan, the FMS (110) generates the subscriber profile update request containing relevant details about the new plan. This request may include the subscriber ID, the updated subscriber profile, and the new service plan. The FMS (110) subscriber profile update request to the PGW through a designated database stream. The subscriber profile update request serves as an official record of the change and prompts the PGW to initiate the necessary adjustments in the network. Upon receiving the update request, the PGW processes the information, updating its configurations and settings related to the subscriber. This includes adjusting the subscriber's profile to reflect the new plan details, ensuring that the user receives the benefits associated with the upgraded plan, such as increased data limits or additional features.

[0135] In an aspect, the PGW may trigger the one or more actions based on the received subscriber profile update requests. For example, the subscriber profile update request may comprise a subscriber ID, a subscriber profile, a service plan and a subscription type. The subscriber ID serves as a unique identifier for each subscriber, enabling the network to distinguish one subscriber from another and ensuring thatupdates are applied to the correct individual. The subscriber profile encompasses a comprehensive set of details about the subscriber, including personal information, preferences, and specific settings related to their account. The service plan outlines the specific services and features the subscriber is entitled to, such as data limits, voice call allowances, and any premium offerings, which are essential for managing the subscriber's access to services. The subscription type distinguishes between various service plans such as individual, family, business, or prepaid. By incorporating these elements, the subscriber profile update request facilitates effective management of the subscriber’s information.

[0136] In an aspect, the one or more actions include updating the subscriber profile, modifying the subscriber profile, and storing the subscriber profile in the database (210). For example, when a subscriber switches from a basic data plan to a premium data plan, the PGW first updates the subscriber profile to reflect this change. This involves modifying relevant fields, such as increasing the data allowance and adding features like priority access during peak times. After these modifications are made, the updated subscriber profile, which now includes the new service plan details and any changes to user preferences, is stored in the database (210). This ensures that all relevant network functions can access the most current information, facilitating efficient service delivery and ensuring that the subscriber benefits from the new plan immediately. In another example, the user may purchase an additional service plan along with the existing one. In such cases, the FMS (110) may notify the modification to the PGW by the update request. The PGW modifies the subscribed profile based on the user subscription.

[0137] At step 404, the PGW may notify the PCF about the SUPI of the updated subscriber profile through the database stream. In an aspect, the SUPI is used by the PCF to identify the UE (104) in the network (106). The PCF may be notified using various notifications, such as an alert notification, an event notification, a servicenotification, a status notification, and a policy notification. For example, the PGW may broadcast the SUPI of the updated subscriber profile to the plurality of PCFs. The plurality of PCFs may receive the SUPI of the updated subscriber profile.

[0138] At step 406, the PGW may update the updated subscriber profile in the database (210). In an aspect, the PGW may send the updated subscriber profile to one or more databases. The one or more databases may form a database cluster. For example, the database cluster is a group of databases that work together as a single database service. The database cluster may enable load balancing by distributing the incoming requests across the databases (210) to optimize resource usage and response time. In another example, the updated subscriber profile may be stored in the one or more databases to facilitate data redundancy in the network (106).

[0139] At step 410, the PCF may read the notification from the database stream and check for the UE session of the SUPI in the memory associated with the PCF. For example, each UE (104-1,104-2..., 104-N) may be assigned to a designated PCF from the plurality of PCFs. For example, the memory may include a cache memory, a random-access memory (RAM), and a secondary memory.

[0140] At step 408, the PCF may examine the subscriber profiles in the database (210). For example, the data repository (210) may store the subscriber profile along with a subscriber ID. The PCF may fetch the updated subscriber profile from the data repository (210) using the SUPI. The PCF may employ the parsing process to retrieve the updated subscriber profile based on the SUPI. If the relevant subscriber profile exists in the database (210), the existing subscriber profile is retrieved by the PCF.

[0141] At step 412, upon checking for the UE session by the PCF, if the UE session is attached to the PCF. At step 414, the PCF may read the subscriber profile based on the received SUPI details from the database (210). The PCF may compare theretrieved subscriber profile from the data repository (210) with the subscriber profile stored in the memory associated with the PCF. For example, the PCF may compare the retrieved existing subscriber profile with the updated subscriber profile to identify value changes in the custom field. The PCF may use a comparison mechanism to determine the change in the subscriber profile. The comparison mechanism may involve identifying whether all the custom fields in the updated subscriber profile are identical to the existing subscriber profile.

[0142] At step 422, the PCF may check if the custom field has been changed in the updated subscriber profile. For example, the subscriber profile may have one or more custom Fields. The custom field 5 may store the UE policy for the service plan, such as a voice-calling plan adopted by the user. The PCF may check the custom field 5 to identify the change in UE policy. At step 424, upon checking by the PCF, the value of the custom field 5 has changed. At step 426, on checking the change in the UE policy, the PCF may initiate the N1N2 Message Transfer request for the AMF if the value of the custom field changes.

[0143] Conversely, at step 416, if the UE session is not attached to the PCF, the PCF may wait for further notification. At step 420, if the custom field of the updated subscriber profile does not change, the PCF may remain idle until further notification from the PGW is received (at step 418). Accordingly, FIG. 4 collectively depicts the end-to-end workflow between the PGW and PCF, showing how subscriber profile updates initiated by an external source (e.g., the FMS) propagate through the database stream to trigger policy synchronization and enforcement across the 5G core network.

[0144] FIG. 5 illustrates another exemplary flow diagram of a method (500) for managing the subscriber profile update in the network (106), in accordance with an embodiment of the present disclosure.

[0145] At step 502, the PGW (208) may receive an update request for a subscriber profile from one or more external sources (110). In an embodiment, the external sources may include systems such as a Fulfillment Management System (FMS), a Network Management System (NMS), or any external operations support or business support system (OSS / BSS) responsible for managing subscriber provisioning and service activation. The update request may contain one or more data elements, including a subscriber identifier (e.g., SUPI), updated plan details, and policy-related configuration. The PGW (208) may parse and validate the update request to ensure data consistency and authorization before proceeding with the profile update process. The receipt of the update request may be triggered by events such as plan modification, renewal, suspension, or activation of new services by the subscriber.

[0146] At step 504, the PGW (208) may update the subscriber profile in a data repository (210) based on the update request. The update operation may involve modifying existing profile entries, inserting new parameters, or replacing outdated information to ensure that the subscriber profile reflects the latest provisioning state.

[0147] At step 506, the PGW (208) may modify a predetermined custom field of the subscriber profile in the data repository (210). The predetermined custom field, such as custom field 5, may be specifically designated to store policy configuration data that corresponds to a subscriber’s current plan or usage profile. For example, custom field 5 may hold identifiers for UE policies such as bandwidth allocation, priority class, access category, or specific service plan type (e.g., data, voice, or video). By modifying this field, the PGW (208) ensures that any change in the subscriber’s plan or policy is immediately reflected at the database level. This modification may also update metadata, such as timestamps or flags, to signal the network functions that a relevant policy update has occurred.

[0148] At step 508, the PGW (208) may broadcast, via a database stream, a notification comprising at least one subscriber identifier associated with the updatedsubscriber profile. The database stream may operate using a Change Data Capture (CDC) mechanism, a publish-subscribe message bus, or an event-driven data pipeline that automatically propagates the change event to all subscribed NFs. The database stream includes a publish-subscribe communication channel configured to transmit real-time update events, including a subscriber identifier, updated field name, and timestamp.

[0149] In an embodiment, the publish-subscribe communication channel operates as an asynchronous, event-driven messaging framework that decouples message producers (for example, the PGW) from message consumers (for example, the PCF or other subscribed network functions). In this model, the PGW acts as a publisher that generates and transmits update events whenever changes occur in the subscriber profile stored in the data repository. The subscribed network functions act as subscribers that receive these updates automatically through the channel. In an embodiment, the updated field name identifies the specific parameter within the subscriber profile that has undergone modification. For example, the updated field name may correspond to the predetermined custom field (such as Custom Field 5) used to store policy-related information, or any other field like service plan ID, QoS class, or access restriction indicator. By including the updated field name, the receiving network function can perform targeted comparisons rather than retrieving and processing the entire subscriber profile, thereby reducing data access overhead and improving response time. The timestamp records the precise time at which the update occurred in the data repository. This temporal marker allows the PCF and other subscribed network functions to determine the recency and sequence of updates, enabling correct ordering of policy evaluations in the case of multiple rapid profile changes. In certain implementations, the timestamp may follow a standardized format such as Coordinated Universal Time (UTC) and may include both seconds and milliseconds for high-resolution event tracking.

[0150] The notification may include the subscriber identifier (e.g., SUPI), update timestamp, and metadata indicating which custom field was modified. In an embodiment, the first network function (NF) (304), such as the PCF, is configured to monitor the database stream at predefined, configurable intervals (for example, after every 30 seconds) for such notifications broadcasted by the PGW (208). The first NF (304) is configured to subscribe to the database stream to receive push notifications. Through this subscription, the PCF registers its interest in specific topics or event keys, for example, all update events corresponding to a particular Subscriber Permanent Identifier (SUPI) or custom field. Once subscribed, the PCF automatically receives update messages without the need for explicit polling or periodic queries. This pushbased model ensures near real-time synchronization between the data repository and the PCF, allowing immediate policy evaluation whenever a subscriber profile changes. The subscription may be implemented using a topic-based or key-based filtering mechanism within the publish-subscribe communication framework, enabling the PCF to receive only relevant notifications and reducing unnecessary message processing. In certain implementations, the subscription state and delivery offsets may be maintained persistently by the message broker, ensuring reliable delivery even in the event of transient network failures or PCF restarts. This enables asynchronous, real-time propagation of subscriber updates without relying on traditional request-response signaling. The streaming mechanism thus ensures that updates reach all relevant PCF instances immediately, minimizing policy synchronization delays.

[0151] On receiving the broadcasted notification, at step 510, the first NF (304), may determine by a whether a session associated with the at least one subscriber identifier exists in a local cache. The local cache may store details of currently active subscriber sessions, including the SUPI, session ID, QoS parameters, and the last applied policy configuration. The first NF (304) retrieves the SUPI of the subscriber from the notification and performs a lookup in its local cache to verify whether an active session is ongoing.

[0152] In an embodiment, if the session exists in the local cache, the first NF (304) may retrieve the updated subscriber profile from the data repository (210) and compare the predetermined custom field in the retrieved subscriber profile with a corresponding cached value stored in the local cache to detect whether the predetermined custom field has changed relative to the cached value. If the session exists, it indicates that the subscriber is currently registered, and policy synchronization is immediately required. The cached value represents the previously applied policy configuration, such as QoS class identifiers, access restrictions, application filtering rules, or the UE policy version identifier used during the last session establishment. The comparison enables the PCF to accurately detect any variation in subscriber plan or service attributes that require policy re-evaluation.

[0153] In an embodiment, upon detecting a change in the predetermined custom field, the first NF (304) may perform at least one operation to manage the subscriber profile in the data repository (210). The at least one operation includes initiating a network signaling procedure to update a subscriber policy at a second network function. The network signaling procedure includes initiating, by the first NF (304), a N1N2 message transfer request towards a second NF (306) to apply an updated subscriber policy. The first NF (304) triggers the N1N2 message transfer request upon detecting the change in the predetermined custom field. The N1N2 message includes policy update information comprising modified QoS rules or access parameters.

[0154] In an embodiment, the modified Quality of Service (QoS) rules define updated traffic treatment policies for the subscriber’s ongoing or newly established session. These rules may include parameters such as the QoS Class Identifier (5QI), which specifies packet forwarding priority and delay tolerance; Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR), which define the minimum and maximum data throughput allowed for a particular data flow; and the Allocation and Retention Priority (ARP), which determines the priority of resource allocation during network congestion.The N1N2 message may also carry modifications to flow-based QoS rules, such as updated service data flow filters or traffic mapping information, enabling the UE to adjust its traffic behavior in alignment with the latest network policy decisions applied by the PCF.

[0155] The access parameters included in the N1N2 message define the network- and service-level permissions applicable to the subscriber. These may include updated access control lists (ACLs), specifying which network slices, data services, or PLMN identifiers the UE is authorized to access; policy association identifiers (PAIs) used to link specific service sessions to a defined policy set; and subscriber-specific access categories that regulate data network access priority or restrict access to certain network domains based on operator-defined criteria. In certain implementations, the access parameters may also include updated connectivity type restrictions (for example, restricted access or allowing 5G standalone mode only) and mobility management parameters, which govern UE handover or registration behavior.

[0156] The N1N2 procedure allows the PCF to deliver control-plane signaling directly to the UE via the AMF, carrying the updated policy information (e.g., modified QoS rules or access parameters). This ensures immediate reflection of the new subscriber policy on the UE without requiring session re-establishment or additional signaling from other entities such as a Charging Function (CHF) or an Online Charging System (OCS). The mechanism thereby reduces signaling complexity and enhances policy enforcement responsiveness.

[0157] In an embodiment, if the session does not exist in the local cache, the first NF (304) foregoes initiation of the at least one operation. In this scenario, the PCF determines that the subscriber is either idle, detached, or not currently active in the network, and therefore, no immediate policy enforcement action is required. The PCF may log the received notification for deferred action, storing it in a pending-update queue to be reprocessed when the subscriber next registers or establishes a new session.The pending-update queue serves as a persistent data structure that ensures deferred policy updates are not lost due to temporary network or session unavailability.

[0158] In an aspect, the PCF maintains the pending-update queue as a persistent storage entity, which may be implemented using a message broker, or an equivalent streaming platform, or alternatively as a database table within the data repository. Each entry in the pending-update queue may include fields such as the SUPI, an update timestamp, the policy update payload (for example, the modified Custom Field 5 or corresponding policy parameters), and a processing status indicator (for example, “pending,” “delivered,” or “expired”). This design ensures durability and recovery even in the event of PCF restarts or network failures. When the subscriber becomes active again, the PCF retrieves the corresponding entry from the queue and initiates the deferred policy update procedure by triggering the N1N2 message transfer request toward the AMF. This persistent queuing mechanism provides reliability and robustness to the overall policy management framework, ensuring that no subscriber policy updates are missed or discarded during periods of inactivity. It also contributes to network efficiency by preventing redundant signaling attempts for offline subscribers and guarantees eventual synchronization of subscriber policies once the UE resumes connectivity.

[0159] In an exemplary implementation, the system architecture 300 illustrated in FIG. 3 depicts the end-to-end data flow between the Gateway (e.g., PGW), the database stream, the PCF, and the AMF. The PGW operates as a publisher, generating update events whenever a subscriber profile or custom field (for example, Custom Field 5) is modified in the data repository (210). These events are transmitted via a publish- subscribe database stream, which serves as the communication medium between the PGW and all subscribed network functions. The PCF acts as a subscriber, receiving push notifications through the stream in real time and verifying whether the affected subscriber has an active session within its local cache. If an active session is detected,the PCF retrieves the updated subscriber profile and evaluates the corresponding changes; if no session exists, the update notification is deferred for later processing through the pending-update queue.

[0160] In certain implementations, the database stream message schema may be structured as a lightweight data object or pay load designed for efficient serialization, transmission, and parsing. Each notification message may include a plurality of data fields that collectively describe the nature of the update event. These fields may include, but are not limited to, a subscriber identifier, an updated field name, an old value, a new value, and a timestamp.

[0161] In an embodiment, the Subscriber Identifier uniquely identifies the subscriber profile that has been modified, for example, by including the SUPI (e.g., SUPI-123456789). The Updated Field Name specifies which field or parameter within the subscriber profile has changed (for example, the predetermined custom field such as Custom Field 5). The old value field (e.g., Policy Version 2.0) and new value field (e.g., Policy Version 3.0) represent the previous and the newly updated data values for that parameter, allowing the receiving network function to perform differential or version-based analysis. The Timestamp records (e.g., 20xx-10-24, 11:35:00 AM) the precise time at which the modification occurred, thereby enabling ordered processing of events and synchronization across distributed network functions.

[0162] In an embodiment, when the PCF receives a notification from the database stream, it evaluates the contents of the message to determine whether the updated field corresponds to the predetermined custom field. If the updated field matches the custom field (for example, Custom Field 5), the PCF retrieves the subscriber’s corresponding record from its local cache using the Subscriber Identifier. The PCF then compares the newly received value of the custom field against the cached value previously stored in memory. If a difference between the two values is detected, such as a change in the policy version number, access restriction, or Quality of Service(QoS) parameter, the PCF initiates a signaling procedure, such as the N1N2 message transfer request, to apply the updated policy to the subscriber’s active session. If no difference is detected, the PCF may log the event as a no-change condition. If the corresponding subscriber record is not found in the cache, the notification is recorded in a pending-update queue for deferred processing when the subscriber reconnects or re-registers with the network.

[0163] The above-mentioned exemplary database stream message schema illustrates how the PCF validates whether a notification corresponds to a cached subscriber session and determines whether a policy change has occurred, triggering the N1N2 message transfer procedure only when necessary.

[0164] In an embodiment, the present disclosure supports error recovery and retry mechanisms to handle temporary failures, such as database stream interruptions, PCF restarts, or unreachable UEs. If a notification fails to process due to transient issues, it is logged in the pending-update queue along with a retry counter and timestamp. The PCF periodically reviews the queue and retries delivery at configurable intervals (for example, exponential backoff intervals such as 10s, 20s, 40s). Upon successful confirmation from the AMF that the N1N2 message has been delivered to the UE, the corresponding queue entry is cleared. This mechanism ensures reliability, persistence, and graceful recovery across system restarts and network disruptions, maintaining synchronization integrity between the subscriber database and the network functions.

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

[0166] As shown in FIG. 6, the computer system (600) is described as representative of the system 108 which may include an external storage device (610), a bus (620), a main memory (630) (analogous to the memory (204)), a read onlymemory (640), a mass storage device (650), a communication port (660), and a processor (670) (analogous to the PGW (208)). A person skilled in the art will appreciate that the computer system (600) may include more than one processor (670) and communication ports (660). Processor (670) may include various modules associated with embodiments of the present disclosure.

[0167] In an embodiment, the components of the computer system (600) may be utilized to implement the functions of the PGW (208) and one or more network functions (NFs) described in the present disclosure. The processor (670) may execute computer-executable instructions stored in the main memory (630) or mass storage (650) to perform the method steps, such as: receiving an update request for a subscriber profile from external entities (e.g., the FMS or NMS), updating the subscriber profile in the data repository (210), modifying the predetermined custom field, broadcasting notifications via the database stream, and determining session presence within the local cache. The main memory (630) may temporarily store the subscriber profile data, cached values, flags, and intermediate results generated during these operations. The mass storage (650) may persistently store subscriber profile records, configuration files, and program modules required for executing the subscriber-profile management logic. The communication port (660) facilitates the exchange of signaling or data with other network functions, such as the PCF, AMF, or external entities. Thus, FIG. 6 illustrates an exemplary computing platform capable of enabling or hosting the software modules and procedures necessary to carry out the system and method for managing subscriber profile updates as disclosed herein.

[0168] The communication port (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 (660) may be chosen depending on a network, such a LocalArea Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects.

[0169] The memory (630) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. 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).

[0170] The mass storage (650) may be any current or future mass storage solution, which may be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).

[0171] The bus (620) communicatively couples the processor(s) (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).

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

[0173] In an exemplary embodiment, a system for managing a subscriber profile update in a network is disclosed. The system includes a data repository and a PGW coupled to the data repository. The PGW is configured to receive an update request for a subscriber profile from one or more external sources, update the subscriber profile in the data repository based on the update request, modify a predetermined custom field of the subscriber profile in the data repository, and broadcast, via a database stream, a notification comprising at least one subscriber identifier associated with the updated subscriber profile. The system further includes a first network function (NF) configured to receive the broadcasted notification from the PGW and determine whether a session associated with the at least one subscriber identifier exists in a local cache. The disclosed system is industrially applicable in telecommunication networks, particularly for 5G / 6G network function scalability.

[0174] In another exemplary embodiment, a computer program product is disclosed. The computer program product includes a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing a subscriber profile update in a network. The method includes receiving, by a processing entity, an update request for a subscriber profile from one or more external sources, updating the subscriber profile in a data repository based on the update request, modifying a predetermined custom field of the subscriber profile in the data repository, broadcasting, by the processing entity, via a database stream, a notification comprising at least one subscriber identifier associated with the updated subscriber profile, and determining, by a first network function (NF), whether a session associated with the at least one subscriber identifier exists in a local cache upon receiving the broadcasted notification.

[0175] The present disclosure provides a technical advancement in subscriber profile and policy management within telecommunication networks by enabling realtime management of subscriber updates through a database stream-based notification mechanism. Unlike conventional approaches, where subscriber policy modifications are propagated through multiple network entities, for instance, a Charging Function (CHF) sending a Subscriber Notification Request (SNR) to the PCF based on plan change information received from the Online Charging System (OCS) via the Sy interface, the present disclosure provides a direct, event-driven framework in which the PGW automatically broadcasts subscriber profile updates via a database stream. The PCF, upon receiving the broadcast notification, determines whether a session exists in its local cache and, if present, retrieve the updated subscriber profile to compare the predetermined custom field (for example, Custom Field 5) with the corresponding cached value. Upon detecting a change in the custom field, the PCF triggers an N1N2 message transfer request towards the AMF to immediately apply the updated policy at the UE. This approach eliminates intermediate signaling between the OCS, CHF, and PCF, substantially reduces network cost and signaling overhead, and ensures that updated subscriber policies are delivered to the UE in near real time. Furthermore, the system supports scalability across multiple data repositories, PCF / AMF clusters, and external systems such as FMS, NMS, and NEF, ensuring adaptability in large-scale 5G and future 6G deployments. The present disclosure, therefore, enhances network responsiveness, reduces operational latency, and improves policy consistency, providing a significant advancement in dynamic subscriber and policy management for next-generation telecommunication networks.

[0176] The method (500) and system (108) of the present disclosure may be implemented in a number of ways. For example, the method (500) and system (108) 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 presentdisclosure 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.

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

[0178] The present disclosure provides a system and a method that enable updating of User Equipment (UE) policy based on service provisioning updates reflected in the subscriber profile, thereby ensuring that any change in subscriber data directly triggers corresponding policy modifications.

[0179] The present disclosure facilitates initiation of an N1N2 message transfer request towards the Access and Mobility Management Function (AMF) to update the UE policy in the UE, significantly reducing latency and saving time in reflecting policy changes on the UE.

[0180] The present disclosure reduces overall network cost associated with policy update procedures by eliminating intermediate signaling dependencies and enabling direct communication between a Provisioning Gateway (PGW) and the Policy Control Function (PCF) through a database stream.

[0181] The present disclosure minimizes dependency on multiple network services, thereby simplifying policy update operations and ensuring immediate and reliable reflection of updated policies on the UE.

Claims

We claim:

1. A method (500) for managing a subscriber profile update in a network (106), the method (500) comprising: receiving (502), by a provisioning gateway (PGW) (208), an update request for a subscriber profile from one or more external sources (110); updating (504), by the PGW (208), the subscriber profile in a data repository (210) based on the update request; modifying (506), by the PGW (208), a predetermined custom field of the subscriber profile in the data repository (210); broadcasting (508), by the PGW (208), via a database stream, a notification comprising at least one subscriber identifier associated with the updated subscriber profile; and on receiving the broadcasted notification, determining (510), by a first network function (NF) (304), whether a session associated with the at least one subscriber identifier exists in a local cache.

2. The method (500) as claimed in claim 1, wherein if the session exists in the local cache, the first NF (304) retrieves the updated subscriber profile from the data repository (210) and compares the predetermined custom field in the retrieved subscriber profile with a corresponding cached value stored to detect whether the predetermined custom field has changed relative to the cached value.

3. The method (500) as claimed in claim 2, wherein upon detecting a change in the predetermined custom field, the first NF (304) performs at least one operation to manage the subscriber profile in the data repository (210), whereinthe at least one operation comprises initiating a network signaling procedure to update a subscriber policy at a second NF (206), and wherein the network signaling procedure comprises: initiating, by the first NF (304), an N1N2 message transfer request towards a second NF (306) to apply an updated subscriber policy, wherein the first NF (304) triggers the N1N2 message transfer request upon detecting the change in the predetermined custom field.

4. The method (500) as claimed in claim 1, wherein if the session does not exist in the local cache, the first NF (304) logs the notification for deferred action in a pending-update queue.

5. The method (500) as claimed in claim 1 , wherein the database stream comprises a publish-subscribe communication channel configured to transmit real-time update events.

6. The method (500) as claimed in claim 1, wherein the local cache stores active session context data.

7. The method (500) as claimed in claim 1, further comprising: monitoring, by the first NF (304), the database stream at a predefined configurable intervals for the notification broadcasted by the PGW (208), wherein the first NF (304) is configured to subscribe to the database stream to receive push notifications.

8. A system (108) for managing a subscriber profile update in a network (106), the system (108) comprising: a data repository (210);a provisioning gateway (PGW) (208) coupled to the data repository (210) and is configured to execute instructions stored in the data repository (210) to: receive an update request for a subscriber profile from one or more external sources (110); update the subscriber profile in a data repository (210) based on the update request; modify a predetermined custom field of the subscriber profile in the data repository (210); broadcast, via a database stream, a notification comprising at least one subscriber identifier associated with the updated subscriber profile; and a first network function (NF) (304) configured to: receive the broadcasted notification from the PGW (208); and determine whether a session associated with the at least one subscriber identifier exists in a local cache.

9. The system (108) as claimed in claim 8, wherein if the session exists in the local cache, the first NF (304) is configured to: retrieve the updated subscriber profile from the data repository (210) and compare the predetermined custom field in the retrieved subscriber profile with a corresponding cached value stored to detect whether the predetermined custom field has changed relative to the cached value10. The system (108) as claimed in claim 9, wherein upon detecting a change in the predetermined custom field, the first NF (304) is further configured to: perform at least one operation to manage the subscriber profile in the data repository (210), wherein the at least one operation comprises initiating anetwork signaling procedure to update a subscriber policy at a second NF (306), and wherein the network signaling procedure comprises: initiate an N1N2 message transfer request towards a second NF (306) by the first NF (304) to apply an updated subscriber policy, wherein the first NF (304) triggers the N1N2 message transfer request upon detecting the change in the predetermined custom field.

11. The system (108) as claimed in claim 8, wherein if the session does not exist in the local cache, the first NF (304) foregoes initiation of the at least one operation.

12. The system (108) as claimed in claim 8, wherein the database stream comprises a publish-subscribe communication channel configured to transmit real-time update events.

13. The system (108) as claimed in claim 8, wherein the local cache stores active session context data.

14. The system (108) as claimed in claim 8, wherein the first NF (304) is configured to monitor the database stream at a predefined configurable intervals for the notification broadcasted by the PGW (208), wherein the first NF (304) is configured to subscribe to the database stream to receive push notifications.

15. A user equipment (UE) (104) communicatively coupled with a system (108) in a network (106), the coupling comprises steps of: receiving, by the system (108), a connection request; sending, by the system (108), an acknowledgment of the connection request to the UE (104); andtransmitting a plurality of signals in response to the connection request, wherein the system (108) is configured for managing a subscriber profile update, as claimed in claim 8.

16. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for managing a subscriber profile update in a network (106), the method (500) comprising: receiving, by a processing entity (208), an update request for a subscriber profile from one or more external sources (110); updating, by the processing entity (208), the subscriber profile in a data repository (210) based on the update request; modifying, by the processing entity (208), a predetermined custom field of the subscriber profile in the data repository (210); broadcasting, by the processing entity (208), via a database stream, a notification comprising at least one subscriber identifier associated with the updated subscriber profile; and on receiving the broadcasted notification, determining, by a first network function (NF) (304), whether a session associated with the at least one subscriber identifier exists in a local cache.

Images