Method and system for managing transactions in a telecommunication network

Abstract

The present disclosure relates to a system (108) and a method (400) for managing message subscriptions in a communication network. The method (400) includes a first network function (204) to receive a request corresponding to a User Equipment (UE) from a second network function (202). Further, the first network function (204) identifies at least one parameter from the request. After identifying, the first network function (204) determines a flag status associated with the first network function (204) corresponding to the UE (104) based on the at least one parameter. After determining, the first network function (204) deletes a subscription record associated with the UE (104) from a database (214) based on the at least one parameter upon determining the flag status to be a disabled flag status.

Description

METHOD AND SYSTEM FOR MANAGING TRANSACTIONS IN A TELECOMMUNICATION 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.FIELD OF DISCLOSURE

[0002] The embodiments of the present disclosure generally relate to communication networks. In particular, the present disclosure relates to a system and a method for managing message subscriptions in a communication 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 to indicate otherwise.

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

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

[0006] The term ‘N15 interface’ used herein in the specification refers to an interface for communication between the PCF and the AMF. The N15 interface acts as a reference point between the PCF and the AMF in the case of a non-roaming scenario, the PCF in the visited network and the AMF in the case of a roaming scenario.

[0007] The term ‘Subscriber Control Point (SCP)’ used herein in the specification refers to a network component in telecommunications that manages and processes subscriber-related information, i.e., user-related operations, such as service preferences and account details. The SCP ensures efficient routing, billing, and delivery of services to users by interacting with other network components.

[0008] The term ‘service request’ used herein in the specification refers to a formal request made by a user or the UE to terminate, modify, access, or utilize a specific service within the communication network.

[0009] The term ‘subscription ID’ used herein in the specification refers to a unique ID assigned to a specific subscription (e.g., a data usage plan, a voice calling and texting plan, etc.) associated with the UE within the communication network.

[0010] The term ‘subscription record’ used herein in the specification refers to a detailed data entry in a database of the PCF that contains all relevant information about a subscription (e.g., a data usage plan) associated with the UE, including subscription resources (such as service quality parameters like bandwidth, priority, and latency), service (i.e., a data service) entitlements, usage limits, billing details, and configuration settings.

[0011] The term ‘flag’ is a configurable control parameter within a network function, such as the PCF. It is a boolean variable, for example, isUeUnsubscribeEnabled, which can have one of two status: either enabled or disabled.

[0012] The term ‘message’ used herein refers to service-based interface signalling exchanged between the PCF and the AMF over the N15 interface. The message may be implemented as an API request / response (e.g., HTTP / 2 over TLS) that conveys control information related to policy, registration, session, or notification handling for the UE.

[0013] The term ‘message subscription’ used herein refers to a registration maintained between the PCF and the AMF to receive asynchronous notifications tied to a UE context. The message subscription is represented by the subscription record uniquely identified by a Subscription Identifier (ID) and includes subscription metadata such as a callback / reference endpoint, event scope, validity / expiry, and status.

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

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

[0016] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second- generation (2G) technology was introduced, text messaging and data services became possible. The 3Gtechnology marked the introduction of high-speed internetaccess, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth-generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further.

[0017] In communication networks, managing allocation and deallocation of resources (also referred to as network resources) efficiently is critical to maintaining high performance and service quality. A Policy Control Function (PCF) plays a pivotal role in managing network policies and making decisions related to the network resources allocation and a subscriber management. One essential function of the PCF involves handling unsubscribe requests, which are used to terminate or modify existing subscriptions corresponding to a User Equipment (UE). Some traditional techniques used for managing the subscriptions of the UEs in the communication networks involve a series of well-established processes designed to ensure efficient allocation and deallocation of the network resources.

[0018] Typically, the traditional techniques used for managing the subscriptions requires multiple transactions between network components including the PCF, an Access and Mobility Management Function (AMF), and a Subscriber Control Point (SCP). While the traditional techniques have been effective in managing the subscriptions, however these traditional techniques are associated with several challenges such as high transaction overhead, redundant transactions, latency and performance bottlenecks, inflexibility in adapting to dynamic network conditions.

[0019] Due to these above-listed challenges, there is a need for a more efficient and adaptable technique that enhance network performance and enableeffective network resource management, particularly through improved management of UE subscriptions.

[0020] There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existing prior arts.OBJECTIVES OF THE PRESENT DISCLOSURE

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

[0022] An object of the present disclosure is to provide a method and a system for managing transactions in a communication network.

[0023] Another objective of the present disclosure is to optimize a communication network capacity by authorizing a Policy Control Function (PCF) to initiate unsubscribe requests for User Equipments (UEs) based on a flag status associated with each unsubscribe request. By enabling the PCF to manage these unsubscribe requests, unnecessary transactions and data exchanges within the communication network are minimized.

[0024] Another object of the present disclosure is to provide a flag-based mechanism that allows the PCF to dynamically adjust its behaviour regarding the unsubscribe requests. For example, if the flag status for an unsubscribe request is set to a false flag status, indicating that the unsubscribe request is unnecessary, the PCF may avoid initiating a transaction for the unsubscribe request.

[0025] Another object of the present disclosure is to eliminate the unnecessary transactions, such as redundant unsubscribe requests, through the use of the flag-based mechanism.

[0026] Another object of the present disclosure is to improve the network resources management across the network components (e.g., the PCF, the SCP, the AMF) by minimizing the unnecessary transactions and allowing for dynamic adjustment of a subscriber management process.

[0027] 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

[0028] In an exemplary embodiment, a method for managing message subscriptions in a communication network. The method includes receiving, by a first network function, a request corresponding to a User Equipment (UE) from a second network function. The method includes identifying, by the first network function, at least one parameter from the request. The method includes determining, by the first network function, a flag status associated with the first network function corresponding to the UE based on the at least one parameter. The method includes deleting, by the first network function, a subscription record associated with the UE from a database based on the at least one parameter upon determining the flag status to be a disabled flag status.

[0029] In some embodiments, the flag is configured at the first network function, and the flag status indicates whether a network-initiated unsubscribe procedure is enabled or disabled for the UE based on predefined network conditions.

[0030] In some embodiments, upon determining the flag status to be an enabled flag status, the first network function generates an unsubscribe request corresponding to the request associated with the UE. The first network function sends the unsubscribe request to the second network function.

[0031] In some embodiments, the second network function deletes the subscription record associated with the UE from the database in response to receiving the unsubscribe request from the first network function.

[0032] In some embodiments, the second network function sends a response depicting a successful deletion of the subscription record associated with the UE to the first network function, wherein the deletion indicates unsubscribing the UEfrom network services. Upon receiving the response from the second network function, the first network function deletes the subscription record associated with the UE from the database

[0033] In some embodiments, the at least one parameter comprises a subscription Identifier (ID) associated with the UE.

[0034] In some embodiments, the first network function is a policy control function (PCF) and the second network function is an access and mobility management function (AMF).

[0035] In some embodiments, the flag status can either be enabled or disabled and based on the flag status, an action is determined.

[0036] In some embodiments, the flag is dynamically configured at the first network function based on predefined network conditions, the network conditions comprising at least one of: network congestion thresholds, UE load levels, or policy-based rules.

[0037] In an exemplary embodiment, a system for managing message subscriptions in a communication network. The system includes a receiving unit configured to receive, by a first network function, a request corresponding to a User Equipment (UE) from a second network function. An identification unit configured to identify, by the first network function, at least one parameter from the request. A determination unit configured to determine, by the first network function, a flag status associated with the first network function corresponding to the UE based on the at least one parameter and upon determining the flag status to be a disabled flag status, the determination unit deletes, by the first network function, a subscription record associated with the UE from a database based on the at least one parameter

[0038] In an exemplary embodiment, a User Equipment (UE) communicatively coupled with a network is disclosed. The coupling includes receiving, by the communication network, a connection request from the UE. The coupling includes sending, by the communication network, an acknowledgment ofthe connection request to the UE. The coupling includes transmitting a plurality of signals in response to the connection request, wherein based on the plurality of signals, message subscriptions in the communication network is managed.

[0039] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing message subscriptions in a communication network. The method includes receiving, by a first network function, a request corresponding to a User Equipment (UE) from a second network function. The method includes identifying, by the first network function, at least one parameter from the request. The method includes determining, by the first network function, a flag status associated with the first network function corresponding to the UE based on the at least one parameter. The method includes deleting, by the first network function, a subscription record associated with the UE from a database based on the at least one parameter upon determining the flag status to be a disabled flag status.

[0040] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.BRIEF DESCRIPTION OF DRAWINGS

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

[0042] FIG. 1 illustrates an exemplary network architecture of a system for managing message subscriptions in a communication network, in accordance with an embodiment of the present disclosure.

[0043] FIG. 2A illustrates an exemplary architecture of the system for managing message subscriptions in the communication network, in accordance with an embodiment of the present disclosure.

[0044] FIG. 2B illustrates an exemplary block diagram depicting network components configured for managing message subscriptions in the communication network, in accordance with an embodiment of the present disclosure.

[0045] FIG. 3 illustrates an exemplary process flow for managing message subscriptions in the communication network, in accordance with an embodiment of the present disclosure.

[0046] FIG. 4 illustrates an exemplary process flow of a method managing message subscriptions in the communication network, in accordance with an embodiment of the present disclosure.

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

[0048] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 -User Equipments (UEs)106 - Network108 - System200A -System Architecture202 - Access and Mobility Management Function (AMF) / second network function204 - Policy Control Function (PCF) / first network function200B - Block diagram206 - Processor(s)208 - Memory210 -Interface(s)212 - Processing engine214 - Database216 - Receiving unit218 - Identifying unit220 - Determining unit300 - Flow Diagram400 - Flow Diagram500 - A Computer System510 - External Storage Device520 - Bus530 - Main Memory540 - Read Only Memory550 - Mass Storage Device560 - Communication Port570 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0049] 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 all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

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

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

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

[0053] 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 in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

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

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

[0056] Embodiments herein relate to a method for managing transactions (i.e., transactions associated with unsubscribe requests) in a communication network. In particular, the method includes receiving, by a first network component, a service request including a subscription Identifier (ID) associated with a User Equipment (UE), from a second network component. A subscription ID is a unique ID assigned to a specific subscription (e.g., a data usage plan, a voice calling and text package, etc.) associated with the UE within the communication network. In an embodiment, the first network component may correspond to a Policy Control Function (PCF). The second network component may correspond to an Access and Mobility Management Function (AMF). Upon receiving the service request, the first network component is configured to determine a flag status corresponding to the UE. The flag status is one of an enabled flag status or a disabled flag status. In an embodiment, upon determining the flag status to be the disabled flag status, the first network component is configured to delete a subscription record associated with the UE from a database associated with the first network component based on subscription ID. The subscription record is a detailed data entry in the database that contains all relevant information about a subscription (e.g., the data usage plan)associated with the UE, including service (e.g., a data service) entitlements, usage limits, billing details, and configuration settings. In another embodiment, upon determining the flag status to be the enabled flag status, the first network component is configured to generate an unsubscribe request corresponding to the UE based on the service request. Further, the first network component is configured to send the unsubscribe request to the second network component for deleting the subscription record associated with the subscription ID corresponding to the UE.

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

[0058] FIG. 1 illustrates an exemplary network architecture (100) for managing message subscriptions in a communication network (106), in accordance with embodiments of the present disclosure.

[0059] Referring to FIG. 1, the network architecture (100) may include one or more User Equipments (UEs) (104-1, 104-2. .. 104-N) associated with one or more users (102-1, 102-2. . . 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2. .. 102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that the one or more user equipments (104-1, 104-2. .. 104-N) may be individually referred to as the UE (104) and collectively referred to as the UEs (104). Although three UEs (104) are depicted in FIG. 1, however, any number of the UEs (104) may be included without departing from the scope of the ongoing description. In an embodiment, each of the UE (104) may have a first unique identifier attribute associated therewith. In an embodiment, the first unique identifier attribute may be indicative of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.

[0060] 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 user equipment (104) may include, but is not limited to, intelligent, multi -sensing, network-connected devices that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0061] In an embodiment, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general -purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, 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 thatthe UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0062] Referring to FIG. 1, the UE (104) may communicate with a system (108) via the network (106). The UE (104) may be communicatively coupled with the network (106). The communicative coupling comprises receiving, from the UE (104), a connection request by the network (106), sending an acknowledgment of the connection request to the UE (104), and transmitting a plurality of signals in response to the connection request. In an embodiment, the network (106) may include at least one of a Fourth Generation (4G) network, a Fifth Generation (5G) network, a Sixth Generation (6G) network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

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

[0064] 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) mayperform functions described as being performed by one or more other components of the network architecture (100).

[0065] FIG. 2A illustrates an exemplary system architecture (200A) for managing message subscriptions in the communication network (106), in accordance with an embodiment of the present disclosure. FIG. 2A is explained in conjunction with FIG. 1. Examples of the communication network may include, the 4G network, the 5G network, the 6G network, and the like.

[0066] In an embodiment, the message subscriptions managed by the disclosed system may include at least: (i) an N1N2-Message subscription, whereby the first network function (204) subscribes to notifications ofNl and / or N2 message delivery status / events associated with the UE (104); and (ii) a policy / associati on- related subscription, whereby the first network function (204) subscribes to policy or context change notifications relevant to the UE (104).

[0067] In order to manage the resources in the communication network, an Access and Mobility Management Function (AMF) (202) and a Policy Control Function (PCF) (204) are configured to communicate with each other over an N15 interface. The N15 interface is used for exchanging policy control information and data between the AMF (202) and the PCF (204). Initially, the PCF (204) may receive the service request corresponding to the UE from the AMF (202) over the N15 interface. In an embodiment, the service request may include the subscription ID and the other relevant information such as the UE ID, the service request type (i.e., the delete request or the modify request), the service type or the policy reference associated with the subscription of the UE (104), the service request timestamp, etc., corresponding to the UE (104). In an embodiment, the service request, for example, may correspond to the UE delete request. Examples of the service request may include, but are not limited to, the subscription termination request, the service deactivation request, the data plan reduction request, the roaming service cancellation request, the account deactivation request, the serviceplan change request, and the resource deallocation request. In some embodiments, the service request may correspond to a UE modify request.

[0068] Upon receiving the service request, the PCF (204) determines the flag status corresponding to the UE (104). The flag status may be one of the enabled flag status (i.e., the true flag status) or the disabled flag status (i.e., the false flag status). In an embodiment, the flag may correspond to the Boolean parameter, i.e., ‘isUeUnsubscribeEnabled’. The Boolean parameter ‘isUeUnsubscribeEnabled’ may be used by the PCF (204) to determine whether to initiate the unsubscribe request, i.e., a UE N1N2 message unsubscribe request for the received service request to the AMF (202) or not. In an embodiment, upon determining the flag status to be the disabled flag status, the PCF (204) is configured to directly delete the subscription record corresponding to the UE (104) from the database associated with the PCF (204). The database may correspond to the local cache or the local memory associated with the PCF (204). In an embodiment, the subscription record may be deleted based on the subscription ID associated with the service request. In an embodiment, deletion of the subscription record includes deleting the one or more subscription resources associated with the subscription ID from the database associated with the PCF (204).

[0069] In an embodiment, the direct deletion of the subscription record from the local cache of the PCF (204) ensures that the UE N1N2 message unsubscribe request is not sent by the PCF (204) to the AMF (202). Further, the PCF (204) may not be able to accept an NIMessageNotifiaction sent from the AMF (202) and may result in termination of a service (e.g., a voice calling service, a video calling service, a data service, etc) associated with the subscription. The service may also be referred to as a network service. In other words, when the subscription record from the local cache of the PCF (204) is deleted, the PCF (204) loses access to relevant information (i.e., relevant subscription details) corresponding to the UE (104) that are necessary for processing network communications and managing network services for the user (102) (also referred to as a subscriber) of the UE (104). The NIMessageNotification is a type of a response message sent from the AMF(202) to the PCF (204), usually to notify about changes or updates (e.g., the deletion of the subscription record) related to the subscription of the UE (104).

[0070] In another embodiment, upon determining the flag status to be the enabled flag status, the PCF (204) is configured to generate and send the unsubscribe request (i.e., the UE N1N2 message unsubscribe request) corresponding to the service request to the AMF (202). In some embodiment, the UE N1N2 message unsubscribe request may be sent towards the UE (104). Further, upon receiving the UE N1N2 message unsubscribe request, the AMF (202) is configured to delete the subscription record corresponding to the UE (104) from the database (214), based on the subscription ID. Once the subscription record is deleted, the AMF (202) sends the response, i.e., the status code (the OK success response) depicting the successful deletion of the subscription record to the PCF (204). The response indicates that the subscription record identified using the subscription ID is successfully deleted.

[0071] Although FIG. 2 A 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. 2A. 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).

[0072] FIG. 2B illustrates an exemplary block diagram (200B) of the system (108) for managing message subscriptions in the communication network (106), in accordance with an embodiment of the present disclosure. FIG. 2B is explained in conjunction with FIGS. 1 and 2A.

[0073] FIG. 2B illustrates the block diagram of the system (108), which may be implemented in the Policy Control Function (PCF) (204) or the Access and Mobility Management Function (AMF) (202). It should be understood that the AMF (202) and the PCF (204) described herein and shown in the figures, such as Figure 2A, are physical hardware components. The AMF (202) and the PCF (204)may be implemented as a dedicated hardware appliance, a virtualized network function (VNF) running on a server, or a combination of hardware and software.

[0074] In an embodiment, the PCF (204) comprise one or more processor(s) (206), a memory (208), an interface (210), a processing engine (212) and a database (214) to perform the functions described herein.

[0075] In an embodiment, the system (108) may include the one or more processor(s) (206). The one or more processor(s) (206) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (206) may be configured to fetch and execute computer- readable instructions stored in the memory (208) of the system (108). The memory (208) 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 (208) may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a nonvolatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0076] In an embodiment, the system (108) may include the interface(s) (210). The interface(s) (210) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as VO devices, storage devices, and the like. The interface(s) (210) may facilitate communication of the system (108). The interface(s) (210) 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, the processing engine (212) and the database (214).

[0077] The processing engine (212) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (228). In examplesdescribed herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (212) may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the processing engine (212) may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine- readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (212). In such examples, the system (108) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine- readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine (212) may be implemented by an electronic circuitry. The processing engine (212) further comprises a receiving unit (216), an identifying unit (218) and a determining unit (220).

[0078] In an embodiment, the database (214) may include data that may be either stored or generated as a result of functionalities implemented by the processing engine (212). In an embodiment, the database (214) may be separate from the system (108). In an embodiment, the database (214) may be indicative of including, but not limited to, a relational database, a distributed database, a cloudbased database, or the like. In an embodiment, the subscription record stored in the database (214) of the first network function (204) may comprise a structured schema including, but not limited to, the following fields: subscription identifier, UE identifier, subscription entitlements (e.g., data plan, voice / SMS plan, or roaming plan), Quality of Service (QoS) parameters (e.g., bandwidth, latency, priority), usage limits (e.g., volume-based, time-based, or event-based thresholds), billing or charging references, and configuration settings (e.g., active / inactive state, policy reference, or unsubscribe flag). Further, the second network function (202) maintains its own context-centric subscription records in a database. The subscription records of the second network function (202) typically include UEidentifiers, registration state, subscription identifiers, and N1N2 message subscription information required to manage UE access and mobility procedures. During an unsubscribe operation, both the first network function (204) and the second network function (202) delete their respective subscription records to ensure synchronized state management and consistency across the communication network (106).

[0079] In an embodiment, the receiving unit (216) is configured to receive by the first network function (204) the request corresponding to the UE (104) from the second network function (202). The first network function (204) and the second network function (202) are logical or physical components within the communication network, such as a 5G core network. In some embodiments, the first network function (204) is the PCF and the second network function (202) is the AMF. The first network function (204) comprises the processing engine (212) to perform the functions described herein. The second network function (202) is likewise provisioned to process requests exchanged with the first network function (204). The processing engine (212) is configured to execute the instructions stored in the memory (208) to carry out the functions of the system (108).

[0080] In an embodiment, the request comprises one or more parameters used for processing the subscription such the subscription ID associated with the UE (104). The subscription ID is a unique ID assigned to a specific subscription (e.g., a data usage plan, a voice calling and texting plan, a video calling plan, a roaming plan, etc.) associated with the UE (104) within the communication network (106). In addition to the subscription ID, the service request may include other relevant information, such as a UE ID, a service request type (i.e., a delete request or a modify request), a service type or a policy reference associated with a subscription of the UE (104), a service request timestamp, etc. In an embodiment, the service request, for example, may correspond to the UE delete request. Examples of the service request may include, but are not limited to, the subscription termination request, the service deactivation request, the data plan reduction request, the roaming service cancellation request, the account deactivation request,the service plan change request, and the resource deallocation request. In some embodiment, the service request may correspond to a UE modify request.

[0081] In an embodiment, the identifying unit (218) is configured to identify, by the first network function (204), at least one parameter from the request. The identified parameter may include, for example, the Subscription ID, a UE context identifier, or another unique identifier associated with a subscription state of the UE (104) within the network (106). The identified parameter is utilized by the processing engine (212) of the first network function (204) to map the request to a subscription record stored in the database (214). The identification of the at least one parameter ensures that the subsequent operations, including subscription record deletion or initiation of unsubscribe procedures, are accurately targeted to the correct UE context.

[0082] In an embodiment, the determining unit (220) is configured to determine by the first network function (204), a flag status associated with the first network function (204) corresponding to the UE (104) based on the at least one parameter. The flag status may be one of the enabled flag status (i.e., a true flag status) or the disabled flag status (i.e., a false flag status). In an embodiment, the flag may correspond to a Boolean parameter. The Boolean parameter, for example may be ‘isUeUnsubscribeEnabled’. The Boolean parameter ‘isUeUnsubscribeEnabled’ may be used by the PCF (204) to determine whether to initiate an unsubscribe request for the received service request to the AMF (202) or not. In particular, the PCF (204) is configured to determine whether the Boolean parameter ‘isUeUnsubscribeEnabled’ within the PCF (204) is enabled or disabled. The processing engine (212) retrieves the flag configuration from the memory (208) and evaluates status of the flag. This determination serves as a decision gate for subsequent actions. The flag may be configured globally for all UEs (104) handled by the first network function (204), per slice (S-NSSAI), per data network name (DNN), or even per individual UE context, thus providing flexibility in network resource management. For instance, the flag could be set to disabled if network congestion is high, if the UE (104) is known to have a temporary subscription, or ifthe subscription record is considered non-critical for network-wide synchronization. Conversely, the flag could be set to enabled for a permanent UE subscription that requires a coordinated deletion across multiple network functions. The determination of the flag status is based on the parameter identified from the request, such as the Subscription ID, which may have an associated policy or profile indicating the flag status.

[0083] In an embodiment, the conditions affecting whether the flag is enabled or disabled may be determined by predefined network policies or dynamic runtime conditions. Examples of such conditions include congestion thresholds in the communication network (106), real-time UE load levels handled by the first network function (204), or slice-specific rules defined in a network policy database. For instance, if the overall network congestion is high, the flag may automatically toggle to a disabled state to reduce signalling overhead and prevent propagation of unsubscribe requests to the second network function (202). Conversely, if the UE (104) belongs to a premium slice with guaranteed service continuity, the flag may be enabled to ensure coordinated deletion across both the first network function (204) and the second network function (202). Other conditions may include policybased triggers, such as expiry of a subscription plan, administrative overrides, or QoS-related constraints, where the network operator enforces coordinated unsubscribe procedures for certain classes of UEs.

[0084] In an embodiment, the flag is configured at the first network function (204), and the flag status explicitly indicates whether a network-initiated unsubscribe procedure is enabled or disabled for the UE (104). The configuration may be applied dynamically by the user (102) through network management interfaces or preconfigured as a static parameter. In some variations, the flag may be automatically toggled by the system (108) based on predefined network conditions such as congestion thresholds, UE load, or policy rules. This dynamic configurability allows the network (106) to balance between signalling efficiency and consistency of state synchronization across network functions. For example, a network-initiated unsubscribe action may occur when the first network function(204) autonomously triggers deletion of an N1N2 message subscription due to network congestion or expiry of a temporary subscription, without any explicit signalling from the UE (104). Conversely, a UE -initiated action may occur when the UE (104) sends a deregistration request, a session release request, or a context release procedure, which in turn causes the second network function (202) to notify the first network function (204) for deletion of the subscription record. In an embodiment, the behaviour of the flag may vary depending on network policies and operational scenarios. For example, the flag may be toggled to the disabled status when the UE (104) has a short-term subscription, when the network (106) experiences congestion above a predefined threshold, or when the subscription record is classified as non-critical. Conversely, the flag may be toggled to the enabled status for long-term or premium subscriptions, where coordinated deletion across the first network function (204) and the second network function (202) is essential to maintain service continuity. The flag status may therefore be preconfigured during network setup, dynamically updated by the processing engine (212) based on policy rules, or explicitly set by the user (102) through network management interfaces, thereby supporting both user-defined and automated control.

[0085] In an embodiment, the term configured at the first network function (204) refers to the fact that the flag, i.e., the Boolean parameter isUeUnsubscribeEnabled, is stored within the database (214) of the first network function (204) as a configurable parameter. The configuration of the flag may be performed in one of several ways. In one embodiment, the network operator or the user (102) explicitly sets the value of the flag through a network management interface, such as an Operations Support System (OSS), Element Management System (EMS), or through standard provisioning protocols. In another embodiment, the flag value may be controlled automatically by policy logic within the first network function (204). For example, the processing engine (212) may toggle the flag in response to predefined network conditions, such as congestion thresholds, UE load, or slice-specific policies defined in a policy database. In yet anotherembodiment, the flag may be configured per subscription profile, wherein the subscription ID of the UE (104) is mapped to a configuration entry that dictates whether unsubscribe requests must be coordinated with the second network function (202). Thus, configuration and control of the flag can be achieved through a combination of manual operator input, automated policy enforcement, or subscription-specific profiles, ensuring flexibility in balancing signalling efficiency and state consistency across the network (106).

[0086] When the first network function (204) determines that the Boolean parameter ‘isUeUnsubscribeEnabled’ is enabled, the flag status is determined to be the enabled flag status. Further, when the first network function (204) determines that the Boolean parameter ‘isUeUnsubscribeEnabled’ is disabled, the flag status is determined to be the disabled flag status. The flag, referred to as isUeUnsubscribeEnabled, is configured at the first network function (204). The flag, which is stored in the database (214) of the first network function (204) as a configurable parameter, indicates whether a network-initiated unsubscribe procedure is enabled or disabled for the UE (104).

[0087] In an embodiment, the determining unit (220) is configured to delete by the first network function (204) the subscription record associated with the UE (104) from the database (214) based on the at least one parameter upon determining the flag status to be a disabled flag status. The database (214) may correspond to a local cache or a local memory associated with the first network function (204) and ensures that the UE N1N2 message unsubscribe request is not sent by the first network function (204) to the second network function (202). The deletion is performed based on the at least one parameter received in the initial request (e.g., the Subscription ID). Further, the first network function (204) may not be able to accept the NlMessageNotifiaction sent from the second network function (202) and may result in termination of a service (e.g., a voice calling service, a video calling service, a data service, etc) associated with the subscription. The service may also be referred to as the network service. In other words, when the subscription record from the local cache of the first network function (204) is deleted, the first networkfunction (204) loses access to relevant information (i.e., relevant subscription details) corresponding to the UE (104) that are necessary for processing network communications and managing network services for the user (also referred to as a subscriber) of the UE (104). The NIMessageNotification is a type of a response message sent from the second network function (202) to the first network function (204), usually to notify about changes or updates (e.g., the deletion of the subscription record) related to the subscription of the UE (104). In other words, upon determining the flag status to be the disabled flag status, the first network function (204) directly delete the subscription record associated with the UE (104) based on the subscription ID to remove an ongoing subscription (e.g., the data usage plan) of the UE (104) efficiently without sending the unsubscribe request to the second network function (202).

[0088] In an alternate embodiment, when the flag status is determined to be an enabled flag status, the first network function (204) generates the unsubscribe request corresponding to the request associated with the UE (104). The unsubscribe request may be the UE N 1N2 message unsubscribe request. The UE N 1N2 message unsubscribe request is a signalling message in 5G networks used to formally request a termination or a modification of a subscription. The UE N1N2 message unsubscribe request facilitates communication between the first network function (204) and the second network function (202) to manage the subscriptions associated with the UE (104). Further, upon receiving the UE N1N2 message unsubscribe request, the second network function (202) is configured to delete the subscription record associated with the UE (104) from the database (214) based on the subscription ID. Deleting the subscription record includes the deletion of one or more subscription resources associated with the subscription ID. Further, the second network function (202) is configured to send the response depicting a successful deletion of the subscription record to the first network function (204). In other words, when the subscription records are deleted based the UE N 1N2 message unsubscribe request received from the first network function (204), the second network function (202) may send the response (e.g., a status code, i.e., an OKsuccess response) to the first network function (204). The response indicates that the subscription record identified using the subscription ID is successfully deleted. In an embodiment, the management of the transactions in the communication network (106) is performed to reduce unnecessary transactions (i.e., unnecessary unsubscribe requests, such as robust unsubscribe requests, or redundant unsubscribe requests) between the second network function (202) and the first network function (204).

[0089] In some embodiment, the managing of the transactions in the communication network (106) may be performed between the second network function (202), the first network function (204), and a Subscriber Control Point (SCP) to reduce unnecessary transactions between the second network function (202), the first network function (204), and the SCP. By reducing the unnecessary transactions between the network components, a network capacity (i.e., a capacity of the communication network) and a process of management of the network resources (e.g., bandwidth, processing power, memory, network links, and the like) across the network components may be optimized.

[0090] In an embodiment, the first network function (204) is configured to generate the unsubscribe request corresponding to the initial request from the second network function (202). The first network function (204) sends the unsubscribe request to the second network function (202). This process ensures that when a network-wide coordinated deletion is required, the proper signalling flow is followed. The unsubscribe request informs the second network function (202) that its corresponding subscription records for the UE (104) should be deleted.

[0091] In an embodiment, the second network function (202) is configured delete the subscription record associated with the UE (104) from the database (214). This action synchronizes the state of the subscription between the two network functions. The second network function (202) then sends a response depicting a successful deletion to the first network function (204). This response confirms that the subscription has been successfully deleted at the second network function (202).Upon receiving this response, the first network function (204) also deletes its own subscription record associated with the UE from its database, completing the synchronized deletion process. This multi-step procedure is essential for maintaining consistency across the network (106) when the flag is enabled.

[0092] FIG. 3 illustrates an exemplary process flow (300) for managing message subscriptions in the communication network (106), in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIGS. 1, 2 A, and 2B. The transactions may correspond to the transactions associated with the unsubscribe requests.

[0093] Initially, at step 302, the PCF (204) may be configured to receive a UE delete request from the AMF (202). The UE delete request may correspond to the service request. Examples of the service request may include, the subscription termination request, the service deactivation request, the data plan reduction request, the roaming service cancellation request, the account (i.e., the user account associated with the user (102) of the UE (104)) deactivation request, the service plan change request, the resource (i.e., the network resource) deallocation request. In an embodiment, the service request may include the subscription ID and other relevant information associated with the UE (104). The other relevant information includes, for example the UE ID, the service request type (i.e., the delete request or the modify request), the service type or the policy reference associated with the subscription of the UE (104), the service request timestamp, and the like.

[0094] Upon receiving the UE delete request from the AMF (202), at step 304, the PCF (204) is configured to perform a check to determine a status (i.e., the flag status) of the flag corresponding to the UE (104). The flag status may be one of the enabled flag status (i.e., the true flag status) or the disabled flag status (i.e., the false flag status). Further, the flag may correspond to the Boolean parameter, i.e., ‘isUeUnsubscribeEnabled’. In an embodiment, the ‘isUeUnsubscribeEnabled’ Boolean parameter (or the flag) within the PCF (204) enables the PCF (204) to determine whether to initiate the unsubscribe request, i.e., the UE NlN2Messageunsubscribe request to the AMF (202) or not, for terminating the subscription of the UE (104) based on the service request.

[0095] Upon determining the flag status to be the disabled flag status, i.e., the false flag status, at step 306, the PCF (204) is configured to delete the subscription record associated with the UE (104) from the local cache (e.g., the database 210), based on the subscription ID. For example, the subscription record may include the one or more subscription resources (such as service quality parameters like bandwidth, priority, and latency), the service (such as the data service, the voice calling service, etc.) entitlements, the access permissions, the billing information, etc., associated with the subscription of the UE (104). In other words, the PCF (204) may be configured to delete the one or more existing subscription resources identified using the subscription ID associated with the UE (104) from the database associated with the PCF (204).

[0096] In another embodiment, based on the check performed at step 304, upon determining the flag status to be the enabled flag status, at step 308, the PCF (204) is configured to generate and send the unsubscribe request corresponding to the service request to the AMF (202). The PCF (204) sends the unsubscribe request to delete the subscription record associated with the subscription ID that is present in the AMF (202). In an embodiment, the unsubscribe request may be the UE N 1N2 message unsubscribe request. The UE N1N2 message unsubscribe request is the signalling message in the 5G networks used to formally request the termination or the modification of the subscription. In some embodiments, the UE N1N2 message unsubscribe request may be sent towards the UE (104). Further, upon receiving the UE N1N2 message unsubscribe request, the AMF (202) is configured to delete the subscription record identified using the subscription ID corresponding to the UE (104). In an embodiment, deleting the subscription record includes deletion of one or more subscription resources associated with the subscription ID.

[0097] Once the one or more subscription resources are deleted, at step 310, the AMF (202) sends the response depicting the successful deletion of the at leastone resource to the PCF (204). The response for example may be the status code, i.e., the OK success response. The response indicates that the one or more subscription resources identified by the subscription ID are successfully deleted. Once the PCF (204) receives the response, the PCF (204) is configured to delete the subscription ID from the local cache as mentioned via step 306. In an embodiment, by allowing the PCF (204) to decide when to initiate the unsubscribe requests, the unnecessary transactions between the AMF (202), the PCF (204), and the SCP are significantly decreased. This significant decrease in the unnecessary transactions between the AMF (202), the PCF (204), and the SCP, provides and efficient management of the network resources within the communication network (106), thereby enhancing the capacity of the communication network (106).

[0098] FIG. 4 illustrates an exemplary flowchart of a method (400) for managing message subscriptions in the communication network (106), in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIG. 1, FIG. 2 and FIG. 3.

[0099] At step 402, the method (400) comprises receiving, by the first network function (204), a request corresponding to the User Equipment (UE) from the second network function (202). The first network function (204) is the Policy Control Function (PCF) (204), while the second network function (202) is the Access and Mobility Management Function (AMF) (202). The request may include signalling messages such as session establishment, modification, or termination requests that carry identifiers of the UE. This initial request serves as the trigger for the entire subscription management process.

[0100] At step 404, the method (400) further comprises identifying, by the first network function (204), the at least one parameter from the received request. The at least one parameter is the subscription Identifier (ID), which uniquely associates the UE (104) with its subscription record stored in one or more databases. In operation, the first network function (204) uses internal parsing modules or application-layer message interpreters to extract the subscription ID from thepayload of the signalling message. This linkage allows the first network function (204) to determine which subscription record must be evaluated or deleted in subsequent steps.

[0101] At step 406, the method (400) comprises determining, by the first network function (204), the flag status associated with the first network function (204) corresponding to the UE based on the at least one parameter. The flag status may be one of the enabled flag status (i.e., the true flag status) or the disabled flag status (i.e., the false flag status). In an embodiment, the flag may correspond to the Boolean parameter, i.e., ‘isUeUnsubscribeEnabled’. The Boolean parameter ‘isUeUnsubscribeEnabled’ may be used by the first network function (204) to determine whether to initiate the unsubscribe request, i.e., the UE N1N2 message unsubscribe request for the received service request to the second network function (202) or not. The status of this flag (either enabled or disabled) is dynamically determined based on the received at least one parameter and predefined network conditions or policies. For example, if the subscription ID indicates a temporary or non-critical subscription, the flag status might be set to disabled to optimize network traffic. Conversely, a long-term or high-priority subscription might have the flag status set to enabled.

[0102] In an embodiment, the flag is explicitly configured at the first network function (204). The configuration may be provisioned by network operators during service deployment or dynamically updated by network orchestration systems. The flag status directly indicates whether the unsubscribe procedure is handled locally (disabled status) or requires inter-function coordination (enabled status).

[0103] At step 408, the method (400) comprises upon determining the flag status to be the disabled flag status, deleting, by the first network function (204), the subscription record associated with the UE (104) from the database (214) based on the at least one parameter. When the determination in the previous step results in a disabled status, the first network function (204) proceeds with a local deletion.The first network function (204) removes the subscription record from the database (212) or cache, using the subscription ID as the key. By taking this action, the method saves a network transaction, as there is no need to send a formal unsubscribe request to the second network function (202). This directly leads to more efficient use of network resources, as described in the previous response. This is a crucial step that distinguishes this method from traditional subscription management procedures.

[0104] In an embodiment, the method (400) comprises upon determining the flag status to be an enabled flag status, generating, by the first network function (204), an unsubscribe request corresponding to the request associated with the UE (104) and sending, by the first network function (204), the unsubscribe request to the second network function (202). This step describes the alternative path of the method (400). If the flag status is determined to be enabled, the method (400) reverts to a traditional, coordinated unsubscribe procedure. The first network function (204) creates the unsubscribe request and transmits it to the second network function (202) to ensure a consistent deletion of the subscription record across both network functions.

[0105] In an embodiment, the method (400) includes in response to receiving the unsubscribe request from the first network function (204), deleting, by the second network function (202), the subscription record associated with the UE (104) from the database (214). In the case where the flag was enabled, this step is performed by the second network function (202) upon receiving the unsubscribe request. This action ensures that the subscription record is properly removed from the database of the second network function (202), thereby synchronizing the subscription state between the first network function (204) and the second network function (202).

[0106] In an embodiment, the method (400) comprises sending, by the second network function (202), the response depicting the successful deletion of the subscription record associated with the UE (104) to the first network function(204), wherein the deletion indicates unsubscribing the UE from network services; and upon receiving the response from the second network function (202), deleting, by the first network function (204), the subscription record associated with the UE (104) from the database (214). The second network function (202) sends the success message (e.g., status code 204) back to the first network function (204). Upon receiving this confirmation, the first network function (204) can safely delete its local copy of the subscription record, completing the process for the enabled flag scenario.

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

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

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

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

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

[0112] In an exemplary embodiment, a User Equipment (UE) communicatively coupled with a network is disclosed. The coupling includes receiving, by the communication network, a connection request from the UE. The coupling includes sending, by the communication network, an acknowledgment of the connection request to the UE. The coupling includes transmitting a plurality of signals in response to the connection request, wherein based on the plurality of signals, message subscriptions in the communication network is managed.

[0113] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the oneor more processors to execute a method for managing message subscriptions in a communication network. The method includes receiving, by a first network function, a request corresponding to a User Equipment (UE) from a second network function. The method includes identifying, by the first network function, at least one parameter from the request. The method includes determining, by the first network function, a flag status associated with the first network function corresponding to the UE based on the at least one parameter. The method includes deleting, by the first network function, a subscription record associated with the UE from a database based on the at least one parameter upon determining the flag status to be a disabled flag status.

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

[0115] The present disclosure provides a technical advancement in managing service requests in a communication network by introducing a racecondition handling mechanism at the Policy Control Function (PCF). Through the use of a request queue and suppression logic, the PCF prevents simultaneous execution of identical requests such as UE create, session management create, or delete requests, ensuring that only one request is processed at a time while subsequent requests are deferred. The present disclosure reduces signalling overhead, avoids inconsistent network states from duplicate processing, and enhances the efficiency, reliability, and stability of session and resource management.ADVANTAGES OF THE PRESENT DISCLOSURE

[0116] The present disclosure provides a method and a system for managing transactions in a communication network.

[0117] The present disclosure optimizes a communication network capacity by authorizing a Policy Control Function (PCF) to initiate unsubscribe requests for User Equipments (UEs) based on the status of a flag associated with each unsubscribe request. By enabling the PCF to manage these unsubscribe requests, unnecessary transactions and data exchanges within the network are minimized. This leads to more effective utilization of network resources, such as a bandwidth, a processing power, etc., and ensures that only essential operations are performed.

[0118] The present disclosure provides a flag-based mechanism that allows the PCF to dynamically adjust its behaviour regarding the unsubscribe requests. For example, if the status of the flag for an unsubscribe request is set to a false flag status, indicating that the unsubscribe request is unnecessary, the PCF may avoid initiating a transaction for the unsubscribe request. This tuning capability of the flag status enables the PCF to take actions in real-time, optimizing the network resources management according to current network conditions and requirements.

[0119] The present disclosure eliminates the unnecessary transactions, such as redundant unsubscribe requests through the use of the flag-based mechanism. The reduction in the unnecessary transactions helps conserve the network resources and prevents overload on network components, including the PCF, a Subscriber Control Point (SCP), and an Access and Mobility Management Function (AMF).

[0120] The present disclosure improves the network resources management across the network components (e.g., the PCF, the SCP, the AMF) by minimizing the unnecessary transactions and allowing for dynamic adjustment of a subscriber management process. The improvement in the network resources management leads to enhanced performance, reduced operational costs, and better overall network scalability and reliability

Claims

CLAIMS1. A method (400) for managing message subscriptions in a communication network (106), the method (400) comprising: receiving (402), by a first network function (204), a request corresponding to a User Equipment (UE) (104) from a second network function (202); identifying (404), by the first network function (204), at least one parameter from the request; determining (406), by the first network function (204), a flag status associated with the first network function (204) corresponding to the UE based on the at least one parameter; and upon determining the flag status to be a disabled flag status, deleting (408), by the first network function (204), a subscription record associated with the UE (104) from a database (214) based on the at least one parameter.

2. The method (400) as claimed in claim 1, wherein the flag is configured at the first network function (204), and the flag status indicates whether a network-initiated unsubscribe procedure is enabled or disabled for the UE (104) based on predefined network conditions.

3. The method (400) as claimed in claim 1, further comprising: upon determining the flag status to be an enabled flag status, generating, by the first network function (204), an unsubscribe request corresponding to the request associated with the UE (104); and sending, by the first network function (204), the unsubscribe request to the second network function (202).

4. The method (400) as claimed in claim 3, further comprising:in response to receiving the unsubscribe request from the first network function (204), deleting, by the second network function (202), the subscription record associated with the UE (104) from the database.

5. The method (400) as claimed in claim 4, further comprising: sending, by the second network function (202), a response depicting a successful deletion of the subscription record associated with the UE (104) to the first network function (204), wherein the deletion indicates unsubscribing the UE (104) from network services; and upon receiving the response from the second network function (202), deleting, by the first network function (204), the subscription record associated with the UE (104) from the database (214).

6. The method (400) as claimed in claim 1, wherein the at least one parameter comprises a subscription Identifier (ID) associated with the UE (104).

7. The method (400) as claimed in claim 1, wherein the first network function (204) is a Policy Control Function (PCF) and the second network function (202) is an Access and Mobility Management Function (AMF).

8. The method (400) as claimed in claim 1, wherein the flag status can either be enabled or disabled, and the method (400) further comprises determining an action based on the flag status.

9. The method (400) as claimed in claim 2, wherein the flag is dynamically configured at the first network function (204) based on predefined network conditions, the network conditions comprising at least one of: network congestion thresholds, UE load levels, or policy -based rules.

10. A system (108) for managing message subscriptions in a communication network (106), the system (108) comprising: a receiving unit (216) configured to:receive, by a first network function (204), a request corresponding to a User Equipment (UE) (104) from a second network function (202); an identifying unit (218) configured to: identify, by the first network function (204), at least one parameter from the request; a determining unit (220) configured to: determine, by the first network function (204), a flag status associated with the first network function (204) corresponding to the UE (104) based on the at least one parameter; and upon determining the flag status to be a disabled flag status, delete, by the first network function (204), a subscription record associated with the UE (104) from a database (214) based on the at least one parameter.

11. The system (108) as claimed in claim 10, wherein the flag is configured at the first network function (204), and the flag status indicates whether a network-initiated unsubscribe procedure is enabled or disabled for the UE (104) based on predefined network conditions.

12. The system (108) as claimed in claim 10, wherein the first network function (204) is further configured to: generate an unsubscribe request corresponding to the request associated with the UE (104) upon determining the flag status to be an enabled flag status; and send the unsubscribe request to the second network function (202).

13. The system (108) as claimed in claim 12, wherein the second network function (202) is configured to:delete the subscription record associated with the UE (104) from the database, in response to receiving the unsubscribe request from the first network function (204).

14. The system (108) as claimed in claim 13, wherein: send, by the second network function (202), a response depicting a successful deletion of the subscription record associated with the UE (104) to the first network function (204), wherein the deletion indicates unsubscribing the UE (104) from network services; and delete, by the first network function (204), the subscription record associated with the UE (104) from the database (214) upon receiving the response from the second network function (202).

15. The system (108) as claimed in claim 10, wherein the at least one parameter comprises a subscription Identifier (ID) associated with the UE (104).

16. The system (108) as claimed in claim 10, wherein the first network function (204) is a Policy Control Function (PCF) and the second network function (202) is an Access and Mobility Management Function (AMF).

17. The system (108) as claimed in claim 10, wherein the flag status can either be enabled or disabled, and the system (108) determines an action based on the flag status.

18. The system (108) as claimed in claim 11, wherein the flag is dynamically configured at the first network function (204) based on predefined network conditions, the network conditions comprising at least one of: network congestion thresholds, UE load levels, or policy -based rules.

19. A User Equipment (UE) (104) communicatively coupled with a communication network (106), the coupling comprises steps of:receiving, by the communication network (106), a connection request from the UE (104); sending, by the communication network (106), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein based on the plurality of signals, message subscriptions in the communication network (106) is managed by a method (400) as claimed in claim 1.

20. 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: receive, by a first network function (204), a request corresponding to a User Equipment (UE) (104) from a second network function (202); identify, by the first network function (204), at least one parameter from the request; determine, by the first network function (204), a flag status associated with the first network function corresponding to the UE (104) based on the at least one parameter; and upon determining the flag status to be a disabled flag status, delete, by the first network function (204), a subscription record associated with the UE (104) from a database based on the at least one parameter.

Images