CN111585808A - A message processing method, apparatus, device, and computer-readable storage medium - Google Patents

Abstract

The embodiment of the application discloses a message processing method, a message processing device, message processing equipment and a computer readable storage medium. The message processing method is connected with message servers of a plurality of sending ends and a plurality of receiving ends, receives and stores messages sent by the sending ends, blocks message requests if messages to be received of the receiving ends do not exist after the message requests sent by the receiving ends are obtained, and sends the messages to be received to the receiving ends after the messages to be received of the receiving ends are received. And because the network protocols of the sending end and the plurality of receiving ends are pre-configured in the message server, the device under the multi-network environment can be supported by the configuration items, and the low addressing cost and the highest transmission speed can be ensured.

Description

A message processing method, apparatus, device, and computer-readable storage medium

technical field

The present application relates to the field of computer network communications, and in particular, to a message processing method, apparatus, device, and computer-readable storage medium.

Background technique

With the continuous development of the computer industry, a wide variety of devices provide a wide variety of functions. The interactive communication between many devices makes many devices form a communication system. However, because the networks where the devices are located may be different, and the communication protocols used may also be different, the communication difficulty and complexity of the communication system composed of multiple devices are relatively high. Therefore, if the target devices are distributed in many places and under multiple networks, a technology designed for only one network environment may lead to lower addressing efficiency and lower network transmission speed.

Therefore, it is accessible in multiple networks and can communicate messages with various devices without multiple link transmissions, such as message transmission technology based on B/S architecture, which can ensure addressing efficiency and network transmission data speed.

However, in the current technology, each device and program needs to continuously send synchronization requests to the server to ensure the timeliness of the message, and the frequent requests lead to high resource occupancy of the device and the server during use.

SUMMARY OF THE INVENTION

In view of this, the present application provides a message processing method, apparatus, device, and computer-readable storage medium, as follows:

A message processing method, applied to a message server, wherein the message server is connected to multiple senders and multiple receivers, the method comprising:

The message server receives and stores the message sent by the sender, wherein the network protocols of the sender and a plurality of receivers are pre-configured in the message server;

After the message server obtains the message request sent by the receiving end, if there is no message to be received by the receiving end, the message server blocks the message request, and after receiving the message to be received from the receiving end, sends the message to the receiving end. The message to be received is sent to the receiving end.

Optionally, the method further includes:

The message server obtains a configuration file, and the configuration file includes the identifiers of the receiving end and the sending end and a parsing method of the message;

The message server registers the receiving end and the sending end according to the configuration file, and creates a storage space for the registered receiving end and the sending end;

In the case of adding a terminal, the message server registers the newly added terminal and creates a storage space for the newly added terminal, and in the case of deleting a terminal, cancels the deleted terminal and releases the deleted terminal storage space, the terminal includes the receiving end and/or the sending end.

Optionally, the receiving end and the sending end exist in multiple types of network environments, and/or the receiving end and the sending end use multiple network protocols of different types.

Optionally, receiving and storing a message sent by the sender, including:

Receive the message sent by the sending end, and if the sending end is registered, store the message in the linked list of the sending end of the message in the storage space according to the order of sending time;

If the sender is not registered, the sender is registered, and the message is stored in the linked list of the sender of the message in the storage space according to the order of sending time.

Optionally, after the message is stored in the linked list of the sender of the message in the storage space in the order of sending time, the method further includes:

grouping the messages in the linked list according to the receiving end;

If there is a target receiver of the message in the linked list, send the message in the packet of the target receiver to the target receiver, and the target receiver is the receiver with the blocked message request .

Optionally, after receiving the to-be-received message of the receiving end, sending the to-be-received message to the receiving end, including:

grouping the messages in the linked list according to the receiving end;

If the receiver of the message in the linked list is a blocked receiver, the message is sent to the blocked receiver.

Optionally, the method further includes:

If there is no message to be received by the blocked receiver within a preset time period, no message feedback is sent to the blocked receiver.

A message processing server, the message server is connected to a plurality of sending ends and a plurality of receiving ends, and the network protocols of the sending ends and the plurality of receiving ends are pre-configured in the message server;

The device includes: a message module and a cache module;

The message module is configured to receive a message sent by the sender;

The cache module is used to store the message sent by the sending end;

The message module is further configured to, after acquiring the message request sent by the receiving end, if there is no message to be received by the receiving end, block the message request, and after receiving the message to be received from the receiving end , and send the to-be-received message to the receiving end.

A message processing device, connecting a plurality of sending ends and a plurality of receiving ends, and the network protocols of the sending ends and the plurality of receiving ends are pre-configured in the message processing device;

The message processing device includes a memory and a processor, where the memory is used for storing a program, and the processor is used for running the program, so as to implement each step of the message processing method as described above.

A computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program runs on a computer device, each step of the above-mentioned message processing method is implemented.

The technical solution described in this application is to connect a message server with multiple senders and multiple receivers, receive and store messages sent by the sender, and after obtaining the message request sent by the receiver, if there is no message to be received by the receiver, then Block the message request, and after receiving the to-be-received message from the receiver, send the to-be-received message to the receiver, because after the message blocks the message request, the receiver will wait for the feedback of the message request. Reduce the resource consumption of message synchronization. And because the network protocols of the sender and multiple receivers are pre-configured in the message server, devices in multiple network environments can be supported through configuration items, which can ensure low addressing costs and the highest transmission speed.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the accompanying drawings that are used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

FIG. 1a is a schematic structural diagram of a message server disclosed in an embodiment of the application;

Figure 1b illustrates a schematic diagram of an example of a blocking message processing method based on B/S architecture;

2 is a schematic flowchart of a message processing method disclosed in an embodiment of the present application;

3 is a schematic flowchart of creating a storage space disclosed in an embodiment of the present application;

4 is a schematic flowchart of storing a message sent by a sending end disclosed in an embodiment of the present application;

FIG. 5 is a schematic flowchart of querying a message to be sent disclosed by an embodiment of the present application;

FIG. 6 is a schematic flowchart of sending a query to a message to be sent disclosed by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a message processing device disclosed in an embodiment of the present application.

Detailed ways

1a to 1b are examples of application scenarios of the message processing method disclosed in the embodiments of the present application, and the scenario includes multiple receiving ends and multiple sending ends. All terminals (including the receiving end and the sending end) may be in different types of networks, and may also use different types of protocols to communicate.

The message processing method disclosed in this application is executed by the message server shown in FIG. 1a. Wherein, the message server is respectively connected with the sender and the receiver, and further, it can be connected with the sender and the receiver respectively through the network layer, and the network layer can include HTTP layer, HTTPS layer, TCP layer and UDP layer. Specifically, as shown in FIG. 1a, the message server may include a cache module, a message module and a registration management module.

In the embodiments of the present application, from the perspective of hardware, the terminal is a tablet, a server, and a computer as examples for description, but it is not limited to the above examples.

From a software perspective, as shown in Figure 1b, the sender may include browser A, a UDP controller, and a TCP controller, and the receiver may include browser B, a UDP controller, and a TCP controller. As can be seen from Figure 1b, both the sender and the receiver are registered with the message server, and the message server implements message communication. Specifically, browsers A and B are HTTP/HTTPS receivers and senders, and are dynamically registered with the message server after the message server is started. The UDP controller can run on the tablet and use the UDP/IP protocol. The TCP controller can run on the server, using the TCP/IP protocol.

The technical solutions in the embodiments of the present application will be further described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

FIG. 2 is a message processing method disclosed by an embodiment of the present application, comprising the following steps:

S201: The message server obtains a configuration file.

Specifically, the configuration file may be set by a technician in advance according to the protocol used by the terminal and the network where the terminal is located, and sent to the message server. The configuration file can also be saved in the message server in advance. When the message service runs, the configuration file is parsed and stored in memory.

Table 1 illustrates the configuration items that can be included in the configuration file (where the suffix * is the items required for dynamic registration and messaging, ^ is the specific item for this instance, and the rest are pre-configured items that cannot be dynamically modified):

Table 1

It can be understood that each configuration value of the configuration item can be configured by the technician according to the receiving end, the sending end, and the network protocol, and in the case of changing the receiving end, the sending end, and the network protocol, the technician can configure more The configuration value of the item is modified. For a specific configuration manner, reference may be made to the prior art, which will not be repeated here.

Because the configuration item includes the identifiers of the receiving end and the transmitting end, the deletion or addition of the transmitting end and/or the receiving end can be realized through the configuration information.

S202: The message server performs initial configuration according to the configuration file.

Specifically, the steps of initializing the configuration include the following:

1. Put the message configuration file according to the location of CONFIGJSON in the configuration item. The specific content of the message configuration file is the set instructions and the corresponding device commands, such as Table 2:

Table 2

WhileScreen command to toggle full screen ABScreen The command to switch the AB screen

It can be understood that the message configuration file can also be preset by a technician.

2. Start the software and hardware of the message server that carries the message service, and initialize the registration information management module.

3. The registration information management module registers the sender and receiver according to the configuration value of the configuration item, and records the global encoding format and other configurations.

It can be understood that the message server can register the newly added terminal and create a storage space for the newly added terminal according to the newly acquired configuration file after the terminal is added or deleted, and then delete the terminal. In this case, the deleted terminal is deregistered and the storage space of the deleted terminal is released, wherein the terminal includes a receiving end and/or a transmitting end.

4. According to the configuration value of the configuration item, the message server starts to try to occupy the UDP listening port and the TCP port. If it fails, the UDP and TCP message receiving and sending functions fail to start.

5. The registration information management module notifies that the initialization is completed, and the message server creates the process of the cache module.

6. The cache module creates the storage space corresponding to the sender. The specific process is shown in Figure 3.

7. The interface of the registration information management module is open, waiting to receive dynamic registration.

8. The cache module sleeps, and the message module waits for a request.

It can be understood that S201 and S202 are pre-configured processes, and if the terminal and the network are not changed, they can be configured only once and do not need to be repeatedly performed. In addition, S201 to S202 are only an optional specific implementation manner of pre-configuration, and it should be noted that the specific implementation manner of pre-configuration includes multiple types, which will not be repeated in this embodiment.

Based on the above configuration, the message server implements the message communication process between the sender and the receiver. Specifically, it can be divided into a scenario where the sender sends a message and a scenario where the receiver sends a message request. For details, see the following steps:

Scenarios where the sender sends a message:

S203: The sender sends a message.

S204: The message server receives the message through the network layer, parses the message according to the global encoding format configured in the configuration file, and obtains the sender identifier of the message.

S205: The registration information management module judges whether the identifier of the sender exists in the registration information, and if so, executes S206-S208, and if not, executes S209-S210.

S206: The message server stores the message sent by the sending end, and the specific process can be referred to as shown in FIG. 4 .

S207: The message server queries the message to be sent, and the specific process can be referred to as shown in FIG. 5 .

S208: The message server sends the queried message to be sent, and the specific process can be referred to as shown in FIG. 6 .

S209: The registration information management module registers the sender.

S210: The message server creates a storage space for the newly registered sender, as shown in FIG. 3 for details.

After S210, execute S206-S208.

The foregoing S202 to S210 are an optional implementation manner of receiving and storing a message sent by the sending end provided by the embodiment of the application. S202 to S210 can be summarized as: receiving a message sent by the sending end, and if the sending end is registered, message is stored. If the sender is not registered, the message is stored after the sender is registered.

It should be noted that, receiving and storing the message sent by the sending end in the embodiments of the present application may also include other implementation manners, which are not limited in the present application.

Scenarios where the receiver sends a message request:

S211: The receiving end sends a message request.

S212: The message server receives the message request through the network layer, parses the message request according to the global encoding format configured in the configuration file, and obtains the identifier of the receiver sending the message request (referred to as the received identifier).

S213: The registration information management module judges whether the receiver identifier exists in the registration information, and if so, executes S214-S218, and if not, executes S219-S220.

S214: The message server queries the message to be sent, and the specific process can be referred to as shown in FIG. 5 .

S215: The message server sends the query to the message to be sent, and the specific process can be referred to as shown in FIG. 6 .

S216: If the message server does not find a message, it blocks the message request.

Blocking is a common technical method in the field of software engineering. Here, it refers to suspending a message request and not allowing it to complete.

In the case that the message request is blocked, the receiving end will not receive the feedback of the message request, therefore, the message request will not be sent again, but will wait for the feedback.

S217: The message server determines whether the blocking duration is greater than the preset duration threshold, and if so, executes S218, and if not, executes S217.

S218: Unblock and reply no message to the sender.

S219: The registration information management module registers the receiver.

S220: The message server creates a storage space for the newly registered receiver, as shown in FIG. 3 for details.

After S220, execute S214-S218.

It should be noted that after receiving the message, the receiving end can parse the message and perform corresponding processing according to the source and content of the message.

The above S212 to S216 can be summarized as:

After obtaining the message request sent by the receiver, the message server blocks the message request if there is no message to be received by the receiver, and sends the message to be received to the receiver after receiving the message to be received from the receiver.

It should be noted that S212 to S216 are only an optional implementation manner, and this embodiment may further include other specific implementation manners, which are not described repeatedly in this embodiment.

The above S217-S220 can be summarized as:

If there is no message to be received by the blocked receiver within the preset time period, no message feedback is sent to the blocked receiver. It should be noted that, S217 to S220 in this embodiment are only optional steps, and are used to feed back no message to the receiving end in time.

The flow shown in Figure 2 has the following beneficial effects:

1. The message server receives and stores the message sent by the sender, and when the receiver requests a message, if there is no message from the receiver, the message request is blocked, because after the message request is blocked, the receiver will wait for the feedback of the message request, so no The message request will be sent again. Therefore, the request frequency is greatly reduced, and the resource occupation of message synchronization can be reduced.

2. The network protocols of the sender and multiple receivers are pre-configured in the message server, so devices in multiple network environments can be supported through configuration items, so low addressing costs and the highest transmission speed can be guaranteed.

3. Since the sender and receiver can be dynamically registered, and the parsing behavior of the customized message can be customized, the flexibility of the service is improved.

The following will further describe the storage space allocation process, the message storage process, the query process for messages to be sent, and the process for sending messages to be sent from the perspective of each module in the message server.

Figure 3 shows the process of creating a storage space, including the following steps:

S301: The cache module is woken up.

S302: The cache module receives an instruction to create a space.

It can be understood that the message module sends a space creation instruction to the cache module as needed, that is, in the case where a storage space needs to be created for the sender, for example, S210, a space creation instruction including the sender identifier is sent, and a space creation instruction needs to be created for the receiver. In the case of storage space, for example, S219, send a space creation instruction including the identifier of the receiver.

S303: The cache module creates the storage space of the terminal according to the space creation instruction.

Specifically, the sender identifier or the received identifier in the space creation instruction is put into the map, and the corresponding relationship between the map and the linked list is created.

Optionally, in order to save resources, the cache module may enter a sleep state after completing the creation of the storage space.

Fig. 4 is the process flow of storing the message that the sending end sends, including the following steps:

S401: The cache module is woken up.

S402: The cache module receives a message storage instruction.

Specifically, the message storage instruction may be issued by the message module after receiving the message sent by the sender.

S403: The cache module stores the messages in a linked list corresponding to the sender according to the sending time sequence.

Optionally, in order to save resources, the cache module may enter a sleep state after storing the message.

Figure 5 is a process of querying messages to be sent, including the following steps:

S501: The cache module is woken up.

S502: The cache module receives a message query instruction.

Specifically, the message query instruction may be sent by the message module at S207 or S214.

S503: The cache module traverses the storage space of the existing sender to find the message to be sent.

S504: Send the message to be sent to the message module.

Optionally, in order to save resources, the cache module may enter a sleep state after completing the message query.

Fig. 6 is the process flow of sending the query to the message to be sent, including the following steps:

S601: The message module receives the message to be sent.

S602: The message module parses the to-be-sent messages, and groups the to-be-sent messages according to the receiving end.

S603: The message module tries to find the blocked receiving end from the registration information management module, and if found, executes S604, and if not found, executes S605.

S604: Wake up the receiver, and send the messages to be sent whose receivers are blocked receivers to the corresponding receivers in chronological order.

S605: Store the message to be sent in the cache module. The specific storage process is as described above.

The embodiment of the native device discloses a message processing device, the message processing device is connected to a plurality of sending ends and a plurality of receiving ends, wherein the network protocols of the plurality of sending ends and the plurality of receiving ends are pre-configured in the message processing device; The device includes a memory and a processor. Wherein, the memory is used for storing the program, and the processor is used for running the program, so as to realize each step of the message processing method.

7 is a schematic structural diagram of a message processing device disclosed in an embodiment of the present application, the device may include: at least one processor 701, at least one communication interface 702, at least one memory 703, and at least one communication bus 704;

In this embodiment of the present application, the number of the processor 701, the communication interface 702, the memory 703, and the communication bus 704 is at least one, and the processor 701, the communication interface 702, and the memory 703 complete the communication with each other through the communication bus 704;

The processor 701 may be a central processing unit (CPU), or a specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of the present invention, etc.;

The memory 703 may include high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), for example, at least one disk memory;

The memory stores a program, and the processor can execute the program stored in the memory to implement the message processing method described in the above item.

Embodiments of the present application further provide a computer-readable storage medium, where a computer program suitable for execution by a processor can be stored in the computer-readable storage medium. When the computer program is executed by the processor, the above message processing method is implemented.

If the functions described in the methods of the embodiments of the present application are implemented in the form of software functional units and sold or used as independent products, they may be stored in a readable storage medium of a computing device. Based on this understanding, the part of the embodiments of the present application that contribute to the prior art or the part of the technical solution may be embodied in the form of a software product, and the software product is stored in a storage medium and includes several instructions to make a A computing device (which may be a personal computer, a server, a mobile computing device or a network device, etc.) executes all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments may be referred to each other.

The above description of the disclosed embodiments enables any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, this application is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. a message processing method, is characterized in that, is applied to message server, and described message server connects multiple sending ends and multiple receiving ends, described method comprises: The message server receives and stores the message sent by the sender, wherein the network protocols of the sender and a plurality of receivers are pre-configured in the message server; After the message server obtains the message request sent by the receiving end, if there is no message to be received by the receiving end, the message server blocks the message request, and after receiving the message to be received from the receiving end, sends the message to the receiving end. The message to be received is sent to the receiving end. 2. The method of claim 1, further comprising: The message server obtains a configuration file, and the configuration file includes the identifiers of the receiving end and the sending end and a parsing method of the message; The message server registers the receiving end and the sending end according to the configuration file, and creates a storage space for the registered receiving end and the sending end; In the case of adding a terminal, the message server registers the newly added terminal and creates a storage space for the newly added terminal, and in the case of deleting a terminal, cancels the deleted terminal and releases the deleted terminal storage space, the terminal includes the receiving end and/or the sending end. 3. The method according to claim 2, wherein the receiving end and the transmitting end exist in multiple types of network environments, and/or the receiving end and the transmitting end use different types of Various network protocols. 4. The method according to claim 2, wherein the receiving and storing the message sent by the sending end comprises: Receive the message sent by the sending end, and if the sending end is registered, store the message in the linked list of the sending end of the message in the storage space according to the order of sending time; If the sender is not registered, the sender is registered, and the message is stored in the linked list of the sender of the message in the storage space according to the order of sending time. 5. The method according to claim 4, characterized in that, after the message is stored in the linked list of the sending end of the message in the storage space according to the order of sending time, the method further comprises: : grouping the messages in the linked list according to the receiving end; If there is a target receiver of the message in the linked list, send the message in the packet of the target receiver to the target receiver, and the target receiver is the receiver with the blocked message request . 6. The method according to claim 4, wherein, after receiving the message to be received from the receiving end, sending the message to be received to the receiving end, comprising: grouping the messages in the linked list according to the receiving end; If the receiver of the message in the linked list is a blocked receiver, the message is sent to the blocked receiver. 7. The method of claim 1, further comprising: If there is no message to be received by the blocked receiver within a preset time period, no message feedback is sent to the blocked receiver. 8. A message processing server, characterized in that the message server is connected to multiple senders and multiple receivers, and the network protocols of the sender and multiple receivers are preconfigured in the message server; The message processing server includes: a message module and a cache module; The message module is configured to receive a message sent by the sender; The cache module is used to store the message sent by the sending end; The message module is further configured to, after acquiring the message request sent by the receiving end, if there is no message to be received by the receiving end, block the message request, and after receiving the message to be received from the receiving end , and send the to-be-received message to the receiving end. 9. A message processing device, characterized in that a plurality of sending ends and a plurality of receiving ends are connected, and the network protocols of the sending ends and the plurality of receiving ends are preconfigured in the message processing device; The message processing device includes a memory and a processor, where the memory is used for storing a program, and the processor is used for running the program, so as to implement the message processing method according to any one of claims 1-7. 10. A computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program is run on a computer device, the message processing method according to any one of claims 1-7 is implemented.

Images