Data transmission method, device and storage medium based on model context protocol

Abstract

This application discloses a data transmission method, device, and storage medium based on the Model Context Protocol (MGP). The MGP-based data transmission method is applied to a data requester, where a communication connection based on MGP exists between the data requester and the data provider. The method includes: obtaining a resource list sent by the data provider; determining a target transmission method from preset data transmission methods based on the obtained data transmission service requirements; sending a target data request to the data provider according to the data identifier of the requested data in the resource list and the target transmission method; and obtaining the target data returned by the data provider. This solution can improve the data transmission efficiency when communicating based on the MGP.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a data transmission method, device, and storage medium based on a model context protocol. Background Technology

[0002] The Model Context Protocol (MCP) is an open-source protocol for establishing secure, bidirectional connections between large models and data sources, designed to integrate large language models with external data sources and tools. For example, data sources can use MCP to transfer data to large models for inference.

[0003] However, existing MCP-based data transmission methods typically transmit the entire data resource content at once according to the Uniform Resource Identifier (URI) in accordance with the MCP specification. This method consumes a large amount of bandwidth in weak network or mobile scenarios. On the other hand, if thumbnail transmission or on-demand loading logic is used, the data transmission process needs to rely on Hypertext Transfer Protocol or Remote Procedure Call (RPC) technology, which cannot be directly reused in MCP-based application scenarios.

[0004] Therefore, there is an urgent need for a data transmission method that can efficiently achieve data transmission within the existing MCP protocol framework without requiring cumbersome and complex changes to the basic form of the protocol. Summary of the Invention

[0005] This application provides at least one data transmission method, apparatus, device, and computer-readable storage medium based on the Model Context Protocol.

[0006] The first aspect of this application provides a data transmission method based on a Model Context Protocol (MGP). The method is applied to a data requester, and a communication connection based on the MGP exists between the data requester and a data provider. The method includes: obtaining a resource list sent by the data provider; determining a target transmission method from preset data transmission methods according to the obtained data transmission service requirements; sending a target data request to the data provider according to the data identifier of the data to be requested in the resource list and the target transmission method; and obtaining the target data returned by the data provider.

[0007] In one embodiment, the target transmission method includes a hierarchical transmission method. The step of sending a target data request to the data provider based on the data identifier of the data to be requested in the resource list and the target transmission method, and obtaining the target data returned by the data provider, includes: generating a target data request corresponding to the hierarchical transmission method based on the data identifier and target level parameters required for the data to be requested; the target level parameters corresponding to the original information entropy of the data to be requested; and sending the target data request to the data provider to obtain the target data returned by the data provider based on the data identifier and the target level parameters.

[0008] In one embodiment, the target level parameter is positively correlated with the original information entropy of the data to be requested. Sending the target data request to the data provider includes: in response to a first request for the data to be requested, initiating a first target data request for the data to be requested to the data provider, the first target data request including a first target level parameter; and in response to a non-first request for the data to be requested, initiating a second target data request for the data to be requested to the data provider, the second target data request including a second target level parameter, the second target level parameter being higher than the first target level parameter.

[0009] In one embodiment, the target transmission method includes an incremental transmission method. The step of sending a target data request to the data provider based on the data identifier of the data to be requested in the resource list and the target transmission method, and obtaining the target data returned by the data provider, includes: in response to a non-first request for the data to be requested, obtaining historical response status parameters of the data to be requested in the incremental transmission method; and initiating a target data request for the data to be requested to the data provider based on the data identifier and the historical response status parameters, thereby obtaining the target data returned by the data provider based on the data identifier and the historical response status parameters.

[0010] In one embodiment, the target transmission method includes an on-demand transmission method. The step of sending a target data request to the data provider based on the data identifier of the data to be requested in the resource list and the target transmission method, and obtaining the target data returned by the data provider, includes: obtaining data requirement parameters corresponding to the on-demand transmission method; initiating a target data request for the data to be requested to the data provider based on the data identifier and the data requirement parameters, and obtaining the target data returned by the data provider based on the data identifier and the data requirement parameters.

[0011] A second aspect of this application provides a data transmission method based on a Model Context Protocol (MGP). The method is applied to a data provider, and a communication connection based on the MGP exists between the data provider and a data requester. The method includes: sending a resource list to the data requester; in response to receiving a target data request sent by the data requester according to the resource list, parsing the target data request to obtain a data identifier and a target transmission method in the target data request, wherein the data identifier is determined by the data requester based on the data identifier of the data to be requested in the resource list, and the target transmission method is determined by the data requester from a preset data transmission method based on acquired data transmission service requirements; determining the corresponding target data based on the data identifier and the target transmission method, and sending the target data to the data provider.

[0012] In one embodiment, the target transmission method includes a hierarchical transmission method. The step of determining the corresponding target data according to the data identifier and the target transmission method, and sending the target data to the data provider, includes: obtaining the target level parameter corresponding to the hierarchical transmission method, wherein the target level parameter corresponds to the original information entropy of the data to be requested; The corresponding target data is located based on the data identifier and the target level parameter, and the target data is sent to the data provider.

[0013] In one embodiment, the target transmission method includes an incremental transmission method. The step of determining the corresponding target data according to the data identifier and the target transmission method, and sending the target data to the data provider, includes: obtaining historical response status parameters corresponding to the incremental transmission method; determining the incremental data corresponding to the data identifier according to the historical response status parameters; determining the incremental data as the target data, and sending it to the data provider.

[0014] A third aspect of this application provides a data transmission apparatus based on a Model Context Protocol (MGP). The apparatus is applied to a data requester, and a communication connection based on the MGP exists between the data requester and a data provider. The apparatus includes: an acquisition module for acquiring a resource list sent by the data provider; a transmission determination module for determining a target transmission method from preset data transmission methods based on the acquired data transmission service requirements; and a data request module for sending a target data request to the data provider based on the data identifier of the data to be requested in the resource list and the target transmission method, and obtaining the target data returned by the data provider.

[0015] A fourth aspect of this application provides a data transmission apparatus based on a Model Context Protocol (MGP). The apparatus is applied to a data provider, and a communication connection based on the MGP exists between the data provider and a data requester. The apparatus includes: a resource sending module for sending a resource list to the data requester; a request-response module for responding to receiving a target data request sent by the data requester according to the resource list, parsing the target data request, and obtaining a data identifier and a target transmission method in the target data request. The data identifier is determined by the data requester based on the data identifier of the data to be requested in the resource list, and the target transmission method is determined by the data requester from a preset data transmission method based on acquired data transmission service requirements; and a data sending module for determining corresponding target data based on the data identifier and the target transmission method, and sending the target data to the data provider.

[0016] The fifth aspect of this application provides an electronic device, including a memory and a processor, wherein the processor is configured to execute program instructions stored in the memory to implement the data transmission method based on the Model Context Protocol described above.

[0017] The sixth aspect of this application provides a computer-readable storage medium having program instructions stored thereon, which, when executed by a processor, implement the above-described data transmission method based on the Model Context Protocol.

[0018] The above scheme can be applied to the data requester. A communication connection based on a model context protocol exists between the data requester and the data provider. By obtaining the resource list sent by the data provider, the data that the data provider can provide can be determined. Based on the obtained data transmission service requirements, the target transmission method is determined from the preset data transmission methods. Then, based on the data identifier of the requested data and the target transmission method in the resource list, the data required by the data requester and the required transmission method can be determined, and a corresponding target data request can be generated. This target data request is then sent to the data provider, who can then return the target data based on the received target data request. Therefore, in the communication process between the data requester and the data provider based on the model context protocol, the data type and data transmission method required can be confirmed by the data requester and expressed through explicit request parameters. This allows the data provider to respond based on the received request parameters, and it is decoupled from the underlying data processing algorithm. This enables all parties involved in the communication process to interoperate by adhering to the same set of communication parameters and structural conventions, reducing integration costs and optimizing data transmission efficiency.

[0019] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this application. Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.

[0021] Figure 1 This is a schematic flowchart of an exemplary embodiment of the data transmission method based on the model context protocol of this application; Figure 2 This is a block diagram illustrating a data transmission apparatus based on a model context protocol, as shown in an exemplary embodiment of this application. Figure 3 This is a schematic diagram of the structure of an embodiment of the electronic device of this application; Figure 4 This is a schematic diagram of the structure of an embodiment of the computer-readable storage medium of this application. Detailed Implementation

[0022] The solution of this embodiment will now be described in detail with reference to the accompanying drawings.

[0023] In the following description, specific details such as particular system architectures, interfaces, and technologies are presented for illustrative purposes rather than for limiting purposes, in order to provide a thorough understanding of this application.

[0024] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, "many" in this document means two or more. Moreover, the term "at least one" in this document means any combination of at least two of any one or more of a plurality of objects. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0025] For ease of understanding, one of the applicable scenarios of this application is illustrated by example.

[0026] The Model Context Protocol (MCP) is an open-source protocol for establishing secure, bidirectional connections between large models and data sources, designed to integrate large language models with external data sources and tools. For example, data sources can use MCP to transfer data to large models for inference.

[0027] For example, in application scenarios where data acquisition devices on the edge (such as smart cameras, smart doorbells, vehicle cameras, mobile phone or tablet cameras, etc.), edge nodes (such as home gateways, store / factory edge boxes, vehicle ECUs, etc.) and large models in the cloud are collaborated through MCP, data needs to be transmitted between the edge and cloud via MCP's Resources and Tools for the large model to perform inference.

[0028] However, existing MCP-based data transmission methods typically transmit the entire data resource content at once according to the Uniform Resource Identifier (URI) in accordance with the MCP specification. For example, the entire data is read by the URI via "resources / read", or the entire data is passed as an input parameter of a tool. This method consumes a lot of bandwidth in weak network or mobile scenarios. Furthermore, the first data packet arrives late, affecting the interactive experience on the large model side (for example, in visual data transmission scenarios, it is possible to preview low-quality images before deciding whether to retrieve high-quality images), and it cannot achieve a gradual transmission of "lower layers first, then higher layers" at the protocol layer.

[0029] However, if thumbnail transmission or on-demand loading logic is used at the application layer, the data transmission process relies on Hypertext Transfer Protocol (HTTP) or Remote Procedure Call (RPC) technologies. These protocols do not specify the semantics of data transmission methods (e.g., layered transmission, incremental transmission, and / or on-demand transmission) in the URIs, content, and request parameters of Resources and Tools within MCP. If the edge-cloud architecture has uniformly adopted MCP as the data transmission interface, the above solutions cannot be directly reused on the MCP request / response path, resulting in a gap between the protocol layer and the technical solution.

[0030] Therefore, within the MCP protocol framework, how to achieve efficient and high-performance data transmission without changing the basic form of the protocol has become an urgent technical problem to be solved.

[0031] It should be noted that the data transmission method based on the model context protocol in this application can be applied to transmit data of multiple modalities as needed, depending on the specific application scenario, and is not limited here. For ease of explanation, this application mainly uses visual data as an example for the description of embodiments, and will not elaborate further thereafter.

[0032] Firstly, please refer to Figure 1 , Figure 1This is a flowchart illustrating an exemplary embodiment of the data transmission method based on the Model Context Protocol (MTP) of this application. This method can be applied to a data requester where a communication connection based on the MTP exists between the data requester and the data provider.

[0033] To facilitate understanding, some technical terms in the data transmission method based on the model context protocol of this application will be briefly explained.

[0034] MCP: Model Context Protocol, a JSON-RPC-based protocol used to transfer data sources, tools, and prompts between clients, hosts, and servers. The visual data in this application can be provided and accessed through MCP's Resources (such as resources / list, resources / read) and / or Tools.

[0035] Visual Resources: Visual data (such as images, video frames, and / or visual-related metadata) that can be exposed in MCP via resources / list and resources / read. In this solution, its URI or content can carry extended semantics such as data level, data version (baseVersion / stateId), and data requirement parameters.

[0036] Visual Tools: Visual capabilities (such as frame extraction, region-based cropping, etc.) available to the Client in MCP. The input / output parameters in this solution can be set according to the actual application scenario, such as agreeing on the data transmission method in this application (such as layered, incremental, on-demand).

[0037] Data Level: An abstract representation of visual data. For example, for a given set of visual data, its original frame format can correspond to data level L0, its decoded frames, thumbnails, etc., can correspond to data level L1, the detection results (e.g., bounding boxes + categories) obtained after performing a detection algorithm on the visual data can correspond to data level L2, further event judgments or information statistics on the visual data can correspond to data level L3, and the text description generated based on the visual data can correspond to data level L4.

[0038] In essence, the data hierarchy parameters in this application can correspond to the original information entropy of the data. For example, if L0 is the highest data hierarchy, then the data hierarchy of a certain data can be positively correlated with the original information entropy of that data; that is, the higher the data hierarchy, the higher the information entropy of the corresponding data compared to its original data (e.g., the original frame contains more information than the thumbnail). Therefore, the data hierarchy parameters can be used to specify which level of data to request or return during layered transmission.

[0039] Layered transmission: In MCP, different data layers are distinguished by the URI or content of the Resource, allowing the Client to first request the lower-level form of a certain data (such as L1) to obtain the first packet, and then request the higher-level data of the same data (such as L0) as needed; or declare the data layer through the Tool input / output parameters, thereby reducing the amount of data in the first packet and the latency.

[0040] Incremental transfer: In MCP, response messages from Resources or Tools can carry the base version identifier and / or state identifier (baseVersion / stateId) of the data, along with incremental blocks (deltaType, deltaPayload). Request messages can carry the previous state identifier (lastStateId) of a given data and whether incremental transfer is needed (needDelta), allowing the data requester to obtain only the data differences (incremental data) relative to the previous state from the data provider and merge the data, reducing redundant transfers of already obtained data.

[0041] On-demand transmission: Data requirement parameters can be carried in the MCP read request or Tool input parameters, including but not limited to one or more of the following: the time range of the required data (tStart, tEnd), region of interest (ROI), maximum resolution (maxWidth, maxHeight), and maximum number of frames (maxFrames). The server then parses the data and processes it according to the relevant parameter constraints (such as cropping, sampling, etc.) before returning it, making the amount of data transmitted precisely controllable.

[0042] MCP Server (Data Provider): Can be deployed at edge nodes (such as home gateways, store / factory edge boxes, vehicle ECUs, etc.), or at the gateway / agent on the side where the data acquisition device is located; no limitation is made here. The embodiments in this application mainly use deployment at an edge node as an example for illustration.

[0043] MCP Server can provide visual resources (resources / list, resources / read) and visual tools to the outside world. Its data source can come from edge data acquisition devices (such as smart cameras, doorbells, vehicle cameras, mobile phone / tablet cameras, etc.).

[0044] The edge device can actively push or respond to requests to collect visual data and provide it to the edge node as needed. The MCP Server on the edge node then organizes and responds to the data according to the data transmission method of this application.

[0045] MCP Client (data requester or data consumer): can be deployed in the cloud (such as cloud-based large model services, multimodal inference services, etc.) or on user terminals (such as Apps, Web, voice assistants, etc.).

[0046] The MCP Client can initiate requests such as resources / list, resources / read, or visual tool calls to the MCP Server on the edge node (or end-side gateway), carrying data transmission parameters pre-defined in this application (such as level parameters, incremental parameters (lastStateId, needDelta), and / or data requirement parameters (tStart, tEnd, roi, maxWidth, maxHeight, maxFrames), etc.). The MCP Client can receive and process the content and / or tool output parameters returned by the Server (e.g., which may contain hierarchical, incremental, or on-demand transmitted visual data) to obtain the target data.

[0047] Data acquisition devices may include, but are not limited to, devices responsible for collecting and uploading raw data or data processed using certain preset methods to edge nodes (or the node where the local MCP Server is located). They do not necessarily need to function directly as an MCP Server or MCP Client.

[0048] For ease of understanding and explanation, the MCP Server and MCP Client in this solution mainly refer to the two parties that request and respond to visual data between the edge node and the cloud through the MCP protocol, so as to avoid ambiguity in determining whether the "end device is a Client or a Server".

[0049] Specifically, the method of this application may include the following steps: Step S110: Obtain the resource list sent by the data provider.

[0050] A resource list refers to a list of data resources that a data provider can offer, such as a list of data identifiers (URIs) that can provide data.

[0051] For example, the data requester may initiate a resource list request (such as "resources / list") to the data provider and obtain the resource list of visual resources returned by the data provider; or the data provider may actively send the resource list to the data requester, which is not limited here.

[0052] Therefore, after obtaining the resource list, the data requester can specify the data to be requested to the data provider through the URI in the resource list.

[0053] Step S120: Determine the target transmission method from the preset data transmission methods based on the obtained data transmission service requirements.

[0054] For ease of understanding, the data transmission methods preset in this application are mainly illustrated by the more typical layered transmission method, incremental transmission method, and on-demand transmission method. However, this application does not limit the method to actual application scenarios. More types of data transmission methods can be set according to actual needs, which are not limited here.

[0055] For example, the methods for obtaining data transmission service requirements may include, but are not limited to, obtaining preset data transmission service requirements, and / or obtaining them according to user operation instructions, and / or obtaining them according to system-preset judgment logic, etc.

[0056] For example, the data requester can respond to user-issued operation instructions (such as data request instructions) to obtain the corresponding data transmission service requirements. Alternatively, the data requester can adaptively select the corresponding transmission method based on its own operating status (such as selecting a layered transmission method when the network environment is poor, selecting an incremental erase transmission method when a portion of a set of data has been stored, and selecting an on-demand transmission method when the amount of data in the resource list is large).

[0057] The methods for identifying the network environment, determining whether partial data of a certain data has been stored, and identifying the data volume can be set with reference to relevant technologies in this field, and will not be elaborated here. For example, the network environment can be judged by identifying transmission bandwidth and / or signal strength and then comparing it with the corresponding threshold; the partial data of a certain data can be judged by searching for stored data and / or data request logs; the data volume can be judged by identifying the number of URIs in the resource list and / or identifying the data volume information carried by each URI in the resource list and then comparing it with the corresponding threshold, etc., and will not be elaborated here.

[0058] Step S130: Send a target data request to the data provider according to the data identifier and target transmission method of the data to be requested in the resource list, and obtain the target data returned by the data provider.

[0059] Among them, the target data request is a type of MCP request. MCP request service refers to the AI ​​model sending a data request to the MCP server (such as the data provider) through an MCP client (such as the data requester) to obtain context information (reading Resource) or perform operations (calling Tool).

[0060] Based on the steps described above, after obtaining the resource list and determining the target transmission method, a target data request can be constructed according to the data identifier of the data to be requested in the resource list and the target transmission method, and then sent to the data provider. In this way, the target data returned by the data provider based on the target data request can be obtained.

[0061] It should be noted that the requested data and the target data can be in the same or different forms. That is, the target data returned by the data provider can be the requested data itself, or it can be data in other forms of the requested data (e.g., if the requested data is the initial image A, then the returned target data can be a thumbnail of the initial image A). There is no limitation here.

[0062] As can be seen, the method of this application can be applied to the data requester. A communication connection based on the Model Context Protocol exists between the data requester and the data provider. By obtaining the resource list sent by the data provider, the data that the data provider can provide can be determined. Based on the obtained data transmission service requirements, the target transmission method is determined from the preset data transmission methods. Then, based on the data identifier of the requested data and the target transmission method in the resource list, the data required by the data requester and the required transmission method can be determined, and a corresponding target data request can be generated. This target data request is then sent to the data provider, and the target data returned by the data provider based on the received target data request can be obtained. Therefore, in the communication process between the data requester and the data provider based on the Model Context Protocol, the required data type and required data transmission method can be confirmed by the data requester and expressed through explicit request parameters. This allows the data provider to respond based on the received request parameters, and it is decoupled from the underlying data processing algorithm. This enables all parties involved in the communication process to interoperate by following only the same set of communication parameters and structural conventions, reducing the interface cost and optimizing data transmission efficiency.

[0063] Based on the above embodiments, this embodiment describes the method in step S130.

[0064] The target transmission method may include a layered transmission method. This embodiment mainly illustrates the process of layered transmission.

[0065] Specifically, in this embodiment, the method of sending a target data request to the data provider based on the data identifier and target transmission method of the data to be requested in the resource list, and obtaining the target data returned by the data provider, includes at least the following steps S210 to S220: Step S210: Generate a target data request corresponding to the hierarchical transmission method based on the data identifier and the target level parameters required for the requested data; the target level parameters correspond to the original information entropy of the requested data.

[0066] The methods for constructing the target data request can be found in relevant technologies in this field, and will not be elaborated here.

[0067] It should be noted that the target data request constructed according to this embodiment needs to include at least a data identifier and target level parameters.

[0068] The target level parameter can correspond to the original information entropy of the requested data. Original information entropy refers to the information entropy contained in the requested data in its original form. For example, depending on the actual application scenario, if the original data is set to the highest data level, the level parameter and the original information entropy can be positively correlated; that is, the lower the level parameter, the less original information entropy is contained in the corresponding data form. If the original data is set to the lowest data level, the level parameter and the original information entropy can be negatively correlated; that is, the higher the level parameter, the less original information entropy is contained in the corresponding data form.

[0069] For example, in the case of visual data, where the raw data is set to the highest data level, the image data (such as RAW images, JPEG images, etc.) acquired by the data acquisition device can be the raw data (corresponding to the data level L0), and its corresponding information entropy is the raw information entropy.

[0070] For the thumbnail of the original data (corresponding to level L1, L1 < L0), the thumbnail contains less entropy of the original information compared to the original data.

[0071] Step S220: Send a target data request to the data provider and obtain the target data returned by the data provider based on the data identifier and target level parameters.

[0072] To illustrate with the steps above, if it is necessary to obtain a thumbnail from the original data (corresponding to data level L1), the data requester can construct a target data request based on the URI of the original data and the target data level L1 and send it to the data provider. In this way, the target data determined by the data provider based on the URI of the original data and the target data level L1 can be obtained.

[0073] It should be noted that the method for determining the target data based on the URI of the original data and the target data level L1 may include, but is not limited to: the data provider pre-stores the L1 level data (thumbnail) corresponding to the original data, and the thumbnail can be returned; or, if the data provider does not store the L1 level data corresponding to the original data, the original data is first found according to the URI, and then the original data is processed according to the preset data processing algorithm (such as the downsampling algorithm in this embodiment) or preset tool corresponding to the L1 data level to obtain the target data that can be returned.

[0074] Similarly, for application scenarios that request other data level parameters, the methods in the previous examples can be used for setting and execution, which will not be elaborated here.

[0075] Based on the above embodiments, this embodiment describes the method in step S220.

[0076] In scenarios where the data level parameter corresponding to the original data is the highest level parameter, the target level parameter and the original information entropy of the requested data can be positively correlated. That is, the closer the data level of the target data is to the data level of the original data, the more original information entropy the target data contains.

[0077] Specifically, the method for sending a target data request to a data provider in this embodiment includes at least the following steps S310 to S320: Step S310: In response to the initial request for requested data, a first target data request for the requested data is initiated to the data provider. The first target data request includes a first target level parameter.

[0078] Step S320: In response to a non-first request for requested data, a second target data request for the requested data is initiated to the data provider. The second target data request includes a second target level parameter, which is higher than the first target level parameter.

[0079] As illustrated in the foregoing embodiments, it is understood that the initial request for data, especially in weak network or mobile scenarios, consumes significant bandwidth, and the first packet arrives late. For example, in a visual data request, the large model might first acquire a preview image for analysis before deciding whether to acquire the original image.

[0080] Therefore, this embodiment proposes a describable, segmented request process of "first requesting a low-level level, then requesting a higher-level level", which can reduce the latency of the first packet.

[0081] For example, in a layered transmission method, the data level (first target level parameter) for the first request of the same requested data can be lower than the data level (second target level parameter) for subsequent requests. That is, when requesting data for the first time, a lower-level form of the data (such as a thumbnail) can be requested first, while when requesting the same data for subsequent requests, a higher-level form of the data (such as the original image) can be requested. Therefore, the layered transmission method of this embodiment can speed up the arrival time of the first packet and improve the interactive experience in weak network environments.

[0082] For example, the data requester may initiate a target data request to the data provider (which may include a resource read request or a tool call request), and the request URI or Tool input parameter may carry a hierarchy parameter that is not the highest data level (such as L1 in the previous example, or L2, L3, etc. can be set as needed, which will not be elaborated here).

[0083] Furthermore, after receiving a target data request, the data provider can parse the target data request and obtain the target level parameters. Based on these parameters, the provider can generate or select the corresponding data and return the content and the corresponding data level (which can be represented by an extended field such as visualLevel) in the response to the data requester.

[0084] Optionally, if the data requester needs data at a higher data level (such as L0 raw data), it can initiate a read request or Tool call request again with a higher data level parameter (such as level=L0); then the data provider can return the target data at the corresponding data level after receiving the request.

[0085] It should also be noted that in other possible implementations, if it is necessary to determine the data level of the original data as the lowest data level, the target level parameter can also be set to be negatively correlated with the original information entropy of the data to be requested, that is, starting from the data level of the original data, the higher the data level, the lower the information entropy.

[0086] Based on the above embodiments, this embodiment describes the method in step S130.

[0087] The target transmission method may include incremental transmission. This embodiment mainly illustrates the incremental transmission process.

[0088] Specifically, in this embodiment, the method of sending a target data request to the data provider based on the data identifier and target transmission method of the data to be requested in the resource list, and obtaining the target data returned by the data provider, includes at least the following steps S410 to S420: Step S410: In response to a non-first request for requested data, obtain the historical response status parameters of the requested data in the incremental transmission mode.

[0089] The response status parameter is what the data provider can return synchronously with the requested data after responding to the data request. It can be used to characterize the data status that the data requester has obtained (or it can be considered as the data status when the data provider responded to the data request).

[0090] For example, response status parameters may include a status identifier (indicating the data has been acquired) and a baseline version identifier (indicating the version of the acquired data). If the data requester has acquired a certain data, the data status identifier of that data (i.e., historical response status parameters) can be found in the history records; if the data requester has not acquired a certain data, the data status identifier of that data cannot be found in the history records.

[0091] In other words, the data requester can determine whether it is the first time it has initiated a request for the data to be requested by checking whether a status indicator for the data to be requested exists locally.

[0092] Step S420: Based on the data identifier and historical response status parameters, initiate a target data request to the data provider to obtain the target data returned by the data provider based on the data identifier and historical response status parameters.

[0093] In conjunction with the foregoing embodiments, when a data requester initiates its first request for a certain data to be requested, the target data request initiated by the data requester will not carry the historical response status parameter of that data (or the historical response status parameter is 0 or empty).

[0094] Therefore, based on the target data request that does not carry historical response status parameters (or whose historical response status parameters are 0 or empty), the data provider can know that the data requester is making a request for the data for the first time. The data provider can then return the full data or keyframe data of the requested data and attach the response status parameters (such as stateId, baseVersion, etc.) to the response.

[0095] After receiving the target data returned by the data provider, the data requester can synchronously record the response status parameters corresponding to the data to obtain historical response status parameters (such as lastStateId).

[0096] Therefore, if the data requester initiates another request for the target data from the data provider, the data requester can carry the historical response status parameters (or incremental transmission parameters) of the data in the subsequent requests, such as the historical status identifier and the incremental request flag (e.g., lastStateId, needDelta=true).

[0097] Therefore, the data provider can obtain the historical state of the requested data by parsing the request, and calculate the increment since that state based on the historical state identifier. This will give the incremental block of the data since the historical state. The provider can then return the incremental block, version information, etc. (such as baseVersion, deltaType, deltaPayload, etc., and can also include the response status parameters for this request) in the response to the data requester.

[0098] The data requester can find the local cached data of the baseline version state based on the baseVersion in the received response message, and merge deltaPayload with the data of the baseline version state according to deltaType to obtain the data of the latest version state, thus realizing the request and transmission of the incremental data part of the requested data.

[0099] Similarly, if there are multiple requests for the same data in the future, you can refer to the example method above and include the corresponding lastStateId in the target data request so that the data provider can determine the incremental data to return.

[0100] Optionally, the status identifier can also serve as a unique identifier for the data. Therefore, the data requester can include a data identifier and / or status identifier in the target data request of the incremental transmission method to locate the requested data; the data provider can also locate the requested data by using the data identifier and / or status identifier carried in the request after receiving the target data request of the incremental transmission method, which is not limited here.

[0101] Based on the above embodiments, this embodiment describes the method in step S130.

[0102] The target transmission method may include on-demand transmission. This embodiment mainly illustrates the on-demand transmission process, and will not be elaborated upon here.

[0103] Specifically, in this embodiment, the method of sending a target data request to the data provider based on the data identifier and target transmission method of the data to be requested in the resource list, and obtaining the target data returned by the data provider, includes at least the following steps S510 to S520: Step S510: Obtain the data requirement parameters corresponding to the on-demand transmission method.

[0104] The data requirement parameters may include, but are not limited to, pre-set parameters, parameters determined by user operation instructions, or parameters flexibly determined according to the task requirements of the actual application scenario; no limitation is made here.

[0105] Data requirement parameters may include, but are not limited to, one or more of the following: the time range of the required data (requirement start time tStart, requirement end time tEnd), region of interest (ROI), maximum resolution (maxWidth, maxHeight), maximum number of frames (maxFrames).

[0106] Step S520: Based on the data identifier and data requirement parameters, initiate a target data request to the data provider to obtain the target data returned by the data provider based on the data identifier and data requirement parameters.

[0107] Referring to the foregoing embodiments, in the on-demand transmission method, the target data request must at least carry a data identifier and data requirement parameters. Therefore, after parsing the target data request, the data provider can decide whether to process the requested data before returning it based on the data requirement parameters.

[0108] For example, if no data requirement parameters are provided (or the data requirement parameters are 0 or empty), the data provider can directly return the data corresponding to the data identifier.

[0109] If the data requirement parameter specifies a data time range, the data provider needs to perform time-based cropping of the requested data according to the data time range to obtain the target data for return.

[0110] If the data request parameters specify a region of interest, the data provider needs to crop the requested data based on the region of interest to obtain the target data and return it.

[0111] If the data requirement parameter specifies a target frame rate, the data provider needs to sample the requested data according to the target frame rate and return the target data.

[0112] It should be noted that a single target data request may include multiple data requirement parameters. In other words, the data provider may process the requested data multiple times according to the various data requirement parameters to obtain the target data and return it.

[0113] For example, the data requester can include data requirement parameters in the URI request body of "resources / read" or in the input parameters of the vision tool, including: time range (such as tStart, tEnd), region of interest (such as ROI), maximum resolution (such as maxWidth, maxHeight), and maximum number of frames (such as maxFrames).

[0114] The data provider receives and parses the target data request to obtain the example data requirement parameters mentioned above. Based on the data requirement parameters, the provider extracts the target data corresponding to the requested data from the original data of the data to be requested by time range, ROI cropping, downsampling by maximum resolution, and sampling by maximum frame count. The target data is then returned to the data requester as Resourcecontent or Tool output parameters.

[0115] Furthermore, the data requester can receive and process the response information returned by the data provider (e.g., displaying the target data, caching it, or forwarding it to a large model, etc., which are not limited here).

[0116] In conjunction with the foregoing embodiments, it can be noted that the various data transmission methods in this application can be selected individually or in combination, and no limitation is made here.

[0117] For example, in the target data request sent by the data requester to the data provider, one or more of the data level parameters, incremental transmission parameters, and data requirement parameters can be substituted into the target data request to combine multiple data transmission methods, that is, to constrain the data level, data volume, and data attributes of the target data corresponding to the requested data.

[0118] Secondly, this application also proposes a data transmission method based on the model context protocol, which can be applied to the data provider, where there is a communication connection between the data provider and the data requester based on the model context protocol.

[0119] Specifically, the method in this embodiment includes at least the following steps S610 to S630: Step S610: Send the resource list to the data requester.

[0120] For example, the data provider may proactively send the resource list to the data requester, and / or the data provider may send the resource list after receiving the data requester's request for the resource list; this is not limited here.

[0121] Step S620: In response to receiving a target data request sent by the data requester according to the resource list, the target data request is parsed to obtain the data identifier and target transmission method in the target data request. The data identifier is determined by the data requester according to the data identifier of the data to be requested in the resource list, and the target transmission method is determined by the data requester from the preset data transmission methods according to the obtained data transmission service requirements.

[0122] In conjunction with the steps described above, after the resource list is sent to the data requester, the data requester can determine the URI of the data to be requested based on the URI of the data that can be requested in the resource list, and generate the corresponding target data request (sent to the data provider) by combining the relevant parameters required by the target transmission method.

[0123] Therefore, the data provider can receive the target data request sent by the data requester. After parsing the target data request, the data identifier and relevant parameters of the target transmission method carried in the target data request can be obtained.

[0124] For details regarding data identification, target transmission method, etc., please refer to the explanation of the data transmission method applied to the data requester in the foregoing embodiments, which will not be repeated here.

[0125] Step S630: Determine the corresponding target data based on the data identifier and target transmission method, and send the target data to the data provider.

[0126] Based on the steps outlined above, after parsing the target data request, the data provider can determine the corresponding requested data based on the data identifier and determine the transmission method for the requested data based on the target transmission method (which may include, but is not limited to, hierarchical transmission, incremental transmission, and on-demand transmission), which will not be elaborated here.

[0127] Based on the above embodiments, this embodiment describes the method in step S630.

[0128] The target transmission method includes a layered transmission method.

[0129] Specifically, the method in this embodiment for determining the corresponding target data based on the data identifier and the target transmission method, and sending the target data to the data provider, includes at least the following steps S710 to S720: Step S710: Obtain the target layer parameters corresponding to the layered transmission method. The target layer parameters correspond to the original information entropy of the data to be requested.

[0130] Step S720: Locate the corresponding target data based on the data identifier and target level parameters, and send the target data to the data provider.

[0131] In conjunction with the foregoing embodiments, after receiving a target data request for a layered transmission method, the data provider can obtain the target layer parameters corresponding to the layered transmission method from the target data request.

[0132] Therefore, the data provider can locate the corresponding requested data based on the data identifier, generate or select target data (such as a thumbnail) corresponding to the requested data (such as the original image) according to the target level parameters, and then generate a response message based on the target data and return it to the data requester. For a detailed explanation of the data transmission method applied to the data requester in the foregoing embodiments, please refer to the previous examples; it will not be elaborated upon here.

[0133] Based on the above embodiments, this embodiment describes the method in step S630.

[0134] The target transmission method includes incremental transmission.

[0135] Specifically, the method in this embodiment for determining the corresponding target data based on the data identifier and the target transmission method, and sending the target data to the data provider, includes at least the following steps S810 to S830: Step S810: Obtain the historical response status parameters corresponding to the incremental transmission mode.

[0136] Step S820: Determine the incremental data corresponding to the data identifier based on the historical response status parameters.

[0137] Step S830: The incremental data is identified as the target data and sent to the data provider.

[0138] In conjunction with the foregoing embodiments, after receiving a target data request in the incremental transmission mode, the data provider can obtain the historical response status parameters corresponding to the incremental transmission mode from the target data request.

[0139] Therefore, the data provider can locate the corresponding requested data based on the data identifier, determine the incremental data of the requested data since the state of the historical response status parameters, identify the incremental data as the target data, and then generate a response message based on the target data and return it to the data requester. For a detailed explanation of the data transmission method applied to the data requester in the foregoing embodiments, it will not be repeated here.

[0140] Alternatively, the data provider can directly determine the incremental data corresponding to the requested data based on historical response status parameters, etc., without limitation here.

[0141] It should be noted that if the target data request received by the data provider does not carry incremental transmission parameters (such as historical response status parameters), or the incremental transmission parameters are empty or 0, it can be indicated that the data requester is initiating a request for the data to be requested corresponding to the target data request for the first time.

[0142] Therefore, the data provider can find the corresponding requested data based on the data identifier, and can choose to return the full data (or keyframe data, etc.) of the requested data corresponding to the data identifier as the target data, without any limitation here.

[0143] Based on the above embodiments, this embodiment describes the method in step S630.

[0144] The target transmission method includes on-demand transmission.

[0145] Specifically, the method in this embodiment for determining the corresponding target data based on the data identifier and the target transmission method, and sending the target data to the data provider, includes at least the following steps: After receiving the target data request for the on-demand transmission method, the data provider can obtain the data requirement parameters corresponding to the on-demand transmission method from the target data request.

[0146] Therefore, the data provider can locate the corresponding requested data based on the data identifier, determine the target data corresponding to the data requirement parameters from the requested data, and then generate a response message based on the target data and return it to the data requester. For a detailed explanation of the data transmission method applied to the data requester in the foregoing embodiments, the specific implementation process will not be elaborated here.

[0147] In summary, the data transmission method based on the Model Context Protocol in this application delegates the decision-making power regarding "the required data level, the required time / region / resolution / frame count, and whether full or incremental transmission is required" to the data requester. The data requester expresses its needs through explicit request parameters, and the data provider responds according to the received parameters.

[0148] This architecture differs from the existing design in traditional methods, where "the data provider / server makes unilateral decisions based on channel, encoding, or content analysis," in terms of control and decision-making authority. It is more suitable for the mode in which the cloud or user terminal actively pulls visual data according to business needs in the end-edge-cloud scenario, and it is easy to flexibly combine with algorithms such as caching, transmission retry, and degradation strategies.

[0149] For example, the semantics of layered transmission, incremental transmission, and on-demand transmission in this application are all pre-defined in the parameters and structure of the request / response, decoupled from the underlying data processing algorithms (such as compression algorithms, encoding / decoding formats, and content analysis algorithms (such as clarity requirements and motion estimation)). When different algorithms are used, interoperability can be maintained as long as the same set of parameter conventions is followed, reducing the interface cost and facilitating the formation of a stable and scalable data interface between edge nodes and the cloud.

[0150] Especially in visual data transmission scenarios, where the visual service provider (edge ​​node) provides visual resources / tools, and the cloud or user terminal acts as the visual data requester to pull data, this proposal uses layered transmission. This allows the first packet to contain only low-level data, quickly presenting an image preview, and then pulling higher-level data on demand. This reduces the latency of the first packet and improves the "see first, then retrieve" experience for large models or applications. At the same time, it can reduce unnecessary full transmissions through on-demand transmission and reduce repeated transmissions in continuous states through incremental transmission, thus adapting to the constraints of edge bandwidth and cloud computing power.

[0151] It should be further noted that the execution entity of the model context protocol-based data transmission method can be a model context protocol-based data transmission device. For example, the model context protocol-based data transmission method can be executed by a terminal device, a server, or other processing devices. The terminal device can be a user equipment (UE), computer, mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, in-vehicle device, wearable device, etc. In some possible implementations, this model context protocol-based data transmission method can be implemented by the processor calling computer-readable instructions stored in memory.

[0152] Figure 2 This is a block diagram illustrating a data transmission apparatus based on the Model Context Protocol (MGP) as an exemplary embodiment of this application. This apparatus can be applied to a data requester, where a communication connection based on the MGP exists between the data requester and the data provider. Figure 2 As shown, this exemplary data transmission device 200 based on the Model Context Protocol includes: an acquisition module 210, a transmission determination module 220, and a data request module 230. Specifically: The acquisition module 210 is used to acquire the resource list sent by the data provider.

[0153] The transmission determination module 220 is used to determine the target transmission method from the preset data transmission methods based on the acquired data transmission service requirements.

[0154] The data request module 230 is used to send a target data request to the data provider according to the data identifier and target transmission method of the data to be requested in the resource list, and to obtain the target data returned by the data provider.

[0155] In this exemplary data transmission device based on the Model Context Protocol (MGP), a communication connection based on MGP exists between the data requester and the data provider. By obtaining the resource list sent by the data provider, the data that the data provider can provide can be determined. Based on the obtained data transmission service requirements, the target transmission method is determined from the preset data transmission methods. Then, based on the data identifier of the requested data and the target transmission method in the resource list, the data required by the data requester and the required transmission method can be determined, and a corresponding target data request can be generated. The target data request is then sent to the data provider, and the target data returned by the data provider based on the received target data request can be obtained. Thus, in the communication process between the data requester and the data provider based on the MGP, the required data type and required data transmission method can be confirmed by the data requester and expressed through explicit request parameters. The data provider can then respond according to the received request parameters. Furthermore, it is decoupled from the underlying data processing algorithm, enabling all parties involved in the communication process to interoperate by following only the same set of communication parameters and structural conventions, reducing the docking cost and optimizing data transmission efficiency.

[0156] Additionally, this application also provides a block diagram of a data transmission apparatus based on the Model Context Protocol (MGP). This apparatus can be applied to a data provider, where a communication connection based on the MGP exists between the data requester and the data provider. This exemplary MGP-based data transmission apparatus may include: The resource sending module is used to send a list of resources to the data requester.

[0157] The request-response module is used to respond to a target data request sent by a data requester based on a resource list, parse the target data request, and obtain the data identifier and target transmission method in the target data request. The data identifier is determined by the data requester based on the data identifier of the data to be requested in the resource list, and the target transmission method is determined by the data requester from a preset data transmission method based on the obtained data transmission service requirements.

[0158] The data sending module is used to determine the corresponding target data based on the data identifier and the target transmission method, and to send the target data to the data provider.

[0159] It should be noted that the apparatus and method provided in the above embodiments belong to the same concept, and the specific ways in which each module and unit performs operations have been described in detail in the method embodiments, and will not be repeated here. In practical applications, the apparatus provided in the above embodiments can be assigned to different functional modules as needed, that is, the internal structure of the apparatus can be divided into different functional modules to complete all or part of the functions described above, and this is not a limitation.

[0160] The functions of each module can be found in the implementation examples of the data transmission method based on the model context protocol, and will not be repeated here.

[0161] Please see Figure 3 , Figure 3 This is a schematic diagram of the structure of an embodiment of the electronic device of this application. The electronic device 100 includes a memory 101 and a processor 102. The processor 102 is used to execute program instructions stored in the memory 101 to implement the steps in any of the above-described embodiments of the data transmission method based on the Model Context Protocol. In a specific implementation scenario, the electronic device 100 may include, but is not limited to, a microcomputer or a server. In addition, the electronic device 100 may also include mobile devices such as laptops and tablets, which are not limited here.

[0162] Specifically, processor 102 controls itself and memory 101 to implement the steps in any of the above-described embodiments of the data transmission method based on the model context protocol. Processor 102 may also be referred to as a CPU (Central Processing Unit). Processor 102 may be an integrated circuit chip with signal processing capabilities. Processor 102 may also be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. A general-purpose processor may be a microprocessor or any conventional processor. Furthermore, processor 102 may be implemented using integrated circuit chips.

[0163] In this exemplary electronic device, a communication connection based on a Model Context Protocol exists between the data requester and the data provider. By obtaining the resource list sent by the data provider, the data that the data provider can provide can be determined. Based on the obtained data transmission service requirements, the target transmission method is determined from the preset data transmission methods. Then, based on the data identifier of the data to be requested in the resource list and the target transmission method, the data required by the data requester and the required transmission method can be determined, and a corresponding target data request can be generated. The target data request is then sent to the data provider, and the target data returned by the data provider based on the received target data request can be obtained. Thus, in the communication process between the data requester and the data provider based on the Model Context Protocol, the required data type and required data transmission method can be confirmed by the data requester and expressed through explicit request parameters. The data provider can then respond according to the received request parameters. Furthermore, this is decoupled from the underlying data processing algorithm, enabling all parties involved in the communication process to interoperate by following only the same set of communication parameters and structural conventions, reducing the docking cost and optimizing data transmission efficiency.

[0164] Please see Figure 4 , Figure 4 This is a schematic diagram of a computer-readable storage medium according to an embodiment of the present application. The computer-readable storage medium 110 stores program instructions 111 that can be executed by a processor. The program instructions 111 are used to implement the steps in any of the above embodiments of the data transmission method based on the Model Context Protocol.

[0165] In this exemplary storage medium, by running program instructions within the storage medium, the data requester obtains a resource list sent by the data provider, thus understanding the data the data provider can offer. Based on the obtained data transmission service requirements, it determines the target transmission method from a preset set of data transmission methods. Then, based on the data identifier of the requested data in the resource list and the target transmission method, it determines the data required by the data requester and the required transmission method, generates a corresponding target data request, and sends the target data request to the data provider. The data provider then returns the target data based on the received target data request. Therefore, in the communication process between the data requester and the data provider based on the model context protocol, the data type and data transmission method required can be confirmed by the data requester and expressed through explicit request parameters. This allows the data provider to respond based on the received request parameters, and it is decoupled from the underlying data processing algorithm. This enables interoperability between the participating parties in the communication process by adhering to the same set of communication parameters and structural conventions, reducing integration costs and optimizing data transmission efficiency.

[0166] In some embodiments, the functions or modules of the apparatus provided in this disclosure can be used to perform the methods described in the above method embodiments. The specific implementation can be referred to the description of the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0167] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to, and for the sake of brevity, they will not be repeated here.

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

[0169] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A data transmission method based on a model context protocol, characterized in that, The method is applied to a data requester, where a communication connection based on the model context protocol exists between the data requester and the data provider. The method includes: Obtain the list of resources sent by the data provider; The target transmission method is determined from the preset data transmission methods based on the obtained data transmission service requirements; Based on the data identifier of the data to be requested in the resource list and the target transmission method, a target data request is sent to the data provider, and the target data is returned by the data provider.

2. The method according to claim 1, characterized in that, The target transmission method includes a hierarchical transmission method. The step of sending a target data request to the data provider based on the data identifier of the data to be requested in the resource list and the target transmission method, and obtaining the target data returned by the data provider, includes: Based on the data identifier and the target layer parameters required for the requested data, a target data request corresponding to the layered transmission method is generated; the target layer parameters correspond to the original information entropy of the requested data. Send the target data request to the data provider and receive the target data returned by the data provider based on the data identifier and the target level parameter.

3. The method according to claim 2, characterized in that, The target level parameter is positively correlated with the original information entropy of the requested data, and sending the target data request to the data provider includes: In response to the initial request for the requested data, a first target data request for the requested data is initiated to the data provider, the first target data request including a first target level parameter; In response to a non-first request for the requested data, a second target data request for the requested data is initiated to the data provider. The second target data request includes a second target level parameter, which is higher than the first target level parameter.

4. The method according to claim 1, characterized in that, The target transmission method includes an incremental transmission method. The step of sending a target data request to the data provider based on the data identifier of the data to be requested in the resource list and the target transmission method, and obtaining the target data returned by the data provider, includes: In response to a non-first request for the requested data, the historical response status parameters of the requested data in the incremental transmission method are obtained. Based on the data identifier and the historical response status parameters, a target data request for the requested data is initiated to the data provider, and the target data returned by the data provider based on the data identifier and the historical response status parameters is obtained.

5. The method according to claim 1, characterized in that, The target transmission method includes an on-demand transmission method. The step of sending a target data request to the data provider based on the data identifier of the data to be requested in the resource list and the target transmission method, and obtaining the target data returned by the data provider, includes: Obtain the data requirement parameters corresponding to the on-demand transmission method; Based on the data identifier and the data requirement parameters, a target data request for the requested data is initiated to the data provider, and the target data returned by the data provider based on the data identifier and the data requirement parameters is obtained.

6. A data transmission method based on a model context protocol, characterized in that, The method is applied to a data provider, and a communication connection based on the model context protocol exists between the data provider and the data requester. The method includes: Send the resource list to the data requester; In response to receiving a target data request sent by the data requester according to the resource list, the target data request is parsed to obtain the data identifier and target transmission method in the target data request. The data identifier is determined by the data requester according to the data identifier of the data to be requested in the resource list, and the target transmission method is determined by the data requester from a preset data transmission method according to the obtained data transmission service requirements. The corresponding target data is determined based on the data identifier and the target transmission method, and the target data is sent to the data provider.

7. The method according to claim 6, characterized in that, The target transmission method includes a hierarchical transmission method. The step of determining the corresponding target data based on the data identifier and the target transmission method, and sending the target data to the data provider, includes: Obtain the target layer parameter corresponding to the layered transmission method, wherein the target layer parameter corresponds to the original information entropy of the data to be requested; The corresponding target data is located based on the data identifier and the target level parameter, and the target data is sent to the data provider.

8. The method according to claim 6, characterized in that, The target transmission method includes an incremental transmission method. The step of determining the corresponding target data based on the data identifier and the target transmission method, and sending the target data to the data provider, includes: Obtain the historical response status parameters corresponding to the incremental transmission method; The incremental data corresponding to the data identifier is determined based on the historical response status parameters; The incremental data is identified as the target data and sent to the data provider.

9. An electronic device, characterized in that, The method includes a memory and a processor, the processor being configured to execute program instructions stored in the memory to implement the method according to any one of claims 1 to 8.

10. A computer-readable storage medium having program instructions stored thereon, characterized in that, When the program instructions are executed by the processor, they implement the method described in any one of claims 1 to 8.

Images