Database construction method, information management method and related equipment

Abstract

The invention provides a database construction method of an intelligent medical system, an information management method and related equipment. Specifically, the database construction method comprises the following steps: constructing at least one standard attribute and at least one product model; the product model corresponds to one piece of Internet of Things equipment and is used for equipment registration of the Internet of Things equipment; the product model comprises basic information and at least one piece of attribute information; the attribute information maps the standard attribute. According to the technical scheme, the problems of complex registration and poor attribute normalization of the Internet of Things equipment are solved by using the standard attribute and the product model, and the storage efficiency and quality of the Internet of Things data are improved.

Description

Technical Field

[0001] The present disclosure relates to the technical field of Internet of Things, and in particular to a database construction method, an information management method and related equipment. Background Art

[0002] With the rapid development of Internet of Things (IoT) technology, the types and models of IoT devices in smart health care scenarios are increasing, generating a large amount of real-time and diversified data, such as physiological indicator monitoring data, environmental data, activity data, etc. Traditional relational databases are increasingly unable to meet the real-time and data processing efficiency requirements of smart health care scenarios. Summary of the invention

[0003] In view of this, the purpose of the present disclosure is to propose a database construction method, an information management method and related equipment for a smart medical system.

[0004] Based on the above purpose, the present disclosure provides a database construction method for a smart medical system, the database construction method comprising:

[0005] constructing at least one standard attribute; and

[0006] Construct at least one product model; wherein the product model corresponds to an IoT device and is used for device registration of the IoT device;

[0007] The product model includes basic information and at least one attribute information; the attribute information maps the standard attribute.

[0008] Based on the same inventive concept, this common embodiment also provides an information management method, the method comprising:

[0009] Obtaining reported data of the IoT device;

[0010] The reported data is parsed using a physical model and sent to a message queue; wherein the physical model is determined based on a preset product model;

[0011] Based on the preset publish-subscribe rules, the data in the message queue is processed.

[0012] Based on the same inventive concept, an embodiment of the present disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the database construction method or information management method as described in any one of the above is implemented.

[0013] Based on the same inventive concept, an embodiment of the present disclosure also provides a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to execute any of the above-mentioned database construction methods or information management methods.

[0014] Based on the same inventive concept, an embodiment of the present disclosure also provides a computer program product, including computer program instructions. When the computer program instructions are executed on a computer, the computer executes any of the above-mentioned database construction methods or information management methods.

[0015] From the above, it can be seen that the present disclosure provides a database construction method, an information management method and related equipment for a smart medical system. Specifically, the database construction method includes constructing at least one standard attribute and at least one product model; the product model corresponds to an IoT device and is used for device registration of the IoT device; the product model includes basic information and at least one attribute information; the attribute information maps the standard attribute. Such a technical solution uses standard attributes and product models to solve the problems of complex registration of IoT devices and poor attribute standardization, and improves the storage efficiency and quality of IoT data. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0017] Figure 1 A schematic diagram of the architecture of a health Internet of Things platform provided by an embodiment of the present disclosure is shown;

[0018] Figure 2 A structural schematic diagram of another health Internet of Things platform provided by an embodiment of the present disclosure is shown;

[0019] Figure 3 A schematic diagram showing an architecture of a data flow process provided by an embodiment of the present disclosure;

[0020] Figure 4A A schematic diagram showing the structure of a product model provided by an embodiment of the present disclosure is shown;

[0021] Figure 4B A schematic diagram of an interface for building a product model provided by an embodiment of the present disclosure is shown;

[0022] Figure 4C A functional display diagram of a product object model provided by an embodiment of the present disclosure is shown;

[0023] Figure 5A A schematic diagram of a storage model for time series data provided by the related art is shown;

[0024] Figure 5B A schematic diagram of a storage model for time series data provided by a disclosed embodiment is shown;

[0025] Fig. 6A A schematic diagram showing the structure of a device registration interface provided by an embodiment of the present disclosure is shown;

[0026] Figure 6B A schematic diagram showing the structure of a device details interface provided by an embodiment of the present disclosure is shown;

[0027] Figure 7 A schematic diagram showing the structure of a data processing management interface provided by an embodiment of the present disclosure is shown;

[0028] Figure 8 A schematic diagram showing a flow chart of a database construction method provided by an embodiment of the present disclosure;

[0029] Fig. 9 A schematic structural diagram of an electronic device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0030] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0031] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present disclosure should be understood by people with ordinary skills in the field to which the present disclosure belongs. The "first", "second" and similar words used in the embodiments of the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0032] As mentioned in the background technology section, with the advancement of Internet technology, the medical Internet of Things has developed rapidly. Figure 1 FIG. 1 is a schematic diagram showing the architecture of a health Internet of Things platform 100 provided by an embodiment of the present disclosure. Figure 1As shown, the health Internet of Things platform 100 includes a health Internet of Things device 101, a device connection layer 102, a data lake 103, an application connection layer 104, a health Internet of Things application 105, and a visualization operating system 106.

[0033] The health IoT device 101 refers to the terminal sensor of the health IoT, which can detect physiological parameters of the human body, such as heart rate, blood pressure, blood sugar and other indicators, environmental data, such as temperature, humidity, etc., activity data, such as number of steps, running time, etc., and can access the Internet to realize the collection and transmission of medical data. The device connection layer 102 is set between the health IoT device 101 and the data lake 103, and is used to transmit the health information collected by the health IoT device 101 to the data lake 103, so that the data lake 103 can store, manage and process the health information. The health IoT application 105 is connected to the data lake 103 through the application connection layer 104, and then uses the data stored, processed and managed by the data lake 103 to monitor, manage, analyze, warn and diagnose the health status of the target individual or group.

[0034] Furthermore, the data lake 103 is configured with a visualization operating system 106. The visualization operating system 106 can reduce the difficulty of operating the data lake 103, thereby facilitating improving the efficiency of data management and data processing.

[0035] The inventors of the present disclosure are based on Figure 1 The architecture of the health Internet of Things platform 100 shown in FIG. 1 provides a more specific health Internet of Things platform 200, such as Figure 2 Reference Figure 2 , the health Internet of Things platform 200 includes a device layer 201, an access layer 202, a data lake 203 and a business system 204. It should be understood that the device layer 201 includes at least one health Internet of Things device 101. The access layer 202 includes a device connection layer 102 and an application connection layer 104. The business system 204 corresponds to the health Internet of Things application 105.

[0036] Combine the following Figure 2 , the device layer 201, the access layer 202, the data lake 203 and the business system 204 are described in detail respectively.

[0037] There are differences in the communication methods between the health IoT device 101 and the Internet, such as wired connection, wireless connection, etc. Based on this, the devices of the device layer 201 can be divided into direct connection devices, gateway devices, and cloud platform devices according to the communication method. Based on the connection method of the device, the access layer 202 provides a variety of ways for devices to access the data lake 203, such as direct access, gateway access, and cloud-to-cloud docking. It should be noted that the communication method between the device layer 201 and the access layer 202 can be WiFi, NB-IoT, serial port, USB, RJ-4S, Zigbee, LoRa, cloud-to-cloud docking, etc., which is not limited in this disclosure.

[0038] At the same time, multiple communication protocols can be used between the device layer 201 and the access layer 202 to communicate to meet the communication needs of various devices in the device layer 201. For example, for directly accessed devices, HTTPS protocol, TCP Socket protocol, MQTT protocol, etc. can be used. For gateway accessed devices, multi-protocol gateways, MQTT protocol converters, etc. can be used to achieve communication. For cloud-to-cloud devices, HTTPS protocol, MQTT protocol, AMQP protocol, etc. can be used.

[0039] In addition, the access layer 202 also provides message communication services. For example, the attribute information uploaded by the device layer 201 in the data lake 203 is reported to the business system 204; for example, the instructions of the business system 204 are sent to the data lake 203 so as to be sent to the corresponding devices in the device layer 201 through the data lake 203.

[0040] The data lake 203 includes a storage engine module 2031, a registration center module 2032, a rule engine module 2033, and a data service module 2034, etc.

[0041] In some embodiments, the storage engine module 2031 includes a data storage submodule and a data calculation submodule, etc. The data storage submodule can store basic information, device information, dictionary information, product models, device timing data, etc.

[0042] In some embodiments, the registration center module 2032 includes a product model module and a device management module. The product model module can build a product model based on basic information, attribute information, data analysis, etc.; the device management module is used to manage device information, device status and device registration.

[0043] In some embodiments, the rule engine module 2033 is used to implement data forwarding and data standardization. The data forwarding method may include subscription push, data push, data processing, etc.; data standardization includes access standardization, storage standardization, forwarding standardization, etc.

[0044] In some embodiments, the data service module 2034 provides services such as application management, interface services, security authentication, application authentication, and statistical analysis. Among them, application management, application authentication, etc. are for applications involved in the business system 204, such as smart health care systems, health apps, public health systems, respiratory chronic disease management systems, etc.

[0045] The devices in the device layer 201 include basic information and attribute information, wherein the basic information is static information and does not change with time series, such as device identification, manufacturer, model, etc.; attribute information is a parameter indicator that the device can detect and can change with time series, for example, the attribute information of a height and weight scale includes height, weight and body mass index (Body Mass Index, abbreviated as BMI).

[0046] Based on the different objects detected by the devices in the device layer 201, they can be divided into blood glucose meters, blood pressure meters, height and weight meters, blood oximeters, etc. For the same detection object, different brands have different ways of presenting attribute information. For example, the unit of height in some height and weight meters is centimeters, and the unit of weight in some height and weight meters is meters. In addition, for different models of the same brand and the same type of product, the attribute information provided is also different. For example, the attribute information of the first product includes height and weight, and the attribute information of the second product includes height, weight and body mass index. The differences between devices not only increase the complexity of device registration, but also increase data access errors and delays caused by unclear attributes, reducing the efficiency and quality of data storage in the data lake 203.

[0047] In view of this, the embodiments of the present disclosure provide a database construction method, an information management method and related equipment for a smart medical system. Specifically, the database construction method includes constructing at least one standard attribute and at least one product model; the product model corresponds to an IoT device and is used for device registration of the IoT device; the product model includes basic information and at least one attribute information; the attribute information maps the standard attribute. This technical solution uses standard attributes and product models to solve the problems of complex IoT device registration and poor attribute standardization, and improves the storage efficiency and quality of IoT data.

[0048] In some embodiments, the rule engine 2033 is used to implement attribute standardization, and the attribute is standardized to obtain a standard attribute. Optionally, the standard attribute can be stored in a data dictionary (such as Figure 3As shown). Here, the attribute specification definition includes the attribute name, unit, step length, range, etc. For example, the physiological indicator height, the corresponding Chinese name height, the standard abbreviation Height, the unit cm, the step length 0.1, the data type double, the range 0 to 300. It should be noted that for the same attribute, it can correspond to multiple standard attributes, and different standard attributes can be distinguished by markers, so that the subsequent construction of the product model is to select the appropriate standard attribute. Those skilled in the art can understand that the method of pre-constructing standard attributes can greatly save the time of constructing product models and improve efficiency.

[0049] Attribute standardization is achieved through clear and unified attribute definitions. Attribute standardization helps to eliminate data ambiguity, ensure data accuracy and consistency, provide clear specifications for device access, make the access process smoother and more efficient, and reduce access errors and delays caused by unclear attributes. Standardized data storage formats facilitate data management and retrieval, improve the efficiency and quality of data storage, set unified standards for data forwarding, ensure the integrity and accuracy of data during transmission, and enable the recipient to quickly and accurately understand and process data.

[0050] In order to reduce the complexity of device registration, the product model module of the registration center 2032 can be used to manage product models. Based on the characteristics and capabilities of the product, an abstract model (i.e., product model) of a device with the same characteristics and capabilities is constructed to facilitate the data lake 203 to understand the basic information (corresponding characteristics) and attribute information (corresponding capabilities) of the product. In other words, the product model is used to describe the characteristics and capabilities of an IoT product. It should be noted that the same product model can be applicable to multiple devices. For example, XX company usually produces multiple products of model XX, and a product model can be constructed. Then, the company's devices of this model can all use the product model during subsequent registrations.

[0051] The following uses height and weight as an example to explain in detail how to build a product model. Figure 4A A structural schematic diagram of a product model provided by an embodiment of the present disclosure is shown. As shown in FIG4 , the height and weight scale HNH219 includes basic information and service capabilities. Among them, the basic information includes product ID, product code, product name (height and weight scale-Chengdu), protocol type (http / https), product type (height and weight scale), product model (HNH219), manufacturer name (XXX company), product picture, remarks, etc. Service capabilities correspond to attribute information, including height, weight and BMI.

[0052] Figure 4B A schematic diagram of an interface 400 for building a product model provided by an embodiment of the present disclosure is shown. Figure 4BThe interface for building a product model is shown in Figure 4A The basic information and attribute information of the product can be used to build the corresponding product model.

[0053] In some embodiments, the interface 400 for constructing a product model includes a first basic information editing area 401 and an attribute definition area 402. Through the first basic information editing area 401, basic information of the product model such as product name, protocol type, product type, manufacturer name, product code, product ID, etc. can be input or imported.

[0054] The attribute definition area 402 includes an attribute rule matching column 4021, which can be used to map the attribute information of the product with the pre-set standard attributes. The method of directly mapping the standard attributes not only achieves accurate description of the attribute information, but also saves the steps of setting the attribute information, thereby improving the convenience of operation. In addition, for different product models, standard attributes can be reused, which greatly reduces the repeated operations in the process of building the product model and improves the operation performance of the platform.

[0055] Clear and unambiguous product model definitions enable accurate descriptions of the capabilities and characteristics of equipment, reducing information ambiguity and uncertainty.

[0056] Based on the constructed product model, the physical model can be determined. Here, the physical model is a digital representation of entities in the physical space (such as sensors, blood glucose meters, height and weight meters, blood pressure meters, etc.) in the cloud, which can standardize the definition of the same type of equipment to facilitate the access of equipment and the connection of data. Figure 3 A schematic diagram showing an architecture of a data flow process provided by an embodiment of the present disclosure; Figure 4C FIG. 1 shows a functional display diagram of a product object model provided by an embodiment of the present disclosure. Figure 3 and Figure 4C As shown, the device at the device end 301 can report data using the access protocol 3041 (e.g., TCP), and the business application 303 interacts with the data lake 302 through the preset protocol 3042. The reported data can be formed into Json format data in the data parsing module. Based on the Json format data, the object model can extract relevant attribute information and at least part of the basic information to construct a data table for storage. It should be noted that after the product model is constructed in the data lake 302, the object model can be determined and synchronized to the device access module.

[0057] The data of various equipment products in smart health care scenarios is growing explosively. These data usually have time series characteristics and are called time series data. Based on this, it is crucial to build a data lake that can efficiently process and store time series data.

[0058] Figure 5AA schematic diagram of a storage model for time series data provided by the related technology is shown. This storage method is based on a relational database (such as MySQL, Oracle, etc.). When storing time series data, the data structure is row storage. All device data is placed in a table. Multiple measurement points of a single device need to be guaranteed by dataid to ensure data consistency. Data access only supports second-level writes. As the amount of data surges, the write performance becomes worse and worse. The performance is poor when processing high-concurrency writes and massive data queries, and it is difficult to meet the requirements of smart health care scenarios for real-time and data processing efficiency. In addition, the data model cannot clearly and intuitively represent the relationship between device data and product models.

[0059] Related technologies attempt to use NoSQL databases (such as HBASE, Cassandra, MongoDB, etc.) to store time series data. Although they can cope with the growth of data scale to a certain extent, they have limitations in data compression, distributed expansion, and complex queries, poor real-time computing, large computing memory and CPU overhead, and insufficient optimization of time series data algorithm processing. For example, OpenTSDB is a commonly used time series database, but it is relatively bulky. In the face of the continuous iteration of business needs and the continuous increase in data volume, its limitations gradually become apparent.

[0060] In addition, Hadoop big data processing can also be used to store time series data, but it has many complex components, a bloated architecture, supports distribution but has low single-node efficiency, and has high hardware and manpower investment costs.

[0061] In order to better meet the characteristics of high reporting frequency, large data volume, and strong real-time performance of health time series data, and to break the limitations of the original IoT data lake and industry pain points, it is inevitable to choose a reasonable time series database to build an IoT data lake.

[0062] Figure 5B A schematic diagram of a storage model for time series data provided by the disclosed embodiment is shown. Figure 5B As shown, the time series data is stored in the TDengine database. Specifically, the TDengine time series data model constructs a super table 501 for one product and a sub table 502 for one device. The super table can be constructed based on the aforementioned product model. Here, the super table can record the attribute information and configuration tags in the product model, such as Metrics: ts timestamp, weight double, height double, bmi double; Tags: dataID bigint, deviceID bigint, so that the super table can be used as a template for all similar device data. It should be noted that, considering that there is a lot of basic information, part of it can be selected to build a super table, such as product ID as a product identifier, and the present disclosure does not limit this.

[0063] The pre-established super table greatly improves the efficiency and response speed of data storage and can quickly meet the needs of data processing. In addition, the super table schema built based on the measurement point information (corresponding attribute information) and product identification helps to achieve structured and standardized storage of data, providing a solid foundation for subsequent data management, analysis and application, thereby improving the performance and reliability of the entire system.

[0064] Subtable 502 may be created after device registration. Figure 5B As shown, subtable 502 includes a label row 5021 and a time series data row 5022. Label row 5021 includes multiple attribute indicators, such as body weight 5023, weight 5024, BMI 5025, etc. It should be noted that the label of label row 5021 can be determined based on the attribute information recorded in super table 501 and the configured label (such as deviceID). Each time series data row 5022 stores the specific values ​​of the attribute indicators at different times. Different devices of the same product model are set with different subtables. For example, device 22798 sets subtable 22798, and device 12799 sets subtable 12799 (such as Figure 5B shown).

[0065] This data structure simplifies data modeling, reduces data redundancy, and facilitates cross-device aggregate queries. Columnar storage (different columns of the same row store different attribute data) is very suitable for efficient storage and query of time series data. This storage method reduces disk I / O and can significantly improve query speed and efficiency for IoT applications that need to frequently access and analyze large amounts of historical data. In addition, such a database structure can intuitively and clearly represent the relationship between device data and product models, and automatically maintain timestamp indexes, which makes queries based on time ranges very fast.

[0066] In summary, the design and optimization of the TDengine time series database achieves optimizations in multiple technical aspects such as data access, storage methods, data modeling, and index management, providing an efficient, reliable, and flexible solution for processing large-scale time series data.

[0067] Before establishing the sub-table 502, device registration is required. Fig. 6A FIG. 1 is a schematic diagram showing a structure of a device registration interface provided by an embodiment of the present disclosure. Fig. 6AAs shown, the device registration interface 600A includes a second basic information editing area 601. It should be noted that, using the visual operating system 106, the device registration interface 600A can be displayed based on the operation instruction, and the specific operation method is not limited by this disclosure. The second basic information editing area 601 can edit the device name, the affiliated application (from the business system 204), the device identification (such as device ID, device SN, etc.), the product name, etc., and use the device registration interface 600A to realize the functions of single device registration, batch device registration, product binding, and operation status monitoring.

[0068] After the device registration is completed, the aforementioned sub-table 502 may be constructed to use the sub-table 502 to store the uploaded time series data of the device.

[0069] In some embodiments, the device registration interface 600A further displays a details button. Clicking the details button allows you to view detailed information about the device registration. Figure 6B A schematic diagram of the structure of a device details interface 600B provided in an embodiment of the present disclosure is shown. Figure 6B As shown, the device details interface 600B includes a basic information display area 602 and a data reporting display area 603. The basic information display area 602 can be used to view the device registration information. If error information is found, it can be modified by deleting and re-registering.

[0070] The data reporting display area 603 includes at least one indicator display window 6031. For example, if the device is a blood pressure monitor, the indicator display window 6031 can display systolic pressure, diastolic pressure, heart rate, etc. After the device registration is completed, the data can be reported to the data lake. The object model in the data lake can process the reported data and extract time series data, which can be displayed in the data reporting display area 603. In this way, it is easy and convenient to verify whether the device registration and device access are successful.

[0071] In some embodiments, the data report display area 603 may further include a refresh button. Through the refresh button, the time series data displayed in the data report display area 603 may be refreshed to display the latest reported data.

[0072] Based on the super table 501 and the sub table 502, large-scale time series data reported by IoT devices can be stored. Considering the data characteristics of different devices, the embodiment of the present disclosure also provides a simple and convenient data processing method. Optionally, the data processing method can be implemented by the rule engine module 2033.

[0073] In some embodiments, a device information data table is established based on a preset relational database, and the device information data table is used to store registered device information, such as basic information. Figure 3 As shown, the device information 3051 is sent to the data table in MySQL of the platform data storage unit included in the storage engine 2031. The platform data storage unit also includes a redis database, which can be used as a cache. When the data service module needs device information, it can query the cache 3052. If the redis database does not find the target device information, it can query the database 3053. If the device information exists in MySQL, it can be synchronized to the redis database.

[0074] The adopted technical solution stores the basic information and attribute data (corresponding to time series data) of the registered devices in different databases respectively, thereby isolating the time series data from the platform data (corresponding to the basic information), which helps to ensure the safety and reliability of the data.

[0075] Figure 7 FIG. 7 is a schematic diagram showing a structure of a data processing management interface 700 provided by an embodiment of the present disclosure. Figure 7 As shown, the data processing management interface 700 includes a basic information setting area 701 and a script information editing area 702. Based on the third basic information setting area 701, the basic information of the script edited in the script information editing area 702 can be edited, such as script coding, product selection, etc.

[0076] In some embodiments, the script information editing area 702 includes a script editing bar 7021, a parameter editing bar 7022, an operation result bar 7023, a test button ( Figure 7 7021). The script editing bar 7021 is used to modify the script that fails the test.

[0077] By using the data processing management interface 700, functions such as building data processing scripts for editing, script deployment, and real-time processing of designated product data can be realized. Based on the assigned application set for the designated product, the processed data can be sent to the designated assigned application.

[0078] In the face of various complex business scenarios, the data processing management interface 700 can provide dynamic rule configuration, modify the rules at runtime without interrupting the service, implement message filtering and processing functions, and convert the message flow reported by the device into the data required by the business application.

[0079] Combine the following Figure 3, the flow process of the reported data in the embodiment of the present disclosure is exemplarily described. The registered device in the device end 301 reports data, and the object model can process the reported data and send it to the message queue in the message communication.

[0080] For messages in the message queue, different processing methods can be used based on preset rules. Exemplarily, if the message is subscribed, it can enter the time series database, and the data processing module can call the matching script for data processing. Exemplarily, if the message is not subscribed, it can be written to the time series database for storage. It should be noted that the data stored in the time series database can be reprocessed by the data processing module. Exemplarily, the application of business application 303 can also directly call the matching interface to directly obtain the messages in the message queue.

[0081] In summary, the information management method provided by the embodiment of the present disclosure creates a clear and standardized data open platform through attribute standardization and product model management, solves the problems of complex device registration and non-standard attributes, and effectively improves device access efficiency and data quality. The TDengine time series data model is used to achieve super table and sub-table adaptation and improve query and storage efficiency. In addition, through cooperation with relational data, attribute data and basic information data are stored separately to ensure security and reliability. Finally, a visual rule engine is constructed to support custom data processing and orchestration, provide powerful script computing capabilities, realize message filtering, processing and circulation, improve data forwarding flexibility, support dynamic rule configuration, and greatly improve data forwarding flexibility and ease of use.

[0082] Such technical solutions will help improve the data processing efficiency and quality of medical and health equipment, provide strong support for precision medicine and health management, and are expected to be widely used in medical institutions, health care institutions, etc., creating huge social and economic value.

[0083] It should be noted that the method of the embodiment of the present disclosure can be performed by a single device, such as a computer or a server. The method of the present embodiment can also be applied in a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present disclosure, and the multiple devices will interact with each other to complete the described method.

[0084] It should be noted that the above describes some embodiments of the present disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0085] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure also provides a method for constructing a database of a smart medical system. Figure 8 The following is a flow chart showing a method for constructing a database of a smart medical system provided by an embodiment of the present disclosure. Figure 8 As shown, the database construction method specifically includes:

[0086] S801: Construct at least one standard attribute; and

[0087] S803: Construct at least one product model; wherein the product model corresponds to an IoT device and is used for device registration of the IoT device;

[0088] The product model includes basic information and at least one attribute information; the attribute information maps the standard attribute.

[0089] Optionally, the attribute information of the product model includes attribute names, and attribute names of standard attributes can be matched based on the attribute names, thereby achieving accurate mapping.

[0090] In some embodiments, the standard attribute includes an attribute name, and the basic information includes a product identifier, such as a product ID; the information management method further includes:

[0091] refer to Figure 5B , based on the product model, constructing a first data table (corresponding to super table 501) in a preset time series database; wherein the first data table includes the product identifier and at least one attribute name;

[0092] Based on the device information and the corresponding product identification of the IoT device, determine a matching first data table and construct a second data table (corresponding to subtable 502); wherein the device information and the corresponding product identification are obtained through device registration;

[0093] The second data table is a subtable of the first data table, and is used to store the time series data uploaded by the IoT device; wherein the time series data includes the attribute name.

[0094] In some embodiments, labels (eg, attribute names) of the second data table are determined by the first data table.

[0095] In some embodiments, the label of the second data table (corresponding to the sub-table 502 ) includes a timestamp and at least one attribute name.

[0096] In some embodiments, the preset time series database is a TDengine database; and the first data table is a super table.

[0097] In some embodiments, it also includes:

[0098] refer to Figure 3 Based on the device information, a third data table is constructed in a preset relational database (such as MySQL); wherein the third database is used to store the device information.

[0099] The present disclosure also provides an information management method. Specifically, the method includes:

[0100] like Figure 3 As shown, obtaining the reported data of the IoT device;

[0101] The reported data is parsed using a physical model and sent to a message queue; wherein the physical model is determined based on a preset product model;

[0102] Based on the preset publish-subscribe rules, the data in the message queue is processed.

[0103] In some embodiments, the basic information includes a product identification; before obtaining the reported data of the Internet of Things device, the information management method further includes:

[0104] like Fig. 6A As shown, the belonging application information, device information and corresponding product identification of the IoT device are obtained; here, the above information can be obtained with the help of the device registration interface 600A;

[0105] Based on the product identification, a product model is determined; here, the product model includes the product identification, so based on the product identification, a corresponding product model can be matched;

[0106] Device registration is performed based on the home application information, the device information and the product model.

[0107] In some embodiments, it also includes:

[0108] Obtain and display the data in the message queue on the device details interface (such as clicking a details button) based on the device details display request (such as clicking a details button). Figure 6BAs shown); wherein, the data in the message queue includes the timing data in the reported data.

[0109] In some embodiments, it also includes:

[0110] refer to Figure 7 , obtain and display the data processing management interface 700 based on the data processing management request; wherein, the data processing management interface includes a basic information setting area 701 and a script information editing area 702; the script in the script information editing area 702 is applicable to the product selected in the basic information setting area 701.

[0111] In some embodiments, reference Figure 7 , the script information editing area 702 includes a script editing bar 7021; the information management method also includes:

[0112] Script parameters and test requests are obtained, and the script in the script editing bar is tested using the script parameters; wherein the script that passes the test is used to process the time series data uploaded by the IoT device.

[0113] In some embodiments, the IoT device corresponds to a home application; and the processing of the data in the message queue specifically includes:

[0114] Send the data in the message queue to the second data table corresponding to the IoT device for storage (corresponding data writing); or

[0115] Calling a script that matches the IoT device to process the data and forward it to a matching home application (corresponding to data subscription); or

[0116] The corresponding data in the message queue is sent to the home application through a matching interface.

[0117] In some embodiments, the information management method is applied to a smart medical Internet of Things.

[0118] The above embodiment corresponds to the corresponding information management method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0119] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the database construction method or information management method described in any of the above embodiments is implemented.

[0120] Fig. 9A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0121] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0122] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0123] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0124] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0125] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0126] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0127] The electronic device of the above embodiment is used to implement the corresponding information management method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0128] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the database construction method or information management method described in any of the above embodiments.

[0129] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0130] The computer instructions stored in the storage medium of the above embodiments are used to enable the computer to execute the database construction method or information management method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0131] Based on the same inventive concept, corresponding to the information management method described in any of the above embodiments, the present disclosure also provides a computer program product, which includes computer program instructions. In some embodiments, the computer program instructions can be executed by one or more processors of a computer so that the computer and / or the processor execute the database construction method or the information management method. Corresponding to the execution subject corresponding to each step in each embodiment of the information management method, the processor that executes the corresponding step can belong to the corresponding execution subject.

[0132] The computer program product of the above embodiment is used to enable the computer and / or the processor to execute the database construction method or information management method described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0133] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples. Based on the concept of the present disclosure, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of simplicity.

[0134] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present disclosure difficult to understand, the known power / ground connections to the integrated circuit (IC) chips and other components may or may not be shown in the provided figures. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure will be implemented (that is, these details should be fully within the scope of understanding of those skilled in the art). Where specific details (e.g., circuits) are set forth to describe exemplary embodiments of the present disclosure, it is apparent to those skilled in the art that the embodiments of the present disclosure can be implemented without these specific details or with changes in these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0135] Although the present disclosure has been described in conjunction with specific embodiments of the present disclosure, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0136] The embodiments of the present disclosure are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A method for constructing a database of a smart medical system, characterized in that: The database construction method comprises: constructing at least one standard attribute; and Construct at least one product model; wherein the product model corresponds to an IoT device and is used for device registration of the IoT device; The product model includes basic information and at least one attribute information; the attribute information maps the standard attribute.

2. The database construction method according to claim 1, characterized in that: The standard attribute includes an attribute name, and the basic information includes a product identifier; the database construction method further includes: Based on the product model, construct a first data table in a preset time series database; wherein the first data table includes the product identifier and at least one attribute name; Based on the device information and the corresponding product identification of the IoT device, determining a matching first data table and constructing a second data table; wherein the device information and the corresponding product identification are obtained through device registration; The second data table is a subtable of the first data table, and is used to store the time series data uploaded by the IoT device; wherein the time series data includes the attribute name.

3. The database construction method according to claim 2, characterized in that: The label of the second data table is determined by the first data table; and / or, The label of the second data table includes a timestamp and at least one attribute name.

4. The database construction method according to claim 2, characterized in that: The preset time series database is a TDengine database; the first data table is a super table.

5. The database construction method according to claim 2, characterized in that: Also includes: Based on the device information, a third data table is constructed in a preset relational database; wherein the third database is used to store the device information.

6. An information management method, characterized in that: include: Obtaining reported data of the IoT device; The reported data is parsed using a physical model and sent to a message queue; wherein the physical model is determined based on a preset product model; Based on the preset publish-subscribe rules, the data in the message queue is processed.

7. The information management method according to claim 6, characterized in that: Before obtaining the reported data of the Internet of Things device, the information management method further includes: Obtaining the belonging application information, device information and corresponding product identification of the IoT device; Based on the product identification, matching a corresponding product model; Device registration is performed based on the home application information, the device information and the product model.

8. The information management method according to claim 6, characterized in that: Also includes: Obtain and display the data in the message queue on the device details interface based on the device detailed display request; wherein the data in the message queue includes the time series data in the reported data.

9. The information management method according to claim 6, characterized in that: Also includes: Obtaining and displaying a data processing management interface based on a data processing management request; wherein the data processing management interface includes a basic information setting area and a script information editing area; The script in the script information editing area is applicable to the product selected in the basic information setting area.

10. The information management method according to claim 9, characterized in that: The script information editing area includes a script editing bar; The information management measures also include: Script parameters and test requests are obtained, and the script in the script editing bar is tested using the script parameters; wherein the script that passes the test is used to process the time series data uploaded by the IoT device.

11. The information management method according to claim 6, characterized in that: The IoT device corresponds to a home application; and the processing of the data in the message queue specifically includes: Send the data in the message queue to the second data table corresponding to the IoT device for storage; or Calling a script that matches the IoT device to process the data and forward it to a matching home application; or The corresponding data in the message queue is sent to the home application through a matching interface.

12. The information management method according to claim 6, characterized in that: The information management method is applied to the smart medical Internet of Things.

13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable by the processor, characterized in that: The processor implements the database construction method according to any one of claims 1 to 5 or the information management method according to any one of claims 6 to 12 when executing the computer program.

14. A non-transitory computer-readable storage medium, characterized in that: The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the database construction method according to any one of claims 1 to 5 or the information management method according to any one of claims 6 to 12.

15. A computer program product, characterized in that The method comprises computer program instructions, which, when executed on a computer, enable the computer to execute the database construction method according to any one of claims 1 to 5 or the information management method according to any one of claims 6 to 12.

Images