CN114884987B

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

Info

Publication number: CN114884987B
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: 2024-03-29
Anticipated expiration: 2042-04-24
Also published as: CN114884987A

Abstract

The embodiment of the application discloses a method, a device and a storage medium for acquiring equipment state information, belonging to the technical field of medical informatization. In this embodiment of the present application, the main line Cheng Meige of the server actively acquires device state information based on the type of the subscription device provided in advance by the monitoring device at a preset time interval, and pushes the acquired device state information of the medical device to the monitoring device, so when a certain monitoring device monitors the same medical device or the same type of medical device at the same time, compared with a mode that each monitoring device actively requests the device state information to the server, the server can be prevented from repeatedly acquiring the device state information of certain medical devices, thereby saving processing resources of the server.

Description

Method, device and storage medium for acquiring equipment state information

Technical Field

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

Background

With the development of medical information technology, one server can connect a large number of medical devices in a medical information system. Wherein, whether each medical device is in a normal operation state can be judged by monitoring the device state information of the medical device. Based on the above, 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, applied to a main thread in a server, the method including:

acquiring 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 equipment address information of a plurality of configured medical equipment at preset time intervals;

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

Optionally, the acquiring the subscription device type set includes:

respectively establishing long connection with the plurality of monitoring devices;

receiving subscription information of each monitoring device through long connection with each monitoring device, wherein the subscription information comprises subscription device types;

And de-duplicating the types of the subscription equipment in the subscription information of the plurality of monitoring equipment to obtain the subscription equipment type set.

Optionally, after the acquiring the subscription device type set, the method further includes:

when updated subscription information of target monitoring equipment is received through long connection with the target monitoring equipment, searching whether the subscription equipment type set comprises target subscription equipment types contained in the updated subscription information or not, wherein the target monitoring equipment is any monitoring equipment in the plurality of monitoring equipment;

and if the target subscription device type is not included in the subscription device type set, updating the subscription device type set based on the target subscription device type.

Optionally, the subscription information includes a subscription device type;

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

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

Acquiring 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 of the plurality of sub-threads is used for acquiring the device state information of one medical device.

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

sequentially acquiring the plurality of sub-threads from a thread resource pool, and when one sub-thread is acquired, distributing a query task to the acquired target sub-thread, wherein the query task comprises equipment address information of a target medical equipment, and 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 storing the equipment state information into a database after acquiring the equipment state information of the corresponding medical equipment;

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

Optionally, before the acquiring the device state information of the target medical devices obtained by the multiple sub-threads from the database, the method further includes:

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 one of the plurality of sub-threads completes the distributed query task, the count value of the counter is reduced by 1;

and when the count 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 plurality of sub-threads from the database.

Optionally, the method further comprises:

and after detecting that the target sub-thread completes the distributed query task, recycling the target sub-thread to the thread resource pool.

Optionally, pushing the obtained device status information to the plurality of monitoring devices according to the subscription device type set includes:

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

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

the first acquisition module is used for acquiring 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;

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

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

Optionally, the first obtaining module is further configured to:

Optionally, the device is further configured to:

Optionally, the subscription information includes a subscription device type;

the second acquisition module is further configured to:

Optionally, the second acquisition module is further configured to:

Optionally, the device is further configured to:

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

Optionally, the device is further configured to:

Optionally, the sending module is configured to:

In another aspect, an apparatus for obtaining device state information is provided and applied to a main thread in a server, where the apparatus includes a processor having a main thread running therein, 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, the computer program implementing the steps of the method for acquiring device status information described above when executed by a computer.

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

The beneficial effects that technical scheme that this application embodiment provided include at least:

in this embodiment of the present application, the main line Cheng Meige of the server actively acquires device state information based on the type of the subscription device provided in advance by the monitoring device at a preset time interval, and pushes the acquired device state information of the medical device to the monitoring device, so when a certain monitoring device monitors the same medical device or the same type of medical device at the same time, compared with a mode that each monitoring device actively requests the device state information to the server, the server can be prevented from repeatedly acquiring the device state information of certain medical devices, thereby saving processing resources of the server.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

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

FIG. 2 is a flowchart of a method for obtaining device status information according to an embodiment of the present application;

FIG. 3 is a flowchart of another method for obtaining device status information according to an embodiment of the present application;

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

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the 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, application scenarios of the embodiments of the present application are described.

With the development of medical information technology, in a medical information system, one server may often be connected to a large number of medical devices, for example, in a teleoperation teaching system, a server and a plurality of terminal devices installed in a teaching room connected to the server are included, and the plurality of terminal devices are used for decoding and playing video data in an operating room captured by a camera. In general, 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, a 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 be an overlap between 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 status information of all the medical devices in a short time. If the medical equipment is in an abnormal operation state such as disconnection, blocking or downtime, the server may need a long time to acquire the equipment state information of all the medical equipment. Moreover, since the medical devices monitored by different monitoring devices may overlap, the server may request the device status information of the same medical device when receiving the status query request sent by different monitoring devices, and in this case, the server needs to repeatedly acquire the device status information of the same medical device according to the status query requests sent by the respective monitoring devices, which may cause waste of processing resources of the server. Based on this, the embodiment of the application provides a method for acquiring device state information, so as to reduce the acquisition time of the device state information of the medical device and save the processing resources of the server.

The system architecture to which the embodiments of the present application relate is described next.

Fig. 1 is a system architecture diagram related to a method for obtaining device status information according to an embodiment of the present application. As shown in fig. 1, the system includes a plurality of monitoring devices 101, a server 102, and a plurality of medical devices 103. Wherein the server 102 may communicate with the plurality of monitoring devices 101 via a wireless network, and the server 102 may also communicate with the plurality of medical devices 103 via 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., the device type of the medical device 103 monitored by the monitoring device 101.

The server 102 is configured to obtain subscription information of the plurality of monitoring devices 103, and generate a set of subscription device types according to the plurality of subscription information. Wherein each subscription information in the set of subscription device types corresponds to at least one monitoring device 103 of the plurality of monitoring devices. The server 102 is also configured to obtain device status information of a plurality of medical devices 103. Wherein the server 102 includes a main thread and a plurality of sub-threads. The main thread may acquire device address information of the configured plurality of medical devices 103 from the database at preset time intervals, and then determine a plurality of target medical devices matching the subscribed device type in the subscribed device type set from the acquired device address information of the plurality of medical devices. And then, 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 of the plurality of sub-threads is configured to obtain device status information for one of the medical devices 103. After acquiring the device status information of the plurality of medical devices 103, the server 102 may push the acquired device status information to the plurality of monitoring devices 101 according to the subscription device type set.

Each of the plurality of monitoring devices 101 is further configured to receive 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 be provided with a monitoring client, 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 intelligent medical devices having communication and data processing functions, for example, terminal devices installed in a teaching room for decoding and playing video data in an operating room captured by a camera, or other medical devices in the operating room, which is not limited in this embodiment of the present application. The monitoring device 101 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, etc., which is not limited in this embodiment of the present application.

Next, a method for obtaining device status information provided in an embodiment of the present application will be 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 to acquire and push device status information to a monitoring device, and as shown in fig. 2, the method includes the following steps:

step 201: a set of subscribing device types is obtained, the set of subscribing device types comprising a plurality of subscribing device types, each subscribing device type corresponding to at least one monitoring device of the plurality of monitoring devices.

In the embodiment of the application, a main thread in a server can respectively establish long connection with a plurality of monitoring devices, and receive subscription information of the corresponding monitoring devices through the long connection with each monitoring device, wherein the subscription information comprises subscription device types; and de-duplicating the types of the subscription devices in the subscription information of the plurality of monitoring devices to obtain a subscription device type set.

For example, after a plurality of monitoring devices are online, a main thread in a server may establish a websocket long connection with each of the plurality of monitoring devices. Then, each monitoring device in the plurality of monitoring devices can send own subscription information to the main thread through the websocket long connection. Wherein the subscription information includes subscription device types of the respective monitoring devices. By way of example, the subscription device types may include decoders, central controllers, and other types of medical devices within the operating room, as embodiments of the present application are not limited in this regard.

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

After receiving subscription information sent by one monitoring device, the main thread can acquire the device identification of the monitoring device through a long connection established between the main thread and the monitoring device. And then, storing the equipment identification of the monitoring equipment in correspondence with the subscription information sent by the monitoring equipment. In this way, the main thread may obtain a mapping relationship table between the device identifications of the monitoring devices and the subscription information based on the subscription information and the device identifications transmitted by the plurality of monitoring devices.

And then, the main thread can acquire the subscription device types of the plurality of monitoring devices in the mapping relation table, and de-duplicate the subscription device types of the plurality of monitoring devices to obtain a subscription device type set.

It should be noted that, since the subscription device types of several 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 subscription device types of the received multiple monitoring devices to obtain a subscription device type set. At this time, each subscription device type in the subscription device type set 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 for the plurality of monitoring devices over a long connection with the plurality of monitoring devices. After updated subscription information of the plurality of monitoring devices is received, device identifiers of the plurality of monitoring devices and the updated subscription information are correspondingly stored in a mapping relation table of the device identifiers and the subscription information.

And then, the main thread searches whether the target subscription device type included in the updated subscription information is included in the subscription device type set. Any one of the plurality of monitoring devices is taken as an example, and for convenience of explanation, the 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, it may be searched whether the target subscription device type is included in the subscription device type set. If the target subscribing device type is not included in the subscribing device type set, updating the subscribing device type set based on the target subscribing device type. That is, the target subscribing device type is added to the subscribing device type set. If the target subscribing device type is included in the subscribing device type collection, updating of the subscribing device type collection is not required.

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

In the embodiment of the present application, the device address information of a plurality of medical devices is preconfigured in the database. The main thread in the server can acquire the device address information of the plurality of medical devices configured once from the database at preset time intervals. After acquiring the device address information of the plurality of medical devices, the main thread may acquire device status 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 IP (Internet Protocol Adress, internet protocol address) of the plurality of medical devices and device interface information of the plurality of medical devices, among others. The device interface information is illustratively used to indicate the interface on the respective medical device for reporting its own device status information to the server. In addition, the preset time interval may be set to a value of 5s or 8s, which is not limited in the embodiment of the present application.

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

Illustratively, each of the plurality of medical devices corresponds to a device type. Based on the above, the main thread may search for the 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 medical device corresponding to the searched device type consistent with each subscribed device type as the target medical device.

After determining the target medical device, the main thread may acquire device state information of the plurality of target medical devices through the plurality of sub-threads, respectively, based on device address information of the plurality of target medical devices. Wherein each of the plurality of sub-threads is configured to obtain device status information for a medical device.

In this embodiment of the present application, the server includes a thread resource pool, where a plurality of sub-threads are pre-stored in the thread resource pool. Wherein each sub-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 a target medical device, and is configured to instruct the target sub-thread to send a status query request to a corresponding medical device based on the received device address information, and store the device status information to the database after acquiring the device status information of the corresponding medical device. The main thread may then obtain device state information for 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 obtains 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 will be referred to as device address information of the first target medical device. Thereafter, the main thread may obtain the sub-threads from the thread resource pool. If there is a free sub-thread in the thread resource pool, the main thread may obtain a sub-thread from the free sub-threads in the thread resource pool, and for convenience of explanation, the obtained sub-thread is referred to as a target sub-thread. The main thread may then assign a query task to the target sub-thread, the query task carrying device address information of the first target medical device. After assigning the inquiry task 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 equipment address information of the rest target medical equipment again, acquires one sub-thread from the thread resource pool again, if the sub-thread is acquired, distributes the query 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 distributes the equipment address information of each target medical equipment in the query task to the corresponding sub-thread, and the main thread can enter a blocking state to wait for each sub-thread to complete the distributed query task.

Accordingly, after each sub-thread receives the query task allocated by the main thread, a status query request may be sent 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 sub-thread fails to establish a connection with the first interface of the first target medical device, the target sub-thread may generate device state information for the first target medical device, where the device state information includes abnormal operation state information for indicating that the operation state 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 the 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 sending 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 itself is abnormal, at which 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 the embodiment of the present application.

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

For example, the target sub-thread may obtain the operating temperature of the device from the received device state information, and if the operating temperature is greater than the operating temperature threshold of the device, determine that the first target medical device is operating abnormally, at which point abnormal operating state information may be generated.

After obtaining the device state information of the first target medical device, if the device state information of the first target medical device is already stored in the database, the target sub-thread may update the device state information of the first target medical device stored in the database to the device state information of the first target medical device that is currently obtained, and if the device state information of the first target medical device is not stored in the database, the target sub-thread may directly store the device state information of the first target medical device that is currently obtained to the database. Wherein, the equipment address information of each medical equipment in the database is stored correspondingly with the equipment state information.

For example, in one possible scenario, if the device state information of the first target medical device includes abnormal operation state information, and the abnormal operation state information is generated by the target sub-thread based on the device state information of the first target medical device not being received within the device timeout response time, the target sub-thread may invoke a 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 state information of the first target medical device includes abnormal operation state information, and the abnormal operation state information is generated by the target sub-thread based on parameters included in the state information fed back by the first target medical device, the target sub-thread may invoke a request failure code to update the device state information of the first target medical device to the database.

In a third possible scenario, if the device state information of the first target medical device includes normal operating state information, the target sub-thread may invoke a request success code to update the device state 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 allocated by the main thread, and update the obtained device state information of the target medical device to the database, which is not described in detail in the embodiment of the present application.

After each sub-thread updates the obtained device state information of the target medical device to the database, the main thread can exit the blocking state and resume the execution task state, so that the device state information of the target medical device corresponding to each subscription device type in the subscription device type set is obtained 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, where an initial count value of the counter is equal to the number of target medical devices to be queried. After setting the counter, the main thread may call the await () method to enter the blocking state. Then, in the process of executing the query task, for any one of the sub-threads, 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, the countDown () method may be also called to decrement the count value of the counter by 1. Based on this, the main thread can detect whether the count value of the counter is 0 in real time after entering the blocking state. When the count value of the counter is detected to be 0, it is determined that each sub-thread completes its own query task, and at this time, the main thread may acquire device state information of the target medical device corresponding to each subscription device type from the database according to each subscription device type in the subscription device type set.

Taking any subscription device type in the subscription device type set as an example, the main thread may search for a medical device consistent with the subscription device type from the database according to the subscription device type, where the searched medical device is the target medical device corresponding to the subscription device type. And then, the main thread acquires the device state information of the searched target medical device from the database, and takes the acquired device state information of the target medical device as the device state information of the target medical device corresponding to the subscription device type. According to the same method, the main thread can acquire the device state information of the target medical device corresponding to each subscription device type in the subscription device type set from the database.

Optionally, in one possible implementation, each time the main thread detects that the count value of the counter is decremented by 1, the sub-thread that calls the countDown () method to decrement the count value of the counter by 1 may also be recycled into the thread resource pool. Thus, after each sub-thread completes its own query task, the main thread can recycle each sub-thread to the thread resource pool. Subsequently, the main thread may also continue to assign other query tasks to each sub-thread. Therefore, the multiplexing of the sub-threads in the thread resource pool is realized, and the consumption of creating and destroying the sub-threads to the computing resources is reduced.

Optionally, in some possible cases, when the main thread is acquiring the sub-thread from the thread resource pool when the main thread is allocating the query task to the sub-thread, there may be no idle sub-thread in the thread resource pool, that is, all the sub-threads in the thread resource pool are executing their own 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 currently-to-be-allocated query task 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 waiting task queue is idle, the task to be queried is stored in the task queue to wait for allocation.

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

In this embodiment of the present application, after obtaining device status information of a target medical device corresponding to each subscription device type in the subscription device type set, the main thread may push, to at least one monitoring device corresponding to each subscription device type in the subscription device type set, device status information of a target medical device corresponding to the corresponding subscription device type.

As is apparent from the foregoing description, a mapping relationship table between the device identification of the monitoring device and the subscription information is stored in advance in the main thread. Based on the above, after the main thread obtains the device status information of the target medical device corresponding to each subscription device type in the subscription device type set, the main thread may search the device identifier of the monitoring device corresponding to each subscription device type in the mapping relationship table of the subscription information stored by the main thread and the device identifier of the monitoring device. And then, determining the corresponding monitoring equipment according to the equipment identification of each monitoring equipment. It is known from the foregoing description of step 201 that there may be one or more monitoring devices corresponding to the same subscription device type. Taking any subscription equipment type as an example, when the monitoring equipment corresponding to the subscription equipment type is one, the main thread can push the acquired equipment state information of the target medical equipment to the monitoring equipment through the websocket long connection established between the main thread and the monitoring equipment. If the number of the monitoring devices corresponding to the subscription device type is multiple, the main thread can push the acquired device state information of the target medical device corresponding to the subscription device type to the monitoring devices through the websocket long connection established among the 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, based on which, after determining a 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 in the corresponding device state information that is the same as the subscription information type according to the subscription information type included in the subscription information corresponding to the determined monitoring device.

Taking the subscription device type a as an example, the main thread determines the monitoring device corresponding to the subscription device type a through the method described above after obtaining the device state information B corresponding to the subscription device type a. The main thread obtains the subscription information type in the subscription information corresponding to the monitoring device C, and the main thread can push the obtained working temperature in the device state information B to the monitoring device C, assuming that the obtained subscription information type is the working temperature.

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

In addition, in the embodiment of the present application, after each sub-thread completes the allocated query task, the sub-thread may be recycled into the thread resource pool, and the subsequent main thread may continue to allocate other query tasks to the sub-threads. Therefore, the multiplexing of the sub-threads in the thread resource pool is realized, the consumption of creating and destroying the sub-threads to the computing resource is reduced, and meanwhile, as the sub-threads in the thread resource pool can be recycled and reused, the number of the sub-threads in the thread resource pool can be fixed, so that the management of the sub-threads in the thread resource pool is convenient.

Based on the method for acquiring device status information provided in the above embodiment, fig. 3 shows a possible implementation flowchart for acquiring device status information. Referring to fig. 3, first, a main thread in a 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. The process of generating the subscription device type set may refer to the foregoing step 201, which is not described in detail in the embodiment of the present application.

Alternatively, if the main thread does not receive the subscription information sent by the monitoring device, the main thread Cheng Mofa generates a subscription device type set, at which point the main thread ends its own task.

And 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 subscription device types in the subscription 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 acquired. 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 can sequentially acquire a plurality of sub-threads from the thread resource pool, and when one sub-thread is acquired, the main thread distributes inquiry tasks to the acquired sub-threads. The implementation manner of the main thread to allocate the query task to each sub-thread may refer to the foregoing step 202, which is not repeated in the embodiment of the present application. Thereafter, the main thread may enter a blocking state to wait for each sub-thread to complete the assigned query task.

After each sub thread receives the query task distributed by the main thread, the corresponding query task can be executed, namely, the device state information of the corresponding target medical device is acquired. The method for each sub-thread to obtain the device status information of the corresponding target medical device may refer to the foregoing step 202, which is not described in detail in the embodiment of the present application.

After each sub-thread acquires the device address information of the corresponding target medical device, the countDown () method can be called to reduce the count value of the counter in the main thread by 1. Thereafter, each sub-thread may update the obtained device state information of the target medical device to the database, and 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 the foregoing step 202, which is not described in detail in the embodiments of the present application.

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 its own query task, and at this time, the main thread can acquire device state information of a plurality of target medical devices obtained by a plurality of sub-threads from the database. The method for the main thread to obtain the device status information of the plurality of target medical devices obtained by the plurality of sub-threads from the database may refer to the foregoing step 202, which is not repeated in the embodiment of the present application.

After acquiring the device state information of the plurality of target medical devices, 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. The method for pushing the device status information of the target medical device to the monitoring device by the main thread may refer to the foregoing step 203, which is not described herein in detail.

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

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

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

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

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

and the sending module 403 is configured to push the obtained device status information to the plurality of monitoring devices according to the subscribed device type set.

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

respectively establishing long connection with a plurality of monitoring devices;

Receiving subscription information of the corresponding monitoring device through long connection with each monitoring device, wherein the subscription information comprises subscription device types;

and de-duplicating the types of the subscription devices in the subscription information of the plurality of monitoring devices to obtain a subscription device 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, searching whether the subscription device type set comprises the target subscription device type contained in the updated subscription information or not, wherein the target monitoring device is any monitoring device in the plurality of monitoring devices;

if the target subscribing device type is not included in the subscribing device type set, updating the subscribing device type set based on the target subscribing device type.

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

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

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

sequentially acquiring a plurality of sub-threads from a thread resource pool, and when one sub-thread is acquired, distributing a query task to the acquired target sub-thread, wherein the query task comprises equipment address information of a target medical equipment, and 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 storing the equipment state information into a database after acquiring the equipment state information of the corresponding medical equipment;

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

Optionally, the apparatus 400 is further configured to:

detecting whether the count value of the 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 one of the plurality of sub-threads completes 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 acquisition module 402 is triggered to execute a step of acquiring device state information of a plurality of target medical devices obtained by a plurality of sub-threads from the database.

Optionally, the apparatus 400 is further configured to:

And after detecting that the target sub-thread completes the allocated query task, recycling the target sub-thread to the thread resource pool.

Optionally, the sending module 403 is further configured to:

In summary, in the embodiment of the present application, the main line Cheng Meige of the server actively acquires the device state information based on the subscription device type provided in advance by the monitoring device, and pushes the acquired device state information of the medical device to the monitoring device, so when a certain monitoring device monitors the same medical device or the same type of medical device at the same time, compared with a mode that each monitoring device actively requests the device state information to the server, the server can be prevented from repeatedly acquiring the device state information of certain medical devices, thereby saving the processing resources of the server.

It should be noted that, when the apparatus for acquiring device status information provided in the foregoing embodiment acquires device status information, only the division of the foregoing functional modules is used as an example, in practical application, the foregoing functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus for acquiring the device state information provided in the foregoing embodiment belongs to the same concept as the method embodiment for acquiring the device state information, and the specific implementation process of the apparatus is detailed in the method embodiment, which is not described herein again.

Fig. 5 is a schematic diagram of a server architecture according to one exemplary 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 backend server cluster. Specifically, the present invention relates to a method for manufacturing a semiconductor device.

The server 500 includes a central processing unit (Central Processing Unit, CPU) 501, a system Memory 504 including a random access Memory (Random Access Memory, RAM) 502 and a Read-Only Memory (ROM) 503, and a system bus 505 connecting the system Memory 504 and the central processing unit 501. The server 500 also includes a basic Input/Output system (I/O) 506 for facilitating the transfer of information between various 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 includes a display 508 for displaying information and an input device 509, such as a mouse, keyboard, etc., for user input of information. Wherein both the display 508 and the input device 509 are coupled to the central processing unit 501 via an input output controller 510 coupled 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, the 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 CD-ROM (Compact Disc Read-Only Memory) drive.

Computer readable media may include computer storage media and communication media without loss of generality. 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, erasable programmable read-only memory), EEPROM (Electrically Erasable Programmable Read Only Memory, charged erasable programmable read-only memory), flash memory or other solid state memory device, CD-ROM, DVD (Digital Versatile Disc, 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 recognize that computer storage media are not limited to the ones described above. 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, the server 500 may also operate by a remote computer connected to the network through a network, such as the Internet. I.e., server 500 may be connected to network 512 via a network interface unit 511 coupled to system bus 505, or other types of networks or remote computer systems (not shown) may be coupled to using network interface unit 511.

The memory also includes one or more programs, one or more programs stored in the memory and configured to be executed by the CPU. The one or more programs include instructions for performing the methods of obtaining device state information provided by embodiments of the present application.

The present application also provides a computer-readable storage medium, which when executed by a processor of a server, enables the server to perform the method for acquiring device state information provided in the above embodiments. For example, the computer readable storage medium may be ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc. It is noted that the computer readable storage medium mentioned in the embodiments of the present application may be a non-volatile storage medium, in other words, may be a non-transitory storage medium.

It should be understood that all or part of the steps to implement the above-described 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 that, when run on a computer, cause the computer to perform the method of acquiring device state 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 related to the embodiments of the present application are all authorized by the user or are fully authorized by the parties, and the collection, use and processing of the related data is required to comply with the relevant laws and regulations and standards of the relevant countries and regions.

The foregoing description is not intended to limit the embodiments of the present application, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the embodiments of the present application are intended to be included within the scope of the embodiments of the present application.

Claims

1. A method of obtaining device state information, for use with a main thread in a server, the method comprising:

performing de-duplication on the received subscription equipment types in the subscription information of the plurality of monitoring equipment to obtain a subscription equipment type set, wherein the subscription equipment type set comprises a plurality of subscription equipment types, and each subscription equipment type corresponds to at least one monitoring equipment in the plurality of monitoring equipment;

determining a plurality of target medical devices matched with the subscription device types in the subscription device type set from a plurality of medical devices at preset time intervals;

acquiring 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 of the plurality of sub-threads is used for acquiring the device state information of one medical device;

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

3. The method of claim 1, wherein the obtaining, by a plurality of sub-threads, device status information of the plurality of target medical devices based on device address information of the plurality of target medical devices comprises:

4. The method of claim 3, wherein prior to obtaining device state information for the plurality of target medical devices obtained by the plurality of sub-threads from the database, further comprising:

5. A method according to claim 3, characterized in that the method further comprises:

6. The method of claim 1, wherein pushing the obtained device state information to the plurality of monitoring devices according to the set of subscribed device types comprises:

7. An apparatus for obtaining device state information, the apparatus being applied to a main thread in a server, the apparatus comprising a processor having a main thread running therein, the main thread being configured to:

8. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a computer program which, when executed by a computer, implements the method of acquiring device state information according to any of claims 1-6.