Cross-platform memory sharing method, device, equipment, storage medium and program product

Abstract

This application provides a cross-platform memory sharing method, apparatus, device, storage medium, and program product. The method includes: responding to a query request sent by a first requesting platform based on a standardized interface defined by a memory sharing protocol layer; verifying the query request according to preset permission information; wherein the permission information includes access permissions granted by the service platform to different requesting platforms; the access permissions are associated with at least one database or sub-database in the service platform and specify the corresponding operation type; if the query request is verified, performing a semantic query on the query request to obtain a memory fragment; and returning the memory fragment to the first requesting platform based on an interoperability engine. This method can achieve efficient sharing and collaboration of memory across platforms, improving the continuity and personalization of overall intelligent services.

Description

Technical Field

[0001] This application relates to the field of artificial intelligence technology, and in particular to a cross-platform memory sharing method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the acceleration of digitalization, various platforms (such as social platforms, medical platforms, financial platforms, and IoT platforms) have accumulated massive amounts of user and business data. Among these, with the rapid development of artificial intelligence (AI) agents, long-term memory has become a key module for improving the consistency, adaptability, and intelligence level of agents within platforms.

[0003] However, user behavior and information are locked onto a single platform, often creating "data silos" between platforms, making it difficult to meet the needs of complex business scenarios. Summary of the Invention

[0004] This application provides a cross-platform memory sharing method, apparatus, device, storage medium, and program product, which can realize efficient sharing and collaboration of memory across platforms, thereby improving the continuity and personalization of overall intelligent services.

[0005] In a first aspect, this application provides a cross-platform memory sharing method, the method being applied to a service platform; the method includes:

[0006] In response to a query request sent by the first requesting platform based on a standardized interface defined by the memory sharing protocol layer, the query request is verified according to preset permission information; wherein, the permission information includes the access permissions that the service platform grants to different requesting platforms respectively; the access permissions are associated with at least one database or data sub-database in the service platform and specify the corresponding operation type;

[0007] If the query request is verified, a semantic query is performed on the query request to obtain a memory fragment;

[0008] Based on the interoperability engine, the memory fragment is returned to the first requesting platform.

[0009] In one possible implementation, the access permissions include the granularity of access to the at least one database or sub-database and the access topic; the operation types include read-only permissions and edit permissions.

[0010] In one possible implementation, the method further includes:

[0011] Determine the data synchronization logic between the platform and the second requesting platform; wherein the data synchronization logic includes data synchronization time;

[0012] According to the data synchronization logic, the updated memory data is actively pushed to the second requesting platform, or the updated memory data is sent in response to the passive request of the second requesting platform.

[0013] In one possible implementation, performing a semantic query on the query request to obtain a memory fragment includes:

[0014] Based on the query request, a multi-dimensional data combination query is performed from multiple heterogeneous storage structures to obtain the initial query results;

[0015] The initial query results are input into a large language model for context integration processing to generate the memory fragment.

[0016] In one possible implementation, the step of performing a multi-dimensional data combination query from multiple heterogeneous storage structures to obtain initial query results based on the query request includes:

[0017] The query request is parsed to obtain the query conditions; wherein, the query conditions include at least one of time range, memory type, and associated entity;

[0018] Based on the query conditions of the query request, at least one initial memory segment is extracted from the heterogeneous storage structure;

[0019] The initial memory fragments are combined according to time axis or correlation to obtain the initial query result.

[0020] In one possible implementation, the method further includes:

[0021] The standardized interface is divided into a metadata interface, a retrieval interface, a write interface, and a status change interface; wherein, the metadata interface is used to declare the access permissions supported by the service platform; the retrieval interface is used to process query requests; the write interface is used to process write requests; and the status change interface is used to change the memory sharing authorization status.

[0022] Secondly, this application provides a cross-platform memory sharing device, the device being applied to a service platform; the device includes:

[0023] The verification module is used to respond to a query request sent by the first requesting platform based on the standardized interface of the memory sharing protocol definition layer, and to verify the query request according to preset permission information; wherein, the permission information includes the access permissions that the service platform opens to different requesting platforms respectively; the access permissions are associated with at least one database or data sub-database in the service platform and specify the corresponding operation type;

[0024] The query module is used to perform a semantic query on the query request to obtain a memory fragment if it is determined that the query request has passed the verification.

[0025] The return module is used to return the memory fragment to the first requesting platform based on the interoperability engine.

[0026] In one possible implementation, the access permissions include the granularity of access to the at least one database or sub-database and the access topic; the operation types include read-only permissions and edit permissions.

[0027] In one possible implementation, the apparatus is further configured to: determine data synchronization logic with a second requesting platform; wherein the data synchronization logic includes data synchronization time; and, according to the data synchronization logic, actively push updated memory data to the second requesting platform, or send the updated memory data in response to a passive request from the second requesting platform.

[0028] In one possible implementation, the query module is specifically used to: perform multi-data combination queries from multiple heterogeneous storage structures according to the query request to obtain initial query results; input the initial query results into a large language model for context integration processing to generate the memory fragment.

[0029] In one possible implementation, the query module is further specifically used to: parse the query request to obtain the query conditions of the query request; wherein the query conditions include at least one of time range, memory type, and associated entity; extract at least one initial memory segment from the heterogeneous storage structure according to the query conditions of the query request; and combine the at least one initial memory segment according to the time axis or the degree of association to obtain the initial query result.

[0030] In one possible implementation, the device is further configured to: divide the standardized interface into a metadata interface, a retrieval interface, a write interface, and a status change interface; wherein the metadata interface is used to declare the access permissions supported by the service platform; the retrieval interface is used to process query requests; the write interface is used to process write requests; and the status change interface is used to change the memory sharing authorization status.

[0031] Thirdly, this application provides an electronic device, including: a memory and a processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, causing the processor to perform the first aspect and / or various possible embodiments of the first aspect as described above.

[0032] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible embodiments of the first aspect.

[0033] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0034] The cross-platform memory sharing method, apparatus, device, storage medium, and program product provided in this application allow a first requesting platform to send a query request to a service platform through a standardized interface of the memory sharing protocol definition layer. The service platform verifies the query request based on preset permission information. If the query request is verified, a semantic query is performed on the query request to obtain a memory fragment, which is then returned to the first requesting platform through an interoperability engine. Furthermore, by setting a standardized interface of the memory sharing protocol definition layer, different requesting platforms can initiate query requests to the service platform using a unified interaction specification, thereby achieving efficient sharing and collaboration of memory across platforms and improving the continuity and personalization of the overall intelligent service. Attached Figure Description

[0035] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0036] Figure 1 This application provides an illustration of an application scenario.

[0037] Figure 2 A flowchart illustrating a cross-platform memory sharing method provided in an embodiment of this application;

[0038] Figure 3 This application provides a schematic diagram of the structure of a cross-platform memory sharing system as an embodiment of the present application.

[0039] Figure 4 A flowchart illustrating another cross-platform memory sharing method provided in an embodiment of this application;

[0040] Figure 5 This is a schematic diagram of the structure of a cross-platform memory sharing device provided in an embodiment of this application;

[0041] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0042] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0043] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0044] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, they do not violate public order and good morals, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0045] Furthermore, the technical solution involved in this application, which involves big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.) and the use of artificial intelligence technology for automated decision-making, and makes decisions that have a significant impact on user rights based on the results of automated decision-making, provides users with corresponding operation entry points for users to choose to agree to or reject the results of automated decision-making; if the user chooses to reject, the process will proceed to the expert decision-making process.

[0046] This application can be applied to scenarios involving multi-platform AI Agent collaboration, for example, Figure 1 This application provides an illustration of an application scenario, such as... Figure 1 As shown, the user's conversation history with the virtual assistant on the social platform needs to be accessed by the Agent with the same name on the e-commerce platform to optimize recommendations.

[0047] Based on the scenarios described above, it's clear that AI agents' memory storage is locked to a single platform. For example, a social media platform's agent might use a vector database to store user conversation embeddings, while an e-commerce platform's agent might use a graph database to build a product recommendation relationship graph. Due to the lack of a unified interface protocol, cross-platform calls require additional adaptation layers, and access control is limited to coarse-grained APIs (e.g., completely open or completely closed), failing to refine to the specific memory topic or data granularity. Furthermore, the parsing and fusion of heterogeneous data (such as vectors, graphs, and logs) relies on the platform's internal logic, resulting in low cross-platform retrieval efficiency and preventing users from independently managing the scope of their private data sharing.

[0048] The cross-platform memory sharing method provided in this application enables different requesting platforms to initiate query requests to the service platform with a unified interaction specification by setting a standardized interface for the memory sharing protocol definition layer, thereby achieving efficient sharing and collaboration of memory across platforms.

[0049] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0050] Figure 2 This is a flowchart illustrating a cross-platform memory sharing method provided in an embodiment of this application, as shown below. Figure 2 As shown, the method includes:

[0051] 201. In response to the query request sent by the first requesting platform based on the standardized interface of the memory sharing protocol definition layer, the query request is verified according to the preset permission information; wherein, the permission information includes the access permissions that the service platform opens to different requesting platforms respectively; the access permissions are associated with at least one database or data sub-database in the service platform and specify the corresponding operation type.

[0052] For example, the executing entity in this embodiment may be an electronic device, hereinafter referred to as the device. A cross-platform memory sharing system is deployed in the device. Figure 3 This application provides a schematic diagram of the structure of a cross-platform memory sharing system, as shown in the embodiments. Figure 3As shown, the system includes a memory sharing protocol definition layer, an interoperability engine, a memory access toolset, and a permission and granular control mechanism. Based on the memory sharing protocol definition layer, standardized interfaces (such as / mlp / search, / mlp / write, etc., Hypertext Transfer Protocol (HTTP) interfaces) are deployed. A unified memory linking protocol (such as JSON / YAML) defines the interface specifications for memory access between multiple agents, ensuring that the standardized interface conforms to the memory linking protocol. Furthermore, a cross-platform interface is defined through a unified semantic specification (such as JSON / YAML), eliminating differences between interfaces on different platforms and achieving unified read / write expression.

[0053] The first request platform, acting as the Agent, can generate a natural language query request through this standardized interface. This query request conforms to the data format of the memory linking protocol. The first request platform sends this query request to the service platform to request cross-platform memory resources. Upon receiving the query request, the service platform, based on a permission and granularity control mechanism, obtains preset permission information to verify the query request. This permission information includes the access permissions granted by the service platform to different request platforms, such as access topics and synchronization times. These access permissions are associated with at least one database or sub-database within the service platform and specify the corresponding operation type, such as a write operation. The service platform verifies the query request according to the access permissions corresponding to the first request platform in the permission information, obtaining the verification result to determine whether the query request has passed verification.

[0054] Access permissions include the granularity of access to at least one database or sub-database and the topic of access; operation types include read-only permissions and edit permissions.

[0055] For example, based on the preset permission information, when the social platform Agent requests to write user conversation summaries to the e-commerce platform (i.e., the service platform) through the / mlp / write interface, the e-commerce platform verifies whether the target database requested by the social platform to write user conversation summaries has been authorized to write permissions for the "product recommendation" topic, and checks whether the user conversation summaries to be written comply with data granularity restrictions (such as only allowing writing of summary fields).

[0056] By combining control over thematic, data granularity, and visibility dimensions, the service platform can accurately match write requests with user-declared permission policies, ensuring the compliance of data sharing. This can further enhance the security and controllability of cross-platform memory sharing while protecting user privacy.

[0057] In one example, the first request platform can use a memory access toolset to construct requests and configure the environment to obtain query requests and configuration files.

[0058] For example, combined Figure 3 The memory access toolset provides a client library for cross-platform calls, cache control, and permission verification. The first request platform constructs requests based on the memory access toolset, transforming vague requirements into structured, precise API calls or commands to obtain query requests. Using the memory access toolset, the query request undergoes environment configuration processing to obtain a configuration file, including the context, parameters, permissions, and resources required for the execution of this request / command, ensuring that the processed query request adapts to the current application environment of cross-platform memory sharing.

[0059] For example, through prompt engineering or fine-tuning, large language models can understand user intent and output the function name and parameters to be called in a structured format (such as JSON) for request construction to obtain query requests.

[0060] 202. If the query request is verified, a semantic query is performed on the query request to obtain the memory fragment.

[0061] For example, if the service platform determines that the query request of the first requesting platform has been verified, it uses the agent of the service platform to perform semantic recognition on the query request, obtains the query semantics, and uses technologies such as vector retrieval and graph jump to query from at least one database or data sub-database in the service platform to obtain multimodal data and process it to generate memory fragments that users can understand.

[0062] 203. Based on the interoperability engine, return the memory fragment to the first requesting platform.

[0063] For example, the service platform standardizes memory fragments through an interoperability engine, ensuring that the data structure of the memory fragments conforms to the standardized data structure defined by a unified memory linking protocol. This allows for compatibility with various heterogeneous storage structures and adapts to the data evolution needs of different platforms. Based on the interoperability engine, the memory fragment is returned to the caller of the Agent, i.e., the first requesting platform, without exposing the platform's internal details, thereby achieving cross-platform memory interoperability.

[0064] Among them, the interoperability engine supports the fusion recall and response standard format return of heterogeneous memory structures (dense vectors, sparse vectors, graphs, logs, etc.).

[0065] For example, the social platform (first request platform) agent sends a natural language query to the e-commerce platform agent via the ` / mlp / search` interface. The e-commerce platform (service platform) agent returns a standardized memory fragment. This memory fragment is described using a structured schema, including fields such as `text`, `summary`, `timestamp`, `source_platform`, `reference_id`, `visibility`, and `confidence`. This provides Time-To-Live (TTL), Access Control Lists (ACLs), and vector-level permission boundaries. TTL can be used to force cache updates, ensuring data freshness, automatically cleaning up unnecessary or expired data, saving memory resources, and improving business consistency. Thematic ACLs are used to define permission rules for "who can publish / subscribe".

[0066] This embodiment provides a cross-platform memory sharing method. By setting a standardized interface for the memory sharing protocol definition layer, different requesting platforms can initiate query requests to the service platform with a unified interaction specification. This enables efficient sharing and collaboration of memories across platforms, thereby improving the continuity and personalization of the overall intelligent service.

[0067] Figure 4 A flowchart illustrating another cross-platform memory sharing method provided in this application embodiment is shown below. Figure 4 As shown, the method includes:

[0068] 301. In response to a query request sent by the first requesting platform based on the standardized interface of the memory sharing protocol definition layer, the query request is verified according to the preset permission information; wherein, the permission information includes the access permissions that the service platform opens to different requesting platforms respectively; the access permissions are associated with at least one database or data sub-database in the service platform and specify the corresponding operation type.

[0069] For example, the content of this step is the same as step 201, and will not be repeated here.

[0070] In one possible implementation, the standardized interface is divided into a metadata interface, a retrieval interface, a write interface, and a status change interface; wherein, the metadata interface is used to declare the access permissions supported by the service platform; the retrieval interface is used to process query requests; the write interface is used to process write requests; and the status change interface is used to change the memory sharing authorization status.

[0071] Specifically, the standardized interfaces for cross-platform memory access are divided into metadata interfaces, retrieval interfaces, and write interfaces. Metadata interfaces declare the memory topics, granularity, and access permissions supported by the service platform; for example, the ` / mlp / topics` interface returns the "product recommendations" topic supported by the service platform and declares that this topic only allows read-only access. Retrieval interfaces receive query requests from external agents and return matching memory fragments; for example, an e-commerce platform receives a natural language query "recommend red dresses" from a social platform via the ` / mlp / search` interface and returns a summary of relevant products. Write interfaces receive write requests from the external first-request platform agent and process memory fragments; for example, a social platform writes a user conversation summary to an e-commerce platform via the ` / mlp / write` interface, and the e-commerce platform stores the summary after verifying permissions.

[0072] For example, the / mlp / topics interface declares the memory topics supported by the platform (such as "product recommendations") and their access permissions (such as read-only), the / mlp / search interface receives natural language queries and returns matching memory fragments, and the / mlp / write interface receives write requests from external agents and stores the data after verifying permissions.

[0073] Through layered interface design, agents from different platforms can achieve cross-platform memory sharing based on a unified standard, realizing the modularity and scalability of cross-platform memory sharing. This can improve the standardization and maintainability of cross-platform interfaces, while reducing the complexity of inter-platform integration.

[0074] 302. If the query request is verified, perform a multi-data combination query from multiple heterogeneous storage structures according to the query request to obtain the initial query results.

[0075] For example, if the service platform determines that the query request has been verified, it calls multiple internal heterogeneous storage structures (such as graph databases, vector databases, etc.) and extracts at least one initial memory fragment related to the query request from these multiple heterogeneous storage structures through vector retrieval, graph jump and other technologies.

[0076] For example, the service platform extracts semantic features from query requests, converting them into semantic feature vectors for similarity matching and structured semantic elements for relationship identification. Subsequently, based on the semantic features, it selects or combines different retrieval paths, retrieves semantically similar memory content from the vector storage structure, and performs jump queries from the graph structure storage based on entity relationships or association paths. If necessary, it can also combine time series or event records for supplementary retrieval. The results returned by each retrieval path are uniformly abstracted into standardized initial memory fragments to obtain the initial query results.

[0077] In one possible implementation, step 302 includes:

[0078] Step 1: Parse the query request to obtain the query conditions; the query conditions include at least one of time range, memory type, and related entities.

[0079] Step 2: Based on the query conditions of the query request, extract at least one initial memory segment from the heterogeneous storage structure.

[0080] Step 3: Combine at least one initial memory fragment according to the time axis or relevance to obtain the initial query results.

[0081] Specifically, the service platform parses the query request to obtain the query conditions. These conditions include at least one of the following: time range (e.g., "3 quarters"), memory type (e.g., "images and vectors"), and associated entity (e.g., "used mobile phones"). Based on these query conditions, the service platform uses techniques such as vector retrieval and graph navigation to extract at least one initial memory segment from the heterogeneous storage structure that matches the query conditions. The service platform then combines these initial memory segments according to the timeline or the correlation between each initial memory segment and the query conditions to obtain initial query results, thereby improving the relevance of the query results.

[0082] For example, based on the relevance between each initial memory fragment and the query conditions of the query request, all the obtained initial memory fragments are filtered to obtain a preset number of initial memory fragments with high relevance. Then, based on the time axis, the preset number of initial memory fragments are sorted (such as by the rerank algorithm) to obtain the initial query results.

[0083] In one possible implementation, step 302 further includes: adjusting the memory sharing granularity and scope based on the behavioral context of the query request; wherein the memory sharing granularity and scope are used to verify the query request.

[0084] Specifically, the backend memory system, while adhering to the MLP protocol, can implement static or dynamic permission policies. That is, based on the query request, the backend memory system obtains the behavioral context of the user making the query request and dynamically adjusts the granularity and scope of memory sharing according to this behavioral context to verify the query request. The MLP protocol itself is only responsible for defining, transmitting, and exchanging verification results for parameters related to the permission policy.

[0085] 303. Input the initial query results into the large language model, perform context integration processing, and generate memory fragments.

[0086] For example, the initial query results are input into the large language model of the service platform. Through the context-aware capabilities of the large language model, the initial query results are integrated into the context to obtain memory fragments that are easy for users to understand.

[0087] For example, image memories (such as product images) uploaded by users on social platforms can be converted into text descriptions through cross-modal embedding technology and retrieved by association with product text summaries in the vector database of e-commerce platforms. The large language model combines the vector similarity and semantic matching degree between the text description and the product text summary, and merges the text descriptions with both vector similarity and semantic matching degree greater than the threshold with the product text summary to generate memory fragments.

[0088] 304. Based on the interoperability engine, return a memory fragment to the first requesting platform.

[0089] For example, the content of this step is the same as step 203, and will not be repeated here.

[0090] 305. Determine the data synchronization logic between the platform and the second requesting platform; wherein the data synchronization logic includes data synchronization time.

[0091] For example, the service platform determines the data synchronization logic with the second requesting platform based on the memory access toolset, including the data synchronization time for memory sharing between the service platform and the second requesting platform, and also includes the data synchronization mode, such as active push mode or passive request mode.

[0092] 306. Based on the data synchronization logic, actively push updated memory data to the second requesting platform, or send updated memory data in response to a passive request from the second requesting platform.

[0093] For example, the service platform, based on the memory access toolset, actively pushes updated memory data to the second requesting platform according to the data synchronization time and the active push mode in the data synchronization logic. Alternatively, in response to a passive request from the second requesting platform, the service platform sends updated memory data to the second requesting platform based on the memory access toolset, according to the data synchronization time and the passive request mode in the data synchronization logic.

[0094] By pre-determining the data synchronization logic (including key parameters such as data synchronization time) between the service platform and the second requesting platform, the service platform can flexibly configure the synchronization strategy according to different business scenarios, network conditions, or the characteristics of the second requesting platform itself, thereby improving the flexibility and adaptability of data synchronization; and by combining the two mechanisms of active push and passive request, it can effectively maintain data consistency across platforms.

[0095] In this embodiment, based on the above embodiments, a hierarchical topic + granularity permission control mechanism is used, combined with data synchronization logic between each other requesting platform. While ensuring users' autonomous control over memory sharing and data security, data silos between platforms are broken down, and knowledge (such as user behavior records and product recommendation logic) is shared between cross-platform Ages, thereby improving the continuity and personalization of the overall service.

[0096] Figure 5 This is a schematic diagram of the structure of a cross-platform memory sharing device provided in an embodiment of this application, as shown below. Figure 5 As shown, the device is used in a service platform; the device includes:

[0097] The verification module 401 is used to respond to the query request sent by the first requesting platform based on the standardized interface of the memory sharing protocol definition layer, and to verify the query request according to the preset permission information; wherein, the permission information includes the access permissions that the service platform opens to different requesting platforms respectively; the access permissions are associated with at least one database or data sub-database in the service platform and specify the corresponding operation type;

[0098] The query module 402 is used to perform a semantic query on the query request to obtain the memory fragment if it is determined that the query request has been verified.

[0099] Return module 403 is used to return a memory fragment to the first requesting platform based on the interoperability engine.

[0100] In one possible implementation, access permissions include the granularity of access to at least one database or subdatabase and the topic of access; operation types include read-only permissions and edit permissions.

[0101] In one possible implementation, the apparatus is further configured to: determine data synchronization logic with the second requesting platform; wherein the data synchronization logic includes data synchronization time; and according to the data synchronization logic, actively push updated memory data to the second requesting platform, or send updated memory data in response to a passive request from the second requesting platform.

[0102] In one possible implementation, the query module 402 is specifically used to: perform multi-data combination queries from multiple heterogeneous storage structures according to the query request to obtain initial query results; input the initial query results into a large language model for context integration processing to generate memory fragments.

[0103] In one possible implementation, the query module 402 is further specifically used for: parsing the query request to obtain the query conditions of the query request; wherein the query conditions include at least one of time range, memory type, and associated entity; extracting at least one initial memory segment from the heterogeneous storage structure according to the query conditions of the query request; and combining the at least one initial memory segment according to the time axis or the degree of association to obtain the initial query result.

[0104] In one possible implementation, the apparatus is further configured to: divide the standardized interface into a metadata interface, a retrieval interface, a write interface, and a status change interface; wherein the metadata interface is used to declare the access permissions supported by the service platform; the retrieval interface is used to process query requests; the write interface is used to process write requests; and the status change interface is used to change the memory sharing authorization status.

[0105] The apparatus in this embodiment can execute the technical solutions in the above method. Its specific implementation process and technical principles are the same, and will not be repeated here.

[0106] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, such as... Figure 6 As shown, the electronic device includes: a memory 501 and a processor 502; the memory 501 is a memory used to store instructions executable by the processor 502.

[0107] The processor 502 is configured to perform the method provided in the above embodiments.

[0108] The electronic device also includes a receiver 503 and a transmitter 504. The receiver 503 is used to receive instructions and data sent by other devices, and the transmitter 504 is used to send instructions and data to external devices.

[0109] The specific implementation process of the processor can be found in the above method embodiments, and its implementation principle and technical effect are similar, so it will not be repeated here.

[0110] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0111] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed on a computer, cause the computer to perform the technical solutions described above.

[0112] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory, electrically erasable programmable read-only memory, erasable programmable read-only memory, programmable read-only memory, read-only memory, magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0113] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. The readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an application-specific integrated circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in a device.

[0114] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solutions in the above embodiments.

[0115] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as magnetic disks or optical disks.

[0116] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A cross-platform memory sharing method, characterized in that, The method is applied to a service platform; the method includes: In response to a query request sent by the first requesting platform based on a standardized interface defined by the memory sharing protocol layer, the query request is verified according to preset permission information; wherein, the permission information includes the access permissions that the service platform grants to different requesting platforms respectively; the access permissions are associated with at least one database or data sub-database in the service platform and specify the corresponding operation type; If the query request is verified, a semantic query is performed on the query request to obtain a memory fragment; Based on the interoperability engine, the memory fragment is returned to the first requesting platform.

2. The method according to claim 1, characterized in that, The access permissions include the granularity of access to the at least one database or data sub-database and the access topic; the operation types include read-only permissions and edit permissions.

3. The method of claim 1, wherein, The method further includes: Determine the data synchronization logic between the platform and the second requesting platform; wherein the data synchronization logic includes data synchronization time; According to the data synchronization logic, the updated memory data is actively pushed to the second requesting platform, or the updated memory data is sent in response to the passive request of the second requesting platform.

4. The method of claim 1, wherein, The semantic query performed on the query request to obtain memory fragments includes: Based on the query request, a multi-dimensional data combination query is performed from multiple heterogeneous storage structures to obtain the initial query results; The initial query results are input into a large language model for context integration processing to generate the memory fragment.

5. The method of claim 4, wherein, The step of performing a multi-dimensional data combination query from multiple heterogeneous storage structures according to the query request to obtain initial query results includes: The query request is parsed to obtain the query conditions; wherein, the query conditions include at least one of time range, memory type, and associated entity; Based on the query conditions of the query request, at least one initial memory segment is extracted from the heterogeneous storage structure; The initial memory fragments are combined according to time axis or correlation to obtain the initial query result.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: The standardized interface is divided into a metadata interface, a retrieval interface, a write interface, and a status change interface; wherein, the metadata interface is used to declare the access permissions supported by the service platform; the retrieval interface is used to process query requests; the write interface is used to process write requests; and the status change interface is used to change the memory sharing authorization status.

7. A cross-platform memory sharing apparatus, comprising: The device is used in a service platform; the device includes: The verification module is used to respond to a query request sent by the first requesting platform based on the standardized interface of the memory sharing protocol definition layer, and to verify the query request according to preset permission information; wherein, the permission information includes the access permissions that the service platform opens to different requesting platforms respectively; the access permissions are associated with at least one database or data sub-database in the service platform and specify the corresponding operation type; The query module is used to perform a semantic query on the query request to obtain a memory fragment if it is determined that the query request has passed the verification. The return module is used to return the memory fragment to the first requesting platform based on the interoperability engine.

8. An electronic device, comprising: include: Memory and processor; The memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-6.

9. 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-6.

10. A computer program product, characterised in that, The computer program product includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

Images