CN114422618A - IOT platform protocol adaptation method, device, equipment and medium based on cloud protogenesis - Google Patents
IOT platform protocol adaptation method, device, equipment and medium based on cloud protogenesis Download PDFInfo
- Publication number
- CN114422618A CN114422618A CN202111674480.6A CN202111674480A CN114422618A CN 114422618 A CN114422618 A CN 114422618A CN 202111674480 A CN202111674480 A CN 202111674480A CN 114422618 A CN114422618 A CN 114422618A
- Authority
- CN
- China
- Prior art keywords
- iot platform
- cloud
- adaptation
- container
- component
- 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.)
- Granted
Links
- 230000006978 adaptation Effects 0.000 title claims abstract description 166
- 238000000034 method Methods 0.000 title claims abstract description 58
- 238000012795 verification Methods 0.000 claims abstract description 14
- 230000005540 biological transmission Effects 0.000 claims description 11
- 238000004458 analytical method Methods 0.000 claims description 7
- 238000013507 mapping Methods 0.000 claims description 6
- 238000006243 chemical reaction Methods 0.000 claims description 4
- 238000012546 transfer Methods 0.000 claims description 4
- 238000003860 storage Methods 0.000 abstract description 11
- 238000005516 engineering process Methods 0.000 abstract description 4
- 230000000694 effects Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 230000000712 assembly Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- 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
-
- 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/2866—Architectures; Arrangements
- H04L67/30—Profiles
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses a cloud-native-based IOT platform protocol adaptation method, a device, equipment and a storage medium, wherein the method comprises the following steps: the cloud IOT platform issues a product adaptation component which is assembled in advance according to needs to the edge IOT platform; the side IOT platform checks the product adaptation component issued by the cloud IOT platform; if the verification is passed, the marginal IOT platform creates a resource deployment file and a service configuration file according to the product adaptation component; and the marginal IOT platform starts a container according to the resource deployment file and the service configuration file. According to the IOT platform protocol adaptation method based on the cloud-native technology, the network component and the protocol component of the equipment can be flexibly selected according to requirements, and meanwhile, the resources of the container are managed based on the cloud-native technology, so that the effects of flexible equipment access and balanced hardware resource load are achieved. The device can be conveniently accessed to the Internet of things platform, and the network adaptation and the protocol adaptation can be realized.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a cloud-native-based IOT platform protocol adaptation method, device, equipment and medium.
Background
In the equipment access work of the Internet of things industry, particularly in the equipment access process of the Internet of things of the traffic industry, the Internet of things platform is adaptive to equipment access work of multiple manufacturers and multiple protocols. Different equipment manufacturers use respective specifications and can use various protocols according to different projects, so that huge challenges are brought to equipment access of the Internet of things in the traffic industry. Therefore, an internet of things platform scheme meeting flexible access of various devices needs to be implemented urgently.
Disclosure of Invention
The embodiment of the application provides a cloud-native-based IOT platform protocol adaptation method, device, equipment and medium. The following presents a simplified summary in order to provide a basic understanding of some aspects of the disclosed embodiments. This summary is not an extensive overview and is intended to neither identify key/critical elements nor delineate the scope of such embodiments. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.
In a first aspect, an embodiment of the present application provides a cloud-based IOT platform protocol adaptation method, including:
the cloud IOT platform issues a product adaptation component which is assembled in advance according to needs to the edge IOT platform;
the method comprises the steps that an edge IOT platform checks a product adaptation component issued by a cloud IOT platform;
if the verification is passed, the marginal IOT platform creates a resource deployment file and a service configuration file according to the product adaptation component;
and the marginal IOT platform starts the container according to the resource deployment file and the service configuration file.
In an optional embodiment, before the cloud IOT platform issues the product adaptation component assembled in advance as needed to the edge IOT platform, the method further includes:
the cloud IOT platform selects the type, address, port and private configuration item of the network component according to the data transmission protocol and network transmission protocol required by the accessed edge IOT platform and the terminal device to obtain a configured network adaptation component;
the cloud IOT platform obtains a configured protocol adaptation component according to a protocol adaptation packet developed by the project access equipment and the configured component analysis parameters;
the cloud IOT platform creates product metadata according to the product specification and the product description information, associates the network adaptation component and the protocol adaptation component, and obtains a product adaptation component assembled according to needs.
In an optional embodiment, the verifying, by the frontend IOT platform, the product adaptation component issued by the cloud IOT platform includes:
the side IOT platform checks the type support, IP address availability and port availability of the network adaptation component;
and checking the format support and the data integrity of the protocol adaptation component.
In an optional embodiment, the edge IOT platform creates the resource deployment file and the service configuration file according to the product adaptation component, including:
loading a preset resource deployment file template by the edge IOT platform, initializing initcontainers items by a configuration container according to the resource deployment file template and the configuration information of the product adaptation component, assembling the address and default configuration items of a protocol adaptation package, and generating a resource deployment file;
the side IOT platform analyzes the configuration information of the network adaptation component, judges whether the network component is a server side or not, loads a preset service configuration file template when the network component is the server side, and generates a service configuration file according to the service configuration file template and the associated information of the inner port and the outer port of the container in the configuration information.
In an optional embodiment, the side IOT platform starts the container according to the resource deployment file and the service configuration file, including:
calling an API (application program interface) of K8S, pushing configuration information of the service configuration file to a K8S cluster main node server, and obtaining a mapping relation between an inner port and an outer port of the container;
and calling the API interface of the K8S, pushing the configuration information of the resource deployment file to the K8S cluster main node server, starting a container, and simultaneously starting a Pod watch listening state.
In an optional embodiment, pushing the configuration information of the resource deployment file to the K8S cluster master node server and starting the container, and simultaneously starting the Pod watch listening state includes:
according to configuration information of the resource deployment file, pulling a container base mirror image from a mirror image warehouse to an edge IOT platform;
according to the configuration information of the resource deployment file, pulling a protocol adaptation packet from a file transfer protocol server to an edge IOT platform;
when the container is started, loading the protocol adaptation package which is mounted in the container to the program context, and after the container is started successfully, starting a Pod Watch thread to report the Pod state.
In an optional embodiment, starting the Pod Watch thread to report the Pod status includes:
receiving data reported by equipment by a container;
the container calls a protocol adaptation packet internal analysis transcoding program, and data reported by the equipment is converted into a format common to the IOT platform;
the side IOT platform checks the data after the container conversion;
and if the verification is passed, the converted data is sent to the cloud IOT platform.
In a second aspect, an embodiment of the present application provides a cloud-native-based IOT platform protocol adaptation apparatus, including:
the cloud IOT platform is used for issuing a product adaptation component which is assembled in advance according to needs to the edge IOT platform;
and the edge IOT platform is used for verifying the product adaptation component issued by the cloud IOT platform, creating a resource deployment file and a service configuration file according to the product adaptation component if the verification is passed, and starting a container according to the resource deployment file and the service configuration file.
In a third aspect, an embodiment of the present application provides a cloud-native-based IOT platform protocol adaptation device, which includes a processor and a memory storing program instructions, where the processor is configured to execute the cloud-native-based IOT platform protocol adaptation method provided in the foregoing embodiment when executing the program instructions.
In a fourth aspect, the present application provides a computer-readable medium, on which computer-readable instructions are stored, where the computer-readable instructions are executed by a processor to implement a cloud-native-based IOT platform protocol adaptation method provided in the foregoing embodiment.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
the IOT platform protocol adaptation method based on cloud protogenesis can flexibly assemble network adaptation components and protocol adaptation components required by equipment in advance according to equipment requirements to obtain product adaptation components, sends the spliced product adaptation components to the edge-end Internet of things platform, and starts a container according to the product adaptation components. The method can flexibly select the network component and the protocol component of the equipment according to the requirements, and simultaneously manages the resources of the container based on the cloud native technology, thereby achieving the effects of flexible access of the equipment and load balancing of hardware resources. The device can be conveniently accessed to the Internet of things platform, and the network adaptation and the protocol adaptation can be realized.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a flowchart illustrating a cloud-native based IOT platform protocol adaptation method in accordance with an exemplary embodiment;
FIG. 2 is a flowchart illustrating an edge IOT platform obtaining assembled protocol adaptation packets in accordance with an illustrative embodiment;
FIG. 3 is a schematic diagram illustrating an edge IOT platform generating and applying resource deployment files and service configuration files in accordance with an illustrative embodiment;
FIG. 4 is a schematic flow diagram illustrating a starting vessel according to an exemplary embodiment;
FIG. 5 is a schematic flow diagram illustrating a process for making a container base image in accordance with an exemplary embodiment;
fig. 6 is a schematic flowchart illustrating a process in which an edge IOT platform synchronizes data reported by a device to a cloud IOT platform according to an exemplary embodiment;
FIG. 7 is a schematic diagram illustrating an architecture of a cloud-native based IOT platform protocol adaptation device, according to an example embodiment;
FIG. 8 is a schematic diagram illustrating a computer storage medium in accordance with an exemplary embodiment.
Detailed Description
The following description and the drawings sufficiently illustrate specific embodiments of the invention to enable those skilled in the art to practice them.
It should be understood that the described embodiments are only some embodiments of the invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of systems and methods consistent with certain aspects of the invention, as detailed in the appended claims.
In the prior art, because multiple manufacturers use respective rules and different project scenes use respective access protocols in an internet of things platform, an internet of things platform scheme meeting flexible access of various devices is in urgent need of implementation. The method and the device aim at providing a solution for the Internet of things platform to adapt to the flexible selection protocol of the devices of multiple manufacturers to complete the access of the devices to the Internet of things, and the purpose that the devices use the protocol flexibly and network components are combined to access the Internet of things platform is achieved.
The cloud-based IOT platform protocol adaptation method provided by the embodiment of the present application will be described in detail below with reference to fig. 1. Referring to fig. 1, the method specifically includes the following steps.
S101 the cloud IOT platform issues the product adaptation components which are assembled in advance according to needs to the edge IOT platform.
In a possible implementation manner, before executing step S101, the method further includes entering network component information and protocol component information in the cloud IOT platform, and combining the adapters as needed.
Specifically, according to one or more accessed edge IOT platforms and a data transmission protocol and a network transmission protocol required by data transmission of terminal equipment, a network adaptation component is input into the cloud IOT platform, and the type, the address, the port and some private configuration items of the component are selected to obtain the configured network adaptation component. Common network adaptation components include HTTP, TCP, MQTT, and the like.
Further, a protocol adaptation packet developed by the equipment to which the project needs to be accessed is uploaded into the protocol adaptation component, and the analysis parameters of the component are configured to obtain the configured protocol adaptation component. The protocol adaptation component is mainly a program package adapted based on the device data protocol.
Further, the cloud IOT platform creates product metadata according to the product specification and the product description information, associates the network adaptation component and the protocol adaptation component, and obtains the product adaptation component assembled according to the requirement. At this point, the flexibly assembled product adapter assemblies are configured. The product is a parent level of one type of equipment, and one product comprises a plurality of equipment.
Further, the cloud IOT platform sends the assembled product adaptation components to one or more corresponding edge IOT platforms, and at the moment, the cloud IOT platform sends the device data, the network adaptation component data and the protocol adaptation component data to the corresponding edge IOT platforms.
And S102, the IOT platform at the side end checks the product adaptation components issued by the cloud IOT platform.
In a possible implementation manner, after the IOT platform at the edge receives the delivered product adaptation component, the IOT platform checks the received product adaptation component.
Specifically, the marginal IOT platform checks the type support, the availability of the IP address and the availability of the port of the network adaptation component, determines whether the type of the network adaptation component is supported, whether the IP address is available, and whether the port is available, checks the format support and the data integrity of the protocol adaptation component, and determines whether the data format of the protocol adaptation component is supported and whether the data is complete.
By verifying the received product adaptation component, the correctness and usability of the product adaptation component can be ensured.
Fig. 2 is a schematic flow chart illustrating a process of obtaining an assembled protocol adaptation package by an edge IOT platform according to an exemplary embodiment, as shown in fig. 2, first logging in a cloud IOT platform, logging in a network adaptation component and a protocol adaptation component, sending the logged-in protocol adaptation package to an FTP server, then creating product metadata according to product specifications and product description information, and associating the network adaptation component and the protocol adaptation component to obtain a product adaptation component assembled as needed. And sending the product adaptation components assembled as required to the edge IOT platform, checking the issued network adaptation components and protocol adaptation components by the edge IOT platform, and pulling the protocol adaptation package from the FTP server if the checking is passed.
S103, if the verification is passed, the marginal IOT platform creates a resource deployment file and a service configuration file according to the product adaptation component.
In a possible implementation manner, if the verification fails, the marginal IOT platform returns information that the verification fails to pass to the cloud IOT platform, and the cloud IOT platform regenerates the product adaptation component and sends the product adaptation component to the marginal IOT platform until the verification of the marginal IOT platform passes.
And if the verification of the edge IOT platform is passed, the edge IOT platform creates a resource deployment file and a service configuration file according to the product adaptation component.
Specifically, the IOT platform at the edge side loads a preset resource deployment file template, initializes initcontainers entries according to the resource deployment file template and configuration information of the product adaptation component, assembles an address and a default configuration entry of the protocol adaptation package, and generates a resource deployment file.
Further, the IOT platform at the side end analyzes the configuration information of the network adaptation component, judges whether the network component is a server side or not, loads a preset service configuration file template when the network component is the server side, and generates a service configuration file according to the service configuration file template and the associated information of the inner port and the outer port of the container in the configuration information. The container port and the physical host port may be mapped according to the service profile.
And S104, the IOT platform at the side end starts the container according to the resource deployment file and the service configuration file.
In a possible implementation manner, after the resource deployment file and the service configuration file are generated, the method further includes starting a container according to the resource deployment file and the service configuration file.
Specifically, an API interface of K8S is called, and the configuration information of the service configuration file is pushed to the K8S cluster master node server, so as to obtain the mapping relationship between the internal and external ports of the container. At this point, a mapping relationship between the internal and external ports of the container has been established.
Further, calling the API interface of K8S, pushing the configuration information of the resource deployment file to the K8S cluster master node server and starting the container, and simultaneously starting the Pod watch listening state.
Fig. 3 is a schematic diagram illustrating an edge IOT platform generating and applying a resource deployment file and a service configuration file according to an exemplary embodiment, as shown in fig. 3, verifying a network adaptation component and a protocol adaptation component, and if the verification passes, loading a preset template to assemble the resource deployment file and the service deployment file. The IOT platform at the side end analyzes the configuration information of the network adaptation component and the protocol adaptation component, initializes initcontainers items according to the resource deployment file template and the configuration information of the product adaptation component, assembles the address and default configuration items of the protocol adaptation package and generates a resource deployment file.
And further, judging whether the network component is a server side, and generating a service configuration file according to the service configuration file template and the associated information of the inner port and the outer port of the container in the configuration information when the network component is the server side. The container port and the physical host port may be mapped according to the service profile.
Further, the service configuration file is applied, the API interface of the K8S is called, the configuration information of the service configuration file is pushed to the K8S cluster main node server, and the mapping relation of the inner port and the outer port of the container is obtained. At this point, a mapping relationship between the internal and external ports of the container has been established. And applying the resource deployment file, calling the API (application program interface) of the K8S, pushing the configuration information of the resource deployment file to the K8S cluster main node server, starting a container, and starting a Pod watch monitoring state at the same time.
In one possible implementation, the detailed starting procedure of the container includes:
firstly, according to the configuration information of the resource deployment file, a container base mirror image is pulled from a mirror image warehouse to an edge IOT platform.
Before pulling the container base image from the image repository according to the configuration information of the resource deployment file, the container base image is further manufactured, fig. 5 is a schematic flow diagram illustrating a process for manufacturing the container base image according to an exemplary embodiment, as shown in fig. 5, Java8-jdk is used as the base image, a program of Adapter Mesh is embedded into a container to be prefabricated as a default starting item, and the image is uploaded to the image repository (product repository Harbor) for subsequent use after the image is manufactured.
Further, according to the configuration information of the resource deployment file, the protocol adaptation packet is pulled from the file transfer protocol server to the edge IOT platform.
Specifically, according to the address configured by initcontainers, a protocol adaptation package is pulled from an FTP (file transfer protocol) server to a storage file of a local server, and the program package is configured to be mounted to a specified position inside the container in a Deployment file of the Deployment resource of the container.
And finally, starting the container, loading the protocol adaptation package which is mounted in the container to the program context, and starting a Pod Watch thread to report the Pod state after the container is successfully started.
Fig. 4 is a schematic flowchart illustrating a container starting process according to an exemplary embodiment, as shown in fig. 4, first, an Adapter Mesh base image is pulled from a product library to a server of an edge IOT platform according to the Deployment file configuration information of the Deployment resource; according to the address configured by initcontainers (initialization container), pulling a protocol adaptation package from the FTP server into a storage file of a local server, wherein the program package is configured to be mounted to a specified position in the container after a resource file is deployed in the Deployment of the Deployment; and then when the Adapter Mesh container is started, loading the protocol adaptation packet which is mounted in the container into the program context, and after the starting is successful, starting a Pod Watch thread to monitor the subsequent state.
In an optional embodiment, starting the Pod Watch thread to report the Pod status includes: the container receives data reported by the equipment, when an internal program of the equipment triggers an event to report a preset threshold value, the data reporting is started, and the data is reported to an Adapter Mesh container through a configured address.
Further, a general interface of the container receives the data reported by the equipment, calls an internal analysis transcoding program of the protocol adaptation package, and converts the data reported by the equipment into an SDK format general for the IOT platform.
Further, the frontend IOT platform checks the data after the container conversion, for example, checks the integrity, format correctness, and the like of the data, and if the check is passed, the converted data is sent to the cloud IOT platform.
Fig. 6 is a schematic flowchart illustrating a process in which an edge IOT platform synchronizes data reported by a device to a cloud IOT platform according to an exemplary embodiment, as shown in fig. 6, when an event triggered by an internal program of the device reports a preset threshold, data reporting is started, and data is reported to an Adapter Mesh container through a configured address. And the container receives the data reported by the equipment, calls an internal analysis transcoding program of the protocol adaptation package, and converts the data reported by the equipment into an SDK format commonly used by the IOT platform. Further, the frontend IOT platform checks the data after the container conversion, for example, checks the integrity, format correctness, and the like of the data, and if the data passes the check, the frontend IOT platform sends the converted data to the cloud IOT platform, and the cloud IOT platform analyzes and displays the received data.
In a specific implementation manner, when a device type is newly added, a network adaptation component and a protocol adaptation component of the device can be flexibly selected according to requirements of a network transmission protocol, a data transmission protocol and the like required by an access device, and the network adaptation component and the protocol adaptation component are assembled into a product adaptation component.
If a new device is accessed, a protocol adaptation component assembled by an access adaptation protocol corresponding to the new device, such as a network transmission protocol, a data transmission protocol and the like, is uploaded to the protocol adaptation component on the basis of an existing protocol adaptation component at the cloud end, but the protocol of the new protocol and the protocol of the existing protocol adaptation component are loosely coupled or mutually isolated, product metadata is created according to the product specification, the product description and other information of the product, the product metadata is associated to the corresponding network adaptation protocol, and the network adaptation protocol is associated with the product, so that the registration of the new device and the flexible addition of the adaptation protocol are completed.
In one embodiment, a new product adapter is separately made for a new product adaptation protocol, i.e. the product adapter of the new device is loosely coupled with an original product adaptation component or is isolated from the original product adapter component, then the adapter is selected by a cloud-based technology to be started, and the configured new protocol can be automatically issued to a corresponding edge IOT platform, and particularly to the edge IOT platform, as shown in the method embodiment, thereby realizing flexible addition of the new device, greatly improving the flexibility of accessing the new device, realizing addition of new devices and protocols without modifying the original protocol adaptation component of the IOT platform, and adopting the method, when the new device type is required, only the cloud new device and the adaptation protocol are needed, and repeated protocol adaptation setting is not needed for a plurality of edge IOT platforms, the workload is greatly reduced, and after the cloud protocol adaptation is completed, the cloud protocol adaptation can be issued to the corresponding edge IOT platform according to the requirements of the edge.
The embodiment of the present application further provides a cloud-native-based IOT platform protocol adaptation device, which includes:
the cloud IOT platform is used for issuing a product adaptation component which is assembled in advance according to needs to the edge IOT platform;
and the edge IOT platform is used for verifying the product adaptation component issued by the cloud IOT platform, creating a resource deployment file and a service configuration file according to the product adaptation component if the verification is passed, and starting a container according to the resource deployment file and the service configuration file.
It should be noted that, when the IOT platform protocol adaptation device based on cloud-based native provided in the foregoing embodiment executes the IOT platform protocol adaptation method based on cloud-based native, only the division of the functional modules is illustrated, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules, so as to complete all or part of the functions described above. In addition, the cloud-based IOT platform protocol adaptation device provided in the foregoing embodiments and the cloud-based IOT platform protocol adaptation method embodiment belong to the same concept, and details of implementation processes thereof are referred to in the method embodiment and are not described herein again.
The embodiment of the present application further provides an electronic device corresponding to the cloud-based IOT platform protocol adaptation method provided in the foregoing embodiment, so as to execute the cloud-based IOT platform protocol adaptation method.
Referring to fig. 7, a schematic diagram of an electronic device provided in some embodiments of the present application is shown. As shown in fig. 7, the electronic apparatus includes: the processor 700, the memory 701, the bus 702 and the communication interface 703, wherein the processor 700, the communication interface 703 and the memory 701 are connected through the bus 702; the memory 701 stores a computer program that can be executed on the processor 700, and when the computer program is executed by the processor 700, the cloud-based IOT platform protocol adaptation method provided by any of the foregoing embodiments of the present application is performed.
The Memory 701 may include a high-speed Random Access Memory (RAM) and may further include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 703 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, and the like can be used.
The processor 700 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 700. The Processor 700 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 701, and the processor 700 reads the information in the memory 701, and completes the steps of the method in combination with the hardware thereof.
The electronic device provided by the embodiment of the application and the IOT platform protocol adaptation method based on cloud-based originality provided by the embodiment of the application have the same beneficial effects as the method adopted, operated or realized by the electronic device.
Referring to fig. 8, the computer-readable storage medium is an optical disc 800, on which a computer program (i.e., a program product) is stored, and when the computer program is executed by a processor, the computer program executes the method for adapting the cloud-native-based IOT platform protocol provided in any of the foregoing embodiments.
It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory, or other optical and magnetic storage media, which are not described in detail herein.
The computer-readable storage medium provided by the above-mentioned embodiment of the present application and the cloud-based native IOT platform protocol adaptation method provided by the embodiment of the present application have the same beneficial effects as the method adopted, operated or implemented by the application program stored in the computer-readable storage medium.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above examples only show some embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. An IOT platform protocol adaptation method based on cloud-native is characterized by comprising the following steps:
the cloud IOT platform issues a product adaptation component which is assembled in advance according to needs to the edge IOT platform;
the side IOT platform checks the product adaptation component issued by the cloud IOT platform;
if the verification is passed, the marginal IOT platform creates a resource deployment file and a service configuration file according to the product adaptation component;
and the marginal IOT platform starts a container according to the resource deployment file and the service configuration file.
2. The method of claim 1, wherein before the cloud IOT platform issues the pre-assembled product adaptation component to the edge IOT platform, the method further comprises:
the cloud IOT platform selects the type, address, port and private configuration item of the network component according to the data transmission protocol and network transmission protocol required by the accessed edge IOT platform and the terminal device to obtain a configured network adaptation component;
the cloud IOT platform obtains a configured protocol adaptation component according to a protocol adaptation packet developed by the project access equipment and the configured component analysis parameters;
and the cloud IOT platform creates product metadata according to the product specification and the product description information, associates the network adaptation component and the protocol adaptation component, and obtains a product adaptation component assembled according to the requirement.
3. The method of claim 2, wherein verifying, by the edge IOT platform, the product adaptation component issued by the cloud IOT platform comprises:
the marginal IOT platform checks the type support, the IP address availability and the port availability of the network adaptation component;
and checking the format support and the data integrity of the protocol adaptation component.
4. The method of claim 2, wherein the edge-side IOT platform creates a resource deployment file and a service configuration file from the product adaptation component, comprising:
loading a preset resource deployment file template by the edge IOT platform, initializing initcontainers items by a configuration container according to the resource deployment file template and the configuration information of the product adaptation component, assembling the address and default configuration items of a protocol adaptation package, and generating the resource deployment file;
and the side IOT platform analyzes the configuration information of the network adaptation component, judges whether the network component is a server side or not, loads a preset service configuration file template when the network component is the server side, and generates the service configuration file according to the service configuration file template and the associated information of the inner port and the outer port of the container in the configuration information.
5. The method of claim 1, wherein the side IOT platform starts a container according to the resource deployment file and a service configuration file, comprising:
calling an API (application program interface) of K8S, pushing configuration information of the service configuration file to a K8S cluster main node server, and obtaining a mapping relation between an inner port and an outer port of the container;
and calling the API interface of the K8S, pushing the configuration information of the resource deployment file to the K8S cluster main node server, starting a container, and simultaneously starting a Pod watch listening state.
6. The method of claim 5, wherein pushing configuration information of the resource deployment file to the K8S cluster master node server and starting the container, and simultaneously starting the Pod watch listening state comprises:
according to configuration information of the resource deployment file, pulling a container base mirror image from a mirror image warehouse to an edge IOT platform;
according to the configuration information of the resource deployment file, pulling a protocol adaptation packet from a file transfer protocol server to an edge IOT platform;
when the container is started, loading the protocol adaptation package which is mounted in the container to the program context, and after the container is started successfully, starting a Pod Watch thread to report the Pod state.
7. The method of claim 6, wherein starting a Pod Watch thread to report Pod status comprises:
receiving data reported by equipment by a container;
the container calls a protocol adaptation packet internal analysis transcoding program, and data reported by the equipment is converted into a format common to the IOT platform;
the side IOT platform checks the data after the container conversion;
and if the verification is passed, the converted data is sent to the cloud IOT platform.
8. An IOT platform protocol adaptation device based on cloud protogenesis, comprising:
the cloud IOT platform is used for issuing a product adaptation component which is assembled in advance according to needs to the edge IOT platform;
and the side IOT platform is used for verifying the product adaptation component issued by the cloud IOT platform, creating a resource deployment file and a service configuration file according to the product adaptation component if the verification is passed, and starting a container according to the resource deployment file and the service configuration file.
9. A cloud-native based IOT platform protocol adaptation device comprising a processor and a memory storing program instructions, the processor configured to, when executing the program instructions, perform the cloud-native based IOT platform protocol adaptation method of any of claims 1-7.
10. A computer readable medium having computer readable instructions stored thereon which are executed by a processor to implement a cloud-native based IOT platform protocol adaptation method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111674480.6A CN114422618B (en) | 2021-12-31 | 2021-12-31 | Cloud-protogenesis-based IOT platform protocol adaptation method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111674480.6A CN114422618B (en) | 2021-12-31 | 2021-12-31 | Cloud-protogenesis-based IOT platform protocol adaptation method, device, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114422618A true CN114422618A (en) | 2022-04-29 |
| CN114422618B CN114422618B (en) | 2024-01-02 |
Family
ID=81272066
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111674480.6A Active CN114422618B (en) | 2021-12-31 | 2021-12-31 | Cloud-protogenesis-based IOT platform protocol adaptation method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114422618B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115514611A (en) * | 2022-09-21 | 2022-12-23 | 杭州网易再顾科技有限公司 | Message processing method, device, equipment and storage medium |
| CN115643263A (en) * | 2022-12-08 | 2023-01-24 | 阿里巴巴（中国）有限公司 | Cloud native platform resource allocation method, storage medium and electronic device |
| CN117792913A (en) * | 2024-02-23 | 2024-03-29 | 北京天维信通科技股份有限公司 | Method for realizing ECR mirror image file adaptation to public cloud based on component package |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106603659A (en) * | 2016-12-13 | 2017-04-26 | 南京邮电大学 | Intelligent manufacturing special network data acquisition scheduling system |
| CN109327551A (en) * | 2018-12-04 | 2019-02-12 | 浩云科技股份有限公司 | By the method and device of internet of things equipment access platform of internet of things, server |
| CN110417766A (en) * | 2019-07-22 | 2019-11-05 | 深圳市酷达通讯有限公司 | A kind of method and apparatus of protocol analysis |
| CN111083168A (en) * | 2019-12-31 | 2020-04-28 | 广东嘉泰智能技术有限公司 | Configurable data transmission method and device of Internet of things platform gateway and gateway |
| CN111416821A (en) * | 2020-03-20 | 2020-07-14 | 杭州物源科技有限公司 | Internet of things equipment information acquisition method, system and device |
| CN111784076A (en) * | 2020-07-22 | 2020-10-16 | 济源国泰自动化信息技术有限公司 | Cloud metering system for industrial Internet and use method thereof |
| CN111970230A (en) * | 2020-06-24 | 2020-11-20 | 格创东智(深圳)科技有限公司 | Industrial field protocol automatic analysis method and system based on cloud identification |
| CN112379934A (en) * | 2019-07-29 | 2021-02-19 | 中移(苏州)软件技术有限公司 | Deployment method and device of cloud computing platform and storage medium |
| CN112422519A (en) * | 2020-10-27 | 2021-02-26 | 黑龙江省电工仪器仪表工程技术研究中心有限公司 | Electric power Internet of things IP fusion terminal and communication method thereof |
| CN112596740A (en) * | 2020-12-28 | 2021-04-02 | 北京千方科技股份有限公司 | Program deployment method and device |
| KR102248727B1 (en) * | 2019-12-13 | 2021-05-06 | 주식회사 두두원 | Multi-protocol iot gateway for energy management |
| KR102262321B1 (en) * | 2019-11-29 | 2021-06-08 | 주식회사 두두원 | IoT GATEWAY SYSTEM FOR INDUSTRIAL |
| CN112995348A (en) * | 2021-05-12 | 2021-06-18 | 北京金山云网络技术有限公司 | Control method, device and system of Internet of things equipment |
| CN113452743A (en) * | 2021-03-05 | 2021-09-28 | 浙江华云信息科技有限公司 | MQTT protocol and COAP protocol fusion algorithm |
-
2021
- 2021-12-31 CN CN202111674480.6A patent/CN114422618B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106603659A (en) * | 2016-12-13 | 2017-04-26 | 南京邮电大学 | Intelligent manufacturing special network data acquisition scheduling system |
| CN109327551A (en) * | 2018-12-04 | 2019-02-12 | 浩云科技股份有限公司 | By the method and device of internet of things equipment access platform of internet of things, server |
| CN110417766A (en) * | 2019-07-22 | 2019-11-05 | 深圳市酷达通讯有限公司 | A kind of method and apparatus of protocol analysis |
| CN112379934A (en) * | 2019-07-29 | 2021-02-19 | 中移(苏州)软件技术有限公司 | Deployment method and device of cloud computing platform and storage medium |
| KR102262321B1 (en) * | 2019-11-29 | 2021-06-08 | 주식회사 두두원 | IoT GATEWAY SYSTEM FOR INDUSTRIAL |
| KR102248727B1 (en) * | 2019-12-13 | 2021-05-06 | 주식회사 두두원 | Multi-protocol iot gateway for energy management |
| CN111083168A (en) * | 2019-12-31 | 2020-04-28 | 广东嘉泰智能技术有限公司 | Configurable data transmission method and device of Internet of things platform gateway and gateway |
| CN111416821A (en) * | 2020-03-20 | 2020-07-14 | 杭州物源科技有限公司 | Internet of things equipment information acquisition method, system and device |
| CN111970230A (en) * | 2020-06-24 | 2020-11-20 | 格创东智(深圳)科技有限公司 | Industrial field protocol automatic analysis method and system based on cloud identification |
| CN111784076A (en) * | 2020-07-22 | 2020-10-16 | 济源国泰自动化信息技术有限公司 | Cloud metering system for industrial Internet and use method thereof |
| CN112422519A (en) * | 2020-10-27 | 2021-02-26 | 黑龙江省电工仪器仪表工程技术研究中心有限公司 | Electric power Internet of things IP fusion terminal and communication method thereof |
| CN112596740A (en) * | 2020-12-28 | 2021-04-02 | 北京千方科技股份有限公司 | Program deployment method and device |
| CN113452743A (en) * | 2021-03-05 | 2021-09-28 | 浙江华云信息科技有限公司 | MQTT protocol and COAP protocol fusion algorithm |
| CN112995348A (en) * | 2021-05-12 | 2021-06-18 | 北京金山云网络技术有限公司 | Control method, device and system of Internet of things equipment |
Non-Patent Citations (2)
| Title |
|---|
| NANXI CHEN: "A Decentralized Adaptation System for QoS Optimization", 《WILEY TELECOM》 * |
| 田创: "物联网平台接入网关研究", 《信息技术》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115514611A (en) * | 2022-09-21 | 2022-12-23 | 杭州网易再顾科技有限公司 | Message processing method, device, equipment and storage medium |
| CN115514611B (en) * | 2022-09-21 | 2023-07-28 | 杭州网易再顾科技有限公司 | Message processing method, device, equipment and storage medium |
| CN115643263A (en) * | 2022-12-08 | 2023-01-24 | 阿里巴巴（中国）有限公司 | Cloud native platform resource allocation method, storage medium and electronic device |
| CN117792913A (en) * | 2024-02-23 | 2024-03-29 | 北京天维信通科技股份有限公司 | Method for realizing ECR mirror image file adaptation to public cloud based on component package |
| CN117792913B (en) * | 2024-02-23 | 2024-04-23 | 北京天维信通科技股份有限公司 | Method for realizing ECR mirror image file adaptation to public cloud based on component package |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114422618B (en) | 2024-01-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114422618B (en) | Cloud-protogenesis-based IOT platform protocol adaptation method, device, equipment and medium | |
| US20190347079A1 (en) | Software defined network controller | |
| US11550562B2 (en) | Virtualization platform for creating, deploying, modifying, and relocating applications | |
| US20150242200A1 (en) | Re-configuration in cloud computing environments | |
| CN106886434B (en) | Distributed application installation method and device | |
| US11461206B2 (en) | Cloud simulation and validation system | |
| US11665023B2 (en) | Configuration validation of a device | |
| EP2608585A1 (en) | Method, device and system for triggering terminal operation | |
| CN106844213A (en) | A kind of front end method of testing and device | |
| CN113687858B (en) | Configuration file checking method and device, electronic equipment and storage medium | |
| CN113141405B (en) | Service access method, middleware system, electronic device, and storage medium | |
| CN111596927A (en) | Service deployment method and device and electronic equipment | |
| CN112738181B (en) | Method, device and server for cluster external IP access | |
| CN107301053B (en) | Picture configuration method and device and electronic terminal | |
| US9665464B2 (en) | System and method for running a validation process for an information handling system during a factory process | |
| CN114095498B (en) | Cluster environment deployment method, system, computer equipment and storage medium | |
| CN109842498B (en) | Client configuration method, server, client and electronic equipment | |
| CN115758334A (en) | Cloud application access method and device, electronic equipment and storage medium | |
| CN113076128B (en) | Method, device, electronic equipment and storage medium for robot configuration | |
| CN114615285A (en) | Physical machine deployment method and device, electronic equipment and storage medium | |
| CN110971642B (en) | Data processing method and device for cloud computing platform | |
| CN112732332B (en) | Software package management method and device suitable for koji management system and electronic equipment | |
| CN111198721A (en) | Application program running method and device | |
| CN117560285B (en) | Intelligent control internet of things OTA upgrading method, client and server | |
| CN110401554B (en) | VNF (virtual network function) nanotube management method, device, system, 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 |