WO2024001213A1

WO2024001213A1 - Information processing method, publisher, subscriber, and computer-readable storage medium

Info

Publication number: WO2024001213A1
Application number: PCT/CN2023/076291
Authority: WO
Inventors: 邵楠
Original assignee: 中兴通讯股份有限公司
Priority date: 2022-06-29
Filing date: 2023-02-15
Publication date: 2024-01-04
Also published as: CN117354199A

Abstract

The present application provides a message processing method, a publisher, a subscriber, and a computer-readable storage medium. The message processing method comprises: (110) obtaining a message to be published, and obtaining first sequence information of a corresponding target channel according to the message to be published; (120) encapsulating the message to be published and the first sequence information to obtain a published message; and (130) sending the published message to a subscriber corresponding to the target channel, such that the subscriber determines the continuity of the published message according to the first sequence information.

Description

Message processing method, publisher, subscriber and computer-readable storage medium

Cross-references to related applications

This application is filed based on a Chinese patent application with application number 202210750160.2 and a filing date of June 29, 2022, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated into this application as a reference.

Technical field

This application relates to but is not limited to the field of communication technology, and in particular, to a message processing method, a publishing end, a subscribing end, and a computer-readable storage medium.

Background technique

In the field of microservice management of embedded devices. There are dependencies on status changes between businesses. Multiple businesses located at different nodes need to pay attention to the status changes of a certain service at the same time. Therefore, a subscription publishing mechanism needs to be used to process business messages. When a business message is generated, the publisher publishes the business message. , so that subscribers can receive the business message. However, in the processing method of the related technology, the publisher usually publishes the message to the channel, and the subscribers who subscribe to the channel can receive the corresponding message. In some cases, for example, the amount of messages in the channel exceeds the buffer. When the message is lost, the subscriber cannot determine whether the message is lost in the channel because the subscriber cannot determine the continuity of the received message.

Contents of the invention

The following is an overview of the topics described in detail in this article. This summary is not intended to limit the scope of the claims.

In the first aspect, embodiments of the present application provide a message processing method, which is applied to the publishing end. The method includes: obtaining a message to be published, and obtaining the first sequence information of the corresponding target channel according to the message to be published; The message to be released is encapsulated with the first sequence information to obtain a release message; and the release message is sent to the subscriber corresponding to the target channel, so that the subscriber determines the release based on the first sequence information. Message continuity.

In the second aspect, embodiments of the present application provide a message processing method, which is applied to the subscribing end. The method includes: receiving a publishing message, which is sent by the publishing end; parsing the publishing message to obtain the first Sequence information: determine the continuity of the release message according to the first sequence information and the locally saved second sequence information.

In a third aspect, embodiments of the present application provide a publishing terminal, which includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, it implements the message processing method described in the first aspect.

In a fourth aspect, embodiments of the present application provide a subscription terminal, which includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, it implements the message processing method described in the second aspect.

In a fifth aspect, embodiments of the present application provide a computer-readable storage medium that stores a program. When the program is executed by a processor, the message processing method described in the first aspect is implemented, or the second aspect is implemented. The message processing method described.

Other features and advantages of the present application will be set forth in, and in part will be apparent from, the description that follows. Easily seen, or learned by practicing this application. The objectives and other advantages of the application may be realized and obtained by the structure particularly pointed out in the specification, claims and appended drawings.

Description of drawings

The drawings are used to provide a further understanding of the technical solution of the present application and constitute a part of the specification. They are used to explain the technical solution of the present application together with the embodiments of the present application and do not constitute a limitation of the technical solution of the present application.

Figure 1 is a schematic flow chart of a message processing method applied to the publishing end according to the embodiment of the present application;

Figure 2 is a flow chart of a message processing method provided by another embodiment of the present application;

Figure 3 is a flow chart for obtaining messages to be published provided by another embodiment of the present application;

Figure 4 is a schematic flowchart of a message processing method applied to a subscriber according to an embodiment of the present application;

Figure 5 is a flow chart of a message processing method provided by another embodiment of the present application;

Figure 6 is a flow chart of a message processing method provided by another embodiment of the present application;

Figure 7 is a flow chart of a message processing method provided by another embodiment of the present application;

Figure 8 is a flow chart of a message processing method provided by another embodiment of the present application;

Figure 9 is a system architecture diagram for executing a message processing method provided by another embodiment of the present application;

Figure 10 is a device diagram of a publishing end provided by another embodiment of the present application;

Figure 11 is a device diagram of a subscriber provided by another embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application and are not used to limit the present application.

It should be noted that although the functional modules are divided in the device schematic diagram and the logical sequence is shown in the flow chart, in some cases, the modules can be divided into different modules in the device or the order in the flow chart can be executed. The steps shown or described. The terms "first", "second", etc. in the description, claims, and above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific sequence or sequence.

Understandably, in the field of embedded device microservice management. There are dependencies on status changes between businesses. Multiple businesses located at different nodes need to pay attention to the status changes of a certain service at the same time. Therefore, a subscription publishing mechanism needs to be used to process business messages. When a business message is generated, the publisher publishes the business message. , so that subscribers can receive the business message. In the processing method of related technologies, the publisher usually publishes the message to the channel, and the subscribers who subscribe to the channel can receive the corresponding message. In some cases, for example, there are a large number of embedded devices and the status changes. Frequent, causing each embedded device to generate a lot of messages, which can easily cause the amount of messages in the corresponding channel to exceed the buffer, resulting in the loss of some messages, and because the subscriber cannot determine the continuity of the received messages, thus As a result, the subscriber cannot sense whether a message is lost in the channel, making the embedded device unable to process the lost message, and thus cannot guarantee the reliability of the message transmission process.

Based on this, this application provides a message processing method, a publishing end, a subscribing end and a computer-readable storage medium. The message processing method includes obtaining the message to be published, obtaining the first sequence information of the corresponding target channel according to the message to be published; The publication message is encapsulated with the first sequence information to obtain the publication message; the publication message is sent to the subscriber corresponding to the target channel, so that the subscriber determines the continuity of the publication message based on the first sequence information. Able to determine the continuity of messages and thus Determine whether message loss occurs.

The embodiments of the present application will be further described below with reference to the accompanying drawings.

Referring to Figure 1, Figure 1 is a flow chart of a message processing method provided by an embodiment of the present application. The message processing method is applied to the publishing end. The message processing method may include but is not limited to step S110, step S120 and step S130.

Step S110, obtain the message to be published, and obtain the first sequence information of the corresponding target channel according to the message to be published;

Step S120: Encapsulate the message to be released and the first sequence information to obtain the release message;

Step S130: Send a publish message to the subscriber corresponding to the target channel, so that the subscriber determines the continuity of the publish message based on the first sequence information.

It is worth noting that the first sequence information may include the name of the corresponding target channel and the sequence number used to characterize the order of the published message in the target channel. When the subscriber receives the published message, it can parse the published message. Obtain the corresponding target channel name and the sequence number of the published message, so as to know the order of the published message in the target channel, so that the subscriber can determine the publication based on the sequence number of the published message and the previous sequence number saved by the subscriber. The continuity of the message can determine whether there is any message loss before the message is published based on the continuity of the published message. It should be noted that this application does not limit the specific content of the first sequence information. The first sequence information can represent the corresponding target channel and the order of publishing messages in the target channel. Those skilled in the art can Configure the specific content of the first sequence information according to actual needs.

In one embodiment, the publishing end can be an embedded device, the corresponding subscriber can be another embedded device, and a target channel is established between the publishing end and the subscriber. When the business status of the embedded device as the publishing end changes, a corresponding business message is generated, and the business message is used as a message to be published. The publishing end obtains the first sequence information of the corresponding target channel based on the message to be published, and the message to be published is compared with the message to be published. The first sequence information is encapsulated to obtain a publishing message, and then the publishing message is sent to the subscriber corresponding to the target channel through the target channel, so that the subscriber determines the continuity of the published message based on the first sequence information.

It is worth noting that when the publisher and subscriber are both embedded devices, due to the tight memory resources of the embedded device under normal circumstances, component memory consumption needs to be strictly controlled, and there are many subscribers and publishers, and they are distributed in different locations. On the host node, it is necessary to ensure high distributed concurrency, especially when new nodes/business modules are added. Therefore, the general subscription publishing component cannot meet the needs of embedded devices, and in this embodiment , using the subscription and publishing function of redis to build a basic subscription and publishing model. It does not persist published messages, and supports multiple nodes and multiple subscription channels, with minimal memory consumption. For example, the publisher and subscriber establish corresponding target channels through the redis server, and store the first sequence information through redis. When the publisher obtains the message to be published, it obtains the first sequence information of the corresponding target channel from the server, and then publishes The terminal encapsulates the message to be published and the first sequence information to obtain the published message, and then sends the publishing message to the subscriber corresponding to the target channel, so that the subscriber determines the continuity of the published message based on the first sequence information. It should be noted that each embedded device can serve as both a publisher and a subscriber. In some embodiments, multiple embedded devices are included, and a subscription and publishing device is provided. The subscription and publishing device includes a redis-based subscription component and a publishing component, and all embedded devices are managed uniformly through the subscription and publishing device.

It should be noted that the above-mentioned embodiment uses the subscription and publishing function of redis to build a basic subscription and publishing model, and uses redis to store sequence information. However, in actual use, there are subscription and publishing components with similar characteristics to redis, which can be used as the subscription end and Regarding the basic components of the publishing side, those skilled in the art can set the basic components of the subscribing side and the publishing side according to actual needs.

It should be noted that the publisher and subscriber mentioned above are embedded devices. They are just an example and cannot be understood. To limit the scope of this application, for example, the publisher can also be a publishing agent component in an embedded device, and the subscriber can be a subscription agent component in an embedded device, or the publisher can be other devices, and the subscriber can also be other devices. Equipment, this application does not limit this.

It can be understood that, with reference to Figure 2, Figure 2 is a flow chart of a message processing method provided by another embodiment of the present application. In step S110, a message to be published is obtained, and the first sequence information of the corresponding target channel is obtained according to the message to be published. Afterwards, it may also include but is not limited to step S140.

Step S140: Update the first sequence information and save the updated first sequence information.

It is worth noting that the first sequence information is updated, for example, the sequence number in the first sequence information is incremented, and the first sequence information after the sequence number is incremented is saved. The updated first sequence information corresponds to the next one to be released. message, in this way, each message to be published can correspond to a unique sequence number, and the sequence numbers corresponding to each message to be published are incremented in order, so that after the subscriber receives the published message, it can judge the message based on the first sequence information continuity. It should be noted that the sequence number uses a continuous counting method to set the order, or it can be any method that can represent the sequence of the measured message, and this application does not limit this.

In some embodiments, the publishing end is based on the publish and subscribe function of redis and stores the first sequence information in the redis server. After receiving the message to be published, the publishing end obtains the corresponding first sequence information from the redis server and stores it in the redis server. The first sequence information is updated, and the updated first sequence information is stored in the redis server. It should be noted that the issuing end may also store the first sequence information locally on the issuing end, and this application does not limit this.

It can be understood that, with reference to Figure 3, Figure 3 is a flow chart for obtaining messages to be published provided by another embodiment of the present application. Obtaining the message to be published in step S110 may include but is not limited to step S111 and step S112.

Step S111: When the service message is received within the first preset period, the service message is used as a message to be released;

Step S112: When no service message is received within the first preset period, a keep-alive message is generated and used as a message to be released.

It is worth noting that when the service status of the embedded device as the publishing end changes, a corresponding business message is generated, and the business message is used as a message to be published, and the publishing end obtains the first sequence information of the corresponding target channel based on the message to be published. , encapsulate the message to be released and the first sequence information to obtain the release message, and then send the release message to the subscriber corresponding to the target channel through the target channel, so that the subscriber determines the continuity of the release message based on the first sequence information, and The embedded device as the subscribing end can obtain the service message, thereby learning the change in the service status of the embedded device as the publishing end.

It should be noted that when no business message is received within the first preset period, a keep-alive message is generated and used as a message to be published. This setting enables the publishing end to be able to Send a publication message to the corresponding subscriber so that the subscriber can determine that the target channel with the publisher is not disconnected. It should be noted that this application does not limit the time of the first preset period. Those skilled in the art can set the specific time of the first period according to actual needs; this application does not limit the specific content of the keep-alive message. Those skilled in the art can configure the specific content of the keep-alive message according to actual needs.

It is worth noting that, in one embodiment, this application uses atomic operations when executing the above-mentioned steps, so that when executing the above-mentioned steps of this application, the order cannot be disrupted, nor can it be Cut and perform only part of it.

In one embodiment, the type length value TLV format is used to encapsulate the message to be released and the first sequence information, and a cyclic redundancy check (Cyclic Redundancy Check, CRC) is used for encoding, thereby obtaining the release message. For example, T is Tag, which can indicate that the message to be published is a business message or a keep-alive message; L is Length, which indicates the data length; V is Value, which can be used to indicate the first sequence information. CRC is a channel coding technology that generates a short fixed-digit check code based on network data packets or computer files. It is mainly used to detect or verify errors that may occur after data transmission or storage. The subscriber receives After publishing a message, a CRC check can be performed to confirm the security of the published message. It should be noted that the use of TLV format and CRC for message encapsulation in this embodiment is only an example and cannot be understood as limiting the invention. Those skilled in the art can set the encapsulation format and encoding method according to actual needs.

In addition, referring to Figure 4, the embodiment of the present application provides a message processing method, applied to the subscriber side. The message processing method may include but is not limited to step S410, step S420 and step S430.

Step S410, receive the publishing message, which is sent by the publishing end;

Step S420, parse the release message to obtain the first sequence information;

Step S430: Determine the continuity of the published message based on the first sequence information and the locally saved second sequence information.

It is worth noting that the subscriber can be an embedded device, and the corresponding publisher can be another embedded device. A target channel is established between the publisher and the subscriber. The subscribing end receives the publishing message sent by the publishing end, parses the publishing message, obtains the first sequence information, and determines the continuity of the publishing message by using the first sequence information and the second sequence information pre-stored locally. For example, in one embodiment, the second sequence information represents the sequence number of the last published message. For example, the sequence number is 3. Then when the sequence number in the first sequence information is 4, it indicates that the published message is the same as the previous published message. Messages are continuous, so you can be sure that no message loss has occurred. In another embodiment, the second sequence information is the sequence number after the sequence number of the last published message is incremented. For example, the sequence number of the last published message is 3 and is incremented to 4. Then the second sequence information represents The sequence number is 4. When the sequence number in the first sequence information is 4, it indicates that the published message is continuous with the previous published message, so it can be determined that no message loss has occurred. When the sequence number in the first sequence information is 4 , it indicates that the published message is not continuous with the previous published message, so it can be determined that message loss has occurred. At this time, the subscriber generates an alarm message to notify the embedded device that message loss has occurred.

It can be understood that, with reference to Figure 5, Figure 5 is a flow chart of a message processing method provided by another embodiment of the present application. In step S430, the continuity of the published message is determined based on the first sequence information and the locally saved second sequence information. , after that, it may also include but is not limited to step S440.

Step S440: Update the locally saved second sequence information to the first sequence information.

It is worth noting that updating the locally saved second sequence information to the first sequence information includes updating the sequence number in the second sequence information to the sequence number of the first sequence information, so that when the next sequence is received at the subscribing end When publishing a message, the updated second sequence information can be compared with the first sequence information in the next published message to determine the continuity of the next published message. In one embodiment, the current sequence number of the first sequence information is 3, and the sequence number of the locally saved second sequence information is 2, then the sequence number in the second sequence information is updated to the sequence number of the first sequence information. , so that the sequence number in the updated second sequence information is 3. When the next publishing message is received, when the sequence number of the first sequence information in the next publishing message is 4, it indicates that the publishing messages are continuous, so It can be determined that no message loss has occurred; when the sequence number of the first sequence information of the next published message is not 4, such as 5 or 6 or other values, it indicates that the published messages are discontinuous, so it can be determined that message loss has occurred. At this time The subscriber generates alarm information to notify the embedded device that message loss has occurred.

It can be understood that, with reference to Figure 6, Figure 6 is a flow chart of a message processing method provided by another embodiment of the present application. Before step S410, receiving the release message, step S610 may be included but is not limited to.

Step S610: When it is detected that the target channel corresponding to the publishing end exists and the second sequence information of the target channel does not exist locally, If there is information, obtain the second sequence information of the target channel and save it locally.

It is worth noting that in some embodiments, the subscriber uses the subscription and publishing function based on redis as the basic component. The subscriber establishes a corresponding target channel with the publisher through the redis server, and the second sequence information of the target channel is stored in the redis server. , when it is detected that the target channel corresponding to the publisher exists and the second sequence information of the target channel does not exist locally, the subscriber obtains the second sequence information of the target channel from the redis server and saves it locally. When it is detected that the target channel corresponding to the publisher exists and the second sequence information of the target channel exists locally, the subscriber no longer obtains the second sequence information of the target channel from the redis server, but saves the locally saved second sequence information. The sequence information is updated to the first sequence information in the published message.

It can be understood that, with reference to Figure 7, Figure 7 is a flow chart of a message processing method provided by another embodiment of the present application. Before step S410, receiving the release message, step S710 may be included but is not limited to.

Step S710: When it is detected that the target channel corresponding to the publishing end does not exist, generate the second sequence information and the corresponding channel name, and establish the target channel with the publishing end based on the second sequence information and the channel name.

It is worth noting that when it is detected that the target channel corresponding to the publisher does not exist, the subscriber needs to establish a target channel with the publisher. The subscriber generates the second sequence information and the corresponding channel name, and based on the second sequence The information and channel name establish a target channel with the publisher, so that the subscriber can obtain the publication message sent by the publisher through the target channel. In some embodiments, there are many publishers and subscribers, and there are many corresponding target channels. Therefore, the channel name is used to represent a unique target channel, and the second sequence information of each target channel does not interfere with each other.

It can be understood that, with reference to FIG. 8 , FIG. 8 is a flow chart of a message processing method provided by another embodiment of the present application. The message processing method also includes step S810.

Step S810: When the publishing message is not received within the second preset period, the target channel with the publishing end is re-established.

In some embodiments, the second preset period is longer than the first preset period. During the first preset period, if the publishing end does not receive the service message, a keep-alive message is generated and the keep-alive message is As a message to be published, a publish message is then generated and sent to the subscriber. If the subscriber does not receive the publish message within the second preset period, it indicates that the target channel between the subscriber and the publisher is disconnected, or an error occurs. The message is lost, therefore, the target channel with the publisher is re-established, and the subscriber generates an exception message and sends the exception message to the embedded device.

It is worth noting that the subscriber can be a subscription agent component in an embedded device. After the subscription agent component obtains the published message, it performs a CRC check on the published message. If the verification is incorrect, an exception message is sent to the embedded device. When If the verification is correct, the published message will be parsed. When the message in the published message is a business message, the business message will be forwarded to the embedded device. When the message in the published message is a keep-alive message, it will not be forwarded to the embedded device.

It can be understood that, with reference to FIG. 9 , FIG. 9 is an architecture diagram of an example of the present application. The architecture includes a redis server, a subscription and publishing module and multiple business ends. Each business end is an embedded device. The subscription and publishing module manages all business ends in a unified manner. The subscription and publishing module includes a subscription agent component and a publishing agent component. The publishing agent component establishes a target channel with the subscription agent component through the redis server. When one of the business terminals changes status and generates a business message, the publishing agent component treats the business message as a message to be published and determines the target channel corresponding to the message to be published. And the first sequence information of the target channel, where the first sequence information of the target channel is stored in the redis server, and the message to be released is encapsulated with the first sequence information to obtain the release message, and the release message is sent to the subscription agent through the redis server. After receiving the publication message, the subscription agent parses the publication message to obtain the first sequence information, and determines the continuity of the publication message based on the first sequence information and the locally saved second sequence information. When it is determined that the published messages are continuous and the messages in the published messages are business messages, the business message will be sent to the business end subscribed to the target channel. When the messages in the published messages are keep-alive messages, Then the keep-alive message will not be forwarded to the business end. When it is determined that the published messages are discontinuous, it is determined that message loss has occurred, an exception message is generated, and an exception message is sent to the business end subscribed to the target channel.

In addition, referring to Figure 10, the embodiment of the present application provides a publishing terminal 300, which includes a memory 310 and a processor 320. The memory 310 stores a computer program. When the processor 320 executes the computer program, it implements a message processing method applied to the publishing terminal 300. .

The processor 320 and the memory 310 may be connected through a bus or other means.

As a non-transitory computer-readable storage medium, the memory 310 can be used to store non-transitory software programs and non-transitory computer executable programs. In addition, memory 310 may include high-speed random access memory 310 and may also include non-transitory memory 310 , such as at least one disk memory 310 , a flash memory device, or other non-transitory solid-state memory 310 . In some embodiments, the memory 310 optionally includes memory 310 located remotely relative to the processor 320, and these remote memories 310 may be connected to the processor 320 through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.

It should be noted that the non-transitory software programs and instructions required to implement the message processing method in the above embodiment are stored in the memory 310. When executed by the processor 320, the message processing method in the above embodiment is executed, for example, executing The method steps S110 to S130 in FIG. 1 , the method step S40 in FIG. 2 , and the method steps S111 to S112 in FIG. 3 are described above.

In addition, referring to Figure 11, the embodiment of the present application provides a subscriber 400, which includes a memory 420 and a processor 410. The memory 420 stores a computer program. When the processor 410 executes the computer program, it implements a message processing method applied to the subscriber 400. .

The processor 410 and the memory 420 may be connected through a bus or other means.

As a non-transitory computer-readable storage medium, the memory 420 can be used to store non-transitory software programs and non-transitory computer executable programs. In addition, memory 420 may include high-speed random access memory 420 and may also include non-transitory memory 420 such as at least one disk memory 420 , flash memory device, or other non-transitory solid-state memory 420 . In some embodiments, the memory 420 optionally includes memory 420 located remotely relative to the processor 410, and these remote memories 420 may be connected to the processor 410 through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.

It should be noted that the non-transitory software programs and instructions required to implement the message processing method in the above embodiment are stored in the memory 420. When executed by the processor 410, the message processing method in the above embodiment is executed, for example, executing The method steps S410 to S430 in FIG. 4 , the method step S440 in FIG. 5 , the method step S610 in FIG. 6 , the method step S710 in FIG. 7 , and the method step S810 in FIG. 8 are described above.

The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separate, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, embodiments of the present application provide a computer-readable storage medium. The storage medium stores a program. When the program is executed by a processor, it implements a message processing method applied to the publishing end, or implements a message processing method applied to the subscribing end.

The program of the present application is executed by a processor or controller, for example, by a processor in the above-mentioned device embodiment, which can cause the above-mentioned processor to execute the message processing method in the above-mentioned embodiment, for example, execute the above-described Figure 1 Method steps S110 to S130 in Figure 2 , method steps S40 in Figure 2 , method steps S111 to S112 in Figure 3 , method steps S410 to S430 in Figure 4 , method step S440 in Figure 5 , and the method in Figure 6 Step S610, the method in Figure 7 Method step S710, method step S810 in Figure 8.

The solution provided by this application can determine the continuity of messages and further determine whether message loss occurs.

Those of ordinary skill in the art can understand that all or some steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit . Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is known to those of ordinary skill in the art, the term computer storage media includes volatile and nonvolatile media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. removable, removable and non-removable media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassettes, tapes, disk storage or other magnetic storage devices, or may Any other medium used to store the desired information and that can be accessed by a computer. Additionally, it is known to those of ordinary skill in the art that communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

The above is a detailed description of the preferred implementation of the present application, but the present application is not limited to the above-mentioned embodiments. Those skilled in the art can also make various equivalent modifications or substitutions without violating the essence of the present application. Equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

A message processing method, applied to the publishing side, the method includes:

Obtain the message to be published, and obtain the first sequence information of the corresponding target channel according to the message to be published;

Encapsulate the message to be released and the first sequence information to obtain a release message;

The publishing message is sent to the subscriber corresponding to the target channel, so that the subscriber determines the continuity of the publish message based on the first sequence information.
The message processing method according to claim 1, wherein after obtaining the message to be published and obtaining the first sequence information of the corresponding target channel according to the message to be published, it further includes:

Update the first sequence information, and save the updated first sequence information.
The message processing method according to claim 1 or 2, wherein said obtaining the message to be published includes:

When a service message is received within the first preset period, the service message is used as the message to be released;

When the service message is not received within the first preset period, a keep-alive message is generated and used as the message to be released.
A message processing method, applied to the subscriber, the method includes:

Receive publishing messages, which are sent by the publishing end;

Parse the release message to obtain the first sequence information;

The continuity of the published message is determined according to the first sequence information and the locally saved second sequence information.
The message processing method according to claim 4, wherein after determining the continuity of the published message based on the first sequence information and the locally saved second sequence information, it further includes:

Update the locally saved second sequence information to the first sequence information.
The message processing method according to claim 4 or 5, wherein before receiving the release message, it further includes:

When it is detected that the target channel corresponding to the publishing end exists and the second sequence information of the target channel does not exist locally, the second sequence information of the target channel is obtained and saved locally.
The message processing method according to claim 4 or 5, wherein before receiving the release message, it further includes:

When it is detected that the target channel corresponding to the publishing end does not exist, the second sequence information and the corresponding channel name are generated, and the relationship with the channel is established based on the second sequence information and the channel name. The target channel between the publishing side.
The message processing method according to claim 7, further comprising:

When the publishing message is not received within the second preset period, the target channel with the publishing end is re-established.
A publishing end includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, the message processing method described in any one of claims 1 to 3 is implemented.
A subscriber includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, the message processing method described in any one of claims 4 to 8 is implemented.
A computer-readable storage medium stores a program. When the program is executed by a processor, the message processing method described in any one of claims 1 to 8 is implemented.