CN108881455B - Data packaging and transmission method in heterogeneous cloud storage system of low-capacity storage node - Google Patents
Data packaging and transmission method in heterogeneous cloud storage system of low-capacity storage node Download PDFInfo
- Publication number
- CN108881455B CN108881455B CN201810687916.7A CN201810687916A CN108881455B CN 108881455 B CN108881455 B CN 108881455B CN 201810687916 A CN201810687916 A CN 201810687916A CN 108881455 B CN108881455 B CN 108881455B
- Authority
- CN
- China
- Prior art keywords
- mirror image
- node
- data
- platform
- management platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
Abstract
The invention provides a data encapsulation and transmission method in a heterogeneous cloud storage system of a low-capacity storage node. The function generalization of the front-end sensor is realized, the specific IoT platform is not required to be pre-programmed, the data processing environment can be more seamlessly adapted by acquiring different container images, the IoT system can be more conveniently constructed and modified, and the construction and maintenance cost of the system and the investment of hardware are saved.
Description
Technical Field
The invention relates to the field of data transmission, in particular to a universal data packaging, converting, transmitting and storing method aiming at multi-manufacturer heterogeneous sensor equipment based on a container packaging technology, and solves the problems of butt joint and data transmission between a sensor node and a universal storage management platform in the heterogeneous Internet of Things (IoT).
Background
In recent years, cloud storage systems have been widely used in data intensive data management. For such applications that the front end has low requirements on computing capability and data collection is very frequent, but analysis and processing of data can delay processing, generally, a cloud computing architecture with a low-capacity storage node as the front end can be used to construct a corresponding system. The internet of things (IoT) is a typical representative of such cloud storage systems with low capacity front-end nodes. On the other hand, under the promotion of the commercialization process of related technologies and components such as wireless modules, sensors and microcontrollers which are necessary in the internet of things (IoT), because the cost is low and the acquisition method is simple and convenient, the rapid growth trend of the deployment of the general IoT service platform on public clouds is very obvious, and the application of the IoT service in the actual production environment is widely popularized and rapidly developed.
In such systems, the front-end node needs to specify a transport protocol and a storage interface protocol when communicating with the IoT service platform at the back-end. But at present, the industry does not form a uniform protocol, but still stays in a state of mixing and coexisting various private protocols. Generally, the basic flow of IoT system traffic processing mainly involves three functional modules: 1) and the connection equipment management is responsible for authentication, connection, data conversion and equipment management of the sensor. 2) Data storage and data analysis, and storage, analysis and processing of the acquired data are realized. 3) The vertical industry analysis application solves the problems related to specific services, such as data analysis, data visualization display, data reuse and the like, of an IoT system in a specific field application, and the general architecture of the IoT system is shown in FIG. 1.
If an IoT sensor, an IoT gateway, a storage and analysis processing module of a backend, and a service platform in an IoT system are all provided end-to-end by a single vendor, the IoT system is said to be in a homogeneous mode. In the process of processing services by the IoT system with the isomorphic mode, protocol differences do not exist among nodes and between the nodes and a back-end service platform, so that the processes of protocol adaptation, data format conversion and the like are not needed.
However, as the demand of IoT system applications rapidly increases, on one hand, the suppliers of IoT networking devices, the types and the number of networking devices increase dramatically, and it is very likely that products of different manufacturers are different in data model, storage format and transmission protocol; on the other hand, inside a specific IoT configuration scenario, due to the different requirements for temperature, gravity, humidity, gas detection, etc., the system must simultaneously require a plurality of different kinds of sensors with different characteristics provided by suppliers; third, the expansion of the IoT system application domain also leads to more and more vendors that provide application service platforms of different types at the backend. Thus, in such complex diverse IoT systems, the homogeneous processing model is clearly inadequate for administrative work. For such systems, three key issues need to be addressed: 1) the problems of standardization of data formats and standardization of transmission protocols of sensors of different suppliers are solved, and further a cloud computing platform is utilized to perform analysis processing by a single program. 2) And a security guarantee mechanism in the transmission process is provided, and security processing mechanisms such as signature algorithms and the like which are different from different manufacturers are uniformly handled. 3) And periodically updating the built-in processing module of the heterogeneous sensor according to programs provided by different manufacturers.
The typical solution today is to provide a Software Development Kit (SDK) in the gateway that programs the IoT gateway, implementing protocol adaptation and data transformation, such as microsoft Azure platform. This approach requires each sensor manufacturer to design the data format, communication protocol, etc. that implements the home sensor based on a particular SDK. Obviously, the method has very large limitation on the sensor manufacturer, the limitation comes from various aspects such as an operating system, a program language, and a data format and a protocol type of the SDK, so that upgrading and evolution of the sensor and platform application services are restricted, and workload is large, so that updating and releasing are inconvenient; meanwhile, the sensor product is not suitable for a plurality of SDK platforms, and the universality of the sensor product is also limited, so that the compatibility of the IoT system is poor, and thus the expansibility of the IoT system is also affected.
Disclosure of Invention
In order to overcome the defects of the prior art and overcome the defects of an IoT system isomorphic mode and a heterogeneous system in an SDK processing mode, the invention provides a general management platform realized by using a container technology to replace the function of an SDK, realize the corresponding management of a container mirror image and a container example, autonomously realize the data conversion related to sensor equipment by a sensor manufacturer, and perform packaging, publishing, registering, discovering, updating and running in the container mode. When the sensor is released, only one universal agent (agent, namely the running environment of the container mirror image) is loaded, and basic mirror images and protocol programs facing all platform service manufacturers do not need to be provided, so that the characteristic of low capacity of the nodes is better adapted, the universal management platform is separated from specific implementation, and the purpose of packaging the specific implementation and the environment is achieved.
The technical scheme adopted by the invention for solving the technical problem comprises the following steps:
step 1: universal management platform initialization
Initializing a management platform information summary table, a registered node information table, a registered platform service information table and a mirror image information table of a mirror image warehouse in a rear-end general management platform, initializing a container mirror image warehouse, and setting a monitoring mechanism, namely periodically detecting related requests of rear-end general management platform service and front-end nodes, wherein the requests include but are not limited to registration, updating and deletion;
step 2: backend generic management platform service registration
A platform service provider sends a registration application to a back-end general management platform, the back-end general management platform registers in a corresponding information table after receiving the request of the registration application, and stores a basic mirror image and a protocol processing program uploaded by the platform service provider in a container mirror image warehouse, and the back-end general management platform monitors the registration of a front-end node and the registration request of back-end platform service;
and step 3: front end node registration
Step 3.1: in the IP-enabled gateway of a given front-end node's micro-processing device or a set of homogeneous sensors, a container operating environment is built in which the micro-processing device or homogeneous sensors can operate, namely, the container operating environment is a general-purpose agent;
step 3.2: the user selects the service type of the back-end platform through the general agent according to the self equipment type and the service requirement, starts the container operation environment, operates a container mirror image corresponding to the service type of the target platform, and then the general agent of the front-end node sends a 'registration' request to the back-end general management platform;
step 3.3: the back-end general management platform updates a platform information total table and a registered node table according to a registration request of the front-end node, modifies the number field of corresponding nodes in a container mirror image table, adds the ID of the node in the corresponding platform service node in the registered platform service information table, establishes the association between the node and the platform service and the corresponding container mirror image in a container mirror image warehouse, packs a target container mirror image and informs the front-end node;
step 3.4: the front-end node downloads the required container mirror image package from the container warehouse according to the notification returned by the back-end general management platform, and the local general agent starts the container mirror image package to form a mirror image instance; the mirror image instance completes the establishment of connection at two ends and the conversion and encryption processing of a data transmission format according to a protocol defined by the platform service, establishes a channel for data transmission and processing, and sends local data stored by the sensor to the back-end general management platform service;
and 4, step 4: deploying services
Firstly, after the initialization of a node is finished, data acquisition is carried out on sensor equipment, a general agent carries out format conversion on the data according to an acquired protocol definition, and standardized data are encrypted and transmitted to a back-end general management platform; the data receiving module of the rear-end universal management platform decrypts the received data after receiving the data, cleans and analyzes the data according to the specific requirements of the platform service application, and stores the data into a cloud storage or cloud database; finally, the corresponding application service in the platform service acquires data from the cloud storage according to the content of the specific service and processes the data;
and 5: update, change processing
The back-end general management platform periodically monitors the update and change requests of the services of the front-end nodes and the back-end platform, and finishes updating the mirror image warehouse, adding and deleting the services of the front-end nodes and upgrading the platform by maintaining each information table and each storage area in the back-end general management platform.
The invention has the beneficial effects that the isolation among different layers and the independent updating of each layer are realized in a layered packaging mode. The function generalization of the front-end sensor is realized, the specific IoT platform does not need to be pre-programmed, and the data processing environment can be more seamlessly adapted by acquiring different container images. The IoT system can be constructed and modified more conveniently, and the construction and maintenance cost of the system and the investment of hardware are saved.
Drawings
Fig. 1 is a schematic diagram of an IoT system traffic processing basic flow.
FIG. 2 is a logical schematic of the container mirror layered packaging of the present invention.
Fig. 3 is a schematic diagram illustrating the content of the container mirror key according to the present invention.
FIG. 4 is a schematic diagram of the major tables and their interrelationships maintained in the platform management of the present invention.
Fig. 5 is a data structure diagram of nodes in each table in the platform management of the present invention.
Detailed Description
The invention is further illustrated with reference to the following figures and examples.
The invention has the following implementation steps:
step 1: universal management platform initialization
In the general management platform of the back end, initializing a management platform information summary table, a registered node information table, a registered platform service information table and a mirror image information table of a mirror image warehouse, wherein the logical relationship of each table and the data structure of specific content in each table are shown in fig. 4 and fig. 5, initializing a container mirror image warehouse, and setting a monitoring mechanism, namely periodically detecting related requests of the general management platform service of the back end and a front end node, wherein the requests include but are not limited to registration, updating and deletion;
step 2: and (5) registering the back-end general management platform service.
A platform service provider sends a registration application to a back-end general management platform, the back-end general management platform registers in a corresponding information table after receiving the request of the registration application, and stores a basic mirror image and a protocol processing program uploaded by the platform service provider in a container mirror image warehouse, and the back-end general management platform monitors the registration of a front-end node and the registration request of back-end platform service;
and step 3: front end node registration
Step 3.1: in the IP-enabled gateway of a given front-end node's micro-processing device or a set of homogeneous sensors, a container operating environment is built in which the micro-processing device or homogeneous sensors can operate, namely, the container operating environment is a general-purpose agent;
step 3.2: the user selects the service type of the back-end platform through the general agent according to the self equipment type and the service requirement, starts the container operation environment, operates a container mirror image corresponding to the service type of the target platform, and then the general agent of the front-end node sends a 'registration' request to the back-end general management platform;
step 3.3: the back-end general management platform updates a platform information total table and a registered node table according to a registration request of the front-end node, modifies the number field of corresponding nodes in a container mirror image table, adds the ID of the node in the corresponding platform service node in the registered platform service information table, establishes the association between the node and the platform service and the corresponding container mirror image in a container mirror image warehouse, packs a target container mirror image and informs the front-end node;
step 3.4: the front-end node downloads the required container mirror image package from the container warehouse according to the notification returned by the back-end general management platform, and the local general agent starts the container mirror image package to form a mirror image instance; the mirror image instance completes the establishment of connection at two ends and the conversion and encryption processing of a data transmission format according to a protocol defined by the platform service, establishes a channel for data transmission and processing, and sends local data stored by the sensor to the back-end general management platform service;
and 4, step 4: firstly, after the initialization of a node is completed, data acquisition is carried out on sensor equipment, a general agent carries out format conversion on the data according to an acquired protocol definition, and standardized data is encrypted and transmitted to a rear-end general management platform; the data receiving module of the rear-end universal management platform decrypts the received data after receiving the data, cleans and analyzes the data according to the specific requirements of the platform service application, and stores the data into a cloud storage or cloud database; finally, the corresponding application service in the platform service acquires data from the cloud storage according to the content of the specific service and processes the data;
and 5: and (5) updating and changing.
The back-end general management platform periodically monitors the update and change requests of the services of the front-end nodes and the back-end platform, and finishes updating the mirror image warehouse, adding and deleting the services of the front-end nodes and upgrading the platform by maintaining each information table and each storage area in the back-end general management platform.
The main content of the invention comprises the following two parts:
the first part
In the back-end IoT gateway, a generic management platform is implemented. The management platform is responsible for the operations of management and maintenance related to registration, discovery, updating, deletion and the like of the container mirror images and controls the process of managing data service processing.
The second part
As shown in fig. 2 and fig. 3, abstract encapsulation and conversion of data of the IoT system front-end device in the container are implemented, that is, a complete container mirroring process is implemented. This section divides the mirrored processing into four layers: the first layer encapsulates a basic mirror image (namely a Thin Operating System, which is a simplified Operating System and is hereinafter referred to as TOS) on the bottom layer of the container mirror image; the second layer is responsible for controlling and processing the work of the general-purpose agent; the third layer is responsible for management work such as gateway protocol communication, equipment discovery, registration, authentication, updating, deletion and the like; and the fourth layer completes data extraction, conversion and packaging of the sensor equipment. The processing work of the first layer and the third layer is completed by a universal management platform, the generation of container mirror images is provided, and packaging is completed; the second layer and the third layer are packaged by each manufacturer according to the type and the data model of the sensor equipment of the manufacturer, and the packaging is completed in a universal agent environment.
First, specific meanings of main terms related to the present invention are as follows.
1) And (3) node: sensor devices operating as clients in IoT systems, with low storage capacity and limited computing power, are produced by different vendors. The nodes comprise an IP type and a non-IP type, the former is internally provided with a proxy and can directly run a container instance, the latter needs to be configured with an IP-enabled gateway (in a homogeneous system, a plurality of sensors can share one gateway), and the container instance is run on the gateway.
2) A container: a relatively independent operating environment including programs and a reduced operating system. Containers are not completely independent as are virtual machines. But within the container, the external influence is controlled to a minimum.
3) Container mirroring: in the general management platform of the IoT, according to definition information provided by a platform service provider, resources such as corresponding operating systems and protocols are acquired from an image repository to construct a generated container. Including the common layer (the reduced operating system) and the protocol translation layer, are typically packaged for download and use by the nodes.
4) Example of the vessel: the container instance refers to a container mirror image downloaded from a general management platform by the node according to specific requirements and starts to run, and provides programming and running environments for running the custom program matched with the background application platform by the sensor. The container instance runs on the node (for IP class nodes, it runs inside the node; for non-IP class devices, it runs on the gateway.
5) A container warehouse: a set of container images created and maintained in a common management platform. The system mainly comprises a basic mirror image program set, a protocol processing program set, container mirror image metadata used for management and maintenance and other related information.
1. Joining of new nodes
New sensor devices join systems, including two types: one is the joining of a new node, which means that the newly joined node belongs to the registered node type; and the other is new product addition, and the new product is registered in the general management platform.
The specific treatment is as follows:
firstly, initializing N _ flag to-1, and then entering step (II)
The new device sends a 'node joining' request to a universal management platform at the rear end, the universal management platform searches a corresponding registered service metadata record in a registered platform service information table according to the service name and the service manufacturer name information in the request, if the service name and the service manufacturer name information in the request are found, the device is added as a new node, a container mirror image ID1 in the metadata record is obtained, N _ flag is set to be 0, otherwise, N _ flag is set to be 1 for new product addition. Step III
Thirdly, if N _ flag is equal to 0, acquiring a container mirror image ID1 according to the step two, and searching a corresponding container mirror image element data record M in a mirror image information table of a mirror image warehouseoGo directly to step (c)
If N _ flag is 1, a new node metadata record V is created and initializednewIs a number VnewAssign a new node ID, fill in VnewThe information of fields such as node ID, node manufacturer name and registration time enters the fifth step
Creating and initializing a container mirror metadata record MnewIs MnewAssign a new container image ID, fill in M based on known informationnewAccording to the service name and the service manufacturer name, searching the matched platform service metadata record S in the registered platform service information tableoObtaining SoService ID and container image ID1, MnewThe value of the container mirror ID of (1) is added to SoAt the end of the container mirror image ID list, go to step |)
Sixthly, according to the container mirror image ID1, the corresponding container mirror image element data record M is searched in the mirror image information table of the mirror image warehouseoWill MoCopying the values of fields such as protocol ID, basic image ID, protocol address, basic image address and image version to MnewCorresponding field of V, willnewNode ID value of (2) appended to MnewUpdate the mirror version information to V at the end of the node ID listnewThe mirror version field of (c), step (c)
Seventhly, the general service platform is based on MoThe protocol and basic mirror image information in (1) packaging container mirror image, returning ready notice to the equipment sending node joining request, after the new equipment receives the ready notice, downloading the packaged container mirror image, running in the local general agent, and going to the step (b)
And the nodes are ready and can interactively develop services with a rear end.
2. Processing of container image updates
There are three types of triggers in the update process, one is front-end-only update, one is backend-only platform service update, and the third is simultaneous update of the front-end-and backend-platform services. In a specific implementation, the three types of updates may be processed uniformly, specifically as follows:
setting UV _ flag to 0 and US _ flag to 0, and entering step (C)
② front end node VaWhen the equipment is upgraded and updated, the container mirror image example of the node sends a node updating notice to the general management platform, and the step III is carried out, wherein the UV _ flag is set to be 1
Third, serve as the back end platform SaWhen the program is updated, the application universal management platform sends out a mirror image updating notice, sets US _ flag to 1, and enters the step (c)
If the UV _ flag is 1, the general management platform is according to VaSearching corresponding node ID in the node information table, acquiring container mirror image ID and node manufacturer name from corresponding node metadata record, and informing node VaMarking the data to be updated as data to be uploaded pkg _ v, packaging the data to be uploaded and uploading the data to be uploaded to a general management platform; entering the step five
If the US _ flag is 1, the universal management platform searches a corresponding platform service metadata record in the platform service information table according to the platform service ID information notified by the update, acquires a container mirror image ID list and a service manufacturer name from the metadata record, acquires and records a specific address new _ addr of a program storing the platform service update, and packages and marks the corresponding program as pkg _ m; according to the container mirror image ID list, positioning corresponding container mirror image data records one by one in a mirror image information table of a mirror image warehouse, updating corresponding program addresses (basic mirror image addresses or protocol addresses) in the container mirror image data records according to the new _ addr, completing the updating times +1, and updating mirror image version information; step (ii) is
Sixthly, if the US _ flag is equal to 0, entering a step seventhly; otherwise, followAnd circularly scanning each container mirror ID in the acquired container mirror ID list, and processing as follows: finding container mirror image element data record M corresponding to current container mirror image ID in mirror image information table of mirror image warehouseiTo MiAnd all front end nodes corresponding to each node ID in the intermediate node ID list send mirror image updating notifications, and each front end node updates the local container mirror image according to the notification download pkg _ m data packet, and returns a download completion notification to the general management platform after the download is completed. The back end informs MiAnd a value of +1 of a field 'download times' of (a) and searching for a node metadata record V having the same node ID in a registered node information tablejChanging VjAnd entering the value of the field 'mirror image update times' plus 1 into step (c)
Seventhly, if the UV _ flag is equal to 0, directly entering the step ((b)); otherwise, searching the corresponding container mirror element data record M in the mirror image information table of the mirror image warehouse according to the container mirror image ID obtained in the step IVVUpdate MVThe container mirror image key field of the M, and the information of two fields of ' device type ' and ' device versionVAll front-end nodes corresponding to all records in the node ID list send ' node update ' notification, each front-end node downloads pkg _ v data packets according to the notification, updates the local node, searches node metadata records with the same node ID in a registered node information table, and enters the step ' +1
And (8) finishing the updating process.
3. Node deletion processing
The specific treatment is as follows:
firstly, when the front end node sends a deletion request to the rear end general management platform, the general management platform searches the corresponding record V in the registered node information table according to the node ID information of the nodedFrom VdObtaining container mirror image ID, proceeding to step 2
Secondly, the back-end general management platform searches corresponding container mirror image element data records in a mirror image information table of the mirror image warehouse according to the value of the container mirror image IDMdAt MdIs searched for and V in the node listdAnd one item corresponding to the matched node ID. If the node ID is not the only entry in the node list, then only delete that entry; otherwise, delete the entire record MdGo to step III
Deleting V in registered node information table by back-end general management platformdAnd returns the notification of the completion of the deletion of the information table to the requesting front-end node, and the step (iv) is entered
And fourthly, after receiving the return notification, the front-end node stops the running of the mirror image instance and terminates the data interaction with the back-end general management platform and the platform service. The node deletion process is completed.
The present invention is not limited to the foregoing embodiments, and the present invention is applicable to any service platform that is connected to a high-speed network connection device through a heterogeneous terminal device with certain computation and storage capabilities, where the platform is responsible for monitoring and managing an application system related to problems such as compatibility, adaptation, data exchange, update, and maintenance of the corresponding device.
Claims (1)
1. A data encapsulation and transmission method in a heterogeneous cloud storage system of a low-capacity storage node is characterized by comprising the following steps:
step 1: universal management platform initialization
Initializing a management platform information summary table, a registered node information table, a registered platform service information table and a mirror image information table of a mirror image warehouse in a rear-end general management platform, initializing a container mirror image warehouse, and setting a monitoring mechanism, namely periodically detecting related requests of rear-end general management platform service and front-end nodes, wherein the requests include but are not limited to registration, updating and deletion;
step 2: backend generic management platform service registration
A platform service provider sends a registration application to a back-end general management platform, the back-end general management platform registers in a corresponding information table after receiving the request of the registration application, and stores a basic mirror image and a protocol processing program uploaded by the platform service provider in a container mirror image warehouse, and the back-end general management platform monitors the registration of a front-end node and the registration request of back-end platform service;
and step 3: front end node registration
Step 3.1: in the IP-enabled gateway of a given front-end node's micro-processing device or a set of homogeneous sensors, a container operating environment is built in which the micro-processing device or homogeneous sensors can operate, namely, the container operating environment is a general-purpose agent;
step 3.2: the user selects the service type of the back-end platform through the general agent according to the self equipment type and the service requirement, starts the container operation environment, operates a container mirror image corresponding to the service type of the target platform, and then the general agent of the front-end node sends a 'registration' request to the back-end general management platform;
step 3.3: the back-end general management platform updates a platform information total table and a registered node table according to a registration request of the front-end node, modifies the number field of corresponding nodes in a container mirror image table, adds the ID of the node in the corresponding platform service node in the registered platform service information table, establishes the association between the node and the platform service and the corresponding container mirror image in a container mirror image warehouse, packs a target container mirror image and informs the front-end node;
step 3.4: the front-end node downloads the required container mirror image package from the container warehouse according to the notification returned by the back-end general management platform, and the local general agent starts the container mirror image package to form a mirror image instance; the mirror image instance completes the establishment of connection at two ends and the conversion and encryption processing of a data transmission format according to a protocol defined by the platform service, establishes a channel for data transmission and processing, and sends local data stored by the sensor to the back-end general management platform service;
and 4, step 4: deploying services
Firstly, after the initialization of a node is finished, data acquisition is carried out on sensor equipment, a general agent carries out format conversion on the data according to an acquired protocol definition, and standardized data are encrypted and transmitted to a back-end general management platform; the data receiving module of the rear-end universal management platform decrypts the received data after receiving the data, cleans and analyzes the data according to the specific requirements of the platform service application, and stores the data into a cloud storage or cloud database; finally, the corresponding application service in the platform service acquires data from the cloud storage according to the content of the specific service and processes the data;
and 5: update, change processing
The back-end general management platform periodically monitors the update and change requests of the services of the front-end nodes and the back-end platform, and finishes updating the mirror image warehouse, adding and deleting the services of the front-end nodes and upgrading the platform by maintaining each information table and storage area in the back-end general management platform;
the update processing includes three trigger types, one is only front-end node update, one is only backend platform service update, the third is that the front-end node and backend platform service update simultaneously, and the three types of update are processed uniformly, and the specific processing is as follows:
setting UV _ flag to be 0 and US _ flag to be 0, and entering a step II;
② front end node VaWhen the equipment is upgraded and updated, the container mirror image example of the node sends a node updating notice to the general management platform, and the step III is carried out, wherein the value of UV _ flag is 1;
third, serve as the back end platform SaWhen the program is updated, the application item general management platform sends out a mirror image updating notice, sets US _ flag as 1, and enters a step IV;
if the UV _ flag is 1, the general management platform is according to VaSearching corresponding node ID in the node information table, acquiring container mirror image ID and node manufacturer name from corresponding node metadata record, and informing node VaMarking the data to be updated as data to be uploaded pkg _ v, packaging the data to be uploaded and uploading the data to be uploaded to a general management platform; entering the fifth step;
if the US _ flag is 1, the universal management platform searches a corresponding platform service metadata record in the platform service information table according to the platform service ID information notified by the update, acquires a container mirror image ID list and a service manufacturer name from the metadata record, acquires and records a specific address new _ addr of a program storing the platform service update, and packages and marks the corresponding program as pkg _ m; according to the container mirror image ID list, positioning corresponding container mirror image data records one by one in a mirror image information table of a mirror image warehouse, updating corresponding program addresses (basic mirror image addresses or protocol addresses) in the container mirror image data records according to the new _ addr, completing the updating times +1, and updating mirror image version information; entering the step of sixthly;
seventhly, if the US _ flag is equal to 0, entering the step 0; otherwise, sequentially scanning each container mirror image ID in the obtained container mirror image ID list, and circularly performing the following processing: finding container mirror image element data record M corresponding to current container mirror image ID in mirror image information table of mirror image warehouseiTo MiAll front end nodes corresponding to each node ID in the middle node ID list send mirror image updating notifications, each front end node downloads pkg _ m data packets according to the notifications, updates local container mirror images, and returns a download completion notification to the general management platform after the download is completed; the back end informs MiAnd a value of +1 of a field 'download times' of (a) and searching for a node metadata record V having the same node ID in a registered node information tablejChanging VjThe mirror image version information in (1), and entering step (c) with the value of field mirror image update times + 1;
seventhly, if the UV _ flag is equal to 0, directly entering the step 0; otherwise, searching the corresponding container mirror image element data record M in the mirror image information table of the mirror image warehouse according to the container mirror image ID obtained in the step 0VUpdate MVThe container mirror image key field of the M, and the information of two fields of ' device type ' and ' device versionVAll front end nodes corresponding to all records in the node ID list send a 'node update' notice, each front end node downloads pkg _ v data packets according to the notice, updates a local node, searches node metadata records with the same node ID in a registered node information table, and enters the step (b) with the field 'node update times' +1 of the node metadata records;
and (8) finishing the updating process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810687916.7A CN108881455B (en) | 2018-06-28 | 2018-06-28 | Data packaging and transmission method in heterogeneous cloud storage system of low-capacity storage node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810687916.7A CN108881455B (en) | 2018-06-28 | 2018-06-28 | Data packaging and transmission method in heterogeneous cloud storage system of low-capacity storage node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108881455A CN108881455A (en) | 2018-11-23 |
| CN108881455B true CN108881455B (en) | 2020-12-08 |
Family
ID=64296330
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810687916.7A Active CN108881455B (en) | 2018-06-28 | 2018-06-28 | Data packaging and transmission method in heterogeneous cloud storage system of low-capacity storage node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108881455B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20220303283A1 (en) * | 2019-09-12 | 2022-09-22 | Jabil Inc. | Method and System for Managing Secure IoT Device Applications |
| CN111552494B (en) * | 2020-04-24 | 2021-05-11 | 星环信息科技(上海)股份有限公司 | Method, device, system and medium for managing container group |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103001809A (en) * | 2012-12-25 | 2013-03-27 | 曙光信息产业(北京)有限公司 | Service node state monitoring method for cloud storage system |
| CN106330923A (en) * | 2016-08-26 | 2017-01-11 | 中国联合网络通信集团有限公司 | Kubernetes system-based node registration method, and system |
| CN107220039A (en) * | 2017-04-11 | 2017-09-29 | 国家电网公司 | A kind of heterogeneous resource standardized packages system based on cloud environment |
| CN107580083A (en) * | 2017-09-20 | 2018-01-12 | 北京京东尚科信息技术有限公司 | A kind of method and system of container IP address distribution |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130339510A1 (en) * | 2012-06-15 | 2013-12-19 | Digital River, Inc | Fast provisioning service for cloud computing |
| US10255054B2 (en) * | 2016-04-13 | 2019-04-09 | International Business Machines Corporation | Enforcing security policies for software containers |
-
2018
- 2018-06-28 CN CN201810687916.7A patent/CN108881455B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103001809A (en) * | 2012-12-25 | 2013-03-27 | 曙光信息产业(北京)有限公司 | Service node state monitoring method for cloud storage system |
| CN106330923A (en) * | 2016-08-26 | 2017-01-11 | 中国联合网络通信集团有限公司 | Kubernetes system-based node registration method, and system |
| CN107220039A (en) * | 2017-04-11 | 2017-09-29 | 国家电网公司 | A kind of heterogeneous resource standardized packages system based on cloud environment |
| CN107580083A (en) * | 2017-09-20 | 2018-01-12 | 北京京东尚科信息技术有限公司 | A kind of method and system of container IP address distribution |
Non-Patent Citations (2)
| Title |
|---|
| "Cloudification and Autoscaling Orchestration for Container-Based Mobile Networks toward 5G: Experimentation, Challenges and Perspectives";Duc-Hung Luong等;《2018 IEEE 87th Vehicular Technology Conference (VTC Spring)》;20180626;全文 * |
| "分级存储管理技术研究";赵晓南,李战怀,曾雷杰,张晓;《计算机研究与发展》;20120522;第48卷;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108881455A (en) | 2018-11-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11368522B2 (en) | Lightweight IoT information model | |
| US10009707B2 (en) | Interworking light weight machine-to-machine protocol with device management protocol | |
| US9065813B2 (en) | Adapter device for coupling an industrial field instrument to an industrial wireless network and related system and method | |
| JP6456472B2 (en) | Enhanced operation between service layer and management layer in an M2M system by enabling execution of multiple commands on multiple devices | |
| JP3711866B2 (en) | Framework having plug and play function and reconfiguration method thereof | |
| US11940778B2 (en) | Method of commissioning a field device in an industrial system network | |
| JP2001222500A (en) | Method for distributing program in network gateway | |
| CN108881455B (en) | Data packaging and transmission method in heterogeneous cloud storage system of low-capacity storage node | |
| Leppänen et al. | Mobile agents for integration of internet of things and wireless sensor networks | |
| US20080080550A1 (en) | Plug-and-play reader support for an RF switch | |
| CN103488696A (en) | Business query method, device and system of CPE (customer premises equipment), ACS (auto-configuration server) and CPE | |
| CN103987064A (en) | Access point (AP) upgrading method and device | |
| Vasconcelos et al. | An adaptive middleware for opportunistic mobile sensing | |
| KR102285352B1 (en) | PROXY, METHOD FOR INTERWORKING BETWEEN HETEROGENEOUS IoT DEVICE AND IoT FLATFORM AND SYSTEM THE PROXY | |
| CN116760822A (en) | Method, system and device for transmitting files of Internet of things equipment | |
| Gigan et al. | Sensor Abstraction Layer: a unique software interface to effectively manage sensor networks | |
| Jin et al. | IoT device management architecture based on proxy | |
| CN116743795A (en) | Deployment method for application function configuration of Internet of things | |
| Ye et al. | PIoT: Programmable IoT using information centric networking | |
| CN112637037B (en) | Cross-region container communication system, method, storage medium and computer equipment | |
| CN103532999A (en) | Data transmission method, mobile device and background service system | |
| CN102546237B (en) | Device management server, client and target operation object positioning method | |
| KR20230115878A (en) | Method and apparatus for calibrating device group in machine to machine system | |
| CN116708508A (en) | Network target range communication method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220620 Address after: 201100 room 13, floor 2, building 4, No. 728, Guanghua Road, Minhang District, Shanghai Patentee after: SHANGHAI DI'AN TECHNOLOGY Co.,Ltd. Address before: 710072 No. 127 Youyi West Road, Shaanxi, Xi'an Patentee before: Northwestern Polytechnical University |
|
| TR01 | Transfer of patent right |