FORM 2
THE PATENTS ACT, 1970 (39 OF 1970)
& THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR TRANSITION FROM PRIMARY SITE TO DISASTER RECOVERY SITE WITHOUT DATABASE REPLICATION”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

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 at the primary site to determine if one or more SMSF modules are down. Next, the method includes in an event when each of the SMSF modules at the primary site are down, sending, by the router, the message request to a SMSF module at the DR site. Next, the method includes checking, by the SMSF module at the DR site, the identity information, associated with the received message request, of one or more SMSF module at the primary site. Next, the method includes identifying, by the SMSF module at the DR site, a circle name based on the checking of the identity information of said one or more SMSF module of the primary site. Next, the method includes determining, by the SMSF module at the DR site, a unified data management (UDM) module based on the identified circle name. Next, the method includes receiving, by the SMSF module at the DR site

from the identified UDM module, an identity of the AMF module. Thereafter, the method includes forwarding, by the SMSF module at the DR site, the message to the AMF module based on the received AMF module identity for final termination.
[0009] In an exemplary aspect of the present disclosure, the method further comprises sending by the one or more first SMSF modules at the primary site, the identity information associated with the one or more first SMSF modules at the primary site to a network resource function (NRF) module.
[0010] In an exemplary aspect of the present disclosure, the method further comprises the identity information associated with the one or more SMSF modules at the primary site is sent as a JSON file.
[0011] In an exemplary aspect of the present disclosure, the method further comprises storing, in a storage unit, by the SMSF module at the DR site, information associated with all primary sites identity map in a configuration data file.
[0012] In an exemplary aspect of the present disclosure, the method further comprises the router is a service communication proxy (SCP) based router.
[0013] In an exemplary aspect of the present disclosure, the method further comprises the AMF module sends the message sending request to the router over HTTP2 network communication protocol.
[0014] In an exemplary aspect of the present disclosure, the method further comprises identifying, by the router, one or more SMSF modules at all primary sites.

[0015] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the SMSF module at the DR site from the identified UDM module, the identity of the AMF module comprises receiving, by the SMSF module at the DR site from the identified UDM module, a user profile; and determining, by the SMSF module, the identity of the AMF module corresponding to the received user profile.
[0016] Another aspect of the present disclosure may relate to 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 configured to forward 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. The system comprises the router configured to check each of a plurality of available instances associated with the one or more SMSF modules at the primary site to determine if one or more SMSF modules are down; send the message request to a SMSF module at the DR site in an event when each of the SMSF modules at the primary site are down. The system comprises the SMSF module at the DR site further configured to check, the identity information, associated with the received message request, of one or more SMSF module at the primary site; identify a circle name based on the checking of the identity information of said one or more SMSF module of the primary site; determine a unified data management (UDM) module based on the identified circle name; receive from the identified UDM module, an identity of the AMF module; and forward, the message to the AMF module based on the received AMF module identity for final termination.
[0017] Yet another aspect of the present disclosure may relate to 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 to forward a message request to a router, wherein the message request comprises the identity information associated with the one or more first SMSF modules at the primary site; the router to: check each of a plurality of available instances associated with the one or more first SMSF modules at the primary site to determine if one or more first SMSF modules are down; send the message request to a SMSF module at the DR site in an event when each of the one or more first SMSF modules at the primary site are down; the second SMSF module [304b] at the DR site to: check, the identity information, associated with the received message request, of one or more first SMSF module at the primary site; identify a circle name based on the checking of the identity information of said one or more first SMSF module of the primary site; determine a unified data management (UDM) module based on the identified circle name; receive from the identified UDM module, an identity of the AMF module; and forward, the message to the AMF module based on the received AMF module identity for final termination.
OBJECTS OF THE INVENTION
[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system and a method for avoiding database replication at disaster recovery (DR) site that allows smooth transition between primary site to DR site.
[0020] It is another object of the present disclosure to provide a system and a method for providing smooth and uninterrupted telecom services during primary site is down.

DESCRIPTION OF THE DRAWINGS
[0021] 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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0022] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core
[0023] (5GC) network architecture.
[0024] FIG. 2 illustrates an exemplary block diagram of a computer system upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0025] FIG. 3 illustrates an exemplary block diagram of a system for transition of network traffic from a primary site to a disaster recovery (DR) site without a database replication, in accordance with exemplary implementations of the present disclosure.
[0026] FIG. 4 illustrates a method flow diagram for transition of network traffic from a primary site to a disaster recovery (DR) site without a database replication in accordance with exemplary implementations of the present disclosure.

[0027] FIG. 5 illustrates an exemplary system block diagram for transition of
network traffic from a primary site to a disaster recovery (DR) site without a
database replication in accordance with exemplary implementations of the present
5 disclosure.
[0028] The foregoing shall be more apparent from the following more detailed description of the disclosure.
10 DETAILED DESCRIPTION
[0029] 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
15 embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
20
[0030] 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.
25 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.
[0031] Specific details are given in the following description to provide a thorough
30 understanding of the embodiments. However, it will be understood by one of
9

ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. 5
[0032] 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 may be performed in parallel or
10 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.
[0033] The word “exemplary” and/or “demonstrative” is used herein to mean
15 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
20 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.
25
[0034] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality
30 of microprocessors, one or more microprocessors in association with a (Digital
10

Signal Processing) DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing,
input/output processing, and/or any other functionality that enables the working of
5 the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
[0035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
10 “a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant,
15 tablet computer, wearable device or any other computing device which is capable
of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
20
[0036] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”),
25 magnetic disk storage media, optical storage media, flash memory devices or other
types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
11

[0037] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with
5 each other, which also includes the methods, functions, or procedures that may be
called.
[0038] As used herein “database replication” refers to a process in which data is copied from one database in one computer or server to one or more other databases
10 across different computers or servers, ensuring that each database mirror contains
the same information. The database replication can be done in real-time or on a scheduled basis, and it can be configured in various ways depending on the needs of the application, such as master-slave replication where one database is the authoritative source that updates others, or peer-to-peer replication where each
15 database can accept write operations. The primary purpose of database replication
is to increase the reliability, fault-tolerance, and accessibility of data, thereby enhancing the overall performance of the system by distributing the load and providing redundancy.
20 [0039] As used herein "HTTP/2" or "HTTP2", or "HTTP Version 2" refers to a
protocol aimed at enhancing web performance. HTTP2 introduces features such as multiplexing, which allows multiple requests and responses to be sent simultaneously over a single connection, and header compression, which reduces overhead. Additionally, HTTP/2 implements server push, where servers can
25 proactively send resources to the client, improving load times. Employing a binary
protocol rather than the textual format of its predecessor, HTTP/2 streamlines data exchange and maintains high compatibility with existing web applications by using the same APIs and URIs.
12

[0040] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more
5 microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0041] As used herein the transceiver unit include at least one receiver and at least
10 one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system and/or connected with the system.
[0042] As discussed in the background section, in traditional disaster recovery
15 (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
20 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
25 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
30 fallback operations, and securing data across multiple sites, necessitate complex
13

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
5 management complexity.
[0043] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by introducing a method and system that facilitates the transition of network traffic from a primary site to a disaster
10 recovery (DR) site without relying on database replication. The proposed solution
involves a sequence of operations starting with the AMF module forwarding a message request containing identity information of SMSF modules at the primary site to a router. The router checks the availability of these modules and direct traffic to an alternate SMSF module at the DR site if the primary modules are down. The
15 redirection is based on identity information alone, eliminating the need for live data
replication and thus sidestepping the latency and synchronization challenges that typically accompany such processes. Furthermore, the SMSF module at the DR site upon receiving the traffic, it verifies the identity information and identifies the relevant network circle or segment. It then consults a Unified Data Management
20 (UDM) module to retrieve the necessary AMF module identity, ensuring that the
message is forwarded correctly. The proposed solution does not require a mirrored database but rather operates on dynamically retrieved and verified data, which significantly enhances the system’s responsiveness and reduces recovery time during failovers. By deploying router (such as a service communication proxy
25 (SCP)) and utilizing modern network communication protocols like HTTP2, along
with data formats such as JSON, the system further ensures that the transmission of identity information is both efficient and secure.
[0044] It would be appreciated by the person skilled in the art that the proposed
30 solution addresses the drawbacks of previous DR systems by simplifying the
14

operational complexity, minimizing resource expenditure, enhancing security
measures, and ensuring quicker, more reliable failover capabilities. This not only
leads to improved service levels and network availability but also significantly
lowers the overall operational costs and security risks associated with disaster
5 recovery in telecommunications.
[0045] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network
10 architecture [100] includes a user equipment (UE) [102], a radio access network
(RAN) [104], an access and mobility management function (AMF) module [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network
15 Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118],
a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious
20 to the person skilled in the art for implementing features of the present disclosure.
[0046] Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network).
25 It consists of radio base stations and the radio access technologies that enable
wireless communication.
[0047] Access and Mobility Management Function (AMF) module [106] is a 5G core network function responsible for managing access and mobility aspects, such
15

as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
[0048] Session Management Function (SMF) [108] is a 5G core network function
5 responsible for managing session-related aspects, such as establishing, modifying,
and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0049] Service Communication Proxy (SCP) [110] is a network function in the 5G
10 core network that facilitates communication between other network functions by
providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
[0050] Authentication Server Function (AUSF) [112] is a network function in the
15 5G core responsible for authenticating UEs during registration and providing
security services. It generates and verifies authentication vectors and tokens.
[0051] Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is a network function that provides authentication and
20 authorization services specific to network slices. It ensures that UEs can access only
the slices for which they are authorized.
[0052] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors
25 such as subscription, requested services, and network policies.
[0053] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications. 30
16

[0054] Network Repository Function (NRF) [120] (alternatively referred to as NRF module [120]) is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions. 5
[0055] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
10 [0056] Unified Data Management (UDM) [124] (alternatively referred to as UDM
module [124]) is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0057] Application Function (AF) [126] is a network function that represents
15 external applications interfacing with the 5G core network to access network
capabilities and services.
[0058] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
20 enforcement.
[0059] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
25
[0060] FIG. 2 illustrates an exemplary block diagram of a computer system [1000]] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computer system [1000] may also implement a method for
30 transition of network traffic from a primary site to a disaster recovery (DR) site
17

without a database replication utilising the system. In another implementation, the
computer system [1000] itself implements the method for transition of network
traffic from a primary site to a disaster recovery (DR) site without a database
replication using one or more units configured within the computer system [1000],
5 wherein said one or more units are capable of implementing the features as
disclosed in the present disclosure.
[0061] The computer system [1000] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of
10 computer system [1000] include, but are not limited only to, personal computers,
laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computer system [1000] may include peripheral devices, such as monitors, keyboards, and printers, as well
15 as integrated components within larger electronic systems, showcasing their
versatility in various technological applications.
[0062] The computer system [1000] may include a bus [1002] or other communication mechanism for communicating information, and a processor [1004]
20 coupled with bus [1002] for processing information. The processor [1004] may be,
for example, a general purpose microprocessor. The computer system [1000] may also include a main memory [1006], such as a random access memory (RAM), or other dynamic storage device, coupled to the bus [1002] for storing information and instructions to be executed by the processor [1004]. The main memory [1006] also
25 may be used for storing temporary variables or other intermediate information
during execution of the instructions to be executed by the processor [1004]. Such instructions, when stored in non-transitory storage media accessible to the processor [1004], render the computer system [1000] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computer
30 system [1000] further includes a read only memory (ROM) [1008] or other static
18

storage device coupled to the bus [1002] for storing static information and instructions for the processor [1004].
[0063] A storage device [1010], such as a magnetic disk, optical disk, or solid-state
5 drive is provided and coupled to the bus [1002] for storing information and
instructions. The computer system [1000] may be coupled via the bus [1002] to a display [1012], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [1014], including
10 alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [1002] for communicating information and command selections to the processor [1004]. Another type of user input device may be a cursor control [1016], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [1004], and for controlling
15 cursor movement on the display [1012]. This input device typically has two degrees
of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0064] The computer system [1000] may implement the techniques described
20 herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computer system [1000] causes
or programs the computer system [1000] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
computer system [1000] in response to the processor [1004] executing one or more
25 sequences of one or more instructions contained in the main memory [1006]. Such
instructions may be read into the main memory [1006] from another storage medium, such as the storage device [1010]. Execution of the sequences of instructions contained in the main memory [1006] causes the processor [1004] to perform the process steps described herein. In alternative implementations of the
19

present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0065] The computer system [1000] also may include a communication interface
5 [1018] coupled to the bus [1002]. The communication interface [1018] provides a
two-way data communication coupling to a network link [1020] that is connected to a local network [1022]. For example, the communication interface [1018] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a
10 corresponding type of telephone line. As another example, the communication
interface [1018] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [1018] sends and receives electrical, electromagnetic or optical signals that carry digital
15 data streams representing various types of information.
[0066] The computer system [1000] can send messages and receive data, including program code, through the network(s), the network link [1020] and the communication interface [1018]. In the Internet example, a server [1030] might
20 transmit a requested code for an application program through the Internet [1028],
the ISP [1026], the host [1024], the local network [1022] and the communication interface [1018]. The received code may be executed by the processor [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage for later execution.
25
[0067] Referring to FIG. 3, an exemplary block diagram of a system [300] for transition of network traffic from a primary site to a disaster recovery (DR) site without a database replication is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one
30 first Short Message Service Function (SMSF) module [304a] for primary site, at
20

least one Short Message Service Function (SMSF) module [304b] for disaster
recovery site, at least one Access and Mobility Management Function (AMF)
module [106], at least one generation unit [308], at least one Router (such as SCP
based router) [306], at least one Unified Data Management (UDM) module [124],
5 at least one Network Resource Function (NRF) module [120] and at least one
Storage Unit [302]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the
10 system [300] may comprise multiple such units or the system [300] may comprise
any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device to implement the features of the present disclosure. The system [300] may be a part of the user device or may be independent of but in communication with
15 the user device (may also referred herein as a UE [102]). In another implementation,
the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.
20 [0068] The system [300] is configured for transition of network traffic from a
primary site to a disaster recovery (DR) site without a database replication, with the help of the interconnection between the components/units of the system [300].
[0069] The system [300] comprises the AMF module [106], which is configured to
25 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 AMF (Access and Mobility Management Function) module
[106] acts as a gateway that handles all the signalling between user device [102]
and the network infrastructure, ensuring that mobility is managed efficiently, even
30 when the user moves across different geographical network segments. Examples of
21

the identity information include but are not limited only to unique SMSF Module Identifiers assigned to each SMSF module, IP addresses information, configuration information, and status information, and location information.
5 [0070] The AMF module [106] initiates communication with the disaster recovery
(DR) site by sending a message request to the router [306] (alternatively referred to as SCP based router [306] hereinafter). The message request includes identity information, such as unique identifiers or configuration details, of the one or more first SMSF modules [304a] that are operating at the primary site. The one or more
10 first SMSF modules [304a] facilitates in handling SMS messaging services within
the network. The identity information might detail the operational status, capabilities, and any specific service configurations of the SMSF modules. The router [306] then uses the identity information to route the message appropriately within the network, ensuring that the DR site can take over the messaging services
15 without interruption. The one or more first SMSF modules [304a] at the primary
site are 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]. In an embodiment, the identity information associated with the one or more first SMSF modules [304a] at the primary site is sent as a JavaScript Object
20 Notation (JSON) file format.
[0071] The AMF module [106] forwards the message request to the router [306] over HTTP2 network communication protocol. The message request further may include information such as, but not limited to, user profile information, user service
25 circle name, and AMF module [106] information. In an implementation, the AMF
module [106] sends setID information of SMSF in Header (such as, for example, 3gpp-sbi-discovery-target-nf-set-id). In an exemplary aspect, the router [306] is a service communication proxy (SCP) based router [306]. In an exemplary aspect, the AMF module [106] may receive the identity information associated with the
30 one or more first SMSF modules [304a] via the NRF module [120]. In another
22

exemplary aspect, the AMF module [106] may receive the identity information associated with the one or more first SMSF modules [304a] over N20 interface.
[0072] The system [300] further comprises the router [306], which is configured to
5 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. The router [306] facilitates in ensuring that the one or more first SMSF modules [304a] are functioning correctly and are available to handle network traffic as required. For example, the router [306] may periodically
10 send heartbeat signals or status request messages to each of the one or more first
SMSF modules [304a]. The messages help to ascertain the operational status of the one or more first SMSF modules [304a]. If any module of the one or more first SMSF modules [304a] does not respond within a predetermined time frame, or if the response indicates a failure or a fault condition, the router [306] marks that
15 particular SMSF module as "down" or "unavailable". In an exemplary aspect, after
receiving the message request from the AMF module [106], the router or SCP based router [306] checks the received identity information associated with the one or more first SMSF modules [304a] at the primary site to determine one or more first SMSF modules [304a] are in active or down state. The router or SCP based router
20 [306] is configured to identify the one or more first SMSF modules [304a] at all
primary sites. If the router or SCP based router [306] determines each of the one or more first SMSF modules [304a] are down, the router or SCP based router [306] sends the message request to the second SMSF module [304b] at the disaster recovery (DR) site.
25
[0073] The router [306] is further configured to send the message request to the second SMSF module [304b] at the DR (Disaster Recovery) site in an event when each of the one or more first SMSF modules [304a] at the primary site are down. For example, in a large telecommunications network, the primary site includes
30 several SMSF modules responsible for handling SMS traffic for a vast number of
23

users. If an unforeseen issue, such as a power outage, hardware failure, or network
disruption, results in all these SMSF modules becoming non-operational, the router
[306] automatically activates its failover protocol. It reroutes all pending and
incoming message requests to the second SMSF module [304b] located at the DR
5 site which is unaffected by the same incident. In an embodiment, the DR sire may
be geographically separate from the primary site. In another embodiment, The DR site may be geographically at the same as the primary site.
[0074] The system [300] further comprises a second SMSF module [304b] at the
10 DR site, which is configured to check the identity information associated with the
received message request, of one or more first SMSF modules [304a] at the primary site. For instance, when the router [306] detects that one or more first SMSF modules [304a] at the primary site are down, it forwards the message request to the second SMSF module [304b] at the DR site. Upon receiving the message request,
15 the second SMSF module [304b] validates the identity information associated with
the message request. By checking the identity information, the second SMSF module [304b] at the DR site can determine the context of the message requests, such as their origin, priority, and intended processing requirements. For example, in a scenario where the primary site's SMSF modules are configured to handle
20 messages with specific security protocols or routing preferences. The DR SMSF
module, upon verifying these settings from the identity information, would then ensure these protocols or preferences are adhered to when handling the incoming messages, thereby maintaining the integrity and consistency of the service as experienced by the end users.
25
[0075] The second SMSF module [304b] at the DR site is further configured to identify a circle name based on the checking of the identity information of said one or more first SMSF modules [304a] at the primary site. For example, the primary site’s SMSF modules are configured to manage SMS traffic for specific circle. The
30 circles could represent distinct areas like cities, states, or even specific customer
24

segments. Each of the one or more first SMSF modules [304a] at the primary site
might be responsible for handling SMS traffic for one or more such circles. The
identity information includes details that define these circle associations. When the
second SMSF module [304b] at the DR site receives the message request from the
5 primary site, it first checks the identity information associated with the message
request to determine which circle or circles the one or more first SMSF modules [304a] were servicing. By identifying the circles, the DR site's second SMSF module [304b] can then continue to provide services according to the predefined specifications for those circles.
10
[0076] For example, the primary site handles SMS services for urban and rural circles differently, offering different routing priorities or message-handling protocols. When the DR site’s SMSF module identifies the circle names from the identity information, it can apply the same differentiated service rules, ensuring that
15 users continue to receive SMS services seamlessly and without disruption, even
though the service is now being managed from the DR site.
[0077] The circle refers to a geographic or administrative region within which a particular set of network services and regulations are uniformly applied. The circle
20 facilitates mobile network operators to manage and organize their services
according to the distinct regulatory, commercial, and technical requirements of different areas. For example, in a country, the telecom industry is divided into various circles that may correspond to one or more states or sometimes parts of a state. Each of these circles will have its own set of tariffs, network infrastructure,
25 regulatory compliances, and customer service policies that are tailored to the local
market conditions and regulatory environment. The regional segmentation allows operators to optimize their services and pricing structures according to the specific demands and competition in each area. Within such a circle, all operational activities, from billing and customer service to network management and
30 compliance, are designed to align with the local regulations and customer
25

preferences. For example, a telecom circle in a metropolitan area might focus on providing high-speed data services due to high demand for fast internet, while a circle in a rural area might prioritize wide coverage and voice services.
5 [0078] The second SMSF module [304b] at the DR site is further configured to
determine a Unified Data Management (UDM) module [124] based on the
identified circle name. For example, the second SMSF module [304b] determines
that the incoming message request originates from a primary SMSF module that
was serving the NorthZone circle. The UDM module [124] associated with the
10 NorthZone circle contains all user profiles, service preferences, and other data
specific to subscribers in that geographical area. Upon identifying the circle name, the second SMSF module [304b] consults the UDM to retrieve the necessary information to handle the incoming messages correctly.
15 [0079] It would be appreciated by the person skilled in the art that by determining
the UDM module, the proposed solution facilitates in ensuring that all user-specific settings and preferences are maintained even when the service is transitioned to the DR site. For example, if the NorthZone circle has specific rules for message routing during peak hours or preferences for message delivery reports, these can be
20 accurately applied by the DR SMSF module only if it consults the correct UDM.
Further, determining the correct UDM ensures compliance with any regional regulations or service standards that might apply to the handling of communications for users in that circle. For example, if the NorthZone requires adherence to stricter privacy standards or has opted into enhanced service features, the DR SMSF
25 module can only apply these if it retrieves the relevant data from the UDM
designated for the NorthZone.
[0080] The second SMSF module [304b] at the DR site is further configured to
receive from the identified UDM module [124], an identity of the AMF module
30 [106]. The UDM (Unified Data Management) module [124], which stores user data
26

and service configurations, provides the second SMSF module [304b] with the
specific identity details of the appropriate AMF module [106] that it needs to
interact with. This identity information typically includes network addresses,
service capabilities, and other operational parameters essential for establishing and
5 maintaining a connection between the second SMSF module [304b] and the AMF
module [106]. For example, if a user's session was initially being managed by an AMF module at the primary site, the DR SMSF module will use the identity information received from the UDM module [124] to select a corresponding AMF module at the DR site or another operational site.
10
[0081] The second SMSF module [304b] at the DR site is further configured to forward the message to the AMF module [106] based on the received AMF module identity for final termination. For example, once the second SMSF module [304b] at the DR site has received the necessary identity information of the appropriate
15 AMF module [106] from the UDM module [124], it uses this information to route
messages accurately. The AMF module identity includes specific network addresses, routing information, and service specifications that enable the second SMSF module [304b] to establish a direct communication link with the correct AMF module for maintaining service continuity, especially in scenarios where
20 multiple AMF modules may be present, each handling different segments of
network traffic or different user groups.
[0082] 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
25 a configuration data file. By storing detailed identity information about each
primary site, the second SMSF module [304b] ensures that it has all necessary data to quickly assume control over network services in the event of a primary site failure. For example, the stored information might include unique identifiers, operational status, network configurations, and specific service settings for each
30 SMSF module operating at the primary sites. The data is organized in a
27

configuration data file within the storage unit [302], which allows for rapid access
and retrieval when needed. During a disaster recovery scenario, when a primary
site's SMSF modules become unavailable, the DR site's second SMSF module
[304b] can immediately reference this stored data to understand the operational
5 context and service requirements of the affected modules.
[0083] It would be appreciated by the person skilled in the art that the pre-emptive
storage of detailed identity maps not only facilitates a faster response during
disruptions but also minimizes the potential for service degradation or errors in
10 handling network traffic, thus upholding the network's reliability and efficiency
under all circumstances.
[0084] 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
15 identity of the AMF module [106] corresponding to the received user profile. The
UDM module [124], stores comprehensive user profiles including service preferences, device details, and network usage patterns, sends this information to the second SMSF module [304b] at the DR site. Upon receiving a user profile, the second SMSF module [304b] analyses the data to identify which AMF module
20 [106] currently manages services for this particular user. For example a user who
accesses services in a specific network segment managed by a particular AMF module. If the primary site fails, the DR site's SMSF module, having received the user's profile from the UDM module [124], will use the profile details to determine which AMF module [106] at the DR site should take over the management of that
25 user's session. This process involves matching the user's service area and
preferences with the capabilities and location of the available AMF modules at the DR site.
[0085] In an exemplary aspect, the disclosure encompasses getting user profile
30 from the UDM module [124] and mentions UDM’s PLMN in header such as 3gpp-
28

sbi-discovery-target-plmn-list. In response to this, the second SMSF module [304b]
gets AMF ID information such as, but not limited to in
Amf3GppAccessRegistration header. Thereafter, the second SMSF module [304b]
at disaster recovery site forwards message or SMS to the identified AMF ID for
5 final termination.
[0086] Referring to FIG. 4, an exemplary method flow diagram [400] for transition
of network traffic from a primary site to a disaster recovery (DR) site without a
database replication, in accordance with exemplary implementations of the present
10 disclosure is shown. In an implementation the method [400] is performed by the
system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].
15 [0087] At step [404], the method [400] as disclosed by the present disclosure
comprises 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 the one or more first Short Message Service Function (SMSF) modules [304a] at the primary site.
20
[0088] The AMF (Access and Mobility Management Function) module [106] acts as a gateway that handles all the signalling between user device [102] and the network infrastructure, ensuring that mobility is managed efficiently, even when the user moves across different geographical network segments. Examples of the
25 identity information include but are not limited only to unique SMSF Module
Identifiers assigned to each SMSF module, IP addresses information, configuration information, and status information, and location information.
[0089] The AMF module [106] initiates communication with the disaster recovery
30 (DR) site by sending a message request to the router [306] (alternatively referred to
29

as SCP based router [306] hereinafter). The message request includes identity
information, such as unique identifiers or configuration details, of the one or more
first SMSF modules [304a] that are operating at the primary site. The one or more
first SMSF modules [304a] facilitates in handling SMS messaging services within
5 the network. For example, there is a situation where the primary site is experiencing
a failure or significant disruption. In such cases, the AMF module [106] detects the issue and prepares a message request that includes identity information about the SMSF modules at risk. The identity information might detail the operational status, capabilities, and any specific service configurations of the SMSF modules. The
10 router [306] then uses the identity information to route the message appropriately
within the network, ensuring that the DR site can take over the messaging services without interruption. 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)
15 module [120]. In an embodiment, 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.
[0090] The AMF module [106] forwards the message request to the router [306]
20 over HTTP2 network communication protocol. The message request further may
have information such as, but not limited to, user profile information, user service
circle name, and AMF module [106] information. In an implementation, the AMF
module [106] sends setID information of SMSF in Header (such as, for example,
3gpp-sbi-discovery-target-nf-set-id. In an exemplary aspect, the router [306] is a
25 service communication proxy (SCP) based router. In an exemplary aspect, the AMF
module [106] may receive the identity information associated with the one or more
first SMSF modules [304a] via the NRF module [120]. In another exemplary aspect,
the AMF module [106] may receive the identity information associated with the
one or more first SMSF modules [304a] over N20 interface.
30
30

[0091] Next, at step [406], the method [400] as disclosed by the present disclosure
comprises 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. The router [306]
5 facilitates in ensuring that the one or more first SMSF modules [304a] are
functioning correctly and are available to handle network traffic as required. For example, the router [306] may periodically send heartbeat signals or status request messages to each of the one or more first SMSF modules [304a]. The messages help to ascertain the operational status of the modules. If any module of the one or more
10 first SMSF modules [304a] does not respond within a predetermined time frame, or
if the response indicates a failure or a fault condition, the router [306] marks that particular SMSF module as "down" or "unavailable". In an exemplary aspect, after receiving the message request from the AMF module [106], the router or SCP based router [306] checks the received identity information associated with the one or
15 more first SMSF modules [304a] at the primary site to determine one or more first
SMSF modules [304a] are in active or down state. The router or SCP based router [306] is configured to identify the one or more first SMSF modules [304a] at all primary sites. If the router or SCP based router [306] determines each of the one or more first SMSF modules [304a] are down, the router or SCP based router [306]
20 sends the message request to the second SMSF module [304b] at the disaster
recovery (DR) site.
[0092] Next, at step [408], the method [400] as disclosed by the present disclosure comprises sending, by the router [306], the message request to the second SMSF
25 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. For example, in a large telecommunications network, the primary site includes several SMSF modules responsible for handling SMS traffic for a vast number of users. If an unforeseen issue, such as a power outage, hardware failure, or network disruption, results in all
30 these SMSF modules becoming non-operational, the router [306] automatically
31

activates its failover protocol. It reroutes all pending and incoming message
requests to the second SMSF module [304b] located at the DR site which is
unaffected by the same incident. In an embodiment, the DR sire may be
geographically separate from the primary site. In another embodiment, The DR site
5 may be geographically at the same as the primary site.
[0093] Next, at step [410], the method [400] as disclosed by the present disclosure
comprises 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
10 SMSF module [304a] at the primary site.
[0094] Next, at step [412], the method [400] as disclosed by the present disclosure comprises identifying, by the second SMSF module [304b] at the DR site, a circle
15 name based on the checking of the identity information of said one or more first
SMSF module [304a] of the primary site. For instance, when the router [306] detects that one or more first SMSF modules [304a] at the primary site are down, it forwards the message request to the second SMSF module [304b] at the DR site. Upon receiving the message request, the second SMSF module [304b] validates the
20 identity information associated with the message request. By checking the identity
information, the second SMSF module [304b] at the DR site can determine the context of the message requests, such as their origin, priority, and intended processing requirements. For example, in a scenario where the primary site's SMSF modules are configured to handle messages with specific security protocols or
25 routing preferences. The DR SMSF module, upon verifying these settings from the
identity information, would then ensure these protocols or preferences are adhered to when handling the incoming messages, thereby maintaining the integrity and consistency of the service as experienced by the end users.
32

[0095] Next, at step [414], the method [400] as disclosed by the present disclosure
comprises determining, by the second SMSF module [304b] at the DR site, a unified
data management (UDM) module [124] based on the identified circle name. For
example, the second SMSF module [304b] determines that the incoming message
5 request originates from a primary SMSF module that was serving the NorthZone
circle. The UDM module [124] associated with the NorthZone circle contains all user profiles, service preferences, and other data specific to subscribers in that geographical area. Upon identifying the circle name, the second SMSF module [304b] consults the UDM to retrieve the necessary information to handle the
10 incoming messages correctly. It would be appreciated by the person skilled in the
art that by determining the UDM module, the proposed solution facilitates in ensuring that all user-specific settings and preferences are maintained even when the service is transitioned to the DR site. For example, if the NorthZone circle has specific rules for message routing during peak hours or preferences for message
15 delivery reports, these can be accurately applied by the DR SMSF module only if it
consults the correct UDM. Further, determining the correct UDM ensures compliance with any regional regulations or service standards that might apply to the handling of communications for users in that circle. For example, if the NorthZone requires adherence to stricter privacy standards or has opted into
20 enhanced service features, the DR SMSF module can only apply these if it retrieves
the relevant data from the UDM designated for the NorthZone.
[0096] Next, at step [416], the method [400] as disclosed by the present disclosure comprises receiving, by the second SMSF module [304b] at the DR site from the
25 identified UDM module [124], an identity of the AMF module [106]. The UDM
(Unified Data Management) module [124], which stores user data and service configurations, provides the second SMSF module [304b] with the specific identity details of the appropriate AMF module [106] that it needs to interact with. This identity information typically includes network addresses, service capabilities, and
30 other operational parameters essential for establishing and maintaining a connection
33

between the second SMSF module [304b] and the AMF module [106]. For
example, if a user's session was initially being managed by an AMF module at the
primary site, the DR SMSF module will use the identity information received from
the UDM module [124] to select a corresponding AMF module at the DR site or
5 another operational site.
[0097] Next, at step [418], the method [400] as disclosed by the present disclosure comprises 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
10 final termination. For example, once the second SMSF module [304b] at the DR
site has received the necessary identity information of the appropriate AMF module [106] from the UDM module [124], it uses this information to route messages accurately. The AMF module identity includes specific network addresses, routing information, and service specifications that enable the second SMSF module [304b]
15 to establish a direct communication link with the AMF module [106] for
maintaining service continuity, especially in scenarios where multiple AMF modules may be present, each handling different segments of network traffic or different user groups.
20 [0098] Thereafter, the method [400] terminates at step [420].
[0099] FIG. 5 illustrates an exemplary system block diagram [500] for transition of
network traffic from a primary site to a disaster recovery (DR) site without a
database replication in accordance with exemplary implementations of the present
25 disclosure.
[0100] As shown in FIG.5, the system [500] comprises at least one NRF [120], at
least one AMF module [106], at least one SMSF [502], at least one UDM module
[124] and at least one IP short message (IPSM) gateway [504]. The SMSF [502]
30 communicates with NRF [120] module using HTTP2 protocol. The SMSF [502]
34

communicates with the AMF module [106] using HTTP2 protocol via N20 interface. The SMSF [502] communicates with UDM module [124] using HTTP2 protocol via N20 interface. The SMSF [502] communicates with IPSM [504] using Diameter protocol via SGd interface. 5
[0101] As shown in FIG. 5, the system [500] enables a seamless transition of network traffic from a primary site to a disaster recovery (DR) site without the necessity for database replication.
10 [0102] The NRF module [120] holds details about various network functions and
their instances for managing the service registration and discovery process. The NRF module [120] facilitates in identifying which network functions are operational or down, as well as in locating alternative resources in disaster recovery scenarios.
15
[0103] The AMF module [106] facilitates in managing user sessions and their mobility across the network. The AMF module [106] facilitates in forwarding message requests, which include identity information of SMSF modules from the primary site to a router.
20
[0104] The SMSF [502] manages all SMS communications within the network. In the disaster recovery scenario, the SMSF [502] at the DR site checks the identity information received from the primary site's SMSF modules, identifies relevant service parameters (like circle names), and interacts with the UDM to retrieve
25 necessary user and AMF information for message forwarding.
[0105] The UDM module [124] stores and manages detailed user profiles and
service data. Once the SMSF [502] at the DR site identifies the required service
circle, it retrieves from the UDM module [124] the identity of the appropriate AMF
30 module [106] to which messages should be forwarded to ensure that all user-
35

specific services are maintained accurately, even during the transition to the DR site.
[0106] The IPSM [504] facilitate the integration of traditional short message
5 service (SMS) communications into modern IP (Internet Protocol) networks. The
IPSM gateway enhances interoperability by allowing seamless transmission of
SMS messages not just over cellular networks but also via the internet.
Furthermore, the IPSM is responsible for converting protocols to ensure
compatibility between different network types. This involves transforming
10 messages from standard SMS formats to those suitable for IP networks, such as SIP
(Session Initiation Protocol) or SMPP (Short Message Peer-to-Peer).
[0107] The present disclosure further discloses a non-transitory computer-readable storage medium storing instruction for transition of network traffic from a primary
15 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
20 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; [0108] send the message request to the 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
25 site are down; the second SMSF module [304b] at the DR site 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]
30 based on the identified circle name; receive from the identified UDM module [124],
36

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.
[0109] As is evident from the above, the present disclosure provides a technically
5 advanced solution for database replication at disaster recovery site. The solution
provides a system and a method that allows smooth transition of the database of SMS messages from a primary site to a disaster recovery site.
[0110] Further, in accordance with the present disclosure, it is to be acknowledged
10 that the functionality described for the various the components/units can be
implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
15 as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
20 [0111] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to
25 be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
37

We Claim:
. 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.