Network device application interface

• US 20040133896A1
• Filed: 12/20/2002
• Published: 07/08/2004
• Est. Priority Date: 12/20/2002
• Status: Abandoned Application

• Current Assignee: Sony Corporation (Sony Group Corp.), Sony Electronics Inc. (Sony Group Corp.)
• Original Assignee: SONY CORPORATION AND SONY ELECTRONICS, INC.
• Inventors: Sato, Naoyuki, Lym, Kevin K., Sun, Jadie
• Application Number:
  US10/327,573
• Publication Number:
  US 20040133896A1
• Time in Patent Office: Days
• US Class Current: 719/315
• CPC Class Codes: H04L 12/2803 Home automation networks
• CPC Class Codes: H04L 12/2805 Home Audio Video Interoperability [HAVI] networks
• CPC Class Codes: H04L 12/282 based on user interaction within the home receiver circuitry for displaying additional information being controlled by a remote control apparatus H04N21/42204
• CPC Class Codes: H04L 12/2836 Protocol conversion between an external network and a home network controlling appliance services of a home automation network from a device located outside the home and the home network H04L12/2818; protocol conversion H04L69/08; adaptation of digital video signals for transport over a specific home network H04N7/24
• CPC Class Codes: H04L 2012/2849 Audio/video appliances

Abstract

A network device application programming interface (API) provides an interface to control and receive events from network devices. The network device API preferably resides within a control device, which is coupled to a network of devices. Each network device preferably uses IP-based protocols for sending control commands, and for receiving responses to the commands and asynchronous events. The network device API provides an interface that can be used across many different platforms. The interface is used as part of an application or as a standalone application. The network device API also provides a framework for defining and implementing a device control protocol. The framework for defining and implementing the device control protocol provides common functionality across multiple control and eventing protocols.

Claims

1. A control device coupled to a network of devices the control device comprising:

a. one or more applications;

b. a network layer coupled to interface with one or more network devices; and

c. an interface layer coupled to communicate with the applications and the network layer and provide control, query and event communications between the applications and one or more network devices.

2. The control device of claim 1 wherein the interface layer comprises a device object for each network device.

3. The control device of claim 2 wherein each device object includes one or more service objects and one or more event objects.

4. The control device of claim 3 wherein the one or more service objects and the one or more event objects of each device object are coupled to the network layer.

5. The control device of claim 2 wherein the device object includes a device description corresponding to the network device.

6. The control device of claim 5 wherein the device description includes control and response functionality of the network device.

7. The control device of claim 1 wherein the network is an Internet Protocol (IP) based network.

8. The control device of claim 1 wherein the interface layer is an application programming interface (API).

9. The control device of claim 1 wherein the interface layer is protocol independent.

10. The control device of claim 1 wherein the network layer includes a Universal Plug and Play protocol stack.

11. The control device of claim 10 wherein one or more network devices are Universal Plug and Play enabled devices.

12. A network comprising:

a. one or more network devices; and

b. a control device comprising;

i. one or more applications;

ii. a network layer coupled to interface with the one or more network devices; and

iii. an interface layer coupled to communicate with the applications and the network layer and provide control, query and event communications between the applications and the one or more network devices.

13. The network of claim 12 wherein the interface layer comprises a device object for each network device.

14. The network of claim 13 wherein each device object includes one or more service objects and one or more event objects.

15. The network of claim 14 wherein the one or more service objects and the one or more event objects of each device object are coupled to the network layer.

16. The network of claim 13 wherein the device object includes a device description corresponding to the network device.

17. The network of claim 16 wherein the device description includes control and response functionality of the network device.

18. The network of claim 12 wherein the network is an Internet Protocol (IP) based network.

19. The network of claim 12 wherein the interface layer is an application programming interface (API).

20. The network of claim 12 wherein the interface layer is protocol independent.

21. The network of claim 12 wherein the network layer includes a Universal Plug and Play protocol stack.

22. The network of claim 21 wherein one or more network devices are Universal Plug and Play enabled devices.

23. A method of providing an interface to applications resident within a control device coupled to a network of devices, the method comprising:

a. sending and receiving messages to and from the applications through an interface layer regarding control commands to control one or more of the network devices by the applications; and

b. generating and receiving communications at the interface layer to complete the control commands.

24. The method of claim 23 wherein communications generated at the interface layer are sent to a network layer within the control device and communications received at the interface layer are received from the network layer.

25. The method of claim 24 wherein the network layer includes a Universal Plug and Play protocol stack and one or more of the network devices are Universal Plug and Play enabled devices.

26. The method of claim 24 wherein the interface layer generates a device object for each network device to communicate with the network layer.

27. The method of claim 26 wherein the interface layer generates one or more service objects within the device object such that each service object corresponds to a service or a set of services provided by the network device corresponding to the device object.

28. The method of claim 26 wherein the interface layer generates one or more event objects within the device object such that each event object corresponds to an event associated with the network device corresponding to the device object.

29. A method of providing an interface to applications resident within a control device coupled to a network of devices, the method comprising:

a. generating a device object corresponding to a network device;

b. generating one or more service objects within the device object wherein each service object corresponds to a service or a set of services provided by the network device;

c. generating one or more event objects within the device object wherein each event object corresponds to an event associated with the network device; and

d. providing control, query and event communications between a network layer and the service and event objects;

wherein the control device uses the device object to provide control commands to the network device.

30. An application programming interface (API) used by a control device, the API comprising:

a. a plurality of interfaces to define control and response functionality of a network device coupled to the control device;

b. an input-output class to handle input and output functionality of the control device; and

c. a data container class to define a data object corresponding to the network device wherein the API provides control, query and event communications between the network device and an application resident within the control device.