WO2017101247A1

WO2017101247A1 - Self-service equipment hardware management method and device

Info

Publication number: WO2017101247A1
Application number: PCT/CN2016/081805
Authority: WO
Inventors: 熊飞; 江清源; 吴胜楠; 黄三朋; 陈明宇; 李珂烨
Original assignee: 广州广电运通金融电子股份有限公司
Priority date: 2015-12-18
Filing date: 2016-05-12
Publication date: 2017-06-22
Also published as: CN105426253A

Abstract

An embodiment of the present invention discloses a method for self-service equipment hardware management for solving the inability of the prior art to allow two application programs to coexist further resulting in an inability to accomplish an application scenario requiring simultaneous completion of functions by two application programs. The method thereby alleviates the technical problem of poor control efficiency of equipment hardware control. The embodiment of the present invention comprises: when an application program is running, acquire an equipment and a port required for use by the application program; determine whether the equipment and the port exists, if so, then control the equipment on the basis of the application program and an existing instance, and if not, then make a further determination; the further determination determines whether the port required for use by the application program has been occupied, if so, then control the application program to reassign the port required for use, and if not, then establish a new instance on the basis of the equipment and the port required for use by the application program; and control the equipment on the basis of the application program and the new instance. The embodiment of the present invention also provides a self-service equipment hardware management device.

Description

Self-service device hardware management method and device

This application claims priority to Chinese Patent Application No. 201510967254.5, entitled "A Self-Service Hardware Management Method and Apparatus", filed on December 18, 2015, the entire contents of which are incorporated herein by reference. In the application.

Technical field

The present invention relates to the field of self-service device control technologies, and in particular, to a self-service device hardware management method and apparatus.

Background technique

The communication control of the self-service terminal device module is generally performed by serial port or USB. One module usually only performs connection control through one communication line, which causes the control of the device by different applications to be physically exclusive and exclusive access. In actual application scenarios, there are usually multiple applications that need to control the same module. For example, two applications need to control the movement, one of which is used to issue money and another application to obtain the movement. Device status, in order to meet the needs of this scenario, at present, the common practice at home and abroad is to develop a hardware device control DLL (dynamic link library) for a module, different applications respectively load different instances of the DLL to complete the exclusive use of the device Access control, when multiple applications are required to access the device, an application is required to complete control and then exit the occupation of the device link, and then another application obtains the occupation of the device link.

Such a process has the following problems: 1. Reduce the efficiency of the application to device control. Both applications need to continuously acquire and release links, consume link resources, and waste processing time. 2. The two applications cannot coexist at the same time, reducing the user's experience with the self-service terminal device.

Summary of the invention

The embodiment of the invention provides a self-service device hardware management method and device, which can solve the problem that the two technologies cannot coexist at the same time in the prior art, and the two application functions need to be completed at the same time. The application scenario cannot be implemented, and the technical problem of controlling the hardware control efficiency of the device is reduced.

A self-service device hardware management method provided by an embodiment of the present invention includes:

Get the device and port that the application needs to call when running the application;

Determining whether there is a device and a port that the existing instance calls the required call, and if so, controlling the device according to the application and the existing instance, if not, making further judgment;

The determining is further: determining whether the port required to be called by the application is occupied, and if so, controlling the application to re-allocate the port to be called, and if not, the device to be invoked according to the application And create a new instance of the port;

The device is controlled according to the application and the newly created instance.

Optionally, the reference count of the existing instance is incremented by 1 before the device is controlled according to the application and the existing instance;

The reference count of the newly created instance is incremented by 1 before the device is controlled according to the application and the newly created instance;

When the application exits controlling the device, the reference count of the corresponding instance is decremented by one;

When the instance's reference count is 0, the instance is deleted.

Optionally, after the new device is created according to the device and the port that is to be invoked by the application, the instance information of the newly created instance is saved in a preset device instance table, where the instance information includes the newly created instance. The device name of the calling device, the port number of the called port, the corresponding reference count, and the device status information of the called device.

Optionally, acquiring device state information of the device in real time, and updating the device state information to the device instance table;

When it is required to acquire device state information of the device controlled by the application, the device state information is obtained and returned from the device instance table.

Optionally, when the device is controlled according to the application, whether the device is in a normal state is determined according to the acquired device state information of the device, and if yes, the device is not initialized, and the device is directly controlled to work.

A self-service device hardware management device provided by the embodiment of the invention includes:

a first obtaining module, configured to acquire a device and a port that the application needs to call when the application is running;

An instance judgment module is configured to determine whether there is a device and a port that the existing instance calls the required call;

a first control module, configured to: when the judgment result of the existing instance judgment module is YES, control the device according to the application program and the existing instance;

a port occupancy judging module, configured to determine, when the judgment result of the existing instance judging module is negative, whether the port that the application program needs to be called is occupied;

a redistribution module, configured to: when the judgment result of the port occupation judging module is yes, control the application to reallocate a port to be called;

The new instance module is configured to: when the judgment result of the port occupation judgment module is negative, create an instance according to the device and port to be invoked by the application;

And a second control module, configured to control the device according to the application and the newly created instance.

Optionally, the device comprises:

a first reference counting module, configured to add a reference count of the existing instance by 1 before the first control module controls the device according to the application and the existing instance;

a second reference counting module, configured to add a reference count of the newly created instance by 1 before the second control module controls the device according to the application and the newly created instance;

a third reference counting module, configured to: when the application exits and control the device, the reference count of the corresponding instance is decreased by 1;

The instance delete module is configured to delete the instance when the reference count of the instance is 0.

Optionally, the device comprises:

An instance information saving module, configured to save the instance information of the newly created instance to a preset device instance table after the newly created instance module creates an instance according to the device and the port that is to be invoked by the application, the instance The information includes the device name of the device invoked by the newly created instance, the port number of the called port, the corresponding reference count, and the device status information of the called device.

Optionally, the device comprises:

a status information update module, configured to acquire device status information of the device in real time, and update the device status information to the device instance table;

The status information obtaining module is configured to acquire and return the device status information from the device instance table when the device status information of the device controlled by the application is required to be acquired.

Optionally, the device comprises:

a device status determining module, configured to determine, according to the acquired device state information of the device, whether the device is in a normal state when the first control module or the second control module controls the device according to the application program;

The direct control module is configured to: when the judgment result of the device state judging module is YES, perform an initialization operation of the device, and directly control the working of the device.

It can be seen from the above technical solutions that the embodiments of the present invention have the following advantages:

In the embodiment of the present invention, first, when the application is running, the device and the port that are required to be called by the application are acquired; then, it is determined whether there is an existing instance calling the device and the port that is required to be called, and if so, according to The application and the existing instance control device, if not, make further determination; then further determine whether the port that the application needs to call is occupied, and if so, control the application to reallocate the required call Port, if not, create an instance based on the device and port that the application needs to call; finally, control the device based on the application and the newly created instance. In the embodiment of the present invention, the hardware management method of the self-service device can solve the problem that the existing technology cannot realize the simultaneous coexistence of two applications, and the application scenario that needs to complete two application functions at the same time cannot be implemented, and the technology for reducing the hardware control efficiency of the device is reduced. problem.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are Some embodiments of the present invention may also be used to obtain other drawings based on these drawings without departing from the art.

1 is a flowchart of an embodiment of a self-service device hardware management method according to an embodiment of the present invention;

2 is a flowchart of another embodiment of a self-service device hardware management method according to an embodiment of the present invention;

3 is a structural diagram of an embodiment of a self-service device hardware management apparatus according to an embodiment of the present invention;

4 is a structural diagram of another embodiment of a self-service device hardware management apparatus according to an embodiment of the present invention; Figure.

detailed description

The embodiments of the present invention provide a self-service device hardware management method and device, which are used to solve the problem that the two technologies cannot coexist at the same time in the prior art, and the application scenario that needs to complete two application functions at the same time cannot be implemented, and the device hardware is reduced. Technical issues that control efficiency.

In order to make the object, the features and the advantages of the present invention more obvious and easy to understand, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. The described embodiments are only a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

Referring to FIG. 1, an embodiment of a self-service device hardware management method according to an embodiment of the present invention includes:

101. When running the application, obtain the device and port that the application needs to call;

First, when you run the application, you can get the devices and ports that the application needs to call.

102, judging whether there is an existing instance to call the device and port to be called, if yes, proceed to step 103, and if not, proceed to step 104;

After running the application, after obtaining the device and port that the application needs to call, it can be determined whether there is an existing instance calling the device and port that is required to be called. If yes, step 103 is performed, and if not, step 104 is performed. .

103. Control the device according to the application and the existing instance;

If it is determined that there is an existing instance calling the device and port to be called, the device is controlled according to the application and the existing instance.

104, determine whether the port required to be called by the application is occupied, and if so, step 105 is performed, and if not, step 106 is performed;

If it is determined that there is no device and port that the existing instance calls the required call, it is further determined whether the port that the application needs to call is occupied. If yes, step 105 is performed, and if no, step 106 is performed.

105. Control the application to reallocate the port to be called;

If it is further determined that the port that the application needs to call is occupied, then the application is controlled to reallocate the port to be called.

106. Create an instance according to the device and port that the application needs to call;

If it is further determined that the port that the application needs to call is not occupied, a new instance is created according to the device and port that the application needs to call.

107. Control the device according to the application and the newly created instance.

After you create a new instance of the device and port that you want to invoke based on the application, you can control the device based on the application and the newly created instance.

In this embodiment, first, when the application is running, the device and the port that the application needs to be called are acquired; then, it is determined whether there is an existing instance calling the device and port that is required to be called, and if so, according to the application And the existing instance control device, if not, make further judgment; then further determine whether the port that the application needs to call is occupied, and if so, control the application to re-allocate the port to be called, if not, then Create an instance based on the device and port that the application needs to call; finally, control the device based on the application and the newly created instance. In this embodiment, the hardware management method of the self-service device can solve the problem that the two technologies cannot coexist at the same time in the prior art, and the application scenario that needs to complete the two application functions at the same time cannot be implemented, and the technical problem of reducing the hardware control efficiency of the device is reduced. .

For ease of understanding, a self-service device hardware management method in the embodiment of the present invention is described in detail below. Referring to FIG. 2, another embodiment of the self-service device hardware management method in the embodiment of the present invention includes:

201. When running the application, obtain the device and port that the application needs to call;

First, when you run the application, get the device and port that the application needs to call. It can be understood that when the application needs to call the device hardware, it needs both the device to be called and the port corresponding to the device. In general, the port is assigned by the application itself. In this embodiment, the device name and port number of the device can be obtained to obtain the device and port that the application needs to invoke.

202. Determine whether an existing instance calls the device and port that are required to be called, and if yes, execute Step 203, if no, step 205 is performed;

After obtaining the device and port that the application needs to call, it can be determined whether there is an existing instance calling the device and port that is required to be called. If yes, step 203 is performed, and if not, step 205 is performed. It can be understood that the system may already be running another application or applications before running the application, so there are existing instances in the system that call certain devices and ports. When it is found that there is an existing instance calling the device and port of the required call, it indicates that the existing instance can be called by the application without wasting resources to re-establish a new instance.

203. The reference count of the existing instance is increased by one;

If it is determined that there is an existing instance calling the device and port of the required call, the reference count of the existing instance is incremented by one. It should be noted that each instance can contain the "reference count" attribute, and the "reference count" attribute indicates how many applications are currently called by the instance. For example, assuming that the reference count for instance A is 2, it means that instance A is currently being called by 2 applications.

204. Control the device according to the application and the existing instance;

After the reference count of the existing instance is incremented by one, the device can be controlled according to the application and the existing instance.

205, determine whether the port required to be called by the application is occupied, and if so, proceed to step 206, and if not, proceed to step 207;

If it is determined that there is no device and port that the existing instance calls the required call, it is further determined whether the port that the application needs to call is occupied. If yes, step 206 is performed, and if no, step 207 is performed. It can be understood that when there is no device and port that the existing instance calls the required call, it means that an instance needs to be created for the application, and if the port is occupied, the instance cannot be created according to the port, so Need to determine if the port that the application needs to call is occupied.

206. Control the application to reallocate the port to be called;

If it is determined that the port that the application needs to call is occupied, then the application is controlled to reallocate the port to be called.

It can be understood that if the reassigned port is not occupied, a new instance can be created; if the reassigned port is still occupied, it is re-allocated until the assigned port is not occupied, and then a new instance is created.

207. Create an instance according to the device and port that the application needs to invoke;

If it is determined that the port that the application needs to call is not occupied, an instance can be created according to the device and port that the application needs to call.

208. Save the instance information of the newly created instance to a preset device instance table.

After creating an instance of the device and the port to be invoked according to the application, the instance information of the newly created instance may be saved to a preset device instance table, where the instance information includes the device name of the device invoked by the newly created instance. The port number of the called port, the corresponding reference count, and the device status information of the called device. The table structure of the device instance table can be as follows:

Equipment name

Serial port ID

Instance

Application count

Device status information

It should be noted that the instance information of each instance is saved in the device instance table. To ensure the real-time validity of the device instance table, the device status information of the device can be obtained in real time, and the device status information is updated to the device instance. Table; when the device status information of the device controlled by the application needs to be obtained, the device status information is obtained and returned from the device instance table.

209. The reference count of the newly created instance is increased by one;

The reference count for this newly created instance is incremented by one before the device is controlled according to the application and the newly created instance.

210. Control the device according to the application and the newly created instance;

After you create a new instance, you can control the device based on the application and the newly created instance.

It should be noted that, when the device is controlled according to the application, in order to improve the efficiency of the operation, the device may be determined according to the obtained device state information of the device, and if so, the device is not initialized. Control the device to work. There is no need to initialize the device before each control device, which reduces the wear and tear of the device.

211. Determine whether the application exits and control the device. If yes, execute step 212. If not, the reference count of the corresponding instance remains unchanged.

After controlling the device according to the application and the newly created instance, it can be determined whether the application exits and controls the device, and if so, step 212 is performed, and if not, the reference count of the corresponding instance remains unchanged.

212, the reference count of the corresponding instance is decreased by 1;

If it is determined that the application exits the control of the device, the reference count of the corresponding instance is decremented by one.

213. When the reference count of the instance is 0, the instance is deleted.

When the instance's reference count is 0, the instance is deleted. It can be understood that when the reference count of the instance is 0, it indicates that the instance is not currently called by any application, so in order to save system resources, the instance can be deleted.

For ease of understanding, according to the embodiment described in FIG. 2, a self-service device hardware management method in the embodiment of the present invention is described in three practical application scenarios:

Scenario 1: Normal: Two applications control the same device through the same port.

1. The first application App1.exe calls the device manager DeviceServie.exe to specify the port (such as serial port COM2) to open the device. The device manager calls the hardware driver library DevDriver.dll to physically open the device port, and the device is successfully opened. The device port 2 is occupied, and the device manager saves the device connection instance information to the device instance table, and the reference count of the instance is +1. The table structure is as follows:

Equipment name

Serial port ID

Instance

Application count

Device status information

2. The first application calls the initialization command of the device manager, and the device manager calls the hardware driver library to physically initialize the device, and the action hardware is initialized successfully.

3. The second application App2.exe calls the same port specified by the device management (such as serial COM2) to open the same device. The device manager uses the device name + serial port number to find out whether the device connection instance exists in the device instance table. Exist, use an existing instance. If it does not exist, check whether it is the same port. If it is the same port, it will fail. App2.exe needs to reset the new serial port ID or device name and then re-execute step 3. If it is a different port, create a new device connection instance and follow the specified The device name + port opens the physical device. In this example, specify the same port with the same device name, use the existing instance, that is, share the same instance.

4. The second application invokes the device manager initialization (Init) command. Since the physical operation of the initialization command is time consuming, the device manager obtains the current state of the device. If it is in a normal state, the hardware device is not physically initialized. Return directly to success. In this way, the efficiency of command execution is improved, and the wear of the device is reduced.

5. For example, the first application calls the device manager's cash-out instruction, and the device manager calls the hardware dynamic library to issue the banknotes, and updates the device state information corresponding to the device instance in the device manager (as in step 1). Table Structure).

6. The second application invokes the acquisition status command of the device manager, and the device manager directly returns the status information of the device from the device instance table (ie, the memory data), without operating the hardware device, improving the efficiency of acquiring the device state information. . At the same time, in order to improve the timeliness of the device status information, a status query thread periodically acquires the hardware status of the device in the device manager, ensuring that the status in the device manager memory is real-time.

7. After the run is complete, the first application calls the device manager's command to shut down the device. The device manager logically decrements the reference count of the corresponding device connection instance by one until the reference count is 0 to physically disconnect the device through the hardware driver library.

8. After the run is complete, the second application invokes the device manager's command to shut down the device. The device manager logically decrements the reference count of the corresponding device connection instance by one until the reference count is 0 to physically disconnect the device through the hardware driver library.

Scenario 2: Two applications control different devices through the same port.

1. The first application App1.exe calls the device manager DeviceServie.exe to specify the port (such as serial port COM2) to open the device. The device manager calls the hardware driver library DevDriver.dll to physically open the device port, and the device port 2 is opened successfully. Occupied, the device manager saves the device connection instance information to the device instance table, and the reference count of the instance is +1.

3. The second application App2.exe calls the specified port of the device management (such as serial port COM2) to open another different device. The device manager uses the device name + serial port number to find out whether the device connection instance exists. If it exists, the current use Some examples. If it does not exist, check whether it is the same port. If it is the same port, it will fail. App2.exe needs to reset the new serial port ID or device name and then re-execute step 3. If it is a different port, create a new device connection instance and follow the specified The device name + port opens the physical device. In this example, specifying the same port but using a different device name fails to return to open the device.

Scenario 3: Two applications control different devices through different ports.

1. The first application App1.exe calls the device manager DeviceServie.exe to specify the port (such as serial port COM2) to open the device. The device manager calls the hardware driver library DevDriver.dll to physically open the device port, and the device is successfully opened. The device port 2 is occupied, and the device manager saves the device connection instance information to the device instance table, and the reference count of the instance is +1.

3. The second application App2.exe calls the specified port of the device management (such as serial port COM2) to open another different device. The device manager uses the device name + serial port number to find out whether the device connection instance exists. If it exists, the current use Some examples. If it does not exist, check whether it is the same port. If it is the same port, it will fail. If it is a different port, create a new device connection instance and open the physical device according to the specified device name + port. In this example, you specify a different device with a different device name and create a new device connection instance.

4. The second application invokes the initialization command of the device manager. Since the instance corresponding to the request in the device manager is the first initialization operation, the device manager invokes the initialization command of the hardware dynamic library to complete the initialization of the device. There are physical actions.

5. The first application calls the device manager's cash-out instruction, and the device manager calls the hardware dynamic library to issue the money to the device.

6. The second application invokes the device manager's get state command, and the device manager returns the state of the device in memory.

The above describes a hardware management method for the self-service device. A self-service device hardware management device is described in detail below. Referring to FIG. 3, an embodiment of the self-service device hardware management device in the embodiment of the present invention includes:

a first obtaining module 301, configured to acquire a required call of the application when the application is run Devices and ports;

The existing instance determining module 302 is configured to determine whether there is an existing instance calling the device and the port that is required to be called;

The first control module 303 is configured to: when the judgment result of the existing instance determination module 302 is YES, control the device according to the application program and the existing instance;

The port occupancy judging module 304 is configured to: when the judgment result of the existing instance judging module 302 is negative, determine whether the port that the application program needs to be called is occupied;

The redistribution module 305 is configured to, when the result of the determination by the port occupancy determining module 304 is YES, control the application to re-allocate the port to be called;

The new instance module 306 is configured to: when the judgment result of the port occupation determining module 304 is negative, create an instance according to the device and port that the application needs to invoke;

The second control module 307 is configured to control the device according to the application and the newly created instance.

In this embodiment, first, when the application is running, the first obtaining module 301 acquires the device and port that the application needs to call; then, the existing instance determining module 302 determines whether there is an existing instance calling the required call. The device and the port; when the judgment result of the existing instance judging module 302 is YES, the first control module 303 controls the device according to the application program and the existing instance; when the judgment result of the existing instance judging module 302 is no The port occupancy determining module 304 determines whether the port to be called by the application is occupied; then, when the result of the port occupancy determining module 304 is YES, the redistribution module 305 controls the application to reallocate the port to be called. When the judgment result of the port occupation judging module 304 is no, the new instance module 306 creates an instance according to the device and port that the application needs to call; finally, the second control module 307 according to the application and the newly created instance. controlling device. In this embodiment, the self-service device hardware management device can solve the technical problem that the existing technology cannot realize the simultaneous coexistence of two applications, and the application scenario that needs to complete two application functions at the same time cannot be implemented, and the control efficiency of the device hardware is reduced. .

For ease of understanding, a self-service device hardware management device in the embodiment of the present invention is described in detail below. Referring to FIG. 4, another embodiment of the self-service device hardware management device in the embodiment of the present invention includes:

a first obtaining module 401, configured to acquire a required call of the application when the application is run Devices and ports;

The existing instance determining module 402 is configured to determine whether there is an existing instance calling the device and the port that is required to be called;

The first control module 403 is configured to: when the judgment result of the existing instance determination module 402 is YES, control the device according to the application program and the existing instance;

The port occupancy judging module 404 is configured to determine, when the judgment result of the existing instance judging module 402 is negative, whether the port to be called by the application program is occupied;

The redistribution module 405 is configured to, when the result of the determination by the port occupancy determining module 404 is YES, control the application to reallocate the port to be called;

The new instance module 406 is configured to: when the judgment result of the port occupation determining module 404 is negative, create an instance according to the device and port that the application needs to invoke;

The second control module 407 is configured to control the device according to the application and the newly created instance.

The device in this embodiment may include:

The first reference counting module 408 is configured to: before the first control module 403 controls the device according to the application and the existing instance, the reference count of the existing instance is incremented by one;

a second reference counting module 409, configured to add a reference count of the newly created instance by 1 before the second control module 407 controls the device according to the application and the newly created instance;

The third reference counting module 410 is configured to: when the application exits and control the device, the reference count of the corresponding instance is decreased by 1;

The instance deletion module 411 is configured to delete the instance when the reference count of the instance is 0.

The device in this embodiment may include:

The instance information saving module 412 is configured to save the instance information of the newly created instance to a preset device instance table after the new instance module 406 creates an instance according to the device and the port that the application needs to invoke, and the instance information is The device name of the device called by the newly created instance, the port number of the called port, the corresponding reference count, and the device status information of the called device.

The device in this embodiment may include:

The status information update module 413 is configured to acquire device status information of the device in real time, and update the device status information to the device instance table.

a status information obtaining module 414, configured to acquire a device of the device controlled by the application When the status information is obtained, the device status information is obtained and returned from the device instance table.

The device in this embodiment may include:

The device status determining module 415 is configured to determine, according to the acquired device state information of the device, whether the device is in a normal state when the first control module 403 or the second control module 407 controls the device according to the application program;

The direct control module 416 is configured to: when the determination result of the device status determination module 415 is YES, the initialization operation of the device is not performed, and the device is directly controlled to work.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a software product. The storage medium includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the embodiments are modified, or the equivalents of the technical features are replaced by the equivalents of the technical solutions of the embodiments of the present invention.

Claims

A self-service device hardware management method, comprising:

Get the device and port that the application needs to call when running the application;

Determining whether there is a device and a port that the existing instance calls the required call, and if so, controlling the device according to the application and the existing instance, if not, making further judgment;

The determining is further: determining whether the port required to be called by the application is occupied, and if so, controlling the application to re-allocate the port to be called, and if not, the device to be invoked according to the application And create a new instance of the port;

The device is controlled according to the application and the newly created instance.
The method according to claim 1, wherein the reference count of the existing instance is incremented by one before the device is controlled according to the application and the existing instance;

The reference count of the newly created instance is incremented by 1 before the device is controlled according to the application and the newly created instance;

When the application exits controlling the device, the reference count of the corresponding instance is decremented by one;

When the instance's reference count is 0, the instance is deleted.
The method of claim 1, wherein the instance information of the newly created instance is saved to a preset device instance table after the new device is created according to the device and the port that is called by the application, The instance information includes a device name of the device invoked by the newly created instance, a port number of the called port, a corresponding reference count, and device state information of the called device.
The method according to claim 3, wherein the device status information of the device is acquired in real time, and the device status information is updated to the device instance table;

When it is required to acquire device state information of the device controlled by the application, the device state information is obtained and returned from the device instance table.
The method according to claim 4, wherein when the device is controlled according to the application, it is determined whether the device is in a normal state according to the acquired device state information of the device, and if so, the device is not initialized. Directly control the operation of the device.
A self-service device hardware management device, comprising:

a first obtaining module, configured to acquire a device and a port that the application needs to call when the application is running;

An instance judgment module is configured to determine whether there is a device and a port that the existing instance calls the required call;

a first control module, configured to: when the judgment result of the existing instance judgment module is YES, control the device according to the application program and the existing instance;

a port occupancy judging module, configured to determine, when the judgment result of the existing instance judging module is negative, whether the port that the application program needs to be called is occupied;

a redistribution module, configured to: when the judgment result of the port occupation judging module is yes, control the application to reallocate a port to be called;

The new instance module is configured to: when the judgment result of the port occupation judgment module is negative, create an instance according to the device and port to be invoked by the application;

And a second control module, configured to control the device according to the application and the newly created instance.
The device of claim 6 wherein said device comprises:

a first reference counting module, configured to add a reference count of the existing instance by 1 before the first control module controls the device according to the application and the existing instance;

a second reference counting module, configured to add a reference count of the newly created instance by 1 before the second control module controls the device according to the application and the newly created instance;

a third reference counting module, configured to: when the application exits and control the device, the reference count of the corresponding instance is decreased by 1;

The instance delete module is configured to delete the instance when the reference count of the instance is 0.
The device of claim 6 wherein said device comprises:

An instance information saving module, configured to save the instance information of the newly created instance to a preset device instance table after the newly created instance module creates an instance according to the device and the port that is to be invoked by the application, the instance The information includes the device name of the device invoked by the newly created instance, the port number of the called port, the corresponding reference count, and the device status information of the called device.
The device of claim 8 wherein said device comprises:

a status information update module, configured to acquire device status information of the device in real time, and update the device status information to the device instance table;

The status information obtaining module is configured to acquire and return the device status information from the device instance table when the device status information of the device controlled by the application is required to be acquired.
The device of claim 9 wherein said device comprises:

a device status determining module, configured to determine, according to the acquired device state information of the device, whether the device is in a normal state when the first control module or the second control module controls the device according to the application program;

The direct control module is configured to: when the judgment result of the device state judging module is YES, perform an initialization operation of the device, and directly control the working of the device.