Virtual device model system

• US 10,268,495 B2
• Filed: 02/18/2016
• Issued: 04/23/2019
• Est. Priority Date: 02/18/2016
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Chen, Zhong, Zhu, Lin, Hao, Jianxiu
• Primary Examiner(s): Gebresilassie, Kibrom K
• Application Number:
  US15/046,991
• Publication Number:
  US 20170242714A1
• Time in Patent Office: 1,160 Days
• Field of Search: None
• CPC Class Codes: B64U 2101/00 UAVs specially adapted for particular uses or applications
• CPC Class Codes: B64U 2101/21 for providing Internet access
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 12/2823 Reporting information sensed by appliance or service execution status of appliance services in a home automation network device-related reporting H04L43/065; arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom H04Q9/00
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

A computer device may include logic configured to receive, from a user device via a network, a manufacturer-independent request intended for a target device; identify a virtual device model instance associated with the target device; and identify a virtual device model associated with the identified virtual device model instance. The logic may be further configured to select a manufacturer adapter based on the identified virtual device model instance and the identified virtual device model; generate a manufacturer-specific request for the target device based on the received manufacturer-independent request and the selected manufacturer adapter; and send, via the network, the generated manufacturer-specific request to the target device.

Claims

1. A method performed by a computer device, the method comprising:

receiving, by the computer device via a network from an application running on a user device, a manufacturer-independent request intended for a target device, wherein the manufacturer-independent request includes an instruction for the target device to perform an action, and wherein the instruction is in a protocol or format associated with a virtual device model;

identifying, by the computer device, a virtual device model instance associated with the target device;

identifying, by the computer device, a virtual device model associated with the identified virtual device model instance;

selecting, by the computer device, a manufacturer adapter based on the identified virtual device model instance and the identified virtual device model;

converting, by the computer device, the manufacturer-independent request to a manufacturer-specific request for the target device using the selected manufacturer adapter, wherein the manufacturer-specific request includes the instruction for the target device to perform the action in a protocol or format associated with a manufacturer'"'"'s implementation of the target device, and wherein converting the manufacturer-independent request to the manufacturer-specific request for the target device hides a manufacturer'"'"'s implementation of the target device from the application running on the user device; and

sending, by the computer device and via the network, the manufacturer-specific request to the target device to perform the action.

2. The method of claim 1, wherein receiving the manufacturer-independent request intended for the target device includes:

providing an Application Programming Interface (API), for generating and accessing virtual device models, to the user device; and

receiving the manufacturer-independent request via the provided API.

3. The method of claim 2, further comprising providing a wrapper for the API, wherein the wrapper enables a particular operating system to interface with the API.

4. The method of claim 1, wherein converting the manufacturer-independent request to the manufacturer-specific request for the target device using the selected manufacturer adapter includes:

identifying a first set of attribute-value pairs associated with the manufacturer-independent request;

identifying a second set of attribute-value pairs associated with the manufacturer-specific request; and

mapping the first set of attribute-value pairs to the second set of attribute-value pairs.

5. The method of claim 4, further comprising:

determining that a particular one of the second set of attribute-value pairs has not been provided with a value as a result of the mapping; and

generating a default value for the particular one of the second set of attribute-value pairs.

6. The method of claim 4, wherein mapping the first set of attribute-value pairs to the second set of attribute-value pairs includes:

selecting a particular one of the first set of attribute-value pairs;

executing a conversion function to convert a first value from the particular one of the first set of attribute-value pairs into a second value; and

generating a particular one of the second set of attribute-value pairs, associated with the particular one of the first set of attribute-value pairs, wherein the particular one of the second set of attribute-value pairs includes the second value.

7. The method of claim 1, further comprising:

receiving a manufacturer-specific message from a source device;

identifying a source device virtual device model instance associated with the source device;

identifying a source device adapter associated with the source device virtual device model instance;

generating a manufacturer-independent message using the identified source device adapter based on the received manufacturer-specific message;

determining a target device for the manufacturer-independent message; and

providing the manufacturer-independent message to the determined target device.

8. The method of claim 7, further comprising:

determining that a rule is associated with the identified source device virtual device model instance; and

executing the rule in response to generating the manufacturer-independent message.

9. The method of claim 1, further comprising:

receiving a request to generate a new virtual device model instance for another target device;

identifying a device type associated with the other target device;

determining whether the identified device type is associated with an existing virtual device model; and

generating the new virtual device model instance based on the existing virtual device model, when the identified device type is associated with an existing virtual device model.

10. The method of claim 9, further comprising:

determining that the identified device type is associated with another device type;

identifying the existing virtual device model associated with the other device type; and

deriving a new virtual device model from the existing virtual device model using inheritance.

11. The method of claim 9, further comprising:

determining whether a compatible manufacturer adapter exists for the new virtual device model instance;

associating the compatible manufacturer adapter with the new virtual device model instance, when the compatible manufacturer adapter exists; and

generating a new manufacturer adapter for the new virtual device model instance, when the compatible manufacturer adapter does not exist.

12. A computer device comprising:

logic configured to;

receive, from an application running on a user device via a network, a manufacturer-independent request intended for a target device, wherein the manufacturer-independent request includes an instruction for the target device to perform an action, and wherein the instruction is in a protocol or format associated with a virtual device model;

identify a virtual device model instance associated with the target device;

identify a virtual device model associated with the identified virtual device model instance;

select a manufacturer adapter based on the identified virtual device model instance and the identified virtual device model;

convert the manufacturer-independent request to a manufacturer-specific request for the target device using the selected manufacturer adapter, wherein the manufacturer-specific request includes the instruction for the target device to perform the action in a protocol or format associated with a manufacturer'"'"'s implementation of the target device, and wherein converting the manufacturer-independent request to the manufacturer-specific request for the target device hides a manufacturer'"'"'s implementation of the target device from the application running on the user device; and

send, via the network, the manufacturer-specific request to the target device to perform the action.

13. The computer device of claim 12, wherein, when receiving the manufacturer-independent request intended for the target device, the logic is further configured to:

provide an Application Programming Interface (API), for generating and accessing virtual device models, to the user device; and

receive the manufacturer-independent request via the provided API.

14. The computer device of claim 12, wherein, when converting the manufacturer-independent request to the manufacturer-specific request for the target device using the selected manufacturer adapter, the logic is further configured to:

identify a first set of attribute-value pairs associated with the manufacturer-independent request;

identify a second set of attribute-value pairs associated with the manufacturer-specific request; and

map the first set of attribute-value pairs to the second set of attribute-value pairs.

15. The computer device of claim 14, wherein the logic is further configured to:

determine that a particular one of the second set of attribute-value pairs has not been provided with a value as a result of the mapping; and

generate a default value for the particular one of the second set of attribute-value pairs.

16. The computer device of claim 15, wherein, when mapping the first set of attribute-value pairs to the second set of attribute-value pairs, the logic is further configured to:

select a particular one of the first set of attribute-value pairs;

execute a conversion function to convert a first value from the particular one of the first set of attribute-value pairs into a second value; and

generate a particular one of the second set of attribute-value pairs, associated with the particular one of the first set of attribute-value pairs, wherein the particular one of the second set of attribute-value pairs includes the second value.

17. The computer device of claim 12, wherein the logic is further configured to:

receive a request to generate a new virtual device model instance for another target device;

identify a device type associated with the other target device;

determine whether the identified device type is associated with an existing virtual device model; and

generate the new virtual device model instance based on the existing virtual device model, when the identified device type is associated with an existing virtual device model.

18. The computer device of claim 17, wherein the logic is further configured to:

determine that the identified device type is associated with another device type;

identify the existing virtual device model associated with the other device type; and

derive a new virtual device model from the existing virtual device model using inheritance.

19. The computer device of claim 18, wherein the logic is further configured to:

determine whether a compatible manufacturer adapter exists for the new virtual device model instance;

associate the compatible manufacturer adapter with the new virtual device model instance, when the compatible manufacturer adapter exists; and

generate a new manufacturer adapter for the new virtual device model instance, when the compatible manufacturer adapter does not exist.

20. A non-transitory memory device, storing instructions executable by a processor, the non-transitory memory device comprising:

one or more instructions to receive via a network, from an application running on a user device, a manufacturer-independent request intended for a target device, wherein the manufacturer-independent request includes an instruction for the target device to perform an action, and wherein the instruction is in a protocol or format associated with a virtual device model;

one or more instructions to identify a virtual device model instance associated with the target device;

one or more instructions to identify a virtual device model associated with the identified virtual device model instance;

one or more instructions to select a manufacturer adapter based on the identified virtual device model instance and the identified virtual device model;

one or more instructions to convert the manufacturer-independent request to a manufacturer-specific request for the target device using the selected manufacturer adapter, wherein the manufacturer-specific request includes the instruction for the target device to perform the action in a protocol or format associated with a manufacturer'"'"'s implementation of the target device, and wherein converting the manufacturer-independent request to the manufacturer-specific request for the target device hides a manufacturer'"'"'s implementation of the target device from the application running on the user device; and

one or more instructions to send, via the network, the manufacturer-specific request to the target device to perform the action.