CN113905072A - Hospital intranet communication method and system - Google Patents
Hospital intranet communication method and system Download PDFInfo
- Publication number
- CN113905072A CN113905072A CN202111177756.XA CN202111177756A CN113905072A CN 113905072 A CN113905072 A CN 113905072A CN 202111177756 A CN202111177756 A CN 202111177756A CN 113905072 A CN113905072 A CN 113905072A
- Authority
- CN
- China
- Prior art keywords
- data
- client
- server
- request data
- connection
- 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
- 238000004891 communication Methods 0.000 title claims abstract description 48
- 238000000034 method Methods 0.000 title claims abstract description 35
- 230000003993 interaction Effects 0.000 claims abstract description 7
- 238000012545 processing Methods 0.000 claims description 34
- 230000001360 synchronised effect Effects 0.000 claims description 13
- 230000002452 interceptive effect Effects 0.000 claims description 12
- 230000005540 biological transmission Effects 0.000 claims description 11
- 238000012544 monitoring process Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 6
- 230000007246 mechanism Effects 0.000 claims description 3
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 230000000712 assembly Effects 0.000 abstract 1
- 238000000429 assembly Methods 0.000 abstract 1
- 230000003287 optical effect Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 7
- 238000002955 isolation Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000000926 separation method Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000007935 neutral effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
Abstract
The invention discloses a hospital intranet communication method and a system, wherein the method comprises the following steps: acquiring request data of an external application, and establishing connection between a server and a client according to the request data; judging whether the connection state of the server and the client is effective or not; if the request data is invalid, waiting for the next request data; if the connection is valid, the connection between the server and the client is maintained; the server side sends request data to the client side; the client acquires internal data of the internal application according to the request data and sends the internal data to the server; the system comprises a client deployed in an intranet environment, a server deployed in a cloud or an extranet environment and control assemblies respectively connected with the client and the server, wherein the server is connected with the client through a port to achieve data interaction, the server is externally connected with an external application, and the client is externally connected with an internal application.
Description
Technical Field
The invention relates to the field of hospital intranet communication, in particular to a hospital intranet communication method and system.
Background
The current solutions for intranet and extranet security and data sharing include: an optical disc-based cross-network data exchange transmission system, comprising: a disk storage device disposed in the neutral position; the first optical disk drive is arranged in a first physical isolation network and can read and write data, and the first manipulator is controlled by the first physical isolation network; the second optical disk drive is arranged in the second physical isolation network and can read and write data, and the second manipulator is controlled by the second physical isolation network; the mechanical arm of the corresponding physical isolation network transmits the optical disc between the optical disc driver and the optical disc storage device of the corresponding physical isolation network, the technical problem that potential signal permeation is caused by transient connection of circuit structures between networks possibly occurring during data transmission across the separation network is solved, the technical problem that data transmission efficiency is low during data transmission across the physical separation network is solved, but the technical scheme needs to erect additional hardware equipment on site and intervene in an inherently stable network architecture, certain hidden danger risks exist, and the optical disc cannot be realized under the condition that physical network conditions are not met.
Disclosure of Invention
The technical problem to be solved by the invention is that the existing internal and external networks need to establish extra hardware equipment on site, intervene in an inherently stable network architecture, have certain hidden danger risks and cannot be realized under the condition that physical network conditions are not satisfied, the invention provides a hospital intranet communication method, and also provides a hospital intranet communication system, which can be conveniently deployed and implemented from the perspective of pure software without depending on other extra hardware equipment, and the physical network environment is not limited for the internal network communication, compared with a cross-network data exchange transmission system based on an optical disk, the intranet communication system is convenient and fast to deploy and implement from the perspective of pure software without intervening in the original network architecture, the risk of influencing the whole network ecological environment is reduced to the minimum when the deployment is carried out, the intranet communication system is safer without depending on extra site, hardware equipment and the like, and for later operation and maintenance, hardware loss, manpower and other costs are reduced to the lowest, and after an emergency event happens, the normal working state can be quickly and automatically recovered, manual intervention is not needed, and the defects caused by the prior art are overcome.
In order to solve the technical problems, the invention provides the following technical scheme:
in a first aspect, a method for hospital intranet communication includes the following steps:
step A1: acquiring request data of an external application, and establishing connection between a server and a client according to the request data;
step A2: judging whether the connection state of the server and the client is effective or not;
if the request data is invalid, waiting for the next request data;
if the connection is valid, the connection between the server and the client is maintained;
step A3: the server side sends request data to the client side;
step A4: and the client acquires the internal data of the internal application according to the request data and sends the internal data to the server.
In the hospital intranet communication method, the request data includes connection request data and data request data;
in step a1, the server establishes a connection with the client according to the connection request data;
in step a3, the server sends the data request data to the client, and if the client does not receive the request data sent by the server, the client reconnects with the server, and if the reconnection is unsuccessful, the client disconnects;
in step a4, the client obtains internal data of an internal application according to the data request data and sends the internal data to the server, and if the client does not send the internal data to the server, the server destroys the request data.
The hospital intranet communication method further comprises the step of synchronizing data from the client to the server, and the specific steps are as follows:
step B1: the client acquires synchronous request data of the internal application, and the client establishes connection with the server according to the synchronous request data;
step B2: judging whether the connection state of the server and the client is effective or not;
if the data is invalid, waiting for the next synchronous request data;
if the connection is valid, the connection between the server and the client is maintained;
step B3: the client acquires internal data of the internal application and sends the internal data to the server.
In a second aspect, a hospital intranet communication system includes a client deployed in an intranet environment, a server deployed in a cloud or extranet environment, and control components respectively connected to the client and the server, where the server establishes a connection with the client through a port to implement data interaction, and connects the client and the server through only one port, so that a long-term effective connection can be maintained without exposing an internal IP address, the server is externally connected to an external application, and the client is externally connected to an internal application;
the server is used for acquiring request data of the external application and establishing connection with the client according to the request data;
the client is used for acquiring the internal data of the internal application and transmitting the internal data to the server according to the request data;
the control component comprises an initialization module, a connection monitoring module, a data packet processing module and a heartbeat packet processing module;
the initialization module is used for loading necessary parameter data when the client and the server are started, and the client and the server can normally operate after initialization is completed;
the connection monitoring module is used for acquiring the connection state between the client and the server and/or the connection data transmitted to the heartbeat packet processing module by the data interaction information;
the heartbeat packet processing module is used for acquiring the connection data, judging whether the connection between the client and the server is normal or not, and generating feedback data transmitted to the client and the server.
In the hospital intranet communication system, the request data includes connection request data and data request data;
the server side establishes connection with the client side according to the connection request data;
the server side sends the data request data to the client side, if the client side does not receive the request data sent by the server side, reconnection is carried out on the client side, and if the reconnection is unsuccessful, disconnection is carried out;
and the client acquires internal data of the internal application according to the data request data and transmits the internal data to the server, and if the client does not send the internal data to the server, the server destroys the request data.
In the hospital intranet communication system, the client is further configured to obtain synchronization request data of an internal application and transmit internal data updated by the internal application to the server according to the synchronization request data.
In the hospital intranet communication system, the parameter data includes a data transmission protocol, a data packet size, a heartbeat packet mechanism, and a log recording mode.
In the hospital intranet communication system, the control component further includes a data packet processing module;
the connection monitoring module is also used for generating interactive data transmitted to the data packet processing module;
the data packet processing module is used for acquiring the interactive data and processing the interactive data to generate a data packet;
in the hospital intranet communication system, the manner in which the data packet processing module processes the interactive data to generate the data packet includes any one or more of the following methods: packaging, analyzing, combing and converting data format.
In a third aspect, a computer-readable storage medium is characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, performs the steps of the method of any one of the first aspect.
According to the technical scheme provided by the hospital intranet communication method and system provided by the invention, the technical effects are as follows:
this technical scheme provides a hospital intranet communication system need not rely on other extra hardware equipment, the physics network environment has just not had the limitation to the intranet, compare the cross-network data exchange transmission system based on the CD, the intranet leads to the angle of system from pure software, it is convenient to deploy and implement, do not intervene original network architecture, it falls to minimumly to whole network ecological environment's influence risk to deploy, it is safer, the intranet leads to the system and need not extra place, dependence such as hardware equipment, to later stage fortune dimension, the hardware loss, cost such as manpower falls to minimumly, after the emergent incident of proruption, can quick automatic recovery normal operating condition, need not artificial intervention.
Drawings
FIG. 1 is a flow chart of a hospital intranet communication method of the present invention;
FIG. 2 is a schematic structural diagram of a hospital intranet communication system according to the present invention;
fig. 3 is a schematic structural diagram of a specific implementation of the hospital intranet communication system of the present invention.
Wherein the reference numbers are as follows:
the system comprises a client 101, a server 102, an external application 103, an internal application 104, an initialization module 105, a connection monitoring module 106, a data packet processing module 107 and a heartbeat packet processing module 108.
Detailed Description
In order to make the technical means, the inventive features, the objectives and the effects of the invention easily understood and appreciated, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the specific drawings, and it is obvious that the described embodiments are a part of the embodiments of the present invention, but not all of the embodiments.
All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
It should be understood that the structures, ratios, sizes, and the like shown in the drawings and described in the specification are only used for matching with the disclosure of the specification, so as to be understood and read by those skilled in the art, and are not used to limit the conditions under which the present invention can be implemented, so that the present invention has no technical significance, and any structural modification, ratio relationship change, or size adjustment should still fall within the scope of the present invention without affecting the efficacy and the achievable purpose of the present invention.
In addition, the terms "upper", "lower", "left", "right", "middle" and "one" used in the present specification are for clarity of description, and are not intended to limit the scope of the present invention, and the relative relationship between the terms and the terms is not to be construed as a scope of the present invention.
The first embodiment of the invention provides a hospital intranet communication method, aiming at providing a method that no other extra hardware equipment is needed to be relied on, the physical network environment is not limited for intranet communication, compared with a cross-network data exchange and transmission system based on an optical disk, the intranet communication system is convenient to deploy and implement from the perspective of pure software, the deployment and implementation are not involved in the original network architecture, the risk of influencing the whole network ecological environment is reduced to the minimum when the deployment is carried out, the deployment is safer, the intranet communication system is not needed to rely on extra fields, hardware equipment and the like, the cost of later operation and maintenance, hardware loss, manpower and the like is reduced to the minimum, and after an emergency event occurs, the normal working state can be rapidly and automatically recovered without manual intervention.
As shown in fig. 1, a first aspect, a first embodiment, a method for communicating within a hospital intranet, includes the following steps:
step A1: acquiring request data of an external application 103, and establishing connection between a server 102 and a client 101 according to the request data;
step A2: judging whether the connection state of the server 102 and the client 101 is valid;
if the request data is invalid, waiting for the next request data;
if the connection is valid, the connection between the server 102 and the client 101 is maintained;
step A3: the server 102 sends request data to the client 101;
step A4: the client 101 obtains the internal data of the internal application 104 according to the request data and sends the internal data to the server 102.
In the hospital intranet communication method, the request data includes connection request data and data request data;
in step a1, the server 102 creates a connection with the client 101 according to the connection request data;
in the step a3, the server 102 sends data request data to the client 101, if the client 101 does not receive the request data sent by the server 102, it is determined that the server 102 is abnormal, and reconnects with the server 102, and if the reconnection is unsuccessful, the connection is disconnected;
in step a4, the client 101 obtains the internal data of the internal application 104 according to the data request data and sends the internal data to the server 102, and if the client 101 does not send the internal data to the server 102, it is determined that the connection of the client 101 is abnormal, and the server 102 destroys the request data.
The hospital intranet communication method further comprises the step of synchronizing data from the client 101 to the server 102, and the specific steps are as follows:
step B1: the client 101 acquires synchronous request data of the internal application 104, and the client 101 establishes connection with the server 102 according to the synchronous request data;
step B2: judging whether the connection state of the server 102 and the client 101 is valid;
if the data is invalid, waiting for the next synchronous request data;
if the connection is valid, the connection between the server 102 and the client 101 is maintained;
step B3: the client 101 acquires internal data of the internal application 104 and sends the internal data to the server 102.
As shown in fig. 2-3, a second aspect, a second embodiment, a hospital intranet communication system, includes a client 101 deployed in an intranet environment, a server 102 deployed in a cloud or extranet environment, and control components respectively connected to the client 101 and the server 102, where the server 102 establishes a connection with the client 101 through a port to implement data interaction, and performs connection between the client 101 and the server 102 through only one port, so as to maintain a long-term effective connection without exposing an internal IP address, where the server 102 is externally connected to an external application 103, and the client 101 is externally connected to an internal application 104;
the server 102 is configured to obtain request data of the external application 103 and create a connection with the client 101 according to the request data;
the client 101 is configured to obtain internal data of the internal application 104 and transmit the internal data to the server 102 according to the request data;
the control component comprises an initialization module 105, a connection monitoring module 106, a data packet processing module 107 and a heartbeat packet processing module 108;
the initialization module 105 is configured to load necessary parameter data when the client 101 and the server 102 are started, and the client 101 and the server 102 can normally operate after initialization is completed;
the connection monitoring module 106 is configured to acquire a connection state between the client 101 and the server 102 and/or connection data transmitted to the heartbeat packet processing module 108 by the data interaction information;
the heartbeat packet processing module 108 is configured to obtain connection data, determine whether the connection between the client 101 and the server 102 is normal, and generate feedback data transmitted to the client 101 and the server 102.
In the hospital intranet communication system, the request data includes connection request data and data request data;
the server 102 establishes connection with the client 101 according to the connection request data;
the server 102 sends data request data to the client 101, if the client 101 does not receive the request data sent by the server 102, the client is reconnected with the server 102, and if the reconnection is unsuccessful, the connection is disconnected
The client 101 obtains the internal data of the internal application 104 according to the data request data and transmits the internal data to the server 102, and if the client 101 does not send the internal data to the server 102, the server 102 destroys the request data.
In the above hospital intranet communication system, the client 101 is further configured to obtain synchronization request data of the internal application 104 and transmit the internal data updated by the internal application 104 to the server 102 according to the synchronization request data.
In the hospital intranet communication system, the parameter data includes a data transmission protocol, a data packet size, a heartbeat packet mechanism, and a log recording mode.
In the hospital intranet communication system, the control component further includes a data packet processing module 107;
the connection monitoring module 106 is further configured to generate interactive data transmitted to the data packet processing module 107;
the data packet processing module 107 is configured to obtain the interactive data and process the interactive data to generate a data packet;
in the hospital intranet communication system, the way for processing the interactive data by the data packet processing module 107 to generate the data packet includes any one or more of the following methods: packaging, analyzing, combing and converting data format.
In a third aspect, a computer-readable storage medium is characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method of any one of the first aspect.
For example, the memory may include random access memory, flash memory, read only memory, programmable read only memory, non-volatile memory or registers, or the like;
the processor may be a Central Processing Unit (CPU) or the like, or a Graphics Processing Unit (GPU) memory may store executable instructions;
the processor may execute execution instructions stored in the memory to implement the various processes described herein.
It will be appreciated that the memory in this embodiment can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory;
the non-volatile memory may be a ROM (Read-only memory), a PROM (programmable Read-only memory), an EPROM (erasable programmable Read-only memory), an EEPROM (electrically erasable programmable Read-only memory), or a flash memory.
The volatile memory may be a RAM (random access memory) which functions as an external cache;
by way of illustration and not limitation, many forms of RAM are available, such as SRAM (staticaram, static random access memory), DRAM (dynamic RAM, dynamic random access memory), SDRAM (synchronous DRAM ), DDRSDRAM (double data rate SDRAM, double data rate synchronous DRAM), ESDRAM (Enhanced SDRAM, Enhanced synchronous DRAM), SLDRAM (synchlink DRAM, synchronous link DRAM), and DRRAM (directrrambus RAM, direct memory random access memory). The memory 205 described herein is intended to comprise, without being limited to, these and any other suitable types of memory 205.
In some embodiments, the memory stores elements, upgrade packages, executable units, or data structures, or a subset thereof, or an extended set thereof: operating systems and applications;
the operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks;
the application programs comprise various application programs and are used for realizing various application services. The program for implementing the method of the embodiment of the present invention may be included in the application program.
Those of skill in the art would understand that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of software and electronic hardware;
whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution;
skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments of the present application, the disclosed system, apparatus and method may be implemented in other ways;
for example, the division of a unit or a module is only one logic function division, and there may be another division manner in actual implementation;
for example, a plurality of units or modules or components may be combined or may be integrated into another system;
in addition, functional units or modules in the embodiments of the present application may be integrated into one processing unit or module, or may exist separately and physically.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the processes do not mean the execution sequence, and the execution sequence of the processes should be determined by the functions and the inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a machine-readable storage medium;
therefore, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a machine-readable storage medium and may include several instructions to cause an electronic device to execute all or part of the processes of the technical solution described in the embodiments of the present application;
the storage medium may include various media that can store program codes, such as ROM, RAM, a removable disk, a hard disk, a magnetic disk, or an optical disk.
In conclusion, the hospital intranet communication method and system do not need to rely on other extra hardware equipment, the physical network environment is not limited to intranet communication, compared with a cross-network data exchange and transmission system based on an optical disk, the intranet communication system is convenient to deploy and implement from the perspective of pure software, does not intervene in an original network architecture, is safer, has the lowest influence risk on the whole network ecological environment after deployment, is free from dependence on extra fields, hardware equipment and the like, is lowest in cost on later-stage operation, hardware loss, manpower and the like, and can quickly and automatically recover a normal working state after an emergency event, and does not need manual intervention.
Specific embodiments of the invention have been described above. It is to be understood that the invention is not limited to the particular embodiments described above, in that devices and structures not described in detail are understood to be implemented in a manner common in the art; various changes or modifications may be made by one skilled in the art within the scope of the claims without departing from the spirit of the invention, and without affecting the spirit of the invention.
Claims (10)
1. A hospital intranet communication method is characterized by comprising the following steps:
step A1: acquiring request data of an external application, and establishing connection between a server and a client according to the request data;
step A2: judging whether the connection state of the server and the client is effective or not;
if the request data is invalid, waiting for the next request data;
if the connection is valid, the connection between the server and the client is maintained;
step A3: the server side sends request data to the client side;
step A4: and the client acquires the internal data of the internal application according to the request data and sends the internal data to the server.
2. The hospital intranet communication method according to claim 1, wherein the request data includes connection request data and data request data;
in step a1, the server establishes a connection with the client according to the connection request data; in step a3, the server sends the data request data to the client, and if the client does not receive the request data sent by the server, the client reconnects with the server, and if the reconnection is unsuccessful, the client disconnects;
in step a4, the client obtains internal data of an internal application according to the data request data and sends the internal data to the server, and if the client does not send the internal data to the server, the server destroys the request data.
3. The hospital intranet communication method according to claim 1 or 2, further comprising a client synchronizing data to a server, and the specific steps are as follows:
step B1: the client acquires synchronous request data of the internal application, and the client establishes connection with the server according to the synchronous request data;
step B2: judging whether the connection state of the server and the client is effective or not;
if the data is invalid, waiting for the next synchronous request data;
if the connection is valid, the connection between the server and the client is maintained;
step B3: the client acquires internal data of the internal application and sends the internal data to the server.
4. A hospital intranet communication system is characterized by comprising a client deployed in an intranet environment, a server deployed in a cloud or extranet environment and control components respectively connected with the client and the server, wherein the server is connected with the client through a port to realize data interaction, the server is externally connected with an external application, and the client is externally connected with an internal application;
the server is used for acquiring request data of the external application and establishing connection with the client according to the request data;
the client is used for acquiring the internal data of the internal application and transmitting the internal data to the server according to the request data;
the control component comprises an initialization module, a connection monitoring module, a data packet processing module and a heartbeat packet processing module;
the initialization module is used for loading necessary parameter data when the client and the server are started;
the connection monitoring module is used for acquiring the connection state between the client and the server and/or the connection data transmitted to the heartbeat packet processing module by the data interaction information;
the heartbeat packet processing module is used for acquiring the connection data, judging whether the connection between the client and the server is normal or not, and generating feedback data transmitted to the client and the server.
5. The hospital intranet communication system according to claim 4, wherein the request data comprises connection request data and data request data;
the server side establishes connection with the client side according to the connection request data;
the server side sends the data request data to the client side, if the client side does not receive the request data sent by the server side, reconnection is carried out on the client side, and if the reconnection is unsuccessful, disconnection is carried out;
and the client acquires internal data of the internal application according to the data request data and transmits the internal data to the server, and if the client does not send the internal data to the server, the server destroys the request data.
6. The hospital intranet communication system according to claim 4 or 5, wherein the client is further configured to obtain synchronization request data of an internal application and transmit internal data updated by the internal application to the server according to the synchronization request data.
7. The hospital intranet communication system according to claim 6, wherein the parameter data includes a data transmission protocol, a data packet size, a heartbeat packet mechanism, and a log record mode.
8. The hospital intranet communication system of claim 4, 5 or 7, wherein the control module further comprises a data packet processing module;
the connection monitoring module is also used for generating interactive data transmitted to the data packet processing module;
and the data packet processing module is used for acquiring the interactive data and processing the interactive data to generate a data packet.
9. The hospital intranet communication system according to claim 8, wherein the way of the data packet processing module processing the interactive data to generate the data packet comprises any one or more of the following methods: packaging, analyzing, combing and converting data format.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method according to any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111177756.XA CN113905072A (en) | 2021-10-09 | 2021-10-09 | Hospital intranet communication method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111177756.XA CN113905072A (en) | 2021-10-09 | 2021-10-09 | Hospital intranet communication method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113905072A true CN113905072A (en) | 2022-01-07 |
Family
ID=79190700
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111177756.XA Pending CN113905072A (en) | 2021-10-09 | 2021-10-09 | Hospital intranet communication method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113905072A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6253234B1 (en) * | 1997-10-17 | 2001-06-26 | International Business Machines Corporation | Shared web page caching at browsers for an intranet |
| US20050125529A1 (en) * | 2003-11-24 | 2005-06-09 | Brockway Tad D. | Seamless discovery of workstation-installed remote applications from an extranet |
| CN104363235A (en) * | 2014-11-20 | 2015-02-18 | 成都博高科技有限责任公司 | Communication method, device and system and communication channel establishing method and device |
| CN106302413A (en) * | 2016-08-04 | 2017-01-04 | 中车青岛四方机车车辆股份有限公司 | Corporate intranet access method, ios terminal, transfer processing method, transfer server |
| CN110166432A (en) * | 2019-04-17 | 2019-08-23 | 平安科技（深圳）有限公司 | The access method of internal net destination service provides the method for Intranet destination service |
-
2021
- 2021-10-09 CN CN202111177756.XA patent/CN113905072A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6253234B1 (en) * | 1997-10-17 | 2001-06-26 | International Business Machines Corporation | Shared web page caching at browsers for an intranet |
| US20050125529A1 (en) * | 2003-11-24 | 2005-06-09 | Brockway Tad D. | Seamless discovery of workstation-installed remote applications from an extranet |
| CN104363235A (en) * | 2014-11-20 | 2015-02-18 | 成都博高科技有限责任公司 | Communication method, device and system and communication channel establishing method and device |
| CN106302413A (en) * | 2016-08-04 | 2017-01-04 | 中车青岛四方机车车辆股份有限公司 | Corporate intranet access method, ios terminal, transfer processing method, transfer server |
| CN110166432A (en) * | 2019-04-17 | 2019-08-23 | 平安科技（深圳）有限公司 | The access method of internal net destination service provides the method for Intranet destination service |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101478446B (en) | Network appliance version loading method, apparatus and system | |
| US11221612B2 (en) | System and method of communicating data over high availability industrial control systems | |
| US9231779B2 (en) | Redundant automation system | |
| CN110967969A (en) | High availability industrial automation system and method for transmitting information through the same | |
| CN115277727B (en) | Data disaster recovery method, system, device and storage medium | |
| CN112118137B (en) | Firmware upgrading method, device, computer equipment and readable storage medium | |
| US8582422B2 (en) | Access point configuration propagation | |
| US20170026236A1 (en) | A method and a system for the deterministic autoconfiguration of a device | |
| CN113905072A (en) | Hospital intranet communication method and system | |
| EP3703342A1 (en) | Dynamic load balancing in network centric process control systems | |
| EP3466016B1 (en) | Interdevice communications | |
| CN110309649B (en) | Support device, nonvolatile computer-readable recording medium, and setting method | |
| CN116962184A (en) | Method, system, terminal and medium for automatically deploying RoCE cluster | |
| KR20200113995A (en) | Triple or Multiple Architecture and Method for High Availability Guarantee on Edged AI Service | |
| CN114840495A (en) | Database cluster split-brain prevention method, storage medium and device | |
| KR20190041732A (en) | Backup device management system and method | |
| JP2007334668A (en) | Memory dumping method, cluster system, node constituting the system, and program | |
| CN109510725B (en) | Communication equipment fault detection system and method | |
| CN112732495A (en) | Information interaction method and device and storage medium | |
| US20200052968A1 (en) | Switch configuration | |
| JP2001251346A (en) | Data transmission system | |
| JP2008197907A (en) | Monitoring network system and data backup method | |
| KR100899470B1 (en) | A distributed controller system having a structure of double | |
| CN113285905A (en) | Cross-protocol control equipment and cross-protocol equipment restoring method thereof | |
| KR101740799B1 (en) | Method of failover for network service in software defined networking environment |
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 |