EP-4740494-A1 - METHOD AND SYSTEM FOR TRANSITION FROM PRIMARY SITE TO DISASTER RECOVERY SITE WITHOUT DATABASE REPLICATION

EP4740494A1EP 4740494 A1EP4740494 A1EP 4740494A1EP-4740494-A1

Abstract

The present disclosure relates to method for transition of network traffic from a primary site to a DR site without a database replication, comprising forwarding a message request to a router [306]; checking available instances associated with first SMSF modules [304a] to determine if first SMSF modules [304a] are down; in an event when each of the first SMSF modules [304a] are down, sending the message request to second SMSF module [304b]; checking the identity information associated with the received message request of first SMSF module [304a]; identifying a circle name based on the checking of the identity information of said first SMSF module [304a]; determining a UDM module [124] based on the identified circle name; receiving from the identified UDM module [124], an identity of the AMF module [106]; and forwarding the message to the AMF module [106] based on the received AMF module identity for final termination.

Inventors

SINHA, ANURAG
BHATNAGAR, AAYUSH
Hingu, Ketan
Kadam, Pradnya
Deb, Joy
SINGH, Kumar Gaurav

Assignees

Jio Platforms Limited

Dates

Publication Date: 20260513
Application Date: 20240611

Claims (1)

^ We Claim: 1. A method for transition of network traffic from a primary site to a disaster recovery (DR) ϱ^ site without a database replication, the method comprising: forwarding, by an access and mobility management function (AMF) module [106], a message request to a router [306], wherein the message request comprises an identity information associated with one or more first Short Message Service Function (SMSF) modules [304a] at the primary site; ϭϬ^ checking, by the router [306], each of a plurality of available instances associated with the one or more first SMSF modules [304a] at the primary site to determine if one or more first SMSF modules [304a] are down; in an event when each of the one or more first SMSF modules [304a] at the primary site are down, sending, by the router [306], the message request to a second SMSF module ϭϱ^ [304b] at the DR site; checking, by the second SMSF module [304b] at the DR site, the identity information, associated with the received message request, of one or more first SMSF module [304a] at the primary site; identifying, by the second SMSF module [304b] at the DR site, a circle name based ϮϬ^ on the checking of the identity information of said one or more first SMSF module [304a] of the primary site; determining, by the second SMSF module [304b] at the DR site, a unified data management (UDM) module [124] based on the identified circle name; receiving, by the second SMSF module [304b] at the DR site from the determined Ϯϱ^ UDM module [124], an identity of the AMF module [106]; and forwarding, by the second SMSF module [304b] at the DR site, the message to the AMF module [106] based on the received AMF module identity for final termination. 2. The method as claimed in claim 1, comprises sending, by the one or more first SMSF ϯϬ^ modules [304a] at the primary site, the identity information associated with the one or more first SMSF modules [304a] at the primary site to a network resource function (NRF) module [120]. Ϯ^^ ^ ^ 3. The method as claimed in claim 1, wherein the identity information associated with the one or more first SMSF modules [304a] at the primary site is sent as a JavaScript Object Notation (JSON) file format. ϱ^ 4. The method as claimed in claim 1, further comprising storing, in a storage unit [302], by the second SMSF module [304b] at the DR site, information associated with all primary sites identity map in a configuration data file. 5. The method as claimed in claim 1, wherein the router [306] is a service communication ϭϬ^ proxy (SCP) based router. 6. The method as claimed in claim 1, wherein the AMF module [106] sends the message sending request to the router over HTTP2 network communication protocol. ϭϱ^ 7. The method as claimed in claim 1, wherein further comprising identifying, by the router [306], one or more first SMSF modules [304a] at all primary sites. 8. The method as claimed in claim 1, wherein receiving, by the second SMSF module [304b] at the DR site from the identified UDM module [124], the identity of the AMF module [106] ϮϬ^ comprises: receiving, by the second SMSF module [304b] at the DR site from the identified UDM module [124], a user profile; and determining, by the second SMSF module [304b], the identity of the AMF module [106] corresponding to the received user profile. Ϯϱ^ 9. A system for transition of network traffic from a primary site to a disaster recovery (DR) site without a database replication, the system comprising: an access and mobility management function (AMF) module [106] configured to forward a message request to a router [306], wherein the message request comprises an ϯϬ^ identity information associated with one or more first SMSF modules [304a] at the primary site; the router [306] configured to: check each of a plurality of available instances associated with the one or more first SMSF modules [304a] at the primary site to determine if one or more first SMSF ϯϱ^ modules [304a] are down; Ϯ^^ ^ ^ send the message request to a second SMSF module [304b] at the DR site in an event when each of the one or more first SMSF modules [304a] at the primary site are down; the second SMSF module [304b] at the DR site further configured to: ϱ^ check, the identity information, associated with the received message request, of one or more first SMSF module [304a] at the primary site; identify a circle name based on the checking of the identity information of said one or more first SMSF module [304a] of the primary site; determine a unified data management (UDM) module [124] based on the ϭϬ^ identified circle name; receive from the determined UDM module [124], an identity of the AMF module [106]; and forward, the message to the AMF module [106] based on the received AMF module identity for final termination. ϭϱ^ 10. The system as claimed in claim 9, wherein the one or more first SMSF modules [304a] at the primary site is configured to send the identity information associated with the one or more first SMSF modules [304a] at the primary site to a network resource function (NRF) module [120]. ϮϬ^ 11. The system as claimed in claim 9, wherein the identity information associated with the one or more first SMSF modules [304a] at the primary site as a JSON file. 12. The system as claimed in claim 9, the system comprising a storage unit [302], wherein the Ϯϱ^ second SMSF module [304b] at the DR site is configured to store, in the storage unit [302], information associated with all primary sites identity map in a configuration data file. 13. The system as claimed in claim 9, wherein the router [306] is a service communication proxy (SCP) based router. ϯϬ^ 14. The system as claimed in claim 9, wherein the AMF module [106] is configured to send the message sending request to the router over HTTP2 network communication protocol. 15. The system as claimed in claim 9, wherein the router [306] is further configured to identify ϯϱ^ the one or more first SMSF modules [304a] at all primary sites. 16. The system as claimed in claim 9, wherein the second SMSF module [304b] is further configured to: ϯϬ^ ^ ^ receive, at the DR site from the identified UDM module [124], a user profile; and determine the identity of the AMF module [106] corresponding to the received user profile. ϱ^ 17. A non-transitory computer-readable storage medium storing instruction for transition of network traffic from a primary site to a disaster recovery (DR) site without a database replication, the storage medium comprising executable code which, when executed by one or more units of a system, causes: an access and mobility management function (AMF) module [106] to forward a ϭϬ^ message request to a router [306], wherein the message request comprises the identity information associated with the one or more first SMSF modules [304a] at the primary site; the router [306] to: check each of a plurality of available instances associated with the one or more first SMSF modules [304a] at the primary site to determine if one or more first SMSF ϭϱ^ modules [304a] are down; and send the message request to a SMSF module [304b] at the DR site in an event when each of the one or more first SMSF modules [304a] at the primary site are down; the second SMSF module [304b] at the DR site further to: check, the identity information, associated with the received message request, of ϮϬ^ one or more first SMSF module [304a] at the primary site; identify a circle name based on the checking of the identity information of said one or more first SMSF module [304a] of the primary site; determine a unified data management (UDM) module [124] based on the identified circle name; Ϯϱ^ receive from the identified UDM module [124], an identity of the AMF module [106]; and forward, the message to the AMF module [106] based on the received AMF module identity for final termination.^ ϯϭ^ ^

Description

^ METHOD AND SYSTEM FOR TRANSITION FROM PRIMARY SITE TO DISASTER RECOVERY SITE WITHOUT DATABASE REPLICATION FIELD OF THE DISCLOSURE ϱ^ [0001] Embodiments of the present disclosure generally relates to the field of wireless communication system. More particularly, embodiments of the present disclosure relate to methods and systems for the transition of network traffic from a primary site to a disaster recovery (DR) site without a database replication. ϭϬ^ BACKGROUND [0002] 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. [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] In traditional disaster recovery (DR) systems within telecommunications, several key problems are prevalent, largely due to the reliance on database replication between the primary and DR sites. Firstly, such replication demands high resources, both computational and in terms ϯϱ^ of storage. Each site must have the infrastructure to handle a complete set of mirrored data, which ϭ^ ^ ^ significantly drives up costs. Secondly, maintaining data synchronization across geographically diverse sites introduces complexity. Network issues like latency or packet loss can lead to data inconsistencies, which are particularly problematic during a failover scenario. Moreover, as data volumes and the number of network nodes increase, scalability becomes a challenge. The system's ϱ^ ability to efficiently manage large datasets and adapt to network changes or demands for rapid scaling can be severely tested. Additionally, the recovery time, the duration needed to switch operations from the primary to the DR site, can be substantial in systems dependent on database replication. This delay, necessary to ensure data currency and consistency, can adversely affect service levels and availability. Continuous monitoring of replication processes, managing failover ϭϬ^ and fallback operations, and securing data across multiple sites, necessitate complex operational procedures and substantial financial outlay. Lastly, the replication of sensitive data across multiple locations heightens security and privacy risks. Ensuring secure data transmission, storage compliance with regulatory standards, and effective access control across multiple sites adds further layers of security management complexity. ϭϱ^ [0005] The currently known solutions for database replication are complex and not easy to implement. Thus, the existing solutions also involve huge costs, at least in terms of system resources. ϮϬ^ [0006] Thus, there exists an imperative need in the art for avoiding database replication at a disaster recovery site for the transition of network traffic from a primary site to a disaster recovery (DR) site, which the present disclosure aims to address. SUMMARY Ϯϱ^ [0007] 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 claimed subject matter. ϯϬ^ [0008] An aspect of the present disclosure may relate to a method for transition of network traffic from a primary site to a disaster recovery (DR) site without a database replication. The method includes forwarding, by an access and mobility management function (AMF) module, a message request to a router, wherein the message request comprises the identity information associated with the one or more SMSF modules at the primary site. Next, the method includes checking, by the ϯϱ^ router, each of a plurality of available instances associated with the one or more SMSF modules Ϯ