Memory synchronous storage management method and device, equipment and storage medium

Abstract

The invention provides a memory synchronous storage management method and device, equipment and a storage medium, and belongs to the technical field of data synchronous storage, and the method comprises the steps that when it is detected that a user updates first memory data through first equipment, a data popularity label and updated second memory data are obtained; if the data label is a hot data label, the incremental data packet is extracted to update local data of the first device, a target synchronization protocol is determined based on a device operation state to push the incremental data packet to a cloud edge node, the node updates a cache copy and pushes the cache copy to an associated second device, and the second device feeds back a synchronization state after storage; and if the first equipment is a cold data label, caching second memory data, updating a cold data index of the first equipment, compressing the second memory data to generate a compressed data packet, pushing the compressed data packet and an index entry to a cloud edge node, and updating cloud archiving storage area data and a cloud cold data index by the node. Stable synchronization of multi-device data can be achieved, and the resource utilization rate is increased.

Description

Technical Field

[0001] This application belongs to the field of data synchronization storage technology, and more specifically, relates to memory synchronization storage management methods, devices, equipment, and storage media. Background Technology

[0002] Memory data refers to data created by users on electronic devices that needs to be retained and reused, including but not limited to text or structured information such as memos, to-do lists, and schedules. With the popularization of mobile internet and multi-device collaboration scenarios, users often manage memory data through multiple electronic devices, which places higher demands on the real-time performance of cross-device data synchronization, resource utilization, and storage costs.

[0003] Currently, existing technologies for synchronous storage management of memory data mainly employ two methods: full synchronization and fixed protocol synchronization. Full synchronization transmits the updated full data to other devices during data updates to achieve data consistency; fixed protocol synchronization uses a preset fixed communication protocol to complete data synchronization. However, these solutions have drawbacks: firstly, existing technologies do not make efficient use of data transmission and storage resources for full synchronization of memory data, leading to resource waste; secondly, fixed protocol synchronization suffers from poor stability, and data consistency after synchronization across multiple devices is difficult to guarantee, impacting user experience.

[0004] Therefore, there is an urgent need for an optimized memory synchronization storage management method to solve the problems of low resource utilization and poor synchronization stability in existing technologies. Summary of the Invention

[0005] The purpose of this application is to provide a memory synchronization storage management method, apparatus, device, and storage medium to achieve stable data synchronization across multiple devices and improve resource utilization.

[0006] A first aspect of this application provides a memory synchronization storage management method, including: In response to detecting that a user updates the first memory data through the first device, the system obtains the heat tag of the first memory data and the second memory data; the heat tag is determined based on the user's behavioral data on the memory data, and the second memory data refers to the first memory data updated by the user. If the heat tag of the first memory data is a hot data tag, then incremental extraction is performed on the second memory data to obtain an incremental data packet; the first memory data stored in the first device is updated based on the incremental data packet; the target synchronization protocol is determined based on the current operating status of the first device, and the incremental data packet is pushed to the cloud edge node based on the target synchronization protocol; the cloud edge node is used to update the cached copy of the first memory data based on the incremental data packet, and push the incremental data packet to the second device associated with the user; the second device is used to store the incremental data packet and report the synchronization completion status to the cloud edge node; If the hot data label of the first memory data is a cold data label, then the second memory data is cached; an index entry is generated based on the second memory data, and the cold data index entry stored on the first device is updated based on the index entry; the second memory data is compressed to obtain a compressed data package, and the compressed data package and index entry are pushed to the cloud edge node; the cloud edge node is also used to update the first memory data stored in the cloud archive storage area based on the compressed data package, and to update the cold data index entry stored on the cloud edge node based on the index entry.

[0007] A second aspect of this application provides a memory synchronization storage management device, comprising: The update operation detection module is used to respond to the detection that a user has performed an update operation on the first memory data through the first device, and to obtain the heat label of the first memory data and the second memory data; the heat label is determined based on the user's behavior data on the memory data, and the second memory data refers to the first memory data after the user updates it; The hot data synchronization storage module is used to incrementally extract the second memory data to obtain an incremental data packet if the heat tag of the first memory data is a hot data tag; update the first memory data stored in the first device based on the incremental data packet; determine the target synchronization protocol based on the current operating status of the first device; and push the incremental data packet to the cloud edge node based on the target synchronization protocol; the cloud edge node is used to update the cached copy of the first memory data based on the incremental data packet and push the incremental data packet to the second device associated with the user; the second device is used to store the incremental data packet and report the synchronization completion status to the cloud edge node; The cold data storage management module is used to cache the second memory data if the heat tag of the first memory data is a cold data tag; generate index entries based on the second memory data; update the cold data index entries stored on the first device based on the index entries; compress the second memory data to obtain a compressed data package; and push the compressed data package and index entries to the cloud edge node; the cloud edge node is also used to update the first memory data stored in the cloud archive storage area based on the compressed data package, and to update the cold data index entries stored on the cloud edge node based on the index entries.

[0008] A third aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the steps of the memory synchronization storage management method described above.

[0009] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the memory synchronization storage management method described above.

[0010] The beneficial effects of the memory synchronization storage management method, apparatus, device, and storage medium provided in this application are as follows: This application's embodiments differentiate data priorities using popularity tags. For frequently used "hot" data, only the modified portions are extracted to generate incremental data packets, rather than transmitting the complete data, thereby reducing bandwidth consumption and saving traffic and synchronization time. For infrequently used "cold" data, only index information such as titles and tags is stored locally, while the complete content is compressed and stored in the cloud to avoid occupying device storage space. At the same time, compressed transmission reduces bandwidth consumption, fundamentally improving resource utilization.

[0011] This application's embodiments dynamically select the synchronization protocol based on the device status, avoiding synchronization failures caused by insufficient compatibility with fixed protocols and improving synchronization stability. Hot data is distributed in incremental packets in real time through cloud edge nodes closer to the user, and the status is promptly reported after synchronization by associated devices to ensure no data is missed during synchronization; the index and compressed content of cold data are synchronized to the cloud, and each device obtains the latest version when accessing it, solving the problem of data inconsistency among multiple devices.

[0012] In summary, the data synchronization of the embodiments of this application is more resource-efficient and stable, ensuring that data from multiple devices remains consistent and reducing issues such as wasted bandwidth, synchronization lag, or data conflicts. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 A schematic flowchart of a memory synchronization storage management method provided in an embodiment of this application; Figure 2 A structural block diagram of a memory synchronization storage management device provided in an embodiment of this application; Figure 3 This is a schematic block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0015] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0016] It is understood that in the embodiments of this application, data such as user information are involved. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with relevant laws, regulations and standards.

[0017] It should be noted that the terms "first," "second," etc., used in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in sequences other than those illustrated or described herein.

[0018] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a memory synchronization storage management method provided in an embodiment of this application. The method can be executed by an electronic device, and specifically, the method may include S101 to S103.

[0019] S101: In response to detecting that a user updates the first memory data through the first device, obtain the heat label of the first memory data and the second memory data; the heat label is determined based on the user's behavior data on the memory data, and the second memory data refers to the first memory data updated by the user.

[0020] In this embodiment, the first device refers to an electronic device, such as a mobile phone or computer, from which the user initiates a memory data update operation. The first memory data refers to the user's original memory data to be updated. The update operation refers to operations performed by the user on the first memory data, such as modification, addition, or deletion. The second memory data refers to the latest memory data obtained after the update operation. Behavioral data refers to data such as the frequency of the user's access to the memory data, the frequency of modification, and the time of the most recent operation.

[0021] This embodiment detects user update operations to capture the latest data status in real time, ensuring data integrity and real-time synchronization. Based on user behavior data, this embodiment determines popularity tags, distinguishing data access priorities and avoiding resource waste or inefficiency issues caused by traditional unified synchronization strategies. Simultaneously, this embodiment simultaneously acquires popularity tags and secondary memory data, providing crucial information for adapting different synchronization schemes to hot and cold data, ensuring the targeting and effectiveness of the synchronization strategy, thereby improving resource utilization and user experience.

[0022] For example, a user opens a schedule management application on a tablet (i.e., the first device) and adjusts their stored travel plans for next month (i.e., the first memory data). The tablet's application background detects this adjustment and determines it as an update operation. The tablet can obtain the user's adjusted itinerary information in real time and integrate it to generate the second memory data. Simultaneously, the tablet can obtain the popularity tag of the first memory data. This popularity tag is obtained by the tablet based on the historical behavioral data of the first memory data, according to preset popularity judgment rules, and by comprehensively evaluating the extracted behavioral data. The historical behavioral data may include the number of visits in the past 30 days, the frequency of modification, and the time of the most recent operation. Assuming the first memory data has been visited 10 times and modified 3 times in the past 30 days, meeting the hot data judgment threshold, the popularity tag is determined to be a hot data tag; if the data has only been visited once in the past 30 days and has no historical modification records, the popularity tag is determined to be a cold data tag.

[0023] S102: If the heat tag of the first memory data is a hot data tag, then incremental extraction is performed on the second memory data to obtain an incremental data packet; the first memory data stored in the first device is updated based on the incremental data packet; the target synchronization protocol is determined based on the current operating status of the first device, and the incremental data packet is pushed to the cloud edge node based on the target synchronization protocol; the cloud edge node is used to update the cached copy of the first memory data based on the incremental data packet, and push the incremental data packet to the second device associated with the user; the second device is used to store the incremental data packet and report the synchronization completion status to the cloud edge node.

[0024] In this embodiment, incremental extraction is performed on the second memory data to obtain an incremental data packet. Specifically, this includes: obtaining the changed fields between the second memory data and the first memory data, and generating an incremental data packet carrying a data ID, changed fields, modification timestamp, and verification hash value.

[0025] In this embodiment, the target synchronization protocol is determined based on the current operating state of the first device, and incremental data packets are pushed to the cloud edge node based on the target synchronization protocol. Specifically, if the first device is in the foreground running state, the target synchronization protocol is determined to be Web Socket, and incremental data packets are pushed to the cloud edge node through Web Socket; if the first device is in the background running state and / or in a low power state, the target synchronization protocol is determined to be MQTT, and incremental data packets are pushed to the cloud edge node through MQTT.

[0026] In this embodiment, there is at least one second device, and the storage of incremental data packets is achieved by the second device in the following manner: For each second device, if the second device is in the foreground state, the incremental data packets are stored in the hot data storage area of ​​the second device; if the second device is in the background state, the incremental data packets are cached, and when the second device is woken up, the cached incremental data packets are stored in the hot data storage area of ​​the second device.

[0027] In this embodiment, incremental extraction refers to the process of extracting only the differences between the second memory data and the first memory data. The change field refers to the specific content added, modified, or deleted in the second memory data relative to the first memory data. The incremental data packet refers to the data packet used to synchronize updated data content. The data ID refers to the encoded information used to uniquely identify the memory data. The modification timestamp refers to the specific time information recording the completion of the update operation of the second memory data. The check hash value refers to the characteristic information used to verify the integrity of the incremental data packet during transmission and prevent data tampering. The current running state refers to the working state of the first device during data synchronization, such as foreground running state, background running state, and low battery state. The target synchronization protocol refers to the communication protocol selected based on the current running state of the first device for transmitting incremental data packets. WebSocket is a high-efficiency real-time communication protocol suitable for the foreground running state. MQTT is a low-power communication protocol suitable for the background running state and low battery state. The foreground running state refers to the state where the first device is directly operated by the user and the application is actively displayed. The background running state refers to the state where the first device is not directly operated by the user and the application resides in the background. The low battery state refers to the state where the remaining battery power of the first device is lower than a preset battery threshold (e.g., 20%). The hot data storage area refers to a dedicated storage area in the second device used to store hot data tag memory data. Cache refers to the operation of temporarily storing incremental data packets when the second device is in the background. Wake-up refers to the second device switching from a background running state to an active state where it can be operated by the user.

[0028] The core objective of this embodiment is to construct an efficient, adaptable, and stable synchronous storage system based on the characteristics of high-frequency access and high real-time requirements of hot data. This embodiment uses incremental extraction to transmit only changed fields, avoiding the resource waste of full data transmission and improving synchronization efficiency; verification hash values ​​ensure data transmission integrity. This embodiment dynamically selects the synchronization protocol based on device operating status, using WebSocket to meet the real-time requirements of the foreground scenario and MQTT to reduce power consumption and interruption risks in the background and low-power scenarios. This embodiment synchronizes cloud edge nodes to shorten transmission distances and ensure low latency for hot data synchronization; the second device stores memory data in different states, ensuring timely updates to the foreground state and no missed updates to the background state, ultimately achieving high efficiency, stability, and consistency in multi-device hot data synchronization, meeting users' needs for high-frequency data.

[0029] For example, a user uses a mobile phone as the first device to open an office application and modify a project plan (i.e., the first memory data) that has been marked as hot data. The user adds three task assignments to the document. After the application background detects the update operation and obtains the second memory data, it starts the hot data synchronization process.

[0030] The phone compares the second memory data with the first memory data field by field, identifies the three newly added task assignments as a change field, and generates an incremental data packet. This packet contains the unique data ID corresponding to the memory data, the three newly added task assignments change field, the modification timestamp recording the current modification time, and a verification hash value calculated based on the change field and the data ID, ensuring that the data packet is complete and tamper-proof.

[0031] The phone integrates the changed fields in the incremental data packet into the first memory data stored locally, overwriting the old version content. This ensures that the data stored locally on the first device is updated to the second memory data in real time, guaranteeing that the user will access the latest version on the first device in the future.

[0032] The mobile phone can determine the current operating status of the first device and select the target synchronization protocol. If the phone screen is on, the office application is displayed in the foreground, and the user is still performing subsequent operations (i.e., in the foreground running state), then the target synchronization protocol is determined to be Web Socket. The phone can establish a long-term connection with the cloud edge node deployed in the user's frequently used region via the Web Socket protocol, quickly pushing incremental data packets to that node. If the user switches to other applications after making modifications, the office application is pushed to the background, the phone screen is on but the application is not directly operated (i.e., in the background running state), or the phone's remaining battery is only 15% or less than the preset threshold of 20% (in a low battery state), then the target synchronization protocol is determined to be MQTT. The phone can establish a low-power connection via the MQTT protocol, ensuring connection persistence while smoothly pushing incremental data packets to the cloud edge node, avoiding rapid power consumption or transmission interruption caused by high-power protocols.

[0033] After receiving the incremental data packet, the cloud edge node first verifies the integrity of the data packet by checking the hash value. Once confirmed to be correct, it updates the copy of the first-memory data in the node cache based on the changed fields and data ID, ensuring that the edge node stores the latest version. The cloud edge node then queries the list of second devices associated with the user, finding two online devices—a tablet and a laptop—and pushes the incremental data packet to both of them.

[0034] For a tablet as a secondary device, assuming the user is currently browsing the web while the office application is in the background, the tablet can activate a caching mechanism upon receiving the incremental data packet. This mechanism temporarily stores the incremental data packet in the local temporary storage area and marks it as pending. When the user subsequently opens the office application on the tablet, waking it from the background, the storage process is immediately triggered. The cached incremental data packet is retrieved and stored in the tablet's hot data storage area. Simultaneously, the tablet integrates the changed fields into the original locally stored first-memory data, completing the update.

[0035] For the laptop as a secondary device, assuming the user is currently viewing the project plan in an office application and the device is in the foreground, after receiving the incremental data packet, the tablet can directly store it in the hot data storage area and immediately merge the changed fields into the first memory data in local storage. The user can see the three newly added task assignments without manually refreshing.

[0036] After the tablet and laptop complete storage and updates, they report the synchronization completion status to the cloud edge node. The cloud edge node records the synchronization results of each device, forming a complete synchronization loop to ensure that all associated secondary devices are synchronized to the latest data.

[0037] This embodiment improves data synchronization efficiency and resource utilization through its synchronous storage design for hot data tags. Incremental extraction transmits only changed fields, reducing bandwidth consumption and synchronization time. The dynamically adaptable synchronization protocol ensures real-time performance in the foreground while reducing power consumption and interruption risks in the background and low-power scenarios. Cloud edge nodes shorten transmission latency, second-device state-based storage prevents data loss, and hash value verification ensures data integrity. After synchronization across multiple devices, all devices can obtain the latest data, solving the problems of resource waste, poor stability, and insufficient consistency in traditional synchronization solutions, thus improving the user experience for high-frequency data.

[0038] S103: If the hot data label of the first memory data is a cold data label, then the second memory data is cached; an index entry is generated based on the second memory data, and the cold data index entry stored in the first device is updated based on the index entry; the second memory data is compressed to obtain a compressed data packet, and the compressed data packet and the index entry are pushed to the cloud edge node; the cloud edge node is also used to update the first memory data stored in the cloud archive storage area based on the compressed data packet, and to update the cold data index entry stored in the cloud edge node based on the index entry.

[0039] In this embodiment, after pushing the compressed data packet and index entries to the cloud edge node, the method further includes: If a user access operation for the second memory data is detected, a data access request is sent to the cloud edge node so that the cloud edge node can extract the compressed data packet from the archive storage area and send it to the first device; Receive and decompress compressed data packets.

[0040] In this embodiment, after pushing the compressed data packet and index entry to the cloud edge node, the cloud edge node is further configured to: if it detects that a user accesses the second memory data through the target device, extract the compressed data packet from the archive storage area of ​​the cloud edge node and push the compressed data packet to the target device; the target device is any one of the first device and all the second devices.

[0041] In this embodiment, an index entry refers to an entry containing key data identification information used for quickly locating cold data. For example, an index entry may include a data ID, data title, core semantic tags, creation timestamp, latest modification timestamp, and data source identifier. A cold data index entry refers to an entry in the first device specifically storing cold data tags, memory data, and index information. A cloud archive storage area refers to a low-cost storage area in the cloud specifically used for long-term storage of cold data tag memory data. A target device refers to the device on which the user initiates a second memory data access operation, which can be the first device or any second device.

[0042] The core objective of this embodiment is to achieve a balance between efficient resource utilization and secure data retention, taking advantage of the low access frequency and long-term retention characteristics of cold data. For cold data, only the index entries are stored locally, avoiding the consumption of local storage resources by the complete data. The complete data is compressed before storage and transmission, reducing bandwidth and cloud storage costs. Cloud edge nodes act as relays, ensuring both synchronous updates of the index and compressed data packets and rapid data retrieval upon user access. This embodiment can push compressed data packets on demand when a user accesses the data, avoiding meaningless real-time distribution of cold data and further saving resources. At the same time, the cloud archive storage area ensures the long-term secure retention of cold data, meeting the user's subsequent access needs.

[0043] For example, a user uses their mobile phone as the first device to open a notes application and supplement and modify a travel note from six months ago, which is marked as cold data, i.e., the first memory data, by adding detailed descriptions of the attractions at that time. After the application background detects the update operation and obtains the second memory data, it starts the cold data synchronization process.

[0044] The first device caches the second memory data, temporarily retaining the complete content for subsequent operations. Based on the second memory data, the first device generates an index entry containing key information such as the data ID, travel note title, core tags, and the latest modification timestamp. The first device then uses this index entry to overwrite the corresponding cold data index entry originally stored locally, completing the local index update.

[0045] The first device can use a high compression ratio algorithm to compress the second memory data, generating a compressed data packet to reduce the data size. The first device then pushes the compressed data packet along with the updated index entries to the cloud edge node via a low-priority transmission channel.

[0046] After receiving the compressed data packet and index entries, the cloud edge node first verifies the data integrity. Once confirmed to be correct, it transmits the compressed data packet to the cloud archive storage area, overwriting the original cold data corresponding to the data ID, thus completing the full data update in the cloud. Simultaneously, the cloud edge node updates its own stored corresponding cold data index entries with the received new index entries, ensuring consistency between the cloud index and the local index.

[0047] At some point later, the user, using a tablet as the target device, searches for the travel notes in a notes application. The application triggers an access request and sends it to the cloud edge node. Upon detecting this access operation, the cloud edge node retrieves the corresponding compressed data packet from the cloud archive storage area and pushes the compressed data packet to the tablet using a transmission protocol adapted to the tablet's current state. After receiving the compressed data packet, the tablet decompresses it to obtain the complete content of the second memory data, which the user can then view or further manipulate. This entire process saves overall storage and bandwidth resources while ensuring availability when the user accesses cold data.

[0048] As can be seen from the above, this embodiment distinguishes data priorities by using popularity tags. For frequently used hot data, only the modified parts are extracted to generate incremental data packets, rather than transmitting the complete data, in order to reduce bandwidth consumption and save traffic and synchronization time. For infrequently used cold data, only index information such as titles and tags is stored locally, while the complete content is compressed and stored in the cloud to avoid occupying device storage space. At the same time, compressed transmission reduces bandwidth consumption, thereby improving resource utilization from the root.

[0049] This embodiment dynamically selects the synchronization protocol based on the device status, avoiding synchronization failures caused by insufficient compatibility of a fixed protocol and improving synchronization stability. Hot data is distributed in incremental packets in real time through cloud edge nodes closer to the user, and the status is promptly reported after the associated devices are synchronized, ensuring that no data is missed during synchronization; the index and compressed content of cold data are synchronized to the cloud, and each device obtains the latest version when accessing it, solving the problem of data inconsistency among multiple devices.

[0050] In summary, the data synchronization in this embodiment is more resource-efficient and stable, ensuring consistent data across multiple devices and reducing issues such as wasted bandwidth, synchronization lag, or data conflicts.

[0051] In one embodiment of this application, the memory synchronization storage management method further includes: In response to receiving user input information, generate user input text based on the user input information, and generate a first semantic label based on the user input text; Obtain the second semantic tag corresponding to each of the high-frequency operation data, and calculate the matching degree between the first semantic tag and each second semantic tag respectively; high-frequency operation data refers to the memory data whose heat tag is the hot data tag; If at least one second semantic tag has a matching degree greater than the matching degree threshold with the first semantic tag, then the heat tag of the user input text is determined to be a hot data tag. If the matching degree between each of the second semantic tags and the first semantic tag is not greater than the matching degree threshold, then the hot tags of the user input text are determined to be cold data tags. Target memory data is generated based on the first semantic tag, popularity tag, and user input text; Target memory data is stored based on popularity tags.

[0052] In this embodiment, generating user input text based on user input information specifically includes: If the user input is voice information, the voice information is recognized to obtain text information, and the text information is preprocessed to obtain the user input text. If the user input is text, then the text is preprocessed to obtain the user input text.

[0053] In this embodiment, the target memory data is stored based on heat tags, specifically including: If the heat tag is a hot data tag, the target memory data is stored in the hot data storage area of ​​the first device; the target memory data is pushed to the cloud edge node, which is also used to cache the target memory data to obtain a copy of the cached target memory data; If the heat tag is a cold data tag, then a target index entry is generated based on the target memory data, and the target index entry is stored in the cold data index storage area of ​​the first device; the target memory data is cached; the target memory data is compressed to obtain a target compressed data package, and the target compressed data package and the target index entry are pushed to the cloud edge node; the cloud edge node is also used to store the target compressed data package in the cloud archive storage area of ​​the cloud edge node; the cloud edge node is also used to update the cold data index entries stored in the cloud edge node based on the target index entries.

[0054] In this embodiment, user input information refers to the original information input by the user through the first device that requires memory retention, such as text input and voice input. User input text refers to standardized text data generated based on the conversion / preprocessing of user input information, such as voice input after text conversion. The first semantic tag is used to characterize the theme, purpose, and other features of the text. High-frequency operation data refers to memory data with a heat label as a hot data label, that is, data whose user access or modification frequency is higher than a preset threshold. The second semantic tag refers to the semantic identifier corresponding to each high-frequency operation data, which is consistent with the dimension of the first semantic tag. The matching degree is used to quantify the semantic correlation between the first semantic tag and the second semantic tag. The matching degree threshold refers to the numerical standard for judging whether the semantic matching is qualified based on experience. The target index entry refers to the index entry containing the key identification information of the target memory data, used for cold data location.

[0055] The cold data index storage area only retains location credentials for cold data, avoiding the use of local storage resources for the complete content. It also allows users to quickly search the cold data index and retrieve the complete content from the cloud as needed. The cold data index storage area can use ordinary local storage media on the device, with low read / write speed requirements, only needing to meet the needs of fast index entry lookup and updates, resulting in low storage costs. The hot data storage area ensures local, instant access and rapid modification of hot data (high-frequency access, high real-time requirements), avoiding reliance on cloud transmission and improving the user experience. The hot data storage area can use high-speed local storage media on the device (such as a combination of flash memory and RAM cache), with fast read / write speeds, supporting millisecond-level access and real-time updates, adapting to high-frequency operation needs.

[0056] Low-priority transmission channels refer to communication transmission links specifically used for transmitting cold data (such as compressed data packets and index entries). Their transmission priority is lower than that of high-priority transmission channels for hot data, and they are primarily suited to the needs of cold data with low access frequency and non-real-time synchronization. Low-priority transmission channels feature off-peak transmission, low bandwidth consumption, and low power consumption. They can dynamically avoid peak network periods or hot data transmission peaks, and the transmission rate can be flexibly adjusted according to network resource conditions, without preempting the bandwidth and device resources required for hot data synchronization. Simultaneously, low-priority transmission channels employ a lightweight transmission mechanism to reduce power consumption of devices in the background or at low battery levels, ensuring transmission stability. The core design principle of low-priority transmission channels is to achieve reliable transmission of cold data without affecting the real-time synchronization efficiency of hot data, balancing resource optimization and data synchronization integrity, and adapting to use cases where cold data is stored long-term and accessed on demand.

[0057] The core objective of this embodiment is to establish a hot-tag determination and differentiated storage mechanism based on newly generated memory data, tailored to user preferences. The second semantic tags of frequently used user data reflect their core needs and usage habits. This embodiment determines hot tags through semantic matching, allowing new data to quickly adapt to user preferences and ensuring efficient access to frequently related data. Simultaneously, this embodiment can implement tiered storage based on hot tags. Hot data is cached locally and at cloud edge nodes to ensure real-time performance, while cold data is indexed locally and archived in the cloud to save resources, achieving a balance between new data storage efficiency and resource utilization.

[0058] For example, a user uses a laptop as the primary device to open a memory management application and voice-inputs "Complete the market research report and submit it for approval next Wednesday." After receiving the user's input, the application's backend initiates a new data generation and storage process.

[0059] The first device processes user input in the form of voice, converting it into standardized user input text, "Complete the market research report and submit it for approval next Wednesday," via an on-device speech-to-text interface. The first device can then extract the core meaning of the user input text using a lightweight semantic recognition model, generating the first semantic tag "#marketresearch#report#to-do#approval".

[0060] The first device can acquire the second semantic tags corresponding to all of the user's high-frequency operation data. This high-frequency operation data is the user's past memory data marked as hot data tags. Assume that the second semantic tags include #market research#to-do, #report submission#approval, #work task#deadline, etc. The first device can calculate the matching degree between the first semantic tag and each second semantic tag using a semantic similarity algorithm, with a preset matching degree threshold of 80%. Assume that the matching degree between the first semantic tag and #market research#to-do is 85%, and the matching degree with #report submission#approval is 88%, both exceeding the matching degree threshold. Therefore, the user's input text is determined to be a hot data tag. If, after calculation, the matching degree between all second semantic tags and the first semantic tag is 60%, which is not greater than the matching degree threshold, then the hot tag is determined to be a cold data tag.

[0061] The first device can structurally integrate the first semantic tag, the popularity tag, and the user-input text to generate target memory data. If the popularity tag is a hot data tag, the first device can directly store the target memory data in the laptop's hot data storage area to ensure fast local access. At the same time, the first device can push the target memory data to the cloud edge node in the user's frequently used region via the Web Socket protocol. After receiving it, the cloud edge node will cache it to generate a cached copy of the target memory data, ensuring low latency when accessing across devices.

[0062] If the user inputs travel notes compiled from six months ago, the generated first semantic tag "#travelnotes#archives" matches no more than 80% of all second semantic tags, thus being classified as a cold data tag according to the rules. The first device can generate a target index entry containing a data ID, title, core tags, and creation timestamp based on the target memory data, and store this target index entry in the laptop's cold data index storage area. Simultaneously, the first device can temporarily cache the target memory data and compress it using a high compression ratio algorithm to obtain a target compressed data package. The first device can then push the target compressed data package and the target index entry together to the cloud edge node via a low-priority transmission channel. Upon receiving the data, the cloud edge node stores the target compressed data package in its own cloud archive storage area and updates its corresponding cold data index entry based on the target index entry, ensuring consistency between the cloud index and the local index.

[0063] This embodiment uses semantic matching combined with user preferences to determine the popularity tags of newly generated memory data, ensuring that the new data storage strategy aligns with user needs. Default hot data tag settings guarantee efficient and immediate access to new data. This embodiment employs a storage method that combines local storage of hot data with cloud edge node caching, improving cross-device synchronization and access speed. Cold data is indexed locally and archived in the cloud, saving local and bandwidth resources. This embodiment enables personalized adaptation of new data storage, balancing access efficiency and resource optimization, solving the problems of low efficiency and resource waste caused by traditional unified storage of new data, and improving the user experience.

[0064] Corresponding to the memory synchronization storage management method in the above embodiments, Figure 2 This is a structural block diagram of a memory synchronization storage management device provided according to an embodiment of this application. For ease of explanation, only the parts relevant to the embodiment of this application are shown. References Figure 2 The memory synchronization storage management device 20 includes: an update operation detection module 21, a hot data synchronization storage module 22, and a cold data storage management module 23.

[0065] The update operation detection module 21 is used to respond to the detection that a user has performed an update operation on the first memory data through the first device, and to obtain the heat label of the first memory data and the second memory data; the heat label is determined based on the user's behavior data on the memory data, and the second memory data refers to the first memory data after the user's update; The hot data synchronization storage module 22 is used to incrementally extract the second memory data to obtain an incremental data packet if the heat tag of the first memory data is a hot data tag; update the first memory data stored in the first device based on the incremental data packet; determine the target synchronization protocol based on the current operating status of the first device; and push the incremental data packet to the cloud edge node based on the target synchronization protocol; the cloud edge node is used to update the cached copy of the first memory data based on the incremental data packet and push the incremental data packet to the second device associated with the user; the second device is used to store the incremental data packet and report the synchronization completion status to the cloud edge node; The cold data storage management module 23 is used to cache the second memory data if the heat label of the first memory data is a cold data label; generate index entries based on the second memory data; update the cold data index entries stored on the first device based on the index entries; compress the second memory data to obtain a compressed data packet; and push the compressed data packet and index entries to the cloud edge node; the cloud edge node is also used to update the first memory data stored in the cloud archive storage area based on the compressed data packet, and to update the cold data index entries stored on the cloud edge node based on the index entries.

[0066] In one embodiment of this application, the memory synchronization storage management device 20 further includes: a new data storage module, used to generate user input text based on the user input information and generate a first semantic tag based on the user input text in response to receiving user input information; Obtain the second semantic tag corresponding to each of the high-frequency operation data, and calculate the matching degree between the first semantic tag and each second semantic tag respectively; high-frequency operation data refers to the memory data whose heat tag is the hot data tag; If at least one second semantic tag has a matching degree greater than the matching degree threshold with the first semantic tag, then the heat tag of the user input text is determined to be a hot data tag. If the matching degree between each of the second semantic tags and the first semantic tag is not greater than the matching degree threshold, then the hot tags of the user input text are determined to be cold data tags. Target memory data is generated based on the first semantic tag, popularity tag, and user input text; Target memory data is stored based on popularity tags.

[0067] In one embodiment of this application, the newly added data storage module, when storing target memory data based on heat tags, is specifically used for: If the heat tag is a hot data tag, the target memory data is stored in the hot data storage area of ​​the first device; the target memory data is pushed to the cloud edge node, which is also used to cache the target memory data to obtain a copy of the cached target memory data; If the heat tag is a cold data tag, then a target index entry is generated based on the target memory data, and the target index entry is stored in the cold data index storage area of ​​the first device; the target memory data is cached; the target memory data is compressed to obtain a target compressed data package, and the target compressed data package and the target index entry are pushed to the cloud edge node; the cloud edge node is also used to store the target compressed data package in the cloud archive storage area of ​​the cloud edge node; the cloud edge node is also used to update the cold data index entries stored in the cloud edge node based on the target index entries.

[0068] In one embodiment of this application, when the hot data synchronization storage module 22 determines the target synchronization protocol based on the current operating state of the first device and pushes incremental data packets to the cloud edge node based on the target synchronization protocol, it is specifically used for: if the first device is in the foreground running state, then the target synchronization protocol is determined to be Web Socket, and the incremental data packets are pushed to the cloud edge node through Web Socket; if the first device is in the background running state and / or in a low power state, then the target synchronization protocol is determined to be MQTT, and the incremental data packets are pushed to the cloud edge node through MQTT.

[0069] In one embodiment of this application, the second device is at least one, and the storage of incremental data packets is achieved by the second device in the following manner: For each second device, if the second device is in the foreground state, the incremental data packets are stored in the hot data storage area of ​​the second device; if the second device is in the background state, the incremental data packets are cached, and when the second device is woken up, the cached incremental data packets are stored in the hot data storage area of ​​the second device.

[0070] In one embodiment of this application, the hotness tag of the first memory data is a cold data tag; the memory synchronization storage management device 20 further includes: an access trigger synchronization module, which, after pushing the compressed data packet and index entry to the cloud edge node, if a user access operation for the second memory data is detected, sends a data access request to the cloud edge node so that the cloud edge node extracts the compressed data packet from the archive storage area and sends it to the first device; and receives and decompresses the compressed data packet.

[0071] In one embodiment of this application, when the hot data synchronization storage module 22 performs incremental extraction on the second memory data to obtain an incremental data packet, it is specifically used to: obtain the change field between the second memory data and the first memory data, and generate an incremental data packet carrying a data ID, the change field, the modification timestamp, and the verification hash value.

[0072] See Figure 3 , Figure 3This is a schematic block diagram of an electronic device provided according to an embodiment of this application. Figure 3 The electronic device 300 in this embodiment may include one or more processors 301, one or more input devices 302, one or more output devices 303, and one or more memories 304. The processors 301, input devices 302, output devices 303, and memories 304 communicate with each other via a communication bus 305. The memories 304 store computer programs, including program instructions. The processors 301 execute the program instructions stored in the memories 304. Specifically, the processors 301 are configured to invoke the program instructions to perform the functions of the modules in the aforementioned device embodiments, for example... Figure 2 The functions of the update operation detection module 21, the hot data synchronization storage module 22, and the cold data storage management module 23 are shown.

[0073] It should be understood that, in the embodiments of this application, the processor 301 may be a central processing unit (CPU), but it may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0074] Input device 302 may include a touchpad, a fingerprint sensor (for collecting the user's fingerprint information and fingerprint orientation information), a microphone, etc., and output device 303 may include a display (LCD, etc.), a speaker, etc.

[0075] The memory 304 may include read-only memory and random access memory, and provides instructions and data to the processor 301. A portion of the memory 304 may also include non-volatile random access memory. For example, the memory 304 may also store device identification information.

[0076] In specific implementations, the processor 301, input device 302, and output device 303 described in the embodiments of this application can execute the implementation methods described in the embodiments of the memory synchronization storage management method provided in the embodiments of this application, or they can execute the implementation methods of the electronic device 300 described in the embodiments of this application, which will not be repeated here.

[0077] In another embodiment of this application, a computer-readable storage medium is provided. This computer-readable storage medium stores a computer program, which includes program instructions. When executed by a processor, the program instructions implement all or part of the processes in the methods described above. Alternatively, the computer program can instruct related hardware to complete the process. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include any entity or device capable of carrying computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0078] The computer-readable storage medium can be an internal storage unit of the electronic device in any of the foregoing embodiments, such as a hard disk or memory of the electronic device. The computer-readable storage medium can also be an external storage device of the electronic device, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD) card, flash card, etc., equipped on the electronic device. Furthermore, the computer-readable storage medium can include both internal and external storage units of the electronic device. The computer-readable storage medium is used to store computer programs and other programs and data required by the electronic device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0079] Those skilled in the art will recognize that the modules / units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0080] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the electronic devices and units described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0081] In the several embodiments provided in this application, it should be understood that the disclosed electronic devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of modules / units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules, units, or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces or modules / units, or it may be an electrical, mechanical, or other form of connection.

[0082] The modules / units described as separate components may or may not be physically separate. Similarly, the components shown as modules / units may or may not be physical modules / units; they may be located in one place or distributed across multiple network modules / units. Some or all of the modules / units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0083] Furthermore, the functional modules / units in the various embodiments of this application can be integrated into one processing module / unit, or each module / unit can exist physically separately, or two or more modules / units can be integrated into one module / unit. The integrated modules / units described above can be implemented in hardware or in the form of software functional modules / units.

[0084] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A memory synchronization storage management method, characterized in that, Applied to the first device, including: In response to detecting that a user updates the first memory data through the first device, the system obtains the heat tag of the first memory data and the second memory data; the heat tag is determined based on the user's behavioral data on the memory data, and the second memory data refers to the first memory data updated by the user. If the heat tag of the first memory data is a hot data tag, then incremental extraction is performed on the second memory data to obtain an incremental data packet; the first memory data stored in the first device is updated based on the incremental data packet; the target synchronization protocol is determined based on the current operating status of the first device, and the incremental data packet is pushed to the cloud edge node based on the target synchronization protocol; the cloud edge node is used to update the cached copy of the first memory data based on the incremental data packet, and push the incremental data packet to the second device associated with the user; the second device is used to store the incremental data packet and report the synchronization completion status to the cloud edge node; If the hot data label of the first memory data is a cold data label, then the second memory data is cached; an index entry is generated based on the second memory data, and the cold data index entry stored on the first device is updated based on the index entry; the second memory data is compressed to obtain a compressed data package, and the compressed data package and index entry are pushed to the cloud edge node; the cloud edge node is also used to update the first memory data stored in the cloud archive storage area based on the compressed data package, and to update the cold data index entry stored on the cloud edge node based on the index entry.

2. The memory synchronization storage management method as described in claim 1, characterized in that, Also includes: In response to receiving user input information, the system generates user input text based on the user input information and generates a first semantic tag based on the user input text; Obtain the second semantic tag corresponding to each of the high-frequency operation data, and calculate the matching degree between the first semantic tag and each second semantic tag respectively; the high-frequency operation data refers to the memory data of hot data tags; If at least one second semantic tag has a matching degree greater than the matching degree threshold with the first semantic tag, then the popularity tag of the user input text is determined to be a hot data tag. If the matching degree between each of the second semantic tags and the first semantic tag is not greater than the matching degree threshold, then the hot tag of the user input text is determined to be a cold data tag. Target memory data is generated based on the first semantic tag, the popularity tag, and the user input text; The target memory data is stored based on the heat tags.

3. The memory synchronization storage management method as described in claim 2, characterized in that, The storage of the target memory data based on the heat tag includes: If the heat tag is a hot data tag, the target memory data is stored in the hot data storage area of ​​the first device; the target memory data is pushed to the cloud edge node, and the cloud edge node is also used to cache the target memory data to obtain a cached copy of the target memory data; If the heat tag is a cold data tag, then a target index entry is generated based on the target memory data, and the target index entry is stored in the cold data index storage area of ​​the first device; the target memory data is cached; the target memory data is compressed to obtain a target compressed data packet, and the target compressed data packet and the target index entry are pushed to the cloud edge node; the cloud edge node is also used to store the target compressed data packet in the cloud archive storage area of ​​the cloud edge node; the cloud edge node is also used to update the cold data index entry stored on the cloud edge node based on the target index entry.

4. The memory synchronization storage management method as described in claim 1, characterized in that, The process of determining the target synchronization protocol based on the current operating status of the first device, and pushing incremental data packets to the cloud edge node based on the target synchronization protocol, includes: If the first device is running in the foreground, the target synchronization protocol is determined to be WebSocket, and the incremental data packet is pushed to the cloud edge node through the WebSocket; If the first device is running in the background and / or has low power, the target synchronization protocol is determined to be MQTT, and the incremental data packets are pushed to the cloud edge node through MQTT.

5. The memory synchronization storage management method as described in claim 1, characterized in that, The second device is at least one, and the storage of incremental data packets is implemented by the second device in the following manner: For each second device, if the second device is in the foreground state, the incremental data packet is stored in the hot data storage area of ​​the second device; if the second device is in the background state, the incremental data packet is cached, and when the second device is woken up, the cached incremental data packet is stored in the hot data storage area of ​​the second device.

6. The memory synchronization storage management method as described in claim 1, characterized in that, After pushing the compressed data packet and index entries to the cloud edge node, the method further includes: If a user access operation for the second memory data is detected, a data access request is sent to the cloud edge node, so that the cloud edge node retrieves the compressed data packet from the archive storage area and sends it to the first device; Receive and decompress the compressed data packet.

7. The memory synchronization storage management method as described in claim 1, characterized in that, The incremental extraction of the second memory data to obtain the incremental data packet includes: Obtain the change fields between the second memory data and the first memory data, and generate an incremental data packet carrying the data ID, change fields, modification timestamp, and verification hash value.

8. A memory synchronization storage management device, characterized in that, include: The update operation detection module is used to respond to the detection that a user has performed an update operation on the first memory data through the first device, and to obtain the heat tag of the first memory data and the second memory data; The popularity tags are determined based on user behavior data related to memory data, where the second memory data refers to the user's updated first memory data; The hot data synchronization storage module is used to incrementally extract the second memory data to obtain an incremental data packet if the heat label of the first memory data is a hot data label. The first memory data stored in the first device is updated based on incremental data packets; the target synchronization protocol is determined based on the current operating status of the first device, and the incremental data packets are pushed to the cloud edge node based on the target synchronization protocol; The cloud edge node is used to update the copy of the cached first memory data based on incremental data packets, and push the incremental data packets to the second device associated with the user; the second device is used to store the incremental data packets and report the synchronization completion status to the cloud edge node. The cold data storage management module is used to cache the second memory data if the heat label of the first memory data is a cold data label; Index entries are generated based on the second memory data, and the cold data index entries stored in the first device are updated based on the index entries; The second memory data is compressed to obtain a compressed data packet, and the compressed data packet and index entries are pushed to the cloud edge node; The cloud edge node is also used to update the first memory data stored in the cloud archive storage area based on compressed data packets, and to update the cold data index entries stored in the cloud edge node based on index entries.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 7.

Images