Abstract: ABSTRACT METHOD AND SYSTEM FOR PROVIDING DATA BACK UP DURING LACK OF CONNECTIVITY The present disclosure relates to a system (108) and a method (400) for providing data back up during lack of connectivity. The system (108) includes a transceiver (220) to receive the data from Network Functions (NFs) and transmit the data to a probing system (210). In one embodiment, the probing system (210) includes at least one or more components in communication with each other. The system (108) includes a monitoring module (225) to monitor the communication interface to check for a failure in connectivity between the one or more components and pause the transfer of data between the at least one or more components. Further, the system (108) includes a storing module (230) to store the data received from the one or more NFs in a database (212) in response to pausing of the transfer of data. Ref. Fig. 2
DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR PROVIDING DATA BACK UP DURING LACK OF CONNECTIVITY
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION
THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.
FIELD OF THE INVENTION
[0001] The present invention generally relates to wireless networks, and more particularly relates to a system for providing data back up during lack of connectivity.
BACKGROUND OF THE INVENTION
[0002] In a wireless communication network such as a 5G network, there are many Network Functions (NFs). Further, there are hundreds of network instances for each NF. In conventional technologies, probing system is the front end node that interacts directly with the network function (NF). So once the NF sends data to the probing system, it does not store the data for backup purpose at network functions end. So once the data enters into the probing system, it fires and forgets the data. Thus, the data that is being communicated between the NF and the probing system is lost. Once the data is transferred between the NF and the probing system, the data is then deleted from the NF. Once an acknowledgment of receiving the data is sent, then the NF forgets the data and no backup is maintained.
[0003] Therefore, there is a need for a method wherein once that data enters into the system is made available and data backup should be maintained. Further, there is a requirement of a system that ensures the storage of the data once it is received from the NF.
SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a system and method of providing data back up during lack of connectivity.
[0005] In one aspect of the present invention a system for providing data back up during lack of connectivity is disclosed. The system includes a transceiver. The transceiver is configured to receive data from one or more network functions (NFs) and transmit the received data to a probing system. The probing system includes at least one or more components in communication with each other via communication interface to process the received data. The system includes a monitoring module. The monitoring module is configured to monitor the communication interface to check for a failure in connectivity between the one or more components of the probing system and further, pause the transfer of data between the at least one or more components. The system includes a storing module. The storing module is configured to store the data received from the one or more NFs in a database in response to pausing of the transfer of data.
[0006] In one embodiment, the monitoring module is configured to determine the availability of the one or more components to resume the transfer of data and further, resume the transfer of data received from the one or more NFs and the data stored in the database. In one embodiment, the monitoring module is configured to pause the transfer of data between the at least one or more components via one of a Machine Learning (ML) unit and a user interface unit.
[0007] In one embodiment, the ML unit receives inputs such as connectivity status of the communication interface and status of the interface to one of pause and resume the transfer of data between the at least one or more components.
[0008] In one embodiment, the one or more components include at least one of, a ML probe, a conductor, an indexer, a computation engine, a correlation engine, and a normalizer.
[0009] In one embodiment, the subscriber data includes data pertaining to Streaming Data Records (SDRs).
[0010] In one embodiment, the probing system accepts the subscriber data traffic pertaining to the SDR traffic with an auto pause feature and prevents the probing system to forward the SDR traffic to the one or more components.
[0011] In one embodiment, subsequent to resuming transfer of data received from the one or more NFs, the probing system transmits Application Data Records (ADRs) between the one or more components.
[0012] In another aspect of the present invention, a method of providing data back up during lack of connectivity is disclosed. The method includes the step of receiving the data from one or more network functions (NFs). The method includes the step of transmitting the received data to a probing system. Further, the probing system includes at least one or more components, in communication with each other via a communication interface to process the received data. The method includes the step of monitoring the communication interface to check for a failure in connectivity between the one or more components of the probing system. The method includes the step of pausing the transfer of data between the at least one or more components. Further, the method includes the step of storing the data received from the one or more NFs in a database in response to pausing of the transfer of data.
[0013] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings.
[0014] The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015] 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. 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 implement such components.
[0016] FIG. 1 is an exemplary block diagram of an environment for providing data back up during lack of connectivity, according to various embodiments of the present invention.
[0017] FIG. 2 is an exemplary block diagram of a system for providing data back up during lack of connectivity, according to various embodiments of the present system.
[0018] FIG. 3 is an exemplary block diagram of a system architectural diagram for providing pause/resume and auto/manual functionality in 5G probing system, according to various embodiments of the present invention.
[0019] FIG. 4 shows a flow diagram of a method for providing data back up during lack of connectivity, according to various embodiments of the present system.
[0020] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0021] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0022] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0023] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0024] As per various embodiments depicted, the present disclosure relates to a method and system for providing pause/resume and auto/manual functionality in 5G probing system. The method supports automatic/manual pause and resume functionality for operational purpose. Thus, this method ensures zero data loss in various scenarios such as connectivity failure with data or other components. In an embodiment of the present disclosure, the method facilitates in data protection in multiple scenarios such as network scenario, any server failure, hardware failure, OS failure, any hard disk failure. Further, the method facilitates in always maintaining the data back up during lack of connectivity between network entities. The unique feature of the present disclosure is that the data loss is avoided.
[0025] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for providing data back up during lack of connectivity, according to various embodiments of the present invention. In one embodiment, the network entities 101 is one of, but not limited to, a base station. The environment 100 includes one or more user devices 102-1, 102-2,…,102-n. At least one of the user device 102-1 from the one or more user devices 102-1, 102-2,…102-n is communicatively connected to a system 108 via a network 106. The one or more user devices 102-1, 102-2,…102-n will henceforth collectively and individually be referred to as “the user device 102” without limiting the scope and deviating from the scope of the present disclosure. In one embodiment, the user device 102 is one of, but not limited to, a user equipment (UE), a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication or VoIP capabilities.
[0026] In one embodiment, the user device 102 may comprise one or more processors coupled with a memory storing instructions, which are executed by the one or more processors. The user device 102 may comprise memory, such as a volatile memory (e.g., RAM), a non-volatile memory (e.g., disk memory, FLASH memory, EPROMs, etc.), an unalterable memory, and/or other types of memory. In one implementation, the memory might be configured or designed to store a data. The data may pertain to attributes and access rights specifically defined for at least one of the user devices 102.
[0027] In one embodiment, the network 106, includes, by way of example but not limitation, one or more wireless interfaces/protocols such as, for example, 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (Wi-Max), 802.22, Cellular standards such as CDMA, CDMA2000, WCDMA, 5G, Radio Frequency (e.g., RFID), Infrared, laser, Near Field Magnetics, etc. The network 106 also includes, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 also includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0028] The environment 100 further includes a remote server 104 communicably coupled to the user device 102 via the network 106. In one embodiment, the remote server 104 includes, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise, a defence facility, or any other facility that provides content.
[0029] The environment 100 further includes the system 108 communicably coupled to the remote server 104 and the user device 102 via the network 106. The system 108 is configured to provide data back up during lack of connectivity. Further, in alternate embodiments, the system 108 is adapted to be embedded within the remote server 104 or is embedded as an individual entity, without deviating from the scope of the present disclosure.
[0030] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0031] Referring to FIG. 2, FIG. 2 illustrates an exemplary block diagram of a system 108 for providing data back up during lack of connectivity, according to various embodiments of the present system. As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, an input/output interface unit 206, a display 208, a database 212, a probing system 210 and a Machine Learning (ML) unit 235. The one or more processors 202, hereinafter referred to as the processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. The processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204 of the system 108.
[0032] The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over the network 106. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as Electrically Erasable Programmable Read-only Memory (EPROM), flash memory, and the like. In an embodiment, the input/output interface unit 206 includes a variety of interfaces, for example, interfaces for data input and output devices, referred to as input/output interface unit 206, storage devices, and the like. The input/output interface unit 206 may facilitates communication for the system 108. In one embodiment, the input/output interface unit 206 may also provide a communication pathway for one or more components of the system 108.
[0033] Further, the processor 202, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 202 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor 202. In such examples, the system 102 comprises the memory 204 for storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0034] The probing system 210 includes one or more components such as a probe 214, a conductor unit 216 and a normalizer 218. In an alternate embodiment, the probing system 210 also includes the one or more components such as an indexer, a computation engine, and a correlation engine. In one embodiment, the probe 214 process the received Streaming Data Records (SDRs) data from the probing system 210. The SDRs can be a transaction or procedure in 5G or a call flow in 4G network. In one embodiment, the SDR can also be a Call Detail Records (CDR) written in network nodes or a debugging record and can be logs. In one embodiment, probe 214 may include a ML model. The probe 214 utilizes the ML techniques to analyse and process the SDR data received from the one or more NFs. In one embodiment, the probe 214 reduces the false positives and enhances decision-making certainty based on the processed data. In one embodiment, for example, the ML techniques include at least one of, but not be limited to, a Supervised Learning (SL), a Support Vector Machine (SVM), a K-Nearest Neighbours (KNN), a Support Vector Regression (SVR) and a Gaussian Process Regression (DPR) algorithm. The probe 214 sends the processed SDR data to the conductor unit 216 for further processing the data. Then the conductor unit 216 transmits the processed data to the Normalizer 218. Further, the normalizer 218 receives the processed SDR data from the conductor unit 216 to perform the data normalization.
[0035] In an alternate embodiment, an ML model is deployed separately without limiting the scope of the present invention. The ML model is communicably coupled to the probe 214. In one embodiment the probe 214 the ML probe can be used in combination or interchangeably. In one embodiment, the probe 214 uses a Machine learning as a service (MLaaS). The MLaaS is a range of services that offer machine-learning tools as part of cloud computing services.
[0036] In one embodiment, the probe 214 is a component that monitors and analyses network activity and may also perform prevention actions. The probe 214 acts as a messenger, delivering queries to network devices such as one or more NFs and retrieving data to be analysed from the one or more NFs. In particular, probe 214 collects the data from NFs, and stream the data in real-time to other components of probing system 210. The data collected by the probe 214 is based on preconfigured policies such as request parameters which includes at least one of, but not limited to, an alias name, a call flow name, and a version for each of the NF among the one or more NFs. In one embodiment, the probe 214 is embedded in the one or more NFs of 5G or 4G core network. This allows probe 214 to geographically distribute Virtualized Network Functions (VNFs)/Cloud Native Functions (CNFs).
[0037] In one embodiment, the conductor unit 216 of the probing system 210 is a customized decoder which deciphers and ingests processed data based on policy before feeding it to other components of the probing system 210. Further, the conductors perform primary operations on the incoming data. The primary operations include at least one of, but not limited to, sorting the data, filtering certain configured attributes which are not required for analysis, splitting the data, etc, based on configured policy request parameters.
[0038] In one embodiment, the normalizer 218 of the probing system 210 normalizes the decoded data based on one or more preconfigured policies or rules. In particular, the normalizer 218 processes the data which includes at least one of, but not limited to, reorganizing the data, removing the irrelevant data, formatting the data and removing null values from the data. The main goal of the normalizer 218 is to achieve a standardized data format across the entire system 108. The normalizer ensures that the normalized data is stored appropriately in at least one of, the storage module 230 and the database 212.
[0039] In one embodiment, the indexer of the probing system 210, identifies the location of resources based on file names, key data fields in in at least one of, the storage module 230 and the database 212, text within a file or unique attributes in a graphics or video file. In particular, the indexer creates an index, which is a methodical arrangement of records designed to enable users to locate information quickly.
[0040] In one embodiment, the computation engine of the probing system 210, is a functional unit that performs substantial computations, including numerous arithmetic operations and logic operations without human intervention. In particular, the computation engine performs computation such as any type of arithmetic or non-arithmetic calculation that is well-defined. For example, computation is mathematical equation solving and the execution of computer logics.
[0041] In one embodiment, the correlation engine of the probing system 210, is an analytics tool that uses the logs to detect events on the network 106. For example, the correlation engine uses learning models and machine learning logics to correlate alarms with clear codes or infrastructure events received from other systems.
[0042] In one embodiment, the one or more NFs are communicably coupled to the server 104 via the network 106. The Network Function (NF) is a functional building block within a network infrastructure or the network 106, which has well-defined external interfaces and a well-defined functional behaviour. In particular, a NF is often a network node or a physical appliance. For example, the one or more NFs includes at least one of, but not limited to, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), and a Policy Control Function (PCF).
[0043] In order for the system 108 to operate as data back up during lack of connectivity in the network 106, the processor 202 of the system 108 includes a transceiver 220, a monitoring module 225 and a storing module 230 communicably coupled to each other.
[0044] The transceiver 220 of the processor 202 is communicably connected to the user device 102 and the remote server 104 via the network 106. Accordingly, the transceiver 220 is configured to receive data from one or more network functions (NFs) and transmits the received subscriber data to the probing system 210. Some examples of the NFs may include, but not limited to, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF) and a Network Repository Function (NRF). In an embodiment, the NRF serves as a centralized repository for all the NF instances. The probing system210 includes at least one or more components. In one embodiment, the one or more components are in communication with each other via a communication interface to process the received SDR data.
[0045] In one embodiment, the received data includes the subscriber data pertaining to Streaming Data Records (SDRs). The SDRs include, but not limited to, user identifier, current circle, operator of a mobile number associated with the user device 102, network function, interface, network procedure, error code. Some examples of the NFs may include, but not limited to the Network Repository Function (NRF). In an embodiment, the NRF serves as a centralized repository for all the NF instances. An Application Function (AF) provides application services to the subscriber for at least one of the UE 102.
[0046] In one embodiment, the monitoring module 225 of the processor 202 is communicably connected to the transceiver 220. Accordingly, the monitoring module 225 receives the processed SDR data from the probing system210. The monitoring module 225 monitors the communication interface to check for a failure in connectivity between the one or more \ components. Further, the monitoring module 225 is connected to the ML unit 235 to receive the status of the communication interface. In particular, since ML unit 235 receives the status of the communication interface and the monitoring module 225 of the system utilizes the ML unit 235 for monitoring failure therefore, the monitoring module 225 will also receive the status of the communication interface. Basis the status, the monitoring module 225 is configured to check for the failure in connectivity between one or more components. The ML unit 235 receives inputs to one of pause and resume the transfer of data between the at least one or more components. The inputs are one of, but limited to, such as connectivity status of the communication interface and status of the interface.
[0047] In an exemplary embodiment, the probing system210 monitors the status of the connectivity between the probe 214 and the conductor unit 216. Based on the monitoring, the monitoring module 225 is configured to pause the transfer of data between the one or more components, if the connectivity between the one or more components of the probing system210 fails.
[0048] In one embodiment, the probing system210 accepts the data traffic pertaining to the SDR traffic with the auto-pause feature. If any connectivity failure occurs between the one or more components of the probing system 210, the auto-pause feature prevents the probing system210 from forwarding the SDR traffic to the one or more components. In one embodiment, the probing system210 accepts the data traffic pertaining to the SDR traffic with the auto-pause feature and forwards the SDR data to the available one or more component.
[0049] In one embodiment, based on the availability of the one or more components for data transfer, the monitoring module 225 resumes the transfer of data received from the one or more NFs and the data is stored in the database 212.
[0050] In one embodiment, subsequent to resuming transfer of data received from the one or more NFs, the probing system 210 transmits an Application Data Records (ADRs) between the one or more components. In one embodiment, the ADR is a document that describes a choice made by the probing system210 based on determining the availability of the one or more components, the ADR includes details regarding the connectivity failure occurred between one or more components. For example, the ADR includes the details pertaining to at least one of, an exact location of the connectivity failure and time at which the connectivity failure occurred. Each ADR describes the architectural decision, its context, and its consequences. In one embodiment, the ADR is a file extension functionality where indexed data is stored in files. The ADR file generates data source per file which are then moved to a distributed file system for storage.
[0051] The storing module 230 of the processor 202 is communicably connected to the monitoring module 220. The storing module 220 is configured to store the data received from the one or more NFs in the database 212 in response to pausing of the transfer of data. Owing to the storage of the data based on pausing of the transfer of data, the data is protected in multiple network scenario such as any server failure, hardware failure, Operating System (OS) failure, or any hard disk failure. Accordingly, the data is maintained without any data loss.
[0052] In one embodiment, the transceiver 220, the monitoring module 225, the storing module 230, and the ML unit 235 are located at the one or more components of the probing system 210.
[0053] Referring to FIG. 3, FIG. 3 is an exemplary block diagram of a system diagram for providing pause/resume and auto/manual functionality in 5G probing system network, according to various embodiments of the present invention. In one embodiment, the system 108 architecture includes one or more 5G Network Functions (NFs) 302a, 302b,….302n, the one or more component of the probing system 210 such as first component 304, the second component 306, the third component 308 and the user interface 310. The first component 304, the second component 306 and the third component 308 includes at least one of, the probe 214, the conductor unit 216 and the normalizer 218.
[0054] In one embodiment, the probing system 210 includes the first component 304, the second component 306, and the third component 308 in communication with each other via the communication interface to process the received SDR data from the NFs (302a, 302b,….302n).
[0055] The probe 214 is the front face of the 5G NFs (302a, 302b,….302n).
[0056] As mentioned earlier in the FIG. 2, the processor 202 of the system 108 receives the SDR data from the NFs. More specifically, as per the embodiment, the processor 202 is configured to receive the SDR data from the one or more 5G NFs 302a, 302b,….302n. In one embodiment, the transceiver 220 is configured to receive the SDR from the one or more 5G NFs 302a, 302b,….302n and transmit the SDR data to the first component 304 of the probing system 210.
[0057] In one embodiment, upon receiving the SDR data at the first component 304 via the probe 214 of the probing system 210 the monitoring module 225 is configured to determine the availability of the second component 306 of the probing system 304, in the event of any failure occurring in the connectivity between the first component 304and the second component 306. In one embodiment, an auto-pause, an auto-resume, a manual-pause and a manual-resume features are embedded within the monitoring module 225.
[0058] In one embodiment, let us assume the probe 214 of the probing system 210 is configured to send the SDR data to the first component 304. Herein the probe 214 and the first component 304 are the different components of the probing system 210. While sending the SDR data, if the connection between the probe 214 and the first component 304 fails, the probing system 210 pauses the transfer of data between the probe 214 and the first component 304. Consequently, the probe 214 is configured to maintain non-transferred data in the database 212. In addition, the probe 214 is configured to initiate a thread checking to check the connectivity with the second component 306 of the probing system 210.
[0059] Similarly, if at least one of the NF 302a is sending data to the second component 306 of the probing system 210 and the second component 306 is unable to send the data to the third component 308 via the probe 214, then the second component 306is configured to maintain non-transferred data in the database 212. In addition, the probe 214 is configured to initiate a thread checking to check the connectivity of the third component 308 of the probing system 210.
[0060] In one embodiment, upon identification of the failure in the connectivity between the probe 214 and the first component 304, the probe 214 is configured to auto-pause itself and therefore the data sending from the probe 214 to the first component 304is stopped. Further, the probe 214 is configured to maintain non-transferred data in the database 212. In addition, the probe 214 will start a thread checking to check the connectivity between the probe and the second component 306.
[0061] In one embodiment, after receiving the information of the availability of the second component 306 for the connection, the probe is configured to auto-resume itself on the basis of connectivity acknowledgement received from the ML unit 235. Further, the probe 214 forwards the data that is being received from the NFs to the second component 306 and in addition the probe also reads the data that is stored in the database 212 when there was no connectivity.
[0062] In another embodiment, the User Interface (UI) 310 is capable of manual-pause and manual-resume of the data transfer at least one of the first component 304, second component 306 and the third component 308 from the UI 310. In one embodiment, the system 108 provides one or more options but not limited to, auto-pause, auto-resume, manual-pause and manual-resume.
[0063] In one embodiment, the decision to auto-pause, auto-resume, the manual-pause and the manual-resume is decided by an Artificial Intelligence (AI)/Machine Learning (ML) module such as the ML unit 235 embedded within the system 108. The ML unit 235 the SDR data and the manual-pause and manual-resume options selected via the UI 310 to start the data processing. In particular, the ML unit 235 gets the data feed such as the SDR data and makes decision to stop/pause/resume based on the at least one of, but not limited to, an interface, and statistics of the interface etc.
[0064] In one embodiment, the probing system 210 has a feature such as auto pause in order to automatically pause itself whenever the connectivity breaks between the one or more components. Upon the connectivity break, the probing system 210 still accept the incoming SDR traffic with auto pause feature but doesn’t forward it to another component among the one or more components. In another embodiment, the probing system 210 has a feature such as auto resume in order to auto resuming itself in case the connectivity re-establishes between the one or more components. Subsequent to re-establishes connectivity between the one or more components the probing system 210 starts sending the valid incoming SDR’s as well as the ADR’s which were piled up at the time of auto pause activity to another component among the one or more components. In yet another embodiment the manual-pause and the manual-resume is controlled by the UI 310.
[0065] In one embodiment, for example, once there is a connectivity failure between the first NF 302a and the first component 304, the data is instantly stored in the database 212. The first component 304 utilizes the data stored from the database 212 and processes the stored data for further analysis. Similarly, the user has the option for manual-pausing from the UI 310, when connectivity is better and manual-resume the first component 304 from the UI 310 and starts the data processing.
[0066] Referring to FIG. 4, FIG. 4 illustrates a flow diagram of a method 400 for providing data back up during lack of connectivity between network entities 101, according to various embodiments of the present system.
[0067] At step 401 the method 400 includes the step of receiving the SDR data. The transceiver 220 receives the SDR data from the at least one NFs 302a and transmits the SDR data to the probing system 210. In one embodiment, the probing system 210 includes at least one or more components in communication with each other via communication interface to process the received SDR data.
[0068] At step 402 the method 400 includes the step of monitoring the communication interface to check for a failure in connectivity between the one or more components of the probing system 210. In one embodiment, the ML unit 235 receive the connectivity status of the communication interface and status of the interface to one of pause and resume the transfer of data between the at least one or more components. In one embodiment, the probing system 210 accepts the SDR data traffic pertaining to the SDR traffic with an auto-pause feature and prevents the probing system 210 from forwarding the SDR traffic to the one or more components.
[0069] At step 403 the method 400 includes the step of pausing the data transfer between the first component 304 via the probe 214 and the second component 306 by the user interface unit 310. In the event, the connectivity fails between the probe and the second component 306 of the probing system 210, the transferring of the data is paused between the first component 304 and the second component 306. The non transfer data is thereafter stored in the database 212.
[0070] At step 404 the method 400 includes the step of determining the availability of the one or more components. The monitoring module 225 monitors the status of the communication connectivity between the first component 304 and the second component 306 of the probing system 210 and determines the availability of the one or more component.
[0071] At step 405 the method 400 includes the step of resuming the paused data transfer from the first component 304 to the second component 306, when the communication connectivity is restored. The non-transfer data is thereafter stored in the database 212.
[0072] At step 406 the method 400 includes the step of transmitting the ADRs from the first component 304 to the second component 306, subsequent to resuming the transfer of data received from the NFs.
[0073] At step 407 the method 400 includes the step of manual-pausing and manual-resuming of data transferring among the one or more components by the user from the UI 310.
[0074] The present invention further discloses a non-transitory computer-readable medium, according to some embodiments of the present disclosure. In some embodiments, the non-transitory computer-readable medium having stored thereon computer-readable instructions. Stored thereon computer-readable instructions that, when executed by one or more processors 500, causes the processor 500 to receive data from one or more network functions. Transmit the received data to the probing system 210, the probing system210 includes at least one or more components, such as, one of a probe 214, the conductor 216, and the normalizer 218 in communication with each other via a communication interface to process the received data. Monitors the communication interface to check for a failure in the connectivity between the one or more components of the probing system 210. Pause the transfer of data between the at least one or more components, and store the data received from the one or more network functions in the database 212 in response to pausing of the transfer of data, and thereby providing data back during lack of connectivity.
[0075] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-4) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0076] The present disclosure incorporates technical advancement by providing data back up during lack of connectivity between the network entities. The advantages of the invention include the ability for data protection in multiple scenarios such as network scenario such as any server failure, hardware failure, OS failure, any hard disk failure. The method further facilitates in always maintaining the availability of the system. Further, the present disclosure ensures that the data loss is substantially or completely avoided.
[0077] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.
REFERENCE NUMERALS
[0078] User devices -102;
[0079] Remote server-104;
[0080] Network – 106;
[0081] System-108;
[0082] Input/output interface unit-206;
[0083] Processor-202;
[0084] Memory -204;
[0085] Display-208;
[0086] Probing system-210;
[0087] Database-212;
[0088] Probe- 214;
[0089] Conductor unit- 216;
[0090] Normalizer-218;
[0091] Transceiver-220;
[0092] Monitoring module-225;
[0093] Storing module- 230;
[0094] First component-304;
[0095] Second component-306;
[0096] Third component-308;
[0097] User Interface-310.
,CLAIMS:
CLAIMS:
We Claim:
1. A method (400) of providing data back up during lack of connectivity, the method (400) comprising the steps of:
receiving, by a one or more processors (202), data from one or more network functions;
transmitting, by the one or more processors (202), the received data to a probing system (210), the probing system includes at least one or more components, in communication with each other via a communication interface to process the received data;
monitoring, by the one or more processors (202), the communication interface to check for a failure in connectivity between the one or more components of the probing system (210);
pausing, by the one or more processors (202), transfer of data between the at least one or more components; and
storing, by the one or more processors (202), the data received from the one or more network functions in a database (212) in response to pausing of the transfer of data.
2. The method (400) as claimed in claim 1, further comprising the steps of:
determining, by the one or more processors (202), availability of the one or more components to resume transfer of data; and
resuming, by the one or more processors (202), transfer of data received from the one or more network functions and the data stored in the database (212).
3. The method (400) as claimed in claim 1, wherein the one or more processors (202) is configured to pause the transfer of data between the at least one or more components via one of a Machine Learning (ML) unit (214) and a user interface unit (310).
4. The method (400) as claimed in claim 3, wherein the ML unit (235) receives inputs such as connectivity status of the communication interface and status of the interface to one of pause and resume the transfer of data between the at least one or more components.
5. The method (400) as claimed in claim 1, wherein the one or more components include at least one of, a Machine Learning (ML) probe, a conductor, an indexer, a computation engine, a correlation engine, and a normalizer.
6. The method (400) as claimed in claim 1, wherein the data includes data pertaining to Streaming Data Records (SDRs).
7. The method (400) as claimed in claim 2, wherein the one or more processors (202) enables the probing system (210) to accept the data traffic pertaining to the SDR traffic with an auto pause feature, and prevents the probing system (210) to forward the SDR traffic to the one or more components.
8. The method (400) as claimed in claim 2, wherein subsequent to resuming transfer of data received from the one or more network functions, the one or more processors (202) instructs the probing system (210) to transmit Application Data Records (ADRs) between the one or more components.
9. A system (108) for providing data back up during lack of connectivity, the system (108) comprising:
a transceiver (220) configured to:
receive, data from one or more network functions;
transmit, the received data to a probing system (210), the probing system (210) includes at least one or more components in communication with each other via communication interface to process the received data;
a monitoring module (225) configured to:
monitor, the communication interface to check for a failure in connectivity between the one or more components of the probing system (210);
pause, transfer of data between the at least one or more components; and
a storing module (230) configured to store, the data received from the one or more network functions in a database (212) in response to pausing of the transfer of data.
10. The system (108) as claimed in claim 9, wherein the monitoring module (225) is further configured to:
determine, availability of the one or more components to resume transfer of data; and
resume, transfer of data received from the one or more network functions and the data stored in the database (212).
11. The system (108) as claimed in claim 9, wherein the monitoring module (225) is configured to pause the transfer of data between the at least one or more components via one of a Machine Learning (ML) unit and a user interface unit.
12. The system (108) as claimed in claim 9, wherein the ML unit (235) receives inputs such as connectivity status of the communication interface and status of the interface to one of pause and resume the transfer of data between the at least one or more components.
13. The system (108) as claimed in claim 9, wherein the one or more components include at least one of, a probe (214), a conductor (216), an indexer, a computation engine, a correlation engine, and a normalizer (218).
14. The system (108) as claimed in claim 9, wherein the subscriber data includes data pertaining to Streaming Data Records (SDRs).
15. The system (108) as claimed in claim 10, wherein the probing system (210) accepts the data traffic pertaining to the SDR traffic with an auto pause feature, and prevents the probing system (210) to forward the SDR traffic to the one or more components.
16. The system (108) as claimed in claim 10, wherein subsequent to resuming transfer of data received from the one or more network functions, the probing system (210) transmits Application Data Records (ADRs) between the one or more components.
| # | Name | Date |
|---|---|---|
| 1 | 202321049436-STATEMENT OF UNDERTAKING (FORM 3) [21-07-2023(online)].pdf | 2023-07-21 |
| 2 | 202321049436-PROVISIONAL SPECIFICATION [21-07-2023(online)].pdf | 2023-07-21 |
| 3 | 202321049436-FORM 1 [21-07-2023(online)].pdf | 2023-07-21 |
| 4 | 202321049436-FIGURE OF ABSTRACT [21-07-2023(online)].pdf | 2023-07-21 |
| 5 | 202321049436-DRAWINGS [21-07-2023(online)].pdf | 2023-07-21 |
| 6 | 202321049436-DECLARATION OF INVENTORSHIP (FORM 5) [21-07-2023(online)].pdf | 2023-07-21 |
| 7 | 202321049436-FORM-26 [03-10-2023(online)].pdf | 2023-10-03 |
| 8 | 202321049436-Proof of Right [08-01-2024(online)].pdf | 2024-01-08 |
| 9 | 202321049436-DRAWING [19-07-2024(online)].pdf | 2024-07-19 |
| 10 | 202321049436-COMPLETE SPECIFICATION [19-07-2024(online)].pdf | 2024-07-19 |
| 11 | Abstract-1.jpg | 2024-10-01 |
| 12 | 202321049436-Power of Attorney [25-10-2024(online)].pdf | 2024-10-25 |
| 13 | 202321049436-Form 1 (Submitted on date of filing) [25-10-2024(online)].pdf | 2024-10-25 |
| 14 | 202321049436-Covering Letter [25-10-2024(online)].pdf | 2024-10-25 |
| 15 | 202321049436-CERTIFIED COPIES TRANSMISSION TO IB [25-10-2024(online)].pdf | 2024-10-25 |
| 16 | 202321049436-FORM 3 [03-12-2024(online)].pdf | 2024-12-03 |
| 17 | 202321049436-FORM 18 [20-03-2025(online)].pdf | 2025-03-20 |