Object-oriented web server architecture suitable for various types of devices

• US 6,529,936 B1
• Filed: 12/23/1998
• Issued: 03/04/2003
• Est. Priority Date: 12/23/1998
• Status: Expired due to Term

• Current Assignee: Innovative Building Management Systems, Inc.
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Morgan, Jeffrey Alan, Mayo, Glenna G., Reddy, Jayarami A.
• Primary Examiner(s): WINDER, PATRICE L
• Application Number:
  US09/219,272
• Time in Patent Office: 1,532 Days
• Field of Search: 340/825.06, 700/83, 345/329, 709/201, 709/202, 709/217, 709/218, 709/219, 709/223, 709/203, 717/11
• US Class Current: 709/202
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A web access mechanism in a device is described. The web access mechanism includes at least an object that includes a plurality of functions of the device. The object includes a unique name that identifies the object and a web page that provides an interface to the object. The object also includes a plurality of properties, each of which can represent an interface to one of the functions of the object. The web access mechanism also includes a web core engine that calls one of the functions of the object to be loaded and executed in the web core engine in accordance with a request that contains the unique name of the object and the property name of the function. A method of invoking one of the functions in the web access mechanism is also described.

Claims

1. An object-oriented web access mechanism embedded in a device, the object-oriented web access mechanism comprising:

(A) at least an object that implements a plurality of functions of the device, wherein the object further comprises;

(I) a unique name that identifies the object;

(II) a web page that provides an interface to the object; and

(III) a plurality of properties, each of which can represent an interface to one of the functions of the object and are accessed via a URL; and

(B) a web core engine that provides an execution environment for the object in accordance with a request that contains the unique name of the object and a property name of the function.

2. The object-oriented web access mechanism of claim 1, wherein each of the properties includes an Internet address such that each of the functions of the object can be accessed.

3. The object-oriented web access mechanism of claim 2, wherein the address for one of the properties further comprises:

(I) an argument field that allows data input to the function; and

(II) a result field that allows the function, when executed, to return results.

4. The object-oriented web access mechanism of claim 1, wherein the object can be installed or modified dynamically at run-time and organized relative to the other objects without stopping the web core engine.

5. The object-oriented web access mechanism of claim 1, wherein the object includes a plurality of types, each allowing an external request to access one of a plurality of properties belonging to the type.

6. The object-oriented web access mechanism of claim 1, wherein some of the properties of the object provide interface to other objects to allow the object to contain the other objects such that functions of the other objects can be inherited by the object.

7. The object-oriented web access mechanism of claim 1, further comprising a plurality of objects, including a builder object that links multiple properties from multiple objects together.

8. The object-oriented web access mechanism of claim 7, wherein builder object provides the results of the linked multiple objects either through its web page or directly to a client.

9. The object-oriented web access mechanism of claim 1, wherein the web core engine further comprises an interface manager that calls the object based on the unique name of the object, the Internet addresses of the object and the corresponding property defined in a request for the object.

10. The object-oriented web access mechanism of claim 1, further comprising another object that shares the interface provided by the web page.

11. The object-oriented web access mechanism of claim 1, further comprising a plurality of objects, some of which can be contained by other objects.

12. The object-oriented web access mechanism of claim 1, wherein one of the properties of the object has different parameters and multiple implementations.

13. In a device embedded with an object-oriented web access mechanism, a method of invoking a function of the device, said method comprising:

(A) providing an object that implements a plurality of functions of the device, wherein the object further comprises;

(I) a unique name that identifies the object;

(II) a web page that provides an interface to the object; and

(III) a plurality of properties embedded in the web page, each of which can represent an interface to one of the functions of the object and are accessed via a URL; and

(B) executing the function in an execution environment provided by a web core engine of the object-oriented web access mechanism in accordance with a request that contains the unique name of the object and a property name of the function.

14. The method of claim 13, further comprising:

(I) providing an argument field for the Internet address of one of the properties that allows data input to the corresponding function;

(II) providing a result field for the property that allows the function, when executed, to return results;

(III) providing a specification of the type of the returned property; and

(IV) providing an Internet address to each of the properties such that each of the functions of the object can be accessed, wherein the object only needs a URL address to invoke the property of another object.

15. The method of claim 13, further comprising:

dynamically installing or modifying the object at run-time without stopping the web core engine.

16. The method of claim 13, further comprising:

containing multiple objects in the object by allowing some of the properties of the object to provide interface to the multiple objects such that functions of the multiple objects can be inherited by the object.

17. The method of claim 13, further comprising:

linking multiple properties of multiple objects together in a builder object, wherein the builder object provides the results of the linked multiple objects either through its web page or directly to a client.

18. The method of claim 13, further comprising:

grouping the properties of the object into a number of types, each type allowing an external request to access one of the properties belonging to the type via an interface of the type.