WO2025017719A1

WO2025017719A1 - System and method for managing stacks in a network function

Info

Publication number: WO2025017719A1
Application number: PCT/IN2024/051293
Authority: WO
Inventors: Mukta Shetty; Alok B Jha; Sanjeev Kumar; Rajesh Hansda; Chetan Patidar; Aayush Bhatnagar
Original assignee: Jio Platforms Ltd
Current assignee: Jio Platforms Ltd
Priority date: 2023-07-20
Filing date: 2024-07-18
Publication date: 2025-01-23
Anticipated expiration: 2026-01-20

Abstract

The present disclosure provides a system and a method to start and stop Diameter stacks of network nodes, thereby providing flexibility, control, and improved management of network traffic and resources in a network function application. The present disclosure may purge session data in the network nodes, when the session data in the local cache becomes outdated or inconsistent due to updates or changes in a network environment. Thereby, ensuring that only the most current and accurate session data is stored, maintaining data integrity and avoiding issues caused by using stale information.

Description

SYSTEM AND METHOD FOR MANAGING STACKS IN A NETWORK FUNCTION

RESERVATION OF RIGHTS

[001] 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 (herein after 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

[002] The present disclosure relates to a Policy Control Function (PCF) in a wireless network, and specifically to a system and a method for managing Diameter stacks in a network function.

BACKGROUND

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

[004] To ensure high availability, uninterrupted services, and efficient failover mechanisms, network functions, for example, Policy Control Function/Policy and Charging Rules Function (PCF/PCRF) are deployed in a cluster of 3, each acting as an active cluster, a standby cluster, and a spare cluster. Conventionally, in case of failures or maintenance activities in the active cluster, the active cluster may be shut down and the traffic may be switched or routed to the spare clusters, which may impact the rest of applications or the traffic flow.

[005] The network functions maintain session data in local caches for efficient processing and quick access. Over time, the session data in the local cache may become outdated or inconsistent due to updates or changes in a network environment. Also, session data caches may consume a significant amount of memory resources. As the cache grows in size, it may impact the overall performance and efficiency of the network function.

[006] There is, therefore, a need in the art to improve state of starting and stopping Diameter stacks in the network function, and purging the session cache to overcoming the deficiencies of the prior arts.

SUMMARY OF THE PRESENT DISCLOSURE

[007] The present disclosure relates to a method for managing a diameter stack in a network function of a network node. The method comprises the steps of starting, by a processing engine, the diameter stack of the network node for a switchover of traffic from an active node to one of a spare node and a standby node. The steps of starting the diameter stack comprises initializing, by the processing engine, the diameter stack. Further, upon initializing the diameter stack, setting, by the processing engine, a status of the network node as active. Furthermore, upon setting the status of the network node as active, initiating, by the processing engine, stopping of the diameter stack. Further, stopping of the diameter stack comprises determining, by the processing engine, whether the network node has one of an active status and an inactive status. Further, based on the determination, setting, by the processing engine, the network node as one of the spare node and the standby node. Further, the method comprises, upon stopping the diameter stack, purging, by the processing engine, session data, associated with the network function, in a local cache of the network node. [008] In an embodiment, the network function is deployed in a cluster of three network nodes, wherein the cluster comprises the active node, the standby node, and the spare node.

[009] In an embodiment, if the network node is active, the method includes a step of determining, by the processing engine, if the network node is designated as a spare node. Further, upon determination that the network node is designated as the spare node, the method includes a step of setting, by the processing engine, the status of the network node as a spare node. Thereafter, based on the determination that the network node is not designated as the spare node or is not active, the method includes a step of setting, by the processing engine, the status of the network node as a standby node.

[0010] In an embodiment, the step of purging the session data comprises performing, by the processing engine, a selective clearing of a session cache for at least one instance of the network function.

[0011] In an embodiment, wherein the step of starting the diameter stack comprises determining, by the processing engine, whether the diameter stack initialization is enabled. Further, the method includes a step of determining, by the processing engine, whether the diameter stack is initialized. Moreover, based on the determination that the diameter stack is not initialized, the method includes a step of initializing, by the processing engine, the diameter stack.

[0012] In an embodiment, the network function comprises one of a Policy Control Function (PCF) and a Policy and Charging Rules Function (PCRF) in a wireless network.

[0013] In an embodiment, the method includes the step of logging an error message based on the determination that the diameter stack is already initialized, or the stack initialization is not enabled. [0014] In an embodiment, upon setting the network node’s status as active, the method further comprises the step of raising, by the processing engine, an alarm to indicate that the network node has an active status, wherein the alarm may be used for monitoring and management purposes.

[0015] The present disclosure relates to a system for managing a diameter stack in a network function of a network node. The system comprises a processing engine, and a memory coupled to the processing engine. The memory includes computer implemented instructions to configure the processing engine to start the diameter stack of the network node for a switchover of traffic from an active node to one of a spare node and a standby node Further, to start of the diameter stack, the processing engine is configured to initialize the diameter stack; and upon initializing the diameter stacks, set a status of the network node as active. Furthermore, upon setting the status of the network node as active, the processing engine is configured to initiate stopping of the diameter stack. Further, to stop of the diameter stack, the processing engine is configured to determine whether the network node has one of an active status and an inactive status; and based on the determination, set the network node as one of the spare node and the standby node. Further, the processing engine is configured to upon stopping the diameter stacks, purge session data, associated with the network function, in a local cache of the network node.

[0016] In an embodiment, the network function is deployed in a cluster of three network nodes, wherein the cluster comprises the active node, the standby node, and the spare node.

[0017] In an embodiment, the system is configured to if the network node is active, determine if the network node is designated as a spare node; upon determination that the network node is designated as the spare node, set the status of the network node as a spare node; and based on the determination that the network node is not designated as the spare node or is not active, set the status of the network node as a standby node.

[0018] In an embodiment, the system, to purge the session data, the processing engine is further configured to perform a selective clearing of a session cache for at least one instance of the network function.

[0019] In an embodiment, to start the diameter stack, the processing engine is configured to: determine whether the diameter stack initialization is enabled; determine whether the diameter stack is initialized; and based on the determination that the diameter stack is not initialized, initialize the diameter stack.

[0020] In an embodiment, the network function comprises one of a Policy Control Function (PCF) and a Policy and Charging Rules Function (PCRF) in a wireless network.

[0021] In an embodiment, the system is configured to log an error message based on the determination that the diameter stack is already initialized, or the stack initialization is not enabled.

[0022] In an embodiment, upon setting the network node’s status as active, the processing engine is further configured to raise an alarm to indicate that the network node has an active status, wherein the alarm may be used for monitoring and management purposes.

[0023] In an embodiment, there is a non-transitory computer readable medium including program instructions stored thereon, executed by a system for managing a diameter stack in a network function of a network node. The program instructions comprise starting the diameter stack of the network node for a switchover of traffic from an active node to one of a spare node and a standby node, wherein the starting of the diameter stack comprises initializing the diameter stack; and upon initializing the diameter stacks, setting a status of the network node as active. Further, upon setting the status of the network node as active, the program instructions comprise initiating stopping of the diameter stack, wherein the stopping of the diameter stack comprises: determining whether the network node has one of an active status and an inactive status; and based on the determination, setting the network node as one of the spare node and the standby node. Furthermore, the program instructions comprise upon stopping the diameter stacks, purging session data, associated with the network function, in a local cache of the network node.

[0024] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.

OBJECTS OF THE PRESENT DISCLOSURE

[0025] It is an object of the present disclosure to provide a system and a method to start and stop all Diameter stacks for a manual switchover of traffic from an active node to a spare node without shutting down a local site’s application.

[0026] It is an object of the present disclosure to control the flow of traffic within a network function by starting and stopping the Diameter stacks, thereby allowing to manage and direct traffic to any instance of the network function deployed according to the specific requirements and operational needs of network functions.

[0027] It is an object of the present disclosure to ensure uninterrupted service by switching traffic to backup or spare instance, in case of failures or maintenance activities at the active node. [0028] It is an object of the present disclosure to investigate specific stack- related problems without impacting the rest of the application or the traffic flow.

[0029] It is an object of the present disclosure to purge session cache, thereby ensuring that only most current and accurate session data is stored, maintaining data integrity, and avoiding issues caused by using stale information.

[0030] It is an object of the present disclosure to optimize resource usage, and streamline troubleshooting processes, contributing to smooth operation of the application.

BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In the figures, similar components and/or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label with a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

[0032] The diagrams are for illustration only, which thus is not a limitation of the present disclosure, and wherein:

[0033] FIG. 1 illustrates an exemplary network architecture (100) in which or with which embodiments of the present disclosure may be implemented.

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

[0035] FIG. 3 illustrates an exemplary flow chart (300) implementing a Diameter stack starting method, in accordance with an embodiment of the present disclosure. [0036] FIG. 4 illustrates an exemplary flow chart (400) implementing a Diameter stack stopping method, in accordance with an embodiment of the present disclosure.

[0037] FIG. 5 illustrates an exemplary flow chart (500) implementing a session cache purging method, in accordance with an embodiment of the present disclosure.

[0038] FIG. 6 illustrates an exemplary architecture (600) of the Diameter stacks starting and stopping system (108), in accordance with an embodiment of the present disclosure.

[0039] FIG. 7 illustrates an exemplary computer system (700) in which or with which embodiments of the present disclosure may be implemented.

[0040] FIG. 8 illustrates an exemplary flow diagram (800) of a method for managing a diameter stack in a network function of a network node, in accordance with an embodiment of the present disclosure.

LIST OF REFERENCE NUMERALS

100 - Network architecture

102-1, 102-2... 102-N - Users

104-1, 104-2... 104-N - User Equipments

106 - Network

108- System

200- Block diagram

202 - One or more processor(s)

204 - Memory

206 - Interface(s)

208 - Processing unit/ engine (s)

210 - Database 212 - Start/stop engine

214 - Cache purge engine(s)

216 - Other engine(s)

300- Flow chart

400- Flow chart

500- Flow chart

600- Architecture

700- Computer system

710 - External Storage Device

720 - Bus

730 - Main Memory

740 - Read Only Memory

750 - Mass Storage Device

760 - Communication Port

770 - Processor

800 - Flow Diagram (with steps)

DETAILED DESCRIPTION

[0041] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.

[0042] The present disclosure starts/stops all Diameter stacks of an active network node for a manual switch over of traffic to a spare node without shutting down a local site’s application. The present disclosure may purge session data in a local cache of network functions, thereby ensuring that only the most current and accurate session data is stored, maintaining data integrity and avoiding issues caused by using stale information. Purging the session cache may free up memory resources, optimize resource utilization, and prevent memory-related issues.

[0043] The various embodiments of the present disclosure will be explained in detail with reference to FIGs. 1 to 8.

[0044] FIG. 1 illustrates an exemplary network architecture (100) in which or with which embodiments of the present disclosure may be implemented.

[0045] Referring to FIG. 1, the network architecture (100) may include one or more computing devices or user equipments (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 one or more user equipments (104-1, 104-2... 104-N) may be individually referred to as the user equipment (104) and collectively referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three user equipments (104) are depicted in FIG. 1, however any number of the user equipments (104) may be included without departing from the scope of the ongoing description.

[0046] In an embodiment, the user equipment (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the user equipment (104) may include, but is not limited to, smart phones, 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.

[0047] In an embodiment, the user equipment (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device(e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a 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 user equipment (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, wherein the user equipment ( 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 touch pad, touch enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (104) may not be restricted to the mentioned devices and various other devices may be used.

[0048] Referring to FIG. 1, the user equipment (104) may communicate with a system (108), for example, a Diameter stack managing system, through a network (106). The Diameter stack managing system (108) may start and stop Diameter stacks of the network nodes, thereby providing flexibility, control, and improved management of network traffic and resources in a network function application. The Diameter stack managing system (108) may purge session data in the network nodes, when the session data in the local cache becomes outdated or inconsistent due to updates or changes in a network environment, thereby, ensuring that only the most current and accurate session data is stored, maintaining data integrity and avoiding issues caused by using stale information. Also, a significant amount of memory resources may be freed up, resource utilization may be optimized, and memory-related issues may be prevented. Thus, the network function may operate efficiently, deliver reliable services, and adhere to regulatory requirements.

[0049] In an embodiment, the network (106) may include at least one of a Fifth Generation (5G) network, 6G network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the network architecture (100) and/or with the diameter stack managing 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.

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

[0051] FIG. 2 illustrates an exemplary block diagram (200) of the Diameter stack managing system (108), in accordance with an embodiment of the present disclosure. [0052] In an aspect, the Diameter stack managing 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, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the Diameter stack managing 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 comprise 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.

[0053] In an embodiment, the Diameter stack managing 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, referred to as I/O devices, storage devices, and the like. The interface(s) (206) may facilitate communication of the Diameter stack managing system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the Diameter stack managing system (108). Examples of such components include, but are not limited to, processing unit/engine(s) (208) and a database (210).

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

[0055] The processing engine (208) may include one or more engines selected from any of a start/stop engine (212), a cache purge engine (214), and other engine(s) (216). For example, the other engine(s) (216) may include an alarm engine and a log engine.

[0056] The start/stop engine (212) may start and stop Diameter stacks of the network nodes, thereby providing flexibility, control, and improved management of network traffic and resources in a network function application.

[0057] The cache purge engine (214) may purge session data in the network nodes, when the session data in the local cache becomes outdated or inconsistent due to updates or changes in a network environment, thereby ensuring that only the most current and accurate session data is stored, maintaining data integrity and avoiding issues caused by using stale information.

[0058] In an embodiment, upon setting the network node’s status as active, the alarm engine may raise an alarm to indicate that the network node has an active status. The alarm engine may be used for monitoring and management purposes. Further, a message may be sent to an Element Management System (EMS) to indicate the update of the node as an active node. [0059] The log engine may log an error message if the required Diameter stack is already initialized, or if the stack initialization is not enabled.

[0060] In an embodiment, the database (210) may comprise data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor(s) (202) or the processing engine(s) (208) or the Diameter stack managing system (108).

[0061] Although FIG. 2 shows an exemplary block diagram (200) of the Diameter stack managing system (108), in other embodiments, the Diameter stack managing 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 Diameter stack managing system (108) may perform one or more functions described as being performed by one or more other components of the Diameter stack managing system (108). For example, the system (108) may perform functions as described in detail in FIG. 8.

[0062] FIG. 3 illustrates an exemplary flow chart (300) implementing a Diameter stack starting method, in accordance with an embodiment of the present disclosure.

[0063] Referring to FIG. 3, the Diameter stack starting method may include receiving a request including startAHStacks command at step 302 for starting and initializing the Diameter stacks and interfaces of network functions. In another embodiment, a command line interface (CLI) Command startAll Stacks is executed at step 302 and the Request is sent to at network function (NF) End (PCRF / PCF) at step 304. startAHStacks command is specifically related to starting and initializing the diameter stacks and interfaces for Network Functions (PCF/PCRF) in the system. [0064] The method may include determining if the Diameter stack initialization is enabled or not. In other words, the method may include determining fs stack already initialized at step 306. If a required Diameter stack is not already started, the required Diameter stack may be initialized using a Diameter stack manager at step 310. If the required Diameter stack is already initialized, an error message may be logged at step 308, or if the stack initialization is not enabled, the error message may be logged.

[0065] After initializing the required Diameter stack, the Diameter stack manager may be used to start all the Diameter stacks at step 312, thereby ensuring that all the components of the network functions related to the required Diameter stack are operational. If the stack is not started successfully, an error message is logged.

[0066] Once the Diameter stacks are started, the network node’s status may be set to Active at step 314, and an alarm may be raised to indicate that the network node (PCRF instance) is active at step 316. This alarm may be used for monitoring and management purposes. Further, a message may be sent to an Element Management System (EMS) to indicate the update of the node as an active node.

[0067] FIG. 4 illustrates an exemplary flow chart (400) implementing a Diameter stack stopping method, in accordance with an embodiment of the present disclosure.

[0068] Referring to FIG. 4, the Diameter stack stopping method may include calling up the Diameter stack manager of respective interface(s) to stop all the Diameter stacks associated with the interfaces involved, thereby ensuring that the Diameter stacks are properly terminated, and any ongoing communication is halted. For example, when the diameter stacks are properly terminated, then communication can be restarted only based on a request whereas when the diameter stacks are not properly terminated, then the communication can automatically start after a predetermined period. [0069] The Diameter stack stopping method may include receiving a request including stopAHStacks command at step 402 for stopping the Diameter stacks and interfaces of network functions. In another embodiment, a command line interface (CLI) Command stopAHStacks is executed at step 402 and the Request is sent to at NF End (PCRF / PCF) at step 404. Further, the method may include calling a setActive(false) method to indicate that the node is not active. If the node is designated as a spare node at step 406 (as indicated by isSpare flag) and its current state is Active, the node state may be set to Spare at step 410. Otherwise, if the node is not the spare node or its current state is not Active, the node state may be set to Standby at step 408. The method may include updating the node status in EMS by sending a message on the node’s status to the EMS. The message includes node state information as whether the node is standby or spare. For example, the message may include a flag which may be set to 0 to indicate that the node state as spare and it may be set to 1 to indicate that the node state is standby.

[0070] FIG. 5 illustrates an exemplary flow chart (500) implementing a session cache purging method, in accordance with an embodiment of the present disclosure.

[0071] Referring to FIG. 5, the network functions may maintain session data in local caches for efficient processing and quick access. These session data caches may be purged based on various criteria or triggers to ensure the cache remains up- to-date and accurate. Purging the cache may help in freeing up memory and maintaining the integrity of the data. The session cache may be purged for a particular interface or for all interfaces, depending on the requirement. Thereby, allowing for selective cache clearing based on specific interfaces or a comprehensive clearing of all interfaces. For example, if an interface for Network Function such as PCF/PCRF has occupied a large portion of the cache has not been used since a long time period, then the session cache may be purged for only interface for Network Function PCF/PCRF. However, if a plurality of interfaces are involved in a communication, and that communication has been halted due to termination of the stacks, then the session cache may be purged for all interfaces involved in that communication.

[0072] The session cache purging method may include receiving a cache clearing request at NF based on execution of a CLI command purge SessionCache at step 502. Based on the execution of the command, a request is received at NF request handler at step 504. At step 506, it determined if purge request is for all the interfaces or a specific interface. The local cache associated with a specific interface is cleared based on the request i.e. specific session map associated with the specific interface is cleared at step 508. If the request is to clear all interfaces, the method may execute operations to clear the local caches for all interfaces at step 510.

[0073] FIG. 6 illustrates an exemplary architecture (600) of the Diameter stacks starting and stopping system (108), in accordance with an embodiment of the present disclosure.

[0074] Referring to FIG. 6, the active node may receive traffic at step 604 from various sources, for example, a Packet Network Data Gateway (PGW), Online Charging System (OCS), Proxy-Call Session Control Function (P-CSCF) node, and Traffic Detection Function (TDF) node 602. The active node may receive a StopAllInterface command from the system (108) at step 608, in case of failure of the active node. Upon receiving the StopAllInterface command, the active node (606) may establish a connection with the spare node at step 614, and may switch over the traffic received by the active node to the spare node. Further, the spare node may replicate the active node at step 616. The spare node may then receive traffic from the sources PGW, OCS, P-CSCF, TDF. At step 610, traffic is switched over to spare node after StopAllInterface on active NF.

[0075] A user equipment is communicatively coupled to a system through a network for managing a diameter stack in a network function of a network node. The user equipment is configured to send a command and receive a status of the network node according to steps of the method in the FIG. 3. [0076] FIG. 7 illustrates an exemplary computer system (700) in which or with which embodiments of the present disclosure may be implemented.

[0077] As shown in FIG. 7, the computer system (700) may include an external storage device (710), a bus (720), a main memory (730), a read only memory (740), a mass storage device (750), a communication port (760), and a processor (770). A person skilled in the art will appreciate that the computer system (700) may include more than one processor (770) and communication ports (760). Processor (770) may include various modules associated with embodiments of the present disclosure.

[0078] In an embodiment, the communication port (760) 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 (760) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (700) connects.

[0079] In an embodiment, the memory (730) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (740) 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 (770).

[0080] In an embodiment, the mass storage (750) 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).

[0081] In an embodiment, the bus (720) communicatively couples the processor(s) (770) with the other memory, storage and communication blocks. The bus (720) 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 (770) to the computer system (700).

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

[0083] FIG. 8 illustrates an exemplary flow diagram (800) of a method for managing a diameter stack in a network function of a network node, in accordance with an embodiment of the present disclosure. The flow diagram (800) includes steps 802-818.

[0084] At step 802, the diameter stack of the network node is started, by a processing engine (208), for a switchover of traffic from an active node to one of a spare node and a standby node.

[0085] At step 804, for the starting of the diameter stack, the diameter stack is initialized by the processing engine (208). [0086] At step 806, upon initializing the diameter stack, a status of the network node is set as active by the processing engine (208).

[0087] At step 808, upon setting the status of the network node as active, stopping of the diameter stack is initiated by the processing engine (208).

[0088] At step 810, it is determined, by the processing engine (208), whether the network node has one of an active status and an inactive status.

[0089] At step 812, based on the determination, the network node is set as one of the spare node and the standby node by the processing engine (208).

[0090] At step 814, upon stopping the diameter stack, session data, associated with the network function, is purged in a local cache of the network node by the processing engine (208).

[0091] In an embodiment, the network function is deployed in a cluster of three network nodes, wherein the cluster comprises the active node, the standby node, and the spare node.

[0092] In an embodiment, if the network node is active, the method includes a step of determining, by the processing engine, if the network node is designated as a spare node. Further, upon determination that the network node is designated as the spare node, the method includes a step of setting, by the processing engine, the status of the network node as a spare node. Thereafter, based on the determination that the network node is not designated as the spare node or is not active, the method includes a step of setting, by the processing engine, the status of the network node as a standby node.

[0093] In an embodiment, the step of purging the session data comprises performing, by the processing engine, a selective clearing of a session cache for at least one instance of the network function. [0094] In an embodiment, wherein the step of starting the diameter stack comprises determining, by the processing engine, whether the diameter stack initialization is enabled. Further, the method includes a step of determining, by the processing engine, whether the diameter stack is initialized. Moreover, based on the determination that the diameter stack is not initialized, the method includes a step of initializing, by the processing engine, the diameter stack.

[0095] In an embodiment, the network function comprises one of a Policy Control Function (PCF) and a Policy and Charging Rules Function (PCRF) in a wireless network.

[0096] In an embodiment, the method includes the step of logging an error message based on the determination that the diameter stack is already initialized, or the stack initialization is not enabled.

[0097] In an embodiment, upon setting the network node’s status as active, the method further comprises the step of raising, by the processing engine, an alarm to indicate that the network node has an active status, wherein the alarm may be used for monitoring and management purposes.

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

[0099] The present disclosure provides technical advancement related to gaining control over the flow of traffic within the network function. It allows to manage and direct traffic to any instance of NF deployed according to the specific requirements and operational needs of NFs. Further, starting and stopping diameter stacks facilitate in switching traffic to backup or spare instance, ensuring uninterrupted service. The present disclosure involves stopping diameter stacks which provides an opportunity to isolate issues and perform troubleshooting or debugging tasks. It allows to investigate specific stack-related problems without impacting the rest of the application or the traffic flow. Further, a regular cache clearing helps to maintain optimal performance by preventing the accumulation of unnecessary data and reducing the overhead associated with managing large caches.

ADVANTAGES OF THE PRESENT DISCLOSURE

[00100] The present disclosure provides a system and a method to start and stop all Diameter stacks for a manual switch over of traffic from an active node to a spare node without shutting down a local site’s application.

[00101] The present disclosure controls the flow of traffic within a network function by starting and stopping the Diameter stacks, thereby allowing to manage and direct traffic to any instance of the network function deployed according to the specific requirements and operational needs of network functions.

[00102] The present disclosure facilitates redundancy and failover capabilities by starting and stopping the Diameter stacks.

[00103] The present disclosure ensures uninterrupted service by switching traffic to backup or spare instance, in case of failures or maintenance activities at the active node.

[00104] The present disclosure isolates issues and performs troubleshooting or debugging tasks by stopping the Diameter stacks, and investigates specific stack- related problems without impacting the rest of the application or the traffic flow. [00105] The present disclosure purges session cache, thereby ensuring that only most current and accurate session data is stored, maintaining data integrity, and avoiding issues caused by using stale information.

[00106] The present disclosure may free up memory resources by clearing session caches, thereby efficiently managing memory usage and preventing potential memory leaks or performance issues.

[00107] The present disclosure helps in troubleshooting and resolving issues related to session management by clearing the session caches, which allows for a fresh start and eliminates any potential inconsistencies or conflicts that may have arisen in the cached data.

[00108] The present disclosure helps maintain optimal performance of the network nodes by preventing the accumulation of unnecessary data and reducing the overhead associated with managing large caches.

[00109] The present disclosure optimizes resource usage, and streamline troubleshooting processes, contributing to smooth operation of the application.

Claims

CLAIMS We Claim:

1. A method (800) for managing a diameter stack in a network function of a network node, the method comprising: starting, by a processing engine (208), the diameter stack of the network node for a switchover of traffic from an active node to one of a spare node and a standby node, wherein the starting of the diameter stack comprises: initializing, by the processing engine (208), the diameter stack; and upon initializing the diameter stack, setting, by the processing engine (208), a status of the network node as active; upon setting the status of the network node as active, initiating, by the processing engine (208), stopping of the diameter stack, wherein the stopping of the diameter stack comprises: determining, by the processing engine (208), whether the network node has one of an active status and an inactive status; and based on the determination that the network node has the active status, setting, by the processing engine (208), the network node as a spare node, whereas based on the determination that the network node has the inactive status, setting by the processing engine (208), the network node as a standby node; and upon stopping the diameter stack, purging, by the processing engine (208), session data, associated with the network function, in a local cache of the network node.

2. The method (800) as claimed in claim 1, wherein the network function is deployed in a cluster of three network nodes, wherein the cluster comprises the active node, the standby node, and the spare node.

3. The method (800) as claimed in claim 1, wherein the method comprises: if the network node is active, determining, by the processing engine (208), if the network node is designated as the spare node; upon determination that the network node is designated as the spare node, setting, by the processing engine (208), the status of the network node as the spare node; and based on the determination that the network node is not designated as the spare node or is not active, setting, by the processing engine (208), the status of the network node as the standby node.

4. The method (800) as claimed in claim 1, wherein purging the session data comprises: performing, by the processing engine (208), a selective clearing of a session cache for at least one interface of the network function.

5. The method (800) as claimed in claim 1, wherein starting the diameter stack comprises: determining, by the processing engine (208), whether initialization of the diameter stack is enabled; determining, by the processing engine (208), whether the diameter stack is initialized; and based on the determination that the diameter stack is not initialized, initializing, by the processing engine (208), the diameter stack.

6. The method (800) as claimed in claim 1, wherein the network function comprises one of a Policy Control Function (PCF) and a Policy and Charging Rules Function (PCRF) in a network (106).

7. The method (800) as claimed in claim 1, wherein the method further comprises: logging, by the processing engine (208), an error message based on identifying that: the diameter stack is already initialized, or initialization of the diameter stack is not enabled.

8. The method (800) as claimed in claim 1, wherein, upon setting the network node’s status as active, the method further comprises: raising, by the processing engine (208), an alarm to indicate that the network node has the active status, wherein the alarm may be used for monitoring and management purposes.

9. A system (108) for managing a diameter stack in a network function of a network node, the system (108) comprising: a processing engine (208); and a memory (204) coupled to the processing engine (208), wherein the memory (204) includes computer implemented instructions to configure the processing engine (208) to: start the diameter stack of the network node for a switchover of traffic from an active node to one of a spare node and a standby node, wherein, to start of the diameter stack, the processing engine (208) is configured to: initialize the diameter stack; and upon initializing the diameter stacks, set a status of the network node as active; upon setting the status of the network node as active, initiate stopping of the diameter stack, wherein, to stop of the diameter stack, the processing engine (208) is configured to: determine whether the network node has one of an active status and an inactive status; and based on the determination that the network node has the active status, setting, by the processing engine (208), the network node as a spare node, whereas based on the determination that the network node has the inactive status, setting by the processing engine (208), the network node as a standby node; and upon stopping the diameter stacks, purge session data, associated with the network function, in a local cache of the network node.

10. The system (108) as claimed in claim 9, the network function is deployed in a cluster of three network nodes, wherein the cluster comprises the active node, the standby node, and the spare node.

11. The system (108) as claimed in claim 9, wherein the processing engine (208) is further configured to: if the network node is active, determine if the network node is designated as the spare node; upon determination that the network node is designated as the spare node, set the status of the network node as the spare node; and based on the determination that the network node is not designated as the spare node or is not active, set the status of the network node as the standby node.

12. The system (108) as claimed in claim 9, wherein, to purge the session data, the processing engine (208) is further configured to: perform a selective clearing of a session cache for at least one interface of the network function.

13. The system (108) as claimed in claim 9, wherein to start the diameter stack, the processing engine (208) is configured to: determine whether initialization of the diameter stack is enabled; determine whether the diameter stack is initialized; and based on the determination that the diameter stack is not initialized, initialize the diameter stack.

14. The system (108) as claimed in claim 9, wherein the network function comprises one of a Policy Control Function (PCF) and a Policy and Charging Rules Function (PCRF) in a network (106).

15. The system (108) as claimed in claim 9, wherein the processing engine (208) is further configured to: log an error message based on identifying that: the diameter stack is already initialized, or initialization of the diameter stack is not enabled.

16. The system (108) as claimed in claim 9, wherein, upon setting the network node’s status as active, the processing engine (208) is further configured to: raise an alarm to indicate that the network node has the active status, wherein the alarm may be used for monitoring and management purposes.

17. A non-transitory computer-readable medium having program instructions stored thereon, executed by a system (108) for managing a diameter stack in a network function of a network node, wherein the program instructions comprise: starting the diameter stack of the network node for a switchover of traffic from an active node to one of a spare node and a standby node, wherein the starting of the diameter stack comprises: initializing the diameter stack; and upon initializing the diameter stacks, setting a status of the network node as active; upon setting the status of the network node as active, initiating stopping of the diameter stack, wherein the stopping of the diameter stack comprises: determining whether the network node has one of an active status and an inactive status; and based on the determination that the network node has the active status, setting, by the processing engine (208), the network node as the spare node, whereas based on the determination that the network node has the inactive status, setting by the processing engine (208), the network node as the standby node; and upon stopping the diameter stacks, purging session data, associated with the network function, in a local cache of the network node.

18. A user equipment ( 104) communicatively coupled to a system (108) through a network for managing a diameter stack in a network function of a network node, the user equipment (104) is configured to send a command and receive a status of the network node according to a method as claimed in claim 1.