Message sending method and device, message receiving method and device, electronic equipment and medium

Abstract

The embodiment of the invention discloses a message sending method and device, a message receiving method and device, electronic equipment and a medium. According to one specific embodiment, the method comprises the steps that at least one target message is obtained, and the at least one target message is each message generated by a target user in the layer operation process; for each target message in the at least one target message, executing a first adding step: determining whether a message byte corresponding to the target message meets a preset byte condition or not; in response to determining that the preset byte condition is met, adding the target message to a target database, and generating a database identifier corresponding to the target message; adding the database identifier to a to-be-sent message queue; and the added to-be-sent message queue is sent to a second terminal, and the second terminal is a terminal which performs layer operation synchronization with the first terminal. The implementation mode is related to message processing, the overall sending time delay of the message can be reduced, and the real-time performance of layer cooperation is improved.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technology, and in particular to a message sending method, a message receiving method, a device, an electronic device, and a medium. Background Art

[0002] At present, in the scenario of operating layer sharing, user A wants user B to view the operation of the layer in real time. Therefore, the message transmission corresponding to the operation layer is very important. For the sending of messages, the method usually adopted is: at least one target message generated by the target user during the layer operation process is directly added to the queue of messages to be sent, so as to send the message.

[0003] However, the inventors have found that when the above method is used to send messages, the following technical problems often occur:

[0004] In the case of a target message with a large message size, the transmission time will be relatively long, so that subsequent messages may be delayed in sending, resulting in poor real-time performance of message sending.

[0005] The above information disclosed in this Background section is only for enhancement of understanding of the background of the inventive concept and therefore it may contain information that does not form the prior art that is already known in this country to a person of ordinary skill in the art. Summary of the invention

[0006] The content of this disclosure is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this disclosure is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

[0007] Some embodiments of the present disclosure propose a message sending method, a message receiving method, an apparatus, an electronic device, and a medium to solve the technical problems mentioned in the above background technology section.

[0008] In a first aspect, some embodiments of the present disclosure provide a message sending method, which is applied to a first terminal, and includes: obtaining at least one target message, wherein the at least one target message is each message generated by a target user during a layer operation; for each target message in the at least one target message, executing a first adding step: determining whether the message bytes corresponding to the target message meet a preset byte condition; in response to determining that the preset byte condition is met, adding the target message to a target database, and generating a database identifier corresponding to the target message; adding the database identifier to a queue of messages to be sent; and sending the added queue of messages to be sent to a second terminal, wherein the second terminal is a terminal that performs layer operations synchronously with the first terminal.

[0009] Optionally, before determining whether the message bytes corresponding to the target message meet the preset byte conditions, the method further includes: in response to determining that the target message is an ordered message, adding a generated message sequence identifier to the target message to obtain an identifier-added message; and determining the identifier-added message as the target message.

[0010] Optionally, the determining whether the message bytes corresponding to the target message satisfy a preset byte condition comprises: in response to determining that the target message is an unordered message, determining whether the message bytes corresponding to the target message satisfy the preset byte condition.

[0011] Optionally, after determining whether the target message satisfies a preset byte condition, the method further includes: in response to determining that the preset byte condition is not satisfied, adding the target message to a queue of messages to be sent.

[0012] In a second aspect, some embodiments of the present disclosure provide a message sending device, applied to a first terminal, comprising: an acquisition unit, configured to acquire at least one target message, wherein the at least one target message is each message generated by the target user during the layer operation process; a first execution unit, configured to execute a first adding step for each target message of the at least one target message: determining whether the message bytes corresponding to the target message meet a preset byte condition; in response to determining that the preset byte condition is met, adding the target message to a target database, and generating a database identifier corresponding to the target message; adding the database identifier to a queue of messages to be sent; and a sending unit, configured to send the added queue of messages to be sent to a second terminal, wherein the second terminal is a terminal that performs layer operations synchronously with the first terminal.

[0013] Optionally, the first execution unit may be configured to: in response to determining that the target message is an ordered message, add a generated message sequence identifier to the target message to obtain an identifier-added message; and determine the identifier-added message as the target message.

[0014] Optionally, the first execution unit may be configured to: in response to determining that the target message is an out-of-order message, determine whether message bytes corresponding to the target message meet the preset byte condition.

[0015] Optionally, the first execution unit may be configured to: in response to determining that the preset byte condition is not satisfied, add the target message to a queue of messages to be sent.

[0016] In a third aspect, some embodiments of the present disclosure provide a message receiving method, which is applied to a second terminal, comprising: receiving a queue of messages to be sent after being added and sent by a first terminal; for each added message in the queue of messages to be sent after being added, executing a second adding step: in response to determining that the message type corresponding to the added message is a database identification type, obtaining a stored message corresponding to the added message from a target database; adding the stored message to the queue of messages to be received; and displaying a screen of the target user performing a layer operation process according to the queue of messages to be received after being added.

[0017] Optionally, in response to determining that the message type corresponding to the above-mentioned added message is a database identifier type, after obtaining the stored message corresponding to the above-mentioned added message from the target database, the above-mentioned method also includes: in response to determining that the above-mentioned stored message is an ordered message, obtaining the currently determined message sequence identifier as the current message sequence identifier; in response to determining that the message sequence identifier included in the above-mentioned stored message is the next sequence identifier after the above-mentioned current message sequence identifier, removing the message sequence identifier from the above-mentioned stored message to obtain the original message; and determining the above-mentioned first original message as a stored message.

[0018] Optionally, in response to determining that the message type corresponding to the add message is a database identification type, after obtaining the storage message corresponding to the add message from the target database, the method further includes: in response to determining that the message type corresponding to the add message is not the database identification type, determining the add message as a storage message.

[0019] Optionally, in response to determining that the message sequence identifier included in the above-mentioned stored message is the next sequence identifier after the above-mentioned current message sequence identifier, removing the message sequence identifier from the above-mentioned stored message to obtain the original message, the above-mentioned method also includes: in response to determining that the message sequence identifier corresponding to the above-mentioned original message is not the next sequence identifier, adding the above-mentioned original message to the message waiting queue; in response to detecting that the message sequence identifier included in the above-mentioned stored message is the next sequence identifier, determining the original message in the above-mentioned message waiting queue as a stored message, and setting the current message sequence identifier to the message sequence identifier corresponding to the above-mentioned original message.

[0020] Optionally, the adding the stored message to the queue of messages to be received includes: in response to determining that the message is an out-of-order message, adding the stored message to the queue of messages to be received.

[0021] In a fourth aspect, some embodiments of the present disclosure provide a message receiving device, which is applied to a second terminal, comprising: a receiving unit, configured to receive a queue of messages to be sent after being added and sent by the first terminal; a second execution unit, configured to execute a second adding step for each added message in the queue of messages to be sent after being added: in response to determining that the message type corresponding to the added message is a database identification type, obtaining a stored message corresponding to the added message from a target database; adding the stored message to the queue of messages to be received; and a display unit, configured to display a screen of the target user performing a layer operation process according to the queue of messages to be received after being added.

[0022] Optionally, the second execution unit can be configured to: in response to determining that the above-mentioned stored message is an ordered message, obtain the currently determined message sequence identifier as the current message sequence identifier; in response to determining that the message sequence identifier included in the above-mentioned stored message is the next sequence identifier after the above-mentioned current message sequence identifier, remove the message sequence identifier from the above-mentioned stored message to obtain the original message; and determine the above-mentioned first original message as the stored message.

[0023] Optionally, the second execution unit may be configured to: in response to determining that the message type corresponding to the add message is not the database identification type, determine the add message as a storage message.

[0024] Optionally, the second execution unit can be configured to: in response to determining that the message sequence identifier corresponding to the above-mentioned original message is not the next sequence identifier, add the above-mentioned original message to the message waiting queue; in response to detecting that the message sequence identifier included in the above-mentioned stored message is the next sequence identifier, determine the original message in the above-mentioned message waiting queue as a stored message, and set the current message sequence identifier to the message sequence identifier corresponding to the above-mentioned original message.

[0025] Optionally, the second execution unit may be configured to: in response to determining that the message is an out-of-order message, add the stored message to a queue of messages to be received.

[0026] In a fifth aspect, some embodiments of the present disclosure provide an electronic device comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the implementation methods in the first and third aspects.

[0027] In a sixth aspect, some embodiments of the present disclosure provide a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method described in any one of the implementation modes of the first aspect and the third aspect is implemented.

[0028] In a seventh aspect, some embodiments of the present disclosure provide a computer program product, including a computer program, which, when executed by a processor, implements the method described in any one of the implementation modes of the first and third aspects above.

[0029] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the message sending method of some embodiments of the present disclosure, the overall message sending delay can be reduced, and the real-time performance of layer collaboration can be improved. Specifically, the reason for the poor real-time performance is that in the case of a target message with a large message volume, the transmission time is relatively high, so that subsequent messages may be delayed in sending, resulting in poor real-time performance of message sending. Based on this, the message sending method of some embodiments of the present disclosure first obtains at least one target message. Among them, the at least one target message is each message generated by the target user during the layer operation process. Here, by transmitting at least one target message, the second terminal synchronizes the layer operation process in real time. Then, for each target message in the at least one target message, the first adding step is performed: the first step is to determine whether the message bytes corresponding to the target message meet the preset byte condition, so as to determine the message processing method corresponding to the target message according to the size of the message volume. The second step is to add the target message to the target database in response to determining that the preset byte condition is met, and generate a database identifier corresponding to the target message. Here, by means of target database storage and database identifier generation, not only can the message with a large message volume be converted into a small database identifier, but also the target message can be stored in the target database so as to obtain the corresponding message content from the target database using the database identifier. Thus, the problem that the message volume of a single message is large and the transmission time is long can be avoided, and the subsequent messages are delayed in sending, thereby ensuring the real-time nature of message sending. In the third step, the above-mentioned database identifier is added to the queue of messages to be sent, so as to prepare to send the message in the form of a message queue. Finally, the added queue of messages to be sent is sent to the second terminal, so that each information corresponding to at least one target message is sent to the second terminal, so that the second terminal can display the layer operation process in real time according to each information in the queue of messages to be sent. In summary, when the message bytes corresponding to the target message meet the preset byte conditions, the target message is added to the target database and the corresponding database identifier is generated as the sending object, so that the message with a large message volume can be converted into a small database identifier, thereby avoiding the problem that the message volume of a single message is large and the transmission time is long, and the subsequent messages are delayed in sending, thereby ensuring the real-time nature of message sending. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.

[0031] Figure 1 is a schematic diagram of an application scenario of a message sending method according to some embodiments of the present disclosure;

[0032] Figure 2 is a flow chart of some embodiments of the message sending method according to the present disclosure;

[0033] Figure 3 is a flowchart of some other embodiments of the message sending method according to the present disclosure;

[0034] Figure 4 is a flowchart of some embodiments of the message receiving method according to the present disclosure;

[0035] Figure 5 is a schematic diagram of a process of sending and receiving a message according to some embodiments of the message receiving method of the present disclosure;

[0036] Figure 6 is a schematic diagram of the structure of some embodiments of the message sending device according to the present disclosure;

[0037] Figure 7 is a schematic diagram of the structure of some embodiments of the message receiving device according to the present disclosure;

[0038] Figure 8 It is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION

[0039] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0040] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

[0041] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0042] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0043] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0044] With regard to the collection, storage, and use of user personal information (such as target messages) involved in this disclosure, before performing the corresponding operations, the relevant organizations or individuals shall fulfill their obligations, including conducting personal information security impact assessments, fulfilling the obligation to inform the personal information subject, and obtaining the authorization and consent of the personal information subject in advance.

[0045] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0046] Figure 1 It is a schematic diagram of an application scenario of the message sending method according to some embodiments of the present disclosure.

[0047] exist Figure 1 In the application scenario, first, the electronic device 101 can obtain at least one target message 102. Among them, the at least one target message 102 is each message generated by the target user during the layer operation process. Then, for each target message in the at least one target message 102, the electronic device 101 can perform a first adding step: the first step is to determine whether the message bytes corresponding to the target message 1021 meet the preset byte condition. In this application scenario, the target message 1021 can be the target message A. The message bytes corresponding to the target message A are "1mb". The preset byte condition can be that the message bytes are greater than 500Kb. The second step is to add the target message to the target database 104 in response to determining that the preset byte condition is met, and generate a database identifier 103 corresponding to the target message. In this application scenario, the database identifier 103 can be "1921@". The target database 104 can be an OSS database. The third step is to add the database identifier 103 to the queue of messages to be sent 105. Finally, the electronic device 101 can send the added queue of messages to be sent to the second terminal. The second terminal is a terminal that performs layer operations synchronously with the first terminal.

[0048] Continue to refer Figure 2, shows a process 200 of some embodiments of the message sending method according to the present disclosure. The message sending method, applied to a first terminal, comprises the following steps:

[0049] Step 201: Obtain at least one target message.

[0050] In some embodiments, the execution subject of the above message sending method (for example Figure 1 The first terminal 101 shown in the figure can obtain at least one target message through a wired connection or a wireless connection. Among them, the at least one target message is each message generated by the target user during the layer operation process. That is, at least one target message is each message to be transmitted to at least one layer operation synchronization terminal so that each layer operation synchronization terminal synchronously implements the layer operation process. In practice, at least one target message may include: a message for operating a layer, a message for operating an interface mouse, and a message for selecting an area. For example, at least one target message includes: a message that a user creates 2w layers at one time, a message generated by a user moving the mouse, a message generated by a user modifying the coordinates of one of the layers, and a message generated by a user moving the mouse again.

[0051] Step 202: for each target message in the at least one target message, perform a first adding step:

[0052] Step 2021, determining whether the message bytes corresponding to the above target message meet the preset byte conditions.

[0053] In some embodiments, the execution subject may determine whether the message bytes corresponding to the target message meet a preset byte condition. The message bytes may be the byte size occupied by the message content corresponding to the target message. The preset byte condition may be a pre-set condition indicating that the message bytes are greater than the target bytes. The target bytes may be a value obtained based on relevant experiments. For example, the target bytes may be 500Kb.

[0054] In practice, whether the message bytes corresponding to the above target message meet the preset byte conditions can be determined through a registration table in the message sending controller. The registration table includes the preset byte conditions. The message sending controller can be a controller that controls and processes the message during the message sending process.

[0055] It should be noted that after the target message meets the preset byte condition through the message sending controller channel, the target message will be sent to the extended message sending processor to generate a database identifier. The extended message sending processor is used to store the target message that meets the preset byte condition into the target database and generate a database identifier corresponding to the target message.

[0056] In some optional implementations of some embodiments, in response to determining that the target message is an unordered message, the execution subject may determine whether the message bytes corresponding to the target message meet the preset byte conditions. An unordered message may be a message that does not have an order. In practice, an unordered message may be, but is not limited to, one of the following: a mouse operation message, an area selection message.

[0057] In practice, whether the target message is an out-of-order message can be determined by utilizing a message sending controller.

[0058] In some optional implementations of some embodiments, after step 2021, the steps further include:

[0059] In response to determining that the preset byte condition is not met, the execution entity may directly add the target message to a queue of messages to be sent.

[0060] Step 2022: In response to determining that the preset byte condition is met, the target message is added to a target database, and a database identifier corresponding to the target message is generated.

[0061] In some embodiments, in response to determining that the preset byte condition is met, the execution subject may add the target message to the target database, and generate a database identifier corresponding to the target message. The target database may be a database for temporarily storing messages. For example, the target database may be an OSS database. The database identifier may be a message resource identifier corresponding to the target message. The corresponding target message may be obtained from the target database through the database identifier.

[0062] For example, the target message is:

[0063] "Type: LAYER;

[0064] Seqld:1;

[0065] Content: [{id:Ac, prop:x, value: 100}]".

[0066] The corresponding database identifier may be: "Type: OSS, Content: UAC01CDOOOM1". LAYER represents an ordered message, and SELECTION represents an unordered message.

[0067] Step 2023: Add the above database identifier to the queue of messages to be sent.

[0068] In some embodiments, the execution subject may add the database identifier to a queue of messages to be sent. The queue of messages to be sent may be a queue of messages to be sent to at least one layer operation synchronization terminal. The queue of messages to be sent may support adding multiple messages to be sent to the layer operation synchronization terminal through one message channel.

[0069] Step 203: Send the added message queue to be sent to at least one layer operation synchronization terminal.

[0070] In some embodiments, the execution subject may send the added queue of messages to be sent to the second terminal. The second terminal is a terminal that performs layer operations synchronously with the first terminal. The added queue of messages to be sent may be a message queue after adding at least one target message corresponding to at least one information. For example, if the first terminal performs a layer deletion operation on the target object, the corresponding second terminal also needs to perform a layer deletion operation on the target object.

[0071] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the message sending method applied to the first terminal of some embodiments of the present disclosure, the overall message sending delay can be reduced, and the real-time performance of layer collaboration can be improved. Specifically, the reason for the poor real-time performance is that in the case of a target message with a large message volume, the transmission time is relatively high, so that subsequent messages may be delayed in sending, resulting in poor real-time performance of message sending. Based on this, the message sending method applied to the first terminal of some embodiments of the present disclosure first obtains at least one target message. Among them, the at least one target message is each message generated by the target user during the layer operation process. Here, by transmitting at least one target message, the second terminal synchronizes the layer operation process in real time. Then, for each target message in the at least one target message, the first adding step is performed: the first step is to determine whether the message bytes corresponding to the target message meet the preset byte condition, so as to determine the message processing method corresponding to the target message according to the size of the message volume. The second step is to add the target message to the target database in response to determining that the preset byte condition is met, and generate a database identifier corresponding to the target message. Here, by means of target database storage and database identifier generation, not only can the message with a large message volume be converted into a small database identifier, but also the target message can be stored in the target database so as to obtain the corresponding message content from the target database using the database identifier. Thus, the problem that the message volume of a single message is large and the transmission time is long can be avoided, and the subsequent messages are delayed in sending, thereby ensuring the real-time nature of message sending. In the third step, the above-mentioned database identifier is added to the queue of messages to be sent, so as to prepare to send the message in the form of a message queue. Finally, the added queue of messages to be sent is sent to the second terminal, so that each information corresponding to at least one target message is sent to the second terminal, so that the second terminal can display the layer operation process in real time according to each information in the queue of messages to be sent. In summary, when the message bytes corresponding to the target message meet the preset byte conditions, the target message is added to the target database and the corresponding database identifier is generated as the sending object, so that the message with a large message volume can be converted into a small database identifier, thereby avoiding the problem that the message volume of a single message is large and the transmission time is long, and the subsequent messages are delayed in sending, thereby ensuring the real-time nature of message sending.

[0072] Further references Figure 3 , shows a process 300 of another embodiment of the message sending method according to the present disclosure. The message sending method, applied to a first terminal, comprises the following steps:

[0073] Step 301: Obtain at least one target message.

[0074] Step 302: For each target message in the at least one target message, perform a first adding step:

[0075] Step 3021, in response to determining that the target message is an ordered message, adding the generated message sequence identifier to the target message to obtain an identifier-added message.

[0076] In some embodiments, in response to determining that the target message is an ordered message, the execution subject (i.e., the first terminal 101) may add the generated message sequence identifier to the target message to obtain an identifier-added message. The ordered message may be a message that has an order. The message sequence identifier may be an identifier that characterizes the order position of the target message.

[0077] In practice, the message sending controller can be used to determine whether the target message is an ordered message. Similarly, the message sequence identifier can be generated by the Seqld generator in the message sending control. The function of the Seqld generator is to generate an ordered number to ensure that the message receiver can restore the previous message order based on this number. And adding the message sequence identifier to the target message can be performed in the message sending controller.

[0078] Step 3022: determine the message with the identifier added as the target message.

[0079] In some embodiments, the execution entity may determine the identification-added message as a target message.

[0080] Step 3023, determining whether the message bytes corresponding to the above target message meet the preset byte conditions.

[0081] Step 3024, in response to determining that the preset byte condition is met, adding the target message to the target database, and generating a database identifier corresponding to the target message.

[0082] Step 3025: Add the above database identifier to the queue of messages to be sent.

[0083] Step 303: Send the added message queue to be sent to the second terminal.

[0084] In some embodiments, the specific implementation of steps 301, 3023-3025 and 303 and the technical effects thereof can be referred to in Figure 2 Steps 201, 2021-2023 and 203 in the corresponding embodiments are not repeated here.

[0085] from Figure 3 It can be seen that Figure 2 Compared with the description of some corresponding embodiments, Figure 3In the corresponding process 300 of the message sending method in some embodiments, a message sequence identifier is added to the target message content in order, so that the subsequent layer operation synchronization terminal can obtain the ordered messages in sequence according to the message sequence identifier, thereby ensuring the orderliness of the received messages.

[0086] Continue to refer Figure 4 , shows a process 400 of some embodiments of the message receiving method according to the present disclosure. The message receiving method, applied to the second terminal, comprises the following steps:

[0087] Step 401: receiving the added to-be-sent message queue sent by the first terminal.

[0088] In some embodiments, the execution subject of the above message receiving method (ie, the second terminal) can receive the added queue of messages to be sent sent by the first terminal, wherein the second terminal is a terminal that performs layer operation synchronization with the first terminal.

[0089] Step 402: for each added message in the to-be-sent message queue after the above addition, execute the second adding step:

[0090] Step 4021, in response to determining that the message type corresponding to the above-mentioned adding message is a database identification type, obtaining a storage message corresponding to the above-mentioned adding message from the target database.

[0091] In some embodiments, in response to determining that the message type corresponding to the above-mentioned add message is a database identification type, the above-mentioned execution subject can obtain the stored message corresponding to the above-mentioned add message from the target database. The database identification type can indicate that the add message is a database identification, that is, the original message corresponding to the add message satisfies a preset byte condition.

[0092] Here, the message type can be determined by extending the message receiving processor, and the storage information corresponding to the added information can be obtained.

[0093] In some optional implementations of some embodiments, after step 4021, the steps further include:

[0094] In response to determining that the message type corresponding to the add message is a database identification type, the add message is directly added to the queue of messages to be received.

[0095] In some optional implementations of some embodiments, after step 4021, the steps further include:

[0096] In the first step, in response to determining that the stored message is an ordered message, the execution subject may obtain the currently determined message sequence identifier as the current message sequence identifier, wherein the current message sequence identifier may be the message sequence identifier of the last ordered message added to the to-be-received message queue.

[0097] Here, the message receiving controller determines whether it is an ordered message, and determines whether the message sequence identifier is the next sequence identifier after the current message sequence identifier.

[0098] In the second step, in response to determining that the message sequence identifier included in the above-mentioned stored message is the next sequence identifier after the above-mentioned current message sequence identifier, the message sequence identifier is removed from the above-mentioned stored message to obtain the original message. Among them, the message sequence identifier is the next sequence identifier after the above-mentioned current message sequence identifier, which can indicate that the message sequence identifier and the current message sequence identifier are continuous and have a sequential relationship. For example, the message sequence identifier is "003" and the corresponding current message sequence identifier is "002".

[0099] The third step is to determine the first original message as a stored message.

[0100] Optionally, in response to determining that the message sequence identifier included in the stored message is the next sequence identifier after the current message sequence identifier, after removing the message sequence identifier from the stored message to obtain the original message, the method further includes:

[0101] The first step is to add the original message to a message waiting queue in response to determining that the message sequence identifier corresponding to the original message is not the next sequence identifier, wherein the message waiting queue may be a queue corresponding to the waiting message.

[0102] In the second step, in response to detecting that the message sequence identifier included in the above-mentioned stored message is the next sequence identifier, the original message in the above-mentioned message waiting queue is determined as the stored message, and the current message sequence identifier is set to the message sequence identifier corresponding to the above-mentioned original message.

[0103] In some optional implementations of some embodiments, after step 4021, the step further includes: in response to determining that the message type corresponding to the above-mentioned add message is not the above-mentioned database identification type, the above-mentioned execution entity can determine the above-mentioned add message as a storage message.

[0104] Step 4022, adding the above-mentioned stored message to the queue of messages to be received.

[0105] In some embodiments, the execution subject may add the stored message to a queue of messages to be received. The queue of messages to be received may be a queue for receiving messages. That is, the information subsequently written to the queue of messages to be received is the received message.

[0106] In some optional implementations of some embodiments, in response to determining that the message is an out-of-order message, the execution entity may add the stored message to a queue of messages to be received.

[0107] Step 403: display a screen of the target user performing layer operation according to the added queue of messages to be received.

[0108] In some embodiments, the execution subject may utilize message rendering technology to display a screen showing the target user performing layer operations according to the added queue of messages to be received.

[0109] See also Figure 5 , showing the message sending process and the message receiving process.

[0110] like Figure 5 As shown, first, when user A performs the interaction of the design view, at least one target message will be generated. Then, at least one target message is converted into a database identifier through the message sending controller and the extended message sending processor, and at least one content corresponding to the converted at least one target message is added to the queue of messages to be sent. After at least one content has been added to the queue of messages to be sent, client A uses the message service to broadcast the added queue of messages to be sent to each client, such as client B and client C. After client B receives the added queue of messages to be sent, a receiving message queue will be generated through the message receiving controller and the extended message receiving processor. Through the receiving message queue, user B can display the interactive processing content of the corresponding design view on the corresponding client B.

[0111] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the message receiving method of some embodiments of the present disclosure, each message corresponding to the added message queue to be sent can be effectively and quickly received to realize the real-time display of the screen of the image operation process.

[0112] Further references Figure 6 As an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a message sending device, and these device embodiments are Figure 2 Corresponding to the method embodiments shown, the message sending device can be specifically applied to various electronic devices.

[0113] like Figure 6As shown, a message sending device 600 is applied to a first terminal, comprising: an acquisition unit 601, a first execution unit 602 and a sending unit 603. The acquisition unit 601 is configured to acquire at least one target message, wherein the at least one target message is each message generated by the target user during the layer operation process; the first execution unit 602 is configured to perform a first adding step for each target message in the at least one target message: determining whether the message bytes corresponding to the target message meet the preset byte condition; in response to determining that the preset byte condition is met, adding the target message to the target database, and generating a database identifier corresponding to the target message; adding the database identifier to the queue of messages to be sent; and the sending unit 603 is configured to send the added queue of messages to be sent to the second terminal, wherein the second terminal is a terminal that performs layer operation synchronization with the first terminal.

[0114] In some optional implementations of some embodiments, the first execution unit 602 may be further configured to: in response to determining that the target message is an ordered message, add the generated message sequence identifier to the target message to obtain an identifier-added message; and determine the identifier-added message as the target message.

[0115] In some optional implementations of some embodiments, the first execution unit 602 may be further configured to: in response to determining that the target message is an unordered message, determine whether the message bytes corresponding to the target message meet the preset byte conditions.

[0116] In some optional implementations of some embodiments, the first execution unit 602 may be further configured to: in response to determining that the preset byte condition is not satisfied, add the target message to the queue of messages to be sent.

[0117] It is understandable that the units recorded in the message sending device 600 are similar to those in the reference Figure 2 Therefore, the operations, features and beneficial effects described above for the method are also applicable to the message sending device 600 and the units included therein, and will not be described in detail here.

[0118] Further references Figure 7 As an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a message receiving device, and these device embodiments are Figure 4 Corresponding to the method embodiments shown, the message receiving device can be specifically applied to various electronic devices.

[0119] like Figure 7As shown, a message receiving device 700, applied to a second terminal, comprises: a receiving unit 701, a second execution unit 702 and a display unit 703. The receiving unit 701 is configured to receive the added message queue to be sent from the first terminal; the second execution unit 702 is configured to perform a second adding step for each added message in the added message queue to be sent: in response to determining that the message type corresponding to the added message is a database identification type, obtaining a stored message corresponding to the added message from a target database; adding the stored message to the message queue to be received; and the display unit 703 is configured to display a screen of the target user performing a layer operation process according to the added message queue to be received.

[0120] In some optional implementations of some embodiments, the second execution unit 702 can be configured to: in response to determining that the above-mentioned stored message is an ordered message, obtain the currently determined message sequence identifier as the current message sequence identifier; in response to determining that the message sequence identifier included in the above-mentioned stored message is the next sequence identifier after the above-mentioned current message sequence identifier, remove the message sequence identifier from the above-mentioned stored message to obtain the original message; and determine the above-mentioned first original message as the stored message.

[0121] In some optional implementations of some embodiments, the second execution unit 702 may be configured to: in response to determining that the message type corresponding to the add message is not the database identification type, determine the add message as a storage message.

[0122] In some optional implementations of some embodiments, the second execution unit 702 can be configured to: in response to determining that the message sequence identifier corresponding to the above-mentioned original message is not the next sequence identifier, add the above-mentioned original message to the message waiting queue; in response to detecting that the message sequence identifier included in the above-mentioned stored message is the next sequence identifier, determine the original message in the above-mentioned message waiting queue as a stored message, and set the current message sequence identifier to the message sequence identifier corresponding to the above-mentioned original message.

[0123] In some optional implementations of some embodiments, the second execution unit 702 may be configured to: in response to determining that the message is an out-of-order message, add the stored message to a queue of messages to be received.

[0124] It is understandable that the units recorded in the message receiving device 700 are similar to those in the reference Figure 4 Therefore, the operations, features and beneficial effects described above for the method are also applicable to the message receiving device 700 and the units included therein, and will not be described in detail here.

[0125] Reference below Figure 8, which shows a structural schematic diagram of an electronic device 800 suitable for implementing some embodiments of the present disclosure. Figure 8 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0126] like Figure 8 As shown, the electronic device 800 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory 802 or a program loaded from a storage device 808 into a random access memory 803. Various programs and data required for the operation of the electronic device 800 are also stored in the random access memory 803. The processing device 801, the read-only memory 802, and the random access memory 803 are connected to each other via a bus 804. An input / output interface 805 is also connected to the bus 804.

[0127] Typically, the following devices may be connected to the input / output interface 805: an input device 806 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 807 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 808 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 809. The communication device 809 may allow the electronic device 800 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 8 The electronic device 800 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 8 Each block shown in the figure may represent one device, or may represent multiple devices as required.

[0128] In particular, according to some embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from a network through a communication device 809, or installed from a storage device 808, or installed from a read-only memory 802. When the computer program is executed by the processing device 801, the above-mentioned functions defined in the method of some embodiments of the present disclosure are executed.

[0129] It should be noted that the computer-readable medium in some embodiments of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In some embodiments of the present disclosure, the computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0130] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0131] The computer-readable medium may be included in the electronic device; or it may exist independently without being assembled into the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: obtains at least one target message, wherein the at least one target message is each message generated by the target user during the layer operation process; for each target message in the at least one target message, performs a first adding step: determines whether the message bytes corresponding to the target message meet the preset byte condition; in response to determining that the preset byte condition is met, adds the target message to the target database, and generates a database identifier corresponding to the target message; adds the database identifier to the queue of messages to be sent; sends the added queue of messages to be sent to the second terminal, wherein the second terminal is a terminal that performs layer operation synchronization with the first terminal. Receive the added message queue to be sent sent by the first terminal; for each added message in the above-mentioned added message queue to be sent, execute the second adding step: in response to determining that the message type corresponding to the above-mentioned added message is a database identification type, obtain the stored message corresponding to the above-mentioned added message from the target database; add the above-mentioned stored message to the message queue to be received; according to the added message queue to be received, display the screen of the target user performing the layer operation process.

[0132] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0133] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0134] The units described in some embodiments of the present disclosure may be implemented by software or hardware. The units described may also be provided in a processor, for example, may be described as: a processor includes an acquisition unit, a first execution unit, and a sending unit. The names of these units do not, in some cases, constitute limitations on the units themselves, for example, the acquisition unit may also be described as a "unit for acquiring at least one target message".

[0135] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0136] Some embodiments of the present disclosure further provide a computer program product, including a computer program, which implements any of the above-mentioned message sending methods or message receiving methods when executed by a processor.

[0137] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with the technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) and the technical solutions formed.

Claims

1. A message sending method, applied to a first terminal, comprising: Acquire at least one target message, wherein the at least one target message is each message generated by the target user during the layer operation process; For each target message of the at least one target message, performing a first adding step: Determine whether the message bytes corresponding to the target message meet the preset byte conditions; In response to determining that the preset byte condition is met, adding the target message to a target database, and generating a database identifier corresponding to the target message; Adding the database identifier to the queue of messages to be sent; The added queue of messages to be sent is sent to a second terminal, wherein the second terminal is a terminal that performs layer operation synchronization with the first terminal.

2. The method according to claim 1, wherein: Before determining whether the message bytes corresponding to the target message meet the preset byte conditions, the method further includes: In response to determining that the target message is an ordered message, adding the generated message sequence identifier to the target message to obtain an identifier-added message; The identification-added message is determined as a target message.

3. The method according to claim 1, wherein: The determining whether the message bytes corresponding to the target message meet the preset byte conditions includes: In response to determining that the target message is an out-of-order message, it is determined whether a message byte corresponding to the target message satisfies the preset byte condition.

4. The method according to claim 1, wherein: After determining whether the target message meets the preset byte condition, the method further includes: In response to determining that the preset byte condition is not satisfied, the target message is added to a queue of messages to be sent.

5. A message receiving method, applied to a second terminal, comprising: Receiving the added message queue to be sent sent by the first terminal; For each added message in the to-be-sent message queue after the addition, the second adding step is performed: In response to determining that the message type corresponding to the add message is a database identification type, acquiring a stored message corresponding to the add message from a target database; Adding the stored message to a queue of messages to be received; According to the added queue of messages to be received, the screen of the target user performing layer operations is displayed.

6. The method according to claim 5, wherein: After obtaining a stored message corresponding to the add message from the target database in response to determining that the message type corresponding to the add message is a database identification type, the method further includes: In response to determining that the stored message is an ordered message, obtaining a currently determined message sequence identifier as a current message sequence identifier; In response to determining that the message sequence identifier included in the stored message is the next sequence identifier after the current message sequence identifier, removing the message sequence identifier from the stored message to obtain the original message; The first original message is determined as a storage message.

7. The method according to claim 5, wherein: After obtaining a stored message corresponding to the add message from the target database in response to determining that the message type corresponding to the add message is a database identification type, the method further includes: In response to determining that the message type corresponding to the add message is not the database identification type, the add message is determined to be a storage message.

8. The method according to claim 6, wherein: After, in response to determining that the message sequence identifier included in the stored message is the next sequence identifier after the current message sequence identifier, removing the message sequence identifier from the stored message to obtain the original message, the method further includes: In response to determining that the message sequence identifier corresponding to the original message is not the next sequence identifier, adding the original message to a message waiting queue; In response to detecting that the message sequence identifier included in the stored message is the next sequence identifier, the original message in the message waiting queue is determined as a stored message, and the current message sequence identifier is set to the message sequence identifier corresponding to the original message.

9. The method according to claim 5, wherein: The step of adding the stored message to a queue of messages to be received comprises: In response to determining that the message is an out-of-order message, the stored message is added to a queue of messages to be received.

10. A message sending device, applied to a first terminal, comprising: An acquisition unit is configured to acquire at least one target message, wherein the at least one target message is each message generated by the target user during the layer operation process; The first execution unit is configured to perform a first adding step for each target message in the at least one target message: determining whether the message bytes corresponding to the target message meet a preset byte condition; in response to determining that the preset byte condition is met, adding the target message to a target database, and generating a database identifier corresponding to the target message; adding the database identifier to a queue of messages to be sent; The sending unit is configured to send the added message queue to be sent to the second terminal, wherein the second terminal is a terminal that performs layer operation synchronization with the first terminal.

11. A message receiving device, applied to a second terminal, comprising: A receiving unit, configured to receive the added to-be-sent message queue sent by the first terminal; The second execution unit is configured to execute a second adding step for each added message in the to-be-sent message queue after the addition: in response to determining that the message type corresponding to the added message is a database identification type, obtain a stored message corresponding to the added message from a target database; Adding the stored message to a queue of messages to be received; The display unit is configured to display a screen of the target user performing layer operation according to the added queue of messages to be received.

12. An electronic device comprising: one or more processors; a storage device having one or more programs stored thereon, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 9.

13. A computer readable medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

14. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 9.

Images