CN111211971B - Cluster type instant message system supporting internet inquiry service and implementation method thereof - Google Patents
Cluster type instant message system supporting internet inquiry service and implementation method thereof Download PDFInfo
- Publication number
- CN111211971B CN111211971B CN202010004667.4A CN202010004667A CN111211971B CN 111211971 B CN111211971 B CN 111211971B CN 202010004667 A CN202010004667 A CN 202010004667A CN 111211971 B CN111211971 B CN 111211971B
- Authority
- CN
- China
- Prior art keywords
- message
- client
- service
- registration
- socketio
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
- H04L51/046—Interoperability with other network applications or services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0281—Proxies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- 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/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Abstract
The invention belongs to the technical field of instant messaging, and relates to a cluster type instant message system supporting internet inquiry service and an implementation method thereof. Compared with the standard Jabber/XMPP architecture and protocol, the method has great advantages that firstly, the client is not limited by naming any more, and can be automatically and dynamically registered to any message service of the cluster, thereby greatly ensuring the high reliability of the instant message use of the client; secondly, compared with manual domain name configuration, the network connection number-based load balancing algorithm maximally utilizes the resources of each node in the cluster, has better dynamic flexibility, realizes larger-scale instant message throughput pressure, and finally adopts the mode of MQ message center broadcasting, thereby not only reducing the routing pressure of each message node, but also preventing the concurrent pressure of sudden and sudden rise of a certain message node due to the mode of MQ queue, and completely preventing the message node from crashing due to certain delay of queue processing when a sudden peak condition occurs.
Description
Technical Field
The invention belongs to the technical field of instant messaging, and particularly relates to a cluster type instant message system supporting internet inquiry service and an implementation method thereof.
Background
The instant messaging system is the basic requirement of internet medical service, doctors and patients, doctors and doctors need to pass through a message notification platform facing to internet medical service characteristics and instant messaging, so that the transmission of general information data such as characters, images and files is realized, and the integration and cooperation of third-party medical service systems such as EHR (health record), video exchange and online prescriptions can be realized. For example: the sender provides a patient health record number to the message service node, the message service node calls the EHR system, basic information of a patient in the health record database is extracted and packaged into a network-transferable data packet to the receiver, the receiver can conveniently and quickly look up the basic information of the patient in the data packet, the data packet is finally sent to the receiving end, the receiving end can achieve access penetrating query capability of the EHR system in a hospital according to data sources and certificate authorization in the data packet, and detailed health data retrieval capability of the patient is provided for a client of the receiver. The EHR system has a very tight business collaboration with the instant messaging system, as does video communication, online prescriptions, etc.
In order to meet large-scale and high-concurrency internet message transmission, most instant message products form a distributed network architecture on the basis of a standard internet TCP/IP network protocol, and a sender message is routed to a receiver message service node on the message service node through an application layer Socket communication protocol and finally reaches a target receiving end. For example: the Jabber/XMPP protocol and the framework are standardized by IETFXMPP protocol (RFC3290), namely a more typical standard instant message protocol conforming to the characteristics of a distributed framework, a user name is represented by a Jabber identifier (home @ example. com similar mail format), the former half part of the @ part of the user name is represented by a user name, the latter half part of the @ part of the user name is represented by a domain name of an XMPP protocol server, when a sender @ A.com user sends a message to a receiver @ B.com user, an A.com service node firstly receives an XML stream message sent by a sender, then the XML stream message is routed to a B.com service node through a gateway, and finally the B.com sends the received XML stream message to the receiver user to realize complete message routing transmission. In the whole process, the A.com and B.com service nodes respectively load huge user groups, so that a real distributed network architecture is realized, on one hand, the requirements of large scale and high concurrency are met based on a domain name grouping mode, and on the other hand, interconnection and intercommunication among different service nodes through a standard protocol are realized.
The message service oriented to the internet inquiry service not only needs to realize general information material transmission, but also needs to be tightly combined with a business system, such as: the system comprises an EHR (electronic health record system), a video chat system, a HIS (home information system) system and the like, so that the close combination degree of a message service node and a service system is far greater than that of a common instant message server, if the coupling degree of the message service and the service is too close, if the service system has unreliable factors, the communication fault of the message service node can be caused, and the reliability of the system is extremely high by the Internet medical inquiry service, so that the high reliability of the message service node is very critical to protect.
The instant message system based on the Jabber/XMPP protocol and the framework realizes the transmission of large-scale and high-concurrency instant messages among internet message service nodes in a domain name grouping mode through the convention of Jabber identifiers. However, although the engagement of Jabber identifier skillfully solves the expansion of the message service node, a new problem is brought about, namely that the client node must register on the message service node corresponding to the domain name according to the engaged Jabber identifier name. Once the communication of the message service node corresponding to the domain name is broken, there is no way to dynamically switch all the clients under the service node to other service nodes, unless the user name and the domain of the client are changed, which brings a very high switching cost in view of the universality of the internet users.
Secondly, the message transfer between the service nodes is in a routing mode, that is, the a.com service node is routed to the b.com service node in a TCP/IP connection establishment mode, so that (a) a client to a.com, (B) a.com to b.com, and (B) a TCP communication three-stage message communication chain from b.com to B client are formed, and the same principle can be obtained that the C client, the D client and the E client … … all perform message transfer with the service node in the routing mode and other service nodes. When A, C, D, E … … and other service nodes in the network transmit messages to the B service node at the same time, the B service node becomes a huge pressure point, and once the situation occurs, the B service node may slow or even break down due to the pressure, which may cause abnormal communication in the entire network. And the XMPP protocol transmits an XML stream data format, occupies large network bandwidth, is slow in DOM assembling and unpacking processing and also increases the pressure of service nodes.
Disclosure of Invention
The invention aims to provide a cluster-type instant message system supporting internet inquiry service and an implementation method thereof, so as to solve the problems in the prior art.
The realization process of the invention is as follows:
a method for supporting the implementation of clustered instant messages for Internet interrogation services, comprising:
the method comprises the steps that message node registration is carried out through a client, a temporary and dynamic token is generated through a registration request of a socketIO service node, and the validity of the token is controlled by a socketIO service end for the temporary token taken by the client;
when a sender sends a message to a socketIO service node through message node communication, the socketIO service node traverses the type of the message, establishes an observer mode, monitors an object through image-text messages, and realizes the butt joint with an image storage system; monitoring an object through a video message to realize the butt joint with a video service system; monitoring an object through health record information to realize the butt joint with the EHR system; monitoring an object through a prescription message to realize the object with an HIS system;
if the receiver finds out in the session, the message notification, the service interaction, the result encapsulation and the result message sending receiving end between the SocketIO service node and the service node are carried out.
The method for realizing the cluster instant message supporting the internet inquiry service comprises the following steps of registering message nodes through the client:
s10: initializing client registration, and sending a registration request to a registration request proxy service;
s20: a registration request proxy service receives a registration request of a client;
s21: the registration request proxy service distributes the new client to the socketIO service nodes in a balanced manner;
s30: the socketIO service node performs session registration;
s31: if the registration fails, returning to the step S20 to register the request proxy service, and the registration request proxy will return the error to the client;
s32: if the registration is successful, the socket IO service node creates an identity token for the client and finally responds to the client through an HTTP (hyper text transport protocol);
s40: and the client acquires the token with successful registration and finishes the registration.
The method for realizing the cluster-type instant message supporting the internet inquiry service specifically comprises the following steps of registering message nodes through the client:
s10: client registration initialization
The client needs to register and initialize the service node for instant message communication; in the process of registration initialization, a client establishes connection resources with a socket IO service node by sending a registration request to a registration agent service through a Websocket protocol over an HTTP protocol;
s20: the registration request proxy service receives a registration request of a client and performs dynamic socket IO allocation;
the proxy service is composed of a reverse proxy server based on an HTTP protocol, wherein the Nginx service can be effectively used as a high-performance reverse proxy service, through the two-stage registration mode, a first-stage proxy is used as a client request inlet to realize the dispatching of a socketIO cluster, and the socketIO cluster is used as a second-stage cluster to provide loads of hundreds of registration service sub-nodes;
s21: the process of the Nginx service acting is in a load balancing distribution mode, the load balancing algorithm is used for balancing load according to the minimum connection number algorithm provided by the Nginx service, and new client connection is preferentially registered for the SocketIO service node with the minimum connection number;
s30: the socket IO service node provides data communication between TCP/IP long connections on the basis of a Netty-socket IO open source component;
a session registration step of the socketIO service node: (a) the method comprises the following steps that (a) a socketIO service node obtains a client registration request sent by a registration agent node, (b) the socketIO performs database identity authentication on an identity certificate of the service node, and the identity authentication data is cached in a Redis memory database;
s31: if the registration fails and returns to the step S20, the registration request agent will return the error to the client;
s32: if the registration is successful, the socketIO service node creates an identity token for the client as an identity authorization certificate of the next access, and finally responds to the client through the HTTP;
s40: after the client acquires the token message which is successfully registered, the token is stored in a local temporary database of the client, and when the message is sent next time, the token and the message are sent together.
In the method for implementing the cluster-type instant message supporting the internet inquiry service, in step S40, the token has an expiration time, and if the token exceeds the expiration time, the client needs to re-register for application.
The method for realizing the cluster instant message supporting the internet inquiry service comprises the following steps in the message sending process:
100, the client serves as a sending end and starts to send the serial number of the health file;
200, the socketIO registration node acquires a message sent by a client;
201, inquiring the serial number of the EHR system of the hospital according to the serial number of the health file acquired by the 200socketIO registration node;
202, carrying out data encapsulation on patient index information in the health record and information required by hospital EHR transparent transmission;
the socket IO service node performs sending preparation after completing encapsulation of the health archive data, and confirms whether a receiver client exists in a registration list of the socket IO service node or not;
204, if the registration list of the socketIO service node is confirmed to have a receiver client, directly transmitting the encapsulated health file data to the receiver client;
300: the receiving party client receives the health file data, analyzes the health file data and links the health file data to 700, wherein the receiving party client inquires detailed information by an EHR system in a system to which the receiving party client belongs and returns the detailed information to the receiving party client for detailed display;
if the receiving party client side does not exist in the registration list of the socketIO service node, the socketIO needs to inform the MQ message service center, the socketIO service node acquires an MQ message service center client side object from the local, and pushes the Json data of the encapsulated health file to the MQ message service center through the MQ message service center object until the completion;
400, after data pushing is completed to the MQ message service center, the MQ message service receives the health archive data of the client of the sending party pushed by the SocketIO and adds the health archive data into a channel queue, and the MQ message service center broadcasts the health archive messages to all SocketIO message service nodes subscribed in the message service center;
500, each socket IO message node subscribing the health file channel of the MQ message service center acquires the message pushed by the MQ message service center in a polling way in time and confirms whether a receiver client exists in a registration list of the socket IO service node;
if the session list of the socketIO service node does not have the receiving client, directly discarding the message;
if the session list of the socketIO service node exists in the receiver client, taking out the session connection of the receiver client from the registration list, and directly transmitting the encapsulated health record data to the receiver client until the completion;
and 600, after the health file data transmission is completed to the receiver client, the receiver doctor client acquires the patient health file data transmitted by the sender, the receiver analyzes the health file data, and the health file data is linked to 700. the receiver belongs to a system, inquires detailed information by an EHR system and returns the detailed information to the receiver client for detail display.
In the method for implementing the cluster-type instant message supporting the internet inquiry service, in step 400, each SocketIO message node subscribing to the channel pushes the health archive data of the polling MQ message service center until the pushing is completed.
The above-mentioned method for implementing the cluster instant message supporting the internet inquiry service,
(a) the client sends a request message to the socketIO service node, wherein the request message comprises the type of the message;
(b) the socketIO service node performs message traversal from a monitoring object list, wherein the monitoring object comprises: image message monitoring, video chat message monitoring, health archive message monitoring and prescription message monitoring, wherein if the message type is matched with the monitor, the SocketIO service node implements thread asynchronization on the matched monitor, so that the main service is ensured to continuously process other message requests and is not blocked by the interaction between the monitor and an external service or system, and the main message processing and the service processing are thoroughly decoupled;
(c) the image message monitoring and the image storage service form interaction, mainly uploads an image to the image storage service, and acquires a download address of a packaged image; the video chat message monitoring and the video chat service form interaction, mainly carry out notification, connection establishment and message communication of point-to-point video chat destruction, and encapsulate video session state data; the health archive message monitoring is interacted with a health archive system, and the health archive index data and the transparent transmission source information are inquired and encapsulated according to the patient number; monitoring prescription information, interacting with a hospital HIS system, and inquiring and acquiring prescription data according to a prescription number; the encapsulated business message data is added into an encapsulated data queue event asynchronously processed by a main message service thread and is delivered to the main message service for dequeue processing of the encapsulated data; forming a main message package and a service data package which are completely decoupled;
(d) if the socketIO service node finds the session of the receiver at the service node, the result message is directly sent to the client of the receiver, if the result message is not found, the request message is directly pushed to an MQ message forwarding center without any processing, all message service node clusters subscribing the channel are broadcasted, the broadcast service node of the session of the receiver is found, the message event notification and the message result encapsulation are also carried out, the result message is also directly sent to the client of the receiver, the request message is directly abandoned if the broadcast service node is not found, and the communication and the message routing among all nodes of the clusters are thoroughly decoupled through an MQ broadcast mode.
A cluster instant message system supporting Internet inquiry service comprises a message node registration module, a message node communication module and a message node service integration module;
the message node registration module consists of a node agent service module and a client authorization module;
the message node communication module consists of a node communication module and a session management module;
the message node service integration module is composed of a service adaptation module and a service cooperation module.
Further, the node proxy service module is composed of a balance distribution module and a node management module; the client authorization module consists of a client token module and a client authentication module;
the node communication module consists of a message engine module and an MQ message center module; the session management module consists of a client joining module and a client quitting module;
the service adaptation module consists of a third party integration module and a message registration monitoring module; the service coordination module is composed of a message event notification module and a service calling encapsulation module.
Further, the balanced distribution module adopts a minimum network connection algorithm for distribution; the node management module comprises an adding dynamic detection module and a downtime dynamic detection module;
the message engine module comprises a message receiving module, a message sending module and a message filtering module; the MQ message center module comprises a message subscription module, a message pushing module and a message broadcasting module;
the third-party integration module comprises a video call service module, an image storage service module, a health file system and an HIS (home information system) system.
The key points of the invention are as follows:
the Jabber/XMPP protocol requires that the client de-couples the naming convention, that is, the naming of the client account is specified, especially the user name and the domain name are bound, which results in the locking of the client to the domain name. In the invention, a temporary and dynamic token is generated through the registration request of the socketIO service node, so that the user name and the instant message client mark are separated, and the user name is defined by a service system and is not restricted by an instant message system.
The temporary token taken by the client is also stored in the registration session list of the socketIO, and the validity of the token can be controlled by the socketIO server side through the validity of the fast matching token in the Hash set when each request is required, so that the safety of the whole access is improved.
According to the dynamic load of Nginx and the minimum connection number balancing algorithm, the registration agent enables the registration client to be automatically and uniformly distributed to each socket IO service node by the registration center, so that the resource cannot achieve optimal configuration better than that a Jabber framework needs the client to manually specify and register to the message service. Meanwhile, the client can form a dynamic reconnection mechanism, and even if the client is connected to the socketIO message service and goes down, the client can automatically reselect a new socketIO service node.
When a sender sends a message to a socketIO service node, the sender traverses the type of the message, judges the message to belong to image-text messages, video messages, health archive messages, prescription messages and the like, establishes an observer mode aiming at different message similarities, monitors an object through the image-text messages and realizes the butt joint with an image storage system; monitoring an object through a video message to realize the butt joint with a video service system; monitoring an object through health record information to realize the butt joint with the EHR system; and monitoring the object through the prescription message to realize the object with the HIS system. Therefore, the strong invasion service requirement for medical inquiry can completely decouple the message processing mechanism of the socketIO service node and the interaction of service systems such as medical inquiry and the like through the event monitoring mechanism of the traversal message type.
The receiver does not exist in the sender socketIO message node session, broadcasts in a socketIO message node cluster in the form of MQ message center broadcast, discards the message as long as the receiver does not exist in the session, and performs message notification, service interaction, result encapsulation and result message sending receiving end between the socketIO service node and the service node once found in the session, so that communication and message routing among all nodes of the cluster can be thoroughly decoupled.
The invention has the following positive effects:
compared with the standard Jabber/XMPP architecture and protocol, the cluster instant message system and the method for the internet inquiry service have great advantages, firstly, the client is not limited by naming any more, and can be automatically and dynamically registered to any message service of the cluster, thereby greatly ensuring the high reliability of the instant message use of the client; secondly, compared with manual domain name configuration, the network connection number-based load balancing algorithm maximally utilizes the resources of each node in the cluster, has better dynamic flexibility, realizes larger-scale instant message throughput pressure, and finally adopts the mode of MQ message center broadcasting, thereby not only reducing the routing pressure of each message node, but also preventing the concurrent pressure of sudden and sudden rise of a certain message node due to the mode of MQ queue, and completely preventing the message node from crashing due to certain delay of queue processing when a sudden peak condition occurs.
The client side is registered and decoupled, and the client side is completely decoupled on which message node of the cluster the client side is registered through a balanced load mechanism of a registration agent, so that the client side can more simply and dynamically register, switch and destroy the connection with the message cluster, and the high reliability and experience of the client side are enhanced; secondly, medical service decoupling, namely, completely decoupling the main message processing of the message node from service interaction through an asynchronous event monitoring mechanism and the service interaction, so that the robustness and robustness of the main message service are enhanced, and tightly coupling the message model and the service model can not be generated through the complete decoupling of the main message packaging and the service interaction data packaging, so that not only is the reliability of the service enhanced, but also more service interaction mechanisms can be more easily added on the basis of the message service, and an instant message infrastructure platform more conforming to the requirements of the medical service is created; finally, the route decoupling between the message services is realized through the support of the MQ message center on the pushing, subscribing and broadcasting of the message services, the message services can be added and destroyed more easily without knowing the states of other cluster nodes, and the flexibility of the clusters are greatly enhanced.
Drawings
FIG. 1 is a flow chart of a client registering an instant messaging service node according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating the transmission of a health profile message according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of service decoupling in an embodiment of the present invention;
fig. 4 is a block diagram of a clustered instant messaging system supporting an internet interrogation service in accordance with the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
Fig. 1 is a flow chart of client registering an instant messaging service node. The method comprises the following steps:
s10: client registration initialization
The client needs to perform instant messaging, and registration initialization of the service node is required first.
In the process, a client establishes a connection resource with a socket IO service node by sending a registration request to a registration agent service through a Websocket protocol over an HTTP protocol.
The socketIO service node establishes message communication interaction with other clients for the client, so that in the initialization process, one socketIO service node needs to be dynamically searched by an agent for registration.
S20: and the registration request agent receives the registration request of the client and performs dynamic socket IO allocation.
The proxy service is composed of a reverse proxy server based on the HTTP protocol, for example: the Nginx service can be effectively used as a high-performance reverse proxy service, and through the two-stage registration mode, the purpose that a first-stage proxy is used as a client request inlet is achieved, the dispatching of a socketIO cluster is achieved, and the socketIO cluster is used as a second-stage cluster and provides loads of hundreds of registration service sub-nodes.
For example: in the case of a server configuration with a stand-alone 8-core 64GB, a Nginx proxy can carry an average stand-alone hundred thousand connections and load to 10 SocketIO service nodes, which is equivalent to a message activity of providing a long-time registered active connection of 100 thousand users.
S21: the process of the Nginx agent acting is in a load balancing distribution mode, the load balancing algorithm is used for balancing load according to the minimum connection number algorithm provided by the Nginx, and new client connection is preferentially registered for the SocketIO service node with the minimum connection number.
S30: the socket IO service node is based on a Netty-socket IO open source component and provides data communication between TCP/IP long connections with high performance and end-to-end.
A registration step: (a) the SocketIO service node obtains a client registration request sent by a registration agent node, and (b) the SocketIO performs database identity authentication (generally cached in a Redis memory database) on an identity certificate of the service node.
S31 if the registration fails and returns to the proxy of the registration request, the proxy will return an error to the client.
And S32, if the registration is successful, the Socket service node creates an identity token for the client as an identity authorization certificate for the next access, and finally responds to the client through HTTP.
S40, after obtaining the token message which is registered successfully, the client stores the token in the local temporary database of the client, and when the message is sent next time, the client sends the token and the message together;
in addition, the token also has expiration time, and if the token exceeds the expiration time, the client needs to re-register for application.
FIG. 2 is a messaging flow diagram illustrating the transmission of a health profile message. The flow chart is the most important technical flow description in the patent.
And 100, the client serves as a sending end and starts the serial number sending of the health file.
For example: in the process of instant message communication between doctors and doctors, when one doctor needs to initiate patient condition consultation to the doctor of the other doctor, the doctor needs to share the patient information of the doctor to the other doctor, and the instant message transmission is the simplest and convenient method.
Step (a) a consulting doctor finds a patient by a client application system, (b) the consulting doctor selects the patient to click and send to a chat window of an opposite doctor, and the system can acquire a system number of the patient according to the selected patient in the process; (c) the system number, the registration token, the message type, the sender number and the receiver number are packaged into a message body, the Json format is used as a medium format for internet transmission, and the message body is sent to the socketIO registration node in an http request form.
200, the socketIO registration node acquires and processes the message sent by the consulting doctor client.
The method comprises the following steps: firstly, extracting a registration token from Json data of a client, performing identity authentication, performing next processing after determining that no error exists, extracting the serial number of a doctor of a sender from the Json data sent by the client, and determining a hospital to which the doctor belongs from a database;
firstly 201, extracting a patient number from Json data sent by a client, and acquiring patient health record index data of an EHR system of a hospital according to the patient number and a hospital to which a doctor belongs, wherein the index data comprises basic information capable of describing and clearly showing the whole outline of a patient, such as patient name, sex, an identity card, a last visit record, a common disease mark and the like;
secondly, 202, Json data encapsulation is carried out on the patient index information and the information required by the hospital EHR transparent transmission to form the information package of the patient basic information and the source;
and 203, the socketIO service node performs sending preparation after packaging the health archive data, extracts the number of the receiver from Json data sent by the client, searches and matches the client of the sending end in a session list of the socketIO service node, and confirms whether the client of the receiver exists in a registration list of the socketIO service node.
And 204, if a receiver client is confirmed in the registration list of the socketIO service node, taking out the session connection of the receiver client from the registration list, and directly transmitting the Json data of the encapsulated health record to the receiver client through a socketIO connection object until the completion.
And finally, if the client does not exist in the registration list of the socketIO service node, the socketIO needs to notify the MQ message service center, and the socketIO service node acquires the MQ message service center client object from the local and pushes the Json data of the encapsulated health record to the MQ message service center through the MQ message service center object until the completion.
300: after the health record data transmission is completed from the upper 204 to the receiver client, the receiver doctor client acquires the patient health record data transmitted from the sender, the receiver analyzes the health record Json data, firstly, the most basic personal basic situation and health information of the patient can be seen on the display of the client system, if the personal health situation of the patient needs to be further mastered, a data source including a plurality of lists of EHR transparent transmission information such as the address of the EHR system of the hospital to which the receiver belongs, the access certificate of the EHR system and the like needs to be analyzed from the health record Json data in a link mode, the data source is linked to the system of the hospital to which the receiver belongs through the transparent transmission access mode, the EHR system inquires the detailed health data of the patient, and the detailed health data are returned to the receiver client for detailed display.
400, after the data pushing is completed to the MQ message service center by the upper 205, the MQ message service receives the health file data of the sending party client terminal pushed by the socketIO and adds the health file data into the channel queue. The MQ message service center does not participate in the routing forwarding work of business logic, and indiscriminately broadcasts the health record messages to all the socket IO message service nodes (except for the push nodes) subscribed in the message service center. And each socket IO message node subscribing the channel pushes the health file data of the polling receiving MQ message service center until the pushing is completed.
500, each socketIO message node subscribing the health file channel of the MQ message service center acquires the message pushed by the MQ message service center in a polling way in time.
The method comprises the following steps: firstly, extracting the number of a receiving end of Json data of the health archive message, and determining whether a receiving end client exists in a registration list of the socketIO service node.
Secondly 501, if the receiving client does not exist in the session list of the socketIO service node, the message is directly discarded.
Finally 502, if the session list of the socketIO service node exists in the receiving client, taking out the session connection of the receiving client from the registration list, connecting the Json data of the encapsulated health file with an object through the socketIO service node, and directly transmitting the data to the receiving client until the completion;
600, after the health record data transmission is completed from the upper 502 to the receiver client, the receiver doctor client acquires the patient health record data transmitted from the sender, the receiver analyzes the health record Json data, firstly, the most basic personal basic situation and health information of the patient can be seen on the display of the client system, if the personal health situation of the patient needs to be further mastered, a data source including a certain series of EHR transparent transmission information such as the address of the EHR system of the hospital to which the receiver belongs, the access certificate of the EHR system and the like needs to be analyzed from the health record Json data in a link mode, the data source is linked to the system of the hospital to which the receiver belongs in a transparent transmission access mode, the EHR system inquires the detailed health data of the patient, and the detailed health data are returned to the receiver client for detailed display.
The message and traffic decoupling step is shown in fig. 3:
(a) a client (socketIO client) sends a request message to a socketIO service node (socketIOSever), wherein the request message comprises the type of the message;
(b) the socket ioserver performs message traversal from the listening object list, including: the method comprises the steps that PictureListener (image message monitoring), VideoChatListener (video chat message monitoring), EHR Listener (health archive message monitoring) and HISListener (prescription message monitoring), if the message type is matched with the monitor, the SocketIOServer implements thread asynchronization on the matched monitor, ensures that the main service continues to process other message requests and cannot be blocked by the interaction between the monitor and an external service or system, and realizes the complete decoupling of main message processing and service processing;
(c) the PictureListener and the ImagestorageServer form interaction, mainly upload images to the image storage service, and acquire a download address of the packaged images; the VideoChatListener and the VideoChatServer (video chat service) form interaction, mainly carry out point-to-point video chat message communication such as notification, connection establishment, destruction and the like, and encapsulate video session state data; the EHR Listener interacts with an EHR System (health record System), and inquires and packages health record index data and unvarnished transmission source information according to the patient number; the HISListener interacts with the HISSystem to query and obtain prescription data based on the prescription number. The encapsulated business message data is added into an encapsulated data queue event asynchronously processed by a main message service thread and is delivered to the main message service for dequeue processing of the encapsulated data; the primary message encapsulation is formed to be completely decoupled from the service data encapsulation.
(d) If the socketIOServer finds the session of the receiver in the service node, the result message is directly sent to the socketIOclient (the receiver), if the result message is not found, the request message is directly pushed to an MQ message forwarding center without any processing, all the server IOServer clusters subscribing the channel are broadcasted, the broadcast service node of the session of the receiver is found, the message event notification and the message result encapsulation are also carried out, the result message is also directly sent to the socketIOclient, and the request message is directly discarded if the result message is not found. And communication among all nodes of the cluster is completely decoupled from message routing through an MQ broadcast mode.
(2) Key point of the invention
The Jabber/XMPP protocol requires that the client de-couples the naming convention, that is, the naming of the client account is specified, especially the user name and the domain name are bound, which results in the locking of the client to the domain name. In the invention, a temporary and dynamic token is generated through the registration request of the socketIO service node, so that the user name and the instant message client mark are separated, and the user name is defined by a service system and is not restricted by an instant message system.
The temporary token taken by the client is also stored in the registration session list of the socketIO, and the validity of the token can be controlled by the socketIO server side through the validity of the fast matching token in the Hash set when each request is required, so that the safety of the whole access is improved.
According to the dynamic load of Nginx and the minimum connection number balancing algorithm, the registration agent enables the registration client to be automatically and uniformly distributed to each socket IO service node by the registration center, so that the resource cannot achieve optimal configuration better than that a Jabber framework needs the client to manually specify and register to the message service. Meanwhile, the client can form a dynamic reconnection mechanism, and even if the client is connected to the socketIO message service and goes down, the client can automatically reselect a new socketIO service node.
When a sender sends a message to a socketIO service node, the sender traverses the type of the message, judges the message to belong to image-text messages, video messages, health archive messages, prescription messages and the like, establishes an observer mode aiming at different message similarities, monitors an object through the image-text messages and realizes the butt joint with an image storage system; monitoring an object through a video message to realize the butt joint with a video service system; monitoring an object through health record information to realize the butt joint with the EHR system; and monitoring the object through the prescription message to realize the object with the HIS system. Therefore, the strong invasion service requirement for medical inquiry can completely decouple the message processing mechanism of the socketIO service node and the interaction of service systems such as medical inquiry and the like through the event monitoring mechanism of the traversal message type.
The receiver does not exist in the sender socketIO message node session, broadcasts in a socketIO message node cluster in the form of MQ message center broadcast, discards the message as long as the receiver does not exist in the session, and performs message notification, service interaction, result encapsulation and result message sending receiving end between the socketIO service node and the service node once found in the session, so that communication and message routing among all nodes of the cluster can be thoroughly decoupled.
Example 2
The cluster-type instant message system supporting the internet inquiry service in this embodiment is shown in fig. 4 and includes a message node registration module, a message node communication module, and a message node service integration module; the message node registration module consists of a node agent service module and a client authorization module; the message node communication module consists of a node communication module and a session management module; the message node service integration module is composed of a service adaptation module and a service cooperation module.
Further, the node proxy service module is composed of a balance distribution module and a node management module; the client authorization module consists of a client token module and a client authentication module;
the node communication module consists of a message engine module and an MQ message center module; the session management module consists of a client joining module and a client quitting module;
the service adaptation module consists of a third party integration module and a message registration monitoring module; the service coordination module is composed of a message event notification module and a service calling encapsulation module.
Further, the balanced distribution module adopts a minimum network connection algorithm for distribution; the node management module comprises an adding dynamic detection module and a downtime dynamic detection module;
the message engine module comprises a message receiving module, a message sending module and a message filtering module; the MQ message center module comprises a message subscription module, a message pushing module and a message broadcasting module;
the third-party integration module comprises a video call service module, an image storage service module, a health file system and an HIS (home information system) system.
In summary, the above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (6)
1. A method for supporting the implementation of a clustered instant message for an Internet interrogation service, comprising:
the method comprises the steps that message node registration is carried out through a client, a temporary and dynamic token is generated through a registration request of a socketIO service node, and the validity of the token is controlled by a socketIO service end for the temporary token taken by the client;
when a sender sends a message to a socketIO service node through message node communication, the socketIO service node traverses the type of the message, establishes an observer mode, monitors an object through image-text messages, and realizes the butt joint with an image storage system; monitoring an object through a video message to realize the butt joint with a video service system; monitoring an object through health record information to realize the butt joint with the EHR system; monitoring an object through a prescription message to realize the object with an HIS system;
if the receiver finds out in the session, the message notification, the service interaction, the result encapsulation and the result message sending receiving end between the SocketIO service node and the service node are carried out;
the HIS system is a hospital information management system, and the EHR system is an electronic health record system.
2. The method of claim 1, wherein the message node registration by the client comprises the steps of:
s10: initializing client registration, and sending a registration request to a registration request proxy service;
s20: a registration request proxy service receives a registration request of a client;
s21: the registration request proxy service distributes the new client to the socketIO service nodes in a balanced manner;
s30: the socketIO service node performs session registration;
s31: if the registration fails, returning to the step S20 to register the request proxy service, and the registration request proxy will return the error to the client;
s32: if the registration is successful, the socket IO service node creates an identity token for the client and finally responds to the client through an HTTP (hyper text transport protocol);
s40: and the client acquires the token with successful registration and finishes the registration.
3. The method for implementing clustered instant messaging supporting internet inquiry services as claimed in claim 2, wherein said registering of message nodes by the client comprises the following steps:
s10: client registration initialization
The client needs to register and initialize the service node for instant message communication; in the process of registration initialization, a client establishes connection resources with a socket IO service node by sending a registration request to a registration agent service through a Websocket protocol over an HTTP protocol;
s20: the registration request proxy service receives a registration request of a client and performs dynamic socket IO allocation;
the proxy service is composed of a reverse proxy server based on an HTTP protocol, wherein the Nginx service can be effectively used as a high-performance reverse proxy service, through the two-stage registration mode, a first-stage proxy is used as a client request inlet to realize the dispatching of a socketIO cluster, and the socketIO cluster is used as a second-stage cluster to provide loads of hundreds of registration service sub-nodes;
s21: the process of the Nginx service acting is in a load balancing distribution mode, the load balancing algorithm is used for balancing load according to the minimum connection number algorithm provided by the Nginx service, and new client connection is preferentially registered for the SocketIO service node with the minimum connection number;
s30: the socket IO service node provides data communication between TCP/IP long connections on the basis of a Netty-socket IO open source component;
a session registration step of the socketIO service node: (a) the method comprises the following steps that (a) a socketIO service node obtains a client registration request sent by a registration agent node, (b) the socketIO performs database identity authentication on an identity certificate of the service node, and the identity authentication data is cached in a Redis memory database;
s31: if the registration fails and returns to the step S20, the registration request agent will return the error to the client;
s32: if the registration is successful, the socketIO service node creates an identity token for the client as an identity authorization certificate of the next access, and finally responds to the client through the HTTP;
s40: after the client acquires the token message which is successfully registered, the token is stored in a local temporary database of the client, and when the message is sent next time, the token and the message are sent together.
4. The method of claim 2 or 3 for supporting a clustered instant messaging implementation of an internet interrogation service, characterized in that: in step S40, the token has an expiration time, and if the token exceeds the expiration time, the client needs to re-register the application.
5. The method for implementing the clustered instant message supporting the internet inquiry service as claimed in claim 1, wherein the message transmission process comprises the following steps:
100, the client serves as a sending end and starts to send the serial number of the health file;
200, the socketIO registration node acquires a message sent by a client;
201, inquiring the serial number of the EHR system of the hospital according to the serial number of the health file acquired by the 200socketIO registration node;
202, carrying out data encapsulation on patient index information in the health record and information required by hospital EHR transparent transmission;
the socket IO service node performs sending preparation after completing encapsulation of the health archive data, and confirms whether a receiver client exists in a registration list of the socket IO service node or not;
204, if the registration list of the socketIO service node is confirmed to have a receiver client, directly transmitting the encapsulated health file data to the receiver client;
300: the receiving party client receives the health file data, analyzes the health file data and links the health file data to 700, wherein the receiving party client inquires detailed information by an EHR system in a system to which the receiving party client belongs and returns the detailed information to the receiving party client for detailed display;
if the receiving party client side does not exist in the registration list of the socketIO service node, the socketIO needs to inform the MQ message service center, the socketIO service node acquires an MQ message service center client side object from the local, and pushes the Json data of the encapsulated health file to the MQ message service center through the MQ message service center object until the completion;
400, after the data pushing is completed to the MQ message service center by the upper 205, the MQ message service receives the health file data of the sending party client terminal pushed by the socketIO and adds the health file data into the channel queue; the MQ message service center does not participate in the routing forwarding work of business logic, and indiscriminately broadcasts the health record messages to all the socket IO message service nodes (except for push nodes) subscribed in the message service center;
500, each socket IO message node subscribing the health file channel of the MQ message service center acquires the message pushed by the MQ message service center in a polling way in time and confirms whether a receiver client exists in a registration list of the socket IO service node;
if the session list of the socketIO service node does not have the receiving client, directly discarding the message;
if the session list of the socketIO service node exists in the receiver client, taking out the session connection of the receiver client from the registration list, and directly transmitting the encapsulated health record data to the receiver client until the completion;
and 600, after the health file data transmission is completed to the receiver client, the receiver doctor client acquires the patient health file data transmitted by the sender, the receiver analyzes the health file data, and the health file data is linked to 700. the receiver belongs to a system, inquires detailed information by an EHR system and returns the detailed information to the receiver client for detail display.
6. The method of claim 5 for supporting a clustered instant messaging implementation of an internet interrogation service, characterized in that: in step 400, each SocketIO message node subscribing to the channel pushes the health archive data of the polling MQ message receiving service center until the pushing is completed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010004667.4A CN111211971B (en) | 2020-01-03 | 2020-01-03 | Cluster type instant message system supporting internet inquiry service and implementation method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010004667.4A CN111211971B (en) | 2020-01-03 | 2020-01-03 | Cluster type instant message system supporting internet inquiry service and implementation method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111211971A CN111211971A (en) | 2020-05-29 |
| CN111211971B true CN111211971B (en) | 2021-11-05 |
Family
ID=70786619
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010004667.4A Active CN111211971B (en) | 2020-01-03 | 2020-01-03 | Cluster type instant message system supporting internet inquiry service and implementation method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111211971B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111787073B (en) * | 2020-06-18 | 2023-08-22 | 庞茂林 | Current limiting fusing platform for unified service and method thereof |
| CN111899857A (en) * | 2020-07-29 | 2020-11-06 | 广州海鹚网络科技有限公司 | Data processing method and device based on hospital codes and computer equipment |
| CN112399256A (en) * | 2020-12-14 | 2021-02-23 | 富盛科技股份有限公司 | Method for detecting cluster and monitoring running service based on video streaming media service |
| CN112866091B (en) * | 2021-01-21 | 2022-09-13 | 即时匹配(上海)网络科技有限公司 | Instant communication system and communication method |
| CN114095568B (en) * | 2021-06-02 | 2023-09-12 | 北京机电工程研究所 | Message transmitting device and method based on middleware technology |
| CN113676477A (en) * | 2021-08-20 | 2021-11-19 | 中邮科通信技术股份有限公司 | Method for realizing Socket session cluster communication based on star network and memory routing table |
| CN113556587B (en) * | 2021-09-18 | 2021-12-24 | 广州易方信息科技股份有限公司 | Video playing link route optimization method and device based on android terminal |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101453482A (en) * | 2007-11-29 | 2009-06-10 | 中兴通讯股份有限公司 | Real-time data transmission method and real-time data transmission system |
| CN102447734B (en) * | 2012-02-14 | 2014-01-15 | 浪潮齐鲁软件产业有限公司 | Cloud service method for taxation cloud computing network billing IM (Instant Messaging) online customer system |
| US9270761B1 (en) * | 2014-10-08 | 2016-02-23 | Google Inc. | Device control profile for a fabric network |
| CN106055348A (en) * | 2016-05-19 | 2016-10-26 | 青岛海信电器股份有限公司 | Method and device for informing system attribute updating |
| CN106445705A (en) * | 2016-10-08 | 2017-02-22 | 武汉烽火众智数字技术有限责任公司 | Platform cascading method and system based on Rabbit MQ and Socket.io |
| CN107239675A (en) * | 2017-07-21 | 2017-10-10 | 上海桑格信息技术有限公司 | Biological information analysis system based on cloud platform |
| CN108320242A (en) * | 2017-01-17 | 2018-07-24 | 深圳市联教科技有限公司 | A kind of educational system based on multiple users share database |
| CN109040017A (en) * | 2018-06-25 | 2018-12-18 | 华南理工大学 | A kind of intelligent customer service system and implementation method based on MQTT and HTTP |
| CN109587228A (en) * | 2018-11-23 | 2019-04-05 | 济南浪潮高新科技投资发展有限公司 | A kind of publicly-owned agreement platform of internet of things and equipment cut-in method |
| US10397303B1 (en) * | 2016-08-29 | 2019-08-27 | Amazon Technologies, Inc. | Semantic annotation and translations for devices |
| CN110247971A (en) * | 2019-06-17 | 2019-09-17 | 福建天泉教育科技有限公司 | Reduce the method and its system of message-oriented middleware connection quantity |
| US10721336B2 (en) * | 2017-01-11 | 2020-07-21 | The Western Union Company | Transaction analyzer using graph-oriented data structures |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040019571A1 (en) * | 2002-07-26 | 2004-01-29 | Intel Corporation | Mobile communication device with electronic token repository and method |
-
2020
- 2020-01-03 CN CN202010004667.4A patent/CN111211971B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101453482A (en) * | 2007-11-29 | 2009-06-10 | 中兴通讯股份有限公司 | Real-time data transmission method and real-time data transmission system |
| CN102447734B (en) * | 2012-02-14 | 2014-01-15 | 浪潮齐鲁软件产业有限公司 | Cloud service method for taxation cloud computing network billing IM (Instant Messaging) online customer system |
| US9270761B1 (en) * | 2014-10-08 | 2016-02-23 | Google Inc. | Device control profile for a fabric network |
| CN106055348A (en) * | 2016-05-19 | 2016-10-26 | 青岛海信电器股份有限公司 | Method and device for informing system attribute updating |
| US10397303B1 (en) * | 2016-08-29 | 2019-08-27 | Amazon Technologies, Inc. | Semantic annotation and translations for devices |
| CN106445705A (en) * | 2016-10-08 | 2017-02-22 | 武汉烽火众智数字技术有限责任公司 | Platform cascading method and system based on Rabbit MQ and Socket.io |
| US10721336B2 (en) * | 2017-01-11 | 2020-07-21 | The Western Union Company | Transaction analyzer using graph-oriented data structures |
| CN108320242A (en) * | 2017-01-17 | 2018-07-24 | 深圳市联教科技有限公司 | A kind of educational system based on multiple users share database |
| CN107239675A (en) * | 2017-07-21 | 2017-10-10 | 上海桑格信息技术有限公司 | Biological information analysis system based on cloud platform |
| CN109040017A (en) * | 2018-06-25 | 2018-12-18 | 华南理工大学 | A kind of intelligent customer service system and implementation method based on MQTT and HTTP |
| CN109587228A (en) * | 2018-11-23 | 2019-04-05 | 济南浪潮高新科技投资发展有限公司 | A kind of publicly-owned agreement platform of internet of things and equipment cut-in method |
| CN110247971A (en) * | 2019-06-17 | 2019-09-17 | 福建天泉教育科技有限公司 | Reduce the method and its system of message-oriented middleware connection quantity |
Non-Patent Citations (2)
| Title |
|---|
| 区域卫生信息服务平台健康服务门户系统设计与实现;杨帆;《CNKI中国硕士论文全文数据库》;20141231;全文 * |
| 基于Nginx负载均衡的智能家居研究与实现;左晓麟;《CNKI中国硕士论文全文数据库》;20181231;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111211971A (en) | 2020-05-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111211971B (en) | Cluster type instant message system supporting internet inquiry service and implementation method thereof | |
| US10673938B2 (en) | Method and system for load balancing over a cluster of authentication, authorization and accounting (AAA) servers | |
| JP5898980B2 (en) | Method, system, and storage medium for managing multiple queues of non-persistent messages in a network environment | |
| US20060026290A1 (en) | Scalable infrastructure for handling light weight message protocols | |
| US8892768B2 (en) | Load balancing apparatus and load balancing method | |
| US6216173B1 (en) | Method and apparatus for content processing and routing | |
| US20030217096A1 (en) | Agent based application using data synchronization | |
| US20060036747A1 (en) | System and method for resource handling of SIP messaging | |
| EP2710776B1 (en) | Anonymous signalling | |
| US20040225753A1 (en) | Omnimodal messaging system | |
| US20100281169A1 (en) | Presence-awareness for wireless devices | |
| US20040221207A1 (en) | Proxy response apparatus | |
| CN101795222B (en) | Multi-stage forward service system and method | |
| US20080307062A1 (en) | Method, system and device for sending ims instant messages | |
| US7747694B2 (en) | Low latency and assured delivery using HTTP | |
| MXPA06014817A (en) | Method, system and computer program to enable sip event-based discovery of services and content within a community built on context information. | |
| US20020099858A1 (en) | Network communications protocol | |
| US20070226745A1 (en) | Method and system for processing a service request | |
| US8453229B2 (en) | Push type communications system | |
| US10084835B1 (en) | Systems and methods for distributing streams and stream metadata | |
| US20100306384A1 (en) | Multi-directional secure common data transport system | |
| CN116846959A (en) | Message receiving and transmitting method and device based on MQTT protocol | |
| US20070239827A1 (en) | Global chat system | |
| CN110474781B (en) | Method and device for forwarding multicast data | |
| CN113572678A (en) | Instant messaging method realized based on websocket |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: Room 1003, Building A, Zhongtou International, No. 10 Jinye 1st Road, High tech Zone, Xi'an City, Shaanxi Province, 710065 Patentee after: Xinnengkang Technology Co.,Ltd. Patentee after: Yang Fan Address before: 710077 Yongli international financial center, Jinye 1st Road, high tech Zone, Xi'an, Shaanxi Patentee before: Xi'an Xinneng Technology Co.,Ltd. Patentee before: Yang Fan |