WO2018205267A1

WO2018205267A1 - Input device implementation method and implementation apparatus thereof

Info

Publication number: WO2018205267A1
Application number: PCT/CN2017/084182
Authority: WO
Inventors: 李岩刚
Original assignee: 深圳前海达闼云端智能科技有限公司
Priority date: 2017-05-12
Filing date: 2017-05-12
Publication date: 2018-11-15
Also published as: CN107278294A; CN107278294B

Abstract

An input device implementation method and an implementation apparatus thereof, wherein same are applied in a virtual machine system. The virtual machine system comprises a main operating system (200) and a plurality of guest operating systems (300), wherein the main operating system (200) comprises a physical input device drive unit (210) for communicating with a physical input device; and the guest operating system (300) comprises a guest input device drive unit (310) for communicating with a virtual input device and an input device service unit (320) for providing an input device application. The method comprises: obtaining device data of the physical input device by means of the physical input device drive unit (210), wherein the device data at least comprises an input event; and transmitting the input event to the input device service unit (320) via a dedicated transmission channel, wherein the dedicated transmission channel does not pass through the guest input device drive unit (310).

Description

Input device implementation method and implementation device thereof

Technical field

The present application relates to the field of virtual machine technologies, and in particular, to an input device implementation method and an implementation device thereof.

Background technique

A virtual machine is a computer system that is simulated by software and has a complete hardware system function and runs in a completely isolated environment. In a virtual machine application environment, multiple different operating systems are based on analog hardware, sharing physical hardware devices such as CPUs, memory, and input and output devices.

Generally, a physically existing computer can be referred to as a "host" (HOST), an operating system running on a host can be referred to as a host operating system (HOST OS), and other operating systems can be referred to as a guest operating system (GUEST). OS).

The virtual machine can run as one of the applications within the primary operating system, providing an analog hardware device for use by the guest operating system. For example, the "goldfish" virtual hardware platform provided by Google in the prior art can support the virtual Android operating system supported by the QEMU virtual machine.

In order to implement an input device in a virtual machine, a backend program capable of supporting the operation of the sensor device is usually implemented in the virtual machine in the prior art. The backend program can provide the client operating system with input device related data that needs to be configured, such as input device configuration information, attributes, and input device data. The operation of the input device is implemented by the corresponding input device driver and the input device service program in the guest operating system on the basis of the virtual input device provided by the backend program.

In the process of researching the prior art, the applicant finds that in the implementation process of the existing input device, the input device related data of the virtual input device provided by the backend program passes the input device driver and input in the kernel of the guest operating system. The device's common layer is processed. But since the input data has been processed by the main operating system, the input device in the guest operating system drives The application program and the input device common layer can be directly applied to the service layer for some of the data without processing. Therefore, the input device driver in the guest operating system and the input device common layer have repeated processing on the input device data, which reduces the efficiency of data processing.

Summary of the invention

The embodiment of the present application mainly solves the problem that the input device is repeatedly processed when the input device is implemented in the related art.

To solve the above technical problem, a technical solution adopted by the embodiment of the present application is to provide an input device implementation method, which is applied to a virtual machine system, where the virtual machine system includes a main operating system and a plurality of guest operating systems, The primary operating system includes a physical input device drive unit for communicating with the physical input device; the guest operating system includes a client input device drive unit for communicating with the virtual input device and an input device service unit for providing an input device application. The method includes: acquiring, by the physical input device driving unit, device data of a physical input device, where the device data includes at least an input event; and transmitting the input event to the input device service unit through a dedicated transmission channel; The dedicated transmission channel does not pass through the customer input device drive unit.

In order to solve the above technical problem, another technical solution adopted by the embodiment of the present application is to provide an input device implementation device, which is applied in a virtual machine system, where the virtual machine system includes a main operating system and a plurality of guest operating systems. The main operating system includes a physical input device drive unit for communicating with a physical input device; the guest operating system includes a client input device drive unit for communicating with the virtual input device and an input device service unit for providing an input device application . The device includes: an input device back end support unit, configured to acquire device data of the physical input device by the physical input device driving unit, the device data includes at least an input event; and a dedicated transmission channel, configured to input the event Transmitting to the input device service unit; the dedicated transmission channel does not pass through the client input device drive unit.

The input device implementation method and the implementation device thereof provided by the embodiments of the present application directly transmit an input event to an input device service unit of a guest operating system through a specific dedicated transmission channel, and do not need to pass through a client input device driving unit, thereby avoiding a guest operating system. Guest The repeated processing of the input event by the input device driving unit effectively improves the data processing efficiency in the implementation process of the input device.

DRAWINGS

The one or more embodiments are exemplified by the accompanying drawings in the accompanying drawings, and FIG. The figures in the drawings do not constitute a scale limitation unless otherwise stated.

1 is a schematic diagram of a virtual machine system provided by an embodiment of the present application;

2 is a schematic diagram of an implementation of an input device implementation apparatus provided in an embodiment of the present application on a virtual machine system;

3 is a schematic diagram of input event transmission of a dedicated transmission channel provided by an embodiment of the present application;

4 is a schematic diagram of data interaction between a virtual machine program and a guest operating system provided by an embodiment of the present application;

FIG. 5 is a flowchart of a method for implementing an input device according to an embodiment of the present disclosure;

6 is a flowchart of a method for starting a dedicated transmission channel according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

detailed description

In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

An input device driver refers to a driver or a corresponding function module for an input device. It can serve as a bridge between the input device hardware and the upper operating system, and implements the high-level programming language used in the operating system and the electronic signals of the hardware devices used by the input device.

Thus, in a virtual machine system having a plurality of different operating systems, the host operating system has an input device driver corresponding to the physical input device. Each client operating system also has an input device driver corresponding to the virtual input device for implementing a communication connection between the input device and the operating system.

FIG. 1 is a virtual machine system to which an input device implementation method provided by an embodiment of the present application is applied. As shown in FIG. 1, the virtual machine system includes: a physical hardware device 100, a main operating system 200, a plurality of guest operating systems 300, and a virtual machine program 400.

The physical hardware device 100 is a hardware device shared by the host operating system 200 and the guest operating system 300. It can include any suitable one or more device components that make up a complete computer system, including processor 101, storage medium 102, input/output device 103, sensor device 104, and communication module 105.

The processor 101 may be any suitable type of processor having a certain logic operation capability, such as a central processing unit, a graphics processor, or the like. Processor 101 may also include multiple cores for multi-threading or parallel processing.

The storage medium 102 may include a memory module such as a ROM, a RAM, a flash memory module, and a mass storage such as an optical disk and a hard disk. Computer programs may also be stored in the storage medium 102, and when the processor 101 executes the computer programs, various method steps or processes may be implemented.

The input/output device 103 can be any suitable type of peripheral device that provides one or more user interaction modes, such as a mouse, keyboard or touch input screen that receives user action instructions, a somatosensory camera for acquiring image information, A microphone for collecting sound information or a display screen (LCD display, LED display, etc.) for displaying image information to a user or a speaker for outputting audio.

The input/output device 103 can choose to use a wired or wireless peripheral connection, such as a USB cable or a Bluetooth connection. After the connection is established, device-related information such as device attributes and configuration information that the input/output device has will be transmitted to the operating system for the operating system to configure or correctly use the input/output device. The input device 103 can also receive an operation instruction of the user, etc., and provide the input event to the operating system to implement interaction between the user and the operating system.

Sensor device 104 can be any suitable detection device that is capable of sensing detected information and converting the detected information into an electrical signal or other suitable form of output information. The sensor device can be used for a variety of different types of detected information, with corresponding one or more sensing functions, such as temperature, light intensity, air pressure, acceleration, rotation angle, magnetic field Detection of status, humidity, sound, etc. The sensor device 104 can include one or more discrete sensors for detecting different information to meet the requirements of use.

The communication module 105 can include some network interface devices that establish connections through a wired or wireless communication network. For example, a network cable interface, a bus interface, a USB interface, a WiFi module, or a Bluetooth communication module.

In the actual application process, the physical hardware device 100 may also add or reduce one or more devices to meet different practical application requirements, such as adding a database or server device, and reducing one or more sensors.

Both the main operating system 200 and the guest operating system 300 may be any suitable type of operating system for receiving user instructions and outputting corresponding processing results to the user accordingly. The main operating system 200 uses the hardware devices of the physical hardware device 100. The guest operating system 300 uses the simulated hardware devices provided by the virtual machine program 400.

While the guest operating system 300 is running, the virtual machine program 400 emulates the hardware device for its use on the basis of the physical hardware device through some backend programs. The virtual machine program 400 runs as one of the applications in the main operating system 200. That is, the virtual machine may provide an analog hardware device for use by the guest operating system based on the physical hardware device or the basis of the simulated hardware device provided by the other virtual machine.

There is memory isolation between different operating systems, and the main operating system 200 is also unable to access the memory space of the guest operating system 300. In this way, when there are more than two guest operating systems, when one of the guest operating systems restarts due to an abnormality, the main operating system and other guest operating systems can also operate normally and are isolated from each other. Of course, since the virtual machine program runs as an application in the main operating system. Therefore, all guest operating systems need to be restarted when the primary operating system restarts due to an exception.

As shown in FIG. 1 , the main operating system 200 includes a physical input device driving unit 210 for establishing a connection between the main operating system 200 and the physical input device 100, and providing services such as an interface port in the main operating system. Control of the input device is implemented in 200.

Correspondingly, the guest operating system 300 also includes a client input device driver unit 310. The client input device driving unit 310 is in communication with the virtual machine program 400 to establish a connection between the virtual input devices simulated by the virtual machine program 400 to implement customer operations. System control of the input device.

The guest operating system 300 is further provided with an input device service unit 320 on the upper layer of the client input device driving unit 310. The input device service unit 320 provides one or more input device related services to the guest operating system by the device data processed by the client input device driving unit 310.

During the startup process of the virtual machine system, as the basis of the guest operating system, the main operating system is first started, and the activated main operating system occupies the input/output device 103 in the physical hardware device 100 through which the physical input device driving unit 210 is You can get information about the device properties, configuration information, and input events of the input device.

After the main operating system is started, when there is no task required to execute the main operating system (it can be judged according to the input event), the main operating system 200 can enter the sleep mode and release the occupied input device.

After the main operating system 200 enters the sleep mode, one of the guest operating systems 300 is booted. In a virtual machine system, each guest operating system has its own input device configured or configured. When the guest operating system is started, the client input device driving unit 310 in the kernel of the guest operating system 300 reads the device attributes and configuration information of the corresponding input device, and completes the configuration of the input device of the guest operating system.

The input event of the input device can be processed by the method provided by the embodiment of the present application, and provided to the client operating system to obtain better data processing efficiency. In the case of multiple guest operating systems, the guest operating system can also automatically enter sleep mode and boot other guest operating systems.

Correspondingly, during the operation of the virtual machine system, the operating system can be located in the foreground or in the sleep state, and exists in the background. The operating system can switch between two different states of the foreground and the background according to predetermined instructions. For example, when the predetermined time is not operated, the switch enters the background, or after receiving the operating system switching instruction, the background is switched from the background to the foreground. .

FIG. 2 is a schematic structural diagram of an apparatus for implementing an input device according to an embodiment of the present disclosure. The input device implementation device can be applied in the virtual machine system shown in FIG. 1. As shown in FIG. 2, the input device implementation device includes: an input device backend support unit 410 and a dedicated transmission. Channel 500.

The input device backend support unit 410 is configured to acquire device data of the physical input device by using the physical input device driving unit, where the device data includes at least an input event. The dedicated transmission channel 500 is for transmitting an input event therein to the input device service unit.

In this embodiment, as shown in FIG. 2, the input device backend support unit 410 may be one of the functional modules in the virtual machine program 400. The input device backend support unit 410 can acquire device data (such as device attribute information, configuration information, or input event) from an input device of the main operating system, and provide a virtual input device for the guest operating system according to the guest operating system. Implement input device services.

The dedicated transmission channel 500 is a communication channel connecting the virtual machine program 400 and the guest operating system 300, which may be any suitable form or type, a program, a hardware unit, or a data transmission function running in the virtual machine system. functional module. The dedicated transmission channel 500 provides another communication channel in which the guest operating system 300 is coupled to the virtual machine program 400 in addition to the customer input device driver unit 310.

Through the dedicated transmission channel 500, the input event can be directly transmitted to the input device service unit 320 without the need to input the device driving unit 310 through the client. In this way, the dedicated transmission channel 500 can prevent the client input device driving unit 310 from repeatedly processing the input events of the input device, and can effectively improve the processing efficiency of the input event.

In actual application, the device data may generally include two types, one is input data obtained directly by the device and having obvious time properties. In the present embodiment, "input event" is used to indicate that the input device collects the obtained input data. The other is data that has no timing property, is determined by the nature of the input device itself, for example, device properties or configuration information of the device.

As shown in FIG. 4, in order to implement the configuration or setting of the input device, the input device backend support unit 410 may also associate the device attribute or configuration information of the physical input device with the input device for configuring the information of the input device. Sended to the customer input device driving unit 310, and then the virtual input device preset by the guest operating system 300 is implemented by the customer input device driving unit 310.

The input device backend support unit 410 is a backend program in the virtual machine program for supporting the input device driver operation of the guest operating system. It can provide virtual device virtual registers, address spaces, and virtual interrupt services based on the basis of the physical input device.

FIG. 3 is a schematic diagram of input event transmission performed by the dedicated transmission channel 500 according to an embodiment of the present application. As shown in FIG. 3, in the present embodiment, the dedicated transmission channel 500 may be composed of a transmission channel backend support unit 420 belonging to the virtual machine program 400 and an input event driving unit 330 in the guest operating system.

The transmission channel backend support unit 420 is configured to acquire an input event in the device data; and send the input event to the guest operating system. The input event driving unit 330 is configured to receive the input event. After receiving the input event, the input device service unit 320 can read one or more of the input events to provide a corresponding input service. That is, the transmission channel backend support unit 420 serves as a transmitting end of data, and the input event driving unit 330 is a matching receiving end dedicated to receiving an input event transmitted by the input event.

Specifically, as shown in FIG. 3, since the input event belongs to data having time characteristics. Therefore, during the transmission and reception, the input event 1, the input event 2, the input event 3, and the like can be sequentially transmitted and received in time sequence to ensure that the input event can be accurately read.

Thus, to implement the input device in the guest operating system, the input device service unit 320 of the guest operating system can retrieve the device file node corresponding to the preset input device, and read the file from the client input device driving unit 310 one by one. Determining the attributes and configuration information of the virtual input device, and reading the input event of the corresponding device node received by the input event driving unit 330, or detecting whether a new input event is received by the input event driving unit 330, and then The input events of the virtual input device are processed accordingly.

In this embodiment, the direct data source based on the virtual input device is assumed to be a physical input device corresponding to the main operating system. In other embodiments, the direct data source of the virtual input device may also be a virtual input device corresponding to other guest operating systems. During the actual virtual machine operation, the direct data source of the virtual input device can be distinguished by setting an additional identifier or label.

4 is a complete configuration of a virtual input device of a guest operating system provided by an embodiment of the present application. Schematic diagram of the process. The input device backend support unit 410 in the virtual machine program 400 acquires attributes of the physical input device, configuration information, and input data acquired by the input device (ie, input events) according to corresponding input device files in the kernel of the main operating system 200.

The attribute and configuration information is transmitted to the client input device driving unit 310 of the guest operating system 300, and after being processed by the client input device driving unit 310, is received by the input device service unit 320. The input event can then be transmitted to the input device service unit 320 via the dedicated transmission channel 500.

The input device service unit 320 provides one or more services in the guest operating system to implement the virtual input device according to the received data.

Based on the input device implementation device provided by the foregoing embodiment, the embodiment of the present application further provides an input device implementation method applied to the virtual machine system. FIG. 5 is a flowchart of a method for implementing an input device according to an embodiment of the present disclosure.

As shown in FIG. 5, the method may include the following steps:

100. Acquire, by the physical input device driving unit, device data of a physical input device, where the device data includes at least an input event.

200. Transmitting the input event to the input device service unit through a dedicated transmission channel; the dedicated transmission channel does not pass through the client input device driving unit and supports between the virtual input device and the input device service unit Conduct communication transmission.

Through the dedicated transmission channel, the input events of the physical input device can be independently transmitted to the input device service unit of the guest operating system, thereby avoiding redundant processing of input events by the customer input device driving unit, and improving data processing efficiency.

In actual use, each guest operating system has its own predetermined input device, which can be determined by a preset configuration file. To implement these input devices in the guest operating system, in addition to the transfer of input events, the device attributes and configuration information provided by the virtual machine program are read by the customer input device drive unit (step 300). After the client input device driving unit performs processing, the device attribute or configuration information corresponding to the preset virtual input device is read by the input device service unit (step 400).

In some embodiments, the transmission of the input event can be accomplished in a manner that is sent by the virtual machine and received by the guest operating system. Input event due to input device during transmission There are specific time characteristics, so the input events can be sent sequentially according to the chronological order of the input events.

As disclosed in the virtual machine system, in a virtual machine system, the operating system can run in the foreground or in the background to sleep. 6 is a method of the guest operating system enabling the dedicated transmission channel. As shown in FIG. 6, after receiving the system switching request (step 10), it is determined whether the guest operating system is still in the foreground (step 20). If the guest operating system is switched from the foreground to the background sleep, the input data from the input device of the host operating system may be stopped from the virtual machine program (step 30). If the guest operating system is switched from the background sleep mode to the foreground, the guest operating system begins to retrieve input data from the input device of the host operating system from the virtual machine program (step 40).

It should be noted that the input device implementation method and the input device implementation device provided in the above embodiments are all based on the same inventive concept. Therefore, the steps of the specific implementations of the sensor implementation method may be performed by the corresponding function modules, and the specific functions of the function modules may also have corresponding method steps in the implementation method of the input device, and details are not described herein again.

FIG. 7 is a schematic structural diagram of hardware of an electronic device according to an embodiment of the present disclosure. The hardware device can be applied in a virtual machine system to perform the above input device implementation method. As shown in FIG. 7, the device 70 includes: one or more processors 710 and a memory 720, and one processor 710 is taken as an example in FIG.

The processor 710 and the memory 720 can be connected through a bus or other manners, and the bus connection is taken as an example in FIG. 7 .

The memory 720 is a non-volatile computer readable storage medium, and can be used for storing a non-volatile software program, a non-volatile computer executable program, and a module, such as a program corresponding to the input device implementation method in the embodiment of the present application. An instruction/module (for example, the input device backend support unit 410 and the dedicated transmission channel 500 shown in FIG. 2). The processor 710 implements various functional applications and data processing of the device by executing non-volatile software programs, instructions, and modules stored in the memory 720, that is, implementing the input device implementation method of the above method embodiments.

The memory 720 can include a storage program area and a storage data area, wherein the storage program area can store an operating system, an application required for at least one function; the storage data area can be stored Data created by the use of the device by the input device, and the like. Moreover, memory 720 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 720 can optionally include memory remotely located relative to processor 710, which can be connected to the sensor-implemented device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The one or more modules are stored in the memory 720, and when executed by the one or more processors 710, perform an input device implementation in any of the above method embodiments.

The above products can perform the methods provided by the embodiments of the present application, and have the corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the method provided by the embodiments of the present application.

An embodiment of the present application provides a computer program product, including a computing program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer, The computer performs the input device implementation method in any of the above method embodiments, for example, performing the method steps 100 and 200 of FIG. 5 described above to implement the functions of the corresponding functional modules in FIG.

The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

Through the description of the above embodiments, those skilled in the art can clearly understand that the various embodiments can be implemented by means of software plus a general hardware platform, and of course, by hardware. A person skilled in the art can understand that all or part of the process of implementing the above embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random storage memory. (RandomAccessMemory, RAM), etc.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and are not limited thereto; in the idea of the present application, the technical features in the above embodiments or different embodiments may also be combined. The steps may be carried out in any order, and there are many other variations of the various aspects of the present application as described above, which are not provided in the details for the sake of brevity; although the present application has been described in detail with reference to the foregoing embodiments, The skilled person should understand that the technical solutions described in the foregoing embodiments may be modified, or some of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the embodiments of the present application. The scope of the technical solution.

Claims

An input device implementation method is applied in a virtual machine system, the virtual machine system includes a main operating system and a plurality of guest operating systems, and the main operating system includes a physical input device driving unit for communicating with the physical input device; The guest operating system includes a client input device drive unit for communicating with a virtual input device and an input device service unit for providing an input device application, wherein the method comprises:

Obtaining, by the physical input device driving unit, device data of the physical input device, where the device data includes at least an input event;

The input event is transmitted to the input device service unit through a dedicated transmission channel; the dedicated transmission channel does not pass through the client input device drive unit.
The method according to claim 1, wherein the device data comprises: device attributes of the physical input device, configuration information of the physical input device, and input events.
The method of claim 2, wherein the guest operating system has a preset virtual input device;

The method further includes: when the device data is a device attribute or configuration information of a physical input device, transmitting the device data to the client input device driving unit;

The device attribute or configuration information corresponding to the preset virtual input device is read by the client input device driving unit.
The method according to any one of claims 1-3, wherein the transmitting the input event to the input device service unit through a dedicated transmission channel comprises:

According to the acquisition timing, the input event is sequentially transmitted to the input device service unit through a dedicated transmission channel.
The method according to any one of claims 1-3, wherein the transmitting the input event to the input device service unit through a dedicated transmission channel comprises:

Obtaining an input event in the device data;

Transmitting the input event to the guest operating system;

The input event is received and a corresponding input event is read by the input device service unit.
The method of claim 5 wherein said primary operating system and a plurality of One of the operating systems in the guest operating system runs in the foreground, and the remaining operating systems run in a sleep state;

The reading of the input event is stopped when the guest operating system switches from the foreground operation to the sleep state.
An input device implementing device is applied in a virtual machine system, the virtual machine system includes a main operating system and a plurality of guest operating systems, and the main operating system includes a physical input device driving unit for communicating with the physical input device; The guest operating system includes a client input device driving unit for communicating with the virtual input device and an input device service unit for providing the input device application, including:

An input device back end support unit, configured to acquire device data of the physical input device by using the physical input device driving unit, where the device data includes at least an input event;

a dedicated transmission channel for transmitting the input event to the input device service unit; the dedicated transmission channel does not pass through the client input device drive unit.
The apparatus according to claim 7, wherein the device data comprises: a device attribute of the physical input device, configuration information of the physical input device, and an input event.
The device according to claim 8, wherein the guest operating system has a preset virtual input device;

The input device backend support unit is further configured to: when the device data is a device attribute or configuration information of the physical input device, transmit the device data to the client input device driving unit;

The input device service unit is configured to read, by the customer input device driving unit, device attributes or configuration information corresponding to the preset virtual input device.
The device according to any one of claims 7-9, wherein the dedicated transmission channel is specifically configured to: sequentially transmit the input event to the input device service unit according to an acquisition timing.
The device according to any one of claims 7-9, wherein the dedicated transmission channel specifically comprises:

a transmission channel back end support unit, configured to acquire an input event in the device data; and send the input event to the guest operating system;

An input event driving unit disposed in the guest operating system for receiving the input event to cause the input device service unit to read a corresponding input event.
The apparatus of claim 11 wherein said primary operating system and One of the operating systems of the guest operating system runs in the foreground, and the remaining operating systems run in the sleep state;

The input device service unit is configured to stop reading the input event when the guest operating system switches from a foreground operation to a sleep state.
An electronic device, comprising:

At least one processor; and,

a memory communicatively coupled to the at least one processor; wherein

The memory stores an instruction program executable by the at least one processor, the instruction program being executed by the at least one processor to cause the at least one processor to perform any of claims 1-6 The method described.
A computer program product, comprising: a non-transitory computer readable storage medium; and computer program instructions embedded in the non-transitory computer readable storage medium; The instructions include instructions for causing a processor to perform the method of any of claims 1-6.