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 OPTIMISING AVAILABILITY OF AN UPDATED DATA AT A SECONDARY SITE”
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 OPTIMISING AVAILABILITY OF AN UPDATED DATA AT A SECONDARY SITE
FIELD OF INVENTION
5
[0001] Embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to method and system for optimising availability of an updated data at a secondary site. 10
BACKGROUND OF THE DISCLOSURE
[0002] The following description of related art is intended to provide background
information pertaining to the field of the disclosure. This section may include
15 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.
20 [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
25 services became possible, and text messaging was introduced. The third generation
(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
30 being deployed, promising even faster data speeds, low latency, and the ability to
2

connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
5 [0004] As used herein, NEF refers to a Network Exposure Function which is
considered to be an essential element of the core 5G network. The NEF is located
between the 5G core network and external third-party application functionaries
(AFs) and is responsible for managing the external open network data. In addition,
all external applications that want to access the internal data of the 5G core shall
10 pass through the NEF for security of data.
[0005] When a User Equipment (UE) is connected to an Access & Mobility
Management Function (AMF), a session gets created and information about the
same is transmitted to a NEF site cluster. During communication, when there is a
15 complete failure of the NEF site cluster, in order to restore the communication
handled by such NEF site cluster, the NEF site cluster has to be restarted in order to allow the communication to happen which is a time taking process.
[0006] Further, over the period of time various solutions have been developed to
20 improve the performance of communication devices and to provide data availability
to a Disaster Recovery (DR) Site to allow communication to run smoothly in case
a Geo-Redundant (GR) Site is in a shut-down state or is not working properly.
However, there are certain challenges with existing solutions. The existing
solutions are time-inefficient solutions that also hamper user experience and lead to
25 delayed communication. Further, the existing solutions involve inefficient
utilization of the resources.
[0007] Thus, there exists an imperative need in the art to provide the data availability to the Disaster Recovery (DR) Site to allow communication to run
3

smoothly in case the Geo-Redundant (GR) Site is in a shut-down state or is not working properly, which the present disclosure aims to address.
OBJECTS OF THE DISCLOSURE
5
[0008] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0009] It is an object of the present disclosure to provide a method and system for
10 optimising availability of an updated data at a secondary site.
[0010] It is an object of the present disclosure to provide a system and a method for
availability of data to a Disaster Recovery (DR) Site to allow communication to run
smoothly in case a Geo-Redundant (GR) Site is in a shut-down state or is not
15 working properly.
[0011] It is another object of the present disclosure to provide a solution that is time effective.
20 [0012] It is yet another object of the present disclosure to provide a solution that
provides optimal utilization of resources.
SUMMARY
25 [0013] 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.
4

[0014] An aspect of the present disclosure may relate to a method for optimising
availability of an updated data at a secondary site. The method comprising
receiving, by a transceiver unit at a Network Exposure Function (NEF) from an
Application Function (AF), a service request, wherein the service request is
5 associated with one or more database operation request; identifying, by an
identification unit at the NEF, at least one target database operation based on the one or more database operation request associated with the service request; executing, by an analysis unit from the NEF at a database cluster associated with the NEF, the at least one target database operation; transmitting, by the transceiver
10 unit from the NEF to an auditor associated with the NEF, the at least one target
database operation based on executing at the database cluster the at least one target database operation; and facilitating, by the analysis unit at the NEF, a replication of the at least one target database operation based on the transmission of the at least one target database operation from the transceiver unit of the NEF to the auditor
15 associated with the NEF.
[0015] In an exemplary aspect of the present disclosure, the method further comprises: facilitating, by the analysis unit at the NEF, the replication of the at least one target database operation comprises: generating, by the auditor, an output data
20 based on the at least one target database operation; transmitting, from the auditor
associated with the NEF to the secondary site associated with the NEF, the output data associated with the at least one target database operation; generating, by a disaster recovery auditor associated with the secondary site, a replicate data based on the output data associated with the at least one target database operation;
25 executing, by the disaster recovery auditor at a disaster recovery database cluster
associated with the secondary site, the at least one target database operation based on the replicate data.
[0016] In an exemplary aspect of the present disclosure, the method further
30 comprises: transmitting, from the auditor associated with the NEF to the secondary
5

site associated with the NEF, the output data associated with the at least one target database operation is performed using one of a plurality of paths.
[0017] In an exemplary aspect of the present disclosure, the method further
5 comprises: using a first path of the plurality of paths, the data is received at a second
receiver associated with the secondary site from a first sender associated with a primary site.
[0018] In an exemplary aspect of the present disclosure, the method further
10 comprises: using a second path of the plurality of paths, the data is received at the
second receiver associated with the secondary site from the first sender associated with the primary site via a third proxy deployed at a tertiary site in an event of failure of direct connectivity between the first sender and the second receiver.
15 [0019] In an exemplary aspect of the present disclosure, the method further
comprises: using a third path of the plurality of paths, the data is received at a second proxy associated with the secondary site from the first sender associated with the primary site via a third proxy deployed at a tertiary site during downtime of the receiver associated with the secondary site.
20
[0020] In an exemplary aspect of the present disclosure, the method further comprises: using a fourth path of the plurality of paths, the data is received at the second proxy associated with the secondary site from the first sender associated with the primary site during downtime of the second receiver associated with the
25 secondary site and the third proxy associated with a tertiary site.
[0021] In an exemplary aspect of the present disclosure, the method further comprises: transmitting, by the transceiver unit from the NEF via a cache associated with the NEF to the auditor associated with the NEF, the at least one target database
6

operation based on executing at the database cluster the at least one target database operation.
[0022] In an exemplary aspect of the present disclosure, the one or more database
5 operation request is at least one of a database insert operation request, a database
update operation request, and a database delete operation request.
[0023] In an exemplary aspect of the present disclosure, the method further comprises: detecting, by the analysis unit, a failure status associated with at least
10 one of the NEF and the secondary site associated with the NEF based on one or
more predefined rules; and transmitting, by the transceiver unit, at least a service traffic associated with the service request to at least one of the NEF and the secondary site associated with the NEF based on the failure status associated with at least one of the NEF and the secondary site.
15
[0024] In an exemplary aspect of the present disclosure, the method further comprises: synchronizing, by the analysis unit, in real time, at least the database cluster and the disaster recovery database cluster.
20 [0025] In an exemplary aspect of the present disclosure, the method further
comprises the secondary site is a disaster recovery site.
[0026] Another aspect of the present disclosure may relate to a system for optimising availability of an updated data at a secondary site. The system comprises
25 a transceiver unit at a Network Exposure Function (NEF), the transceiver unit is
configured to receive from an Application Function (AF), a service request, wherein the service request is associated with one or more database operation request; an identification unit at the NEF, the identification unit connected to at least the transceiver unit, the identification unit is configured to identify at least one target
30 database operation based on the one or more database operation request associated
7

with the service request; an analysis unit connected to at least the identification unit,
the analysis unit configured to execute at a database cluster associated with the
NEF, the at least one target database operation; the transceiver unit is further
configured to transmit, from the NEF to an auditor associated with the NEF, the at
5 least one target database operation based on executing at the database cluster the at
least one target database operation, and the analysis unit is further configured to facilitate, by at the NEF, a replication of the at least one target database operation based on the transmission of the at least one target database operation from the transceiver unit of the NEF to the auditor associated with the NEF.
10
[0027] Yet, another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for optimising availability of an updated data at a secondary site. The instructions when executed by one or more units of a system, causes a transceiver unit of the system at a Network
15 Exposure Function (NEF), to receive from an Application Function (AF), a service
request, wherein the service request is associated with one or more database operation request; an identification unit of the system at the NEF, to identify at least one target database operation based on the one or more database operation request associated with the service request; an analysis unit of the system to execute at a
20 database cluster associated with the NEF, the at least one target database operation;
the transceiver unit of the system to transmit, from the NEF to an auditor associated with the NEF, the at least one target database operation based on executing at the database cluster the at least one target database operation, and the analysis unit of the system to facilitate, at the NEF, a replication of the at least one target database
25 operation based on the transmission of the at least one target database operation
from the transceiver unit of the NEF to the auditor associated with the NEF.
BRIEF DESCRIPTION OF DRAWINGS
8

[0028] 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,
5 emphasis instead being placed upon clearly illustrating the principles of the present
disclosure. Some drawings may indicate the components using block diagrams and
may not represent the internal circuitry of each component. It will be appreciated
by those skilled in the art that disclosure of such drawings includes disclosure of
electrical components, electronic components or circuitry commonly used to
10 implement such components.
[0029] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
15 [0030] FIG. 2 illustrates an architecture diagram of a system [200] for optimising
availability of an updated data at a secondary site, in accordance with exemplary embodiments of the present disclosure.
[0031] FIG. 3 illustrates an exemplary block diagram of a system [300] for
20 optimising availability of an updated data at a secondary site, in accordance with
exemplary embodiments of the present disclosure.
[0032] FIG. 4 illustrates an exemplary method flow [400] diagram indicating the
process for optimising availability of an updated data at a secondary site, in
25 accordance with exemplary embodiments of the present disclosure.
[0033] FIG. 5 illustrates a first exemplary embodiment indicating the process [500] for optimising availability of an updated data at a secondary site, in accordance with exemplary embodiments of the present disclosure. 30
9

[0034] FIG. 6 illustrates a second exemplary embodiment indicating the process [600] for optimising availability of an updated data at a secondary site, in accordance with exemplary embodiments of the present disclosure.
5 [0035] FIG. 7 illustrates an exemplary scenario method flow [700] diagram in other
words indicating the process for availability of data into a secondary Site i.e., optimising availability of an updated data at a secondary site, in accordance with exemplary embodiments of the present disclosure.
10 [0036] FIG. 8 illustrates an exemplary block diagram [800] of a computing device
upon which an embodiment of the present disclosure may be implemented, in accordance with exemplary embodiments of the present disclosure.
[0037] The foregoing shall be more apparent from the following more detailed
15 description of the disclosure.
DETAILED DESCRIPTION
[0038] In the following description, for the purposes of explanation, various
20 specific details are set forth in order to provide a thorough understanding of
embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter can each be used independently of one
another or with any combination of other features. An individual feature may not
25 address any of the problems discussed above or might address only some of the
problems discussed above. Some of the problems discussed above might not be
fully addressed by any of the features described herein. Example embodiments of
the present disclosure are described below, as illustrated in various drawings in
which like reference numerals refer to the same parts throughout the different
30 drawings.
10

[0039] 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
5 the art with an enabling description for implementing an exemplary embodiment.
It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
10 [0040] It should be noted that the terms "mobile device", "user equipment", "user
device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for
15 convenience and clarity of description. The invention is not limited to any particular
type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
20 [0041] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to
25 obscure the embodiments in unnecessary detail. In other instances, well-known
circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0042] Also, it is noted that individual embodiments may be described as a process
30 which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
11

diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations can be performed in parallel or
concurrently. In addition, the order of the operations may be re-arranged. A process
is terminated when its operations are completed but could have additional steps not
5 included in a figure.
[0043] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any
10 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed
15 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.
[0044] As used herein, an “electronic device”, or “portable electronic device”, or
20 “user device” or “communication device” or “user equipment” or “device” refers
to any electrical, electronic, electromechanical, and computing device. The user
device is capable of receiving and/or transmitting one or parameters, performing
function/s, communicating with other user devices, and transmitting data to the
other user devices. The user equipment may have a processor, a display, a memory,
25 a battery, and an input-means such as a hard keypad and/or a soft keypad. The user
equipment may be capable of operating on any radio access technology including
but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low
Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For
instance, the user equipment may include, but not limited to, a mobile phone,
30 smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop,
12

a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
5 [0045] Further, the user device may also comprise a “processor” or “processing
unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a
10 DSP core, a controller, a microcontroller, Application Specific Integrated Circuits
(ASIC), Field Programmable Gate Array (FPGA) 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 the system according to the present disclosure. More specifically, the processor is
15 a hardware processor.
[0046] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of
20 technologies. In the field of wireless data communications, the dynamic
advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.
25
[0047] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each
30 RAT has its own set of protocols and standards for communication, which define
13

the frequency bands, modulation techniques, and other parameters used for
transmitting and receiving data. Examples of RATs include GSM (Global System
for Mobile Communications), CDMA (Code Division Multiple Access), UMTS
(Universal Mobile Telecommunications System), LTE (Long-Term Evolution),
5 and 5G. The choice of RAT depends on a variety of factors, including the network
infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.
10
[0048] Network Exposure Function (NEF): The NEF is a component within a telecommunications network architecture responsible for exposing and monetizing network capabilities and assets. It acts as an interface between network services and external applications, allowing third-party developers to access and utilize network
15 functionalities. NEF enables the creation of innovative services and business
models by providing secure and controlled access to network resources.
[0049] Application Function (AF): The AF refers to a component within a network
infrastructure that provides specific application services or functionalities. These
20 functions could include processing and managing data, facilitating communication
between users or devices, executing business logic, or delivering content or services to end-users. AFs are designed to support various applications and services running on the network, enhancing their performance, scalability, and reliability.
25 [0050] As discussed in the background section, the current known solutions for
availability of data to a Disaster Recovery (DR) Site to allow communication to run smoothly in case a Geo-Redundant (GR) Site is in a shut-down state or is not working properly have several shortcomings such as time-inefficiency that also hampers user experience and leads to delayed communication and inefficient
30 utilization of the resources.
14

[0051] The present disclosure aims to overcome the above-mentioned problems and other existing problems in this field of technology by providing a method and system for optimising availability of an updated data at a secondary site. 5
[0052] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0053] FIG. 1 illustrates an exemplary block diagram representation of 5th
10 generation core (5GC) network architecture, in accordance with exemplary
implementation of the present disclosure. As shown in FIG. 1, the 5GC network
architecture [100] includes a user equipment (UE) [102], a radio access network
(RAN) [104], an access and mobility management function (AMF) [106], a Session
Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
15 an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network 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
20 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 to
the person skilled in the art for implementing features of the present disclosure.
[0054] Radio Access Network (RAN) [104] is the part of a mobile
25 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). It consists of radio base stations and the radio access technologies that enable wireless communication.
15

[0055] Access and Mobility Management Function (AMF) [106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging. 5
[0056] Session Management Function (SMF) [108] is a 5G core network function 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.
10
[0057] Service Communication Proxy (SCP) [110] is a network function in the 5G 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.
15
[0058] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
20 [0059] Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
25 [0060] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
16

[0061] 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.
5 [0062] Network Repository Function (NRF) [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.
[0063] Policy Control Function (PCF) [122] is a network function responsible for
10 policy control decisions, such as QoS, charging, and access control, based on
subscriber information and network policies.
[0064] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication,
15 authorization, and subscription information.
[0065] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services. 20
[0066] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
25 [0067] 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.
17

[0068] Referring to FIG. 2, an architecture diagram of a system [200] for optimising availability of an updated data at a secondary site is shown, in accordance with the exemplary implementations of the present disclosure.
5 [0069] The Application Function (AF) sends operation/service request to the NEF
Cluster at Site 1 and Site 2 (depicted as arrow 1). The NEF Clusters process this
data and interact with their respective Persistence DB Clusters (depicted as arrow
2) for data storage. The NEF Auditors at both sites audit the operations within their
corresponding NEF Clusters (depicted as arrow 3). There is communication
10 between the NEF Auditors at both sites (depicted as arrow 4), which ensures
comprehensive auditing across both locations.
[0070] Referring to FIG. 3, an exemplary block diagram of a system [300] for optimising availability of an updated data at a secondary site is shown, in
15 accordance with the exemplary implementations of the present disclosure. The
system [300] comprises at least one transceiver unit [301], at least one identification unit [303], at least one analysis unit [305], and at least one storage unit [307]. Further, the auditor and NEF may be implemented as a single integrated unit or as separate units. Also, all of the components/ units of the system [300] are assumed
20 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 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
25 disclosure. Further, in an implementation, the system [300] may be present in a user
device to implement the features of the present disclosure.
[0071] The system [300] is configured for optimising availability of an updated
data at a secondary site, with the help of the interconnection between the
30 components/units of the system [300].
18

[0072] The system [300] for optimising availability of an updated data at a
secondary site, comprises the transceiver unit [301] at a Network Exposure
Function (NEF), wherein the transceiver unit [301] is configured to receive from an
5 Application Function (AF), a service request, wherein the service request is
associated with one or more database operation request. The transceiver unit [301] may be a device capable of both transmitting and receiving signals within the network and facilitating communication between different components wherein the service request is associated with one or more database operation request.
10
[0073] The identification unit [303] at the NEF, is connected to at least the transceiver unit [301], wherein the identification unit [303] is configured to identify at least one target database operation based on the one or more database operation request associated with the service request. The identification unit [303] may be
15 responsible for recognizing or identifying specific elements or patterns within the
incoming requests.
[0074] The one or more database operation request is at least one of a database create operation request, a database insert operation request, a database update
20 operation request, and a database delete operation request. In one example, the at
least one target database operation based on the one or more database operation request may be at least one of a database insert operation, a database update operation, and a database delete operation based on the database insert operation request, the database update operation request, and the database delete operation
25 request.
[0075] The analysis unit [305] connected to at least the identification unit [303], is configured to execute at a database cluster associated with the NEF, the at least one target database operation. The analysis unit [305], connected to at least the
19

identification unit [303], is set up to perform the specified database operations at a database cluster connected to the NEF.
[0076] The transceiver unit [301] is further configured to transmit, from the NEF
5 to an auditor associated with the NEF, the at least one target database operation
based on executing at the database cluster the at least one target database operation. The transceiver unit [301] is designed to send at least one specific database operation performed at the database cluster from the Network Exposure Function (NEF) to the auditor linked with the NEF. The transceiver unit [301] is further
10 configured to transmit, from the NEF via a cache associated with the NEF to the
auditor associated with the NEF, the at least one target database operation based on executing at the database cluster the at least one target database operation. The at least one target database operations are the specific database operations (create, update, insert, delete) identified and selected for execution based on a service
15 request.
[0077] The analysis unit [305] is further configured to facilitate, by at the NEF, a
replication of the at least one target database operation based on the transmission
of the at least one target database operation from the transceiver unit [301] of the
20 NEF to the auditor associated with the NEF. It is designed to help replicate these
operations at the NEF by using the data transmitted from the NEF's transceiver unit [302] to the associated auditor.
[0078] In the system [300], for the facilitation of the replication of the at least one
25 target database operation at the NEF, the auditor is configured to generate an output
data based on the at least one target database operation. Transmit, to the secondary
site associated with the NEF, the output data associated with the at least one target
database operation. To replicate the specified database operation at the NEF, the
auditor is programmed to generate output data based on the database operation.
30 Then, send the output data to the secondary site connected to the NEF.
20

[0079] The system [300], for the facilitation of the replication of the at least one
target database operation at the NEF, provides a disaster recovery auditor associated
with the secondary site, which is configured to generate a replicate data based on
5 the output data associated with the at least one target database operation; execute,
at a disaster recovery database cluster associated with the secondary site, the at least
one target database operation based on the replicate data. A disaster recovery
auditor at the secondary site creates a copy of the data. And perform the specified
database operation at a disaster recovery database cluster linked to the secondary
10 site based on the replicated data.
[0080] The auditor is further configured to transmit to the secondary site associated
with the NEF, the output data associated with the at least one target database
operation using one of a plurality of paths. The auditor is set up to send the data
15 resulting from the specified database operation to a secondary location connected
with the Network Exposure Function (NEF).
[0081] The analysis unit [305] is further configured to detect a failure status associated with at least one of the NEF and the secondary site associated with the
20 NEF based on one or more predefined rules and the transceiver unit [301] is further
configured to transmit at least a service traffic associated with the service request to at least one of the NEF and the secondary site associated with the NEF based on the failure status associated with at least one of the NEF and the disaster recovery site. The analysis unit [305] is further configured to synchronize, in real time, at
25 least the database cluster and the disaster recovery database cluster wherein the
secondary site may be the disaster recovery site. The analysis unit [305] is also set up to detect if either the NEF or the secondary site connected to the NEF experiences the failure, based on the one or more predefined rules. If the failure is detected, the transceiver unit [301] is designed to direct the service traffic related to
30 the service request to either the NEF or the secondary site, depending on the failure
21

status of each. These one or more predefined rules dictate the analysis unit [305] to
detects the failure statuses associated with the NEF or the secondary site.
Additionally, the analysis unit [305] may programme to ensure real-time
synchronization between the main database cluster and the disaster recovery
5 database cluster, where the secondary site serves as the disaster recovery location.
The storage unit [307] stores at least the data that may be required by one or more units of the system to perform their respective functions.
[0082] Referring to FIG. 4, an exemplary method flow diagram [400] for
10 optimising availability of an updated data at a secondary site in accordance with
exemplary implementations of the present 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]
15 starts at step [402].
[0083] At step 404, the method comprises receiving, by a transceiver unit [301] at
a Network Exposure Function (NEF) from an Application Function (AF), a service
request, wherein the service request is associated with one or more database
20 operation request. The transceiver unit [301] may be a device capable of both
transmitting and receiving signals within the network and facilitating communication between different components wherein the service request is associated with one or more database operation request.
25 [0084] At step 406, the method comprises, an identification unit [303] at the NEF,
the identification unit [303] connected to at least the transceiver unit [301], the identification unit [303] is configured to identify at least one target database operation based on the one or more database operation request associated with the service request. The identification unit [303] may be responsible for recognizing or
30 identifying specific elements or patterns within the incoming requests.
22

[0085] The one or more database operation request is at least one of a database
create operation request, a database insert operation request, a database update
operation request, and a database delete operation request, and wherein the at least
5 one target database operation based on the one or more database operation request
may be at least one of a database insert operation, a database update operation, and a database delete operation based on the database insert operation request, the database update operation request, and the database delete operation request.
10 [0086] At step 408, the method comprises, an analysis unit [305] connected to at
least the identification unit [303], the analysis unit [305] configured to execute at a database cluster associated with the NEF, the at least one target database operation. The analysis unit [305], which is linked to at least the identification unit [303], is set up to perform the specified database operations at a database cluster connected
15 to the NEF.
[0087] At step 410, the transceiver unit [301] is further configured to transmit, from the NEF to an auditor associated with the NEF, the at least one target database operation based on executing at the database cluster the at least one target database
20 operation. The transceiver unit [301] is designed to send at least one specific
database operation performed at the database cluster from the Network Exposure Function (NEF) to the auditor linked with the NEF. The method further comprises transmitting, by the transceiver unit [301] from the NEF via a cache associated with the NEF to the auditor associated with the NEF, the at least one target database
25 operation based on executing at the database cluster the at least one target database
operation. The transceiver unit [301] is also designed to send at least one database operation from the NEF through a cache connected to the NEF to the auditor associated with the NEF. The at least one target database operations are the specific database operations (create, update, insert, delete) identified and selected for
30 execution based on a service request.
23

[0088] The method comprises, transmitting, from the auditor associated with the
NEF to the secondary site associated with the NEF, the output data associated with
the at least one target database operation is performed using one of a plurality of
5 paths. The auditor generates the output data based on the received database
operation. The auditor transmits the output data to the auditor at the secondary site. The auditor at the secondary site replicates the database operation using the received output data in the secondary site’s persistence DB cluster. It can do this using various available pathways.
10
[0089] When the auditor transmits the output data associated with the at least one target database operation, using a first path, the data is received at a second receiver associated with the secondary site from a first sender associated with a primary site wherein the secondary site is disaster recovery site. When the auditor sends the data
15 resulting from the specified database operation using the first route, it is received
by a receiver at the secondary site from a sender at the primary site. The secondary site serves as a disaster recovery location. The first sender, responsible for initiating data transfer from the primary site, can be part of the NEF or the auditor associated with the NEF. When the auditor transmits the output data associated with the at
20 least one target database operation, using a second path, the data is received at the
second receiver associated with the secondary site from the first sender associated with the primary site via a third proxy deployed at a tertiary site in an event of failure of direct connectivity between the first sender and the second receiver. If the auditor sends the data resulting from the specified database operation using a
25 different route (the second path), it is received by a receiver at the secondary site
from a sender at the primary site through the third proxy deployed at a separate location (the tertiary site). This happens when there is a problem with the direct connection between the sender and receiver. The second receiver, responsible for receiving data at the secondary site, can be part of the auditor associated with the
30 NEF or the NEF itself.
24

[0090] When the auditor transmits the output data associated with the at least one
target database operation, using a third path, the data is received at a second proxy
associated with the secondary site from the first sender associated with the primary
5 site via the third proxy deployed at a tertiary site during downtime of the receiver
associated with the secondary site. If the auditor sends the data resulting from the
specified database operation using another route (the third path), it is received by
an intermediary at the secondary site from a sender at the primary site through third
proxy deployed at a separate location (the tertiary site). This occurs when the
10 receiver at the secondary site is not operational.
[0091] When the auditor transmits the output data associated with the at least one target database operation, using a fourth path, the data is received at a second proxy associated with the secondary site from the first sender associated with the primary
15 site during downtime of the second receiver associated with the secondary site and
the third proxy associated with a tertiary site. If the auditor sends the data resulting from the specified database operation using yet another route (the fourth path), it is received by an intermediary at the secondary site from a sender at the primary site. This happens when both the receiver at the secondary site and the intermediary at
20 the tertiary site are not operational.
[0092] At step 412, the method comprises, facilitating, by the analysis unit [305] at
the NEF, a replication of the at least one target database operation based on the
transmission of the at least one target database operation from the transceiver unit
25 [301] of the NEF to the auditor associated with the NEF. It is designed to help
replicate these operations at the NEF by using the data transmitted from the NEF's transceiver unit [301] to the associated auditor.
[0093] To replicate the specified database operation at the NEF, the output data is
30 sent to the secondary site connected to the NEF. A disaster recovery auditor at the
25

secondary site creates a copy of the data and performs the specified database operation at a disaster recovery database cluster linked to the secondary site based on the replicated data.
5 [0094] The method further comprising detecting, by the analysis unit [305], a
failure status associated with at least one of the NEF and the secondary site associated with the NEF based on one or more predefined rule and transmitting, by the transceiver unit [301], at least a service traffic associated with the service request to at least one of the NEF and the secondary site associated with the NEF
10 based on the failure status associated with at least one of the NEF and the secondary
site. The method further comprising synchronizing, by the analysis unit [305], in real time, at least the database cluster and the disaster recovery database cluster. The analysis unit [305] is also set up to detect if either the NEF or the secondary site connected to the NEF experiences a failure, based on the one or more
15 predefined rules. If the failure is detected, the transceiver unit [301] is designed to
direct the service traffic related to the service request to either the NEF or the secondary site, depending on the failure status of each. These one or more predefined rules dictate the analysis unit [305] to detect the failure statuses associated with the NEF or the secondary site. Additionally, the analysis unit [305]
20 may programme to ensure real-time synchronization between the main database
cluster and the disaster recovery database cluster, where the secondary site serves as the disaster recovery location.
[0095] Thereafter, the method terminates at step (414).
25
[0096] Referring to FIG. 5 an exemplary scenario flow diagram [500] for optimising availability of an updated data at a secondary site, in accordance with exemplary embodiments of the present invention is shown. In an implementation, the flow [300] is performed by the system [300] as depicted in FIG. 3.
30
26

[0097] Here, Site 2 creates sessions at the NEF Cluster Site at Site 2 regarding
addition, modification, deletion of UEs. The data regarding the same is stored in
cache and also shared to a Persistence Database (DB) Cluster (like monitoring type
(location reporting), SUPI, maximum Number of Reports). This data is shared via
5 an NEF Auditor at Site 2 to the NEF Auditor at Site 1. The NEF Auditor at Site 1
instructs the NEF Cluster Site at Site 1 to modify a Persistence DB Cluster at Site
1. In this case, the NEF Cluster Site at Site 2 acts as the GR Site and NEF Cluster
Site at Site 1 acts as the DR Site. In case of a complete failure at GR Site, the data
saved in the Persistence DB Cluster at DR Site is used to fetch necessary details
10 and allow the communication to be done seamlessly.
[0098] The NEF Cluster at Site 1 can exchange the data to the NEF Cluster at Site
2 via a NEF Cluster at Site 3. This process is utilized if the NEF Auditor at Site 1
is unable to do a direct communication with the NEF Auditor at Site 2. In order to
15 achieve this, there are 4 paths to share the data from the NEF Auditor at Site 1 to
the NEF Auditor at Site 2:
Path 1: Sender instance (Sen-1) sends data to receiver instance (Rec-2) to replicate
data in the secondary Site Persistence DB.
The sender instances, responsible for initiating data transfer from the primary site,
20 can be part of the NEF or the auditor associated with the NEF.
The receiver instances, responsible for receiving data at the secondary site, can be
part of the auditor associated with the NEF or the NEF itself.
Path 2: Sender (Sen-1) forwards data to intermediate proxy (Proxy-3) deployed at
Site-3, which in turn, sends data to receiver (Rec-2). This path will be used when
25 there is no connectivity between sender (Sen-1) & receiver (Rec-2).
Path 3: Sender (Sen-1) forwards data to intermediate proxy (Proxy-3) deployed at
Site-3, which in turn, sends data to Proxy (Proxy-2) of Site-2. This path will be
used when receiver (Rec-2) is down.
Path 4: Sender (Sen-1) sends data to Proxy (Proxy-2) of Site-2. This path will be
30 used when receiver (Rec-2) & intermediate proxy (Proxy-3) are down.
27

[0099] Following are the functions of the Proxy, which ensures robust and continuous data replication in case of connectivity issues or failures:
- Acts as a backup node for sender when sender goes down: When the primary
sender (Sen1) fails, the Proxy steps in to ensure data transmission continues
5 without interruption.
- Acts as a backup node for receiver when receiver goes down: Similarly, if
the receiver (Rec2) at the primary site is unavailable, the Proxy can receive
and store the data until the receiver is back online.
- Acts as an Intermediate Proxy when there is no connectivity between sender
10 & receiver: The Proxy serves as an intermediary node to facilitate
communication between the sender and receiver when direct connectivity is lost, ensuring the data replication process continues seamlessly.
- Keeps data in cache in case of failure and performs cache data
resynchronization at scheduled time: In case of failure, the Proxy caches the
15 data and later resynchronizes it with the intended receiver or database
cluster at a scheduled time, maintaining data consistency and reliability.
[0100] Referring to FIG. 6, an exemplary scenario flow diagram [600] for optimising availability of an updated data at a secondary site, in accordance with
20 exemplary embodiments of the present invention is shown. In an implementation
the flow [400] is performed by the system [300] as depicted in FIG. 1 and method [400] as depicted in FIG. 4. The NEF Cluster at Site 2 can exchange the data with the NEF Cluster at Site 1 via a NEF Cluster at Site 4. This process is utilized if the NEF Auditor at Site 2 is unable to do a direct communication with the NEF Auditor
25 at Site 1. In order to achieve this, there are 4 paths to share the data from the NEF
Auditor at Site 2 to the NEF Auditor at Site 1:
Path 1: Sender instance (Sen-2) sends data to receiver instance (Rec-1) to replicate data in the secondary Site Persistence DB.
28

Path 2: Sender (Sen-2) forwards data to intermediate proxy (Proxy-4) deployed at Site-3, which in turn, sends data to receiver (Rec-1). This path will be used when there is no connectivity between sender (Sen-2) & receiver (Rec-1).
Path 3: Sender (Sen-2) forwards data to intermediate proxy (Proxy-4) deployed at
5 Site-4, which in turn, sends data to Proxy (Proxy-1) of Site-1. This path will be
used when receiver (Rec-1) is down.
Path 4: Sender (Sen-2) sends data to Proxy (Proxy-1) of Site-1. This path will be used when receiver (Rec-1) & intermediate proxy (Proxy-4) are down.
10 [0101] Referring to FIG. 7, an exemplary method flow diagram [700], for
availability of data into the Disaster Recovery (DR) Site i.e., optimising availability of an updated data at a secondary site, in accordance with exemplary embodiments of the present invention is shown. In an implementation the method [700] is performed by the system [300]. Also, as shown in FIG. 7, the method [700] starts
15 at step [702].
[0102] At step [704], the method [700] is shown as disclosed by the present disclosure, instructing client/AF to share an update Database Request to the NEF Cluster at Site 1, In an implementation of the present disclosure, the method
20 instructs the client or Application Function (AF) to send the update database request
to the Network Exposure Function (NEF) Cluster located at Site 1. The purpose of this request is to execute the database update operation, which involves modifying data in the Persistence Database to ensure it reflects the most recent changes or updates.
25
[0103] At step [706], the method [700] is shown as disclosed by the present disclosure, instructing the NEF Cluster at Site 1 to share the DB operation performed, from its local cache to NEF Auditor at Site 1 which is deployed in the same site. In an implementation of the present disclosure, for the execution of the
30 database operation at Site 1, the method instructs the NEF Cluster at Site 1 to share
29

information about the performed database operation. This information is transmitted from the local cache of the NEF Cluster to the NEF Auditor, which is also located at Site 1. The NEF Auditor is responsible for monitoring and recording database operations for auditing purposes. 5
[0104] At step [708], the method [700] shown as disclosed by the present disclosure, performs sharing the data from the NEF Auditor at Site 1 to the NEF Auditor at Site 2 to replicate the data in the Persistence DB at Site 2, and keeping the Persistence DB at Site 2 in synchronization with the data in the Persistence DB
10 at Site 1. In an implementation of the present disclosure, the data regarding the
performed database operation is transmitted from the NEF Auditor at Site 1 to the NEF Auditor at Site 2. The purpose of this transmission is to replicate the data in the Persistence DB at Site 2, ensuring that the data at the secondary site remains synchronized with the data at the primary site (Site 1). This synchronization is
15 crucial for maintaining data consistency and ensuring availability in the event of a
disaster or failure at the primary site.
[0105] Thereafter, the method terminates at step (710).
20 [0106] FIG. 8 illustrates an exemplary block diagram of a computing device [800]
upon which an embodiment of the present disclosure may be implemented. In an implementation, the computing device [800] implements the method [400] for optimising availability of an updated data at a disaster recovery site utilizing the system [300]. In another implementation, the computing device [800] itself
25 implements the method [400] for managing one or more supplementary services in
a multi-network environment using one or more units configured within the computing device [800], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
30

[0107] The computing device [800] may include a bus [802] or other
communication mechanism for communicating information, and a hardware
processor [804] coupled with bus [802] for processing information. The hardware
processor [804] may be, for example, a general-purpose microprocessor. The
5 computing device [800] may also include a main memory [806], such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus [802] for storing information and instructions to be executed by the processor [804]. The main memory [806] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the
10 processor [804]. Such instructions, when stored in non-transitory storage media
accessible to the processor [804], render the computing device [800] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [800] further includes a read only memory (ROM) [808] or other static storage device coupled to the bus [802] for storing static
15 information and instructions for the processor [804].
[0108] A storage device [810], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [802] for storing information and instructions. The computing device [800] may be coupled via the bus [802] to a
20 display [812], such as a cathode ray tube (CRT), for displaying information to a
computer user. An input device [814], including alphanumeric and other keys, may be coupled to the bus [802] for communicating information and command selections to the processor [804]. Another type of user input device may be a cursor controller [816], such as a mouse, a trackball, or cursor direction keys, for
25 communicating direction information and command selections to the processor
[804], and for controlling cursor movement on the display [812]. 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.
31

[0109] The computing device [800] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware,
and/or program logic which in combination with the computing device [800] causes
or programs the computing device [800] to be a special-purpose machine.
5 According to one embodiment, the techniques herein are performed by the
computing device [800] in response to the processor [804] executing one or more
sequences of one or more instructions contained in the main memory [806]. Such
instructions may be read into the main memory [806] from another storage medium,
such as the storage device [810]. Execution of the sequences of instructions
10 contained in the main memory [806] causes the processor [804] to perform the
process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
[0110] The computing device [800] also may include a communication interface
15 [828] coupled to the bus [802]. The communication interface [828] provides a two-
way data communication coupling to a network link [820] that is connected to a
local network [822]. For example, the communication interface [828] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
20 telephone line. As another example, the communication interface [828] 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 [828] sends and receives electrical,
electromagnetic, or optical signals that carry digital data streams representing
25 various types of information.
[0111] The computing device [800] can send messages and receive data, including
program code, through the network(s), the network link [820] and the
communication interface [828]. In the Internet example, a server [830] might
30 transmit a requested code for an application program through the Internet [828], the
32

ISP [826], the host [824], the local network [822], and the communication interface [828]. The received code may be executed by the processor [804] as it is received, and/or stored in the storage device [810], or other non-volatile storage for later execution. 5
[0112] Further, an aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instruction for optimising availability of an updated data at a secondary site. The instructions when executed by one or more units of a system, causes: a transceiver unit [301] of the system to receive at a
10 Network Exposure Function (NEF), from an Application Function (AF), a service request, wherein the service request is associated with one or more database operation request; an identification unit [303] of the system to identify at the NEF at least one target database operation based on the one or more database operation request associated with the service request; an analysis unit [305] of the system to
15 execute at a database cluster associated with the NEF, the at least one target database operation; the transceiver unit [301] of the system to transmit, from the NEF to an auditor associated with the NEF, the at least one target database operation based on executing at the database cluster the at least one target database operation, and the analysis unit [305] of the system to facilitate, by at the NEF, a replication
20 of the at least one target database operation based on the transmission of the at least one target database operation from the transceiver unit [301] of the NEF to the auditor associated with the NEF.
[0113] As is evident from the above, the present disclosure provides a technically 25 advanced solution for availability of data into a Disaster Recovery (DR) Site to
allow communication to run smoothly in case a Geo-Redundant (GR) Site is in a
shut-down state or is not working properly. Various advantages of the present
disclosure involve:
• time-efficient transfer of data between two NEF Cluster Sites;
30 • Enhanced user experience;
33

• Time-efficient communication.
• Optimal and efficient utilization of the resources.
[0114] While considerable emphasis has been placed herein on the disclosed 5 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 be understood that the foregoing descriptive matter to be implemented is illustrative 10 and non-limiting.
[0115] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a
15 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 as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended
20 functionality described herein, are considered to be encompassed within the scope of the present disclosure.
34

We Claim:
1. A method for optimising availability of an updated data at a secondary site,
the method comprising:
- receiving, by a transceiver unit [301] at a Network Exposure Function
5 (NEF), from an Application Function (AF), a service request, wherein the
service request is associated with one or more database operation request;
- identifying, by an identification unit [303] at the NEF, at least one target
database operation based on the one or more database operation request
associated with the service request;
10 - executing, by an analysis unit [305] at a database cluster associated with the
NEF, the at least one target database operation;
- transmitting, by the transceiver unit [301] from the NEF to an auditor
associated with the NEF, the at least one target database operation based on
executing at the database cluster the at least one target database operation;
15 and
- facilitating, by the analysis unit [305] at the NEF, a replication of the at least
one target database operation based on the transmission of the at least one
target database operation from the transceiver unit [301] of the NEF to the
auditor associated with the NEF.
20
2. The method as claimed in claim 1 wherein the facilitating, by the analysis
unit [305] at the NEF, the replication of the at least one target database
operation comprises:
- generating, by the auditor, an output data based on the at least one target
25 database operation;
- transmitting, from the auditor associated with the NEF to the secondary site
associated with the NEF, the output data associated with the at least one
target database operation;
35

- generating, by an auditor associated with the secondary site, a replicate data
based on the output data associated with the at least one target database
operation; and
- executing, by the auditor at a database cluster associated with the secondary
5 site, the at least one target database operation based on the replicate data.
3. The method as claimed in claim 2, wherein transmitting, from the auditor
associated with the NEF to the secondary site associated with the NEF, the
output data associated with the at least one target database operation is
10 performed using one of a plurality of paths.
4. The method as claimed in claim 3, wherein using a first path of the plurality
of paths, the data is received at a second receiver associated with the
secondary site from a first sender associated with a primary site.
15
5. The method as claimed in claim 3, wherein using a second path of the
plurality of paths, the data is received at a second receiver associated with
the secondary site from a first sender associated with the primary site via a
third proxy deployed at a tertiary site in an event of failure of direct
20 connectivity between the first sender and the second receiver.
6. The method as claimed in claim 3, wherein using a third path of the plurality
of paths, the data is received at a second proxy associated with the secondary
site from a first sender associated with the primary site via a third proxy
25 deployed at a tertiary site during downtime of a receiver associated with the
secondary site.
7. The method as claimed in claim 3, wherein using a fourth path of the
plurality of paths, the data is received at a second proxy associated with the
30 secondary site from a first sender associated with the primary site during
36

downtime of a second receiver associated with the secondary site and a third proxy associated with a tertiary site.
5 8. The method as claimed in claim 1, the method further comprises
transmitting, by the transceiver unit [301] from the NEF via a cache associated with the NEF to the auditor associated with the NEF, the at least one target database operation based on executing at the database cluster the at least one target database operation. 10
9. The method as claimed in claim 1, wherein the one or more database
operation request is at least one of a database create operation request,
database insert operation request, a database update operation request, and
a database delete operation request.
15
10. The method as claimed in claim 1, the method further comprises:
- detecting, by the analysis unit [305], a failure status associated with at least
one of the NEF and the secondary site associated with the NEF based on
20 one or more predefined rules; and
- transmitting, by the transceiver unit [301], at least a service traffic
associated with the service request to at least one of the NEF and the
secondary site associated with the NEF based on the failure status associated
with at least one of the NEF and the secondary site.
25
11. The method as claimed in claim 1, the method further comprising:
synchronizing, by the analysis unit [305], in real time, at least the database
cluster and a disaster recovery database cluster.
37

12. The method as claimed in claim 1, wherein the secondary site is a disaster
recovery site.
13. A system for optimising availability of an updated data at a secondary site,
5 the system comprising:
- a transceiver unit [301] at a Network Exposure Function (NEF), configured
to receive from an Application Function (AF), a service request, wherein
the service request is associated with one or more database operation
request;
10 - an identification unit [303], the identification unit [303] connected to at least
the transceiver unit [301], the identification unit [303] configured to identify, at a Network Exposure Function (NEF) at least one target database operation based on the one or more database operation request associated with the service request; and
15 - an analysis unit [305] connected to at least the identification unit [303], the
analysis unit [305] configured to execute at a database cluster associated with the NEF, the at least one target database operation;
wherein the transceiver unit [301] is further configured to transmit, from the NEF to an auditor associated with the NEF, the at least one target database
20 operation based on executing at the database cluster the at least one target
database operation, and
wherein the analysis unit [305] is further configured to facilitate, at the NEF, a replication of the at least one target database operation based on the transmission of the at least one target database operation from the
25 transceiver unit [301] of the NEF to the auditor associated with the NEF.
14. The system as claimed in claim 13, wherein for the facilitation of the
replication of the at least one target database operation at the NEF:
- the auditor is configured to:

o generate an output data based on the at least one target database
operation, and
o transmit, to the secondary site associated with the NEF, the output
data associated with the at least one target database operation;
5 - a disaster recovery auditor associated with the secondary site is configured
to
o generate a replicate data based on the output data associated with the
at least one target database operation, and
o execute, at a disaster recovery database cluster associated with the
10 secondary site, the at least one target database operation based on
the replicate data.
15. The system as claimed in claim 14, wherein the auditor is configured to
transmit, to the secondary site associated with the NEF, the output data
15 associated with the at least one target database operation using one of a
plurality of paths.
16. The system as claimed in claim 15, wherein using a first path of the plurality
of paths, the data is received at a second receiver associated with the
20 secondary site from a first sender associated with a primary site.
17. The system as claimed in claim 15, wherein using a second path of the
plurality of paths, the data is received at a second receiver associated with
25 the secondary site from a first sender associated with the primary site via a
third proxy deployed at a tertiary site in an event of failure of direct connectivity between a first sender and the second receiver.
18. The system as claimed in claim 15, wherein using a third path of the
30 plurality of paths, the data is received at a second proxy associated with the

secondary site from a first sender associated with the primary site via a third proxy deployed at a tertiary site during downtime of the receiver associated with the secondary site.
5 19. The system as claimed in claim 15, wherein using a fourth path of the
plurality of paths, the data is received at a second proxy associated with the secondary site from a first sender associated with the primary site during downtime of a second receiver associated with the secondary site and a third proxy associated with a tertiary site. 10
20. The system as claimed in claim 13, wherein the transceiver unit [301] is
further configured to transmit, from the NEF via a cache associated with the
NEF to the auditor associated with the NEF, the at least one target database
operation based on executing at the database cluster the at least one target
15 database operation.
21. The system as claimed in claim 13, wherein the one or more database
operation request is at least one of a database insert operation request, a
database update operation request, and a database delete operation request.
20
22. The system as claimed in claim 13, wherein:
- the analysis unit [305] is further configured to detect a failure status
associated with at least one of the NEF and the secondary site associated
with the NEF based on one or more predefined rules; and
25 - the transceiver unit [301] is further configured to transmit at least a service
traffic associated with the service request to at least one of the NEF and the secondary site associated with the NEF based on the failure status associated with at least one of the NEF and the disaster recovery site.

23. The system as claimed in claim 13, wherein the analysis unit [305] is further configured to synchronize, in real time, at least the database cluster and a disaster recovery database cluster.
24. The system as claimed in claim 13, wherein the secondary site is disaster
recovery site.