Message synchronization method and device, electronic equipment and storage medium

Abstract

The invention provides a message synchronization method and device, electronic equipment and a storage medium. The method comprises the following steps: receiving a first message; determining description information of the first message; determining a message synchronization type between the second device and the first device; and based on the description information and the message synchronization type, performing a synchronization operation of the first message to a second device, where the second device shares communication resources with the first device. Therefore, according to the scheme, different message synchronization modes are automatically adapted by determining the message types supported by the first device and the second device, and it is ensured that a user can smoothly receive and display the rich media message on the double terminal devices, so that the compatibility of message synchronization is improved.

Description

Technical Field

[0001] This application relates to the technical fields of information transmission and mobile communication, and in particular to a message synchronization method, apparatus, electronic device and storage medium. Background Technology

[0002] In 5G new communication technology, under the condition that the user's mobile phone number (i.e., the primary number) meets the protocol agreement, the user's mobile phone number is bound to an embedded Subscriber Identity Module (eSIM) terminal device, which is called "one number, two terminals". After binding, the mobile phone is the "primary device" and the eSIM terminal device is the "secondary device". Among them, accessing messages and synchronizing messages on one number and two terminals are the user's basic requirements. Summary of the Invention

[0003] The purpose of this application is to at least partially solve one of the technical problems in the related art.

[0004] Therefore, the first objective of this application is to propose a message synchronization method to enable smooth reception and display of rich media messages on dual-terminal devices, thereby improving the compatibility of message synchronization.

[0005] The second objective of this application is to propose a message synchronization device.

[0006] The third objective of this application is to propose an electronic device.

[0007] The fourth objective of this application is to provide a computer-readable storage medium.

[0008] The fifth objective of this application is to provide a computer program product.

[0009] To achieve the above objectives, a first aspect of this application proposes a message synchronization method, comprising: receiving a first message; determining description information of the first message; determining a message synchronization type between a second device and the first device; and performing a synchronization operation of the first message on the second device based on the description information and the message synchronization type, wherein the second device and the first device share communication resources.

[0010] To achieve the above objectives, a first aspect of this application proposes another message synchronization method, comprising: sending a message synchronization type to a first device, the message synchronization type being used to determine whether a second device supports a first message; receiving a first message synchronized by the first device; wherein the second device shares communication resources with the first device.

[0011] To achieve the above objectives, a second aspect of this application provides a message synchronization device, comprising: a receiving module for receiving a first message; a first determining module for determining description information of the first message; a second determining module for determining a message synchronization type between a second device and the first device; and a synchronization module for performing a synchronization operation of the first message on the second device based on the description information and the message synchronization type, wherein the second device and the first device share communication resources.

[0012] To achieve the above objectives, a second aspect of this application provides another message synchronization device, comprising: a sending module for sending a message synchronization type to a first device, the message synchronization type being used to determine whether a second device supports a first message; and a receiving module for receiving a first message synchronized by the first device; wherein the second device shares communication resources with the first device.

[0013] To achieve the above objectives, a third aspect of this application provides an electronic device, including: a processor; and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to enable the processor to execute the message synchronization method described in the first aspect of the application.

[0014] To achieve the above objectives, a fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, the computer instructions being used to cause the computer to execute the message synchronization method described in the above aspect of the embodiment.

[0015] To achieve the above objectives, a fifth aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the message synchronization method described in the above aspect of the embodiment.

[0016] The message synchronization method, apparatus, electronic device, and storage medium provided in this application receive a first message, determine the description information of the first message, and determine the message synchronization type between the second device and the first device. Therefore, based on the description information and the message synchronization type, a synchronization operation for the first message can be performed on the second device. Thus, this solution automatically adapts to different message synchronization methods by determining the message types supported by the first and second devices, ensuring that users can smoothly receive and display rich media messages on dual-terminal devices, thereby improving the compatibility of message synchronization.

[0017] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0018] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 A flowchart illustrating a message synchronization method provided in an embodiment of this application; Figure 2 A flowchart illustrating another message synchronization method provided in an embodiment of this application; Figure 3 A flowchart illustrating another message synchronization method provided in an embodiment of this application; Figure 4 This is a schematic diagram illustrating the interaction of message fallback synchronization provided in the embodiments of this application; Figure 5 This is an interactive diagram illustrating message synchronization provided in an embodiment of this application. Figure 6 A flowchart illustrating another message synchronization method provided in an embodiment of this application; Figure 7 A flowchart illustrating another message synchronization method provided in an embodiment of this application; Figure 8 A flowchart illustrating another message synchronization method provided in an embodiment of this application; Figure 9 This is an interactive schematic diagram of dual-terminal message security control provided in an embodiment of this application; Figure 10 This is a schematic diagram of the message synchronization process provided in an embodiment of this application; Figure 11 This is a schematic diagram of the structure of a message synchronization device provided in an embodiment of this application; Figure 12 This is a schematic diagram of the structure of a message synchronization device provided in an embodiment of this application. Detailed Implementation

[0019] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0020] The message synchronization method and apparatus of embodiments of this application are described below with reference to the accompanying drawings.

[0021] It should be noted that the message synchronization method proposed in this application is applicable to dual-device communication, where dual-device communication refers to two terminal devices sharing communication resources. For example, dual-device communication includes a first device and a second device, where the first device is a smartphone and the second device is a smartwatch sharing the communication resources of the smartphone.

[0022] It's worth noting that the "one number, two devices" feature can be applied to sports and fitness scenarios. For example, when users are running, swimming, or hiking, they can make and receive calls and send and receive messages through their smartwatch without carrying their phone, avoiding the risk of losing or getting their phone wet. Simultaneously, the watch can monitor data such as heart rate and steps in real time and sync it to the cloud via shared data from the main account. Users can then view the full report directly on their phone after their workout.

[0023] The dual-device feature can also be used in meeting scenarios, such as when the phone is on silent, the watch can receive messages via vibration to avoid missing important calls. It can also be used for location tracking; for example, parents can check the location of their child's watch via their phone and share data for real-time voice calls.

[0024] Based on the message synchronization method proposed in the embodiments of this application, one number for two terminals can also realize collaborative office work among multiple devices. For example, when a user switches between devices such as mobile phones, smartwatches, and tablets, messages (such as SMS, instant messaging, and email) are automatically synchronized without the need for manual transfer.

[0025] While the user is driving, the watch receives critical notifications such as navigation, calls, and text messages, and the phone screen is locked to avoid distractions. When the user is asleep, the phone is silenced at night, and the watch only receives emergency messages (such as calls from family members), ensuring the user's rest is undisturbed.

[0026] Figure 1 This is a flowchart of a message synchronization method provided according to an embodiment of this application, such as... Figure 1 As shown, the message synchronization method of this application embodiment includes, but is not limited to, the following steps: S101, Receive the first message.

[0027] It should be noted that the execution subject of the message synchronization method provided in this application embodiment is a first device, which can be a terminal device. Optionally, the terminal device can be a mobile electronic device or a non-mobile electronic device. For example, a mobile electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc., while a non-mobile electronic device can be a personal computer (PC), television set, etc. This application embodiment does not impose specific limitations.

[0028] In this embodiment, the first device refers to the primary device in a dual-terminal setup, and the second device refers to a secondary device that shares communication resources with the first device, such as a wearable device. For example, if the first device is a smartphone, then the second device is a smartwatch that is linked to the smartphone.

[0029] It should be noted that shared communication resources refer to the first and second devices jointly using or allocating the same set of communication resources during communication to achieve efficient data transmission or collaborative work. These communication resources can be those provided by the operator, such as mobile data traffic, voice call minutes, and SMS messages. Taking voice call minutes as an example, the first and second devices share the call duration; when the second device makes a call, it consumes the first device's call minutes.

[0030] In some embodiments, the first device may receive a first message based on a communication protocol. The first message may be a message sent by another terminal device besides the first and second devices. Optionally, the first device may use a message received from another terminal device as the first message.

[0031] Optionally, the first message can be a 5G message.

[0032] S102, Determine the description information of the first message.

[0033] In some embodiments, by detecting the first message, the message type and message size of the first message can be determined, serving as descriptive information for the first message. That is, the descriptive information includes at least the message type and message size. The message type includes, but is not limited to, 5G messages, 5G message readings, SMS messages, video messages, etc.

[0034] In some embodiments, the message type of the first message can be determined by detecting its message identifier; that is, the message identifier indicates the message type. The message size of the first message can be determined by detecting its field length.

[0035] S103, determine the message synchronization type between the second device and the first device.

[0036] In some embodiments, the message types supported by the second device can be determined, and these message types can be used as the message synchronization type between the second device and the first device. For example, if the message type supported by the second device is 5G message, then the message synchronization type between the second device and the first device is 5G message. As another example, if the message type supported by the second device is SMS, then the message synchronization type between the second device and the first device is SMS.

[0037] In some embodiments, configuration information of the second device can be obtained, and the message synchronization type between the second device and the first device can be determined based on the configuration information of the second device. That is, the configuration information of the second device indicates the message types supported by the second device, so that the message types can be used as the message synchronization type between the second device and the first device.

[0038] S104, based on the description information and message synchronization type, perform a first message synchronization operation on the second device, wherein the second device shares communication resources with the first device.

[0039] In some embodiments, after determining the description information of the first message and the message synchronization type, a synchronization operation of the first message can be performed on the second device to synchronize the first message to the second device.

[0040] In some embodiments, it can be first determined whether the second device supports the first message based on the message synchronization type, and if the first message is supported, the synchronization operation of the first message can be performed on the second device according to the description information.

[0041] In some embodiments, if the second device does not support the first message, the first message can be fallen back to a message type supported by the second device, thereby obtaining a second message that has been fallen back from the first message. Further, according to the description information, a synchronization operation for the second message is performed with the second device.

[0042] In some embodiments, it can be determined whether the second device supports the first message based on the message synchronization type and the message type of the first message in the description information. It is understood that different message types have different message levels.

[0043] In other words, the message type of the first message can indicate the first message level corresponding to the first message, and the message synchronization type can indicate the second message level corresponding to the second message. Then, based on the first message level and the second message level, it can be determined whether the second device supports the first message.

[0044] In some embodiments, it can be determined whether the second message level is greater than or equal to the first message level to determine whether the second device supports the first message. Optionally, if the second message level is greater than or equal to the first message level, it is determined that the second device supports the first message; otherwise, it is determined that the second device does not support the first message.

[0045] In some embodiments, if the second device supports the first message, it can be determined whether the first message needs to be segmented before transmission based on the message size in the description information. Optionally, if the message size is greater than a message size threshold, the first message can be segmented to obtain first message fragments, and the first message fragments can be synchronized with the second device.

[0046] In some embodiments, if the second device does not support the first message, a synchronization operation of the second message segment can be performed on the second device. It can be determined whether the second message needs to be segmented before transmission based on the message size in the description information. Optionally, if the message size is greater than a message size threshold, the second message can be segmented to obtain second message segments, and a synchronization operation of the second message segments can be performed on the second device.

[0047] In the message synchronization method provided in this application embodiment, a first message is received, and the description information of the first message is determined, as well as the message synchronization type between the second device and the first device is determined. Therefore, based on the description information and the message synchronization type, a synchronization operation for the first message is performed on the second device. Thus, this solution automatically adapts to different message synchronization methods by determining the message types supported by the first and second devices, ensuring that users can smoothly receive and display rich media messages on both terminal devices, thereby improving the compatibility of message synchronization.

[0048] Figure 2 This is a flowchart of a message synchronization method provided according to an embodiment of this application, such as... Figure 2 As shown, the message synchronization method of this application embodiment includes, but is not limited to, the following steps: S201, Receive first message.

[0049] S202, Determine the description information of the first message.

[0050] S203, determine the message synchronization type between the second device and the first device.

[0051] In the embodiments of this application, steps S201-S203 can be implemented in any of the embodiments of this application, and no limitation is made here, nor will it be described in detail.

[0052] S204, based on message type and message synchronization type, determine whether the second device supports the first message.

[0053] In some embodiments, it can be determined whether the message synchronization type includes the message type of the first message. If it does, it can be determined that the second device supports the first message; if it does not, it can be determined that the second device does not support the first message.

[0054] In some embodiments, the support of the second device for the first message can be determined based on the message type and message synchronization type message level. For example, the message level of a 5G message is higher than that of an SMS message. If the message type of the first message is a 5G message and the message synchronization type is an SMS message, it can be determined that the second device does not support the first message.

[0055] For example, the message level of 5G message reading is higher than that of SMS. If the message type of the first message is SMS and the message synchronization type is 5G message reading, it can be determined that the second device supports the first message.

[0056] S205, in response to the second device supporting the first message, perform a synchronization operation of the first message to the second device according to the message size and a preset message size threshold.

[0057] In some embodiments, after determining that the second device supports the first message, a synchronization operation can be performed on the first message. Optionally, during the message synchronization process, in order to improve the transmission efficiency of large-volume rich media messages in complex network environments, the synchronization operation of the first message can be performed on the second device according to the message size and a preset message size threshold.

[0058] In some embodiments, it can be determined whether to segment and synchronize the first message based on the message size and a preset message size threshold. Optionally, in response to the message size being greater than the message size threshold, the first message is segmented to obtain a first message fragment, and then the first message fragment is synchronized to the second device.

[0059] In some embodiments, the transmission order and bandwidth corresponding to each first message segment can be dynamically allocated according to the current network status, so that the first message segment can still be effectively transmitted to the second device even in the event of network congestion or unstable signal.

[0060] In some embodiments, the current network state is obtained, and the transmission order and bandwidth of each of the first message segments are determined based on the network state. Further, the first message segments are synchronized with the second device according to the transmission order and bandwidth.

[0061] For example, if the current network condition is good, the first message segments can be synchronized in parallel, that is, the transmission order of each first message segment is the same, and a larger bandwidth is allocated to each message segment for synchronization operation.

[0062] For example, if the current network condition is poor, the transmission order can be determined according to the order of the first message segment in the first message. That is, if the first message segment is earlier in the first message, its corresponding transmission order will be earlier, or if the first message segment is earlier in the first message, its corresponding transmission order will be later. In this way, a smaller bandwidth can be allocated to each message segment for synchronization.

[0063] In some embodiments, the synchronization process of the first message segment can also be monitored in real time. In response to the detection of a synchronization failure of the first message segment, the synchronization operation of the failed first message segment is first performed on the second device, and then the synchronization operation of the remaining message segments is performed on the second device, wherein the remaining message segments refer to the first message segments that have not been synchronized.

[0064] In the message synchronization method provided in this application embodiment, it is determined whether the second device supports the first message. If the second device supports the first message, it is determined whether to segment the first message based on the message size and a preset message size threshold. If the message size is greater than the message size threshold, the first message is segmented to obtain first message fragments, and the first message fragments are synchronized to the second device. By synchronizing the first message after segmentation, the transmission efficiency and continuity of synchronizing large-volume rich media messages in complex network environments can be improved. By introducing a multi-channel parallel transmission mechanism and segmented synchronization, low latency and high reliability of the synchronization process are ensured.

[0065] Figure 3 This is a flowchart of a message synchronization method provided according to an embodiment of this application, such as... Figure 3 As shown, the message synchronization method of this application embodiment includes, but is not limited to, the following steps: S301, receive the first message.

[0066] S302, Determine the description information of the first message.

[0067] S303, Determine the message synchronization type between the second device and the first device.

[0068] S304, based on message type and message synchronization type, determines whether the second device supports the first message.

[0069] In the embodiments of this application, steps S301-S304 can be implemented in any of the embodiments of this application, and no limitation is made here, nor will it be described in detail.

[0070] S305, in response to the second device not supporting the first message, the first message is reverted to obtain the second message.

[0071] In some embodiments, when it is determined that the second device does not support the first message, the second message can be obtained by falling back the first message according to the message synchronization type. That is, the message type of the second message is the same as the message synchronization type, meaning that the second device supports the second message.

[0072] For example, if the first message is a 5G message and the message synchronization type is SMS, then the first message can be reverted to an SMS message as the second message.

[0073] S306, in response to the second message's message size being greater than a message size threshold, the second message is segmented to obtain a second message fragment.

[0074] In some embodiments, during the synchronization process of synchronizing the second message, in order to improve the transmission efficiency of large-volume rich media messages in complex network environments, the second message synchronization operation can be performed on the second device according to the message size and a preset message size threshold.

[0075] In some embodiments, it can be determined whether to segment and synchronize the second message based on the message size and a preset message size threshold. Optionally, if the message size is greater than the message size threshold, it is determined to segment and synchronize the second message, and the second message is then segmented to obtain second message fragments.

[0076] S307, perform synchronization operation on the second message segment to the second device.

[0077] In some embodiments, the transmission order and bandwidth corresponding to each second message segment can be dynamically allocated according to the current network status, so that the second message segment can still be effectively transmitted to the second device even in the event of network congestion or unstable signal.

[0078] In some embodiments, the current network state is obtained, and the transmission order and bandwidth of each of the second message segments are determined based on the network state. Further, synchronization of the second message segments is performed to the second device according to the transmission order and bandwidth.

[0079] For example, if the current network condition is good, the second message segments can be synchronized in parallel, meaning that the transmission order of each second message segment is the same, and a larger bandwidth is allocated to each message segment for synchronization.

[0080] For example, if the current network condition is poor, the transmission order can be determined according to the order of the second message segment in the second message. That is, if the second message segment is earlier in the second message, its corresponding transmission order will be earlier, or if the second message segment is earlier in the second message, its corresponding transmission order will be later. In this way, a smaller bandwidth can be allocated to each message segment for synchronization.

[0081] In other words, for any message segment in the first message segment and the second message segment, performing a synchronization operation on the second device for any message segment may include: obtaining the current network status, determining the transmission order and bandwidth of each message segment based on the network status, and performing a synchronization operation on the second device for any message segment according to the transmission order and bandwidth.

[0082] In some embodiments, the synchronization process of the second message segment can also be monitored in real time. In response to the detection of a second message segment synchronization failure, the synchronization operation of the failed second message segment is performed first on the second device, and then the synchronization operation of the remaining message segments is performed on the second device, wherein the remaining message segments refer to the second message segments that have not been synchronized.

[0083] In some embodiments, to prevent message leakage due to the loss of the second device, the first message or the second message synchronized on the second device can be deleted on the first device. A message deletion command can be sent to the cloud server, instructing the cloud server to delete the first message or the second message from the second device.

[0084] In some embodiments, before synchronizing the first message or the second message to the second device, the second device may be authenticated, and after the second device is authenticated, the synchronization operation of the first message or the second message may be performed based on a secure communication channel.

[0085] In some embodiments, the first message or the second message can be encrypted before synchronization, further ensuring the security of message synchronization.

[0086] In some embodiments, an authentication request can be sent to the second device, and authentication information sent by the second device based on the authentication request can be received. The authentication information includes at least one of the user's biometrics and the device password, thereby enabling the second device to be authenticated based on the authentication information, and establishing a secure communication channel with the second device after the second device is authenticated.

[0087] Furthermore, the first message or the second message can be encrypted based on the key in the first device, and the encrypted first message or the second message can be synchronized to the second device based on a secure communication channel, so as to achieve the security of message synchronization between the first device and the second device and prevent data from being stolen or tampered with.

[0088] In the message synchronization method provided in this application embodiment, it is determined whether the second device supports the first message. If the second device does not support the first message, the first message is recovered to obtain the second message. Based on the message size and a preset message size threshold, it is determined whether to segment the second message. If the message size is greater than the message size threshold, the second message is segmented to obtain second message fragments, and a synchronization operation is performed on the second message fragments to the second device. By synchronizing the second message after segmentation, the transmission efficiency and continuity of synchronizing large-volume rich media messages in complex network environments can be improved. By introducing a multi-channel parallel transmission mechanism and segmented synchronization, low latency and high reliability of the synchronization process are ensured.

[0089] Figure 4 This diagram illustrates the interaction of synchronization after message return. Figure 4 In this system, the first device is the master device, and the second device is the slave device. The master device receives a first message, which is then inspected by a message middleware module to determine its message type and size. The message middleware module further inspects the message synchronization type between the slave and master devices to determine if the slave device supports the first message. If the slave device does not support the first message, it can request the message transmission gateway to perform a fallback of the first message to obtain the second message. The master device then synchronizes the second message with its message synchronization module, allowing the slave device to display the second message and send a message synchronization completion message to the master device.

[0090] Figure 5 The diagram shows the interaction of message synchronization. Figure 5 The first device is the master device, and the second device is the slave device. The master device receives the first message, and the message middleware module detects the first message to determine its message type and size. Figure 4 If the interaction diagram determines that no fallback of the first message is needed, the network switching module determines the current network status. If it determines that there is a single network connection, the multi-channel transmission module synchronizes the first message through a single channel. If it determines that there are multiple network connections, the multi-channel transmission module synchronizes the first message through parallel channels, that is, it segments the first message before synchronization. Furthermore, the synchronized first message is displayed. Optionally, after receiving the synchronized first message from the master device, the slave device can store the first message and send a synchronization completion confirmation message to the master device after storage.

[0091] Figure 6 This is a flowchart of a message synchronization method provided according to an embodiment of this application, such as... Figure 6 As shown, the message synchronization method of this application embodiment includes, but is not limited to, the following steps: S601, Send a message synchronization type to the first device. The message synchronization type is used to determine whether the second device supports the first message.

[0092] It should be noted that the execution subject of the message synchronization method provided in this application embodiment is a second device, which can be a wearable device. Wearable devices may include wrist-worn devices (such as smartwatches and smart bracelets), head-worn devices, foot-worn devices, etc. This application embodiment does not impose specific limitations.

[0093] The second device shares communication resources with the first device.

[0094] In some embodiments, the second device may determine the message synchronization type based on its own configuration information and send the message synchronization type to the first device. Alternatively, the second device may send configuration information to the first device so that the first device can determine the message synchronization type based on the configuration information.

[0095] S602, receive the first message synchronized by the first device.

[0096] In some embodiments, after the second device sends a message synchronization type to the first device, the first device can determine whether the second device supports the first message based on the message synchronization type, and if the second device supports the first message, it can receive the first message synchronized by the first device.

[0097] In some embodiments, it can be determined whether the second device supports the first message based on the message type and message synchronization type of the first message. For example, it can be determined whether the message synchronization type includes the message type of the first message. If it does, it can be determined that the second device supports the first message; if it does not, it can be determined that the second device does not support the first message.

[0098] In some embodiments, the support of the second device for the first message can be determined based on the message type and message synchronization type message level. For example, the message level of a 5G message is higher than that of an SMS message. If the message type of the first message is a 5G message and the message synchronization type is an SMS message, it can be determined that the second device does not support the first message.

[0099] In some embodiments, the second device can receive a first message segment corresponding to a first message synchronized by the first device, and assemble the received first message segment to obtain the first message. After receiving the first message, the device displays the first message.

[0100] In some embodiments, after receiving the first message synchronized by the first device, the second device can also encrypt the first message and store the encrypted first message, thereby improving the security of message storage and preventing information leakage.

[0101] In the message synchronization method provided in this application embodiment, a message synchronization type is sent to a first device so that the first device synchronizes a first message to a second device according to the message synchronization type, thereby enabling the second device to receive the first message synchronized by the first device. Therefore, this solution automatically adapts to different message synchronization methods by determining the message types supported by the first and second devices, ensuring that users can smoothly receive and display rich media messages on both terminal devices, thus improving the compatibility of message synchronization.

[0102] Figure 7 This is a flowchart of a message synchronization method provided according to an embodiment of this application, such as... Figure 7 As shown, the message synchronization method of this application embodiment includes, but is not limited to, the following steps: S701, Send a message synchronization type to the first device. The message synchronization type is used to determine whether the second device supports the first message.

[0103] In the embodiments of this application, step S701 can be implemented in any of the ways described in the embodiments of this application. This is not limited here and will not be described in detail.

[0104] S702, in response to the first message including multiple first message segments, receive the first message segments in the order of transmission of the multiple first message segments.

[0105] In some embodiments, in order to achieve synchronization of the first message under different network conditions, the first device can segment the first message and then synchronize it. That is, the second device can receive multiple first message segments synchronized by the first device, wherein the first message is composed of multiple first message segments.

[0106] In some embodiments, since the synchronization of the first message segment is performed according to the transmission order of the first message segment, the second device can receive the first message segment in the transmission order of the first message segment.

[0107] For example, the first message segment includes segment A, segment B, and segment C, and their respective transmission order is 1, 2, 3, that is, the first transmission segment A, the second transmission segment B, and the third transmission segment C. Then the second device also receives the first message segment in the same transmission order, that is, the first receiving segment A, the second receiving segment B, and the third receiving segment C.

[0108] S703: Assemble the first message segments according to their transmission order to obtain the first message.

[0109] In some embodiments, in order to ensure that the first message can be correctly assembled, the first message segments can be assembled according to the transmission order of the first message segments to obtain the first message.

[0110] Continuing with the example above, the first message segment includes segment A, segment B, and segment C, whose respective transmission order is 1, 2, and 3. They can be assembled in the order of segment A, segment B, and segment C to obtain the first message.

[0111] For example, if the first message segment includes segment A, segment B, and segment C, and their respective transmission orders are 3, 1, and 2, then they can be assembled in the order of segment C, segment A, and segment B to obtain the first message.

[0112] In the message synchronization method provided in this application embodiment, by receiving a first message including multiple first message fragments and assembling the first message fragments to obtain a first message, message synchronization can be achieved under different network conditions, improving the transmission efficiency and continuity of large-volume rich media message synchronization in complex network environments. By introducing a multi-channel parallel transmission mechanism and segmented synchronization, low latency and high reliability of the synchronization process are ensured.

[0113] Figure 8 This is a flowchart of a message synchronization method provided according to an embodiment of this application, such as... Figure 8 As shown, the message synchronization method of this application embodiment includes, but is not limited to, the following steps: S801, Send a message synchronization type to the first device. The message synchronization type is used to determine whether the second device supports the first message.

[0114] In the embodiments of this application, step S601 can be implemented in any of the ways described in the various embodiments of this application. This is not limited here and will not be described in detail.

[0115] S802, receive the second message sent by the first device, the second message being a fallback message of the first message.

[0116] In some embodiments, after sending a message synchronization type to the first device, if the first device determines that the second device does not support the first message, the second device can receive the fallback message of the first message, that is, receive the second message sent by the first device.

[0117] In some embodiments, the second device may also receive multiple second message segments and assemble the second message bands to obtain a second message, thereby improving the efficiency of message synchronization and avoiding delays.

[0118] In some embodiments, in response to the second message including a plurality of second message segments, the second message segments are received in the order of transmission of the plurality of second message segments, and the second message segments are assembled according to the order of transmission of the second message segments to obtain the second message.

[0119] In some embodiments, after receiving the first message or the second message, the second device can also manually delete the first message or the second message. Optionally, in response to the loss of the second device, the second device can receive a message deletion instruction sent by the cloud server. The message deletion instruction is sent by the first device to the cloud server, thereby deleting the first message or the second message in the second device based on the message deletion instruction.

[0120] In some embodiments, before synchronizing the first message or the second message to the second device, device authentication can be performed, and after successful device authentication, the synchronization operation of the first message or the second message can be performed based on a secure communication channel, further ensuring the security of message synchronization.

[0121] In some embodiments, an authentication request is received from a first device, and authentication information is sent to the first device based on the authentication request. The authentication information includes at least one of a user's biometrics and a device password, wherein the authentication information is used to establish a secure communication channel with the first device.

[0122] Furthermore, the encrypted first message or second message synchronized by the first device can be received based on a secure communication channel, and the encrypted first message or second message can be decrypted based on the key in the second device in order to display the first message or second message.

[0123] Furthermore, the decrypted first or second message is subjected to secondary encryption, and the secondary encrypted first or second message is stored.

[0124] Figure 9 This is an interactive diagram illustrating the security control of messages between two terminals. Figure 9 The first device is the master device, and the second device is the slave device. The master device's security authentication module (security authentication module_master) sends an authentication request to the slave device's security authentication module (security authentication module_slave) through a signaling gateway to obtain the second device's authentication information and perform authentication based on that information. Further, the authentication result is sent to the signaling gateway, and after the authentication result indicates that the second device has passed authentication, a secure communication channel is established between the second device and the first device.

[0125] In the message synchronization method provided in this application embodiment, by receiving a second message including multiple second message fragments and assembling the second message fragments to obtain a second message, message synchronization can be achieved under different network conditions, improving the transmission efficiency and continuity of large-volume rich media message synchronization in complex network environments. By introducing a multi-channel parallel transmission mechanism and segmented synchronization, low latency and high reliability of the synchronization process are ensured.

[0126] Figure 10 This is a schematic diagram of the message synchronization process. Figure 10 It includes a message synchronization compatibility enhancement module, a message synchronization transmission optimization module, a device authentication and encryption module, and a management system. The first message is a 5G message.

[0127] Among them, the message synchronization compatibility enhancement module is used to detect the message type and message size of the 5G message when the first device receives the 5G message, obtain the message synchronization type of the second device, and determine whether to perform fallback on the 5G message based on the message synchronization type and message type, so as to adapt the second device to synchronize the 5G message, thereby realizing the synchronization of the 5G message.

[0128] The message synchronization and transmission optimization module detects the current network status and determines whether to segment the 5G message for synchronization based on its size. The 5G message is segmented into multiple message fragments, and the transmission order and bandwidth of each fragment are allocated according to the current network status. A second device can receive these message fragments and assemble them to obtain the final 5G message. Furthermore, an error control mechanism prioritizes retransmitting unsuccessful message fragments when transmission fails, further improving message transmission reliability.

[0129] The device authentication and encryption module is used to authenticate devices, encrypt messages during the synchronization process, establish secure communication channels, and store messages encrypted on a second device.

[0130] The management system is used for message rollback management, network management, and security management during the message synchronization process. By retrieving logs during message synchronization, it can determine whether there are security risks during the synchronization process, and thus take security measures to increase the security of message synchronization.

[0131] Corresponding to the message synchronization methods proposed in the above embodiments, one embodiment of this application also proposes a message synchronization device. Since the message synchronization device proposed in this application corresponds to the message synchronization methods proposed in the above embodiments, the implementation methods of the above message synchronization methods are also applicable to the message synchronization device proposed in this application, and will not be described in detail in the following embodiments.

[0132] To implement the above embodiments, this application also proposes a message synchronization device.

[0133] Figure 11 This is a schematic diagram of a message synchronization device provided in an embodiment of this application.

[0134] like Figure 11 As shown, the message synchronization device 100 includes: Receiver module 101 is used to receive the first message; The first determining module 102 is used to determine the description information of the first message; The second determining module 103 is used to determine the message synchronization type between the second device and the first device; The synchronization module 104 is used to perform a first message synchronization operation with the second device based on the description information and the message synchronization type, wherein the second device and the first device share communication resources.

[0135] In one possible implementation of this application embodiment, the description information includes at least message type and message size. The synchronization module 104 is further configured to: determine whether the second device supports the first message based on the message type and message synchronization type; and, in response to the second device supporting the first message, perform a synchronization operation of the first message to the second device according to the message size and a preset message size threshold.

[0136] In one possible implementation of this application embodiment, the synchronization module 104 is further configured to: in response to a message size greater than a message size threshold, segment the first message to obtain a first message fragment; and perform a synchronization operation on the first message fragment to the second device.

[0137] In one possible implementation of this application embodiment, the synchronization module 104 is further configured to: in response to the second device not supporting the first message, perform fallback on the first message to obtain the second message; in response to the message size of the second message being greater than the message size threshold, segment the second message to obtain the second message fragment; and perform a synchronization operation on the second message fragment to the second device.

[0138] In one possible implementation of this application embodiment, the synchronization module 104 is further configured to: obtain the current network status, and determine the transmission order and bandwidth of each message segment based on the network status; and perform synchronization operation on the second device for each message segment according to the transmission order and bandwidth.

[0139] In the message synchronization device provided in this application embodiment, a first message is received, and the description information of the first message is determined, as well as the message synchronization type between the second device and the first device is determined. Therefore, based on the description information and the message synchronization type, a synchronization operation for the first message is performed on the second device. Thus, this solution automatically adapts to different message synchronization methods by determining the message types supported by the first and second devices, ensuring that users can smoothly receive and display rich media messages on both terminal devices, thereby improving the compatibility of message synchronization.

[0140] Figure 12 This is a schematic diagram of a message synchronization device provided in an embodiment of this application.

[0141] like Figure 12 As shown, the message synchronization device 200 includes: Sending module 201 is used to send a message synchronization type to the first device, and the message synchronization type is used to determine whether the second device supports the first message; The receiving module 202 is used to receive the first message synchronized by the first device; The second device shares communication resources with the first device.

[0142] In one possible implementation of this application embodiment, the receiving module 202 is further configured to: in response to the first message including a plurality of first message segments, receive the first message segments according to the transmission order of the plurality of first message segments; and assemble the first message segments according to the transmission order of the first message segments to obtain the first message.

[0143] In one possible implementation of this application embodiment, the receiving module 202 is further configured to: receive a second message sent by the first device, wherein the second message is a fallback message of the first message.

[0144] In one possible implementation of this application embodiment, the receiving module 202 is further configured to: receive second message segments in accordance with the transmission order of the multiple second message segments in response to the second message including multiple second message segments; and assemble the second message segments according to the transmission order of the second message segments to obtain the second message.

[0145] In the message synchronization device provided in this application embodiment, a message synchronization type is sent to a first device so that the first device synchronizes a first message to a second device according to the message synchronization type, thereby enabling the second device to receive the first message synchronized by the first device. Therefore, this solution automatically adapts to different message synchronization methods by determining the message types supported by the first and second devices, ensuring that users can smoothly receive and display rich media messages on dual-terminal devices, thus improving the compatibility of message synchronization.

[0146] It should be noted that the foregoing explanation of the message synchronization method embodiment also applies to the message synchronization device of this embodiment, and will not be repeated here.

[0147] To implement the above embodiments, this application also proposes an electronic device, including: a processor and a memory communicatively connected to the processor; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory to implement the method provided in the foregoing embodiments. To implement the above embodiments, this application also proposes a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the methods provided in the foregoing embodiments.

[0148] To implement the above embodiments, this application also proposes a computer program product, including a computer program that, when executed by a processor, implements the methods provided in the foregoing embodiments.

[0149] The collection, storage, use, processing, transmission, provision, and application of user personal information involved in this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0150] It should be noted that personal information collected from users should be used for legitimate and reasonable purposes and should not be shared or sold outside of these legitimate uses. Furthermore, such collection / sharing should only be conducted after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement / user notice and sign an agreement / authorization that includes authorization of relevant user information before the user uses the function. In addition, any necessary steps must be taken to protect and safeguard access to such personal information data and ensure that others with access to personal information data comply with their privacy policies and procedures.

[0151] This application is intended to provide an implementation scheme for users to selectively prevent the use or access to their personal information data. Specifically, this application is intended to provide hardware and / or software to prevent or block access to such personal information data. Once personal information data is no longer needed, risks can be minimized by restricting data collection and deleting data. Furthermore, where applicable, such personal information is de-identified to protect user privacy.

[0152] In the foregoing descriptions of the embodiments, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0153] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0154] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0155] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0156] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any of the following techniques known in the art, or a combination thereof: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0157] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0158] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0159] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A message synchronization method, characterized in that, Performed by a first device, the method includes: Receive the first message; Determine the description information of the first message; Determine the message synchronization type between the second device and the first device; Based on the description information and the message synchronization type, the first message is synchronized with the second device, wherein the second device shares communication resources with the first device.

2. The method according to claim 1, characterized in that, The description information includes at least the message type and message size. The step of synchronizing the first message with the second device based on the description information and the message synchronization type includes: Based on the message type and the message synchronization type, determine whether the second device supports the first message; In response to the second device supporting the first message, a synchronization operation for the first message is performed with the second device based on the message size and a preset message size threshold.

3. The method according to claim 2, characterized in that, The step of synchronizing the first message with the second device according to the message size and a preset message size threshold includes: In response to the message size being greater than the message size threshold, the first message is segmented to obtain a first message fragment; The first message segment is synchronized with the second device.

4. The method according to claim 3, characterized in that, The method further includes: In response to the fact that the second device does not support the first message, the first message is reverted to obtain the second message; In response to the second message's message size being greater than the message size threshold, the second message is segmented to obtain a second message fragment; Perform the synchronization operation of the second message segment to the second device.

5. The method according to claim 3 or 4, characterized in that, For any message segment in the first message segment and the second message segment, perform a synchronization operation on the second device for that message segment, including: Obtain the current network status, and determine the transmission order and bandwidth of each message segment based on the network status; Synchronization of any message segment is performed on the second device according to the transmission order and bandwidth.

6. A message synchronization method, characterized in that, Performed by a second device, the method includes: Send a message synchronization type to the first device, the message synchronization type being used to determine whether the second device supports the first message; Receive the first message synchronized by the first device; The second device shares communication resources with the first device.

7. The method according to claim 6, characterized in that, The receiving of the first message synchronized by the first device includes: In response to the first message including a plurality of first message segments, the first message segments are received in the transmission order of the plurality of first message segments; The first message segments are assembled according to their transmission order to obtain the first message.

8. The method according to claim 6, characterized in that, The receiving of the first message synchronized by the first device includes: Receive a second message sent by the first device, wherein the second message is a fallback message of the first message.

9. The method according to claim 8, characterized in that, The receiving of the second message sent by the first device includes: In response to the second message including a plurality of second message segments, the second message segments are received in the transmission order of the plurality of second message segments; The second message is obtained by assembling the second message segments according to their transmission order.

10. A message synchronization device, characterized in that, Suitable for a first device, the apparatus includes: The receiving module is used to receive the first message; The first determining module is used to determine the description information of the first message; The second determining module is used to determine the message synchronization type between the second device and the first device; A synchronization module is used to perform a synchronization operation of the first message to the second device based on the description information and the message synchronization type, wherein the second device and the first device share communication resources.

11. A message synchronization device, characterized in that, Suitable for a second device, the device comprising: A sending module is used to send a message synchronization type to a first device, wherein the message synchronization type is used to determine whether the second device supports the first message; The receiving module is used to receive the first message synchronized by the first device; The second device shares communication resources with the first device.

12. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-9.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-9.

14. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-9.

Images