CN115185609A

CN115185609A - Loading system for accessing equipment based on java language

Info

Publication number: CN115185609A
Application number: CN202210875679.3A
Authority: CN
Inventors: 李业欣; 韩鹏; 陈波; 秦钢; 宋杨; 花京武
Original assignee: Hangzhou Diji Intelligent Technology Co ltd
Current assignee: Hangzhou Diji Intelligent Technology Co ltd
Priority date: 2022-07-25
Filing date: 2022-07-25
Publication date: 2022-10-14

Abstract

The application relates to a loading system for accessing equipment based on java language, which comprises: the main program is used for being responsible for starting, stopping and guarding the adapter process of the access module and maintaining the driving information; and the access module is used for accessing external equipment/service and establishing and maintaining information interaction between the external equipment/service and the main program. This application is for equipment access flexibility, and expansibility is strong, will insert main program and access module separation. The multi-process loading driver is used, isolation among the drivers is realized, one driver is broken down, and other drivers cannot be influenced, so that the phenomenon that the whole program is abnormal and the program is unavailable is avoided. When a new device is accessed, the new device can be adapted without whole program upgrading, only an access module is added, and the risk of program error is reduced.

Description

Loading system for equipment access based on java language

Technical Field

The present disclosure relates to the field of java technologies, and in particular, to a loading system, a method, and a loading control system for device access based on java language.

Background

The actual devices are various, and as the types of devices to be accessed become larger, the programs become bulkier. In the process of docking new equipment, the main program and the driver are integrated, and the technical problem that the whole program has the following problems possibly due to the bug existing in the newly added code is solved:

1. when a new device is accessed in a traditional access mode, the whole program needs to be upgraded to adapt to the new device, so that the risk is high;

2. after the new device is accessed, the whole program is abnormal due to the fact that the newly added part of the program is abnormal, and the computer program is likely to be crashed and flash back under the abnormal condition, so that the whole program is unavailable;

3. when a new docking device is added, the original program needs to be updated together, so that the access of the device is not flexible enough and cannot be expanded in time.

Disclosure of Invention

In order to solve the above problems, the present application provides a loading system, a method and a loading control system for accessing a device based on java language.

One aspect of the present application provides a loading system for accessing a device based on java language, including:

the main program is used for being responsible for starting, stopping and guarding the adapter process of the access module and maintaining the driving information;

at least one access module, which is used for accessing external equipment/service and establishing and maintaining information interaction between the external equipment/service and the main program;

the main program is electrically connected with the access module.

As an optional implementation of the present application, optionally, the access module includes:

the adapter process is used for carrying out information interaction with the main program and is responsible for loading a drive interface;

the driving interface is used as a port for establishing and maintaining information interaction between the external equipment/service and the main program by the access module;

the driving interface is loaded through the adapter process, and data interaction is carried out between the driving interface and the main program through the adapter process.

As an optional implementation of the present application, optionally, a driving control manner of the driving interface includes:

init () is initialized: establishing a connection with the external device/service;

device control access (): access and control the external devices/services;

initialize exit (): disconnecting the connection with the external device/service.

As an optional embodiment of the present application, optionally, a driving protocol of the driving interface is a Modbus protocol.

As an optional implementation of the present application, optionally, a driving protocol of the driving interface is an opuca protocol.

As an optional implementation of the present application, optionally, the driving protocol of the driving interface is a BACnetIP protocol.

In another aspect of the present application, a loading method for a loading system accessing to a device based on java language is provided, which includes the following steps:

establishing connection between the main program and the access module to complete drive initialization;

the main program sends a device driving command to the access module;

and the access module initiates access and control to external equipment/service according to the equipment driving command and returns the execution result of the external equipment/service to the main program.

As an optional embodiment of the present application, optionally, the establishing a connection between the main program and the access module, and completing the initialization of the driver includes:

creating an adapter process through a main program, and carrying an identifier of the adapter process in a starting command line;

the adapter process is started, the identifier is obtained from a starting command line, network connection interacting with the main program is established, and identifier information is sent to the main program;

the main program receives the identifier information and returns the path of the driving file to be loaded by the adapter process and the configuration information of the driving file to the adapter process according to the identifier information;

the adapter process receives the response and starts to load the specified drive file;

the adapter process acquires a drive control mode of initializing init () from a drive file, calls the drive control mode and transmits related configuration information;

after the initialization init () returns success, the adapter process sends a message to inform the main program, and the driver completes initialization.

As an optional implementation of the present application, optionally, the accessing module initiates access and control to an external device/service according to the device driver command, and returns an execution result of the external device/service to a main program, including:

and command execution flow: the adapter process of the access module receives a device execution command sent by the main program; the adapter process calls a drive control mode of the equipment control access () to execute the command; the adapter process returns the command execution result to the main program;

and (4) command exit flow: the adapter process of the access module receives an exit command sent by the main program; the adapter process calls a drive control mode of the reinitialization exit () to execute the command; the adapter process returns a result; the adapter process automatically terminates the process;

driving an abnormal crash flow: the adapter process of the access module is abnormally crashed to cause exit, and the main process receives an adapter process exit signal from an operating system; the host process again performs the "startup procedure".

In another aspect of the present application, a loading control system is further provided, including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to implement the loading method when executing the executable instructions.

The invention has the technical effects that:

the loading system of the present application includes: the main program is used for being responsible for starting, stopping and guarding the adapter process of the access module and maintaining the driving information; and the access module is used for accessing external equipment/service and establishing and maintaining information interaction between the external equipment/service and the main program. The method and the device have the advantages that for equipment access flexibility, expansibility is strong, and an access main program is separated from an access module. The multi-process loading driver is used, isolation among the drivers is realized, one driver is broken down, and other drivers cannot be influenced, so that the phenomenon that the whole program is abnormal and the program is unavailable is avoided. When a new device is accessed, the new device can be adapted without integral program upgrading, only an access module is added, and the risk of program errors is reduced.

Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a diagram illustrating the driving process architecture of the present invention;

fig. 2 is a schematic flow chart of an implementation of the loading method of the present invention.

Detailed Description

Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the subject matter of the present disclosure.

In the present embodiment, the following explanation of technical terms of the present application is first made:

java language: a computer language for program development;

and (4) process: the basic execution entity of the program does not influence other processes in the operating system after abnormal exit;

the main procedure is as follows: the system is used for managing the driver and configuration information thereof and managing the start-stop operation of the Adapter process;

adapter program: a program for loading the driver, which is written by using java language;

driving: the program written by using java language and capable of being dynamically loaded in runtime is similar to a plug-in, and is loaded by an Adapter program to realize function expansion, and the expression form of the program is a file with an expansion name of jar.

Example 1

This application is for equipment access flexibility, and expansibility is strong, will insert main program and access module separation. The multi-process loading driver is used, isolation among the drivers is realized, one driver breaks down, and other drivers cannot be influenced, so that the phenomenon that the whole program is abnormal and the program is unavailable is avoided. When a new device is accessed, the new device can be adapted without integral program upgrading, only an access module is added, and the risk of program errors is reduced.

As shown in fig. 1, in one aspect, the present application provides a loading system for accessing a device based on java language, including:

the main program is electrically connected with the access module.

In order to ensure the equipment access flexibility, the expansibility is strong, and the access main program is separated from the access module. The main program is responsible for managing an access module and configuration information, and the access module comprises an adapter program and a drive interface.

In the main program module, a main program process is configured: the device is responsible for starting, stopping and guarding the adapter process; basic information of the driver (driver file path, device connection information, etc.) is maintained.

In one embodiment, the main program module may access a plurality of access modules, and each access module may access a corresponding external device or service through the driver interface.

As an optional embodiment of the present application, optionally, the access module includes:

and the driving interface is loaded through the adapter process and performs data interaction with the main program through the adapter process.

As shown in fig. 1, the Adapter process is configured in the Adapter, and is mainly used for loading a driver and implementing information interaction with a main program process through the driver.

The driving interface is internally provided with a driving program, is a function extension package realized by using java language, and is compiled and packaged to obtain an extension name jar package. The method cannot be directly used as a process to run, and can be used after being loaded by an adapter program.

The driver process is responsible for establishing and maintaining information interactions with external systems or devices. The information of an external system or equipment accessed at the driving interface is loaded and data exchanged through the Adapter process, and the main program performs logic operation and information maintenance, so that the purpose of data interaction between the driving interface and the main program through the Adapter process is realized.

In this embodiment, the drive control method of the drive interface is provided with several written drive process modes.

device control access (): accessing and controlling the external device/service;

reinitializing exit (): disconnecting the connection with the external device/service.

When the driving code is written, the adapter program can be loaded only by realizing the three methods according to the convention. The driver code is compiled and is realized by adopting java language, so that the adapter process can conveniently acquire and call the code of the driver interface from the jar package. The driving interface mainly realizes equipment control through the following three coding programs:

command execution-initialize init (): establishing a connection with a remote device or service;

exit execution flow — device control access (): accessing and controlling a remote device or service;

drive crash-initialize exit (): the connection to the remote device or service is broken.

When the driving interface is configured specifically, the driving control program can be configured according to the project requirement. The specific programming scheme of each driver is not limited in this embodiment, as long as the scheme of each driver command program can be implemented by the program.

The type of the driving interface needs to be matched with the external device/service, and needs to be established under the condition of the same communication protocol. As shown in fig. 1, the present embodiment provides the following technical protocols:

The external device corresponding to the Modbus protocol is a Modbus device, which is a physical device following the Modbus protocol.

As an optional embodiment of the present application, optionally, a driving protocol of the driving interface is an opuua protocol.

The external device corresponding to the OPCUA protocol is an OPCUA service which is a service end following the OPCUA protocol, and the client can acquire data after being connected to the OPCUA service.

The external device corresponding to the BACnetIP protocol is a BACnetIP device, which is a physical device following the BACnetIP protocol.

Therefore, the isolation between the drivers is realized by using the multi-process loading driver, and the crash of the driver A does not influence the driver B. During specific implementation, the first party informs the second party that equipment needing new support is accessed, the second party can directly develop the original program, and after the development is completed, a complete program package is printed and is upgraded for the first party by field implementation. The equipment can be accessed flexibly and can be expanded. When the new device is connected with the module, only the access module is added, and the risk of program error is reduced

It should be noted that, although the above driving protocol is described by taking three protocols and corresponding external devices as examples, those skilled in the art will understand that the present disclosure should not be limited thereto. In fact, the user can set the driving protocol flexibly according to the actual application scenario, as long as the technical function of the present application can be realized according to the above technical method.

Example 2

In this embodiment, the control of the external device is performed by using the above-described separate loading system based on the implementation principle of embodiment 1.

As shown in fig. 2, in another aspect, the present application provides a loading method for a loading system accessing a device based on java language, including the following steps:

s1, establishing connection between a main program and an access module to complete drive initialization;

s2, the main program sends a device driving command to the access module;

and S3, the access module initiates access and control to the external equipment/service according to the equipment driving command, and returns the execution result of the external equipment/service to the main program.

And (3) information interaction flow:

firstly, communication connection is established, and the connection between a main program and external equipment/service is established by initializing a driver of init (), so that drive initialization is completed.

Secondly, according to the device control access () driver, starting to execute access, initiating access and controlling the external device/service, and returning the execution result.

And finally, when the program crash occurs, disconnecting the external equipment/service by the reinitializing exit () driver.

the main program receives the identifier information, and returns the path of the drive file to be loaded by the adapter process and the configuration information of the drive file to the adapter process according to the identifier information;

the adapter process acquires a drive control mode of the initialization init () from the drive file, calls the drive control mode and transmits related configuration information;

driving an abnormal crash flow: the adapter process of the access module is abnormally crashed to cause exit, and the main process receives an adapter process exit signal from an operating system; the host process again performs the "boot flow".

In specific implementation, the following process is referred to:

1. starting process

The main program creates an adapter process and carries an identifier of the adapter process in a starting command line;

after the adapter process is started, acquiring an identifier from a starting command line, establishing network connection interacting with a main program, and sending identifier information;

after receiving the information, the main program knows that the adapter process is started completely, and returns the path of the driver file to be loaded by the adapter process and other configuration information (usually equipment connection information) to the main program according to the identifier;

the adapter process starts to load the specified drive file after receiving the response (the loading mode is that a jar package loading technology provided by the java language can load the drive interface code realized in the jar package and realize the call);

the adapter process acquires an init () method of the driving interface from the jar packet, calls the init () method and transmits related configuration information;

after init () returns success, the adapter process sends a message to inform the main program, and the driver completes initialization.

2. Command execution flow

The main program sends a device control command to the adapter process;

the adapter process calls an access () method to execute a command;

the adapter process returns the command execution result.

3. Exit flow

The main program sends an exit command to the adapter process;

the adapter process calls the exit () method;

the adapter process returns a result;

the adapter process terminates the process itself.

4. Driving an exception crash flow

The adapter process is exited due to abnormal crash, and other adapter processes run normally;

the method comprises the steps that a main process receives an adapter process exit signal from an operating system;

the host process again performs the "boot flow".

1. The execution flows 2 and 3 are realized according to the set driving program of the driving interface, i.e. the driving control mode.

The execution flow of 4 is executed mainly according to an adapter process exit signal sent by the operating system, and may be sent by a process monitoring program (such as a process of a task manager) of the computer operating system according to the execution condition of the adapter process.

It should be apparent to those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, and the program may be stored in a computer readable storage medium, and when executed, may include the processes of the embodiments of the control methods as described above. The modules or steps of the invention described above can be implemented by a general purpose computing device, they can be centralized on a single computing device or distributed over a network of multiple computing devices, and they can alternatively be implemented by program code executable by a computing device, so that they can be stored in a storage device and executed by a computing device, or they can be separately fabricated into various integrated circuit modules, or multiple modules or steps thereof can be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, and the program may be stored in a computer readable storage medium, and when executed, may include the processes of the embodiments of the control methods as described above. The storage medium may be a magnetic disk, an optical disk, a Read-only memory (ROM), a Random Access Memory (RAM), a flash memory (FlashMemory), a hard disk (hard disk drive, abbreviated as HDD) or a Solid State Drive (SSD), etc.; the storage medium may also comprise a combination of memories of the kind described above.

Example 3

Still further, in another aspect of the present application, a load control system is further provided, including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to implement the loading method of embodiment 2 when executing the executable instructions.

Embodiments of the present disclosure provide a load control system including a processor and a memory for storing processor-executable instructions. Wherein the processor is configured to implement the loading method of embodiment 2 when executing the executable instructions.

Here, it should be noted that the number of processors may be one or more. Meanwhile, in the loading control system of the embodiment of the present disclosure, an input device and an output device may be further included. The processor, the memory, the input device, and the output device may be connected through a bus, or may be connected through another manner, which is not specifically limited herein.

The memory, which is a computer-readable storage medium, may be used to store software programs, computer-executable programs, and various modules, such as: the loading method of the embodiment of the disclosure corresponds to a program or a module. The processor executes various functional applications and data processing of the load control system by executing software programs or modules stored in the memory.

The input device may be used to receive an input number or signal. Wherein the signal may be a key signal generated in connection with user settings and function control of the device/terminal/server. The output means may comprise a display device such as a display screen.

Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A loading system for accessing equipment based on java language is characterized by comprising:

the main program is electrically connected with the access module.

2. The loading system for accessing to equipment based on java language as claimed in claim 1, wherein the access module comprises:

3. The loading system for accessing to equipment based on java language as claimed in claim 2, wherein the driving control mode of the driving interface comprises:

initializing init (): establishing a connection with the external device/service;

4. The loading system for accessing equipment based on java language as claimed in claim 1, wherein the driver protocol of the driver interface is Modbus protocol.

5. The loading system for device access based on java language as claimed in claim 1, wherein the driver protocol of the driver interface is OPCUA protocol.

6. The loading system for device access based on java language as claimed in claim 5, wherein the driver protocol of the driver interface is BACnetIP protocol.

7. A loading method of a loading system for accessing equipment based on java language as claimed in any one of claims 1-6, comprising the following steps:

the main program sends a device driving command to the access module;

and the access module initiates access and control to external equipment/service according to the equipment driving command, and returns an execution result of the external equipment/service to the main program.

8. The loading method according to claim 7, wherein establishing a connection between the main program and the access module, and completing initialization of the driver, comprises:

starting the adapter process, acquiring the identifier from a starting command line, establishing network connection interacting with the main program, and sending identifier information to the main program;

9. The loading method according to claim 8, wherein the accessing module initiates access and control to an external device/service according to the device driver command, and returns an execution result of the external device/service to the main program, and the method includes:

and a command execution flow: the adapter process of the access module receives a device execution command sent by the main program; the adapter process calls a drive control mode of the equipment control access () to execute the command; the adapter process returns the command execution result to the main program;

and (4) command exit flow: the adapter process of the access module receives an exit command sent by the main program; the adapter process calls a drive control mode of the reinitialization exit () to execute a command; the adapter process returns a result; the adapter process automatically terminates the process;

10. A load control system, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to implement the loading method of any of claims 7 to 9 when executing the executable instructions.