Search

EP-4740093-A1 - METHOD AND SYSTEM FOR IMPLEMENTING A SHUTDOWN PROCESS OF A NODE IN A NETWORK

EP4740093A1EP 4740093 A1EP4740093 A1EP 4740093A1EP-4740093-A1

Abstract

The present disclosure relates to a method and a system for implementing a shutdown process of a node in a network. The method includes receiving, by a processing unit [302], request for execution of shutdown process for the node, from UI [602] of the node. The shutdown process comprises one or more phases. The method includes transmitting, by the processing unit [302], a data collection request to a shutdown module [304]. The method further includes receiving, by the processing unit [302], estimated time of completion for each phase of the shutdown process. Further the method includes computing, by the processing unit [302], an estimated time of completion for the shutdown process based on the estimated time for each phase. The method further includes implementing, by the processing unit [302], the phases of the shutdown process, based on a sequence associated with each phase of the one or more phases.

Inventors

  • BISHT, BIRENDRA
  • BHATNAGAR, AAYUSH
  • Singh, Harbinder Pal
  • LUTHRA, GAURAV
  • SINGH, SUMIT
  • JAISWAL, Rakesh Kumar
  • JAT, Saniya
  • KUMAR, RAHUL
  • GUPTA, ANSHUL

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240701

Claims (20)

  1. 1. A method for implementing a shutdown process of a node in a network, comprising: receiving, by a processing unit [302], a request for execution of the shutdown process for the node in the network, from a user interface (UI) [602] of the node, wherein the shutdown process comprises one or more phases; transmitting, by the processing unit [302], a data collection request to a shutdown module [304] at the node; receiving, by the processing unit [302], in response to the data collection request, an estimated time of completion for each phase of the one or more phases of the shutdown process, from the shutdown module [304]; computing, by the processing unit [302], an estimated time of completion for the shutdown process based at least on the estimated time for each phase of the one or more phases; and implementing, by the processing unit [302], the one or more phases of the shutdown process, based on a sequence associated with each phase of the one or more phases.
  2. 2. The method as claimed in claim 1, further comprising: initiating, by the processing unit [302], via the shutdown module [304], an expiry timer before each phase of the one or more phases is implemented; implementing, by the processing unit [302], one or more operations associated with each phase of the one or more phases; receiving, by the processing unit [302], a frame response from the node depicting status of each phase of the one or more phases; and updating, by the processing unit [302], the estimated time of completion for each phase of the one or more phases based at least on the frame response.
  3. 3. The method as claimed in claim 2, further comprising: receiving, by the processing unit [302], via the shutdown module [304], a status update request; and upon receiving the status update request, displaying, by the processing unit [302], at least one of the estimated time of completion of each phase of the one or more phases or the estimated time of completion for execution of the shutdown process, on a display unit [306],
  4. 4. The method as claimed in claim 2, wherein the frame response comprises at least one of an initial frame status and an end frame status.
  5. 5. The method as claimed in claim 1, wherein the one or more phases comprises a first phase, wherein, the first phase terminates registration of new user equipment (UE) with the node.
  6. 6. The method as claimed in claim 1, wherein, the one or more phases comprises a second phase, wherein, the second phase enables de-registration of already connected UE from the node.
  7. 7. The method as claimed in claim 1, wherein, the one or more phases comprises a third phase, wherein, the third phase enables de-registration of the node from the network.
  8. 8. The method as claimed in claim 1, wherein, the one or more phases comprises a fourth phase, wherein, the fourth phase facilitates cleanup of a set of data associated with UE earlier connected with the node, wherein the set of data is stored in a database [308],
  9. 9. The method as claimed in claim 1, further comprising: initiating, by the processing unit [302], from the shutdown module [304], a periodic trigger to the node; checking, by the processing unit [302], via the shutdown module [304], after time-out of the periodic trigger, a state associated with the node, wherein the state denotes one of a presence or an absence of a progress of at least one phase from the one or more phases of the shutdown process; transmitting, by the processing unit [302], via the shutdown module [304], a message about the shutdown process to a standby process at the node, in an event of the absence of the progress of at least one phase from the one or more phases of the shutdown process; and activating, by the processing unit [302], the standby process at the node, based on the transmitted message.
  10. 10. The method as claimed in claim 9, wherein the periodic trigger is triggered to the node until the one or more phases of the shutdown process are implemented.
  11. 11. A system for implementing a shutdown process of a node in a network, comprising: a processing unit [302], configured to: receive a request for execution of the shutdown process for the node in the network, from a user interface (UI) [602] of the node, wherein the shutdown process comprises one or more phases; transmit a data collection request to a shutdown module [304] at the node; receive, an estimated time of completion for each phase of the one or more phases of the shutdown process, from the shutdown module [304]; compute, an estimated time of completion for the shutdown process based at least on the estimated time of completion for each phase of the one or more phases; and implement the one or more phases of the shutdown process, based on a sequence associated with each phase of the one or more phases.
  12. 12. The system as claimed in claim 11, wherein the processing unit [302] is further configured to: Initiate an expiry timer via the shutdown module [304], before each phase of the one or more phases is implemented; Implement one or more operations associated with each phase of the one or more phases; receive a frame response, from the node, depicting status of each phase of the one or more phases; and update the estimated time of completion for each phase of the one or more phases based at least on the frame response.
  13. 13. The system as claimed in claim 12, wherein the processing unit [302] is further configured to: receive a status update request via the shutdown module [304]; and upon receipt of the status update request, display at least one of the estimated time of completion of each phase of the one or more phases or the estimated time of completion for execution of the shutdown process, on a display unit [306],
  14. 14. The system as claimed in claim 12, wherein the frame response comprises at least one of an initial frame status and an end frame status.
  15. 15. The system as claimed in claim 11, wherein the one or more phases comprises a first phase, wherein, the first phase terminates registration of new user equipment (UE) with the node.
  16. 16. The system as claimed in claim 11, wherein, the one or more phases comprises a second phase, wherein, the second phase enables de-registration of already connected UE from the node.
  17. 17. The system as claimed in claim 11, wherein, the one or more phases comprises a third phase, wherein, the third phase enables de-registration of the node from the network.
  18. 18. The system as claimed in claim 11, wherein, the one or more phases comprises a fourth phase, wherein, the fourth phase facilitates cleanup of a set of data associated with UE earlier connected with the node, wherein the set of data is stored in a database [308],
  19. 19. The system as claimed in claim 11, wherein the processing unit [302] is further configured to: initiate, from the shutdown module [304], a periodic trigger to the node; checking, via the shutdown module [304], after time-out of the periodic trigger, a state associated with the node, wherein the state denotes one of a presence or an absence of a progress of at least one phase from the one or more phases of the shutdown process; transmit, via the shutdown module [304], a message about the shutdown process to a standby process at the node, in an event of the absence of the progress of at least one phase from the one or more phases of the shutdown process; and activate, the standby process at the node, based on the transmitted message.
  20. 20. The system as claimed in claim 19, wherein, the periodic trigger is triggered to the node until the one or more phases of the shutdown process are implemented.

Description

METHOD AND SYSTEM FOR IMPLEMENTING A SHUTDOWN PROCESS OF A NODE IN A NETWORK TECHNICAL FIELD [0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to implementing a shutdown process of a node in a network. BACKGROUND [0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art. [0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users. [0004] Moreover, the 5G core networks are based on service-based architecture (SBA) that is centered around network function (NF) services. Each NF can register itself and its supported services to a Network Repository Function (NRF), which is used by other NFs for the discovery of NF instances and their services. The NRF refers to a central repository in the 5th generation network that may provide a unified view of the network resources that may provide ease of communication and coordination between the network elements. The NRF therefore supports functions related to 1) maintaining the profiles of the available network function (NF) instances and their supported services in the 5G core network, 2) allowing NF instances to discover other NF instances in the 5G core network, and 3) allowing the NF instances to track the status of other NF instances. Also, certain NF related details are captured at the NRF whenever an NF comes up with a planned event or first-time commissioning. [0005] Therefore, there are multiple nodes working or providing their functionality services in 5G/4G network. However, due to many reasons like functionality release upgrade, maintenance purposes, troubleshooting etc., the node server needs to be put down from its services for a particular interval of time. For example- due to some maintenance activity it may be required to remove one AMF’s network node from network, this requires shutdown of this AMF node in a holistic manner. [0006] As this node was live before, a certain number of consumers/UEs must be served by this node and sudden shutdown of node may put the consumers/UEs in bad state or chances are there that the consumers/UEs may get stuck in network as this node is providing services to millions of users. Taking an example of AMF node, suppose, N2 Handover procedure, as per 3 GPP standard (TS 23.502) is in progress. The N2 handover procedure refers to transfer of an active session from one gNodeB to another gNodeB. When Handover Required message is received at AMF, AMF sends Updatesmcontext Request towards SMF and after getting Updatesmcontext Response, the AMF sends Handover Request towards T-NGRAN. The Updatesmcontext request is sent during the N2 handover to update a mobility management context of a UE. The T-NGRAN refers to a Radio Access network that may support 5th Generation new radio. At this very point, resources for handover are allocated at above mentioned nodes and if now forceful shutdown of AMF has occurred, this will lead to uncertainty of states of UE in network nodes like UE, RAN, SMF and UPF. [0007] To solve such problems, there is a requirement of an improved Shutdown Framework in the network nodes. Currently known solutions failed to provide such a Shutdown Framework and therefore there is a requirement in the art to overcome the limitations of the existing solutions, which the present disclosure aims to address. SUMMARY [0008] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the clai