Medical internet-of-things network system and data synchronization method

By introducing localized servers and local area networks into the Internet of Things architecture in the medical field, and using storage and cache databases for data synchronization, network stability and security issues are solved, efficient data synchronization and analysis of medical IoT devices are achieved, and the data synchronization and analysis of medical IoT devices is reduced. cost.

CN119030995APending Publication Date: 2024-11-26SHANGHAI ZHUODAO MEDICAL TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202411505916.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-28
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The existing IoT architectures have problems in the medical field of poor network stability, high latency, weak security performance and high maintenance and overhead costs, resulting in limited data synchronization and analysis efficiency and accuracy of medical IoT devices.

Method used

Using localized servers to build a local area network, communicate with medical IoT devices, and use storage and cache databases to synchronize data, reduce transmission through external networks, realize encrypted communication, and synchronize data with remote servers through a unified interface within the local area network, reducing Concurrent pressure on remote servers.

Benefits of technology

Improve network stability and latency performance, enhance data security, reduce maintenance and overhead costs, and improve data synchronization efficiency and accuracy of treatment/rehabilitation training for medical IoT devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119030995A_ABST
    Figure CN119030995A_ABST
Patent Text Reader

Abstract

The invention provides a medical internet-of-things network system and a data synchronization method. The system comprises a plurality of medical internet-of-things devices configured locally; each medical Internet of Things device is configured with a first storage database and a first cache database; and the local server is in communication connection with each medical Internet of Things device through a local area network and is provided with a second storage database and a second cache database. Using storage and cache databases, the medical Internet of Things device may synchronize data with a local server, which may synchronize data with a removably deployed remote server. Therefore, the local equipment data is synchronized to the outside through the local server in the local area network, the equipment data synchronization time delay is reduced, and the network is stable; through data synchronization between the uniform interface, namely the local server and the removably deployed far-end server, the parallel connection number of the removably deployed far-end server is reduced so as to reduce the pressure, and the local equipment is safely isolated from the outside.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of communication network technology, and in particular to a medical Internet of Things network system and a data synchronization method. Background Art

[0002] At present, most IoT devices are connected to the Internet through an IoT gateway and then to a remote server. All data enters the server or device through the Internet, which results in low bandwidth, large network latency, unstable network (affected by weather, number of base stations, number of nearby connected devices, operator servers, etc.), data loss, complex data synchronization, network attacks, high concurrency pressure and other abnormal situations. The maintenance cost and network overhead cost are relatively high, making it inconvenient to maintain.

[0003] In the medical field, with the continuous development of intelligent medical technology, common medical electronic equipment, rehabilitation training equipment and other medical IoT devices may also need to be connected to the IoT network to facilitate the synchronization and analysis of medical / rehabilitation data to improve the efficiency and accuracy of treatment and rehabilitation training. However, if the current IoT architecture mentioned above is adopted, there are many shortcomings such as poor network stability, high network latency, weak network security performance, high network maintenance and overhead costs. Summary of the invention

[0004] In view of the shortcomings of the above-mentioned related technologies, the purpose of the present invention is to provide a medical Internet of Things network system and a data synchronization method to solve the problems in the related technologies.

[0005] The first aspect of the present disclosure provides a medical Internet of Things network system, comprising: a plurality of medical Internet of Things devices configured locally; each medical Internet of Things device runs an application; the application is configured to be able to access and utilize a first storage database and a first cache database configured on the medical Internet of Things device through a device data service; a local server, which is communicatively connected to each of the medical Internet of Things devices through a local area network and is configured with a second storage database and a second cache database; the local server is communicatively connected to a removably deployed remote server through an external network; the removably deployed remote server is configured with a third storage database and a third cache database; wherein the medical Internet of Things device, the local server and the remote server respectively use their respective configured storage databases to store / read data, and use their respective configured cache databases to cache data to be synchronized; and the first communication object can synchronize data with the second communication object to update the corresponding data in the storage database of the second communication object based on the synchronized data obtained from the first communication object; wherein the first communication object and the second communication object are selected as any two of the medical Internet of Things device, the local server and the removably deployed remote server.

[0006] In an example of the first aspect, data is synchronized between the first communication object and the second communication object, including: when data changes occur, the first communication object forms data to be synchronized in a cache database based on the modified data; in response to maintaining a communication connection with the second communication object, the first communication object sends the data to be synchronized to the second communication object for data synchronization, so that when the data synchronization is successful, the second communication object updates the accessed storage database based on the data to be synchronized; in response to successful data synchronization, the first communication object deletes the data to be synchronized.

[0007] In an example of the first aspect, in response to the second communication partner not responding for a preset number of times / duration during data synchronization, the first communication partner determines that the data synchronization has failed.

[0008] In an example of the first aspect, synchronizing data between the first communication object and the second communication object includes: when the first communication object is powered on / reconnected, determining whether there is any unsynchronized data to be synchronized in the accessed cache database; in response to maintaining a communication connection with the second communication object, the first communication object sends the data to be synchronized to a determined second communication object for data synchronization, so that when the data synchronization is successful, the second communication object updates the accessed storage database based on the data to be synchronized; in response to successful data synchronization, the first communication object deletes the data to be synchronized.

[0009] In an example of the first aspect, the local server is used to provide web access services to user terminals within the local area network to form a control path for the medical IoT device; and / or, the removably deployed remote server is used to provide web access services to the local server to user terminals connected in communication.

[0010] In an example of the first aspect, encrypted communication is performed between the medical IoT device and a local server; and / or encrypted communication is performed between the local server and a removably deployed remote server.

[0011] In an example of the first aspect, the encrypted communication uses an encryption algorithm based on a digital certificate; or, a first encryption algorithm for encrypted communication between the local server and a removably deployed remote server is stricter than a second encryption algorithm for encrypted communication between the medical IoT device and the local server.

[0012] In an example of the first aspect, when the medical IoT device synchronizes data including original medical / rehabilitation data to a local server, the local server updates the data in the second storage database and synchronizes data to a remote server including medical / rehabilitation result data obtained based on the original medical / rehabilitation data.

[0013] In an example of the first aspect, the medical IoT device, the local server, and the removably deployed remote server delete the data to be synchronized after the data to be synchronized in the cache databases configured respectively are synchronized successfully.

[0014] A second aspect of the present disclosure provides a data synchronization method, which is applied to a medical Internet of Things network system as described in any one of the first aspects, and the method includes: each of the medical Internet of Things devices sends the data to be synchronized in the first cache database to the local server for data synchronization; the local server updates the second storage database based on the synchronization data obtained from each of the medical Internet of Things devices, and forms the data to be synchronized cached in the second cache database based on the updated data; the local server sends the data to be synchronized in the second cache database to a removably deployed remote server for data synchronization, so that after the synchronization is successful, the remote server can update the third storage database based on the synchronization data.

[0015] The present disclosure provides a medical Internet of Things network system and a data synchronization method, the system includes: a plurality of medical Internet of Things devices configured locally; the application of each medical Internet of Things device is configured to be able to access and utilize the first storage database and the first cache database configured on the medical Internet of Things device through the device data service; the local server is connected to each of the medical Internet of Things devices through a local area network, and is configured with a second storage database and a second cache database. Using the storage and cache databases, the medical Internet of Things device can synchronize data with the local server, and the local server can synchronize data with the removably deployed remote server. Thus, the local device data is synchronized to the outside through the local server in the local area network, reducing the device data synchronization delay and stabilizing the network; the data is synchronized between the unified interface, i.e., the local server and the removably deployed remote server, reducing the number of parallel connections of the removably deployed remote server and reducing the pressure, and isolating the local device from the outside for security, thereby improving the important data security of the medical Internet of Things device. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 Shown is a structural schematic diagram of a medical Internet of Things network system in one embodiment of the present disclosure.

[0017] Figure 2 The diagram shows a flow chart of triggering data synchronization between a first communication object and a second communication object based on data changes of the first communication object in one embodiment of the present disclosure.

[0018] Figure 3 Shown is a schematic diagram of a process for triggering data synchronization between a medical IoT device and a local server based on data changes in the medical IoT device in one embodiment of the present disclosure.

[0019] Figure 4The diagram shows a flow chart of data synchronization between a first communication object and a second communication object based on power-on / reconnection triggering of the first communication object in one embodiment of the present disclosure.

[0020] Figure 5 Shown is a schematic diagram of a process for synchronizing data between a medical IoT device and a local server based on the startup / reconnection triggering of the medical IoT device in one embodiment of the present disclosure.

[0021] Figure 6 Shown is a flow chart of a method for data synchronization among a medical IoT device, a local server, and a remote server in one embodiment of the present disclosure.

[0022] Figure 7 Shown is a schematic diagram of the structure of a computer device in one embodiment of the present disclosure. DETAILED DESCRIPTION

[0023] The following is an explanation of the embodiments of the present disclosure by specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the information disclosed by the present disclosure. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in the present disclosure can also be modified or changed in various ways according to different viewpoints and application modules without departing from the spirit of the present disclosure. It should be noted that the embodiments in the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0024] The following is a detailed description of the embodiments of the present disclosure with reference to the accompanying drawings so that those skilled in the art can easily implement the present disclosure. The present disclosure can be embodied in many different forms and is not limited to the embodiments described herein.

[0025] In the representations of the present disclosure, the reference terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" and the like mean that the specific features, structures, materials, or characteristics represented in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. Moreover, the specific features, structures, materials, or characteristics represented may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples represented in the present disclosure and the features of different embodiments or examples, unless they are mutually contradictory.

[0026] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the representation of the present disclosure, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0027] In order to clearly describe the present disclosure, components not related to the description are omitted, and the same reference numerals are given to the same or similar components throughout the specification.

[0028] Throughout the specification, when a device is said to be "connected" to another device, this includes not only the case of "direct connection" but also the case of "indirect connection" by placing other elements therebetween. In addition, when a device is said to "include" a certain component, unless otherwise stated, it does not exclude other components, but means that other components may be included.

[0029] Although the terms first, second, etc. are used to represent various elements in this article in some examples, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first interface and the second interface, etc. are represented. Moreover, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising", "including" indicate that there are described features, steps, operations, elements, modules, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, modules, projects, kinds, and / or groups. The terms "or" and "and / or" used herein are interpreted as inclusive, or mean any one or any combination. Therefore, "A, B or C" or "A, B and / or C" means "any of the following: A; B; C; A and B; A and C; B and C; A, B and C". Exceptions to this definition occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0030] The technical terms used herein are only used to refer to specific embodiments and are not intended to limit the present disclosure. The singular form used herein also includes the plural form as long as the sentence does not clearly indicate the opposite meaning. The meaning of "including" used in the specification is to specify specific characteristics, regions, integers, steps, operations, elements and / or components, and does not exclude the existence or addition of other characteristics, regions, integers, steps, operations, elements and / or components.

[0031] Although not defined differently, all terms, including technical and scientific terms used herein, have the same meaning as those generally understood by those skilled in the art to which the present disclosure belongs. Terms defined in commonly used dictionaries are additionally interpreted as having meanings consistent with relevant technical literature and the message of the present disclosure, and shall not be overly interpreted as ideal or very formal meanings unless defined.

[0032] The present invention will be described in detail below through specific embodiments in conjunction with the accompanying drawings.

[0033] With the continuous development of smart medical technology, common medical electronic equipment, rehabilitation training equipment and other medical IoT devices may need to be connected to the IoT network to facilitate the synchronization and analysis of medical / rehabilitation data to improve the efficiency and accuracy of treatment and rehabilitation training. However, the IoT architecture based on the related technology, in which IoT devices are connected to the Internet through IoT gateways and then connected to remote servers, has many shortcomings, such as poor network stability, high network latency, weak network security performance, and high network maintenance and overhead costs.

[0034] In view of this, a medical Internet of Things network system is provided in an embodiment of the present disclosure, which solves the problems in the related technology by setting up a localized server to build a local area network with medical Internet of Things devices.

[0035] like Figure 1 As shown, a schematic diagram of the structure of a medical Internet of Things network system in one embodiment of the present disclosure is shown.

[0036] The medical Internet of Things network system includes: a plurality of medical Internet of Things devices 110 configured locally, and a local server 120.

[0037] In some embodiments, the medical IoT device 110 is implemented as a rehabilitation training device. The rehabilitation training device is used to help patients recover their physical functions. As an example, the rehabilitation training device may include one or more of physical therapy equipment, sports rehabilitation equipment, language rehabilitation equipment, cognitive and vocational rehabilitation equipment, auxiliary equipment, etc. Among them, the physical therapy equipment includes: one or more of electrotherapy equipment, ultrasonic therapy equipment, magnetic therapy equipment, and hot and cold compress equipment. The electrotherapy equipment includes low-frequency electrotherapy equipment, medium-frequency electrotherapy equipment, etc., which stimulate muscles through electric current to promote blood circulation and relieve pain. The ultrasonic therapy device uses the vibration and heating effect of ultrasonic waves to promote tissue repair and inflammation absorption. The magnetic therapy equipment, such as a magnetic therapy device, acts on the human body through a magnetic field to achieve the purpose of relieving pain and promoting blood circulation. The hot and cold compress equipment, cold compress is used to reduce swelling and pain, and hot compress helps to promote blood circulation and muscle relaxation. The sports rehabilitation equipment includes limb rehabilitation training equipment, such as one or more of limb training equipment, balance training equipment, gait trainer, etc. The language rehabilitation equipment includes one or more of language training equipment, pronunciation training equipment, swallowing training equipment, etc. The language training equipment provides language training tasks and assessment tools to help patients with speech disorders improve their pronunciation and expression skills. The pronunciation training equipment, such as a pronunciation corrector, is used to train specific pronunciation problems. The swallowing training equipment is used to help patients with swallowing disorders to train their swallowing functions. The cognitive and vocational rehabilitation equipment includes one or more of cognitive ability training equipment, hand function training equipment, and daily life ability training equipment. The cognitive ability training equipment includes memory training equipment, attention training equipment, etc., which are used to improve the patient's cognitive function. The hand function training equipment includes hand grippers, finger flexibility trainers, etc., which help restore hand function. The daily life ability training equipment includes simulated kitchen utensils, dressing trainers, etc., which help patients restore their ability to take care of themselves in daily life. The auxiliary equipment includes wheelchairs, crutches, orthotics, standing beds, commode chairs, etc., which provide mobility, correction, support, etc. for patients with limited mobility to provide convenience. Other rehabilitation equipment includes neuromuscular electrical stimulators, shock wave therapy devices, microwave therapy devices, ultrashort wave therapy devices, etc. Neuromuscular electrical stimulators are used to promote the recovery of nerve and muscle functions through electrical stimulation. The shock wave therapy device utilizes the physical effect of shock waves to treat muscle, bone and other diseases. The microwave therapy device and ultrashort wave therapy device are used to improve local blood circulation, promote inflammation absorption and so on.

[0038] The medical IoT device 110 is also integrated with a circuit module for realizing intelligent processing and IoT communication capabilities, including a processor, a memory, a communicator, etc. The processor includes an MCU, a CPU, a SoC, or an FPGA, and the memory includes a RAM and a ROM. The communicator includes a wired communication interface and / or a wireless communication interface. The processor can run a computer program stored in the memory to realize the required functions. For example, the function operation of the medical IoT device 110, the interaction with the external communication, etc.

[0039] It should be noted that the types of rehabilitation training equipment listed above are only examples. In actual scenarios, the types of rehabilitation training equipment can be changed and are not limited to the above examples. In addition, multiple rehabilitation training functions are integrated in the same rehabilitation training equipment, etc., which is not limited to the above examples. In some embodiments, the medical IoT device 110 can be implemented as an intelligent rehabilitation training device, such as an upper limb rehabilitation training system, an upper limb comprehensive rehabilitation training system, an upper limb three-dimensional rehabilitation training system, a digital operation training platform, a multi-sensory feedback electronic plug-in board, an exoskeleton upper limb rehabilitation training robot, a lower limb rehabilitation training system, a lower limb feedback training system, an ankle joint rehabilitation training system, an upper and lower limb active and passive rehabilitation training system, a scenario interactive training system, a cognitive rehabilitation assessment system and other equipment. One or more.

[0040] In addition, in addition to rehabilitation training equipment, various medical devices with IoT communication capabilities are also included in the category of the medical IoT device 110, which are not listed here one by one.

[0041] In some embodiments, the multiple medical IoT devices 110 can be arranged in different local scenarios, such as hospitals or rehabilitation sanatoriums, based on different types of medical treatment or rehabilitation training. Each medical IoT device 110 runs an application 111. The application 111 includes the software part of the device responsible for IoT, which can realize functions and logic such as data synchronization, storage, addition and deletion, and query. Each of the medical IoT devices 110 is also configured with a first storage database 113 and a first cache database 114 on the local machine, and the application 111 is configured to access and utilize the first storage database 113 and the first cache database 114 through the device data service 112. Among them, the first storage database 113 is used for the medical IoT device 110 to store / retrieve data, and the first cache database 114 is used for the application 111 on the medical IoT device 110 to cache data to be synchronized.

[0042] In some embodiments, the first storage database 113 can be implemented as a relational database system, such as at least one of MySQL, Oracle, SQL Server, DB2, and Postgres. In some embodiments, the first cache database 114 can be implemented as a key-value storage database, such as Redis and Riak, which can be used to quickly cache the data to be synchronized. The medical IoT device 110 can be configured to complete the available first storage database 113 and first cache database 114 by installing the corresponding software of the storage database and cache database and configuring parameters.

[0043] It can be understood that by setting up the first storage database 113 and the first cache database 114 locally in each medical IoT device 110, on the one hand, the security of the local data of the medical IoT device 110 can be guaranteed, and on the other hand, it is also convenient for the medical IoT device 110 to synchronize data with the outside.

[0044] The local server 120 is connected to each of the medical IoT devices 110 through a local area network, and is configured with a second storage database 121 and a second cache database 122. The local server 120 can be connected to each of the medical IoT devices 110 through a local gateway / router.

[0045] In some embodiments, the local server 120 and each of the medical IoT devices 110 are connected by wired communication through a wired local area network (LAN), such as through a router, a network cable, etc. Alternatively, the local server 120 and each of the medical IoT devices 110 are connected by wireless communication through a wireless local area network (WLAN), such as through a wireless network card, a router wireless function, etc.

[0046] It can be understood that the local server 120 and each of the medical IoT devices 110 communicate through a local area network to achieve data synchronization between each other, instead of through an external network (such as wide area Internet, mobile Internet, etc.), which effectively improves network stability, reduces network latency, and prevents external attacks with good security, and also reduces network maintenance and overhead costs.

[0047] In some embodiments, the second storage database 121 is used by the local server 120 to store / access data, and the second cache database 122 is used by the local server 120 to cache data to be synchronized. In some embodiments, the first storage database 113 can be implemented as a relational database system, such as at least one of MySQL, Oracle, SQL Server, DB2, and Postgres. In some embodiments, the first cache database 114 can be implemented as a key-value storage database, such as Redis and Riak, which can be used to quickly cache data to be synchronized. The local server 120 can configure the available first storage database 113 and first cache database 114 by installing the corresponding software of the storage database and cache database and configuring parameters.

[0048] In some embodiments, multiple medical IoT devices 110 can store the data to be synchronized in their respective first cache databases 114. When performing data synchronization, the data to be synchronized is read from the first cache database 114, and then sent to the local server 120 for data synchronization. In some embodiments, it is possible to determine whether the data synchronization is successful through some communication interaction mechanisms. For example, after the medical IoT device 110 sends all the data to be synchronized to the local server 120, it waits for the local server 120 to respond. If the local server 120 has a response indicating that the data synchronization is successful, it means that the data synchronization is successful. Alternatively, if the local server 120 does not respond after a preset number of transmissions (for example, 3 times) or the transmission time expires, it means that the data synchronization has failed and waits for the next synchronization. In some embodiments, when the data synchronization is completed, the data to be synchronized in the cache database can be deleted.

[0049] Through the above synchronization method, the application 111 on the medical IoT device 110 only needs to put the data to be synchronized into the first cache database 114. When synchronizing data, the cache data can be read from the first cache database 114 for synchronization. It is not necessary to distinguish whether the data needs to be synchronized, and it is not necessary to identify the synchronized data. In this way, the synchronization steps and processes can be effectively simplified, the system complexity can be reduced, and the system resource consumption can be reduced.

[0050] Alternatively, the local server 120 can also synchronize data with the medical IoT device 110 through the second cache database 122, that is, the local server 120 can send the data to be synchronized in the second cache database 122 to the medical IoT device 110 for data synchronization to update the corresponding data in the first storage database 113 of the medical IoT device 110.

[0051] In some embodiments, the medical IoT device 110 and the local server 120 can communicate encrypted. As an example, the encrypted communication can use a first encryption algorithm based on a digital certificate. The first encryption algorithm can be based on Secure Sockets Layer (SSL) / Transport Layer Security (TSL). The first encryption algorithm can be an asymmetric encryption algorithm. The asymmetric encryption algorithm uses a pair of keys (public key and private key), the public key can be freely distributed to anyone, and the private key can only be accessed by the owner. The public key is used for encryption, and the private key can be used to decrypt the content encrypted by the corresponding public key. In order to ensure the security of the public key, a digital certificate containing the public key of the certificate owner (Subject) can be obtained by self-signing or requesting a third-party organization (such as CA). In short, a digital certificate is actually an authentication of the public key of the user's identity signed by a trusted object. A digital certificate can ensure that the public key in the digital certificate is indeed the owner of the certificate, or the certificate can be used to confirm the identity of the other party. The SSL communication process is illustrated as follows: During the SSL handshake process, two communicating parties (such as the medical IoT device 110 and the local server 120) can exchange their respective digital certificates for verification by the other party. Once the verification is passed, one party can use the public key in the digital certificate to encrypt data, which can only be decrypted by the other party's private key. Alternatively, one party uses the public key in the digital certificate to encrypt a symmetric key based on a symmetric encryption algorithm for both parties to share, and sends it to the other party for decryption. The other party decrypts and obtains the symmetric key, and then the two parties communicate through the symmetric key.

[0052] In some embodiments, a remote server 130 that is connected to the local server 120 through an external network (such as wired Internet, wireless Internet) can also be deployed in the cloud. The removably deployed remote server 130 is configured with a third storage database 131 and a third cache database 132. In some embodiments, the third storage database is used by the remote server 130 to store / access data, and the third cache database 132 is used by the local server 120 to cache data to be synchronized. In some embodiments, the third storage database 131 can be implemented as a relational database system, such as at least one of MySQL, Oracle, SQL Server, DB2, and Postgres. In some embodiments, the third cache database 132 can be implemented as a key-value storage database, such as Redis and Riak, which can be used to quickly cache data to be synchronized. The remote server 130 can be configured to complete the available third storage database 131 and third cache database 132 by installing the corresponding software of the storage database and cache database and configuring parameters.

[0053] In some data synchronization scenarios, the local server 120 may send the data to be synchronized in the second cache database 122 to the remote server 130 for data synchronization. After receiving the synchronization data, the remote server 130 may update the data to the third storage database 131, and may give the local server 120 a response message indicating that the synchronization is successful. Alternatively, the remote server 130 may send the data to be synchronized in the third cache database 132 to the local server 120 for data synchronization. After receiving the synchronization data, the local server 120 may update the data to the second storage database 121, and may give the remote server 130 a response message indicating that the synchronization is successful. Optionally, the remote server 130 or the local server 120 may also determine that the data synchronization fails in response to the other party not responding for a preset number of times / duration when synchronizing data with the other party, so as to retain the data to be synchronized for the next synchronization.

[0054] Therefore, the local medical IoT device 110 and the local server 120 use local cache plus local storage to synchronize data, which can reduce the complexity of data identification and can conveniently and effectively synchronize all data to be synchronized. The cached data in the cache database are all data to be synchronized, and synchronization can be implemented directly.

[0055] In some embodiments, the local server 120 and the removably deployed remote server 130 are encrypted for communication. The encrypted communication may also use a second encryption algorithm based on a digital certificate. That is, the second encryption algorithm may also be implemented as an encryption communication algorithm based on the SSL / TSL protocol. In some embodiments, the second encryption algorithm may be the same as the first encryption algorithm. Alternatively, in other embodiments, the second encryption algorithm may be stricter than the first encryption algorithm. For example, the complexity of the encryption algorithm may be higher.

[0056] The communication connection and data synchronization between the medical IoT device 110 and the local server 120 are formed through the local area network, which improves the efficiency of device data synchronization and control instructions, reduces latency, and data synchronization in the local area network is the scenario used most of the time, so the external network overhead can be reduced. In addition, all applications in the local area network will not be affected by the external network. Using the network architecture, the unified access point of the medical IoT device 110 is the local server 120, all synchronized data is connected to the local server 120, and then the local server 120 is synchronized to the remote server 130, reducing the concurrency pressure of the remote server 130 (compared to all medical IoT devices 110 directly communicating with the remote server 130), reducing the occupation of IoT network resources, and reducing the computing pressure of the remote server 130. In contrast, the traditional Internet of Things solution will affect the experience when the external network is unstable or abnormal (the Internet of Things network is affected by weather, the number of nearby devices, etc.), while the local area network solution in the embodiment of the present disclosure will not be affected by the above external factors. When the external network is abnormal, the local area network is unobstructed to ensure the normal operation of all functions in the local area network. Therefore, the use of the medical Internet of Things network in the embodiment of the present disclosure does not require a large number of communication equipment to be deployed, reducing material costs and maintenance costs, and has low requirements on the number of nearby base stations, signal requirements, etc. All functions can be used in the local area network, improving system reliability.

[0057] In addition, the medical IoT device 110 in the local area network is connected to the local server 120, and the data to be synchronized can be synchronized to the local server 120 after encryption. The medical IoT device 110 itself is not directly connected to the Internet, does not directly participate in the data exchange of the Internet, and does not expose the connection interface to the outside. Compared with the way that the medical IoT device 110 directly interacts with the remote end through the Internet, the local medical IoT device 110 and the local server 120 in the embodiment of the present disclosure can adopt a private encrypted connection, which is isolated from the external network and is not susceptible to external network attacks and viruses, effectively improving the security of the medical IoT device 110. For medical devices, unlike general network devices, they are extremely related to the life safety of patients, and security is a focus that needs special attention.

[0058] It should be noted that the remote server 130 is selectively deployed, that is, it can be deployed or not deployed. Therefore, two deployment modes of device-local server 120-remote server 130 or device-local server 120 can be selected according to the scene requirements, which is more flexible.

[0059] In some embodiments, according to the characteristics of the original medical / rehabilitation data that the medical IoT device 110 needs to synchronize, the medical / rehabilitation result data that is converted into "data compression / reduction" can be processed and saved when the local server 120 performs corresponding data storage and update, so that when the local server 120 synchronizes data with the remote server 130, the data to be synchronized is also the medical / rehabilitation result data after "data compression / reduction", thereby further reducing the amount of data during external network transmission and effectively reducing the cost of using the external network. For example, when the medical IoT device 110 synchronizes data including the original medical / rehabilitation data to the local server 120, the data corresponding to the second storage database 121 updated by the local server 120 and the data synchronized to the remote server 130 include: medical / rehabilitation result data obtained based on the processing of the original medical / rehabilitation data. Taking rehabilitation training as an example, the original medical / rehabilitation data can exemplarily include patient x performing task a today, using training item c of rehabilitation training equipment b, running for d time, etc. Based on this, the medical / rehabilitation result data can be obtained, for example, including the completion progress e% of patient x performing task a.

[0060] In some embodiments, the local server 120 is used to provide web page access services to user terminals in the local area network to form a control path for the medical IoT device 110. Exemplarily, the user terminal can be implemented as a desktop, a laptop, a tablet computer or a smart phone. Local users (such as doctors, rehabilitation therapists, etc.) can access the local area network through user terminals, log in to the web page to access the local server 120, and perform functional operations of the medical IoT device 110, such as reading the information of the medical IoT device 110, controlling the medical IoT device 110, etc. In some embodiments, different local users can be assigned accounts representing their identities for logging in to the web page in advance, and these accounts can have different levels of control permissions, such as low-level accounts can only read data, and high-level accounts can control device functions, etc. Due to the use of a local area network, the network quality is good and the delay is small when the user performs functional operations on the medical IoT device 110 locally, which can effectively improve the efficiency and effect of the doctor / rehabilitation therapist's treatment / rehabilitation training of patients.

[0061] In some embodiments, the removably deployed remote server 130 is used to provide a web page access service to the local server 120 to a user terminal in communication connection. The server provides the Internet's Web-side functional service, and the local server 120 can be accessed through the Internet login Web page, and the medical IoT device 110 can be remotely controlled. In some embodiments, the control authority level of the account that can remotely control the medical IoT device 110 can be higher than the control authority level of the account that can locally control the medical IoT device 110, and the local server 120 can authenticate the accessed account and manage the corresponding assigned control authority level.

[0062] In some embodiments, the data synchronization action may include two cases.

[0063] Taking the medical IoT device 110, the local server 120, and the remote server as the communication objects, the first case may be that the data of the communication object changes, such as data modification, addition, deletion, etc., and the changed data needs to be synchronized to other communication objects as the data to be synchronized. Taking the medical IoT device 110 as an example, if the information of a patient is deleted on the medical IoT device 110, it is necessary to synchronize the corresponding deletion on the local server 120, and it may also be necessary to synchronize the corresponding deletion on the remote server 130.

[0064] like Figure 2 As shown, a schematic diagram of a process of triggering synchronization of data between a first communication object and a second communication object based on data changes of the first communication object in one embodiment of the present disclosure is shown. The first communication object and the second communication object are selected as any two of the medical IoT device 110, the local server 120, and the removably deployed remote server 130.

[0065] exist Figure 2 The process includes: Step S201: When data changes occur in the first communication object, data to be synchronized in the cache database is formed based on the modified data.

[0066] In some embodiments, if the medical IoT device 110 is the first communication object, when data modification occurs, the medical IoT device 110 can store the modified data in the first storage database 113 after data processing, and put it into the first cache database 114 as data to be synchronized.

[0067] Step S202: In response to maintaining a communication connection with the second communication object, the first communication object sends the data to be synchronized to the second communication object for data synchronization, so that when the data synchronization is successful, the second communication object updates the accessed storage database based on the data to be synchronized.

[0068] In some embodiments, if the medical IoT device 110 is the first communication object and the local server 120 is the second communication object, the medical IoT device 110 sends the data to be synchronized in the first cache database 114 to the local server 120; if the local server 120 receives the data to be synchronized, it can respond that the synchronization is successful and can update the data to be synchronized to the second storage database 121. If the local server 120 does not respond for more than a preset number of times / duration, the medical IoT device 110 can determine that the synchronization has failed.

[0069] Step S203: In response to successful data synchronization, the first communication object deletes the data to be synchronized.

[0070] In some embodiments, if the synchronization is successful, the data to be synchronized may not need to be retained; if the synchronization fails, the data to be synchronized is retained in the cache database until the next synchronization.

[0071] like Figure 3 As shown, it is a schematic diagram of a process of triggering data synchronization between the medical IoT device 110 and the local server 120 based on data changes of the medical IoT device 110 in one embodiment of the present disclosure.

[0072] In this embodiment, the medical IoT device 110 is exemplarily used as the first communication object and the local server 120 is used as the second communication object to demonstrate a preferred embodiment.

[0073] exist Figure 3 The process specifically includes: Step S301: the medical IoT device creates / deletes / modifies data; Step S302: the application performs data processing through the device data service based on the newly created / deleted / modified data; Step S303: storing the processed data in the first storage database; Step S304: caching the processed data into the first cache database to form data to be synchronized; After step S301, step S305 is executed: determining whether the local server 120 is connected; If connected, step S306 is executed: data synchronization is executed, and the data to be synchronized in the first cache database 114 is sent to the local server 120 for data synchronization. If not connected, the synchronization process ends.

[0074] Step S307: The local server 120 receives the synchronization data and returns a response.

[0075] Step S308: The local server 120 updates the second storage database 121 based on the received synchronization data.

[0076] In step S307, if the local server 120 has not completed data synchronization, there may be no response; or, if the local server 120 has not completed storage, the response may not contain content indicating successful synchronization (ie, the local server 120 has completed storage).

[0077] Correspondingly, step S309: the medical IoT device 110 determines whether a response is received; if not, executing step S311: resending the data to be synchronized; if so, executing step S310: determining whether the response contains synchronization success content.

[0078] If the judgment result of step S310 is yes, it indicates that the synchronization is successful, and the synchronization process ends, and step S313 is executed: deleting the successfully synchronized data to be synchronized in the first cache database 114; if the judgment result of step S310 is no, step S311 is executed.

[0079] After step S311, execute step S312: determine whether the number of retransmissions exceeds a preset number n (n is not limited, for example 3, 4, 5 times, etc.); if so, it indicates that the synchronization has failed, and the synchronization process is terminated, and the data to be synchronized is retained and waits for resynchronization; if not, return to step S301.

[0080] It can be seen that the above synchronization method does not distinguish the synchronized data, and does not need to identify whether the data is synchronized. It only needs to complete the synchronization of the cached data, which simplifies the synchronization steps and process, reduces system complexity, and reduces system resource consumption.

[0081] Taking the medical IoT device 110, the local server 120, and the remote server as the communication objects, the second situation may be that the communication object is powered on / reconnected. Taking the medical IoT device 110 as an example, when the medical IoT device 110 is powered on / restarted / reconnected with the local server 120 (it may be that the device or server is offline to online), the data to be synchronized that has not been synchronized needs to be synchronized to the local server 120.

[0082] like Figure 4 As shown, a schematic diagram of a process of triggering synchronization of data between a first communication object and a second communication object based on the power-on / reconnection of the first communication object in one embodiment of the present disclosure is shown. The first communication object and the second communication object are selected as any two of the medical IoT device 110, the local server 120, and the removably deployed remote server 130.

[0083] exist Figure 4 In the process, the process includes: Step S401: when the first communication object is powered on / reconnected, it is determined whether there is any unsynchronized data to be synchronized in the accessed cache database.

[0084] Step S402: In response to maintaining a communication connection with the second communication object, the first communication object sends the data to be synchronized to the determined second communication object for data synchronization, so that when the data synchronization is successful, the second communication object updates the accessed storage database based on the data to be synchronized; Step S403: In response to successful data synchronization, the first communication object deletes the data to be synchronized.

[0085] Take the medical IoT device 110 and the local server 120 as an example. Figure 5 As shown, it is a schematic diagram of the process of synchronizing data between the medical IoT device 110 and the local server 120 based on the power-on / reconnection triggering of the medical IoT device 110 in one embodiment of the present disclosure.

[0086] exist Figure 5 In the process, the process includes: Step S501: The medical IoT device 110 establishes a connection with the local server 120; Step S502: the application of the medical IoT device 110 reads the data to be synchronized that is still in the first cache database 114 through the device data service 112; Step S503: Determine whether the data to be synchronized is read. If yes, execute step S504; if no, end the synchronization process.

[0087] Step S504: Execute data synchronization, and send the data to be synchronized in the first cache database 114 to the local server 120 for data synchronization.

[0088] Step S505: The local server 120 receives the synchronization data and returns a response.

[0089] Step S506: the local server 120 updates the second storage database 121 based on the received synchronization data.

[0090] In step S505, if the local server 120 has not completed data synchronization, there may be no response; or, if the local server 120 has not completed storage, the response may not contain content indicating successful synchronization (ie, the local server 120 has completed storage).

[0091] Correspondingly, step S507: the medical IoT device 110 determines whether a response is received; if not, executing step S509: resending the data to be synchronized; if so, executing step S508: determining whether the response contains synchronization success content.

[0092] If the judgment result of step S508 is yes, it indicates that the synchronization is successful, and the synchronization process ends, and step S509 is executed: deleting the successfully synchronized data to be synchronized in the first cache database 114; if the judgment result of step S508 is no, step S509 is executed.

[0093] After step S509, execute step S510: determine whether the number of retransmissions exceeds a preset number n (n is not limited, for example 3, 4, 5 times, etc.); if so, it indicates that the synchronization has failed, and the synchronization process is terminated, and the data to be synchronized is retained and waits for resynchronization; if not, return to step S504.

[0094] It is understandable that, although the medical IoT device 110 and the local server 120 are used as the communication objects for synchronizing data in the above embodiments, the operation and principle of synchronizing data from the local server 120 to the medical IoT device 110 and the remote server 130 are the same. The process of synchronizing data from the remote server 130 to the local server 120, or the process of synchronizing data from the local server 120 to the medical IoT device 110 is similar to the above embodiments. Therefore, it will not be repeated.

[0095] like Figure 6 As shown, a schematic diagram of a data synchronization method in an embodiment of the present disclosure is shown.

[0096] Figure 6 The data synchronization method in the embodiment can be applied to the medical Internet of Things network system in the present embodiment in the previous embodiment, for example Figure 1 Medical Internet of Things network system.

[0097] exist Figure 6 In the figure, the process of the medical IoT device 110, the local server 120 and the remote server 130 performing two-to-two synchronous transfers on a certain synchronous data is shown. Since the specific technical principle of data synchronization in this embodiment has been specifically described in the previous embodiment, it will not be described in detail in the following description. Specifically, the process of the data synchronization method in this embodiment includes: Step S601: Each of the medical IoT devices 110 sends the data to be synchronized in the first cache database 114 to the local server 120 for data synchronization.

[0098] Step S602: The local server 120 updates the second storage database 121 based on the synchronization data obtained from each of the medical IoT devices 110, and forms the data to be synchronized cached in the second cache database 122 based on the updated data.

[0099] Step S603: the local server 120 sends the data to be synchronized in the second cache database 122 to the removably deployed remote server 130 for data synchronization, so that after the synchronization is successful, the remote server 130 can update the third storage database 131 based on the synchronized data.

[0100] Thus, the data of each medical IoT device 110 is synchronized to the local server 120 via the local area network, and the local server 120 can be used as the only interface to synchronize the data to the remote server 130 via the external network. Thus, in the process of the data to be synchronized from the medical IoT device 110 to the remote server 130, the data is synchronized locally via the local area network, which has the advantages of network stability, low latency and security, and then synchronized remotely via the external network, which has the advantages of unified interface, reducing the concurrent burden of the remote server 130, and reducing the external network overhead and the cost of setting up communication equipment.

[0101] like Figure 7 , which shows a schematic diagram of the structure of a computer device in one embodiment of the present disclosure.

[0102] The computer device 700 can be used to implement the medical Internet of Things equipment, local server or remote server in the above embodiments.

[0103] The computer device 700 includes a bus 701, a processor 702, and a memory 703. The processor 702 and the memory 703 can communicate with each other through the bus 701. The memory 703 can store a computer program or instruction. The processor 702 implements the functions of the medical IoT device, local server, or remote server in the previous embodiment by running the computer program or instruction in the memory 703.

[0104] The bus 701 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, although only one thick line is used in the figure, it does not mean that there is only one bus or one type of bus.

[0105] In some embodiments, the processor 702 may be implemented as a central processing unit (CPU), a microprocessing unit (MCU), a system on chip (System On Chip), or a field programmable logic array (FPGA). The memory 703 may include a volatile memory (Volatile Memory) for temporary storage of data when running a program, such as a random access memory (Random Access Memory, RAM).

[0106] The memory 703 may also include a non-volatile memory (non-volatile memory) for data storage, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid-state disk (SSD).

[0107] In some embodiments, the computer device 700 may further include a communicator 704. The communicator 704 is used to communicate with the outside. In a specific example, the communicator 704 may include one or a group of wired and / or wireless communication circuit modules. For example, the communicator 704 may include one or more of a wired network card, a USB module, a serial interface module, etc. The wireless communication protocols followed by the wireless communication module include: for example, near field communication (NFC) technology, infrared (IR) technology, Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Bluetooth (BT), Global Navigation Satellite System (GNSS), etc. One or more.

[0108] In an embodiment of the present disclosure, a computer-readable storage medium may also be provided, storing a computer program or instruction, which, when executed, implements the functions of the medical Internet of Things device, local server, or remote server in any of the previous embodiments.

[0109] That is, the method steps in the above embodiments are implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or are implemented as computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded via a network and to be stored in a local recording medium, so that the method represented herein can be stored in such software processing on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware (such as an ASIC or FPGA).

[0110] In the embodiments of the present disclosure, a computer program product may be provided, one or more computer programs or instructions, which, when executed, fully or partially execute the functions of the medical IoT device, local server or remote server in the embodiments of the present disclosure. The computer program product includes one or more computer programs or instructions.

[0111] The computer program or instructions may be stored in a readable storage medium or transmitted from one readable storage medium to another readable storage medium, for example, the computer program or instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The readable storage medium may be any available medium that can be accessed or a data storage device such as a server, data center, etc. that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; it may also be a semiconductor medium, such as a solid state drive. The computer readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0112] In summary, the present disclosure provides a medical Internet of Things network system and a data synchronization method, the system includes: multiple medical Internet of Things devices configured locally; the application of each medical Internet of Things device is configured to be able to access and utilize the first storage database and the first cache database configured on the medical Internet of Things device through the device data service; the local server is connected to each of the medical Internet of Things devices through a local area network, and is configured with a second storage database and a second cache database. Using the storage and cache databases, the medical Internet of Things device can synchronize data with the local server, and the local server can synchronize data with the removably deployed remote server. In this way, the local device data is synchronized to the outside through the local server in the local area network, reducing the device data synchronization delay and stabilizing the network; the data is synchronized between the unified interface, i.e., the local server and the removably deployed remote server, reducing the number of parallel connections of the removably deployed remote server and reducing the pressure, and isolating the local device from the outside to improve the important data security of the medical Internet of Things device.

[0113] The above embodiments are merely illustrative of the principles and effects of the present disclosure, and are not intended to limit the present disclosure. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present disclosure. Therefore, all equivalent modifications or changes made by those with ordinary knowledge in the technical field without departing from the spirit and technical ideas disclosed in the present disclosure shall still be covered by the protection scope of the present disclosure.

Claims

1. A medical Internet of Things network system, characterized in that: include: Multiple medical IoT devices configured locally; Each medical IoT device runs an application; the application is configured to be able to access and utilize a first storage database and a first cache database configured in the medical IoT device through a device data service; A local server is connected to each of the medical IoT devices through a local area network and is configured with a second storage database and a second cache database; the local server is configured to be connected to a removably deployed remote server through an external network; the removably deployed remote server is configured with a third storage database and a third cache database; Among them, the medical Internet of Things device, local server and remote server respectively use their own configured storage databases to store / read data, and use their own configured cache databases to cache data to be synchronized; and the first communication object can synchronize data to the second communication object to update the corresponding data in the storage database of the second communication object based on the synchronization data obtained from the first communication object; wherein, the first communication object and the second communication object are selected as any two of the medical Internet of Things device, the local server and the removably deployed remote server.

2. The medical Internet of Things network system according to claim 1, characterized in that: Synchronizing data between the first communication object and the second communication object includes: When data changes occur in the first communication object, the data to be synchronized in the cache database is formed based on the modified data; In response to maintaining a communication connection with the second communication object, the first communication object sends the data to be synchronized to the second communication object for data synchronization, so that when the data synchronization is successful, the second communication object updates the accessed storage database based on the data to be synchronized; In response to successful data synchronization, the first communication object deletes the data to be synchronized.

3. The medical Internet of Things network system according to claim 2, characterized in that: In response to the second communication partner not responding for a preset number of times / duration during data synchronization, the first communication partner determines that the data synchronization has failed.

4. The medical Internet of Things network system according to claim 1, characterized in that: Synchronizing data between the first communication object and the second communication object includes: When the first communication object is powered on / reconnected, it is determined whether there is any unsynchronized data to be synchronized in the accessed cache database; In response to maintaining a communication connection with the second communication object, the first communication object sends the data to be synchronized to the determined second communication object for data synchronization, so that when the data synchronization is successful, the second communication object updates the accessed storage database based on the data to be synchronized; In response to successful data synchronization, the first communication object deletes the data to be synchronized.

5. The medical Internet of Things network system according to claim 1, characterized in that: The local server is used to provide web page access services to user terminals within the local area network to form a control path for the medical IoT device; and / or, the removably deployed remote server is used to provide web page access services to the local server to user terminals connected in communication.

6. The medical Internet of Things network system according to claim 1, characterized in that: Encrypted communication between the medical IoT device and a local server; and / or encrypted communication between the local server and a removably deployed remote server.

7. The medical Internet of Things network system according to claim 6, characterized in that: The encrypted communication uses an encryption algorithm based on a digital certificate; or, the first encryption algorithm for encrypted communication between the local server and the removably deployed remote server is stricter than the second encryption algorithm for encrypted communication between the medical IoT device and the local server.

8. The medical Internet of Things network system according to claim 1, characterized in that: When the medical IoT device synchronizes data including original medical / rehabilitation data to the local server, the local server correspondingly updates the data in the second storage database and synchronizes data to the remote server including: medical / rehabilitation result data obtained based on the original medical / rehabilitation data.

9. The medical Internet of Things network system according to claim 1, characterized in that: After the data to be synchronized in the cache databases configured respectively, the medical IoT device, the local server and the removably deployed remote server successfully synchronize the data to be synchronized, the data to be synchronized are deleted.

10. A data synchronization method, characterized in that: Applied to the medical Internet of Things network system as described in any one of claims 1 to 9, the method comprises: Each of the medical IoT devices sends the data to be synchronized in the first cache database to the local server for data synchronization; The local server updates the second storage database based on the synchronization data obtained from each of the medical IoT devices, and forms the data to be synchronized cached in the second cache database based on the updated data; The local server sends the data to be synchronized in the second cache database to a removably deployed remote server for data synchronization, so that after the synchronization is successful, the remote server can update the third storage database based on the synchronized data.

Citation Information

Patent Citations

  • Data synchronization method and device based on Internet of Things

    CN110798444A

  • Distributed medical image data storage method based on cloud platform

    CN113111130A

  • Data backup method and device, storage medium and electronic equipment

    CN115567372A

  • Cloud intelligent manufacturing Internet of Things terminal and control method thereof

    CN116319912A

  • Network-based medical equipment control and data management system

    CN116963662A