Resource processing method and apparatus

Abstract

Embodiments of the present specification provide a resource processing method and device, wherein the resource processing method comprises: being applied to a target resource processing node, the target resource processing node comprising a communication component, the method comprising: creating a resource processing container in response to a resource processing request, and determining container attribute information corresponding to the resource processing container; establishing a communication channel between the communication component and the resource processing container according to the container attribute information; determining to-be-processed resource information corresponding to the resource processing container, and performing resource detection on an initial resource processing node according to the to-be-processed resource information; in the case where it is detected that the initial resource processing node has to-be-processed resources, calling the communication component to obtain the to-be-processed resources, and sending the to-be-processed resources to the resource processing container through the communication channel. Through the connection of the communication component and the resource processing container and the establishment of the communication channel, subsequent resource acquisition or sending is based on the communication channel, avoiding the attack on the resource processing container, and improving the security of the connection.

Description

Technical Field

[0001] This specification relates to the field of Internet technology, and in particular to a resource processing method. One or more embodiments of this specification also relate to a resource processing apparatus, a resource processing system, a computing device, and a computer-readable storage medium. Background Technology

[0002] With the rapid development of internet technology, more and more users are choosing to use container cloud services with serverless architecture. Serverless architecture is a new type of internet architecture. Compared with server-based architecture, the biggest feature of serverless is the on-demand use of services, reducing the total cost of maintaining applications and enabling the construction of more logic faster. It is widely used in hybrid container clouds. For multi-tenant scenarios in serverless architecture, for the sake of data security isolation between tenants, project teams store container image management in secure containers. This results in each node needing to cache container images separately, and the container images needing to be re-cached when an instance is scheduled to another node, which is detrimental to container instance startup. Therefore, in multi-tenant scenarios in serverless architecture, how to ensure data isolation between tenants while improving the startup speed of container instances is a pressing issue that needs to be addressed. Summary of the Invention

[0003] In view of the above, embodiments of this specification provide a resource processing method. One or more embodiments of this specification also relate to a resource processing apparatus, a resource processing system, a computing device, a computer-readable storage medium, and a computer program, to address the technical deficiencies existing in the prior art.

[0004] According to a first aspect of the embodiments of this specification, a resource processing method is provided, applied to a target resource processing node, the target resource processing node including a communication component, the method comprising:

[0005] In response to a resource processing request, a resource processing container is created, and the container attribute information corresponding to the resource processing container is determined;

[0006] A communication channel is established between the communication component and the resource processing container based on the container attribute information;

[0007] Determine the resource information to be processed corresponding to the resource processing container, and perform resource detection on the initial resource processing node based on the resource information to be processed;

[0008] If the initial resource processing node detects that there are resources to be processed, the communication component is invoked to obtain the resources to be processed, and the resources are sent to the resource processing container through the communication channel.

[0009] According to a second aspect of the embodiments of this specification, a resource processing apparatus is provided, applied to a target resource processing node, the target resource processing node including a communication component, the apparatus comprising:

[0010] The determination module is configured to create a resource processing container in response to a resource processing request and determine the container attribute information corresponding to the resource processing container;

[0011] The module is configured to establish a communication channel between the communication component and the resource processing container based on the container attribute information.

[0012] The detection module is configured to determine the resource information to be processed corresponding to the resource processing container, and to perform resource detection on the initial resource processing node based on the resource information to be processed.

[0013] The sending module is configured to, upon detecting that there are resources to be processed on the initial resource processing node, invoke the communication component to obtain the resources to be processed and send them to the resource processing container through the communication channel.

[0014] According to a third aspect of the embodiments of this specification, a resource processing system is provided, wherein the target resource processing node includes a communication component; the target resource processing node is configured to store a communication channel establishment executable instruction; and when the communication channel establishment executable instruction is executed by the target resource processing node, it implements the steps of the resource processing method.

[0015] According to a fourth aspect of the embodiments of this specification, a computing device is provided, including a memory, a processor, and computer instructions stored in the memory and executable on the processor, wherein the processor executes the computer instructions to implement the steps of the resource processing method.

[0016] According to a fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores computer instructions which, when executed by a processor, implement the steps of the resource processing method.

[0017] According to a sixth aspect of the embodiments of this specification, a computer program is provided, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of the resource processing method described above.

[0018] The resource processing method provided in this specification is applied to a target resource processing node, which includes a communication component. The method includes: creating a resource processing container in response to a resource processing request and determining container attribute information corresponding to the resource processing container; establishing a communication channel between the communication component and the resource processing container based on the container attribute information; determining unprocessed resource information corresponding to the resource processing container and performing resource detection on the resource processing node based on the unprocessed resource information; and, if unprocessed resources are detected on the initial resource processing node, calling the communication component to obtain the unprocessed resources and sending them to the resource processing container through the communication channel.

[0019] One embodiment of this specification implements a method whereby, after creating a resource processing container on a target resource processing node, and while running the resource processing container to acquire the corresponding resources to be processed, a communication component connects to the resource processing container and establishes a communication channel. Subsequent resource acquisition and transmission are based on this communication channel, preventing attacks on the resource processing container and improving connection security. Furthermore, resource detection is performed on the initial resource processing node using the information of the resources to be processed. If resources to be processed are detected on the initial resource processing node, the communication component is invoked to retrieve the shared resources from the initial resource processing node. Compared to retrieving resources from the original database, this reduces the resource acquisition time of the resource processing container, thereby improving its operating speed. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the structure of a resource sharing network in a resource processing method provided in one embodiment of this specification;

[0021] Figure 2 This is a flowchart illustrating a resource processing method provided in one embodiment of this specification;

[0022] Figure 3 This is a flowchart illustrating the processing procedure of a resource processing method provided in one embodiment of this specification.

[0023] Figure 4 This is a schematic diagram of the structure of a resource processing device provided in one embodiment of this specification;

[0024] Figure 5 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0025] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0026] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to any or all possible combinations including one or more of the associated listed items.

[0027] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0028] First, the terms and concepts used in one or more embodiments of this specification will be explained.

[0029] Serverless: Serverless architecture is a new type of internet architecture. Compared with server architecture, the biggest feature of serverless is that services are used on demand, reducing the total cost of maintaining applications and enabling the construction of more logic faster. It is widely used in hybrid container clouds.

[0030] ECI: Elastic Container Instance, is a secure serverless container runtime service. Users only need to provide a packaged Docker image to run the container.

[0031] Currently, for security isolation in multi-tenant storage, container image management is also placed in secure containers. While this improves data security, it sacrifices the performance gains from data sharing. For example, if an instance on a node downloads and uses a certain image, other instances on the same node need to download and prepare the image again, resulting in slow container instance startup. The existing solution to this problem is to set up a separate caching system on each node. Container instances on that node can download container images from this caching system. However, there is no speedup effect when a container instance on that node first obtains the container image; it still needs to download and cache it from the original database. Furthermore, when a container instance is scheduled from that node to another node, it cannot obtain the image resources from the original node, still leading to a slowdown in container instance startup.

[0032] Based on this, this specification provides a resource processing method to improve the startup and running speed of container instances on each resource processing node, and to ensure data isolation between container instances of each tenant, thereby improving data security. This specification also relates to a resource processing apparatus, a resource processing system, a computing device, a computer-readable storage medium, and a computer program, which will be described in detail in the following embodiments.

[0033] Figure 1This diagram illustrates the structure of a resource-sharing network in a resource processing method according to an embodiment of this specification. The resource-sharing network includes resource scheduling nodes, resource processing nodes, and a raw database. The resource scheduling nodes are used to schedule the creation of container instances on each resource processing node, thereby achieving load balancing and preventing a single resource processing node from carrying too many container instances while other resource processing nodes remain idle, which could lead to node crashes due to excessive load and operational pressure. In specific implementations, multiple resource scheduling nodes can be set up in the resource-sharing network to avoid single-node failures. Resource processing nodes are nodes that provide the required services to corresponding tenants. The number of resource processing nodes can be multiple. In the resource-sharing network, resource processing nodes act as peer nodes in a P2P network, used to share resources with other resource processing nodes. When a resource scheduling node schedules a resource processing node to run a service, a container instance running that service is created on that resource processing node. To run the container instance, the corresponding container image for that service needs to be obtained. First, a resource query is performed on other resource processing nodes. If the container image has already been obtained on other resource processing nodes, it can be obtained from those nodes. If the container image is not available on other resource processing nodes, it needs to be downloaded from the original database. The container image can then be cached on the shared file system for use by other resource processing nodes. Compared to downloading the container image from other resource processing nodes, this reduces the data download pressure on the original database, and the better bandwidth between nodes improves the image download speed, thereby shortening the container instance startup time. To ensure security isolation between container instances of different tenants, a communication component can be configured on each resource processing node to connect with the container instances on the node, preventing DDoS attacks initiated by the container instances and ensuring data isolation and security between different tenants. Figure 1 The resource processing nodes include UserA's rund1 (container instance 1) and rund2, and UserB's rund1. The two container instances of a user on this node share image resources, but do not share them with UserB's container instance. When UserA creates a container instance on another resource processing node, it can also obtain the shared image resources on that node, thereby ensuring data isolation between multiple tenants.

[0034] Figure 2 A flowchart of a resource processing method according to an embodiment of this specification is shown, including steps 202 to 208.

[0035] Step 202: In response to the resource processing request, create a resource processing container and determine the container attribute information corresponding to the resource processing container.

[0036] In this context, a resource processing request can be understood as a processing request sent by a user through a container orchestration and scheduling system. This request can be for deploying, scaling, and managing containerized applications. The container orchestration and scheduling system can be, for example, Kubernetes (K8S), but is not limited to this. After a user issues a resource processing request, the resource scheduling node determines the target resource processing node in the resource-shared network to respond to the request. The application corresponding to the resource processing request then runs on the target resource processing node. All other resource processing nodes in the resource-shared network besides the target resource processing node are considered initial resource processing nodes.

[0037] In practical applications, the target resource processing node is equipped with a container management component (containerd). This component manages the containers on the resource processing node based on resource processing requests. After receiving a resource processing request, the container management component creates and initializes a resource processing container on the target resource processing node and determines the container attribute information. The container attribute information can be understood as the attribute information associated with the resource processing container. This information may include: a container ID (used to identify a unique file path name when sharing data later); a security container ID (a security container can be understood as a small virtual machine responsible for managing container images); and a tenant ID (which can be a user's custom account, name, etc.). This container attribute information can be used to establish connections with communication components later.

[0038] In a specific embodiment of this specification, user A wants to run an application and issues a resource processing request in the K8S system. The resource scheduling node in the resource sharing network determines that the resource processing node responding to this resource processing request is resource processing node 1, and then determines resource processing node 1 as the target resource processing node. Other resource processing nodes in the resource sharing network are the initial resource processing nodes. A resource processing container is created on the target resource processing node to run the application. It is also necessary to determine the container attribute information corresponding to the resource processing container. The container attribute information includes container ID, virtual container ID, and user ID.

[0039] Furthermore, to avoid identifying container attribute information that does not correspond to the resource processing container, the container attribute information can be determined by monitoring the network interface of the resource processing container, ensuring the correctness of the container attribute information. Specifically, determining the container attribute information corresponding to the resource processing container includes: monitoring the network port of the resource processing container and determining the container identification information and user identification information corresponding to the resource processing container based on the monitoring results; and generating the container attribute information corresponding to the resource processing container based on the container identification information and the user identification information.

[0040] The network port of the resource processing container can be understood as the vsock port of the resource processing container. The network port is used to enable the resource processing container to communicate with the external network. When creating a resource processing container, if no port mapping is specified, the resource processing container is closed and cannot communicate with the external network. Specifying port mapping allows tenants to access the container through the host's port. After the security container (image-service) in the resource processing container starts successfully, by listening to the network port of the resource processing container, the container identification information of the resource processing container can be determined, including the container SID, the security container vsockID, and the user identification information, i.e., the user ID. Based on the container identification information and the user identification information, the container attribute information corresponding to the resource processing container can be generated, which facilitates the subsequent call to the communication component to connect to the corresponding resource processing container based on the container attribute information.

[0041] In practical applications, after the container management component initializes the container instance and confirms that the secure container of the container instance has started successfully, it will start listening to the corresponding network port, determine the container identification information and user identification information based on the listening results, and generate the container attribute information corresponding to the container instance. Subsequently, the container attribute information can be sent to the communication component to tell the communication component that the container instance has started running.

[0042] In a specific embodiment of this specification, after the resource processing container rund1 is created on resource processing node 1, the listener starts listening to the vsock port corresponding to rund1. Then, based on the listening result, the container identification information SID, vsockID and user identification information UID are determined to generate container attribute information, and the container attribute information is sent to the communication component.

[0043] Based on this, by listening to the network port of the resource processing container, the container attribute information of the resource processing container can be accurately obtained according to the real-time listening results, which makes it easier for subsequent communication components to connect to the corresponding resource processing container based on the container attribute information.

[0044] Step 204: Establish a communication channel between the communication component and the resource processing container based on the container attribute information.

[0045] After determining the container attribute information of the resource processing container, the container management component sends the container attribute information to the communication component. The communication component actively connects to the corresponding resource processing container based on the received container attribute information, and establishes a secure connection, i.e., a communication channel, between the communication component and the resource processing container.

[0046] In practical applications, the resource management container includes a resource-sharing component, dfdaemon, which shares the container's image data with the resource-sharing network for other resource processing nodes to download. Normally, the resource-sharing component acts as the server, and the image-service within the resource processing container acts as the dfdaemon client, sending resource retrieval requests to the resource-sharing component to download the resource data from the network. However, for data security reasons, it's not allowed for the resource processing container to initiate connections to the management service. Therefore, the resource-sharing component must initiate a connection to the resource management container. Since the resource processing container itself lacks a network, a VSock is used for the connection. To address data security, a communication component, dfproxy, is included in the resource management container. This component actively connects to the corresponding resource processing container based on its container attributes, establishing a communication channel between the component and the container.

[0047] Based on this, by setting up a communication component in the resource processing container, the resource processing container can connect with the outside world based on the communication component, thus avoiding DDoS attacks initiated from the resource processing container and ensuring the security of the connection.

[0048] Furthermore, since there are multiple container instances on the resource processing node, in order to prevent the communication component from establishing incorrect communication channels, the communication component needs to determine the corresponding resource processing container for connection based on the container attribute information. Specifically, establishing a communication channel between the communication component and the resource processing container based on the container attribute information includes: sending the container attribute information to the communication component; calling the communication component to establish a communication connection with the resource processing container based on the container attribute information; and establishing a communication channel between the communication component and the resource processing container based on the connection result.

[0049] Since the container attribute information includes container identification information, after the container attribute information is sent to the communication component, the communication component can determine the resource processing container that needs to be connected based on the container identification information, thereby establishing a communication channel between the communication component and the resource processing container.

[0050] In practical applications, the communication component dfproxy determines the resource processing container that needs to be connected based on the container identifier information in the container properties, and establishes a communication channel between the communication component and the resource processing container. Once the connection between the communication component and the resource processing container is established, the resource processing container can send a resource acquisition request to the communication component through the communication channel. The communication component then forwards the resource acquisition request to the local resource sharing component dfdaemon, and subsequently forwards the result returned by the resource sharing component to the resource management container through the communication channel.

[0051] Based on this, by actively establishing a communication connection between the communication component and the resource processing container and setting up a communication channel between the communication component and the resource processing container, it can be ensured that each resource processing container can only have one connection with the communication component, thus avoiding DDoS attacks initiated by the resource processing container and ensuring the security of the connection.

[0052] Step 206: Determine the resource information to be processed corresponding to the resource processing container, and perform resource detection on the initial resource processing node based on the resource information to be processed.

[0053] The pending resource information can be understood as the information about the resources required by the resource processing container during runtime. Based on this information, the image resources needed by the resource processing container can be determined, and subsequent resource detection can be performed on other resource processing nodes. The pending resource information may include resource file information and user information. The initial resource processing node can be understood as a resource processing node other than the target resource processing node in the resource-sharing network. The initial and target resource processing nodes exist in the same P2P network, and nodes can share data resources. Therefore, after obtaining the pending resource information, resource detection can be performed on the initial resource processing node based on this information. This involves checking whether the pending resource has been cached on the initial resource processing node. If it has, the pending resource can be directly obtained from the initial resource processing node, improving the resource acquisition speed of the target resource processing node.

[0054] In practical applications, since a resource-sharing network includes multiple different resource processing nodes, the same tenant can deploy the same service on different resource processing nodes. Therefore, resource processing containers on different resource processing nodes may obtain the same container image data. In specific implementations, different resource processing nodes can be centrally deployed on the same physical device or virtual machine, or they can be distributed across multiple physical devices or virtual machines. Therefore, when a tenant creates a container instance on a certain resource processing node, the container image data needs to be re-cached. To improve the caching efficiency of container image data, it can be obtained from the cached initial resource processing node through the resource-sharing network. Therefore, resource detection of the initial resource processing node in the resource-sharing network needs to be performed based on the resource information to be processed.

[0055] In a specific embodiment of this specification, the resource information to be processed corresponding to the resource processing container is determined to be the file identifier information and user identifier information corresponding to the file. Based on the resource information to be processed, resource detection is performed in the initial resource processing node, that is, based on the resource information to be processed, a search is performed in the initial resource processing node to check whether there is a file corresponding to the user in the initial resource processing node. If there is, it is determined that there is a resource to be processed in the initial resource processing node; otherwise, it is determined that there is no resource to be processed in the initial resource processing node.

[0056] Furthermore, since multiple tenants may deploy container instances on a resource processing node, it is also necessary to ensure data security between different users, i.e., multi-tenant isolation between users, in order to prevent the leakage of tenant resource data. Therefore, user identification information needs to be added to the resource information to be processed for subsequent verification of data usage permissions. Specifically, determining the resource information to be processed corresponding to the resource processing container includes: receiving the resource acquisition request sent by the resource processing container through the communication component, determining the resource attribute information carried in the resource acquisition request; extracting the user identification information from the container attribute information, and generating the resource information to be processed based on the user identification information and the resource attribute information.

[0057] A resource acquisition request can be understood as a request from a resource processing container to acquire a corresponding resource to be processed. For a resource processing container to run, it needs to acquire the corresponding resource to be processed, which is the container image data corresponding to the resource processing container. The resource acquisition request carries resource attribute information, which can be understood as the attribute information corresponding to the resource to be processed. This resource attribute information includes file identification information. In the dragonfly2cache file distribution system, each cached file has a unique cacheID. To prevent other users from acquiring the current user's container image, a user identifier can be added to the cache file's identifier, thus generating the resource information to be processed. This ensures that subsequent users who want to acquire the same resource data will only be able to obtain it using the same file identifier and user identifier information.

[0058] In practice, since each cache file has a unique cacheID, and a tag can be added based on the user identifier, a taskID is generated internally within the cache system. This taskID serves as the verification information for subsequently retrieving the file. In practical applications, the taskID can be obtained using Formula 1, as follows:

[0059] taskID=hash(cacheID+tagID) formula 1

[0060] In this system, `taskID` is the internal identifier of the resource file, `cacheID` is the file identifier of the resource file (resource files within the same image have the same `cacheID`), and `tagID` is the user identifier. The internal identifier `taskID` of each resource cache file is equal to the hash value of `cacheID` plus `tagID`. Within the resource processing container, the container image ID can be used as the cache ID of the caching system, and the user's UID can be used as the tag ID. This way, even if the `cacheID` is the same, other users cannot access the current user's data because their UIDs are different, achieving secure multi-tenancy isolation. Furthermore, to prevent potential attacks on the resource processing container, user identifiers cannot be provided by the resource processing container itself, such as if a user escapes from the container. Therefore, user identifiers must be transparently provided by a trusted management component outside the resource processing container, preventing users from entering arbitrary UIDs to spy on other users' data.

[0061] In practice, user identification information can be added to the communication component dfproxy. The resource processing container only needs to provide the cacheID and then send the resource processing request to the communication component. The communication component generates a specific taskID based on the user identification information sent by containerd and forwards it to dfdaemon. In this way, each container instance can only see the data with the corresponding user identification information, which truly achieves data security for multi-tenant users.

[0062] In a specific embodiment of this specification, a resource acquisition request sent by a resource processing container is received through a communication component. The resource attribute information carried in the resource acquisition request is determined. The resource attribute information includes the file ID of the image file. The resource attribute information is used as a cacheID. The hash value of the user's user identifier information and the resource attribute information is used to generate a taskID for the resource information to be processed. Subsequently, resource detection can be performed on the initial resource processing node based on the taskID.

[0063] In summary, by adding user identification information to the file identifier of each image cache file, each resource processing container can only see the image cache files of the corresponding user, thus avoiding the possibility of user data leakage.

[0064] Furthermore, to prevent malicious users from obtaining other users' data, information verification can be performed when the resource processing container obtains resources from other resource processing nodes. Only after successful verification can the corresponding resources be provided to the node. Specifically, resource detection is performed on the initial resource processing node based on the resource information to be processed, including: determining the initial resource sharing information corresponding to the initial resources in the initial resource processing node; verifying the resource information to be processed based on the initial resource sharing information; and determining the resource detection result of the initial resource processing node based on the verification result.

[0065] The initial resource can be understood as the image resource cached in the initial resource processing node, and the initial resource sharing information can be understood as the internal file identifier corresponding to the initial resource, that is, the taskID corresponding to the initial resource. By using the initial resource to verify the information of the resource sharing information to be processed, it can be determined whether the current user has the permission to obtain the image resource.

[0066] In practical applications, the taskID of the initial resource is used to verify the taskID of the resource to be processed. If the two are the same, it means that the current user's resource processing container has permission to obtain the image resource file. Based on the verification result, it can be determined that there is a resource to be processed corresponding to the resource processing container on the initial resource processing node. If the two are different, it means that the current user's resource processing container does not have permission to obtain the image resource file. Based on the verification result, the detection result that there is a resource to be processed on the initial resource processing node can be not reported to the resource processing container. The resource processing container will not be able to query the resource to be processed on the initial resource processing node, thereby avoiding the leakage of user resource data.

[0067] Based on this, by comparing and verifying the initial resource sharing information of the initial resources on the initial resource processing node with the information of the resources to be processed, access users who are not the corresponding users can be filtered out, protecting user data and achieving the effect of data security among multiple users.

[0068] Step 208: If it is detected that there are resources to be processed in the initial resource processing node, the communication component is invoked to obtain the resources to be processed, and the resources are sent to the resource processing container through the communication channel.

[0069] Once the above information verification method is used, if the verification is successful, the resource processing container can detect that the resource to be processed exists on the initial resource processing node. At this time, the resource processing container has the authority to obtain the resource to be processed, and can call the communication component to obtain the resource to be processed and send it to the resource processing container through the communication channel.

[0070] In practical applications, the resource sharing component can obtain the resource to be processed from the initial resource processing node and forward it to the communication component. After the communication component obtains the resource to be processed, it can forward the resource to be processed to the resource processing container through the communication channel between the communication component and the resource processing container.

[0071] In a specific embodiment of this specification, when it is detected that there are resources to be processed on the initial resource processing node, the resource to be processed is obtained from the initial resource processing node through the resource sharing component dfdaemon, and forwarded to the communication component dfproxy, which then sends the resources to the resource processing container through the communication channel.

[0072] Furthermore, after the resource information to be processed passes the information verification, in order to avoid the resource processing container obtaining a resource that does not correspond to the resource information to be processed, a selection can be made from the initial resources based on the resource to be processed, thereby determining the resource to be processed. Specifically, when it is detected that there is a resource to be processed in the initial resource processing node, the communication component is invoked to obtain the resource to be processed and sent to the resource processing container through the communication channel. This includes: when the resource information to be processed passes the information verification, selecting a target initial resource from the initial resources as the resource to be processed, and executing the steps of invoking the communication component to obtain the resource to be processed and sending it to the resource processing container through the communication channel.

[0073] Once the initial resource sharing information of the initial resource is verified and the verification is successful, it can be determined that the initial resource is the resource data required by the resource processing container. At this time, the initial resource can be selected as the target initial resource and used as the resource to be processed. Then, the subsequent steps of calling the communication component to obtain the resource to be processed and sending it to the resource processing container can be continued.

[0074] In practical applications, the initial resource processing node may cache multiple initial resources. During the verification process of initial resource sharing information and information about resources to be processed, a target initial resource can be selected from the initial resources based on the verification result and used as the resource to be processed. Then, the target resource processing node continues to execute the steps of calling the communication component to obtain the resource to be processed and forwarding it to the resource processing container.

[0075] Based on this, by verifying the information of the resource to be processed through the initial shared resource information, malicious users who illegally obtain the resource to be processed can be filtered out, thus ensuring the data security of users.

[0076] Furthermore, to avoid data contamination between different nodes, a resource sharing space can be set up for each resource processing node, ensuring that each resource processing node has space for corresponding cached data, thereby guaranteeing the correctness of data caching. Specifically, calling the communication component to obtain the resource to be processed and sending it to the resource processing container through the communication channel includes: determining the resource sharing database corresponding to the resource sharing network, and selecting the initial resource sharing space corresponding to the initial resource processing node in the resource sharing database; calling the communication component to obtain the resource to be processed from the initial resource sharing space, and sending it to the resource processing container through the communication channel.

[0077] The resource-sharing database can be understood as a database where each resource processing node in the resource-sharing network can access resource data. This database can consist of each resource processing node's local resource-sharing space. To ensure the correctness of resource data storage, each resource processing node can have its own independent resource-sharing space within the resource-sharing database. The resource data cached by each resource processing node is stored in its corresponding resource-sharing space. The initial resource-sharing space can be understood as the resource-sharing space corresponding to the initial resource processing node.

[0078] In practical applications, the resource-shared space corresponding to the resource processing node can also be categorized according to user identification information to ensure that cached data of the same user is stored in the same directory. Furthermore, container images of different resource processing containers deployed by the same user share a single directory, enabling users to quickly select the corresponding resource to be processed from the directory under the corresponding resource-shared space when deploying resource processing containers on different resource processing nodes.

[0079] In a specific embodiment of this specification, a resource sharing database of a P2P network is determined, and an initial resource sharing space corresponding to an initial resource processing node is selected in the resource sharing database. The resource sharing component dfdaemon of the target resource processing node is called to obtain the resource to be processed and forward it to the communication component, which then forwards it to the resource processing container through the communication channel.

[0080] Based on this, by distinguishing the resource sharing space of different resource processing nodes in the resource sharing database, container instances of the same user on the same resource processing node can cache image data in the same directory, ensuring the rationality of data storage, facilitating subsequent resource detection, and improving resource detection efficiency.

[0081] Furthermore, to prevent the resource processing container from failing to run due to the lack of resources to be processed on the initial resource processing node, a download cache can be performed at the source location corresponding to the resources to be processed. Specifically, the method further includes: when it is detected that there are no resources to be processed on the initial resource processing node, selecting a target original resource from the original resource database, wherein the original resource database is used to provide original resources for the resource processing node; sending the target original resource to the communication component, and calling the communication component to send the target original resource to the resource processing container through the communication channel.

[0082] If no resource to be processed is detected at the initial resource processing node, a target original resource can be selected from the source data location of the resource to be processed, i.e., the original resource database. The target original resource is the source data of the resource to be processed. The original database contains the source data of the mirror resource. It should be noted that the original database also has information verification; users can only obtain mirror resources that they have usage permissions for and cannot obtain mirror resources of other users. Alternatively, the original database can also be the user's local database, which only stores the data of that user, meaning that the original database can only be accessed and used by that user.

[0083] In practical applications, if no resources to be processed are detected on the initial resource processing node, they can be downloaded from the original resource database. However, downloading from the original resource database is slow and cannot provide container startup acceleration. Furthermore, the raw data downloaded from the original resource database, i.e., the image resources, needs to be converted in format before it can be used by the resource processing container. In contrast, the resources to be processed obtained from other resource processing nodes are all converted resources uploaded by other resource processing nodes, eliminating the need for the resource processing container to perform image resource format conversion again, thereby improving container startup speed.

[0084] In a specific embodiment of this specification, if it is detected that there is no resource to be processed at the initial resource processing node, the resource to be processed is downloaded and cached from the source resource location, the target original resource is selected from the original resource database, downloaded and forwarded to the communication component through the resource sharing component of the target resource processing node, and then sent to the resource processing container by the communication component through the communication channel.

[0085] In summary, by selecting the target original resource from the original resource database, the resource processing container can ultimately obtain the resource data used for container operation, thereby ensuring that the resource processing container can operate normally.

[0086] Furthermore, when the resource processing container on the target resource processing node caches the image resource for the first time, in order to avoid the user having to spend a lot of time obtaining resources from the original resource database when deploying resource processing containers on other resource processing nodes later, the image resource can be uploaded to the resource sharing database after the resource processing container on the target resource processing node caches the image resource. The specific method also includes: receiving the resource sharing request sent by the resource processing container through the communication component; determining the target resource sharing space in the resource sharing database; and uploading the target original resource to the target resource sharing space according to the resource sharing request.

[0087] In this context, a resource sharing request can be understood as a request from a resource processing container to upload image resources to a resource sharing database. Once a resource processing container on a target resource processing node has cached an image resource, it can upload that image resource to the resource sharing database. This allows the same user to directly download the image resource from the resource sharing database, i.e., directly from the resource processing node, when deploying resource processing containers on other resource processing nodes, thereby reducing the time spent on image resources and improving the operating efficiency of the resource processing container.

[0088] In practical applications, the image resources shared by the resource processing container need to be saved to the location corresponding to the resource processing container, that is, to the user's shared space. Therefore, the target resource sharing space needs to be determined in the resource sharing database first. The target resource sharing space can be understood as the space where the user caches resource data in this resource processing node. Subsequently, the target original resources can be uploaded to the target resource sharing space according to the resource sharing request for later use.

[0089] In summary, by uploading the target original resource to the target resource shared space, it is ensured that other resource processing containers of the user can obtain the target original resource from the target resource shared space, thereby improving container startup speed. At the same time, it can also prevent other users from obtaining the current user's image data, thus improving data security.

[0090] Furthermore, to prevent unauthorized users from maliciously obtaining image data shared by other users, corresponding image file identification information can be added when uploading image data. Specifically, uploading the target original resource to the target resource sharing space according to the resource sharing request includes: determining the resource cache information carried in the resource sharing request; generating resource sharing information corresponding to the target original resource based on the resource cache information and the user identification information in the container attribute information; and uploading the target original resource and the resource sharing information to the target resource sharing space.

[0091] The resource cache information can be understood as the file identifier of the image cache file, namely the cacheID mentioned above. Then, by performing a hash operation on the user identifier tagID, the resource sharing information corresponding to the target original resource can be generated. The resource sharing information can be used for information verification in the future to prevent other users from obtaining the image cache file.

[0092] In practical applications, by binding the target original resource with resource sharing information and uploading it to the target resource sharing space, information verification can be performed based on the resource sharing information when the target original resource is retrieved later.

[0093] In a specific embodiment of this specification, the resource cache information carried in the resource sharing request is determined. The resource cache information is cacheID. The resource cache information and the user identification information tagID are hashed to generate the resource sharing information taskID corresponding to the target original resource. The target original resource and taskID are then uploaded to the target resource sharing space.

[0094] In summary, by setting corresponding resource sharing information for the target original resource, users can verify the information based on the resource sharing information when they subsequently obtain the target original resource, thus ensuring the security of user data.

[0095] This specification provides a resource processing method applied to a target resource processing node, the target resource processing node including a communication component. The method includes: creating a resource processing container in response to a resource processing request, and determining container attribute information corresponding to the resource processing container; establishing a communication channel between the communication component and the resource processing container based on the container attribute information; determining unprocessed resource information corresponding to the resource processing container, and performing resource detection on an initial resource processing node based on the unprocessed resource information; if unprocessed resources are detected on the initial resource processing node, invoking the communication component to obtain the unprocessed resources, and sending them to the resource processing container through the communication channel. By setting the target resource processing node and the initial resource processing node in a resource-sharing network, and after creating the resource processing container on the target resource processing node, when the resource processing container is running to obtain the unprocessed resources corresponding to the resource processing container, a communication channel is established between the communication component and the resource processing container. Subsequent resource acquisition or transmission is based on the communication channel, avoiding attacks on the resource processing container and improving connection security. Furthermore, the system performs resource detection on the initial resource processing node based on the information of the resources to be processed. If the initial resource processing node is found to have resources to be processed, the communication component is invoked to obtain the shared resources to be processed from the initial resource processing node. Compared with the resource processing container obtaining resources to be processed from the original database, this can reduce the resource acquisition time of the resource processing container, thereby improving the running speed of the resource processing container.

[0096] The following is in conjunction with the appendix Figure 3 Taking the application of the resource processing method provided in this specification in a running container as an example, the resource processing method will be further explained. Figure 3 A flowchart of a resource processing method according to an embodiment of this specification is shown, with specific steps including steps 302 to 322.

[0097] Step 302: Create a resource processing container in response to a resource processing request.

[0098] In one possible approach, a resource processing request sent by the Kubelet component is received and forwarded to the resource management component containerd, which then creates a resource processing container on the target resource processing node.

[0099] Step 304: Listen to the network port of the resource processing container and determine the container identification information and user identification information corresponding to the resource processing container based on the listening results.

[0100] In one feasible approach, the resource management component, upon determining that the resource processing container has started successfully, listens to the network port of the resource processing container and determines the corresponding container identification information SID, vsockID, and user identification information UID based on the listening result.

[0101] Step 306: Generate container attribute information corresponding to the resource processing container based on the container identification information and user identification information.

[0102] In one feasible approach, container attribute information corresponding to the resource processing container is generated based on container identification information and user identification information. The container attribute information includes container SID, security container vsockID, and user UID.

[0103] Step 308: Send container attribute information to the communication component, call the communication component to establish a communication connection with the resource processing container based on the container attribute information, and establish a communication channel between the communication component and the resource processing container based on the connection result.

[0104] In one feasible approach, container attribute information is sent to the communication component dfproxy, which then actively connects to the corresponding resource processing container, establishing a communication channel between the communication component and the resource processing container.

[0105] Step 310: Receive the resource acquisition request sent by the resource processing container through the communication component, and determine the resource attribute information carried in the resource acquisition request.

[0106] In one feasible approach, a resource acquisition request is received via the communication component dfproxy, and the resource attribute information cacheID carried in the resource acquisition request is determined.

[0107] Step 312: Extract the user identification information from the container attribute information, and generate the resource information to be processed based on the user identification information and resource attribute information.

[0108] In one feasible approach, the user identification information (UID) is extracted from the container attribute information, and the resource information to be processed (taskID1) is generated based on the user identification information and resource attribute information.

[0109] Step 314: Determine the initial resource sharing information corresponding to the initial resource in the initial resource processing node.

[0110] In one feasible approach, the initial resource sharing information taskID2 corresponding to the initial resource in other initial resource processing nodes of the resource sharing network P2P network is determined.

[0111] Step 316: Verify the information of the resource to be processed based on the initial resource sharing information, and determine the resource detection result of the initial resource processing node based on the verification result.

[0112] In one feasible approach, the information of the resource to be processed, taskID1, is verified based on the initial resource sharing information taskID2, and the existence of the resource to be processed on the initial resource processing node is determined based on the verification result.

[0113] Step 318: If the information of the resource to be processed passes the information verification, select the target initial resource from the initial resources and use it as the resource to be processed.

[0114] In one feasible approach, if the information of the resource to be processed passes the information verification, it is determined that there is a resource to be processed on the initial resource processing node, and the target initial resource is selected from the initial resources as the resource to be processed.

[0115] Step 320: Determine the resource sharing database corresponding to the resource sharing network, and select the initial resource sharing space corresponding to the initial resource processing node in the resource sharing database.

[0116] In one feasible approach, the initial resource processing node determines the resource sharing database of the P2P network and selects the initial resource sharing space corresponding to the initial resource processing node from the resource sharing database.

[0117] Step 322: Invoke the communication component to obtain the resource to be processed from the initial resource sharing space, and send it to the resource processing container through the communication channel.

[0118] In one feasible approach, the resource to be processed is obtained by the resource-sharing component dfdaemon on the target resource processing node and forwarded to the communication component dfproxy, which then forwards it to the resource processing container through a communication channel.

[0119] This specification provides a resource processing method that sets up a target resource processing node and an initial resource processing node in a resource-sharing network. After creating a resource processing container on the target resource processing node, and while running the resource processing container to acquire the corresponding resources to be processed, a communication component is used to connect with the resource processing container and establish a communication channel. Subsequent resource acquisition and transmission are based on this communication channel, preventing attacks on the resource processing container and improving connection security. Furthermore, resource detection is performed on the initial resource processing node based on the information of the resources to be processed. If resources to be processed are detected on the initial resource processing node, the communication component is invoked to retrieve the shared resources from it. Compared to retrieving resources from the original database, this reduces the resource acquisition time of the resource processing container, thereby improving its operating speed.

[0120] Corresponding to the above method embodiments, this specification also provides resource processing apparatus embodiments. Figure 4 A schematic diagram of a resource processing apparatus according to an embodiment of this specification is shown. Figure 4 As shown, the device is applied to a target resource processing node, which includes a communication component. The device includes:

[0121] The determination module 402 is configured to create a resource processing container in response to a resource processing request and determine the container attribute information corresponding to the resource processing container;

[0122] Module 404 is configured to establish a communication channel between the communication component and the resource processing container based on the container attribute information.

[0123] The detection module 406 is configured to determine the resource information to be processed corresponding to the resource processing container, and to perform resource detection on the initial resource processing node based on the resource information to be processed.

[0124] The sending module 408 is configured to, when it is detected that there is a resource to be processed in the initial resource processing node, call the communication component to obtain the resource to be processed and send it to the resource processing container through the communication channel.

[0125] Optionally, the determining module 402 is further configured to: monitor the network port of the resource processing container and determine the container identification information and user identification information corresponding to the resource processing container based on the monitoring results; and generate container attribute information corresponding to the resource processing container based on the container identification information and the user identification information.

[0126] Optionally, the establishment module 404 is further configured to: send the container attribute information to the communication component; invoke the communication component to establish a communication connection with the resource processing container based on the container attribute information; and establish a communication channel between the communication component and the resource processing container based on the connection result.

[0127] Optionally, the detection module 406 is further configured to: receive a resource acquisition request sent by the resource processing container through the communication component, determine the resource attribute information carried in the resource acquisition request; extract user identification information from the container attribute information, and generate the resource information to be processed based on the user identification information and the resource attribute information.

[0128] Optionally, the detection module 406 is further configured to: determine the initial resource sharing information corresponding to the initial resource in the initial resource processing node; perform information verification on the resource information to be processed based on the initial resource sharing information; and determine the resource detection result of the initial resource processing node based on the verification result.

[0129] Optionally, the sending module 408 is further configured to: if the resource information to be processed passes the information verification, select a target initial resource from the initial resources and use it as the resource to be processed, and execute the step of calling the communication component to obtain the resource to be processed and sending it to the resource processing container through the communication channel.

[0130] Optionally, the sending module 408 is further configured to: determine the resource sharing database corresponding to the resource sharing network, and select the initial resource sharing space corresponding to the initial resource processing node in the resource sharing database; call the communication component to obtain the resource to be processed from the initial resource sharing space, and send it to the resource processing container through the communication channel.

[0131] Optionally, the device further includes a selection module configured to: select a target original resource from the original resource database when it is detected that the initial resource processing node does not have any resources to be processed, wherein the original resource database is used to provide original resources for the resource processing node; send the target original resource to the communication component, and invoke the communication component to send the target original resource to the resource processing container through the communication channel.

[0132] Optionally, the selection module is further configured to: receive a resource sharing request sent by the resource processing container through the communication component; determine a target resource sharing space in the resource sharing database; and upload the target original resource to the target resource sharing space according to the resource sharing request.

[0133] Optionally, the selection module is further configured to: determine the resource cache information carried in the resource sharing request; generate resource sharing information corresponding to the target original resource based on the resource cache information and the user identification information in the container attribute information; and upload the target original resource and the resource sharing information to the target resource sharing space.

[0134] This specification provides a resource processing device applied to a target resource processing node, the target resource processing node including a communication component. The device includes: a determining module configured to create a resource processing container in response to a resource processing request and determine container attribute information corresponding to the resource processing container; an establishing module configured to establish a communication channel between the communication component and the resource processing container based on the container attribute information; a detection module configured to determine the resource information to be processed corresponding to the resource processing container and perform resource detection on an initial resource processing node based on the resource information to be processed; and a sending module configured to, when the initial resource processing node is detected to have resources to be processed, invoke the communication component to obtain the resources to be processed and send them to the resource processing container through the communication channel. By setting the target resource processing node and the initial resource processing node in a resource-sharing network, and after creating a resource processing container on the target resource processing node, when the resource processing container is running and obtaining the resources to be processed corresponding to the resource processing container, a communication channel is established between the communication component and the resource processing container. Subsequent resource acquisition or sending is based on the communication channel, avoiding attacks on the resource processing container and improving connection security. Furthermore, the system performs resource detection on the initial resource processing node based on the information of the resources to be processed. If the initial resource processing node is found to have resources to be processed, the communication component is invoked to obtain the shared resources to be processed from the initial resource processing node. Compared with the resource processing container obtaining resources to be processed from the original database, this can reduce the resource acquisition time of the resource processing container, thereby improving the running speed of the resource processing container.

[0135] The above is an illustrative scheme of a resource processing apparatus according to this embodiment. It should be noted that the technical solution of this resource processing apparatus and the technical solution of the resource processing method described above belong to the same concept. For details not described in detail in the technical solution of the resource processing apparatus, please refer to the description of the technical solution of the resource processing method described above.

[0136] Figure 5 A structural block diagram of a computing device 500 according to an embodiment of this specification is shown. The components of the computing device 500 include, but are not limited to, a memory 510 and a processor 520. The processor 520 is connected to the memory 510 via a bus 530, and a database 550 is used to store data.

[0137] The computing device 500 also includes an access device 540, which enables the computing device 500 to communicate via one or more networks 560. Examples of these networks include a Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the Internet. The access device 540 may include one or more of any type of wired or wireless network interface (e.g., a Network Interface Card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) interface, a Wi-MAX interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0138] In one embodiment of this specification, the above-described components of the computing device 500 and Figure 5 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 5 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0139] The computing device 500 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or PCs. The computing device 500 can also be a mobile or stationary server.

[0140] The processor 520 implements the resource processing method when executing the computer instructions.

[0141] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the resource processing method described above belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the resource processing method described above.

[0142] An embodiment of this specification also provides a resource processing system, the system including a target resource processing node, the target resource processing node including a communication component; the target resource processing node is used to store a communication channel establishment executable instruction; when the communication channel establishment executable instruction is executed by the target resource processing node, it implements the steps of the resource processing method as described above.

[0143] The above is an illustrative scheme of a resource processing system according to this embodiment. It should be noted that the technical solution of this resource processing system and the technical solution of the resource processing method described above belong to the same concept. For details not described in detail in the technical solution of the resource processing system, please refer to the description of the technical solution of the resource processing method described above.

[0144] An embodiment of this specification also provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement the steps of the resource processing method as described above.

[0145] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the resource processing method described above belong to the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the resource processing method described above.

[0146] An embodiment of this specification also provides a computer program, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of the above-described resource processing method.

[0147] The above is an illustrative scheme of a computer program according to this embodiment. It should be noted that the technical solution of this computer program and the technical solution of the resource processing method described above belong to the same concept. For details not described in detail in the technical solution of the computer program, please refer to the description of the technical solution of the resource processing method described above.

[0148] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0149] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0150] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

[0151] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0152] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. A resource processing method applied to a target resource processing node, the target resource processing node including a communication component, the method comprising: In response to a resource processing request, a resource processing container is created, and the container attribute information corresponding to the resource processing container is determined; A communication channel is established between the communication component and the resource processing container based on the container identification information in the container attribute information; The resource information to be processed corresponding to the resource processing container is determined, and the initial resource processing node in the resource sharing network to which the target resource processing node belongs is detected based on the resource information to be processed, wherein the resource information to be processed includes resource file information; If the initial resource processing node detects that there are resources to be processed, the communication component is invoked to obtain the resources to be processed, and the resources are sent to the resource processing container through the communication channel.

2. The method as described in claim 1, wherein determining the container attribute information corresponding to the resource processing container includes: Listen to the network port of the resource processing container, and determine the container identification information and user identification information corresponding to the resource processing container based on the listening results; Container attribute information corresponding to the resource processing container is generated based on the container identification information and the user identification information.

3. The method as described in claim 1, wherein establishing a communication channel between the communication component and the resource processing container based on the container identifier information in the container attribute information, includes: Send the container attribute information to the communication component; The communication component is invoked to establish a communication connection with the resource processing container based on the container identifier information in the container attribute information; A communication channel is established between the communication component and the resource processing container based on the connection result.

4. The method as described in claim 1, wherein determining the resource information to be processed corresponding to the resource processing container includes: The communication component receives a resource acquisition request sent by the resource processing container and determines the resource attribute information carried in the resource acquisition request. Extract the user identification information from the container attribute information, and generate the resource information to be processed based on the user identification information and the resource attribute information.

5. The method as described in claim 4, wherein resource detection is performed on the initial resource processing node in the resource sharing network to which the target resource processing node belongs, based on the resource information to be processed, comprising: Determine the initial resource sharing information corresponding to the initial resource in the initial resource processing node, wherein the initial resource processing node and the target resource processing node belong to the same resource sharing network; Based on the initial resource sharing information, the information of the resource to be processed is verified, and the resource detection result of the initial resource processing node is determined according to the verification result.

6. The method as described in claim 5, wherein, upon detecting that the initial resource processing node has resources to be processed, the method invokes the communication component to obtain the resources to be processed and sends them to the resource processing container through the communication channel, comprising: If the information of the resource to be processed passes the information verification, a target initial resource is selected from the initial resources and used as the resource to be processed. Then, the steps of calling the communication component to obtain the resource to be processed and sending it to the resource processing container through the communication channel are executed.

7. The method of claim 1, wherein the communication component is invoked to obtain the resource to be processed, and the resource is sent to the resource processing container through the communication channel, comprising: Determine the resource sharing database corresponding to the resource sharing network, and select the initial resource sharing space corresponding to the initial resource processing node in the resource sharing database; The communication component is invoked to obtain the resource to be processed from the initial resource sharing space and sent to the resource processing container through the communication channel.

8. The method of claim 7, further comprising: If no resources to be processed are detected at the initial resource processing node, a target original resource is selected from the original resource database, wherein the original resource database is used to provide original resources for the resource processing node; The target raw resource is sent to the communication component, and the communication component is invoked to send the target raw resource to the resource processing container through the communication channel.

9. The method of claim 8, further comprising: The communication component receives resource sharing requests sent by the resource processing container. The target resource sharing space is determined in the resource sharing database, and the target original resource is uploaded to the target resource sharing space according to the resource sharing request.

10. The method of claim 9, wherein uploading the target original resource to the target resource sharing space according to the resource sharing request comprises: Determine the resource cache information carried in the resource sharing request; Based on the resource cache information and the user identification information in the container attribute information, resource sharing information corresponding to the target original resource is generated; Upload the target original resources and the resource sharing information to the target resource sharing space.

11. A resource processing system, the system comprising a target resource processing node, the target resource processing node comprising a communication component; The target resource processing node is used to store executable instructions for establishing communication channels; When the communication channel establishment executable instruction is executed by the target resource processing node, it implements the steps of the method as described in any one of claims 1-10.

12. A computing device comprising a memory, a processor, and computer instructions stored in the memory and executable on the processor, wherein the processor, when executing the computer instructions, performs the steps of the method according to any one of claims 1-10.

13. A computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1-10.

Images