CN114036092A - Medical equipment operation management system, method and storage medium - Google Patents
Medical equipment operation management system, method and storage medium Download PDFInfo
- Publication number
- CN114036092A CN114036092A CN202111357150.4A CN202111357150A CN114036092A CN 114036092 A CN114036092 A CN 114036092A CN 202111357150 A CN202111357150 A CN 202111357150A CN 114036092 A CN114036092 A CN 114036092A
- Authority
- CN
- China
- Prior art keywords
- client
- server
- equipment
- manager
- inter
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 175
- 238000004891 communication Methods 0.000 claims abstract description 111
- 230000003993 interaction Effects 0.000 claims abstract description 9
- 238000007726 management method Methods 0.000 claims description 72
- 230000008569 process Effects 0.000 claims description 26
- 230000001360 synchronised effect Effects 0.000 claims description 25
- 238000012545 processing Methods 0.000 claims description 16
- 238000013507 mapping Methods 0.000 claims description 14
- 230000007246 mechanism Effects 0.000 claims description 8
- 230000008676 import Effects 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 20
- 239000003795 chemical substances by application Substances 0.000 description 19
- 230000004044 response Effects 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 230000018109 developmental process Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000011017 operating method Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000013528 artificial neural network Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000001939 inductive effect Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000005693 optoelectronics Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000001902 propagating effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/382—Information transfer, e.g. on bus using universal interface adapter
- G06F13/385—Information transfer, e.g. on bus using universal interface adapter for adaptation of a particular data processing system to different peripheral devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Abstract
The invention relates to an operation management system, a method and a storage medium of medical equipment, wherein the system comprises a client and a server which are mutually communicated and connected, and the medical equipment is respectively provided with corresponding equipment components at the client and the server for abstract representation, wherein the equipment components are operated and managed through communication interaction between the client and the server so as to realize configuration operation of the medical equipment. According to the invention, different equipment components are developed in parallel based on the equipment operation framework, and the software development efficiency of the magnetic resonance system can be improved.
Description
Technical Field
The present invention relates to the field of medical device management technologies, and in particular, to an operation management system, method and storage medium for medical devices.
Background
The device components are created by abstracting and summarizing a plurality of functional requirements of various medical devices, and are abstract representations of the medical devices in a hardware management system, and different medical devices are expressed by corresponding unique device components in the corresponding hardware management system. In the device system, the configuration of the medical device is often changed, such as deleted, added, or modified, and in the hardware management system, the corresponding device component is also required to be newly developed.
For example, the magnetic resonance system uses a great number of medical devices, such as UART devices, USB devices, PCIe devices, SPI devices, CAN devices, I2C devices, and so on, and the number of the devices and the kinds of the devices are very large, wherein each medical device has different functional features, the communication interfaces of the medical devices are different, and the hardware of the magnetic resonance system configuration is different for different models. Thus, on the one hand, in a magnetic resonance system, the number of medical devices is large, resulting in difficulty in management; on the other hand, when the medical device needs to be reconfigured, the corresponding device component is often required to be redeveloped, and the research and development efficiency is greatly reduced.
In summary, medical device management is difficult, and the overall development efficiency is reduced because of the large workload required for the redevelopment of device components, so how to efficiently manage and develop device components is a problem to be solved.
Disclosure of Invention
In view of the above, there is a need to provide a system, a method and a storage medium for managing operation of medical devices, so as to overcome the problems of difficult management and low development efficiency of medical devices in the prior art.
The invention provides an operating system of medical equipment, which comprises a client and a server which are in communication connection with each other, wherein the medical equipment is provided with corresponding equipment components for abstract representation on the client and the server respectively, and the equipment components are operated and managed through communication interaction between the client and the server so as to realize configuration operation of the medical equipment.
Further, the client is configured to send a device operation request of a caller to the server; the operation result data generated by the server is also received; and the server is used for issuing the received equipment operation request to the corresponding medical equipment for operation, generating the operation result data and sending the operation result data to the client.
Further, the client includes an in-process client for managing a first operation interface of the at least one in-process device component and an inter-process client for managing a second operation interface of the at least one inter-process device component, wherein:
the in-process client comprises an in-process device component manager, wherein the in-process device component manager is used for calling the first operation interface and sending the device operation request to the server, and the in-process device component is an abstract representation corresponding to the medical device in the in-process client;
the interprocess client comprises an interprocess equipment component manager and a client interprocess communication manager, wherein the interprocess equipment component manager is used for calling the second operation interface, and the client interprocess communication manager is used for interacting with the server through an interprocess communication mechanism according to the called second operation interface and sending the equipment operation request, wherein the interprocess equipment component is an abstract representation corresponding to the medical equipment in the interprocess client.
Further, the server comprises a server device component manager, a server inter-process communication manager, a hardware access manager and a communication packet manager, wherein:
the server equipment component manager is used for managing a third operation interface of at least one server equipment component and calling the third operation interface to send the equipment operation request to the corresponding medical equipment;
the server inter-process communication manager comprises at least one inter-process communication server, and the at least one inter-process communication server is used for interacting with the client inter-process communication manager by adopting an inter-process communication mechanism;
the hardware access manager comprises a hardware access server of at least one medical device, and the hardware access server is used for interacting with the medical device which only corresponds to the hardware access server;
the communication packet manager is used for managing various equipment communication packets, wherein the equipment communication packets are used for transmitting equipment access messages between the hardware interface of the medical equipment and the third operation interface.
Further, the hardware access server comprises an asynchronous access agent manager, a synchronous access agent manager and a client communication transaction manager, wherein:
the asynchronous access proxy manager is used for receiving the equipment operation request by using an asynchronous proxy when the communication manager between the client processes in the client sends the equipment operation request, and determining the third operation interface according to a command number in the equipment operation request;
the synchronous access agent manager is used for receiving the equipment operation request by utilizing synchronous agent processing when the in-process equipment component manager in the client sends the equipment operation request, and determining the third operation interface according to a command number in the equipment operation request;
and the client communication transaction manager is used for managing access transactions with the client.
The invention also provides an operating method of the medical device, which is applied to the client in the operation management system of the hardware device, and the operating method comprises the following steps:
the client sends an equipment operation request of a caller to a server, wherein the server issues the received equipment operation request to corresponding medical equipment for operation, generates operation result data and sends the operation result data to the client;
and the client receives the operation result data generated by the server and feeds the operation result data back to the caller.
Further, in the step of determining, by the client, the client operation interface of the corresponding client device component according to the device operation request, the method includes:
the client determines a first name of a client device component needing to be called according to the device operation request, wherein the client device component is an abstract representation of the medical device needing to be called by the caller on the client;
the client determines and calls a client operation interface corresponding to the client equipment component based on the mapping relation in the first dynamic library according to the first name;
the client side imports the first dynamic library which feeds back mapping relations of various information of the client side equipment assembly according to a prestored configuration file; and the client initializes the client equipment component according to the first dynamic library.
The invention also provides an operation management method of a medical device, which is applied to the server in the operation management system of the hardware device, and the operation management method comprises the following steps:
the server sends the received equipment operation request to the corresponding medical equipment for operation, generates operation result data and sends the operation result data to a client, wherein the client sends the equipment operation request of a caller to the server, and the client receives the operation result data generated by the server and feeds the operation result data back to the caller.
Further, in the step that the server issues the received device operation request to the corresponding medical device for operation, generates operation result data and sends the operation result data to the client, the method includes:
the server determines a second name of a server equipment component to be called according to the received equipment operation request, wherein the server equipment component is an abstract representation of the medical equipment to be called by the caller in the server;
the server determines and calls the corresponding third operation interface according to the second name and based on a mapping relation in a second dynamic library, wherein the server imports the second dynamic library which feeds back the mapping relation of various information of the server equipment component according to a prestored configuration file, and the server initializes the server equipment component according to the second dynamic library;
the server accesses the corresponding medical equipment according to the third operation interface, and sends the equipment operation request to the corresponding medical equipment for operation, wherein the medical equipment operates according to the equipment operation request, generates the operation result data and sends the operation result data to the server;
and the server sends the received operation result data to the client.
The present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the operation management method of a medical device applied to a client as described above or the operation management method of a medical device applied to a server as described above.
Compared with the prior art, the invention has the beneficial effects that: in the operation management system of the medical equipment, a client and a server which are communicated with each other are arranged, different medical equipment in the client and the server are abstractly represented by corresponding equipment components, the whole operation management system performs operation management on the equipment components of the client and the server, and simultaneously issues operation management results by using data communication, so that different medical equipment is configured. On the basis of the operation management system of the medical equipment, the equipment operation request of a caller is sent through the client, and after the server receives the equipment operation request, the equipment operation request is issued to the corresponding medical equipment to operate, and the operation result data after the medical equipment operates is received and then sent to the client, so that different configurations of the medical equipment are completed.
Drawings
FIG. 1 is a schematic diagram of an embodiment of an operation management system of a medical device provided by the present invention;
fig. 2 is a schematic structural diagram of an embodiment of a client according to the present invention;
FIG. 3 is a schematic structural diagram of an embodiment of an in-process client according to the present invention;
FIG. 4 is a schematic structural diagram of an embodiment of an interprocess client according to the present invention;
FIG. 5 is a schematic structural diagram of an embodiment of a server provided in the present invention;
FIG. 6 is a schematic structural diagram of an embodiment of an in-process client device component manager, an inter-process client device component manager, or a server device component manager according to the present invention;
FIG. 7 is a block diagram of an embodiment of a server interprocess communication manager;
FIG. 8 is a block diagram of a communication packet manager according to an embodiment of the present invention;
FIG. 9 is a schematic structural diagram of an embodiment of a hardware access server provided in the present invention;
FIG. 10 is a block diagram of an embodiment of a hardware access manager provided in the present invention;
FIG. 11 is a flowchart illustrating an embodiment of a method for managing operation of a medical device applied to a client according to the present invention;
FIG. 12 is a flowchart illustrating an embodiment of step S1101 provided by the present invention;
FIG. 13 is a flowchart illustrating an embodiment of steps included before step S1201 provided in the present invention;
FIG. 14 is a flowchart illustrating an embodiment of step S1302 according to the present invention;
fig. 15 is a schematic flowchart of an embodiment of step S1203 according to the present invention;
FIG. 16 is a flowchart illustrating an embodiment of a server for operation management according to the present invention;
FIG. 17 is a schematic flow chart illustrating an embodiment of steps included before step S1601;
FIG. 18 is a flowchart illustrating an embodiment of step S1601 provided by the present invention;
fig. 19 is a flowchart illustrating an embodiment of step S1602 according to the present invention.
Detailed Description
The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate preferred embodiments of the invention and together with the description, serve to explain the principles of the invention and not to limit the scope of the invention.
In the description of the present invention, the terms "first" and "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implying any number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. Further, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Reference throughout this specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the described embodiments can be combined with other embodiments.
The invention provides an operation management system, a method and a storage medium of medical equipment, wherein different equipment components are developed in parallel based on an equipment operation framework, and a new thought is provided for further improving the system development efficiency. The following are detailed below:
before the specific examples are set forth, the general terms to which the examples of the present invention relate are explained:
the medical device mentioned in the embodiment of the present invention refers to a generic name of various physical devices composed of electronic, mechanical and optoelectronic components in a medical system, and may be a UART device, a USB device, a PCIe device, an SPI device, a CAN device, and an I2C device;
the device component mentioned in the embodiment of the invention is created by abstracting and inducing a plurality of functional requirements of various medical devices, is an abstract representation of each medical device in a device operation management system, and provides a software interface for operating the medical device by service software (such as magnetic resonance system service software) so as to achieve the purpose of managing the medical device.
Referring to fig. 1, fig. 1 is a schematic structural diagram of an embodiment of an operation management system of a medical device provided by the present invention, and the operation management system includes a client 10 and a server 20 that are communicatively connected to each other, and the medical device has corresponding device components for abstract representation at the client 10 and the server 20, where the device components are operated and managed through communication interaction between the client 10 and the server 20, so as to implement configuration operation of the medical device.
In the embodiment of the invention, in the operation management system of the medical equipment, a client and a server which are communicated with each other are arranged, different medical equipment in the client and the server are abstractly represented by corresponding equipment components, and the whole operation management system performs operation management on the equipment components of the client and the server and simultaneously issues the operation management result by utilizing data communication so as to configure different medical equipment.
Wherein, generally speaking, the server is deployed on one computer, and the client can be deployed on different machines according to the needs. For the server and the client, the medical devices have corresponding device components for abstract representation to manage and call interfaces of different medical devices, and different medical devices are configured through communication interaction between the server and the client, where the configuration operation refers to operations of modifying (such as modifying, deleting, adding, replacing, etc. basic hardware configuration information) the medical devices of a certain system.
It should be noted that the operation management system of the medical device may be applied to a magnetic resonance system for hardware management. In the magnetic resonance system, various subsystems are included, such as an examination system operated by a doctor or a technician, a magnetic resonance measurement control system, a calibration system, a safety monitoring system, a sequence control system, a raw data acquisition system, an image reconstruction system and the like, and an operation management system of medical equipment is applied to the magnetic resonance system, so that the medical equipment in various subsystems involved in the operation management system can be managed. Each medical device corresponds to a device component, the device component comprises a client and a server, and other subsystems call an interface provided by the device operation subsystem client. For the operation management system applied to the magnetic resonance system, the server is deployed on the corresponding computer, and the client can be deployed on the machine corresponding to different subsystems, so that the caller can conveniently operate and manage.
As a preferred embodiment, the operation management system of the medical device includes a client and a server, wherein:
a client 10 for sending a device operation request of a caller to a server; the operation data generating unit is also used for receiving operation result data generated by the server;
and the server 20 is configured to issue the received device operation request to the corresponding medical device for operation, generate operation result data, and send the operation result data to the client.
In the embodiment of the invention, based on the CS architecture, the device operation request of the caller is sent by setting the client, and after receiving the device operation request, the server issues the device operation request to the corresponding medical device for operation, receives the operation result data after the medical device is operated, and then sends the operation result data to the client.
As a preferred embodiment, referring to fig. 2, fig. 2 is a schematic structural diagram of an embodiment of a client provided by the present invention, where the client 10 includes an in-process client 101 and an inter-process client 102, where:
the in-process client 101 is used for managing a first operation interface of at least one in-process device component and calling the first operation interface to send a device operation request to the server, wherein the in-process device component is a corresponding intermediate representation of the medical device in the in-process client;
and the inter-process client 102 is configured to manage a second operation interface of at least one inter-process device component, and call the second operation interface to send a device operation request to the server, where the device component in the process is a corresponding intermediate representation of the medical device in the inter-process client.
In the embodiment of the invention, the client is divided into the in-process client and the inter-process client, so that different processes can be effectively ensured to interact with the server by adopting different communication means.
It should be noted that the clients are further divided into an in-process client and an inter-process client, where the functional interfaces provided by the two clients are identical to each other in terms of the processes deployed relative to the device operating subsystem server in the in-process and the inter-process, and only the software deployment is different. The functional interface of the client in the process is provided for other subsystems in the process to use, so that the communication path between the client and the subsystem is shortest, and the efficient management of the equipment in the magnetic resonance scanning process is effectively ensured; and the functional interface of the client-side among the processes is provided for other subsystems which are cross-process to use, so that the system can carry out equipment operation cross-process and cross-machine.
As a preferred embodiment, referring to fig. 3, fig. 3 is a schematic structural diagram of an embodiment of an in-process client provided by the present invention, where the in-process client 101 includes an in-process device component manager 1011, and the in-process device component manager 1011 is configured to invoke a first operation interface, and is further configured to interact with the server 20 in a device synchronous access proxy manner according to the invoked first operation interface, and send a device operation request.
In the embodiment of the invention, the in-process client directly utilizes the in-process equipment component manager to call the first operation interface and utilizes the synchronous access proxy to interact with the server.
In a specific embodiment of the present invention, the in-process client and the server are in the same process, and the in-process client may directly interact with the server. The in-process client need only include the framework function components of the in-process device component manager. Each device component expresses itself in the framework of the in-process client using the in-process client device component, and manages an operation interface provided to the external subsystem, i.e., the first operation interface, using the in-process client device component. When a first operation interface of a client device component in each process is called, a device synchronous access proxy of a hardware access server is directly called to interact with the server, the device synchronous access proxy is responsible for submitting a device operation request (possibly carrying operation data) to the server for processing, and when the server finishes processing, the device synchronous access proxy returns a processing result (possibly carrying result data) to a caller. The whole process uses synchronous operation, and the caller blocks until the operation is completed or the operation is overtime.
As a preferred embodiment, referring to fig. 4, fig. 4 is a schematic structural diagram of an embodiment of an interprocess client provided by the present invention, and the interprocess client 102 includes an interprocess device component manager 1021 and a client interprocess communication manager 1022, wherein:
an inter-process device component manager 1021 for invoking a second operation interface;
the client inter-process communication manager 1022 is configured to interact with the server 20 in an inter-process communication mechanism according to the called second operation interface, and send a device operation request.
In the embodiment of the invention, an inter-process equipment component manager is arranged to effectively call the second operation interface, and a client inter-process communication manager is arranged to perform access interaction with the server.
In a specific embodiment of the present invention, the interprocess client and the server are in different processes, and even in different processes, and the interprocess client needs to interact with the server through interprocess communication. The client inter-process communication manager is preferably an MCDC client manager, namely, the inter-process client comprises two frame function components, namely an inter-process equipment component manager and an MCDC client manager. Each interprocess device component expresses itself in the interprocess client framework using an interprocess client device component and uses the interprocess client device component to manage a second operation interface provided to the external subsystem. When the second operation interface of each interprocess equipment component is called, the second operation interface of each interprocess equipment component needs to interact with the server through the MCDC client manager, the MCDC client manager is responsible for submitting the equipment operation request (possibly carrying operation data) to the MCDC server in the server for processing, and when the MCDC server finishes processing, the MCDC client manager returns the processing result (possibly carrying result data) to the caller. The whole process uses synchronous operation, and the caller blocks until the operation is completed or the operation is overtime. An interprocess client component manager manages these interprocess client device components, while an MCDC client manager manages the communication interactions of these interprocess clients.
As a preferred embodiment, referring to fig. 5, fig. 5 is a schematic structural diagram of an embodiment of a server provided by the present invention, where the server 2 includes a server device component manager 201, a server inter-process communication manager 202, a hardware access manager 203, and a communication packet manager 204, where:
the server device component manager 201 is configured to manage a third operation interface of at least one server device component, and call the third operation interface to send a device operation request to the corresponding medical device;
the server inter-process communication manager 202 comprises at least one inter-process communication server, and the at least one inter-process communication server is used for interacting with the client inter-process communication manager by adopting an inter-process communication mechanism;
a hardware access manager 203 comprising a hardware access server of at least one medical device, the hardware access server for interacting with a uniquely corresponding medical device;
the communication packet manager 204 is configured to manage a plurality of device communication packets, where the device communication packets are used for transmitting device access messages between the hardware interface of the medical device and the third operation interface.
In the embodiment of the invention, a server equipment component manager is arranged to manage a third operation interface of the server; setting a server inter-process communication manager to communicate with an inter-process client; setting a hardware access manager to interact with the medical equipment; and a communication packet manager is arranged to transmit the equipment access message, so that the accuracy of data transmission is ensured.
In a specific embodiment of the present invention, the server-side device component manager manages the server device components at the server side, and when the third operation interface (i.e., the server-side operation interface) of each server device component is called, the corresponding hardware access server issues an operation request to the medical device, and when the medical device is finished processing, the operation and the result and possibly carried data are returned to the client side. The whole process uses synchronous operation, and the caller blocks until the operation is completed or the operation is overtime.
The server-side equipment component manager loads various server equipment components according to configuration files of the server equipment components, wherein the configuration files comprise information such as equipment names, equipment models, equipment IDs and dynamic library names of used equipment components.
In a specific application scenario, taking a magnetic resonance system as an example, types and models of medical devices to be equipped by magnetic resonance systems of different models are also different, each model of magnetic resonance system corresponds to configuration files of different device components (including in-process device components, inter-process device components, and server device components), when an operation management system is initialized, a correct dynamic library (hereinafter referred to as a first dynamic library and a second dynamic library) of the device components is imported according to the configuration files, and the in-process device components, the inter-process device components, and the server device components are initialized at different operation terminals. In this process, a device component manager is needed to manage these different types of device components, and therefore, corresponding device component managers are respectively set at the in-process client, the inter-process client, and the server to manage the corresponding device components, which are respectively referred to as the in-process client device component manager, the inter-process client device component manager, and the server device component manager.
When an external subsystem calls a certain device operation interface, firstly, the corresponding device component is found out according to the device name through the corresponding device component manager, then, the corresponding operation interface is found out according to the operation interface name through the corresponding device component, and finally, the method of the operation interface is called.
In a specific embodiment of the present invention, referring to fig. 6, fig. 6 is a schematic structural diagram of an embodiment of an in-process client device component manager 1011, an inter-process client device component manager 1021, or a server device component manager 201 provided in the present invention, where it can be seen that, no matter the in-process client device component manager, the inter-process client device component manager, or the server device component manager, different device components (including an in-process client device component, an inter-process client device component, and a server device component) and corresponding operation interfaces (including a first operation interface, a second operation interface, and a third operation interface) are correspondingly managed.
In a specific embodiment of the present invention, the server inter-process communication manager is preferably an MCDC server manager, and the inter-process communication server is preferably an MCDC server, and referring to fig. 7, fig. 7 is a schematic structural diagram of an embodiment of the server inter-process communication manager provided by the present invention, where the MCDC server manager 701 includes at least one MCDC server, the MCDC server is managed by the MCDC server manager, the MCDC server is responsible for receiving an operation command request sent by an inter-process client, and the MCDC server manager and the MCDC client manager 701 use an inter-process communication mechanism.
In an embodiment of the present invention, referring to fig. 8, fig. 8 is a schematic structural diagram of an embodiment of the communication packet manager provided in the present invention, the communication packet manager 204 manages various device communication packets (device communication packet 1 to device communication packet N), and when the server communicates with each medical device, one communication packet must be selected. These communication packages share common functions including a transmit interface for transmitting device access messages to the medical device and a receive interface for receiving device access messages from the medical device for processing by the corresponding device component.
As a preferred embodiment, referring to fig. 9, fig. 9 is a schematic structural diagram of an embodiment of a hardware access server provided by the present invention, where the hardware access manager 203 includes at least one hardware access server 2031, and the hardware access server 2031 includes an asynchronous access agent manager 20311, a synchronous access agent manager 20312, and a client communication transaction manager 20313, where:
the asynchronous access proxy manager 20311, configured to receive the device operation request by using an asynchronous proxy when the inter-client-process communication manager sends the device operation request, and determine a third operation interface according to a command number in the device operation request;
the synchronous access agent manager 20312, configured to receive a device operation request sent by the in-process device component manager, process the received device operation request by using a synchronous agent, and determine a third operation interface according to a command number in the device operation request;
the client communication transaction manager 20313 is configured to manage access transactions with the clients.
In the embodiment of the invention, the communication interaction with a communication manager between client processes is managed by setting an asynchronous access proxy manager; managing communication interaction with an in-process device component manager by setting a synchronous access agent manager; and managing the access affairs between the client and the client by arranging the client communication affair manager.
In a specific embodiment of the present invention, referring to fig. 10, fig. 10 is a schematic structural diagram of an embodiment of the hardware access manager provided in the present invention, and the hardware access server 2031 is responsible for accessing medical devices, and each medical device has a unique corresponding hardware access server 2031 in the device operation subsystem server. The hardware access server 2031 is responsible for managing these hardware accesses, and the hardware access server 2031 comprises the three major components, among them:
the asynchronous access agent manager 20311 is responsible for managing device asynchronous access agents, which are provided for device operation use by the interprocess client. After receiving the request of the interprocess client, the MCDC server gives the request to an asynchronous agent for processing, the asynchronous agent carries a request command number and command data, enters a designated hardware access server 2031 to wait for execution, and finds a method of a third operation interface of a corresponding server end through the command number when the asynchronous agent is executed, the hardware access server 2031 issues the operation request to the medical equipment through a client communication transaction manager 2033, processes the response, and sends back the operation result and possibly carried data to the interprocess client through the MCDC;
the synchronous access agent manager 20312 is responsible for managing the device synchronous access agents, and provides the device operation usage for the in-process clients. When the operation interface of the client device in the process is called, a synchronization agent is directly requested to perform subsequent processing, the synchronization agent carries a request command number and command data, enters a designated hardware access server 2031 to wait for execution, and finds a third operation interface of a corresponding server through the command number when the synchronization agent is executed, the hardware access server 2031 issues the operation request to the medical device through a client communication transaction manager 2033, processes the response, and returns the operation result and possibly carried data to the client;
the client communication transaction manager 20313 is responsible for managing device client access transactions, where the access transactions include a request message and a response message, and are divided into client access transactions and server access transactions. The access transaction that initiates the request message is called a client access transaction, which is responsible for issuing the request message and processing the response message; an access transaction that processes a request message is referred to as a server-side access transaction, which is responsible for processing the request message and issuing the response message. The device operating framework uses client access transactions that correlate request messages and response messages so that response messages can be matched to corresponding request messages. The device access messages include requests and responses designed according to the actual access protocol of the device, with different device access protocols having different device access messages.
In a preferred embodiment, in the operation management system of the medical Device, the corresponding Communication architecture is composed of a Device Service interface layer dsif (Device Service interface), an inter-process Communication layer MCDC (MC-Device Communication), a Device management server layer dms (Device Manager series), and a Device abstraction Communication layer dac (Device abstraction Communication).
It should be noted that the overall framework of the system adopts a CS architecture model:
the device service interface layer DSIF belongs to a Client layer (namely a Client), the device management Server layer DMS and the device abstraction communication layer DAC belong to a Server layer (namely a Server), and the interprocess communication layer MCDC (including the MCDC Server manager and the MCDC Client manager) is deployed on both the Client layer and the Server layer; the main function of the device service interface layer DSIF is to provide a device operation interface for an external subsystem, and is divided into two functional interfaces, namely an lnnerprocess interface and an InterProcess interface, which correspond to the first operation interface and the second operation interface respectively, the functional interface of the lnnerprocess (the first operation interface) is provided for other subsystems in a process, and the functional interface of the InterProcess (the second operation interface) is provided for other subsystems across the process. An in-process device component is referred to herein as a localcient and an inter-process device component is referred to herein as a RemoteClient.
The MCDC realizes communication between the inter-process equipment operation subsystem and other subsystems; the device management server layer DMS is a main control module and is responsible for managing device components, processing operation requests of other subsystems and transmitting operation commands (including the device operation requests) to the medical device; the DAC layer of the equipment abstract communication layer (comprising the client communication affair manager) is an abstract layer of the communication between the equipment operation subsystem and each medical equipment, different communication protocol packages are used for communication with each medical equipment, and different communication protocol packages can be loaded according to the peripheral requirement. The communication packages have common functions and mainly comprise a sending interface and a device access message sending function, wherein the sending interface is provided for sending the device access message to the medical device; providing a receiving interface, receiving the equipment access message of the medical equipment, and delivering the equipment access message to the corresponding equipment component for processing;
in combination with the above, the device operation subsystem client includes a device service interface layer DSIF and an inter-process communication layer MCDC, and the device operation subsystem server includes a device management server layer DMS, a device abstraction communication layer DAC and an inter-process communication layer MCDC.
An embodiment of the present invention provides an operation management method for a medical device, which is applied to a client in the operation management system, and referring to fig. 11, fig. 11 is a flowchart illustrating an embodiment of the operation management method for a medical device applied to a client according to the present invention, and includes steps S1101 to S1102, where:
in step S1101, the client sends an equipment operation request of the caller to the server, wherein the server issues the received equipment operation request to the corresponding medical equipment for operation, generates operation result data, and sends the operation result data to the client;
in step S1102, the client receives the operation result data generated by the server and feeds the operation result data back to the caller.
In the embodiment of the invention, the client is arranged to send the equipment operation request of the caller, and the server receives the equipment operation request, then issues the equipment operation request to the corresponding medical equipment for operation, receives the operation result data after the medical equipment is operated, and then sends the operation result data to the client.
As a preferred embodiment, referring to fig. 12, fig. 12 is a schematic flowchart of an embodiment of step S1101 provided by the present invention, and includes steps S1201 to S1203, where:
in step S1201, the client acquires a device operation request of the caller;
in step S1202, the client determines a client operation interface of a corresponding client device component according to the device operation request, where the client device component is expressed in the middle of the client for the medical device that the caller needs to call;
in step S1203, the client accesses the server according to the client operation interface, and transmits a device operation request to the server.
In the embodiment of the invention, when the client side obtains the equipment operation request of the caller, the corresponding client side operation interface is determined, and the server is accessed according to the client side operation interface.
As a preferred embodiment, referring to fig. 13, fig. 13 is a schematic flow chart of an embodiment of steps included before step S1201 provided by the present invention, and includes steps S1301 to S1302, where:
in step S1301, the client imports a first dynamic library that feeds back mapping relationships of multiple information of the client device component according to a pre-stored configuration file;
in step S1302, the client initializes the client device component according to the first dynamic library.
In the embodiment of the invention, the client side initializes according to the pre-stored configuration file to realize the initial configuration of the client side equipment component.
As a preferred embodiment, referring to fig. 14, fig. 14 is a schematic flowchart of an embodiment of step S1302 provided by the present invention, and includes steps S1401 to S1402, where:
in step S1401, according to the device operation request, a first name of a client device component to be called is determined;
in step S1402, a corresponding client operation interface is determined and invoked based on the mapping relationship in the first dynamic library according to the first name.
In the embodiment of the invention, the corresponding client operation interface is called according to the mapping relation in the first dynamic library.
As a preferred embodiment, referring to fig. 15, fig. 15 is a flowchart illustrating an embodiment of step S1203 provided by the present invention, where a client device component includes an in-process device component and an inter-process device component, and step S1203 includes steps S1501 to S1502, where:
in step S1501, if the client is an in-process client, interacting with the server by using an in-process device component manager according to a client operation interface of a corresponding in-process device component in a device synchronous access proxy manner;
in step S1502, if the client is an inter-process client, the client is interacted with the server through an inter-process communication mechanism according to the client operation interface of the corresponding inter-process device component by using the client inter-process communication manager.
In the embodiment of the invention, a synchronous proxy access mode is adopted for an in-process client, and an asynchronous proxy access mode is adopted for an inter-process client, so that the communication effectiveness is ensured.
The embodiment of the invention provides an operation management method of medical equipment, which is applied to a server in the operation management system and comprises the following steps:
the server sends the received equipment operation request to the corresponding medical equipment to run, generates operation result data and sends the operation result data to the client, wherein the client sends the equipment operation request of a caller to the server, and the client receives the operation result data generated by the server and feeds the operation result data back to the caller.
In the embodiment of the invention, based on the CS architecture, the device operation request of the caller is sent by setting the client, and after receiving the device operation request, the server issues the device operation request to the corresponding medical device for operation, receives the operation result data after the medical device is operated, and then sends the operation result data to the client.
As a preferred embodiment, referring to fig. 16, fig. 16 is a schematic flowchart of an embodiment of performing operation management on a server provided by the present invention, and specifically includes steps S1601 to S1603, where:
in step S1601, the server determines a third operation interface of a corresponding server device component according to the received device operation request, where the server device component is expressed in the middle of the server for the medical device that the caller needs to call;
in step S1602, the server accesses the corresponding medical device according to the third operation interface, and sends the device operation request to the corresponding medical device for operation, where the medical device operates according to the device operation request, generates operation result data, and sends the operation result data to the server;
in step S1603, the server transmits the received operation result data to the client.
In the embodiment of the invention, the server receives the equipment operation request from the client, selects the corresponding operation interface and sends the corresponding operation interface to the corresponding medical equipment for operation.
As a preferred embodiment, referring to fig. 17, fig. 17 is a schematic flow chart of an embodiment of a step included before step S1601 provided by the present invention, and before step S1601, the present invention further includes steps S1701 to S1702, where:
in step S1701, the server imports a second dynamic library of mapping relationships of a plurality of types of information of the feedback server device components according to a pre-stored configuration file;
in step S1702, the server initializes the server device component according to the second dynamic library.
In the embodiment of the invention, the server initializes the server equipment component by utilizing the second dynamic library to complete the initial configuration.
As a preferred embodiment, referring to fig. 18, fig. 18 is a schematic flowchart of an embodiment of step S1601 provided by the present invention, and in step S1601, the method includes steps S1801 to S1802, where:
in step S1801, the server determines, according to the device operation request, a second name of the server device component to be called;
in step S1802, the server determines and calls a corresponding third operation interface based on the mapping relationship in the second dynamic library according to the second name.
In the embodiment of the invention, the server uses the mapping relation in the second dynamic library and the name of the server equipment component to search and determine the corresponding third operation interface of the server side.
As a preferred embodiment, referring to fig. 19, fig. 19 is a schematic flowchart of an embodiment of step S1602 provided by the present invention, and includes steps S1901 to S1902, where:
in step S1901, when receiving an equipment operation request sent by a client in the process, a synchronous access proxy server in the server determines a corresponding third operation interface according to a command number in the equipment operation request, and the synchronous access proxy server issues the equipment operation request to the medical equipment through a client communication transaction manager according to the third operation interface;
in step S1902, when receiving the device operation request sent by the inter-process client, the asynchronous access proxy server in the server determines a corresponding third operation interface according to the command number in the device operation request, and the asynchronous access proxy server issues the device operation request to the medical device through the client communication transaction manager according to the third operation interface.
In the embodiment of the invention, the synchronous access proxy server or the asynchronous access proxy server is called to carry out effective communication according to the requests of different clients.
Embodiments of the present invention also provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements the operation management method applied to a medical device of a client as described above, or implements the operation management method applied to a medical device of a server as described above.
Generally, computer instructions for carrying out the methods of the present invention may be carried using any combination of one or more computer-readable storage media. Non-transitory computer readable storage media may include any computer readable medium except for the signal itself, which is temporarily propagating.
A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages, and in particular may employ Python languages suitable for neural network computing and TensorFlow, PyTorch-based platform frameworks. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
Embodiments of the present invention further provide a computing device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the operation management method applied to the medical device of the client or implements the operation management method applied to the medical device of the server, when executing the program.
According to the computer-readable storage medium and the computing device provided by the above embodiments of the present invention, the content specifically described for implementing the operation management method of the medical device described above according to the present invention can be referred to, and the beneficial effects similar to the operation management method of the medical device described above are achieved, and are not repeated herein.
The invention discloses an operation management system, a method and a storage medium of medical equipment, in the operation management system of the medical equipment, a client and a server which are communicated with each other are arranged, different medical equipment is abstractly represented by corresponding equipment components in the client and the server, the whole operation management system is used for operating and managing the equipment components of the client and the server, and meanwhile, the operation management result is issued by utilizing data communication so as to configure different medical equipment; on the basis of the operation management system of the medical equipment, the equipment operation request of a caller is sent through the client, and after the server receives the equipment operation request, the equipment operation request is issued to the corresponding medical equipment to operate, the operation result data after the medical equipment operates is received and then sent to the client, so that different configurations of the medical equipment are completed, and the adaptability and flexibility of developing different equipment components are enhanced.
The technical scheme of the invention is suitable for the change of hardware configuration of products with different models, enhances the adaptability and flexibility of developing different equipment components, has simple development and maintenance of the equipment components, good expansibility and low maintenance cost, can distribute the equipment components to a plurality of developers in case of emergency projects, develops different equipment components in parallel based on an equipment operation framework, and can improve the software development efficiency of the magnetic resonance system.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention.
Claims (10)
1. An operation management system of a medical device is characterized by comprising a client and a server which are in communication connection with each other, wherein the medical device is provided with corresponding device components for abstract representation at the client and the server respectively, and the device components are operated and managed through communication interaction between the client and the server so as to realize configuration operation of the medical device.
2. The system of claim 1, wherein the client is configured to send a device operation request of a caller to the server; the operation result data generated by the server is also received; and the server is used for issuing the received equipment operation request to the corresponding medical equipment for operation, generating the operation result data and sending the operation result data to the client.
3. The medical device operation management system according to claim 2, wherein the client includes an in-process client for managing a first operation interface of at least one in-process device component and an inter-process client for managing a second operation interface of at least one inter-process device component, wherein:
the in-process client comprises an in-process device component manager, wherein the in-process device component manager is used for calling the first operation interface and sending the device operation request to the server, and the in-process device component is an abstract representation corresponding to the medical device in the in-process client;
the inter-process client comprises an inter-process equipment component manager and a client inter-process communication manager, wherein the inter-process equipment component manager is used for calling the second operation interface; and the client inter-process communication manager is used for interacting with the server in an inter-process communication mechanism mode according to the called second operation interface and sending the equipment operation request, wherein the inter-process equipment component is an abstract representation corresponding to the medical equipment in the inter-process client.
4. The system for operation management of a medical device according to claim 1, wherein the server includes a server device component manager, a server inter-process communication manager, a hardware access manager, and a communication packet manager, wherein:
the server equipment component manager is used for managing a third operation interface of at least one server equipment component and calling the third operation interface to send the equipment operation request to the corresponding medical equipment;
the server inter-process communication manager comprises at least one inter-process communication server, and the at least one inter-process communication server is used for interacting with the client inter-process communication manager by adopting an inter-process communication mechanism;
the hardware access manager comprises a hardware access server of at least one medical device, and the hardware access server is used for interacting with the medical device which only corresponds to the hardware access server;
the communication packet manager is used for managing various equipment communication packets, wherein the equipment communication packets are used for transmitting equipment access messages between the hardware interface of the medical equipment and the third operation interface.
5. The medical device operations management system of claim 4, wherein the hardware access server comprises an asynchronous access agent manager, a synchronous access agent manager, and a client communication transaction manager, wherein:
the asynchronous access proxy manager is used for receiving the equipment operation request by using an asynchronous proxy when the communication manager between the client processes in the client sends the equipment operation request, and determining the third operation interface according to a command number in the equipment operation request;
the synchronous access agent manager is used for receiving the equipment operation request by utilizing synchronous agent processing when the in-process equipment component manager in the client sends the equipment operation request, and determining the third operation interface according to a command number in the equipment operation request;
and the client communication transaction manager is used for managing access transactions with the client.
6. An operation management method of a medical device, applied to a client in the operation management system according to any one of claims 1 to 5, the operation management method comprising the steps of:
the client sends an equipment operation request of a caller to a server, wherein the server issues the received equipment operation request to corresponding medical equipment for operation, generates operation result data and sends the operation result data to the client;
and the client receives the operation result data generated by the server and feeds the operation result data back to the caller.
7. The operation management method of a medical device according to claim 6, wherein in the step of determining, by the client, the client operation interface of the corresponding client device component according to the device operation request, the method includes:
the client determines a first name of a client device component needing to be called according to the device operation request, wherein the client device component is an abstract representation of the medical device needing to be called by the caller on the client;
the client determines and calls a client operation interface corresponding to the client equipment component based on the mapping relation in the first dynamic library according to the first name;
the client side imports the first dynamic library which feeds back mapping relations of various information of the client side equipment assembly according to a prestored configuration file; and the client initializes the client equipment component according to the first dynamic library.
8. An operation management method of a medical device, applied to a server in the operation management system according to any one of claims 1 to 5, comprising the steps of:
the server sends the received equipment operation request to the corresponding medical equipment for operation, generates operation result data and sends the operation result data to a client, wherein the client sends the equipment operation request of a caller to the server, and the client receives the operation result data generated by the server and feeds the operation result data back to the caller.
9. The method for managing the operation of the medical device according to claim 8, wherein in the step of the server issuing the received device operation request to the corresponding medical device for operation, generating operation result data and sending the operation result data to the client, the method comprises:
the server determines a second name of a server equipment component to be called according to the received equipment operation request, wherein the server equipment component is an abstract representation of the medical equipment to be called by the caller in the server;
the server determines and calls the corresponding third operation interface according to the second name and based on a mapping relation in a second dynamic library, wherein the server imports the second dynamic library which feeds back the mapping relation of various information of the server equipment component according to a prestored configuration file, and the server initializes the server equipment component according to the second dynamic library;
the server accesses the corresponding medical equipment according to the third operation interface, and sends the equipment operation request to the corresponding medical equipment for operation, wherein the medical equipment operates according to the equipment operation request, generates the operation result data and sends the operation result data to the server;
and the server sends the received operation result data to the client.
10. A computer-readable storage medium on which a computer program is stored, which, when executed by a processor, implements a method of operation management of a medical device according to any one of claims 6 to 7, or a method of operation management of a medical device according to any one of claims 8 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111357150.4A CN114036092A (en) | 2021-11-16 | 2021-11-16 | Medical equipment operation management system, method and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111357150.4A CN114036092A (en) | 2021-11-16 | 2021-11-16 | Medical equipment operation management system, method and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114036092A true CN114036092A (en) | 2022-02-11 |
Family
ID=80144607
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111357150.4A Pending CN114036092A (en) | 2021-11-16 | 2021-11-16 | Medical equipment operation management system, method and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114036092A (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0546414A (en) * | 1991-08-08 | 1993-02-26 | Nec Corp | Shared data processing system |
| JPH1196115A (en) * | 1997-09-22 | 1999-04-09 | Toshiba Corp | Device and method for conversation processing between client and server, and storage medium |
| JP2002244873A (en) * | 2001-02-20 | 2002-08-30 | Hitachi Ltd | Communication processing method and recording medium with communication processing program recorded thereon |
| US20020178126A1 (en) * | 2001-05-25 | 2002-11-28 | Beck Timothy L. | Remote medical device access |
| JP2003162419A (en) * | 2001-08-27 | 2003-06-06 | Ricoh Co Ltd | Apparatus having inter-process communication function |
| US20050216311A1 (en) * | 2003-10-29 | 2005-09-29 | Moritz Gmelin | Communications system and a method of processing medical data |
| US20080127206A1 (en) * | 2006-08-02 | 2008-05-29 | Microsoft Corporation Microsoft Patent Group | Conducting client-server inter-process communication |
| CN101268447A (en) * | 2005-05-26 | 2008-09-17 | 美国联合包裹服务公司 | Software process monitor |
| CN103379023A (en) * | 2012-04-25 | 2013-10-30 | 腾讯科技（深圳）有限公司 | Instant messaging method and instant messaging client-side |
| US20140044201A1 (en) * | 2012-08-07 | 2014-02-13 | Nellcor Puritan Bennett Llc | System, method, and software for communicating with medical devices |
| CN103886167A (en) * | 2012-11-15 | 2014-06-25 | 上海联影医疗科技有限公司 | Medical image processing method and system, client side and server |
| US20180278611A1 (en) * | 2017-03-21 | 2018-09-27 | Dell Products, Lp | System and method for securing an inter-process communication via a named pipe |
| CN212137721U (en) * | 2020-07-16 | 2020-12-11 | 卡瓦科尔牙科医疗器械（苏州）有限公司 | Interconnection management system suitable for oral medical equipment |
| CN112397190A (en) * | 2019-08-14 | 2021-02-23 | 深圳迈瑞生物医疗电子股份有限公司 | Medical equipment system in hospital and equipment management method thereof |
| CN113010333A (en) * | 2021-03-24 | 2021-06-22 | 北京中电兴发科技有限公司 | Multi-scene inter-process communication method suitable for Linux server cluster |
-
2021
- 2021-11-16 CN CN202111357150.4A patent/CN114036092A/en active Pending
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0546414A (en) * | 1991-08-08 | 1993-02-26 | Nec Corp | Shared data processing system |
| JPH1196115A (en) * | 1997-09-22 | 1999-04-09 | Toshiba Corp | Device and method for conversation processing between client and server, and storage medium |
| JP2002244873A (en) * | 2001-02-20 | 2002-08-30 | Hitachi Ltd | Communication processing method and recording medium with communication processing program recorded thereon |
| US20020178126A1 (en) * | 2001-05-25 | 2002-11-28 | Beck Timothy L. | Remote medical device access |
| JP2003162419A (en) * | 2001-08-27 | 2003-06-06 | Ricoh Co Ltd | Apparatus having inter-process communication function |
| US20050216311A1 (en) * | 2003-10-29 | 2005-09-29 | Moritz Gmelin | Communications system and a method of processing medical data |
| CN101268447A (en) * | 2005-05-26 | 2008-09-17 | 美国联合包裹服务公司 | Software process monitor |
| US20080127206A1 (en) * | 2006-08-02 | 2008-05-29 | Microsoft Corporation Microsoft Patent Group | Conducting client-server inter-process communication |
| CN103379023A (en) * | 2012-04-25 | 2013-10-30 | 腾讯科技（深圳）有限公司 | Instant messaging method and instant messaging client-side |
| US20140044201A1 (en) * | 2012-08-07 | 2014-02-13 | Nellcor Puritan Bennett Llc | System, method, and software for communicating with medical devices |
| CN103886167A (en) * | 2012-11-15 | 2014-06-25 | 上海联影医疗科技有限公司 | Medical image processing method and system, client side and server |
| US20180278611A1 (en) * | 2017-03-21 | 2018-09-27 | Dell Products, Lp | System and method for securing an inter-process communication via a named pipe |
| CN112397190A (en) * | 2019-08-14 | 2021-02-23 | 深圳迈瑞生物医疗电子股份有限公司 | Medical equipment system in hospital and equipment management method thereof |
| CN212137721U (en) * | 2020-07-16 | 2020-12-11 | 卡瓦科尔牙科医疗器械（苏州）有限公司 | Interconnection management system suitable for oral medical equipment |
| CN113010333A (en) * | 2021-03-24 | 2021-06-22 | 北京中电兴发科技有限公司 | Multi-scene inter-process communication method suitable for Linux server cluster |
Non-Patent Citations (1)
| Title |
|---|
| 吴佩贤;: "Linux环境下基于UDP的socket编程浅析", 网络安全技术与应用, no. 01, 1 January 2006 (2006-01-01) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8584081B2 (en) | Server side application integration framework | |
| US11409719B2 (en) | Co-locating microservice persistence containers within tenant-specific database | |
| US9674234B2 (en) | Managing an application programming interface in a collaboration space | |
| US7702729B2 (en) | Event heap: a coordination infrastructure for dynamic heterogeneous application interactions in ubiquitous computing environments | |
| US10491700B2 (en) | Application managed service instances | |
| US20020105548A1 (en) | Methods and apparatus for creating a user interface using property paths | |
| CN110083455B (en) | Graph calculation processing method, graph calculation processing device, graph calculation processing medium and electronic equipment | |
| CN107493266B (en) | Communication system, method and device of embedded self-service terminal | |
| CN110658794B (en) | Manufacturing execution system | |
| EP3436935A1 (en) | Pre-formed instructions for a mobile cloud service | |
| CN108881111A (en) | A kind of method and device for realizing multi-tenant system | |
| CN112698921A (en) | Logic code operation method and device, computer equipment and storage medium | |
| CN110008131B (en) | Method and device for managing area AB experiment based on algorithm | |
| CN113162848A (en) | Method, device, gateway and medium for realizing block chain gateway | |
| CN113703997A (en) | Bidirectional asynchronous communication middleware system integrating multiple message agents and implementation method | |
| CN109739624A (en) | Distributed transaction processing method, device, electronic equipment and computer-readable medium | |
| US11615159B2 (en) | Data processing method for mini app, apparatus, device and medium | |
| KR20020021237A (en) | Realtime Middleware apparatus providing an integrated software development frameworks of embedded system and its service method | |
| US10725744B2 (en) | Method for adapting to blockchain and device, terminal and medium performing the same | |
| Matsumoto et al. | Next-Generation MADOCA for the SPring-8 Control Framework | |
| US20170286261A1 (en) | System and method for providing runtime tracing for a web-based client accessing a transactional middleware platform using an extension interface | |
| CN114036092A (en) | Medical equipment operation management system, method and storage medium | |
| CN115834600A (en) | Multi-cloud nanotube data synchronization method and device, electronic equipment and storage medium | |
| US8353013B2 (en) | Authorized application services via an XML message protocol | |
| CN113472638A (en) | Edge gateway control method, system, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |