CN118101752A - Emergency information processing method and system - Google Patents

Emergency information processing method and system Download PDF

Info

Publication number
CN118101752A
CN118101752A CN202410226397.XA CN202410226397A CN118101752A CN 118101752 A CN118101752 A CN 118101752A CN 202410226397 A CN202410226397 A CN 202410226397A CN 118101752 A CN118101752 A CN 118101752A
Authority
CN
China
Prior art keywords
client
server
data
emergency data
emergency
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
Application number
CN202410226397.XA
Other languages
Chinese (zh)
Inventor
李兆元
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Agricultural Bank of China
Original Assignee
Agricultural Bank of China
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Agricultural Bank of China filed Critical Agricultural Bank of China
Priority to CN202410226397.XA priority Critical patent/CN118101752A/en
Publication of CN118101752A publication Critical patent/CN118101752A/en
Pending legal-status Critical Current

Links

Landscapes

  • Information Transfer Between Computers (AREA)

Abstract

The application discloses an emergency information processing method and system, in the method, an HTTP connection request of a client is received, and the HTTP connection request carries a client number of the client; an HTTP response is sent to the client, the HTTP response carries a service port number of the server, so that the client creates a server push event SSE technical connection based on the client port number and the service port number; acquiring target emergency data; if the version number of the target emergency data is the latest version number, acquiring the connection state of the server and the client; and when the connection state between the server and the client is normal, pushing corresponding target emergency data to the client based on the SSE technology. Therefore, through the lightweight SSE technology, the client is automatically in communication connection with the server, when the server and the client are in a connection state, the server pushes the target emergency data with the latest version number to the client, namely, the server pushes the emergency data in real time, and the effect of processing the emergency information is improved to a certain extent.

Description

Emergency information processing method and system
Technical Field
The application relates to the technical field of emergency information processing, in particular to an emergency information processing method and system.
Background
When a bank application system fails, a large amount of emergency data can be generated in a short time, and a worker needs to carry out corresponding emergency repair on the failure according to the emergency data. Because the emergency repair process is time-consuming and heavy in task, emergency information (e.g., emergency data) related to the emergency repair needs to be processed (e.g., pushed and acquired) in time.
In the existing emergency information processing process, the problems of untimely pushing and slower acquisition exist, so that the processing effect of staff is low.
Disclosure of Invention
The application provides an emergency information processing method and system, which can realize active pushing after emergency data updating, establish communication connection through lightweight SSE technology, quickly return emergency data associated with an emergency event, and improve the processing effect of staff in the emergency repair process to a certain extent.
In a first aspect, the present application provides an emergency information processing method, applied to a server, where the method includes:
receiving a hypertext transfer protocol (HTTP) connection request of a client, wherein the HTTP connection request carries a client port number of the client;
Sending an HTTP response to the client, wherein the HTTP response carries a service port number of the server so that the client creates a server push event SSE technical connection based on the client port number and the service port number;
Acquiring target emergency data;
if the version number of the target emergency data is the latest version number, acquiring the connection state of the server and the client;
And pushing corresponding target emergency data to the client based on the SSE technology when the connection state of the server and the client is normal.
Optionally, the obtaining the connection state between the server and the client includes:
Sending a heartbeat packet to the client based on a first time interval, wherein the heartbeat packet is used for verifying the connection state of the client and the server;
If the response of the client is not received in the second time interval, acquiring that the connection state is abnormal; the first time interval corresponds to the second time interval.
Optionally, the method further comprises:
creating a discussion group according to preset emergency event information, wherein the emergency event information comprises the number of at least one member client, and the discussion group comprises at least one member client;
creating an SSE technical connection with the at least one member client;
and broadcasting the message to the discussion group after receiving the message of the member client.
Optionally, the acquiring the target emergency data includes:
acquiring data of a plurality of application systems to obtain initial emergency data;
performing data cleaning on the initial emergency data to obtain target emergency data;
And sealing the target emergency data, and marking the version number of the target emergency data.
Optionally, the HTTP connection request further includes a request header, and the data acquisition is performed on the plurality of application systems to obtain initial emergency data, including:
Acquiring data of the plurality of application systems according to the request head to obtain initial emergency data, wherein the initial emergency data corresponds to the request head, and the initial emergency data comprises fault system data, associated alarm data or associated change data; wherein the fault system data comprises fault condition information of the system; the associated alarm data includes a fault event associated with the fault condition information; the association change data includes configuration change information associated with the fault condition information.
In a second aspect, the present application further provides an emergency information processing method, applied to a client, where the method includes:
Responding to a starting operation of starting the client, and sending a hypertext transfer protocol (HTTP) connection request to a server so as to acquire an HTTP response sent by the server; the HTTP connection request carries a client port number of the client, and the HTTP response carries a service port number of the service end;
Creating a server push event, SSE, technology connection with the server based on the client port number and the service port number, so that the server pushes data to the client based on the SSE technology;
And receiving target emergency data pushed by the server, wherein the connection state of the target emergency data at the server and the client is normal, the server is pushed to the client based on the SSE technology, and the version number of the target emergency data is the latest version number.
Optionally, the method further comprises:
receiving a heartbeat packet sent by the server, wherein the heartbeat packet is sent to the client by the server based on a first time threshold;
And if the heartbeat packet is not received within the first time threshold, executing the SSE technical connection with the service end based on the client port number and the service port number.
Optionally, the method further comprises:
The client is successfully connected with the server, and the latest version number sent by the server is received;
acquiring a current version number of emergency data in the client;
And if the latest version number is inconsistent with the current version number, acquiring the target emergency data.
Optionally, the method further comprises:
Acquiring a message sent by the client;
The message is sent to the server so that the server broadcasts the message to a discussion group, and the discussion group is created by the server based on preset emergency event information; the emergency event information includes a number of the client, and the discussion group includes the client.
In a third aspect, the present application further provides an emergency information processing system, where the system includes a client and a server, where:
The client is used for responding to the starting operation of starting the client and sending an HTTP connection request to the server, wherein the HTTP connection request carries a client port number of the client;
the server is configured to receive the HTTP connection request, send an HTTP response to the client, where the HTTP response carries a service port number of the server;
The client is further configured to receive the HTTP response, and create a server push event SSE technology connection based on the client port number and the service port number;
the server is also used for acquiring target emergency data;
The server is further configured to obtain a connection state between the server and the client if the version number of the target emergency data is the latest version number;
The server is further configured to push target emergency data to the client based on the SSE technology, where the connection state between the server and the client is normal, and the target emergency data corresponds to the client;
the client is further configured to receive the target emergency data.
Optionally, the server is specifically configured to:
Sending a heartbeat packet to the client based on a first time interval, wherein the heartbeat packet is used for verifying the connection state of the client and the server;
If the response of the client is not received in the second time interval, acquiring that the connection state is abnormal; the first time interval corresponds to the second time interval.
Optionally, the client is specifically configured to:
receiving a heartbeat packet sent by the server;
And if the heartbeat packet is not received within the first time threshold, executing the SSE technical connection with the service end based on the client port number and the service port number.
Optionally, the client is further configured to:
The client is successfully connected with the server, and the latest version number sent by the server is received;
acquiring a current version number of emergency data in the client;
And if the latest version number is inconsistent with the current version number, acquiring the target emergency data.
Optionally, the server is further configured to:
creating a discussion group according to preset emergency event information, wherein the emergency event information comprises the number of at least one member, and the discussion group comprises at least one member client;
creating an SSE technical connection with the at least one member client;
and broadcasting the message to the discussion group after receiving the message of the member client.
Optionally, the client is further configured to:
Acquiring a message sent by the client;
And sending the message to the server so that the server broadcasts the message to the discussion group.
Optionally, the server is specifically configured to:
data acquisition is carried out on at least one application system, and initial emergency data are obtained;
performing data cleaning on the initial emergency data to obtain target emergency data;
And sealing the target emergency data, and marking the version number of the target emergency data.
From this, the application has the following beneficial effects:
The application provides an emergency information processing method and system, in the method, an HTTP connection request of a client is received, and the HTTP connection request carries a client number of the client; an HTTP response is sent to the client, the HTTP response carries a service port number of the server, so that the client creates a server push event SSE technical connection based on the client port number and the service port number; acquiring target emergency data; if the version number of the target emergency data is the latest version number, acquiring the connection state of the server and the client; and when the connection state between the server and the client is normal, pushing corresponding target emergency data to the client based on the SSE technology. Therefore, the client is automatically connected with the server through the lightweight SSE technology, and when the server and the client are in a connection state, the server pushes the target emergency data of the latest version number to the client based on the SSE technology, namely the server pushes the emergency data in real time, and the success of staff on emergency information processing is improved to a certain extent.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to these drawings for those of ordinary skill in the art.
FIG. 1 is a schematic flow chart of an emergency information processing method according to an embodiment of the application;
FIG. 2 is a flow chart of another emergency information processing method according to an embodiment of the application;
FIG. 3 is a schematic diagram of an emergency information handling system 300 according to an embodiment of the present application;
FIG. 4 is a flow chart of another emergency information processing method according to an embodiment of the application;
Fig. 5 is a flow chart of another emergency information processing method according to an embodiment of the application.
Detailed Description
The plurality of the embodiments of the present application is greater than or equal to two. It should be noted that, in the description of the embodiments of the present application, the terms "first," "second," and the like are used for distinguishing between the descriptions and not necessarily for indicating or implying a relative importance, or alternatively, for indicating or implying a sequential order.
In order that the above-recited objects, features and advantages of the present application will become more readily apparent, a more particular description of embodiments of the application will be rendered by reference to the appended drawings and appended drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting thereof. In addition, for convenience of description, only a part, not all, of the structures related to the present application are shown in the drawings.
When a bank application system fails, a large amount of emergency data can be generated in a short time, and a worker needs to carry out corresponding emergency repair on the failure according to the emergency data. The inventor finds that the working personnel mainly comprises two aspects of technology in the process of processing emergency information, the first aspect realizes data timing refreshing through a browser, and the second aspect realizes full duplex communication between a server and a client based on a transmission control protocol (Transmission Control Protocol, TCP). However, the page timing refresh occupies a lot of network and server resources, and there is a delay in page update, for example, the timing update time is 5s, but new emergency information is generated at 3s, and then the page is pushed after waiting 2 seconds on a 3s basis; the TCP protocol requires a long time in the connection establishment process, and if the connection is disconnected, the connection cannot be automatically recovered, so that the current effect of processing emergency information is low.
Based on the above, the embodiment of the application provides an emergency information processing method and system, wherein the method comprises the following steps: receiving a hypertext transfer protocol (HyperText Transfer Protocol, HTTP) connection request of the client, the HTTP connection request carrying a client port number of the client; an HTTP response is sent to the client, the HTTP response carries a service port number of the server, so that the client creates a server push event SSE technical connection based on the client port number and the service port number; acquiring target emergency data; if the version number of the target emergency data is the latest version number, acquiring the connection state of the server and the client; and when the connection state between the server and the client is normal, pushing corresponding target emergency data to the client based on the SSE technology.
Therefore, the client is automatically connected with the server through the lightweight SSE technology, and when the server and the client are in a connection state, the server pushes the target emergency data of the latest version number to the client based on the SSE technology, namely the server pushes the emergency data in real time, and the success of staff on emergency information processing is improved to a certain extent.
In order to facilitate understanding of the specific implementation of the emergency information processing method provided by the embodiment of the present application, the following description will be given with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a flowchart of an emergency information processing method according to an embodiment of the present application, where the method may be applied to a server in an emergency information processing system, and the emergency information processing system may be, for example, the emergency information processing system 300 shown in fig. 3.
In an embodiment of the present application, the method may include the following steps:
s101: and receiving the HTTP connection request of the client.
It should be noted that, the HTTP connection request carries a client port number of the client, and the HTTP connection request is used to request to create an SSE Server push event SSE (Server-SEND EVENTS, SSE) technology connection with the Server.
S102: and sending the HTTP response to the client.
It should be noted that the HTTP response carries the service port number of the server, so that the client creates a server push event SSE technology connection based on the client port number and the service port number.
S103: and acquiring target emergency data.
In one possible implementation manner, S103 provided by the implementation of the present application may include: acquiring data of a plurality of application systems to obtain initial emergency data; performing data cleaning on the initial emergency data to obtain target emergency data; and (5) sealing the target emergency data and marking the version number of the target emergency data.
It should be noted that, the target emergency data can be sealed according to the actual service requirement, and the version number is marked, on one hand, the speed and the efficiency of data processing can be improved by recording and comparing the version number, and on the other hand, if the problem exists in the data in the follow-up process, the source of the problem can be traced back according to the version number.
In a possible implementation manner, the HTTP connection request may further include a request header, and then, data acquisition is performed on the multiple application systems to obtain initial emergency data, where the data acquisition includes: and acquiring data of a plurality of application systems according to the request head, and obtaining initial emergency data corresponding to the request head, so that refined data pushing is realized, and the emergency data in different fields are sent to corresponding clients.
The initial emergency data comprise fault system data, associated alarm data or associated change data, the fault system data comprise fault condition information of the system, and the time or reason of the fault is usually recorded; the associated alert data includes fault events associated with the fault condition information; the association change data includes configuration change information associated with the fault condition information.
As an example, the association alert data typically belongs to the field of information technology (Information Technology, IT) or system, the association change data typically belongs to the field of project management or operation, and then the request header of the HTTP connection request is sent for different clients, so as to obtain the emergency data of the corresponding field.
S104: and if the version number of the target emergency data is the latest version number, acquiring the connection state of the server and the client.
In a possible implementation manner, the obtaining the connection state between the server and the client provided by the embodiment of the present application may include: sending a heartbeat packet to the client based on the first time interval; if the response of the client is not received in the second time interval, acquiring that the connection state is abnormal; if the response of the client is received within the second time interval, the connection state is obtained as normal, and S105 is executed.
It should be noted that, the heartbeat packet is used for verifying the connection state of the client and the server, and the first time interval corresponds to the second time interval. In general, considering that a certain time is required for information transmission, the second time interval is set to be greater than the first time interval, which is, of course, only an example, and the embodiment of the present application does not limit the size relationship between the first time interval and the second time interval, and the embodiment of the present application can set the corresponding size relationship according to the actual application scenario, and all the embodiments of the present application are not affected.
It should be noted that, when the server side sends the heartbeat packet to the client side based on the first time interval, if the client side does not receive the heartbeat packet and reports errors in the first time interval, the client side reestablishes the connection. Therefore, besides the built-in automatic reconnection mechanism in the SSE technology, another disconnection reconnection mechanism is realized based on the timing heartbeat packet transmission, and the automatic disconnection reconnection double insurance is realized, so that the data transmission stability is ensured, and the processing efficiency of the emergency data is improved.
S105: and when the connection state between the server and the client is normal, pushing corresponding target emergency data to the client based on the SSE technology.
In a possible implementation manner, the client can also visually display the acquired target emergency data, so that a worker can more intuitively understand related fault conditions, and the emergency information management or processing efficiency is improved.
In one possible implementation manner, in order to improve the communication efficiency of the staff in the emergency information processing process, the method provided by the embodiment of the application further may include: creating a discussion group according to preset emergency event information, wherein the emergency event information comprises the number of at least one member client, and the discussion group comprises at least one member client; creating an SSE technical connection with at least one member client; and broadcasting the message to the discussion group when receiving the message of the member client.
In a particular implementation, the discussion group is created using an ordered set (Sorted Set) data structure of the Redis database, in particular by adding one or more members to the ordered set. When a new emergency event occurs, related emergency information needs to be broadcasted to members of the discussion group, broadcasting is usually achieved by using a publish-subscribe mode of Redis, a publisher publishes a message to a designated channel, and subscribers monitor the channel and receive the message.
As an example, the manager sets corresponding emergency event information according to the emergency event, for example, creates first emergency event information including a member a job number, a member B job number, a member C job number, a member D job number and a member E job number for the first emergency event, and then the server creates a first discussion group according to the first emergency event, at least one member client of the first discussion group includes a member a client, a member B client, a member C client, a member D client and a member E client, and then when the member a opens the client, an HTTP connection request including the client number of the member a is sent to the server, and after the server agrees to connect, an HTTP response is sent to the member a client, thereby implementing automatic connection. For example, the server side obtains the chat message of the client side of the member A and pushes the chat message to other client sides of other members in the discussion group, so that the member A, the member B, the member C, the member D and the member E can carry out online chat in the emergency repair process through the first discussion group, the communication or communication efficiency between the members is improved, and the effect of processing the emergency information is improved.
Thus, based on the emergency information processing method provided by the embodiment of the application, the server side can push the emergency information to the client side in real time by adopting a lighter and simpler SSE technology; the automatic reconnection of broken wires is supported, and specifically, in addition to an automatic reconnection mechanism built in the SSE, another broken wire reconnection mechanism is realized based on the timing sending of the heartbeat packet, and the double insurance of automatic broken wire reconnection is realized; meanwhile, the corresponding discussion group is provided based on the corresponding emergency event, so that the online chat of the staff is realized, and the success of the emergency information processing is improved.
Referring to fig. 2, fig. 2 is a flowchart of another emergency information processing method according to an embodiment of the present application, where the method may be applied to a client in an emergency information processing system, and the emergency information processing system may be, for example, the emergency information processing system 300 shown in fig. 3.
In an embodiment of the present application, the method may include the following steps:
S201: and responding to the starting operation of the starting client, and sending an HTTP connection request to the server so as to acquire an HTTP response sent by the server.
It should be noted that, the starting operation may be to log in the client or open a corresponding interface of the client, where the HTTP connection request carries a client port number of the client, and the HTTP response carries a service port number of the service end.
S202: based on the client port number and the service port number, a server push event SSE technology connection is created with the server so that the server pushes data to the client based on the SSE technology.
In this way, the automatic connection between the client and the server is realized in a short time through S201-S202, and the processing effect of the staff on the emergency information is improved to a certain extent.
S203: and receiving target emergency data pushed by the server.
It should be noted that, the connection state between the server and the client is normal, the server pushes the target emergency data to the client based on the SSE technology, and the version number of the target emergency data is the latest version number.
In one possible implementation manner, a client receives a heartbeat packet sent by a server, wherein the heartbeat packet is sent to the client by the server based on a first time threshold; if no heartbeat packet is received within the first time threshold, SSE technology connection with the server is established based on the client port number and the service port number.
In the specific implementation process, the client and the server are successfully connected, and the client receives the latest version number sent by the server; the method comprises the steps that a client obtains a current version number of emergency data in the client; if the latest version number is inconsistent with the current version number, the version number is proved to be updated, target emergency data corresponding to the updated version number needs to be obtained, and if the latest version number is consistent with the current version number, the emergency data obtained by the client is proved to be the emergency data of the latest version, and no operation is needed. Therefore, the automatic reconnection of the disconnection of the client is realized, and the target emergency data of the latest version number is acquired.
In one possible implementation, a message sent by a client is obtained; the method comprises the steps that a message is sent to a server side, so that the server side broadcasts the message to a discussion group, and the discussion group is created by the server side based on preset emergency event information; the emergency event information includes the number of the client that the discussion group includes. That is, the embodiment of the application establishes the corresponding discussion group aiming at the specific emergency event, and staff in the discussion group can realize online communication, so that the processing efficiency of emergency information is improved.
Thus, the method provided by the embodiment of the application realizes another disconnection reconnection mechanism based on the timing sending of the heartbeat packet and realizes the double insurance of automatic disconnection reconnection besides the built-in automatic reconnection mechanism of the SSE; meanwhile, a corresponding discussion group is provided based on a corresponding emergency event, and connection with a server side is automatically realized when a user opens a client side, so that online chat of staff is realized, and the effect of processing corresponding emergency information is improved.
Referring to fig. 3, fig. 3 is a schematic structural diagram of an emergency information processing system 300 according to an embodiment of the present application, where the system includes a client 301 and a server 302, and the method includes:
The client 301 is configured to send, in response to a startup operation for starting the client 301, an HTTP connection request to the server 302, where the HTTP connection request carries a client port number of the client 301;
the server 302 is configured to receive the HTTP connection request, and send an HTTP response to the client 301, where the HTTP response carries a service port number of the server;
The client 301 is further configured to receive the HTTP response, and create a server push event SSE technology connection based on the client port number and the service port number;
the server 302 is further configured to obtain target emergency data;
the server 302 is further configured to obtain a connection state between the server and the client 301 if the version number of the target emergency data is the latest version number;
The server 302 is further configured to push, to the client 301 based on the SSE technology, target emergency data when a connection state between the server and the client 301 is normal, where the target emergency data corresponds to the client 301;
The client 301 is further configured to receive the target emergency data.
Optionally, the client 301 is further configured to visually display the target emergency data.
Optionally, the server 302 is specifically configured to: sending a heartbeat packet to the client 301 based on a first time interval, wherein the heartbeat packet is used for verifying the connection state of the client 301 and the server 302; if no response of the client 301 is received within the second time interval, acquiring that the connection state is abnormal; the first time interval corresponds to the second time interval.
Optionally, the client 301 is specifically configured to: receiving a heartbeat packet sent by the server 302; if the heartbeat packet is not received within the first time threshold, the SSE technology connection with the server 302 is created based on the client port number and the service port number.
It should be noted that, the specific implementation process may refer to a flow chart of another emergency information processing method shown in fig. 4.
Optionally, the client 301 is further configured to: the client 301 and the server 302 are successfully connected, and the latest version number sent by the server 302 is received; acquiring a current version number of the emergency data in the client 301; and if the latest version number is inconsistent with the current version number, acquiring the target emergency data.
Optionally, the server 302 is further configured to: creating a discussion group according to preset emergency event information, wherein the emergency event information comprises the number of at least one member, and the discussion group comprises at least one member client; creating an SSE technical connection with the at least one member client; and broadcasting the message to the discussion group after receiving the message of the member client.
Optionally, the client 301 is further configured to: acquiring a message sent by the client 301; and sending the message to the server 302, so that the server 302 broadcasts the message to the discussion group.
It should be noted that, the specific implementation process may refer to a flow chart of another emergency information processing method shown in fig. 5.
Optionally, the server 302 is specifically configured to: data acquisition is carried out on at least one application system, and initial emergency data are obtained; performing data cleaning on the initial emergency data to obtain target emergency data; and sealing the target emergency data, and marking the version number of the target emergency data.
From the above description of embodiments, it will be apparent to those skilled in the art that all or part of the steps of the above described example methods may be implemented in software plus general hardware platforms. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network communication device such as a router) to perform the method according to the embodiments or some parts of the embodiments of the present application.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points. The apparatus embodiments described above are merely illustrative, in which the modules illustrated as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the objective of the embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The foregoing is merely a preferred embodiment of the present application and is not intended to limit the scope of the present application. It should be noted that modifications and adaptations to the present application may occur to one skilled in the art without departing from its scope.

Claims (10)

1. An emergency information processing method, which is characterized by being applied to a server, comprises the following steps:
receiving a hypertext transfer protocol (HTTP) connection request of a client, wherein the HTTP connection request carries a client port number of the client;
Sending an HTTP response to the client, wherein the HTTP response carries a service port number of the server so that the client creates a server push event SSE technical connection based on the client port number and the service port number;
Acquiring target emergency data;
if the version number of the target emergency data is the latest version number, acquiring the connection state of the server and the client;
And pushing corresponding target emergency data to the client based on the SSE technology when the connection state of the server and the client is normal.
2. The method of claim 1, wherein the obtaining the connection state of the server and the client includes:
Sending a heartbeat packet to the client based on a first time interval, wherein the heartbeat packet is used for verifying the connection state of the client and the server;
If the response of the client is not received in the second time interval, acquiring that the connection state is abnormal; the first time interval corresponds to the second time interval.
3. The method according to claim 1, wherein the method further comprises:
creating a discussion group according to preset emergency event information, wherein the emergency event information comprises the number of at least one member client, and the discussion group comprises at least one member client;
creating an SSE technical connection with the at least one member client;
and broadcasting the message to the discussion group after receiving the message of the member client.
4. The method of claim 1, wherein the acquiring the target emergency data comprises:
acquiring data of a plurality of application systems to obtain initial emergency data;
performing data cleaning on the initial emergency data to obtain target emergency data;
And sealing the target emergency data, and marking the version number of the target emergency data.
5. The method of claim 4, wherein the HTTP connection request further includes a request header, wherein the data collection for the plurality of application systems to obtain initial emergency data comprises:
Acquiring data of the plurality of application systems according to the request head to obtain initial emergency data, wherein the initial emergency data corresponds to the request head, and the initial emergency data comprises fault system data, associated alarm data or associated change data; wherein the fault system data comprises fault condition information of the system; the associated alarm data includes a fault event associated with the fault condition information; the association change data includes configuration change information associated with the fault condition information.
6. An emergency information processing method, applied to a client, comprising:
Responding to a starting operation of starting the client, and sending a hypertext transfer protocol (HTTP) connection request to a server so as to acquire an HTTP response sent by the server; the HTTP connection request carries a client port number of the client, and the HTTP response carries a service port number of the service end;
Creating a server push event, SSE, technology connection with the server based on the client port number and the service port number, so that the server pushes data to the client based on the SSE technology;
And receiving target emergency data pushed by the server, wherein the connection state of the target emergency data at the server and the client is normal, the server is pushed to the client based on the SSE technology, and the version number of the target emergency data is the latest version number.
7. The method of claim 6, wherein the method further comprises:
receiving a heartbeat packet sent by the server, wherein the heartbeat packet is sent to the client by the server based on a first time threshold;
And if the heartbeat packet is not received within the first time threshold, executing the SSE technical connection with the service end based on the client port number and the service port number.
8. The method of claim 7, wherein the method further comprises:
The client is successfully connected with the server, and the latest version number sent by the server is received;
acquiring a current version number of emergency data in the client;
And if the latest version number is inconsistent with the current version number, acquiring the target emergency data.
9. The method of claim 6, wherein the method further comprises:
Acquiring a message sent by the client;
The message is sent to the server so that the server broadcasts the message to a discussion group, and the discussion group is created by the server based on preset emergency event information; the emergency event information includes a number of the client, and the discussion group includes the client.
10. An emergency information processing system, comprising a client and a server, wherein:
The client is used for responding to the starting operation of starting the client and sending an HTTP connection request to the server, wherein the HTTP connection request carries a client port number of the client;
the server is configured to receive the HTTP connection request, send an HTTP response to the client, where the HTTP response carries a service port number of the server;
The client is further configured to receive the HTTP response, and create a server push event SSE technology connection based on the client port number and the service port number;
the server is also used for acquiring target emergency data;
The server is further configured to obtain a connection state between the server and the client if the version number of the target emergency data is the latest version number;
The server is further configured to push target emergency data to the client based on the SSE technology, where the connection state between the server and the client is normal, and the target emergency data corresponds to the client;
the client is further configured to receive the target emergency data.
CN202410226397.XA 2024-02-29 2024-02-29 Emergency information processing method and system Pending CN118101752A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410226397.XA CN118101752A (en) 2024-02-29 2024-02-29 Emergency information processing method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410226397.XA CN118101752A (en) 2024-02-29 2024-02-29 Emergency information processing method and system

Publications (1)

Publication Number Publication Date
CN118101752A true CN118101752A (en) 2024-05-28

Family

ID=91157395

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410226397.XA Pending CN118101752A (en) 2024-02-29 2024-02-29 Emergency information processing method and system

Country Status (1)

Country Link
CN (1) CN118101752A (en)

Similar Documents

Publication Publication Date Title
US8954504B2 (en) Managing a message subscription in a publish/subscribe messaging system
US6314512B1 (en) Automatic notification of connection or system failure in asynchronous multi-tiered system by monitoring connection status using connection objects
US20060233322A1 (en) Methods and apparatus for switching between data streams
CN112422684B (en) Target message processing method and device, storage medium and electronic device
CN110445697B (en) Video big data cloud platform equipment access service method
CN116319732A (en) Message queue centralized configuration management system and method based on RabbitMQ
US10931529B2 (en) Terminal device management method, server, and terminal device for managing terminal devices in local area network
JP2007199956A (en) Logging information management method and logging information management system
CN112615901B (en) Method for sending user request by client and storage system
CN113259408A (en) Data transmission method and system
CN118101752A (en) Emergency information processing method and system
CN109040286B (en) Client online state maintenance method based on memory database
CN108600004B (en) Video server configuration management method and system
CN112087341B (en) Communication method, system, electronic equipment and storage medium based on multichannel compensation
CN112637337B (en) Data processing method and device
CN107147867B (en) Distributed transcoding method and system
CN111131462A (en) Method for executing terminal instruction through protocol
CN110798398A (en) Group message management method, device, equipment and medium
CN115102854B (en) Remote procedure call route management control method, system and equipment for micro-service
CN109474694A (en) A kind of management-control method and device of the NAS cluster based on SAN storage array
US20220191256A1 (en) Agnostic data collection platform
KR101659579B1 (en) Server multiplex service providing apparatus using publish-subscribe method and method therefor
CN110750369B (en) Distributed node management method and system
JP7424494B2 (en) Request delivery device, request delivery method, and request delivery program
US20060075025A1 (en) System and method for data tracking and management

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination