WO2015138436A1 - Dispositif côté client pour accéder à des données lors d'interruptions de communication - Google Patents

Dispositif côté client pour accéder à des données lors d'interruptions de communication Download PDF

Info

Publication number
WO2015138436A1
WO2015138436A1 PCT/US2015/019685 US2015019685W WO2015138436A1 WO 2015138436 A1 WO2015138436 A1 WO 2015138436A1 US 2015019685 W US2015019685 W US 2015019685W WO 2015138436 A1 WO2015138436 A1 WO 2015138436A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
client terminal
local
terminal device
communication device
Prior art date
Application number
PCT/US2015/019685
Other languages
English (en)
Inventor
Andrew L. CARRICARTE
Samuel Morhaim
Jose M. SANCHEZ
Original Assignee
Tritan Software Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/203,265 external-priority patent/US9774702B2/en
Application filed by Tritan Software Corporation filed Critical Tritan Software Corporation
Priority to SG11201608461SA priority Critical patent/SG11201608461SA/en
Priority to CN201580024173.XA priority patent/CN106464678A/zh
Priority to EP15762108.7A priority patent/EP3117584A4/fr
Publication of WO2015138436A1 publication Critical patent/WO2015138436A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H04W12/033—Protecting confidentiality, e.g. by encryption of the user plane, e.g. user's traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0861—Network architectures or network communication protocols for network security for authentication of entities using biometrical features, e.g. fingerprint, retina-scan
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication

Definitions

  • the invention relates to systems and methods of providing centralized client-side data storage and retrieval on a local network. More particularly, the invention relates to systems and methods of converting data having multiple formats to a predefined format and providing centralized client-side data storage and retrieval of the converted data.
  • the client terminals access the Internet or other remote networks to obtain web-based application data that is stored on remote servers.
  • the client terminals are not able to access the remote servers hosting the web-based data. Thus, communication outages may cause client terminal users to experience
  • productivity loss productivity loss, data loss, or other losses.
  • Client terminals may include applications that store data on the respective client
  • Known client terminal devices store the data in a format that is defined by the application that generates the data.
  • Known systems require each application to generate and store data in a separate database on the
  • Each separate database is distributed and is accessible only to the
  • the invention advantageously discloses a method and system for providing a plurality of client terminal devices with connectivity to a central device during off-line operation.
  • the invention provides a local communication device that locally stores data obtained from a plurality of sources, including a remote server, a local server and a client terminal device.
  • the remote server is associated with an external network and the local server is associated with an internal network.
  • the client terminal device communicates with the remote server over the external network and communicates with the local server over the internal network.
  • the local communication device includes a software agent that communicates with the local server, the remote server and the client terminal device to gather the data from the local server, the remote server and the client terminal device and provides access to the data during time periods when a data connection is disrupted between the client terminal device and the local server or the remote server.
  • the local communication device further includes a storage module that is adapted to store the gathered data to at least one memory device and a conversion module that generates a predefined format for the gathered data.
  • the invention provides a local area network
  • the communication device that locally stores data obtained from a plurality of sources, including a remote server, a local server and a client terminal device.
  • the remote server is associated with an external network and the local server is associated with an internal network.
  • the client terminal device communicates with the remote server over the external network and communicates with the local server over the internal network.
  • the local communication device includes a software agent that communicates with the local server, the remote server and the client terminal device to gather the data from the local server, the remote server and the client terminal device and provides access to the data during time periods when a data connection is disrupted between the client terminal device and the local server or the remote server.
  • the local communication device further includes a database module that generates and manages at least one database, a storage module that is adapted to store the gathered data to the at least one database, a conversion module that generates a predefined format for the gathered data and a synchronizing module that maintains a data version tag for the data stored in the at least one database.
  • a local communication device stores the data transmitted between selected sources and the client terminal devices and monitors whether the client terminal devices are communicating with the selected sources.
  • the local communication device establishes a data connection with the client terminal devices, transmits data to the client terminal devices, and assigns a synchronization start identifier, one or more synchronization intermediate identifiers and a synchronization completed identifier to facilitate data transfer with the selected sources.
  • the local communication device monitors whether a data connection is re-established between the client terminal devices and the selected sources and re-establishes a data connection between the client terminal devices and the selected sources when the client terminal devices are coupled to the selected sources.
  • Data is transmitted between selected sources and client terminal devices and the data is stored to a local communication device. If a communication channel between the client terminal devices and the selected sources is disrupted, then a data connection is established between the client terminal devices and the local communication device. During the network outage, data is transmitting between the local communication device and the client terminal devices. The local communication device and the selected sources synchronize the stored data to provide the latest retrieved data. The client terminal devices are coupled to the selected sources upon determining that the data connection is re-established between the client terminal devices and the selected sources and any data that is entered during offline operation may be synchronized to the selected data source.
  • FIG. 1 illustrates a system diagram according to one embodiment of the invention.
  • FIG. 2 illustrates an exemplary embodiment of the system of FIG. 1 operating in an environment where external communications paths couple the local devices and the external network devices.
  • FIG. 3 illustrates an exemplary embodiment of the system of FIG. 1 operating in an environment where external communications paths are decoupled between the local devices and the external network devices and internal communications paths couple the local devices with the local communications device.
  • FIG. 4 illustrates a system for transferring data between a remote server and a local communication device according to one embodiment of the invention.
  • FIG. 5 illustrates a flow chart for providing a plurality of client terminal devices with off-line connectivity to a central database.
  • the invention provides systems and methods of employing a local communication device that performs centralized client-side data storage and retrieval.
  • the local communication device that performs centralized client-side data storage and retrieval.
  • the communication device may be coupled to a plurality of sources, including external networks, internal networks and client terminal devices, among other sources.
  • the local communication device receives data from and transmits data to the plurality of sources and converts the data to preselected formats prior to storage.
  • the local communication device may receive data in any format including MS Word format, MS Excel format, PDF format, or any other format.
  • the local communication device may convert the received data to preselected formats including Health Level Seven (HL7), Extensible Markup Language (XML), American National Standards Institute (ANSI) standards, viewable format through MEDIOS proprietary application or other preselected formats.
  • HL7 Health Level Seven
  • XML Extensible Markup Language
  • ANSI American National Standards Institute
  • known systems employ distributed architectures that include client terminal devices having individual applications that generate distributed databases on the corresponding client terminal device.
  • the distributed databases are stored at the client terminal devices and are accessible only by the individual applications that generate the distributed database.
  • known systems are deficient at least because the data stored in the distributed database is segmented, non-centralized, non-portable and is available only to the corresponding individual applications.
  • FIG. 1 illustrates an example of the system architecture 100 according to one embodiment of the invention.
  • Client terminal devices 102a-102n may be coupled to one or more local servers 104a-104n (hereinafter identified collectively as 104) and/or to one or more remote servers 130a-130n (hereinafter identified collectively as 130) via a wired network, a wireless network, a combination of the foregoing and/or other networks, such as a local area network 106 and an external network 125.
  • a local communication device 110 may be provided to capture and store data communications between the client terminal devices 102, the local servers 104 and the remote servers 130 and other components.
  • the local communication device 110 may be of modular construction to facilitate adding, deleting, updating and/or amending modules therein and/or features within modules.
  • Modules may include a software agent 112, a storage module 114, a scheduling module 116, a database module 118, a switching module 120, a synchronizing module 121, a conversion module 122, an alert module 123 or other modules. It should be readily understood that a greater or lesser number of modules might be used.
  • One skilled in the art will readily appreciate that the invention may be implemented using individual modules, a single module that incorporates the features of two or more separately described modules, individual software programs, and/or a single software program.
  • the software agent 112 may request data from the plurality of sources with or without end user awareness of the data requests. For example, the software agent 112 may capture data exchanges that occur during communications between the client terminal devices 102 and the remote servers 130, wherein the data exchanges are routed through the external network 125, such as the Internet. The software agent 112 may capture the data exchanges in substantially real-time or at predefined intervals. Alternatively, the software agent 112 may trigger capturing the data exchanges based on availability of system resources, such as bandwidth or other system resources.
  • a storage module 114 may be provided to direct the captured data to a desired memory device for storage.
  • the software agent 112 may include applications that perform the data capture on sources that are coupled to the local communication device 110.
  • the sources may include the client terminal devices 102, the local servers 104, and the remote servers 130, among other sources.
  • security credentials e.g., passwords, digital certificates, etc.
  • the software agent 112 may perform authentication prior to requesting the data transfer to the local communication device 110.
  • the software agent 112 may await a user log-in with the security credentials prior to requesting data transfer to the local communication device 110.
  • Local communication device 110 provides access to the data independent of the geographical location or time periods when a data connection is disrupted between the client terminal devices 102 and local
  • the users may be invited to submit requested information or take other action.
  • the selected sources may perform other processing. For example, the selected sources may load data or other information (e.g., download) to the client terminal devices 102 that an authorized user may be permitted to access, but has not yet received from the selected sources.
  • the user may be asked to input an alphanumeric code.
  • the user may be asked to provide biometric information (i.e., a thumbprint through a fingerprint scanner) or other suitable identifying information.
  • biometric information i.e., a thumbprint through a fingerprint scanner
  • Other authentication schemes may be employed.
  • the local communication device 110 may operate as a redundancy device that stores data accessed or data sought to be accessed by the plurality of sources.
  • FIG. 2 illustrates an exemplary embodiment of the system of FIG. 1 operating under conditions where external communication paths 202 couple the remote server 130 to the client terminal devices 102, the local server 104 and/or the local communication devices 110.
  • the client terminal devices 102 and the local server 104 transmit and receive data from the remote server 130.
  • the local communication device 110 may communicate with the remote server 130 to duplicate and locally store data received from the remote server 130.
  • the software agent 112 may instruct the local communication device 110 to continuously store the requested data. Alternatively, the software agent 112 may instruct the local communication device 110 to update the requested data at predefined schedules or automatically upon availability.
  • a scheduling module 116 may be provided in the local communication device 110 to establish the predefined schedules to include periodic schedules, random schedules, scheduling based on system resources, or other predefined schedules.
  • the local communication device 110 may include a database module 118 that generates and manages a central database 124.
  • the central database 124 may be accessed by one or more sources, including the client terminal devices 102, the local servers 104 and the remote servers 130.
  • the central database 124 may be structured to mirror the data structure of the selected sources, including the client terminal devices 102, the local servers 104 and the remote servers 130.
  • the local communication device 110 may include a switching module 120 that operates to switch a data connection for the client terminal devices 102 between the selected sources and the central database 124.
  • the operation of switching the data connection for the client terminal devices 102 between the selected sources and the central database 124 may be transparent to users of the client terminal devices 102.
  • the operation of switching data connections for the client terminal devices 102 between the selected sources and the central database 124 may be initiated by users of the client terminal devices.
  • the switching module 120 may include a feature that determines the communication status of the client terminal devices 102.
  • the feature may detect whether the client terminal devices 102 are operating online or offline, relative to the external network 125. Additionally, the switching module 120 may detect a type of network connection for the client terminal devices 102, such as a wired connection, a wireless connection or other network connection. If the client terminal devices 102 are determined to be operating offline relative to the external network 125, then the client terminal devices 102 may be coupled to the
  • FIG. 3 illustrates an exemplary embodiment of the system of FIG. 1 operating in an environment where external communication paths 202 are decoupled between the local devices and the external network devices. Under this condition, internal communication paths 302 are provided to couple the local communications device 110 with the client terminal devices 102 and the local server 104. Since the local communication device 110 locally stores a duplicate of the data stored at the remote server 130, users that are accessing the client terminal devices 102 and the local server 104 do not experience a service disruption when the external communication paths 202 are decoupled.
  • the switching module 120 of FIG. 1 may detect trigger events to automatically initiate switching the data connections between the selected sources and the central database 124.
  • the trigger events may include detecting time periods when communication channels to the selected sources are not available, among other trigger events.
  • the switching module 120 may respond to a manually initiated trigger to switch the data connections between the selected sources and the central database 124.
  • the manually initiated trigger may include enabling users to activate a command at the client terminal devices 102 when communication channels to the selected sources are not available, among other manually initiated triggers.
  • the local communication device 110 may include a synchronizing module 121 that maintains data version tags for the data stored at the selected sources and the central database 124.
  • the data version tags may be used at the selected sources and the central database 124 to identify the data that is stored most recent in time.
  • the synchronizing module 121 may analyze the data version tag and determine whether to replicate data from the selected sources to the central database 124 or from the central database 124 to the selected sources. In this way, the synchronizing module 121 prevents the client terminal devices 102 from accessing expired data.
  • the synchronizing module 121 may determine whether the selected sources or the central database 124 is maintaining the most recent data version tag by analyzing which of the selected sources or the central database 124 performed the last save function.
  • the remote server 130 may be configured to synchronize a plurality of local communication devices 110 that are spread across multiple networks.
  • the synchronization module 121 may employ a success/fail transaction protocol that ensures data is successfully transferred without any loss of connectivity.
  • the synchronization module 121 may apply a transaction based, encryption and decryption synchronization algorithm to perform data transfers in predefined stages.
  • the predefined stages may include a start point, breakpoints and a commit point.
  • the synchronization module 121 identifies a start point to the beginning of a selected data transfer. After identifying the start point, the synchronization module 121 may assign intermediate breakpoints to the transferred data. The breakpoints are provided to recover data transfer operations if an interruption occurs before the data transfer is complete. For example, after experiencing a data transfer interruption, the data transfer operation may begin from a previously identified successful breakpoint.
  • the synchronization module 121 enables the data transfer operation to recover from a breakpoint or intermediate transfer point, rather than from the start point or the beginning of the data transfer.
  • the synchronization module 121 assigns an identification number to the data transfer. Additionally, the synchronization module 121 may classify the data transfer as authentic and complete.
  • synchronization module 121 is adapted to monitor a broadcast system that is operated over the network device and into the external network over a predefined protocol. A predefined logical port automatically resolves conflicts of data and, via a series of algorithms, and automatically reestablishes synchronization from the local network and a set of one or more external servers.
  • FIG. 4 illustrates a system for performing data transfer.
  • the remote server 130 and the local communication device 110 begin a synchronization process over communication channel 402 using a plurality of intermediate breakpoints or synchronization intermediate identifiers (403a-403n).
  • breakpoint 1 (403a) and breakpoint 2 (403b) are established between the remote server 130 and the local communication device 110.
  • the remote server 130 and the local communication device 110 transmit status information over communication channel 404.
  • the data transmission may occur without experiencing a data transfer interruption.
  • the synchronization module 121 may identify a Start Point 1 or start identifier at 01/01/Yrl, 03:00:00 SERVER TIME and data transfer may begin over communication channel 402.
  • the data transfer may traverse BREAKPOINT 1 (403a) at 01/01/Yrl, 03:03:00 SERVER TIME and may traverse BREAKPOINT 2 (403b) at
  • the synchronization module 121 may establish a COMMIT POINT and assign a synchronization complete identification number ID:0001 :01/01/Yrl, 03:06:00 SERVER TIME. The data transfer may be considered complete and authenticated upon assignment of identification number ID:0001.
  • the data transmission may occur with a data transfer interruption.
  • the synchronization module 121 may identify a Start Point 1 at 01/01/Yrl, 03:00:00 SERVER TIME and data transfer may begin over communication channel 402.
  • the data transfer may traverse BREAKPOINT 1 (403a) at 01/01/Yrl, 03:03:00 SERVER TIME and may experience an INTERRUPTION at 01/01/Yrl, 03:04:30 SERVER TIME, such as if the server encounters bandwidth loss.
  • the synchronization module 121 may initiate a rollback to BREAKPOINT 1 at 01/01/Yrl, 03:04:35 SERVER TIME.
  • the synchronization module 121 may begin the data transfer at BREAKPOINT 1 at 01/01/Yrl, 03:20:35 and may traverse
  • the synchronization module 121 may establish a COMMIT POINT, assign identification number ID:0002:01/01/Yrl, 03:23:35 SERVER TIME. The data transfer may be considered completed authenticated upon assignment of identification number ID:0002.
  • the local communication device 110 may include a conversion module 122 that converts the received data to preselected formats including Health Level Seven (HL7), Extensible Markup Language (XML), American National Standards Institute (ANSI) standards, or other preselected formats prior to storage.
  • HL7 Health Level Seven
  • XML Extensible Markup Language
  • ANSI American National Standards Institute
  • Other standards that enable interoperability may be employed, such as but not limited to CCD, DICOM, HIPAA, and HITSP.
  • the ANSI compliant file may be denoted as a Vessel Data Exchange (VDE) file.
  • VDE Vessel Data Exchange
  • the data that is stored in the central database 124 may be searched using a variety of techniques. According to one embodiment, the search may be performed using a structured query language (SQL) that uses SQL statements to perform tasks on the database 124, such as retrieving data from the database 124.
  • SQL structured query language
  • the local communication device 110 may include an alert module 123 that generates notifications and/or alerts in real-time. The generated notifications and/or alerts may be delivered in real-time to notify users of the status of the network connectivity.
  • the client terminal devices 102 may include any number of different types of client terminal devices, such as medical devices, medical equipment, personal computers, laptops, smart terminals, personal digital assistants (PDAs), mobile devices, cell phones, Web TV systems, video game consoles, and devices that combine the functionality of one or more of the foregoing or other client terminal devices.
  • the client terminal devices 102 may include processors, RAM, USB interfaces, telephone interfaces, satellite interface, microphones, speakers, a stylus, a computer mouse, a wide area network interface, a local area network interface, hard disks, wireless communication interfaces, DVD/CD reader/burners, a keyboard, a flat touch-screen display, and a display, among other components.
  • the client terminal devices 102 may include a touch- sensitive display screen, a handset, speakers and input buttons, among other features. Select functions may be implemented on the client terminal devices 102 by positioning an indicator over selected icons and manipulating an input receiving device such as a touch-sensitive display screen, a mouse, a keyboard, a voice recognition system or other input receiving devices.
  • the client terminal devices 102 may include a video input device to permit audiovisual communication with other client terminal devices 102, such as to permit dictation by medical personnel.
  • the client terminal devices 102 may communicate with the remote servers 130, the local servers 104, other client terminal devices 102 and/or other systems.
  • Users may access the client terminal devices 102 to communicate with the selected sources, including the client terminal devices 102, the local servers 104 and the remote servers 130.
  • Data requests that originate from the client terminal devices 102 may be broadcast to selected sources and the local communication device 110 in substantially in real- time if the client terminal devices 102 are coupled to networks 106,125.
  • communications from the client terminal devices 102 may be delayed for an amount of time if, for example, a selected client terminal device 102 is not connected to the local area network 106.
  • the data connection between the client terminal device 102 and the local server 104 or the remove server 130 may be disrupted due to a large latency, a delayed connection, or a severed connection, among other disruptions.
  • any requests that are made while the client terminal devices 102 are not connected to the local area network 106 may be stored and propagated from/to the offline client terminal device 102 when the selected sources, the local communication device 110 and the target client terminal device 102 are re-connected to networks 106/125.
  • requests remain in the corresponding client terminal device 102 for dissemination to the local communication device 110 or the selected sources when the target client terminal devices 102 are re-connected to networks 106/125.
  • FIG. 5 illustrates a method 500 of providing a plurality of client terminal devices with off-line connectivity to a central database.
  • Data is transmitted between the selected sources and the client terminal device 102 in operation 501, wherein data communication is performed via networks 106/125.
  • the network 125 may include the Internet.
  • Data communication between the client terminal devices 120 and the selected sources may occur substantially in real-time if the client terminal devices 102 are connected to the networks 106/125.
  • data is transmitted between the selected sources and the local communication device 110, wherein the data communication is performed via network 106/125.
  • communications may be conducted in various ways and among various devices.
  • communications may be conducted in various ways and among various devices.
  • the technology includes a distributed system with one or multiple locations with an optionally defined central hub.
  • the information on each of the nodes is accessed locally by users in that network and is not limited by the connectivity to any of the other nodes.
  • the information is readily available on all nodes as needed on a continuous or scheduled basis with an algorithm that decides how to synchronize.
  • the synchronization can be made either ubiquitous (e.g., complete) so that each node has the same information, or the synchronization can be selective, in which case it only transfers the minimum data needed to operate, plus any additional data selected.
  • the nodes could be stationed on mobile devices such as a network of mobile phones or mobile vessels such as, for example, but not limited to, a truck, a tank, a boat or an airplane.
  • the file system is also transferred by default in selective mode (e.g., it only transfers the minimum needed to operate).
  • the system is self- maintained and possesses an updated mechanism. It also has a disaster recovery mechanism allowing for the system to fully recover itself with a very short recovery time objective (RTO) and recovery point objective (RPO).
  • RTO recovery time objective
  • RPO recovery point objective
  • Communications from or to the nodes can occur via Transmission Control/Internet Protocol (TCP/IP) using TCP and User Datagram Protocol (UDP) transport protocols.
  • TCP/IP Transmission Control/Internet Protocol
  • UDP User Datagram Protocol
  • the specific port numbers can be configured at the time of setup.
  • Packages can be compressed using, for example, the ZLib filter which uses the DEFLATE algorithm.
  • Database data can be stored in any standard relational database including, but not limited to, MySQL, PostgresSQL Lite, and MICROSOFT SQL.
  • the database is configured to report binary logs to a pre-defined local location.
  • a daemon reads each bin- log entry and broadcasts to each enabled node.
  • the bin-log is assigned a globally unique ID and then each node attempts to execute the selected bin- log entry one at a time.
  • Each bin- log entry contains one or multiple SQL statements. The statements can be executed in real-time and in case of two statements attempting to affect the same row, the latest insert prevails.
  • Each node manages time by setting a Network Time Protocol (NTP) with predefined time settings.
  • NTP Network Time Protocol
  • the system can be configured to handle errors in different ways. For example, a Latest Entry Prevails method handles errors by default, by executing all queries and the latest query affecting the same row prevails. Thus, if a conflict arises, each transaction is inserted and a latest inserted occurrence would prevail.
  • a node In a Priority Node method, a node can be configured to have priority over other nodes. Therefore, if two statements affect the same row within a pre-configured time, the priority node would prevail.
  • the outcome could be handled in several ways. For example:
  • a conflict resolution mechanism can be used where transactions are merged across one or more remote servers 130.
  • Selective DB can be accomplished with any relational database including, for example, MySQL, Postgres, SQLite and MSSQL as well as any Non-SQL protocols such as Elastic, MongoDB, CouchDB or Cassandra.
  • the disclosure is not limited to a specific type of relational database.
  • An atomic record is first established. An atomic record is defined as the core entity in the system needed for business operation, and then all dependent entities attached are automatically encapsulated within the atomic record. The record can then be transferred over TCP/IP to one or all nodes. The record can be transferred via a serialized object. The serialized object can be compressed using a ZLib filter based on the DEFLATE strategy.
  • Transfer control assurance can be configured to either confirm the receipt of the object or attempt to resend it if it failed to receive it. This option can be disabled to not expect a confirmation-of -receipt to minimize package size.
  • the files needed to operate the business logic are identified by the application at runtime by flagging each file with its creation location. All files can be scanned at any preselected intervals, (e.g., scanned every 1 -minute) to detect any changes. If another node is requesting the use of the file, then this file is flagged in the requesting node. The flag is transferred to all the nodes via the DB replication. Following this, the file is transferred to any of the requesting nodes.
  • the file can be compressed using ZLib based on the DEFLATE strategy, although other compression protocols may be used.
  • the files can also be deleted from any node where the file is not flagged as being required by the business application.
  • the system can install all required updates as flagged by a central server using the LINUX- based Advanced Packaging Tool (APT) package manager.
  • This includes all operating system (OS) layer updates as well as any other required package needed for operation as flagged by configuration on a central server.
  • the application layer is updated by a remote control script that can be written in, for example, BASH, PERL and PYTHON, which retrieves all the required files needed for the application and transfers them to the nodes.
  • each of the nodes sends a notification to all the other nodes using the DB replication and then self-stop replication.
  • the update takes place by backing up the current application and then replacing all files with the new files.
  • the replication is then restored and a notification is sent to the other nodes. In case of an error, the system remains in maintenance mode and awaits manual intervention. All other nodes continue to operate normally.
  • the system In case of a disaster, the system is reinstalled and flagged as a "fresh" DB. Upon the start of replication, the required data to operate is transferred from the other nodes to take the system to the latest level of data.
  • RPO is determined by the bandwidth available at the time of the disaster. The last sequence broadcasted from the node to the other nodes becomes the recovery point objective.
  • Recovery time objective is determined by the bandwidth available after the disaster. The fastest the connection, the faster the RPO will be reached.
  • the system can issue a Quality of Service (QoS) upgrade request via Simple Network
  • SNMP Network Management Protocol
  • a set of devices and peripherals can be connected to any of terminals devices 102 to collect biometrics data, financial data and/or medical data.
  • the data may be stored locally in terminal device 102, transferred to local server 104 and/or replicated to each of the nodes.
  • the connection from the devices to the terminals can be any standard connection protocol, for example, USB, Serial, BLUETOOTH, Wi-Fi or Network TCP/IP.
  • the data can be transferred using one or more of many different formats such as, for example, HL7, CSV or XML.
  • Biometric data may be collected via the use of one or more traditional data collection methods including but not limited to fingerprint, palm scan, retina scan, and/or facial recognition.
  • Financial data may be collected with the use of one or more scanning techniques such as but not limited to magnetic cards, smart chip cards, BLUETOOTH identifiers and/or barcode ID's.
  • Medical data may be collected with the use of a wide array of medical devices including but not limited to EKG devices, pulse detectors, blood pressure monitors, oximetry sensors, weight and height scales, X-Ray Devices (both digital and film-based), blood analyzers, urine analyzers, stool analyzers, ultrasound devices and Doppler devices, among others.
  • the invention can be realized in hardware, software, or a combination of hardware and software. Any kind of computing system, or other apparatus adapted for carrying out the methods described herein, is suited to perform the functions described herein.
  • a typical combination of hardware and software could be a specialized computer system having one or more processing elements and a computer program stored on a storage medium that, when loaded and executed, controls the computer system such that it carries out the methods described herein.
  • the invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which, when loaded in a computing system is able to carry out these methods.
  • Storage medium refers to any volatile or non-volatile storage device.
  • Computer program or application in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following a) conversion to another language, code or notation; b) reproduction in a different material form.

Abstract

La présente invention concerne un procédé et un système permettant de stocker localement des données obtenues auprès d'une pluralité de sources, le dispositif de communication local étant en communication avec un serveur local qui est associé à un réseau local, le serveur local étant également associé à un réseau externe, et au moins à un dispositif terminal client qui communique avec le serveur local par un réseau interne, le serveur local se synchronisant avec un ensemble d'un ou plusieurs serveurs distants dans le réseau externe.
PCT/US2015/019685 2014-03-10 2015-03-10 Dispositif côté client pour accéder à des données lors d'interruptions de communication WO2015138436A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
SG11201608461SA SG11201608461SA (en) 2014-03-10 2015-03-10 Client side device accessing data during communication distruptions
CN201580024173.XA CN106464678A (zh) 2014-03-10 2015-03-10 在通信中断期间访问数据的客户端装置
EP15762108.7A EP3117584A4 (fr) 2014-03-10 2015-03-10 Dispositif côté client pour accéder à des données lors d'interruptions de communication

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/203,265 2014-03-10
US14/203,265 US9774702B2 (en) 2009-10-19 2014-03-10 System and method of employing a client side device to access local and remote data during communication disruptions

Publications (1)

Publication Number Publication Date
WO2015138436A1 true WO2015138436A1 (fr) 2015-09-17

Family

ID=54072327

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/019685 WO2015138436A1 (fr) 2014-03-10 2015-03-10 Dispositif côté client pour accéder à des données lors d'interruptions de communication

Country Status (4)

Country Link
EP (1) EP3117584A4 (fr)
CN (1) CN106464678A (fr)
SG (1) SG11201608461SA (fr)
WO (1) WO2015138436A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852672A (zh) * 2021-09-07 2021-12-28 天翼数字生活科技有限公司 用于管理和监控分布式数据采集任务的方法和系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110825761B (zh) * 2019-11-14 2024-02-23 中国船舶重工集团公司第七0七研究所 一种面向船岸分布式电子海图系统的海图数据布置与更新方法
CN114827110A (zh) * 2022-03-09 2022-07-29 深圳依时货拉拉科技有限公司 一种路演方法、设备、系统和计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010002900A1 (en) * 1997-03-25 2001-06-07 David A. Romrell System for transparent recovery from disruption of a data transfer
US20040193942A1 (en) * 2003-02-27 2004-09-30 Sun Microsystems, Inc. Method for synchronous support of fault-tolerant and adaptive communication
US20100077017A1 (en) * 2008-09-19 2010-03-25 Yahoo! Inc. System and method for distributing media related to a location
US20100235676A1 (en) * 2002-09-06 2010-09-16 Samy Mahmoud Aboel-Nil Method and system for processing email during an unplanned outage

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101516131B (zh) * 2008-02-18 2012-04-04 华为技术有限公司 一种数据同步的方法、系统和装置
US8671155B2 (en) * 2009-10-19 2014-03-11 Ios Health Systems, Inc. System and method of employing a client side device to access local and remote data during communication distruptions
US9774702B2 (en) * 2009-10-19 2017-09-26 Tritan Software Corporation System and method of employing a client side device to access local and remote data during communication disruptions

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010002900A1 (en) * 1997-03-25 2001-06-07 David A. Romrell System for transparent recovery from disruption of a data transfer
US20100235676A1 (en) * 2002-09-06 2010-09-16 Samy Mahmoud Aboel-Nil Method and system for processing email during an unplanned outage
US20040193942A1 (en) * 2003-02-27 2004-09-30 Sun Microsystems, Inc. Method for synchronous support of fault-tolerant and adaptive communication
US20100077017A1 (en) * 2008-09-19 2010-03-25 Yahoo! Inc. System and method for distributing media related to a location

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852672A (zh) * 2021-09-07 2021-12-28 天翼数字生活科技有限公司 用于管理和监控分布式数据采集任务的方法和系统
CN113852672B (zh) * 2021-09-07 2024-02-20 天翼数字生活科技有限公司 用于管理和监控分布式数据采集任务的方法、系统和介质

Also Published As

Publication number Publication date
EP3117584A1 (fr) 2017-01-18
SG11201608461SA (en) 2016-11-29
CN106464678A (zh) 2017-02-22
EP3117584A4 (fr) 2017-11-08

Similar Documents

Publication Publication Date Title
US9774702B2 (en) System and method of employing a client side device to access local and remote data during communication disruptions
US9973582B2 (en) Method and apparatus for bi-directional communication and data replication between multiple locations during intermittent connectivity
US8671155B2 (en) System and method of employing a client side device to access local and remote data during communication distruptions
US10747714B2 (en) Scalable distributed data store
US10078564B2 (en) Preventing split-brain scenario in a high-availability cluster
US9984140B1 (en) Lease based leader election system
US7937716B2 (en) Managing collections of appliances
US20090063650A1 (en) Managing Collections of Appliances
US9582558B2 (en) Method and system for data definition language (DDL) replication
US10609123B2 (en) Hybrid quorum policies for durable consensus in distributed systems
KR20130131362A (ko) 파일 시스템 내에 투명 페일오버의 제공
CN104731691A (zh) 动态调整分布式文件系统内文件副本数目的方法和系统
US10819641B2 (en) Highly available servers
EP3416354B1 (fr) Procédé et appareil de communication bi-directionnelle et de réplication de données entre des emplacements multiples pendant une connectivité intermittente
US9264414B2 (en) Retry and snapshot enabled cross-platform synchronized communication queue
US20220276993A1 (en) Watermark-based techniques for change-data-capture
WO2015138436A1 (fr) Dispositif côté client pour accéder à des données lors d'interruptions de communication
US10795864B1 (en) Method and apparatus for bi-directional communication and data replication between local and remote databases during intermittent connectivity
WO2023244491A1 (fr) Techniques de pointage de vérification de réplication durant une reprise après sinistre
US10275738B1 (en) Techniques for handling device inventories
US11295836B2 (en) Preservation of multi-server database fidelity
CN107465727B (zh) 一种时间监控系统和方法
CN117643015A (zh) 基于日志记录的客户端密钥修改的快照跨一系列节点管理密钥
CN111294231A (zh) 资源管理方法及系统
US20230409534A1 (en) Techniques for replication checkpointing during disaster recovery

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15762108

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015762108

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015762108

Country of ref document: EP