Hospital calling method, device and equipment based on SIP (Session Initiation Protocol), and medium

Abstract

The invention provides a hospital calling method, device and equipment based on an SIP (Session Initiation Protocol), and a medium, and the method comprises the steps: receiving an operation request sent by a calling terminal, adding the operation request into a request queue, and analyzing the priority, the request type and the authority of the operation request; matching at least one response device according to the priority decreasing sequence and the request type and authority of the operation request, and distributing the operation request to the at least one response device to receive a response result returned by the at least one response device and the state of the response device, the response result is sent to the calling terminal; and deleting the current operation request in the request queue based on the state of the at least one response device, and distributing the next operation request, so as to solve the problems that the patient can only call a nurse, the nurse calls a doctor, the call is not timely, and the emergency level cannot be reflected during the call.

Description

Technical Field

[0001] The present invention relates to the field of smart hospital technology, and in particular to a hospital call method, device, equipment and medium based on the SIP protocol. Background Art

[0002] In today's medical environment, the construction of smart hospitals has become an important trend to improve the quality and efficiency of medical services. Among them, the continuous evolution and innovation of call methods have brought significant changes to medical services.

[0003] In the past, the calling methods of traditional hospitals were relatively simple and limited, usually relying on wired bedside call buttons. Patients could only send a simple help signal to the nurse station through a single button. This method has many shortcomings, such as unclear information transmission, slow response speed, and inability to track the processing progress in real time. With the rapid development of information technology, the calling methods in smart hospitals have gradually become more diversified and intelligent. Nowadays, mobile calling terminals based on wireless networks are widely used. Patients can call the nurse station by pressing the bell next to the bed, and the urgency level of the call can only be known through the patient's description. At the same time, the different urgency levels in the call cannot be notified to the nurse in time, resulting in missed emergencies, and the doctor needs to convey the patient's condition through the nurse, which is easy to cause the condition of seriously ill patients to be delayed.

[0004] Therefore, there is an urgent need to propose a hospital calling method based on the SIP protocol (Session Initiation Protocol) to solve the technical problems in the prior art that patients can only call nurses, nurses calling doctors result in untimely calls, and the emergency level cannot be reflected during the call. Summary of the invention

[0005] In order to overcome the problems existing in the related art, the present disclosure provides a hospital calling method, device, equipment and medium based on the SIP protocol to solve the technical problems in the related art that patients can only call nurses, the calls caused by nurses calling doctors are not timely, and the emergency level cannot be reflected during the call.

[0006] One or more embodiments of this specification provide a hospital calling method based on the SIP protocol, comprising the following steps:

[0007] The calling terminal publishes the operation request message in the ActiveMo messaging middleware via MQTT;

[0008] ActiveMo message middleware sends the operation request message to the call queue in the call logic engine;

[0009] The call logic engine determines the priority level of the operation request message, and initiates the operation request to the response terminal subscribed to the operation request message through the ActiveMo message middleware according to the priority levels from high to low;

[0010] The responding terminal generates and displays the call information and ringing information according to the operation request, and sends the terminal status of the responding terminal to the call logic engine and the calling terminal in real time.

[0011] Preferably, the sending of the terminal status of the responding terminal to the call logic engine and the calling terminal in real time further includes the following steps:

[0012] After the responding device responds to the operation request, the status of the responding device is published in the ActiveMo messaging middleware via MQTT;

[0013] ActiveMo message middleware sends the status of the responding device to the call logic engine and the calling device in real time.

[0014] Preferably, after the responding device responds to the operation request, the following steps are further included:

[0015] After the operation in response to the operation request is completed, the call logic engine deletes the current operation request from the call queue, determines the priority level of the operation request message again, and initiates the operation request to the response terminal that subscribes to the operation request message through the ActiveMo message middleware according to the priority level from high to low.

[0016] Preferably, when the operation request message is a call request message, the following steps are further included:

[0017] The calling terminal sends an INVITE request to the SIP server;

[0018] After receiving the INVITE request, the SIP server initiates a call to the response terminal that subscribes to the operation request message;

[0019] After the responding terminal user answers the call, he / she makes a voice and video call with the calling terminal through the SIP protocol, and sends the call status of the responding terminal to the call logic engine and the calling terminal in real time.

[0020] Preferably, the response terminal generates and displays the call information and ringing information according to the operation request, and further comprises the following steps:

[0021] The display duration of the ringing information and the call information is a preset duration, and the number of ringing times is a preset number. If the preset duration or the preset number of times is exceeded, it automatically returns to a no-response state.

[0022] Preferably, the request types of the operation request include reinforcement, emergency, normal and disposal, wherein the descending order of priority is reinforcement>emergency>normal>disposal.

[0023] One or more embodiments of this specification provide a hospital call device based on the SIP protocol, including a message publishing module,

[0024] Queue module, request module and response module;

[0025] The message publishing module is used for the calling terminal to publish the operation request message in the ActiveMo message middleware through MQTT;

[0026] The queue module is used for ActiveMo message middleware to send the operation request message to the call queue in the call logic engine;

[0027] The request module is used to call the logic engine to determine the priority level of the operation request message, and initiate an operation request to the response terminal that subscribes to the operation request message through the ActiveMo message middleware according to the priority levels from high to low;

[0028] The response module is used for the response terminal to generate and display call information and ring information according to the operation request, and to send the terminal status of the response terminal to the call logic engine and the calling terminal in real time.

[0029] Preferably, the response module is further configured to:

[0030] Used to publish the status of the responding device in the ActiveMo messaging middleware through MQTT after the responding device responds to the operation request;

[0031] ActiveMo message middleware sends the status of the responding device to the call logic engine and the calling device in real time.

[0032] One or more embodiments of the present specification provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the hospital call method based on the SIP protocol as described above when executing the computer program.

[0033] One or more embodiments of the present specification provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the hospital call method based on the SIP protocol are implemented as described above.

[0034] The present invention provides a hospital call method, device, equipment and medium based on the SIP protocol, which has the advantages that the call terminal publishes the operation request message in the ActiveMo message middleware through MQTT, so that the operation request message can be quickly published, asynchronous communication can be realized, and the response speed of the system can be improved; the ActiveMo message middleware sends the operation request message to the call queue in the call logic engine, so as to realize the decoupling, asynchronous processing, reliability, flexibility and monitorability of the system, and provide strong technical support for the efficient operation of the call system; the call logic engine determines the priority level of the operation request message, and initiates the operation request to the response terminal subscribed to the operation request message through the ActiveMo message middleware according to the priority level from high to low, so as to realize efficient resource allocation, meet emergency needs and enhance system stability; the response terminal generates call information and ringing information according to the operation request and displays it, and sends the terminal status of the response terminal to the call logic engine and the call terminal in real time, so as to realize timely feedback and communication, improve processing efficiency, enhance system reliability, improve the response speed of the hospital system to patient calls, improve the medical environment for patients, and ensure the safety of patients. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0036] Figure 1 A flowchart of a hospital calling method based on the SIP protocol provided for one or more embodiments of this specification;

[0037] Figure 2 A system architecture diagram of a hospital calling method based on the SIP protocol provided for one or more embodiments of this specification;

[0038] Figure 3 A flowchart of the processing logic provided for one or more embodiments of this specification;

[0039] Figure 4 A flowchart of call logic provided for one or more embodiments of this specification;

[0040] Figure 5 A flowchart of hang-up logic provided for one or more embodiments of this specification;

[0041] Figure 6A flowchart of answering logic provided for one or more embodiments of this specification;

[0042] Figure 7 A flowchart of information sending logic provided for one or more embodiments of this specification;

[0043] Figure 8 A schematic diagram of the structure of a hospital call device based on the SIP protocol provided in one or more embodiments of this specification;

[0044] Fig. 9 A schematic diagram of the structure of a computer device provided for one or more embodiments of this specification. DETAILED DESCRIPTION

[0045] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the protection scope of the present invention.

[0046] The present invention is described in detail below in conjunction with specific implementation methods and the accompanying drawings.

[0047] Method Embodiment

[0048] According to an embodiment of the present invention, a hospital calling method based on the SIP protocol is provided, such as Figure 1 FIG. 1 is a flow chart of a hospital calling method based on the SIP protocol provided in this embodiment. The hospital calling method based on the SIP protocol according to the embodiment of the present invention comprises the following steps:

[0049] S110. The calling terminal publishes the operation request message in the ActiveMo message middleware through MQTT. The calling terminal is located next to the bed, and at least one response device corresponding to the bed is located at the nurse station or doctor's office. Different request types correspond to different response devices. Whether different response devices can be called is determined according to the authority of the operation request.

[0050] S120. ActiveMo message middleware sends the operation request message to a call queue in a call logic engine.

[0051] S130. The call logic engine determines the priority level of the operation request message, and initiates an operation request to a response terminal that subscribes to the operation request message through the ActiveMo message middleware according to the priority levels from high to low.

[0052] S140: The responding terminal generates and displays call information and ringing information according to the operation request, and sends the terminal status of the responding terminal to the call logic engine and the calling terminal in real time.

[0053] like Figure 2 As shown, it is a system architecture diagram of the hospital calling method based on the SIP protocol provided in this embodiment.

[0054] The method provided in this embodiment publishes the operation request message in ActiveMo message middleware through MQTT by the calling terminal, so as to quickly publish the operation request message, realize asynchronous communication and improve the response speed of the system; ActiveMo message middleware sends the operation request message to the call queue in the call logic engine, realizes the decoupling, asynchronous processing, reliability, flexibility and monitorability of the system, and provides strong technical support for the efficient operation of the call system; the call logic engine determines the priority level of the operation request message, and initiates the operation request to the response terminal that subscribes to the operation request message through ActiveMo message middleware according to the priority level from high to low, so as to realize efficient resource allocation, meet emergency needs and enhance system stability; the response terminal generates call information and ringing information according to the operation request and displays it, and sends the terminal status of the response terminal to the call logic engine and the calling terminal in real time, so as to realize timely feedback and communication, improve processing efficiency, enhance system reliability, improve the response speed of the hospital system to patient calls, improve the medical environment for patients, and ensure the safety of patients.

[0055] In one embodiment, the sending of the terminal status of the responding terminal to the call logic engine and the calling terminal in real time further includes the following steps:

[0056] After the responding device responds to the operation request, the status of the responding device is published in the ActiveMo message middleware through MQTT, and the status of the responding device includes no one connected, hung up and answered, and the response result includes displaying the response status of the responding device or the operation request.

[0057] ActiveMo message middleware sends the status of the responding device to the call logic engine and the calling device in real time.

[0058] The method provided in this embodiment publishes the status of the responding device in the ActiveMQ message middleware through MQTT after the responding device responds to the operation request, and the ActiveMQ message middleware sends the status of the responding device to the call logic engine and the calling device in real time, which can achieve real-time feedback and collaboration, improve system efficiency and reliability, enhance user experience and decision support, and promote system integration and scalability.

[0059] In one embodiment, after the responding device responds to the operation request, the following steps are further included:

[0060] After the operation in response to the operation request is completed, the call logic engine deletes the current operation request from the call queue, determines the priority level of the operation request message in the request queue again, and initiates the operation request to the response terminal that subscribes to the operation request message through the ActiveMo message middleware according to the priority level from high to low.

[0061] The method provided in this embodiment, after the operation in response to the operation request is completed, the call logic engine deletes the current operation request from the call queue, again determines the priority level of the operation request message and initiates a new request in sequence, with the features of efficient task management, optimized resource allocation and enhanced system stability.

[0062] In one embodiment, when the operation request message is a call request message, the following steps are further included:

[0063] The calling terminal sends an INVITE request to the SIP server.

[0064] After receiving the INVITE request, the SIP server initiates a call to the response terminal that subscribes to the operation request message.

[0065] In the method provided in this embodiment, when the operation request message is a call request message, executing the above steps can achieve efficient communication, enhance interactivity and collaboration, and improve the intelligence and automation of the system.

[0066] In one embodiment, the response terminal generates and displays the call information and ring information according to the operation request, and further comprises the following steps:

[0067] The display duration of the ringing information and the call information is a preset duration, and the number of ringing times is a preset number. If the preset duration or the preset number of times is exceeded, it automatically returns to a no-response state.

[0068] The method provided in this embodiment sets a preset duration and a preset number of times when the response terminal displays ringing information and call information, and automatically returns to an unresponsive state after exceeding the time, thereby improving system efficiency, enhancing user experience, and facilitating management and monitoring.

[0069] In one embodiment, the request types of the operation request include reinforcement, emergency, normal and disposal, wherein the descending order of priority is reinforcement>emergency>normal>disposal.

[0070] The method provided in this embodiment sets different priority request types for the patient's operation request, and then processes the operation request in descending order of priority, thereby avoiding missing emergency situations and improving emergency rescue efficiency.

[0071] The following is further explained through specific examples:

[0072] like Figure 3 As shown, it is a flowchart of the processing logic provided in this embodiment.

[0073] Processing logic:

[0074] Call terminal operation request-disposal, and send a DISPOSAL message;

[0075] The logic platform receives the disposal and sends an ON_DISPOSAL message to notify the responding device and the calling terminal to enter the disposal state;

[0076] When the response device receives the disposal message, different devices make different response actions, including door extension: lighting up according to call priority, door light: lighting up according to call priority, corridor screen: displaying call / disposal information according to call priority.

[0077] like Figure 4 The figure is a flowchart of the call logic provided in this embodiment.

[0078] Call logic:

[0079] The calling terminal initiates a call and sends a CALL message;

[0080] The logic platform receives the call and adds it to the call queue. It stores the queues of each call type in the order of reinforcement, emergency, normal, and disposal. It processes the call with the highest priority in the call queue in the order of reinforcement > emergency > normal > disposal. It sends an ON_CALL message to the call initiator to inform the call initiator that the engine has received the call and can enter the calling state. It sends an ON_RING message to the call responder to inform the call responder to start ringing.

[0081] The responding device receives the ON_RING message. Different devices respond to this message in different ways. The device starts ringing and enters the ringing page. The device also sends the ON_RING_STATE message, which indicates that the device has entered the ringing state.

[0082] The logic platform saves the response device status;

[0083] After the responding device rings three times, the device that finishes the first ring sends a FINISH_RING_STATE message;

[0084] After the ringing is finished, the logic platform continues to process the highest priority call from the call queue and sends an ON_RING message to the call responder to notify the call responder to start ringing.

[0085] After the responding device rings three times, the device that finishes the first ring sends a FINISH_RING_STATE message.

[0086] like Figure 5 As shown, it is a schematic diagram of the hang-up logic flow provided by this embodiment.

[0087] Hang up logic:

[0088] In response to the device hanging up the ring, a HANGUP_RING message is sent;

[0089] The logic platform receives the hang-up ring and deletes the call from the call queue; checks whether the call queue is empty. If not, it continues to the process in the [Call Logic] operation; if it is empty, it continues to the next process; notifies the calling terminal that the call has been processed, sends an END_HANDLE message to the calling terminal, and the call initiator displays the page that the nurse has processed; notifies the calling terminal that the call is over, and notifies the responding device that the ringing ends; sends an OFF_CALL message to notify the calling terminal that the call is over, and sends an OFF_RING message to notify the responding device that the ringing ends;

[0090] The calling terminal receives the OFF_CALL message and sends an OFF_CALL_STATE message, and returns to the information display page;

[0091] The responding device receives the OFF_RING message and sends an OFF_RING_STATE message, returns to the information display page, sends an OFF_RING_STATE message, and ends the ringing;

[0092] The logical platform maintains the state of the calling terminal and the responding equipment.

[0093] like Figure 6 As shown, it is a flowchart of the answering logic provided in this embodiment.

[0094] Answering logic

[0095] The responding device answers the call and sends an ANSWER message;

[0096] The logic platform receives the incoming call, deletes the call from the call queue, and checks whether the call queue is empty. If not, it continues to the process in the [Call Logic] operation; if it is empty, it continues to the next process and sends an OFF_RING message to the call initiator to notify the call initiator that the engine has received the incoming call and the ringing state can be ended;

[0097] The responding device receives the OFF_RING message and sends the OFF_RING_STATE message, and sends the OFF_CALL_STATE message to end the call state.

[0098] The logic platform notifies the calling terminal that the call has been processed, sends an END_HANDLE message, notifies the two devices in the call, starts the call, and sends an ON_VOICE message to the two devices in the call to start the call;

[0099] The calling terminal receives the ON_VOICE message, sends an ON_TALK_STATE message, and displays the call page;

[0100] The responding device hangs up the call and sends a HANGUP message;

[0101] The logic platform notifies the two devices in the call to end the call and sends an OFF_VOICE message to the two devices in the call to end the call;

[0102] The calling terminal receives the OFF_VOICE message and sends the OFF_TALK_STATE message. After receiving the message, the engine checks whether the call queue is empty. If not, it continues to the process in the [Call Logic] operation; if it is empty, it continues to the next process;

[0103] The logic platform notifies the device to enter the idle state, sends an ON_IDLE message to the two devices in the call, and enters the idle state;

[0104] The calling terminal and the responding device receive the ON_IDLE message and send an IDLE_STATE message;

[0105] The logical platform saves the device state.

[0106] like Figure 7 The figure is a flow chart of the information sending logic provided in the embodiment.

[0107] Information sending logic

[0108] The message is put into the message queue, and MQ is used to send the message to the engine, which then sends it to the Android terminal through MQ, Android->booter:

[0109] HTTP to obtain patient information

[0110] booter->Android: HTTP returns patient information

[0111] alt HTTP returns patient information successfully

[0112] Android->bingquMQ:pub MQTT@DATA_CHECK_CONFIRM

[0113] bingquMQ->Engine:sub MQTT@DATA_CHECK_CONFIRM

[0114] Engine->Engine: Delete the corresponding device in the handshake queue

[0115] end

[0116] Device Embodiment

[0117] According to an embodiment of the present invention, a hospital calling device based on the SIP protocol is provided, such as Figure 8 As shown, it is a structural diagram of the hospital call device based on the SIP protocol provided in this embodiment. According to the hospital call device based on the SIP protocol in this embodiment of the present invention, it includes a message publishing module 81, a queue module 82, a request module 83 and a response module 84.

[0118] The message publishing module 81 is used for the calling terminal to publish the operation request message in the ActiveMo message middleware through MQTT.

[0119] The queue module 82 is used by ActiveMo message middleware to send the operation request message to the call queue in the call logic engine.

[0120] The request module 83 is used for calling the logic engine to determine the priority level of the operation request message, and to initiate an operation request to a response terminal subscribed to the operation request message through the ActiveMo message middleware according to the priority levels from high to low.

[0121] The response module 84 is used for the response terminal to generate and display call information and ring information according to the operation request, and to send the terminal status of the response terminal to the call logic engine and the calling terminal in real time.

[0122] In the device provided in this embodiment, the message publishing module 81 publishes the operation request message in the ActiveMo message middleware through the calling terminal through MQTT, which can quickly publish the operation request message, realize asynchronous communication, and improve the response speed of the system; the queue module 82 sends the operation request message to the call queue in the call logic engine through the ActiveMo message middleware, realizes the decoupling, asynchronous processing, reliability, flexibility and monitorability of the system, and provides strong technical support for the efficient operation of the call system; the request module 83 determines the priority level of the operation request message through the call logic engine, and initiates the operation request to the response terminal that subscribes to the operation request message through the ActiveMo message middleware according to the priority level from high to low, which can realize efficient resource allocation, meet emergency needs, and enhance system stability; the response module 84 generates call information and ringing information according to the operation request through the response terminal and displays it, and sends the terminal status of the response terminal to the call logic engine and the calling terminal in real time, which can realize timely feedback and communication, improve processing efficiency, enhance system reliability, improve the response speed of the hospital system to patient calls, improve the patient's medical environment, and ensure the safety of patients.

[0123] In one embodiment, the response module 84 is further configured to:

[0124] Used to publish the state of the responding device in the ActiveMo message middleware through MQTT after the responding device responds to the operation request.

[0125] ActiveMo message middleware sends the status of the responding device to the call logic engine and the calling device in real time.

[0126] The apparatus provided in this embodiment publishes the status of the responding device in the ActiveMQ message middleware through MQTT after the responding device responds to the operation request, and the ActiveMQ message middleware sends the status of the responding device to the call logic engine and the calling device in real time, which can realize real-time feedback and collaboration, improve system efficiency and reliability, enhance user experience and decision support, and promote system integration and scalability.

[0127] The embodiment of the present invention is an apparatus embodiment corresponding to the above-mentioned method embodiment. The specific operations of the processing steps of each module can be understood by referring to the description of the method embodiment, which will not be repeated here.

[0128] like Fig. 9As shown, the present invention also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the hospital call method based on the SIP protocol in the above embodiment is implemented, or when the computer program is executed by a processor, the hospital call method based on the SIP protocol in the above embodiment is implemented.

[0129] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0130] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The device and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0131] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein by equivalents. These modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present invention, and the contents not described in detail in the specification of the present invention belong to the common knowledge of those skilled in the art.

Claims

1. A hospital calling method based on SIP protocol, characterized in that: The following steps are involved: The calling terminal publishes the operation request message in the ActiveMo messaging middleware via MQTT; ActiveMo message middleware sends the operation request message to the call queue in the call logic engine; The call logic engine determines the priority level of the operation request message, and initiates the operation request to the response terminal subscribed to the operation request message through the ActiveMo message middleware according to the priority levels from high to low; The responding terminal generates and displays the call information and ringing information according to the operation request, and sends the terminal status of the responding terminal to the call logic engine and the calling terminal in real time.

2. The hospital calling method based on SIP protocol as claimed in claim 1, characterized in that: The step of sending the terminal status of the responding terminal to the call logic engine and the calling terminal in real time also includes the following steps: After the responding device responds to the operation request, the status of the responding device is published in the ActiveMo messaging middleware via MQTT; ActiveMo message middleware sends the status of the responding device to the call logic engine and the calling device in real time.

3. The hospital calling method based on SIP protocol as claimed in claim 2, characterized in that: After the responding device responds to the operation request, the following steps are further included: After the operation in response to the operation request is completed, the call logic engine deletes the current operation request from the call queue, determines the priority level of the operation request message again, and initiates the operation request to the response terminal that subscribes to the operation request message through the ActiveMo message middleware according to the priority level from high to low.

4. The hospital calling method based on SIP protocol as claimed in claim 1, characterized in that: When the operation request message is a call request message, the following steps are also included: The calling terminal sends an INVITE request to the SIP server; After receiving the INVITE request, the SIP server initiates a call to the response terminal that subscribes to the operation request message; After the responding terminal user answers the call, he / she makes a voice and video call with the calling terminal through the SIP protocol, and sends the call status of the responding terminal to the call logic engine and the calling terminal in real time.

5. The hospital calling method based on SIP protocol as claimed in claim 3, characterized in that: The response terminal generates call information and ring information according to the operation request and displays them, and further comprises the following steps: The display duration of the ringing information and the call information is a preset duration, and the number of ringing times is a preset number. If the preset duration or the preset number of times is exceeded, it automatically returns to a no-response state.

6. The hospital calling method based on SIP protocol as claimed in claim 1, characterized in that: The request types of the operation request include reinforcement, emergency, normal and disposal, wherein the descending order of priority is reinforcement>emergency>normal>disposal.

7. A hospital call device based on SIP protocol, characterized in that: Including message publishing module, queue module, request module and response module; The message publishing module is used for the calling terminal to publish the operation request message in the ActiveMo message middleware through MQTT; The queue module is used for ActiveMo message middleware to send the operation request message to the call queue in the call logic engine; The request module is used to call the logic engine to determine the priority level of the operation request message, and initiate an operation request to the response terminal that subscribes to the operation request message through the ActiveMo message middleware according to the priority levels from high to low; The response module is used for the response terminal to generate and display call information and ring information according to the operation request, and to send the terminal status of the response terminal to the call logic engine and the calling terminal in real time.

8. The hospital calling device based on SIP protocol as claimed in claim 7, characterized in that: The response module is further configured as: Used to publish the status of the responding device in the ActiveMo messaging middleware through MQTT after the responding device responds to the operation request; ActiveMo message middleware sends the status of the responding device to the call logic engine and the calling device in real time.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the hospital calling method based on the SIP protocol as claimed in any one of claims 1 to 6 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the hospital call method based on the SIP protocol as claimed in any one of claims 1 to 6 are implemented.

Images