Container system framework, internet of things architecture, and data processing method

Abstract

A container system framework, an Internet of Things architecture and a data processing method, the container system framework comprising: a container client configured to initiate a label processing request; a container daemon configured to receive and process the label processing request; the container daemon comprising a container engine configured to perform a corresponding operation based on the label processing request, and the container engine comprising a data label processing module configured to mark resource usage of an application in a container based on the label processing request, and output a data label to the container client. The embodiment of the present application can track the resource usage of the application in the container, thereby facilitating the embodiment and evaluation of the value of the use of the application to the container, and accordingly providing an implementation method for the value embodiment of data in an end-side architecture.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of Internet of Things, and particularly relate to a container system framework, an Internet of Things architecture and a data processing method. BACKGROUND

[0002] With the wide application of Internet of Things, a large number of Internet of Things devices will generate a large amount of data, and the collection, processing and analysis of the data will become very complex; a cloud platform can provide storage of massive data, value mining, etc.; the access of AI (Artificial Intelligence) makes IoT (Internet of Things) have a "brain" for connection, and deep learning and machine learning become the key to predicting the future; and the application of blockchain technology makes the exchange of data have a source traceable and mutual trust improved.

[0003] With the continuous increase of application scenarios, basic isolation of application programs needs to be performed to ensure stable operation of the device and prevent "all or nothing". Container technology is a kind of kernel light operating system layer virtualization technology, which provides a technology for application to be separated from the bottom hardware limit, and the container shares the same operating system, separates the application process from other parts of the system to realize isolation of computing resources and data, that is, to ensure stable operation of the system.

[0004] However, the current application cannot reflect the value of the use of the application program to the container. SUMMARY

[0005] The problem solved by embodiments of the present application is to provide a container system framework, an Internet of Things architecture and a data processing method, which are beneficial to reflect and evaluate the value of the use of the application program to the container.

[0006] To solve the above problem, the present application provides a container system framework, comprising one or more independently running containers, wherein one or more application programs run in the container; the container system framework comprises: a container client for initiating a label processing request; a container daemon process comprising a container engine, wherein the container engine is configured to perform corresponding operations based on the label processing request, and the container engine comprises a data label processing module, wherein the data label processing module is configured to mark the resource usage of the application program in the container based on the label processing request, and output a data label to the container client.

[0007] Optionally, the container client is further configured to initiate an operation request for creating and running a container; the container daemon is configured to receive and process the operation request and the label processing request; the container daemon further comprises a container server, the container server is configured to receive the operation request and the label processing request, and further configured to forward the operation request and the label processing request to the container engine; the container engine is further configured to perform corresponding operations based on the operation request.

[0008] Optionally, the data label processing module comprises: a command parser configured to parse the label processing request, and output any one or both of a service registration command and a label acquisition command; a service builder configured to register or unregister a specified application with a label service based on the service registration command; and a label generator configured to query and mark resource usage of the application in the running state and having a registered label service in the container based on the label acquisition command, and output corresponding data labels.

[0009] Optionally, the container system framework further comprises: a container driver library configured to customize an execution environment of the container, the container driver being connected to a host operating system and further configured to call resources of the host operating system; and the label generator is configured to query resource usage of the application in the container through an interface between the container driver library and the host operating system, and output corresponding data labels.

[0010] Optionally, the container engine further comprises: a basic transaction processing module configured to perform basic operation processing based on the operation request, and further configured to receive the label processing request and perform preliminary parsing processing on the label processing request, and send the label processing request to the data label processing module after the preliminary parsing processing.

[0011] Optionally, the data label comprises one or more of the following: usage frequency of the application, input / output delay, memory occupation, network bandwidth occupation, and response speed.

[0012] Optionally, the data label processing module is a blockchain data label processing module.

[0013] Correspondingly, the embodiment of the application further provides an Internet of Things architecture, comprising: a cloud platform; an end-side architecture, the end-side architecture comprising: a container system framework provided by the embodiment of the application, the container system framework outputting data labels; and a security component comprising a blockchain engine, the blockchain engine being configured to perform accelerated processing on the data labels, obtain processed data, and upload the processed data to the cloud platform.

[0014] Correspondingly, the embodiment of the present application also provides a data processing method applied to a container system framework, wherein the container system framework comprises one or more independently running containers, and one or more application programs run in the containers; the data processing method applied to the container system framework comprises: initiating a label processing request; based on the label processing request, marking a resource usage of an application program in a container, and outputting a data label; wherein the step of marking the resource usage of the application program in the container comprises: performing analysis processing on the label processing request, and outputting any one or both of a service registration command and a label acquisition command; based on the service registration command, registering or deregistering a specified application program with a label service; based on the label acquisition command, querying and marking a resource usage of an application program in the container in a running state and having registered the label service, and outputting a corresponding data label.

[0015] Optionally, the service registration command comprises a registration command and a deregistration command; the registration of the specified application program with the label service comprises: based on the registration command, judging whether the specified application program is in a running state; when the application program is in the running state, judging whether the application program has registered the label service; when the application program has not registered the label service, adding a record of registering the application program with the label service to a service record pool, and completing the registration of the application program with the label service; when the application program is not in the running state or the application program has registered the label service, exiting the registration of the application program with the label service; the deregistration of the specified application program from the label service comprises: based on the deregistration command, judging whether the application program has registered the label service; if yes, deleting a registration record of the current application program from the service record pool; if no, exiting the deregistration of the application program from the label service.

[0016] Optionally, the resource usage of the application program in the container comprises one or more of a usage frequency of the application program, an input / output delay, memory occupation, network bandwidth occupation and response speed.

[0017] Optionally, the data label is a blockchain data label.

[0018] Compared with the prior art, the technical scheme of the embodiment of the present application has the following advantages:

[0019] The container client is used for initiating a label processing request; the container daemon is internally provided with a container engine, and the container engine comprises a data label processing module, which is used for marking resource usage of an application in a container based on the label processing request and outputting a data label, so that the resource usage of the application in the container can be tracked, and the value of the application to the container can be reflected and evaluated, such as evaluating the usage frequency, running smoothness, occupied memory and CPU resource of the application, and the container system framework is usually applied to an end-side architecture of an Internet of Things architecture, and can provide an implementation method for value reflection of data in the end-side architecture.

[0020] In the data processing method applied to the container system framework, a label processing request is initiated; resource usage of an application in a container is marked based on the label processing request, and a data label is output, so that the resource usage of the application in the container can be tracked, and the value of the application to the container can be reflected and evaluated, such as evaluating the usage frequency, running smoothness, occupied memory and CPU resource of the application, and the container system framework is usually applied to an end-side architecture of an Internet of Things architecture, and can provide an implementation method for value reflection of data in the end-side architecture. BRIEF DESCRIPTION OF DRAWINGS

[0021] Figure 1 is a structure schematic diagram of a container system framework in the prior art;

[0022] Figure 2 is a structure schematic diagram of an embodiment of the container system framework of the application;

[0023] Figure 3 is a structure schematic diagram of an embodiment of the data label processing module;

[0024] Figure 4 is a structure schematic diagram of an embodiment of the Internet of Things architecture;

[0025] Figure 5 is a flow schematic diagram of an embodiment of the data processing method applied to the container system framework of the application;

[0026] Figure 6 is Figure 5 is a flow schematic diagram of an embodiment of step S2 in DETAILED DESCRIPTION

[0027] As can be known from the background art, there is a problem that the use of an application program cannot reflect the value to a container. In combination with a container system framework, the reason why the use of an application program cannot reflect the value to a container is analyzed.

[0028] Figure 1 is a structural schematic diagram of a container system framework in the prior art.

[0029] As shown in Figure 1 , the container system framework 1 comprises: a container client 2 configured to initiate an operation request for creating and running a container 5; a container daemon 3 configured to receive and process the operation request, the container daemon 3 comprising a container server 31 and a container engine 32, wherein the container server 31 is configured to receive the operation request and forward the operation request and a label processing request to the container engine 32, and the container engine 32 is configured to perform a corresponding operation based on the operation request; a container driver library 4 configured to customize an execution environment of the container 5 and manage the container; and one or more independently running containers 5, each of which runs one or more application programs 51.

[0030] Specifically, the container system framework 1 is applied to an Internet of Things architecture, and more specifically, an end-side architecture in the Internet of Things architecture. In the current container system framework 1, the acquisition and tracking of resource usage information of the application programs 51 in the containers 5 are not performed, and accordingly, the use of the application programs 51 cannot reflect the value to the containers 5, and accordingly, the resource occupation of the application programs 51 cannot be accurately acquired at the end side.

[0031] To solve the technical problem, an embodiment of the present application provides a container system framework, comprising one or more independently running containers, and one or more application programs running in the containers; the container system framework comprises: a container client configured to initiate a label processing request; a container daemon comprising a container engine, wherein the container engine is configured to perform a corresponding operation based on the label processing request, and the container engine comprises a data label processing module configured to mark resource usage of the application programs in the containers based on the label processing request, and output a data label to the container client.

[0032] The container client is used for initiating a label processing request; the container daemon process is internally provided with a container engine, and the container engine comprises a data label processing module, and the data label processing module is used for marking resource usage of an application in a container based on the label processing request and outputting a data label; accordingly, the container system framework provided by the embodiment of the application can track the resource usage of the application in the container, thereby facilitating the embodiment and evaluation of the value of the use of the application to the container, for example, evaluating the use frequency, running smoothness, occupied memory and CPU resource situation of the application, and the container system framework is usually applied to an end-side architecture of an Internet of Things architecture, and accordingly can provide an implementation method for the value embodiment of data in the end-side architecture.

[0033] In order to make the above-mentioned purposes, features and advantages of the embodiments of the application more obvious and easy to understand, the specific embodiments of the application will be described in detail below with reference to the drawings. Referring to Figure 2 , a structural schematic diagram of an embodiment of a container system framework of the application is shown.

[0034] As Figure 2 shown, in the embodiment, the container system framework 100 comprises one or more independently running containers 110, and one or more application programs 120 run in the container 110; the container system framework 100 comprises: a container client 130 used for initiating a label processing request; a container daemon process 140 comprising a container engine 150, wherein the container engine 150 is used for performing corresponding operations based on the label processing request, and the container engine 150 comprises a data label processing module 160, wherein the data label processing module 160 is used for marking resource usage of the application program 120 in the container 110 based on the label processing request and outputting a data label to the container client 130.

[0035] The container 110 is used for containing one or more application programs 120 to realize basic isolation of the application program 120, thereby guaranteeing stable operation of the device. Specifically, the container technology is a kernel light-weight operating system layer virtualization technology, which provides a technology for application to be separated from the bottom hardware limit, and the container shares the same operating system, separates the application process and other parts of the system to realize isolation of computing resources and data, that is, to guarantee stable operation of the system.

[0036] The application program 120 is used for collecting data and performing corresponding data processing in response to an operation request of a user. Specifically, the application program 120 collects data through a specific peripheral device.

[0037] The container client 130 initiates a label processing request, so that the data label processing module 160 in the container engine 150 can perform corresponding operations based on the label processing request.

[0038] It should be noted that in this embodiment, the container client 130 is also used to initiate an operation request for creating and running the container 110, for example: the operation request can include the operation request of creating, running and destroying the container 110, so as to perform the management operation of creating, running and destroying the container 110.

[0039] Specifically, the container client 130 is used to send an operation request to the container daemon 140.

[0040] The container daemon 140 is used to receive and process the request initiated by the container client 130, and the container daemon 140 is also used to support the running and management of the container 110.

[0041] In this embodiment, the container daemon 140 is used to receive and process the operation request and the label processing request.

[0042] In this embodiment, the container daemon 140 further includes a container server 170, which is used to receive the operation request and the label processing request, and is also used to forward the operation request and the label processing request to the container engine 150.

[0043] The container server 170 is used to establish communication with the container client 130, so as to receive the request initiated by the container client 130, and forward the request initiated by the container client 130 to the container engine 150 for corresponding processing.

[0044] The container engine 150 is used to perform corresponding processing based on the request initiated by the client 130.

[0045] In this embodiment, the container engine 150 is used to perform corresponding operations based on the label processing request, for example: the operation of obtaining the data label.

[0046] It should be noted that in this embodiment, the container engine 150 is also used to perform corresponding operations based on the operation request. For example: when the operation request is an operation request for managing the container such as creating, running and destroying, the container engine 150 performs the operation of creating, running and destroying the container based on the operation request.

[0047] In the embodiment, the container engine 150 comprises a data tag processing module 160, which is configured to mark the resource usage of the application 120 in the container 110 based on the tag processing request, and output a data tag to the container client 130, so that the resource usage of the application 120 in the container 110 can be tracked, and the value of the use of the application 120 to the container 110 can be reflected and evaluated, for example, the use frequency, running smoothness, memory and CPU resource usage of the application 120 are evaluated, and the container system framework is usually applied to the end-side architecture of the Internet of Things architecture, so that an implementation method for the value reflection of data in the end-side architecture can be provided.

[0048] The data tag processing module 160 outputs a data tag to the container client 130, and the container client 130 can select to upload the data tag to the cloud or as a chain (i.e., uploaded to the blockchain) certificate.

[0049] In specific embodiments, the client 130 can send the data tag to a blockchain engine, which accelerates the processing of the data tag and uploads it to the blockchain cloud as a trusted certificate, so that the value reflection and value discrimination of the application to the end-side client can be objectively reflected.

[0050] In the embodiment, the data tag processing module 160 is a blockchain data tag processing module. By making the data tag processing module 160 a blockchain data tag processing module, the uniqueness and authenticity of the data can be ensured, and the security and effectiveness of the data can be ensured.

[0051] With reference to Figure 3 , a structural schematic diagram of an embodiment of the data tag processing module 160 of the application is shown. As a specific embodiment, the data tag processing module 160 comprises a command parser 161, a service builder 162 and a tag generator 163.

[0052] The command parser 161 is configured to parse and process the tag processing request, and output any one or both of a service registration command and a tag acquisition command.

[0053] The service registration command is used for registration, registration or cancellation of the label marking service of the specified application 120; and the tag acquisition command is used for data tag acquisition.

[0054] In the embodiment, the command parser 161 is further configured to forward the parsed command to the service builder 162 or the tag generator 163 after parsing and processing the tag processing request.

[0055] Specifically, the command parser 161 forwards the service registration command to the service builder 162 and forwards the label acquisition command to the label generator 163 according to the type of the parsed command.

[0056] The service builder 162 is configured to register or unregister the specified application 120 for the label service based on the service registration command.

[0057] The registration of the specified application 120 for the label service enables the specified application 120 to have the qualification to perform the label service, and accordingly, the label generator 163 can acquire and generate the label for the application 120 having the qualification to perform the label service.

[0058] Specifically, the registration of the specified application 120 for the label service by the service builder 162 based on the service registration command includes: the service builder 162 determines whether the application 120 requiring registration of the label service is in a running state; if it is determined that the application 120 requiring registration of the label service is not in the running state, the registration of the specified application 120 for the label service is exited; if it is determined that the application 120 requiring registration of the label service is in the running state, it is determined whether the application 120 has performed the registration of the label service; if the application 120 has not performed the registration of the label service, the application 120 is registered for the label service, i.e., a record is added to the service record pool; if the application 120 has been registered for the label service, the registration of the application for the label service is exited.

[0059] The unregistration of the specified application 120 for the label service enables the specified application 120 to lose the qualification to perform the label service based on the actual demand.

[0060] Specifically, the unregistration of the specified application 120 for the label service by the service builder 162 includes: based on the unregistration command, it is determined whether the application 120 has been registered for the label service; if yes, the registration record of the current application 120 is deleted from the service record pool; if no, the unregistration of the application 120 for the label service is exited.

[0061] The label generator 163 is configured to query and mark the resource usage of the application 120 in the running state and having the registered label service in the container 110 based on the label acquisition command, and output the corresponding data label.

[0062] Specifically, when the label generator 163 receives the label obtaining command, it is queried whether the application 120 is in a running state; if the application 120 is not in a running state, it is exited; if the application 120 is in a running state, it is queried whether the application 120 has a registered label service; if the application 120 has a registered label service, the resource usage of the application 120 in the container 110 is queried and labeled, and the corresponding data label is output; if the application 120 does not have a registered label service, it is exited.

[0063] In this embodiment, the data label can include one or more of the number of times of use of the application, input / output delay, memory occupation, network bandwidth occupation, and response speed.

[0064] In this embodiment, the container engine 150 further includes a basic transaction processing module 190 configured to perform basic operation processing based on the operation request, and further configured to receive the label processing request and perform preliminary analysis processing on the label processing request, and send the label processing request to the data label processing module 160 after the preliminary analysis processing on the label processing request.

[0065] The basic transaction processing module 190 performs basic operation processing based on the operation request can include: performing the operation of creating the container 110 based on the request of creating the container 110; performing the operation of running the container 110 based on the request of running the container 110; and performing the operation of destroying the container 110 based on the request of destroying the container 110.

[0066] The basic transaction processing module 190 is further configured to receive the label processing request and perform preliminary analysis processing on the label processing request, thereby facilitating the difficulty of the command parser 161 in performing analysis processing on the label processing request, improving the analysis efficiency, and accordingly improving the data processing efficiency.

[0067] The basic transaction processing module 190 sends the label processing request to the data label processing module 160 after the preliminary analysis processing on the label processing request, and more specifically, sends the label processing request to the command parser 161.

[0068] In this embodiment, the container system framework 100 further includes a container driver library 180 configured to customize the execution environment of the container 110, the container driver library 180 being connected to the host operating system and further configured to call the resources of the host operating system.

[0069] Correspondingly, the container engine 150 is configured to call the required resources from the container driver library 180 based on the operation request, so as to perform the corresponding operation.

[0070] For example, when the container engine 150 performs the creation of the container 110 based on the operation request of the container client 130, the container engine 150 calls the resources of the host operating system through the container driver library 180 to perform the creation of the container.

[0071] Therefore, in the embodiment, the label generator 163 is configured to query the resource usage of the application 120 in the container 110 through the interface between the container driver library 180 and the host operating system, and output corresponding data labels.

[0072] To solve the problem, the application further provides an Internet of Things architecture. Figure 4 FIG. 1 is a structural schematic diagram of an embodiment of the Internet of Things architecture of the application.

[0073] In the embodiment, the Internet of Things architecture 400 comprises a cloud platform 400 and an end-side architecture 200, wherein the end-side architecture 200 comprises the container system framework 100 provided by the embodiment of the application, the container system framework 100 outputs data labels, and the security component 210 comprises a blockchain engine 220, which is configured to accelerate the processing of the data labels, obtain processed data, and upload the processed data to the cloud platform 400.

[0074] In the Internet of Things architecture 400 provided by the embodiment, the blockchain engine 220 accelerates the processing of the data labels, obtains processed data, and uploads the processed data to the cloud platform 400, so that the use and operation of the data in the end-side architecture 200 can be tracked and recorded, the data flow can be tracked, the value of the data in the end-side architecture can be analyzed and mined, and the value of the data in the end-side architecture can be embodied.

[0075] In the embodiment, the data labels are blockchain data labels, and the blockchain engine 220 is configured to upload the processed data to the cloud platform 300 as a chain-up credential, so as to facilitate the guarantee of the authenticity and effectiveness of the data, prevent the data from being tampered with, and improve the security and effectiveness of the data.

[0076] The cloud platform 300 interacts with the end-side architecture 200 to provide the management of devices, the processing of data, and the analysis and mining of the value of data.

[0077] Specifically, the cloud platform 300 is configured to store, calculate, and record the data transmitted by the end-side architecture 200, perform demand processing, and provide services to the end-side architecture.

[0078] The end-side architecture 200 is used for data interaction with the peripheral device, so as to collect data through the peripheral device and upload the collected data to the cloud platform 300 for analysis and processing.

[0079] The security component 210 is used for ensuring the security of the Internet of Things architecture 100.

[0080] The blockchain engine 220 is used for accelerating the processing of the data tag and obtaining processed data.

[0081] For the detailed description of the Internet of Things architecture 300, this embodiment will not be repeated here.

[0082] To solve the problem, the application further provides a data processing method applied to a container system framework. Figure 5 is a flowchart of an embodiment of the data processing method applied to the container system framework.

[0083] In order to facilitate understanding and description, the data processing method of the present embodiment will be described in detail in combination with the container system framework provided by the embodiments of the present application.

[0084] In the present embodiment, the data processing method is applied to a container system framework 100, and the container system framework 100 includes one or more independently running containers 110, and one or more application programs 120 run in the container 110.

[0085] The container 110 is used to accommodate one or more application programs 120 to achieve basic isolation of the application program 120 and ensure stable operation of the device. Specifically, the container technology is a kernel light operating system layer virtualization technology, which provides a technology for application to escape from the bottom hardware limit. The container shares the same operating system, isolates the application process and other parts of the system, and realizes the isolation of computing resources and data, so as to ensure the stable operation of the system.

[0086] The application program 120 is used for collecting data and performing corresponding data processing in response to the operation request of the user. Specifically, the application program 120 collects data through a specific peripheral device.

[0087] In the present embodiment, the data processing method can include the following steps:

[0088] Step S1: initiating a tag processing request;

[0089] Step S2: based on the tag processing request, marking the resource usage of the application program 120 in the container 110, and outputting a data tag.

[0090] The data processing method provided in the embodiment includes the following steps: a label processing request is initiated, and the resource usage of the application 120 in the container 110 is marked based on the label processing request, and a data label is output. Accordingly, by using the data processing method provided in the embodiment, the resource usage of the application 120 in the container 110 can be tracked, and the value of the use of the application 120 to the container 110 can be reflected and evaluated, for example, the use frequency, running smoothness, memory and CPU resource usage of the application 120 are evaluated. The container system framework 100 is usually applied to an end-side architecture of an Internet of Things architecture, and accordingly can provide an implementation method for the value of data in the end-side architecture.

[0091] The data processing method of the embodiment will be described in detail below with reference to the accompanying drawings.

[0092] Reference Figure 5 Step S1 is performed, and a label processing request is initiated.

[0093] The label processing request is initiated, so that subsequent operations can be performed based on the label processing request.

[0094] Specifically, in the embodiment, the container client 130 initiates the label processing request, so that the data label processing module in the container engine 150 can perform corresponding operations based on the label processing request.

[0095] Continuing to refer to Figure 5 Step S2 is performed, and the resource usage of the application 120 in the container 110 is marked based on the label processing request, and a data label is output.

[0096] The resource usage of the application 120 in the container 110 is marked based on the label processing request, and a data label is output to the container client 130. Accordingly, the resource usage of the application 120 in the container 110 can be tracked, and the value of the use of the application 120 to the container 110 can be reflected and evaluated, for example, the use frequency, running smoothness, memory and CPU resource usage of the application 120 are evaluated. The container system framework is usually applied to an end-side architecture of an Internet of Things architecture, and accordingly can provide an implementation method for the value of data in the end-side architecture.

[0097] In the embodiment, the resource usage of the application 120 in the container 110 includes one or more of the use frequency, input / output delay, memory occupation, network bandwidth occupation and response speed of the application 120.

[0098] In this embodiment, the data tag is a blockchain data tag, which can ensure the uniqueness and authenticity of the data, so that the data is not easy to be tampered with, and accordingly the security and effectiveness of the data can be ensured.

[0099] As an embodiment, the data tag processing module 160 marks the resource usage of the application 120 in the container 110 based on the tag processing request, and outputs a data tag.

[0100] In combination with reference Figure 6 , a flowchart of an embodiment of step S2 is shown. As an embodiment, the step of marking the resource usage of the application 120 in the container 110 includes:

[0101] Step S21: Analyzing and processing the tag processing request, outputting any one or both of a service registration command and a tag acquisition command.

[0102] The service registration command is used for registration or deregistration of the specified application 120 for tag marking service; and the tag acquisition command is used for data tag acquisition.

[0103] As an embodiment, the tag processing request is analyzed and processed by the command parser 161, and any one or both of a service registration command and a tag acquisition command is outputted.

[0104] Step S22: Based on the service registration command, the specified application is registered or deregistered for tag service.

[0105] In this embodiment, the service registration command includes a registration command and a deregistration command.

[0106] As an embodiment, the service builder 162 registers or deregisters the specified application 120 for tag service based on the service registration command.

[0107] The registration of the specified application 120 for tag service enables the specified application 120 to have the qualification for tag service, and accordingly the subsequent acquisition and generation of the tag for the application 120 with the qualification for tag service can be performed.

[0108] In this embodiment, the step of registering a tag service for a specified application 120 includes: determining whether the specified application 120 is running based on the registration command; when the application 120 is running, determining whether the application 120 has already registered for a tag service; when the application 120 has not registered for a tag service, adding the application's tag service registration record to the service record pool to complete the tag service registration for the application 120; and exiting the tag service registration for the application 120 when the application 120 is not running or has already registered for a tag service.

[0109] The labeling service of the specified application 120 is deregistered, thereby making the specified application 120 ineligible to provide labeling services based on actual needs.

[0110] In this embodiment, the step of deregistering the tag service for a specified application 120 includes: determining whether the application 120 has registered for the tag service based on the deregistration command; if so, deleting the registration record of the current application 120 from the service record pool; if not, exiting the deregistration process for the tag service of the application 120.

[0111] Step S23: Based on the tag acquisition command, query and mark the resource usage of the application 120 that is running and has registered tag service in the container 110, and output the corresponding data tags.

[0112] As an example, the tag generator 163, based on the tag acquisition command, queries and marks the resource usage of the application 120, which is in the running state and has a registered tag service, within the container 110, and outputs the corresponding data tags.

[0113] Specifically, when the tag generator 163 receives the tag acquisition command, it queries whether the application 120 is running; if the application 120 is not running, it exits; if the application 120 is running, it queries whether the application 120 has a tag registration service; if the application 120 has a tag registration service, it queries and marks the resource usage of the application 120 in the container 110 and outputs the corresponding data tags; if the application 120 does not have a tag registration service, it exits.

[0114] Although the present application has been disclosed with reference to the above embodiments, the application is not limited to the above embodiments. It will be apparent to those skilled in the art that various modifications and changes can be made thereto without departing from the spirit and scope of the application. The scope of the application should be limited only by the appended claims.

Claims

1. A container system framework, comprising one or more independently running containers, wherein multiple applications run within the containers, characterized in that, The container system framework includes: The container client is used to initiate tag processing requests; The container daemon includes a container engine, which is used to perform corresponding operations based on the tag processing request, and the container engine includes a data tag processing module, which is used to mark the resource usage of the application in the container based on the tag processing request and output data tags to the container client. The data tag processing module includes: a command parser, used to parse and process the tag processing request, and output any one or both of the service registration command and the tag acquisition command; A service builder is used to register or deregister a tag service for a specified application based on the service registration command. The tag generator is used to query and mark the resource usage of applications that are running and have registered tag services within the container based on the tag acquisition command, and output the corresponding data tags. The container system framework also includes: a container driver library, which is used to customize the execution environment of the container. The container driver library is connected to the host operating system and is also used to call the resources of the host operating system. The tag generator is used to query the resource usage of the application within the container through the interface between the container driver library and the host operating system, and output the corresponding data tags. The data tags include one or more of the following: application usage count, input / output latency, memory usage, network bandwidth usage, and response speed.

2. The container system framework as described in claim 1, characterized in that, The container client is also used to initiate operation requests to create and run containers; The container daemon is used to receive and process the operation request and the tag processing request; the container daemon also includes a container server, which is used to receive the operation request and the tag processing request, and to forward the operation request and the tag processing request to the container engine. The container engine is also used to perform corresponding operations based on the operation request.

3. The container system framework as described in claim 2, characterized in that, The container engine further includes a basic transaction processing module, which is used to perform basic operation processing based on the operation request, and is also used to receive the tag processing request and perform preliminary parsing processing on the tag processing request, and after performing preliminary parsing processing on the tag processing request, send the tag processing request to the data tag processing module.

4. The container system framework as described in claim 1, characterized in that, The data tag processing module is a blockchain data tag processing module.

5. An Internet of Things (IoT) architecture, characterized in that, include: Cloud platform; An edge-side architecture, comprising: a container system framework as described in any one of claims 1 to 4, wherein the container system framework outputs data tags; The security component includes a blockchain engine, which is used to accelerate the processing of the data tags, obtain processed data, and upload the processed data to the cloud platform.

6. A data processing method applied to a container system framework as described in any one of claims 1 to 4, wherein the container system framework comprises one or more independently running containers, and multiple applications run within each container; characterized in that, The data processing method applied to the container system framework includes: Initiate a tag processing request; Based on the tag processing request, the resource usage of the application within the container is marked, and data tags are output; The step of tagging the resource usage of an application within the container includes: parsing the tag processing request and outputting one or both of a service registration command and a tag acquisition command; registering or deregistering the tag service for the specified application based on the service registration command; and querying and tagging the resource usage of the running application with registered tag services within the container based on the tag acquisition command, and outputting the corresponding data tags.

7. The data processing method as described in claim 6, characterized in that, The service registration command includes a registration command and a deregistration command; Registering a specified application for tag services includes: based on the registration command, determining whether the specified application is running; if the application is running, determining whether the application has already registered for tag services; if the application has not registered for tag services, adding the application's tag service registration record to the service record pool to complete the registration of the application's tag services; if the application is not running or the application has already registered for tag services, exiting the registration process for the application's tag services. Unregistering a specified application from the tag service includes: based on the unregistration command, determining whether the application has registered for the tag service; if so, deleting the current application's registration record from the service record pool; if not, exiting the unregistration process for the application from the tag service.

8. The data processing method as described in claim 6, characterized in that, The resource usage of the application within the container includes one or more of the following: application usage frequency, input / output latency, memory usage, network bandwidth usage, and response speed.

9. The data processing method as described in claim 6, characterized in that, The data tag is a blockchain data tag.

Images