Device Access Method in the Internet of Things Scenario Based on Container and Multi-Process Technologies

Abstract

The present invention discloses a device access method in the Internet of Things scenario based on container and multi-process technologies, which includes the following steps: Step 1, determine the device type and scenario requirements; Step 2, determine whether there is an access program. If there is no access program, package and make the access program, then upload and configure it to the host device and end. If there is an access program, proceed to the next step; Step 3, determine whether the access program needs to be modified. If it does not need to be modified, directly upload and configure it to the host device and end. The device access method in the Internet of Things scenario based on container and multi-process technologies of the present invention supports generalized devices including third-party platforms, virtual devices, and third-party subsystems, etc. to be embedded in the host service and run stably in a flexible access manner.

Description

Technical Field

[0001] The present invention relates to a device access method, and more particularly to a device access method in the Internet of Things scenario based on container and multi-process technologies. Background Art

[0002] In the Internet of Things device access scenario, in the face of the access of diverse devices and third-party platform systems in multiple fields and scenarios, each type needs to be developed and deeply integrated according to the actual situation. Moreover, the professional knowledge required for the access of each type of device is different. The established access method requires each access person to learn it once. And for a project that requires cooperation, the programming language mastered by the developer determines the relevant technology selection, specific implementation plan, and maintenance plan. For example, person A masters language A and person B masters language B. At this time, if a project is written in language A, then person A can participate in the R & D, while person B cannot. Moreover, in the Internet of Things scenario, there are many types and a large number of devices. When using the Java programming language, more virtual machine resources are occupied. On a gateway device with 512M of memory, the number of access programs is limited, and the number of access points is also limited. Resources cannot be utilized maximally, and at the same time, the execution efficiency is worse than that implemented in the C language, and the requirements for high real-time performance are difficult to meet.

[0003] At the same time, for a device, the technical standard used by the access program is time-limited. When a better programming language or a higher-order function of a unified language emerges, the old access program can only run normally in the previous environment. However, the devices with the old access program still exist and are in use, and for various reasons, they cannot be rewritten, and it is also very difficult to directly use the new language in the previous project.

[0004] Therefore, the current existing technology only provides a specification for interacting with the host service. During the project R & D process, it cannot directly report or receive according to the attributes of the developer and the current device. This requires the developer to develop strictly in accordance with the interaction specification to run normally.

[0005] Moreover, the existing technology adopts an execution method in which containers and multi-processes coexist. In the case of multiple device access programs, the management difficulty will increase. When the corresponding relationship between the access program and the container and the communication interaction strategy are not perfect, resource waste and performance impact will occur. Summary of the Invention

[0006] Aiming at the deficiencies of the prior art, the purpose of the present invention is to embed device access programs implemented in multiple programming languages into a set of standard life cycle management systems based on container and multi - process technologies, allowing direct development in multiple programming languages in the same project. For example, if there is a stable running access program, it can be directly embedded and used without the cost of compatible programming languages. It enables people with different programming language skills to conveniently participate in the same project. At the same time, it provides friendly support for the language selection of device access under different scenario requirements, that is, when developing in multiple languages, the complete ecosystem of the language can be brought in, thereby further improving the R & D efficiency of the device access method.

[0007] To achieve the above - mentioned purpose, the present invention provides the following technical solutions: A device access method in the Internet of Things scenario based on container and multi - process technologies, including the following steps:

[0008] Step 1, determine the device type and scenario requirements;

[0009] Step 2, determine whether there is an access program. If there is no access program, then make and package the access program, upload and configure it to the host device, and then end. If there is an access program, proceed to the next step;

[0010] Step 3, determine whether the access program needs to be modified. If it does not need to be modified, directly upload and configure it to the host device and then end.

[0011] As a further improvement of the present invention, the specific steps of making and packaging the access program in Step 2 are as follows: Step 2 - 1, first select the corresponding programming language and dependent packages according to the actual needs of the scenario;

[0012] Step 2 - 2, secondly, correspond to the attributes, events, and services of the physical model according to the access device type;

[0013] Step 2 - 3, here, implement the access main body logic with reference to the interaction protocol and business requirements;

[0014] Step 2 - 4, finally, package and upload the program in the host service, and fill in the relevant configuration items and parameters on the access program management page.

[0015] As a further improvement of the present invention, when it is determined in Step 3 that the access program needs to be modified, in the existing program project, according to the actual device type parameters, return to Step 2 to make and package the access program.

[0016] As a further improvement of the present invention, the specific steps of uploading and configuring to the host device in Step 3 are as follows:

[0017] Step 3.1: After the access program is uploaded to the host device, confirm the access program configuration, confirm the specific deployment form, determine whether the deployment form is a container or a process. If it is determined that the deployment form is a process, create a process, start the process, and communicate with other services in the host service. If it is determined that the deployment form is a container, continue to the next step;

[0018] Step 3.2: After creating the container, start the container and communicate with other services in the host service.

[0019] As a further improvement of the present invention, the system architecture of the execution method is as follows:

[0020] Interaction management layer: Used to provide the capabilities of physical model configuration, program lifecycle management, and registration management of all programs;

[0021] Access layer: Used to provide the ability to embed the main service of the device access program to operate and interact properly based on the basic functions of lifecycle management and appropriate deployment strategies;

[0022] Core layer: Used to provide the interaction specifications of devices, points, applications, and their mutual communication in the overall solution; Device layer: Used to provide the scalability for unified access of multi-scenario and multi-type devices, third-party platforms, third-party subsystems, and virtual devices.

[0023] As a further improvement of the present invention, the interaction management layer includes:

[0024] Physical configuration module: Used to provide the physical model;

[0025] Program lifecycle management module: Used to perform program lifecycle management;

[0026] Registration management center module: Used to manage the registration of all programs.

[0027] As a further improvement of the present invention, the access layer is composed of several containers and several processes.

[0028] As a further improvement of the present invention, the core layer includes:

[0029] Point model module: Used to provide the point model;

[0030] Interaction protocol module: Used to provide the interaction protocol;

[0031] Device model module: Used to provide the device model;

[0032] Application model module: Used to provide the application model.

[0033] As a further improvement of the present invention, the device layer is composed of sensors, RFID, biometrics, MCU, a third-party platform, virtual devices, and third-party subsystems.

[0034] Advantages of the present invention: The present invention realizes embedding device access programs implemented in multiple programming languages into a standard life cycle management system based on container and multi-process technologies, allowing development directly in multiple programming languages in the same project. For example, if there is a stable running access program, it can be directly embedded and used without the cost of compatible programming languages. It enables personnel with different programming language skills to conveniently participate in the same project. At the same time, it provides friendly support for language selection for device access under different scenario requirements, that is, when developing in multiple languages, the complete ecosystem of the language can be brought in, thereby further improving the R & D efficiency. Description of the Drawings

[0035] Figure 1 It is a flowchart of the device access method in the Internet of Things scenario based on container and multi-process technologies of the present invention;

[0036] Figure 2 is Figure 1 a flowchart of uploading and configuring to the host device in

[0037] Figure 3 It is a block diagram of the module of the application and the system architecture of the method of the present invention. Detailed Embodiments

[0038] The present invention will be further described in detail below with reference to the embodiments given in the drawings.

[0039] Refer to Figure 1 As shown, a device access method in the Internet of Things scenario based on container and multi-process technologies in this embodiment includes the following steps:

[0040] Step 1, determine the device type and scenario requirements;

[0041] Step 2, determine whether there is an access program. If there is no access program, then make and package the access program, upload and configure it to the host device, and then end. If there is an access program, proceed to the next step;

[0042] Step 3: Determine whether the access program needs to be modified. If no modification is required, directly upload and configure it to the host device and then end. During the process of using the access method of this embodiment, only need to sequentially execute Step 1 to Step 3, and the device access can be effectively realized. In this way, this embodiment realizes embedding device access programs implemented in multiple programming languages into a standard lifecycle management system based on container and multi-process technologies, allowing development in multiple programming languages directly in the same project. For example, if there is a stable running access program, it can be directly embedded for use without the cost of compatible programming languages. It enables personnel with different programming language skills to conveniently participate in the same project. At the same time, it provides friendly support for the language selection of device access under different scenario requirements, that is, when developing in multiple languages, the complete ecosystem of the language can be brought in, thereby further improving the R & D efficiency.

[0043] As a specific implementation of the improvement, the specific steps of making and packaging the access program in Step 2 are as follows:

[0044] Step 2-1: First, select the corresponding programming language and dependent packages according to the actual needs of the scenario;

[0045] Step 2-2: Secondly, abstract the attributes, events, and services of the counterpart model according to the access device type;

[0046] Step 2-3: Here, refer to the interaction protocol and business requirements to implement the access main body logic;

[0047] Step 2-4: Finally, package and upload the program in the host service, and fill in the relevant configuration items and parameters on the access program management page. When it is determined in Step 3 that the access program needs to be modified, in the existing program project, according to the actual device type parameters, return to Step 2 to make and package the access program. In the access process of the device in this embodiment, first judge the situation of the access program, specifically:

[0048] No access program situation: First, select the corresponding programming language and dependent packages according to the actual needs of the scenario; secondly, abstract the attributes, events, and services of the counterpart model according to the access device type; thirdly, refer to the interaction protocol and business requirements to implement the access main body logic; finally, package and upload the program in the host service (the whole set of access solutions deployed on a certain device), and fill in the relevant configuration items and parameters on the access program management page;

[0049] Existing access program, no modification required situation: Directly upload the program to the host device and fill in the relevant configuration items and parameters on the access program management page;

[0050] There is an existing access program, and the situation that needs to be modified: In the existing program project, according to the actual device type, refer to Step 2 to perform the corresponding required steps. In this way, during the access process for the existing access program, the corresponding access process can be simplified, and resource waste and performance impact can be reduced.

[0051] As a specific implementation of the improvement, refer to Figure 2 As shown, the specific steps for uploading and configuring to the host device in Step 3 are as follows:

[0052] Step 3-1: After the access program is uploaded to the host device, confirm the configuration of the access program, confirm the specific deployment form, and determine whether the deployment form is a container or a process. If it is determined that the deployment form is a process, then create a process, start the process, and communicate with other services in the host service. If it is determined that the deployment form is a container, continue to the next step;

[0053] Step 3-2: After creating the container, start the container and communicate with other services in the host service. This embodiment can conveniently and friendly support the embedding and running of access programs for all types of devices in the host service. Its basic working process is that the host service, according to the configuration options of the access program and combined with the existing deployment strategy, deploys the access program on the host device (the device where the host service is deployed) in an appropriate form, and the container or process carrying the access program executes the specific code and communicates the execution result with other services in the host service. As a specific implementation of the improvement, refer to Figure 3 As shown, the system architecture of the execution method is as follows: Interaction management layer: used to provide the capabilities of physical model configuration, program life cycle management, and registration management of all programs;

[0054] Access layer: used to provide the ability to embed the main service of the device access program and run it interactively based on the basic functions of life cycle management and appropriate deployment strategies;

[0055] Core layer: used to provide the interaction specifications for devices, points, applications, and their mutual communication in the overall solution; Device layer: used to provide the scalability for unified access to multi-scenario and multi-type devices, third-party platforms, third-party subsystems, and virtual devices. Through the setting of the above four layers, an effective system architecture for executing the method of the above embodiment can be provided, and the capabilities required for the complete execution method process can be provided.

[0056] As a specific implementation of the improvement, the interaction management layer includes:

[0057] Physical configuration module, used to provide the physical model;

[0058] Program life cycle management module, used to perform program life cycle management;

[0059] The registration management center module is used to manage the registration of all programs. Through the settings of the above several modules, the effect of interactive management can be effectively achieved.

[0060] As a specific implementation of the improvement, the access layer is composed of several containers and several processes. Through the method of several containers and several processes, the ability to reasonably and appropriately embed the device access program into the main service for normal operation and interaction based on the basic functions of lifecycle management and appropriate deployment strategies can be effectively achieved.

[0061] As a specific implementation of the improvement, the core layer includes:

[0062] The point model module is used to provide the point model;

[0063] The interaction protocol module is used to provide the interaction protocol;

[0064] The device model module is used to provide the device model;

[0065] The application model module is used to provide the application model. Through the settings of the above modules, the core functional modules such as the interaction specifications of devices, points, applications and their mutual communication in the overall solution can be effectively provided, which is convenient for relevant developers to directly call, focus on the device access business, and at the same time enhance the extended abstraction ability of device access.

[0066] As a specific implementation of the improvement, the device layer is composed of sensors, RFID, biometrics, MCU, third-party platforms, virtual devices and third-party subsystems, thus providing the scalability for unified access to multi-scenario and multi-type devices, third-party platforms, third-party subsystems and virtual devices, etc.

[0067] In summary, the method of this embodiment realizes embedding the device access programs implemented in multiple programming languages into a standard lifecycle management system based on container and multi-process technologies, allows development directly in multiple programming languages in the same project. For example, if there is a stable running access program, it can be directly embedded for use without the cost of compatible programming languages. It enables personnel with different programming language skills to conveniently participate in the same project. At the same time, it provides friendly support for the language selection of device access under different scenario requirements, that is, when developing in multiple languages, the complete ecosystem of the language can be brought in, thereby further improving the R & D efficiency.

[0068] The above are only the preferred embodiments of the present invention. The protection scope of the present invention is not limited to the above embodiments. All technical solutions falling within the concept of the present invention belong to the protection scope of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and refinements should also be regarded as within the protection scope of the present invention.

Claims

1. A device access method in the Internet of Things scenario based on container and multi - process technologies, characterized in that, The system architecture for implementing the access method has an access layer: which is used to provide the ability to enable the embedded main service of the device access program to run and interact properly based on the basic functions of life cycle management and appropriate deployment strategies; the access layer is composed of several containers and several processes; the following steps are included: Step 1, determine the device type and scenario requirements; Step 2, check if there is an access program. If there is no access program, then create, package, upload, and configure the access program to the host device and then end. The specific steps for creating and packaging the access program are as follows: Step 2-1, first select the corresponding programming language and dependency packages according to the actual needs of the scenario; Step 2-2, secondly, according to the attributes, events, and services of the object model corresponding to the access device type; Step 2-3, in this step, implement the access main logic with reference to the interaction protocol and business requirements; Step 2-4, finally, package the program and upload it to the host service, and fill in the relevant configuration items and parameters on the access program management page. If there is an access program, proceed to the next step; Step 3, check if the access program needs to be modified: If no modification is needed, directly upload and configure it to the host device and then end. The specific steps for uploading and configuring to the host device are as follows: Step 3-1, after the access program is uploaded to the host device, confirm the configuration of the access program, confirm the specific deployment form, and determine whether the deployment form is a container or a process. If it is determined that the deployment form is a process, then create a process, start the process, and communicate and interact with other services in the host service. If it is determined that the deployment form is a container, continue to the next step; Step 3-2, create a container, start the container, and communicate and interact with other services in the host service; When modification is needed, in the existing program project, modify according to the actual device type parameters and then return to Step 2 to create and package the access program.

2. The device access method in the Internet of Things scenario based on container and multi-process technology according to claim 1, characterized in that: The system architecture for implementing the access method also has the following: Interaction management layer: which is used to provide the ability of object model configuration, program life cycle management, and registration management of all programs; Core layer: which is used to provide the interaction specifications of devices, points, applications, and their mutual communication in the overall solution; Device layer: which is used to provide the scalability for unified access of multi-scenario and multi-type devices, third-party platforms, third-party subsystems, and virtual devices.

3. The device access method in the Internet of Things scenario based on container and multi-process technologies according to claim 2, characterized in that: The interaction management layer includes: Physical configuration module, which is used to provide the object model; Program life cycle management module, which is used to perform program life cycle management; Registration management center module, which is used to manage the registration of all programs.

4. The device access method in the Internet of Things scenario based on container and multi-process technologies according to claim 3, wherein: The core layer includes: Point model module, which is used to provide the point model; Interaction protocol module, which is used to provide the interaction protocol; Device model module, which is used to provide the device model; Application model module, which is used to provide the application model.

5. The device access method in the Internet of Things scenario based on container and multi-process technology according to claim 4, characterized in that: The device layer is composed of sensors, RFID, biometrics, MCUs, third-party platforms, virtual devices, and third-party subsystems.

Images