CN114884987A

CN114884987A - Method, device and storage medium for acquiring equipment state information

Info

Publication number: CN114884987A
Application number: CN202210454071.3A
Authority: CN
Inventors: 张金龙; 郭秋雨
Original assignee: Qingdao Hisense Medical Equipment Co Ltd
Current assignee: Qingdao Hisense Medical Equipment Co Ltd
Priority date: 2022-04-24
Filing date: 2022-04-24
Publication date: 2022-08-09
Anticipated expiration: 2042-04-24
Also published as: CN114884987B

Abstract

The embodiment of the application discloses a method, a device and a storage medium for acquiring equipment state information, and belongs to the technical field of medical informatization. In the embodiment of the application, the main thread of the server actively acquires the device state information at preset time intervals based on the subscription device type provided by the monitoring device in advance, and pushes the acquired device state information of the medical device to the monitoring device, so that when some monitoring devices simultaneously monitor the same medical device or the same type of medical device, compared with a mode that each monitoring device actively requests the device state information from the server, the server can be prevented from repeatedly acquiring the device state information of some medical devices, and the processing resources of the server can be saved.

Description

Method, device and storage medium for acquiring equipment state information

Technical Field

The present application relates to the field of medical informatization technology, and in particular, to a method, an apparatus, and a storage medium for acquiring device status information.

Background

With the development of medical informatization technology, in a medical informatization system, one server can be connected with a large number of medical devices. The medical equipment state information can be monitored to judge whether each medical equipment is in a normal operation state. Based on this, the monitoring device needs to acquire the device status information of each medical device in real time, so as to execute corresponding operations according to the device status information, thereby ensuring that each medical device can normally operate.

Disclosure of Invention

The embodiment of the application provides a method, a device and a storage medium for acquiring equipment state information, which can reduce the time for acquiring the equipment state information of a plurality of medical equipment. The technical scheme is as follows:

in one aspect, a method for obtaining device state information is provided, and is applied to a main thread in a server, and the method includes:

obtaining a subscription device type set, wherein the subscription device type set comprises a plurality of subscription device types, and each subscription device type corresponds to at least one monitoring device in a plurality of monitoring devices;

acquiring equipment state information of medical equipment corresponding to each subscription equipment type in the subscription equipment type set based on configured equipment address information of a plurality of medical equipment at preset time intervals;

and pushing the obtained equipment state information to the plurality of monitoring equipment according to the subscription equipment type set.

Optionally, the obtaining the set of subscribed device types includes:

respectively establishing long connections with the plurality of monitoring devices;

receiving subscription information of corresponding monitoring equipment through long connection with each monitoring equipment, wherein the subscription information comprises a subscription equipment type;

and removing the duplicate of the subscription equipment types in the received subscription information of the plurality of monitoring equipment to obtain the subscription equipment type set.

Optionally, after acquiring the set of subscribed device types, the method further includes:

when updated subscription information of a target monitoring device is received through long connection with the target monitoring device, searching whether a target subscription device type included in the updated subscription information is included in the subscription device type set, wherein the target monitoring device is any one of the plurality of monitoring devices;

if the target subscribed device type is not included in the set of subscribed device types, updating the set of subscribed device types based on the target subscribed device type.

Optionally, the subscription information includes a subscription device type;

the acquiring device state information of the medical device corresponding to the subscribed device type in the subscribed device type set based on the configured device address information of the plurality of medical devices includes:

determining, from the plurality of medical devices, a plurality of target medical devices that match a subscribed device type of the set of subscribed device types;

and acquiring the device state information of the plurality of target medical devices through a plurality of sub-threads based on the device address information of the plurality of target medical devices, wherein each sub-thread in the plurality of sub-threads is used for acquiring the device state information of one medical device.

Optionally, the acquiring device status information of the plurality of target medical devices through a plurality of sub-threads based on the device address information of the plurality of target medical devices includes:

sequentially acquiring the plurality of sub-threads from the thread resource pool, and distributing a query task to the acquired target sub-thread when one sub-thread is acquired, wherein the query task comprises equipment address information of a target medical device and is used for indicating the target sub-thread to send a state query request to the corresponding medical device based on the received equipment address information, and storing the equipment state information to a database after the equipment state information of the corresponding medical device is acquired;

and acquiring the device state information of the target medical devices obtained by the sub threads from the database.

Optionally, before the obtaining the device state information of the plurality of target medical devices obtained by the plurality of child threads from the database, the method further includes:

detecting whether a count value of a counter is 0, wherein an initial count value of the counter is equal to the number of the target medical devices, and when any sub-thread in the plurality of sub-threads completes the distributed query task, the count value of the counter is decreased by 1;

and when the counting value of the counter is detected to be 0, executing the step of acquiring the device state information of the target medical devices obtained by the sub threads from the database.

Optionally, the method further comprises:

and when the target sub-thread is detected to finish the distributed query task, recovering the target sub-thread to the thread resource pool.

Optionally, the pushing the obtained device state information to the multiple monitoring devices according to the subscription device type set includes:

and pushing the device state information of the target medical device corresponding to the corresponding subscribed device type to at least one monitoring device corresponding to each subscribed device type in the subscribed device type set.

In another aspect, an apparatus for acquiring device status information is provided, the apparatus including:

the device comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a subscribed device type set, the subscribed device type set comprises a plurality of subscribed device types, and each subscribed device type corresponds to at least one monitoring device in a plurality of monitoring devices;

the second obtaining module is used for obtaining the equipment state information of the medical equipment corresponding to each subscribed equipment type in the subscribed equipment type set at intervals of preset time based on the configured equipment address information of the plurality of medical equipment;

and the sending module is used for pushing the obtained equipment state information to the plurality of monitoring equipment according to the subscription equipment type set.

Optionally, the first obtaining module is further configured to:

Optionally, the apparatus is further configured to:

Optionally, the subscription information includes a subscription device type;

the second obtaining module is further configured to:

Optionally, the second obtaining module is further configured to:

Optionally, the apparatus is further configured to:

and when the counting value of the counter is detected to be 0, triggering the second acquisition module to execute the step of acquiring the device state information of the target medical devices acquired by the sub-threads from the database.

Optionally, the apparatus is further configured to:

Optionally, the sending module is configured to:

In another aspect, an apparatus for obtaining device status information is provided, where the apparatus is applied to a main thread in a server, and the apparatus includes a processor, where the main thread runs in the processor, and the main thread is configured to:

Optionally, the main thread is mainly used for:

Optionally, the main thread is further configured to:

Optionally, the subscription information includes a subscription device type, and the main thread is further configured to:

Optionally, the main thread is further configured to:

In another aspect, a computer-readable storage medium is provided, in which a computer program is stored, and the computer program, when executed by a computer, implements the steps of the method for acquiring device status information described above.

In another aspect, a computer program product comprising instructions is provided, which when run on a computer, causes the computer to perform the steps of the above-described method of obtaining device status information.

The beneficial effects brought by the technical scheme provided by the embodiment of the application at least comprise:

in the embodiment of the application, the main thread of the server actively acquires the device state information at preset time intervals based on the subscription device type provided by the monitoring device in advance, and pushes the acquired device state information of the medical device to the monitoring device, so that when some monitoring devices simultaneously monitor the same medical device or the same type of medical device, compared with a mode that each monitoring device actively requests the device state information from the server, the server can be prevented from repeatedly acquiring the device state information of some medical devices, and the processing resources of the server can be saved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a system architecture diagram according to a method for acquiring device status information provided in an embodiment of the present application;

fig. 2 is a flowchart of a method for acquiring device status information according to an embodiment of the present disclosure;

fig. 3 is a flowchart of another method for acquiring device status information according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of an apparatus for acquiring device status information according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a server for acquiring device status information according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Before explaining the embodiments of the present application in detail, an application scenario of the embodiments of the present application will be described.

With the development of medical information technology, in a medical information system, a server may be connected to a large number of medical devices, for example, in a teleoperation teaching system, the server and a plurality of terminal devices connected to the server and installed in a teaching chamber are included, and the plurality of terminal devices are used for decoding and playing video data in the operating chamber captured by a camera. Generally, for a plurality of medical devices connected to a server, device state information of the plurality of medical devices may be monitored by a monitoring device, and then whether each medical device is in a normal operation state is determined according to the obtained device state information of the medical device, so that when a certain medical device is in an abnormal operation state, corresponding operation is performed on the medical device.

In the related art, there may be a plurality of monitoring devices for monitoring medical devices, wherein one monitoring device may monitor a plurality of medical devices, and there may also be an overlap between the medical devices monitored by different monitoring devices. The monitoring devices can send state query requests of the medical devices monitored by the monitoring devices to the server, and the server can sequentially acquire the device state information of each medical device according to the received state query requests of the medical devices after receiving the state query requests sent by the monitoring devices. In this case, if the medical devices are in good operation, the server can acquire the device state information of all the medical devices in a short time. If some medical devices are in abnormal operating states such as disconnection, blockage or downtime, the server may take a long time to acquire the device state information of all the medical devices. Moreover, since the medical devices monitored by different monitoring devices may overlap, the server may request the device state information of the same medical device when receiving the state query requests sent by different monitoring devices, and in this case, the server needs to repeatedly obtain the device state information of the same medical device according to the state query requests sent by the monitoring devices, which may cause waste of processing resources of the server. Based on this, the embodiment of the application provides an acquisition method of device state information, so as to reduce acquisition time of the device state information of medical devices and save processing resources of a server.

Next, a system architecture related to the embodiments of the present application will be described.

Fig. 1 is a system architecture diagram according to an embodiment of the present application, and a method for acquiring device status information is provided. As shown in fig. 1, the system includes a plurality of monitoring devices 101, a server 102, and a plurality of medical devices 103. The server 102 may communicate with the plurality of monitoring devices 101 through a wireless network, and the server 102 may also communicate with the plurality of medical devices 103 through a wireless network.

Wherein each of the plurality of monitoring devices 101 is configured to send its subscription information to the server 102. Illustratively, each subscription information includes a subscription device type of the corresponding monitoring device, i.e., a device type of the medical device 103 monitored by the monitoring device 101.

The server 102 is configured to obtain subscription information of a plurality of monitoring devices 103, and generate a subscription device type set according to the subscription information. Wherein each subscription information in the set of subscribed device types corresponds to at least one monitoring device 103 of the plurality of monitoring devices. The server 102 is also used to obtain device status information for a plurality of medical devices 103. The server 102 includes a main thread and a plurality of sub-threads. The main thread may acquire device address information of the configured multiple medical devices 103 from the database at preset time intervals, and then determine multiple target medical devices matching the subscribed device types in the subscribed device type set from the acquired device address information of the multiple medical devices. Then, device status information of the plurality of target medical devices is acquired through the plurality of sub-threads based on the device address information of the plurality of target medical devices. Wherein each of the plurality of sub-threads is used to obtain device status information for one medical device 103. After obtaining the device status information of the plurality of medical devices 103, the server 102 may push the obtained device status information to the plurality of monitoring devices 101 according to a set of subscribed device types.

Each of the plurality of monitoring devices 101 is further configured to receive the device status information of the medical device transmitted by the server 102 and display the received device status information. It should be noted that each monitoring device 101 may have a monitoring client installed thereon, and based on this, the monitoring client of each monitoring device 101 may display the received device status information in the client page after receiving the device status information of the medical device.

The server 102 may be a single server, or a server cluster, or a cloud platform, for example, the server 102 may be an application server corresponding to a monitoring client installed on the monitoring device 101, or the server 102 may also be a server with other functions, which is not limited in this embodiment of the present application.

The plurality of medical devices 103 may be intelligentized medical devices having communication and data processing functions, for example, terminal devices installed in the teaching room for decoding and playing video data in the operating room captured by the camera, or other medical devices in the operating room, which is not limited in the embodiment of the present application. The monitoring device 101 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, and the like, which is not limited in this embodiment of the present application.

Next, a method for acquiring device status information provided in an embodiment of the present application is described.

Fig. 2 is a method for acquiring device status information according to an embodiment of the present application, where the method may be applied to a main thread in a server, where the main thread is a thread created in the server and used for acquiring and pushing device status information to a monitoring device, and as shown in fig. 2, the method includes the following steps:

step 201: the method comprises the steps of obtaining a subscription device type set, wherein the subscription device type set comprises a plurality of subscription device types, and each subscription device type corresponds to at least one monitoring device in a plurality of monitoring devices.

In the embodiment of the application, a main thread in a server can establish long connections with a plurality of monitoring devices respectively, and receives subscription information of corresponding monitoring devices through the long connections with each monitoring device, wherein the subscription information comprises types of subscription devices; and removing the duplicate of the subscription equipment types in the received subscription information of the plurality of monitoring equipment to obtain a subscription equipment type set.

For example, after a plurality of monitoring devices come online, a main thread in the server may establish a websocket long connection with each of the plurality of monitoring devices. And then, each monitoring device in the plurality of monitoring devices can send own subscription information to the main thread through the websocket long connection. The subscription information includes subscription device types of the corresponding monitoring devices. Illustratively, the subscribed device types may include decoders, central controllers, and other types of medical devices in the operating room, which are not limited in this application.

Optionally, the subscription information sent by each of the multiple monitoring devices to the main thread may further include a type of the subscription information. The subscription information type may be an information type indicating subscribed device status information, for example, the information type may be an operation status or an operating temperature, which is not limited in this embodiment of the present application.

After receiving subscription information sent by a monitoring device, the main thread can acquire the device identifier of the monitoring device through a long connection established between the main thread and the monitoring device. And then, correspondingly storing the device identification of the monitoring device and the subscription information sent by the monitoring device. In this way, the main thread may obtain a mapping relationship table between the device identifier and the subscription information of the monitoring device based on the received subscription information and the device identifier sent by the multiple monitoring devices.

Then, the main thread may obtain the subscription device types of the multiple monitoring devices in the mapping relationship table, and perform deduplication on the subscription device types of the multiple monitoring devices to obtain a subscription device type set.

It should be noted that, since the subscription device types of some monitoring devices may be the same, that is, the medical devices monitored by the several monitoring devices are the same, the main thread may perform deduplication on the received subscription device types of the multiple monitoring devices to obtain a subscription device type set. At this time, each subscribed device type in the set of subscribed device types may correspond to one monitoring device, or may correspond to a plurality of monitoring devices.

Optionally, after obtaining the set of subscribed device types, the main thread may further receive updated subscription information of the plurality of monitoring devices through a long connection with the plurality of monitoring devices. After receiving updated subscription information of a plurality of monitoring devices, correspondingly storing the device identifications of the plurality of monitoring devices and the updated subscription information into the mapping relation table of the device identifications and the subscription information.

Then, the main thread searches whether the target subscription device type included in the updated subscription information is included from the subscription device type set. For convenience of description, any one of the plurality of monitoring devices is referred to as a target monitoring device. When the main thread receives updated subscription information of the target monitoring device through a long connection with the target monitoring device, whether the target subscription device type is included in the subscription device type set or not can be searched. If the target subscribed device type is not included in the set of subscribed device types, the set of subscribed device types is updated based on the target subscribed device type. That is, the target subscribing device type is added to the set of subscribing device types. If the target subscribing device type is included in the set of subscribing device types, the set of subscribing device types does not need to be updated.

202: and acquiring the equipment state information of the medical equipment corresponding to each subscription equipment type in the subscription equipment type set at preset time intervals based on the configured equipment address information of the plurality of medical equipment.

In the embodiment of the present application, the database is preconfigured with the device address information of a plurality of medical devices. The main thread in the server may obtain the device address information of the plurality of medical devices configured once from the database at preset time intervals. After the device address information of the plurality of medical devices is acquired, the main thread may acquire the device state information of the medical device corresponding to each subscribed device type in the subscribed device type set based on the acquired device address information of the plurality of medical devices.

The device address information of the plurality of medical devices may include device IPs (Internet Protocol addresses) of the plurality of medical devices and device interface information of the plurality of medical devices. Illustratively, the device interface information is used to indicate an interface on the corresponding medical device for reporting the device status information of the medical device to the server. In addition, the preset time interval may be set to a value of 5s or 8s, and the like, which is not limited in this embodiment of the application.

Wherein the main thread may determine a plurality of target medical devices from the plurality of medical devices that match the subscribed device types in the set of subscribed device types. After the target medical devices are determined, device state information of the target medical devices is acquired through a plurality of sub-threads based on device address information of the target medical devices, and each sub-thread is used for acquiring device state information of one medical device.

Illustratively, each medical device of the plurality of medical devices corresponds to a device type. Based on this, the main thread may search for a device type consistent with each subscribed device type from the device types corresponding to the plurality of medical devices, and then the main thread may use the searched medical device corresponding to the device type consistent with each subscribed device type as the target medical device.

After the target medical device is determined, the main thread may obtain device state information of the plurality of target medical devices through the plurality of sub-threads, respectively, based on the device address information of the plurality of target medical devices. Wherein each of the plurality of sub-threads is used to obtain device status information of one medical device.

In the embodiment of the present application, the server includes a thread resource pool, and a plurality of sub-threads are stored in the thread resource pool in advance. Where each child thread may be used to perform the same task. Based on the above, the main thread may sequentially acquire a plurality of sub-threads from the thread resource pool, and when one sub-thread is acquired, allocate a query task to the acquired target sub-thread, where the query task includes device address information of one target medical device, and is used to instruct the target sub-thread to send a status query request to the corresponding medical device based on the received device address information, and after the device status information of the corresponding medical device is acquired, store the device status information in the database. Thereafter, the main thread may obtain device status information of the plurality of target medical devices obtained by the plurality of sub-threads from the database. The device status information may include information such as an operating status of the medical device, an operating temperature of the device, and the like.

Illustratively, the main thread first acquires device address information of one target medical device from device address information of a plurality of target medical devices. For convenience of explanation, the device address information of the target medical device is referred to as device address information of the first target medical device. The primary thread may then retrieve the secondary thread from the thread resource pool. If an idle sub-thread exists in the thread resource pool, the main thread can obtain one sub-thread from the idle sub-threads in the thread resource pool, and for convenience of description, the obtained sub-thread is called a target sub-thread. Then, the main thread may assign a query task to the target sub-thread, where the query task carries the device address information of the first target medical device. After the query task is allocated to the target sub-thread, the main thread may delete the device address information of the first target medical device from the acquired device address information of the plurality of target medical devices. And then, the main thread acquires the equipment address information of one target medical equipment from the remaining equipment address information of the target medical equipment again, acquires one sub-thread from the thread resource pool again, if the sub-thread is acquired, allocates an inquiry task carrying the equipment address information of the target medical equipment acquired again to the acquired sub-thread, and so on until the main thread carries the equipment address information of each target medical equipment in the inquiry task and allocates the equipment address information to the corresponding sub-thread, and the main thread can enter a blocking state to wait for each sub-thread to finish the allocated inquiry task.

Correspondingly, after receiving the query task assigned by the main thread, each sub-thread may send a status query request to the corresponding target medical device based on the device address information of the target medical device carried in the received query task, where the status query request is used to request device status information from the corresponding target medical device.

For example, taking the target sub-thread as an example, after receiving the device address information of the first target medical device sent by the main thread, the target sub-thread may establish a connection with the first interface of the first target medical device based on the device IP and the device interface information included in the received device address information of the first target medical device. If the target child thread fails to establish a connection with the first interface of the first target medical device, the target child thread may generate device status information of the first target medical device, where the device status information includes abnormal operating status information indicating that an operating status of the first target medical device is abnormal. Optionally, if the target sub-thread establishes a connection with the first interface of the first target medical device successfully, the target sub-thread may send a status query request to a corresponding interface of the first target medical device through the established connection to request device status information from the first target medical device.

It should be noted that the device timeout response time is preset in each sub thread. Based on this, after the target sub-thread sends the status query request to the first target medical device, if the device status information fed back by the first target medical device is not received after waiting for the timeout response time, the target sub-thread may consider that the medical device to be queried by the target sub-thread is abnormal, and at this time, the target sub-thread may generate the device status information of the first target medical device, where the device status information includes abnormal operation status information indicating that the operation status of the first target medical device is abnormal. The timeout response time of the device may be set to 5s or 7s, which is not limited in this embodiment of the application.

Optionally, if the target sub-thread receives device state information fed back by the first target medical device within the device timeout response time, the target sub-thread may determine whether the first target medical device operates normally currently based on a parameter included in the received device state information, further generate operation state information indicating whether the first target medical device operates normally or abnormally according to a determination result, and use the operation state information and the received device state information as device state information of the first target medical device.

For example, the target child thread may obtain an operating temperature of the device from the received device status information, determine that the first target medical device is operating abnormally if the operating temperature is greater than an operating temperature threshold of the device, and at this time, may generate abnormal operating status information.

After the target sub-thread obtains the device state information of the first target medical device, if the database already stores the device state information of the first target medical device, the target sub-thread may update the device state information of the first target medical device stored in the database to the currently obtained device state information of the first target medical device, and if the database does not store the device state information of the first target medical device, the target sub-thread may directly store the currently obtained device state information of the first target medical device in the database. And the equipment address information and the equipment state information of each medical equipment in the database are correspondingly stored.

Illustratively, in one possible scenario, if the device state information of the first target medical device includes abnormal operating state information generated by the target child thread based on not receiving the device state information of the first target medical device within the device timeout response time, the target child thread may invoke the request timeout code to update the device state information of the first target medical device to the database.

In another possible scenario, if the device status information of the first target medical device includes abnormal operating status information generated by the target child thread based on parameters included in the status information fed back by the first target medical device, the target child thread may invoke the request failure code to update the device status information of the first target medical device to the database.

In a third possible scenario, if the device status information of the first target medical device includes normal operation status information, the target child thread may invoke the request success code to update the device status information of the first target medical device to the database.

According to the same method, each sub-thread can obtain the device state information of the corresponding target medical device according to the device address information included in the query task distributed by the main thread, and update the obtained device state information of the target medical device into the database, which is not described in detail herein.

After each sub-thread updates the acquired device state information of the target medical device to the database, the main thread may exit the blocking state, resume the task execution state, and further acquire the device state information of the target medical device corresponding to each subscribed device type in the subscribed device type set from the database.

It should be noted that, after the main thread allocates the query task to each sub-thread, a counter may be set, and an initial count value of the counter is equal to the number of the target medical devices to be queried. The main thread, after setting the counter, may call the await () method into the blocked state. Then, in the process of executing the query task, for any sub-thread, after the sub-thread updates the obtained device state information of the target medical device to the database, that is, after the sub-thread completes the query task, a countDown () method may be further invoked to subtract 1 from the count value of the counter. Based on this, after the main thread enters the blocking state, whether the count value of the counter is 0 can be detected in real time. When the count value of the counter is detected to be 0, it is determined that each sub-thread completes the query task of the sub-thread, and at this time, the main thread can acquire the device state information of the target medical device corresponding to each subscribed device type from the database according to each subscribed device type in the subscribed device type set.

For example, taking any subscribed device type in the set of subscribed device types as an example, the main thread may search, according to the subscribed device type, a medical device in accordance with the subscribed device type from the database, where the searched medical device is a target medical device corresponding to the subscribed device type. And then, the main thread acquires the searched equipment state information of the target medical equipment from the database, and the acquired equipment state information of the target medical equipment is used as the equipment state information of the target medical equipment corresponding to the subscribed equipment type. According to the same method, the main thread may obtain, from the database, device state information of the target medical device corresponding to each subscribed device type in the set of subscribed device types.

Optionally, in a possible implementation manner, each time the main thread detects that the count value of the counter is decreased by 1, the sub-thread that calls the countDown () method to decrease the count value of the counter by 1 may also be recycled into the thread resource pool. Therefore, after each sub-thread completes the query task of the main thread, the main thread can recycle each sub-thread to the thread resource pool. Subsequently, the main thread may also continue to assign additional query tasks to each of the sub-threads. Therefore, the reuse of the sub-threads in the thread resource pool is realized, and the consumption of creating and destroying the sub-threads on the computing resources is reduced.

Optionally, in some possible cases, when the main thread allocates a query task to the sub-threads and the main thread acquires the sub-threads from the thread resource pool, there may be no idle sub-threads in the thread resource pool, that is, all the sub-threads in the thread resource pool are executing their query tasks. In this case, the main thread may detect whether the task queue is full, and if the task queue is not full, add the query task to be currently allocated to the task queue, so as to allocate the query task to the corresponding sub-thread when an idle sub-thread appears in the thread resource pool. If the task queue is full, the main thread can stop task allocation, and when the task queue is idle, the task to be inquired is stored in the task queue to wait for allocation.

Step 203: and pushing the obtained equipment state information to a plurality of monitoring equipment according to the subscription equipment type set.

In this embodiment of the application, after acquiring the device state information of the target medical device corresponding to each subscribed device type in the subscribed device type set, the main thread may push the device state information of the target medical device corresponding to the corresponding subscribed device type to at least one monitoring device corresponding to each subscribed device type in the subscribed device type set.

Illustratively, as can be seen from the foregoing description, a mapping relationship table between the device identifier of the monitoring device and the subscription information is stored in advance in the main thread. Based on this, after the main thread acquires the device state information of the target medical device corresponding to each subscribed device type in the set of subscribed device types, the main thread may search the device identifier of the monitoring device corresponding to each subscribed device type in the mapping relationship table of the subscription information stored in the main thread and the device identifier of the monitoring device. And then, determining corresponding monitoring equipment according to the equipment identification of each monitoring equipment. As can be seen from the foregoing description in step 201, there may be one or more monitoring devices corresponding to the same subscription device type. Taking any subscription device type as an example, when there is one monitoring device corresponding to the subscription device type, the main thread may push the acquired device state information of the target medical device to the monitoring device through a websocket long connection established between the main thread and the monitoring device. If there are multiple monitoring devices corresponding to the subscription device type, the main thread may also push the acquired device state information of the target medical device corresponding to the subscription device type to the multiple monitoring devices through the websocket long connection established between the multiple monitoring devices corresponding to the subscription device type.

Optionally, as can be seen from the foregoing description, each subscription information may further include a subscription information type, and based on this, after determining the monitoring device corresponding to each subscription device type in the subscription device type set, the main thread may further push, to the monitoring device, information that is the same as the subscription information type in the corresponding device state information according to the subscription information type included in the subscription information corresponding to the determined monitoring device.

For example, taking the subscribed device type a as an example, after obtaining the device state information B corresponding to the subscribed device type a, the main thread determines the monitoring device corresponding to the subscribed device type a by the method described above. Assuming that the determined monitoring device includes the monitoring device C, the main thread acquires a subscription information type in subscription information corresponding to the monitoring device C, and assuming that the acquired subscription information type is a working temperature, the main thread may push the working temperature in the acquired device state information B to the monitoring device C.

Secondly, when acquiring the device state information of a plurality of medical devices, the device state information of the plurality of medical devices is acquired in a parallel mode by adopting a plurality of sub-threads, so that the time for acquiring the device state information can be reduced.

In addition, in the embodiment of the application, after the distributed query tasks are completed, each sub-thread may be recovered to the thread resource pool, and the subsequent main thread may continue to distribute other query tasks to the sub-threads. Therefore, the reuse of the sub-threads in the thread resource pool is realized, the consumption of the creating and destroying of the sub-threads on the computing resources is reduced, and meanwhile, the sub-threads in the thread resource pool can be recycled and reused, so that the number of the sub-threads in the thread resource pool can be fixed, and the management of the sub-threads in the thread resource pool is facilitated.

Based on the method for acquiring device status information provided in the foregoing embodiment, fig. 3 shows a flowchart of a possible implementation of acquiring device status information. Referring to fig. 3, first, a main thread in the server may receive subscription information sent by a plurality of monitoring devices, and generate a subscription device type set according to the received subscription information. For the process of generating the subscribed device type set, reference may be made to step 201, which is not described in this embodiment of the present application again.

Optionally, if the main thread does not receive the subscription information sent by the monitoring device, the main thread cannot generate a subscription device type set, and at this time, the main thread ends its own task.

Then, the main thread acquires the device address information of the configured medical devices from the database, and determines a plurality of target medical devices matched with the subscribed device types in the subscribed device type set from the device address information of the plurality of medical devices. Device address information for a plurality of target medical devices is then obtained. After the main thread acquires the device address information of the plurality of target medical devices, a counter can be set, and the initial count value of the counter is set to be equal to the number of the target medical devices.

Then, the main thread may sequentially obtain a plurality of sub-threads from the thread resource pool, and when each sub-thread is obtained, a query task is distributed to the obtained sub-threads. The step 202 may be referred to in an implementation manner in which the main thread distributes the query task to each sub-thread, which is not described in this embodiment of the present application again. Thereafter, the main thread may enter a blocked state to wait for each sub-thread to complete the assigned query task.

After receiving the query task distributed by the main thread, each sub-thread can execute the corresponding query task, that is, obtain the device state information of the corresponding target medical device. The step 202 may be referred to in the method for obtaining the device state information of the corresponding target medical device by each sub-thread, which is not described in detail herein.

After acquiring the device address information of the target medical device corresponding to each sub-thread, each sub-thread may call a countDown () method to subtract 1 from the count value of the counter in the main thread. Then, each sub-thread may update the obtained device state information of the target medical device to the database, where the implementation manner in which each sub-thread updates the obtained device state information of the target medical device to the database may refer to step 202 described above, and details thereof are not described herein again in this embodiment of the present application.

After the main thread enters the blocking state, whether the count value of the counter is 0 or not can be detected in real time. When the counting value of the counter is detected to be 0, it is determined that each sub-thread completes the query task of the sub-thread, and at this time, the main thread can acquire the device state information of the target medical devices, which is acquired by the sub-threads, from the database. For the method for acquiring the device state information of the multiple target medical devices from the database by the main thread, reference may be made to step 202, which is not described herein again in this embodiment.

After the device state information of the multiple target medical devices is acquired, the main thread can push the device state information of the target medical device corresponding to the corresponding subscription device type to at least one monitoring device corresponding to each subscription device type in the subscription device type set. For the method for pushing the device state information of the target medical device to the monitoring device by the main thread, reference may be made to step 203, which is not described herein again.

After receiving the device state information of the target medical device pushed by the main thread, the monitoring device may display the received device state information of the target medical device.

Next, an apparatus for acquiring device status information provided in an embodiment of the present application will be described.

Referring to fig. 4, an embodiment of the present application provides an apparatus 400 for acquiring device status information, where the apparatus 400 includes: a first obtaining module 401, a second obtaining module 402 and a sending module 403.

A first obtaining module 401, configured to obtain a subscription device type set, where the subscription device type set includes multiple subscription device types, and each subscription device type corresponds to at least one monitoring device of multiple monitoring devices;

a second obtaining module 402, configured to obtain, at preset time intervals, device state information of a medical device corresponding to each subscribed device type in the subscribed device type set based on the device address information of the configured multiple medical devices;

a sending module 403, configured to push the obtained device state information to multiple monitoring devices according to a set of subscribed device types.

Optionally, the first obtaining module 401 is mainly configured to:

respectively establishing long connection with a plurality of monitoring devices;

receiving subscription information of corresponding monitoring equipment through long connection with each monitoring equipment, wherein the subscription information comprises the type of the subscription equipment;

and removing the duplicate of the subscription equipment types in the received subscription information of the plurality of monitoring equipment to obtain a subscription equipment type set.

Optionally, the apparatus 400 is further configured to:

when updated subscription information of the target monitoring device is received through long connection with the target monitoring device, whether a subscription device type set comprises a target subscription device type included in the updated subscription information is searched, wherein the target monitoring device is any one of the monitoring devices;

if the target subscribed device type is not included in the set of subscribed device types, the set of subscribed device types is updated based on the target subscribed device type.

Optionally, the subscription information includes a subscribed device type, and the second obtaining module 402 is further configured to:

determining a plurality of target medical devices from the plurality of medical devices that match a subscribed device type from a set of subscribed device types;

the device state information of the plurality of target medical devices is acquired through a plurality of sub-threads based on device address information of the plurality of target medical devices, each of the plurality of sub-threads being used for acquiring the device state information of one medical device.

Optionally, the second obtaining module 402 is further configured to:

sequentially acquiring a plurality of sub-threads from a thread resource pool, and distributing a query task to the acquired target sub-thread when one sub-thread is acquired, wherein the query task comprises equipment address information of one target medical equipment, is used for indicating the target sub-thread to send a state query request to the corresponding medical equipment based on the received equipment address information, and stores the equipment state information to a database after the equipment state information of the corresponding medical equipment is acquired;

device status information of the plurality of target medical devices obtained by the plurality of sub-threads is obtained from the database.

Optionally, the apparatus 400 is further configured to:

detecting whether the count value of a counter is 0, wherein the initial count value of the counter is equal to the number of the target medical devices, and when any sub-thread in the plurality of sub-threads finishes the distributed query task, the count value of the counter is reduced by 1;

when detecting that the count value of the counter is 0, the second acquiring module 402 is triggered to execute the step of acquiring the device status information of the plurality of target medical devices acquired from the plurality of sub-threads from the database.

Optionally, the apparatus 400 is further configured to:

and when the target sub-thread is detected to complete the distributed query task, recovering the target sub-thread to the thread resource pool.

Optionally, the sending module 403 is further configured to:

and pushing the device state information of the target medical device corresponding to the corresponding subscription device type to at least one monitoring device corresponding to each subscription device type in the subscription device type set.

In summary, in the embodiment of the present application, the main thread of the server actively acquires the device state information at preset time intervals based on the subscription device type provided by the monitoring device in advance, and pushes the acquired device state information of the medical device to the monitoring device, so that when some monitoring devices simultaneously monitor the same medical device or the same type of medical device, compared with a mode in which each monitoring device actively requests the device state information from the server, the server can be prevented from repeatedly acquiring the device state information of some medical devices, and thus processing resources of the server can be saved.

It should be noted that, when the apparatus for acquiring device status information provided in the foregoing embodiment acquires device status information, the division of each functional module is merely illustrated, and in practical applications, the above function allocation may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules, so as to complete all or part of the above described functions. In addition, the apparatus for acquiring device status information and the method embodiment for acquiring device status information provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiment and are not described herein again.

Fig. 5 is a schematic diagram illustrating a server architecture in accordance with an example embodiment. The functions of the server in the above embodiments can be implemented by the server shown in fig. 5. The server may be a server in a cluster of background servers. Specifically, the method comprises the following steps:

the server 500 includes a Central Processing Unit (CPU) 501, a system Memory 504 including a Random Access Memory (RAM) 502 and a Read-Only Memory (ROM) 503, and a system bus 505 connecting the system Memory 504 and the CPU 501. The server 500 also includes a basic Input/Output system (I/O system) 506, which helps transfer information between devices within the computer, and a mass storage device 507 for storing an operating system 513, application programs 514, and other program modules 515.

The basic input/output system 506 comprises a display 508 for displaying information and an input device 509, such as a mouse, keyboard, etc., for user input of information. Wherein a display 508 and an input device 509 are connected to the central processing unit 501 through an input output controller 510 connected to the system bus 505. The basic input/output system 506 may also include an input/output controller 510 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input-output controller 510 also provides output to a display screen, a printer, or other type of output device.

The mass storage device 507 is connected to the central processing unit 501 through a mass storage controller (not shown) connected to the system bus 505. The mass storage device 507 and its associated computer-readable media provide non-volatile storage for the server 500. That is, the mass storage device 507 may include a computer-readable medium (not shown) such as a hard disk or a CD-ROM (Compact disk Read-Only Memory) drive.

Without loss of generality, computer readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), flash Memory or other solid state Memory device, CD-ROM, DVD (Digital Versatile disk), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that computer storage media is not limited to the foregoing. The system memory 504 and mass storage device 507 described above may be collectively referred to as memory.

According to various embodiments of the present application, server 500 may also operate as a remote computer connected to a network through a network, such as the Internet. That is, the server 500 may be connected to the network 512 through the network interface unit 511 connected to the system bus 505, or may be connected to other types of networks or remote computer systems (not shown) using the network interface unit 511.

The memory further includes one or more programs, and the one or more programs are stored in the memory and configured to be executed by the CPU. The one or more programs include instructions for performing the method for acquiring device status information provided by the embodiments of the present application.

Embodiments of the present application further provide a computer-readable storage medium, where instructions executed by a processor of a server enable the server to execute the method for acquiring device status information provided in the foregoing embodiments. For example, the computer readable storage medium may be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like. It is noted that the computer-readable storage medium referred to in the embodiments of the present application may be a non-volatile storage medium, in other words, a non-transitory storage medium.

It should be understood that all or part of the steps for implementing the above embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The computer instructions may be stored in the computer-readable storage medium described above.

That is, in some embodiments, there is also provided a computer program product containing instructions, which when run on a computer, cause the computer to perform the method for acquiring device status information provided by the above embodiments.

It should be noted that the information (including but not limited to user equipment information, user personal information, etc.), data (including but not limited to data for analysis, stored data, presented data), and signals referred to in the embodiments of the present application are authorized by the user or fully authorized by various parties, and the collection, use, and processing of the relevant data need to comply with relevant laws and regulations and standards in relevant countries and regions.

The above description should not be taken as limiting the embodiments of the present application, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the embodiments of the present application should be included in the scope of the embodiments of the present application.

Claims

1. A method for obtaining device state information, which is applied to a main thread in a server, the method comprises:

2. The method of claim 1, wherein obtaining the set of subscribed device types comprises:

3. The method of claim 2, wherein after obtaining the set of subscribed device types, further comprising:

4. The method of claim 1, wherein the subscription information includes a subscription device type;

5. The method according to claim 4, wherein the obtaining device status information of the plurality of target medical devices through a plurality of sub-threads based on the device address information of the plurality of target medical devices comprises:

6. The method according to claim 5, wherein before the obtaining device status information of the plurality of target medical devices obtained by the plurality of sub-threads from the database, further comprising:

detecting whether the count value of a counter is 0, wherein the initial count value of the counter is equal to the number of the plurality of target medical devices, and when any sub-thread in the plurality of sub-threads finishes the distributed query task, the count value of the counter is reduced by 1;

7. The method of claim 5, further comprising:

8. The method of claim 4, wherein pushing the obtained device status information to the plurality of monitoring devices according to the set of subscribed device types comprises:

9. An apparatus for obtaining device status information, wherein the apparatus is applied to a main thread in a server, and the apparatus includes a processor, in which the main thread runs, and the main thread is configured to:

10. A computer-readable storage medium, in which a computer program is stored, and the computer program is executed by a computer to implement the method for acquiring device status information according to any one of claims 1 to 8.