Architecture of a bridge between a non-IP network and the web

• US 20010032273A1
• Filed: 12/13/2000
• Published: 10/18/2001
• Est. Priority Date: 02/23/2000
• Status: Active Grant

• Current Assignee: Koninklijke Philips N.V.
• Original Assignee: Koninklijke Philips N.V.
• Inventors: Cheng, Doreen Yining
• Granted Patent: US 7,111,079 B2
• Time in Patent Office: Days
• US Class Current: 709/249
• CPC Class Codes: H04L 12/2805 Home Audio Video Interoperability [HAVI] networks
• CPC Class Codes: H04L 12/281 indicating a format for calling an appliance service function in a home automation network for remote control or remote monitoring of applications H04L67/025
• CPC Class Codes: H04L 12/2814 Exchanging control software or macros for controlling appliance services in a home automation network arrangements for maintenance or administration involving configuration of the network and network elements H04L41/08
• CPC Class Codes: H04L 12/2832 Interconnection of the control functionalities between home networks single bridge functionality H04L12/4625
• 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 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/085 specially adapted for interworking of IP-based networks with other networks
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Thin glue layers bridge a Non-IP network and the Internet Web. Existing services in both networks are used directly wherever feasible, thereby achieving simplicity and efficiency. A Non-IP-specific application can use a Non-IP API to access Internet services, and an IP-based Internet browser can use commands encoded in HTTP, XML, Java, or proprietary formats to access Non-IP services and to control Non-IP devices. In this manner, changes are not required to the Internet browser. The glue layers translate between the IP protocol and Non-IP API, but also allow commands and responses to tunnel between end applications in the Internet and the Non-IP network without interpretation.

Claims

1. A bridge that is configured to facilitate communications between a first network of Non-IP-compatible entities and a second network of IP-compatible entities, comprising:

a Non-IP to IP interface that is configured to facilitate communications between an application entity on the first network and a Web server on the second network, and an IP to Non-IP interface that is configured to facilitate communications between a Web browser on the second network and a Non-IP device entity on the first network.

2. The bridge as claimed in

claim 1

, wherein

the Non-IP to IP interface includes:

an IP Web client that is operably coupled to the second network, and is configured to appear as a client to the Web server;

a Non-IP Web proxy that is operably coupled to the IP Web client and the first network, and is configured to make the IP Web client compliant with middleware that is associated with the Non-IP network; and

a Non-IP Web proxy client that is operably coupled to the Non-IP Web proxy and the first network, and is configured to allow the application entity to access the Web server.

3. The bridge of

claim 2

, wherein

the IP Web client is configured to selectively translate a first set of communications between the Web server and the first network, and to pass a second set of communications between the Web server and the first network without translation.

4. The bridge as claimed in

claim 2

, wherein

the Non-IP Web proxy is configured to facilitate communications between the Web server and a Non-IP service.

5. A bridge as claimed in

claim 2

, wherein

the IP to Non-IP interface includes:

a Non-IP Web server that is operably coupled to the second network, and is configured to appear as an Internet server to the Web browser;

a Web service executor that is operably coupled to the Non-IP Web server and to the first network, and is configured to provide access to the Non-IP device entity;

a Web page generator that is operably coupled to the Non-IP Web server and to the first network, and is configured to generate web pages for presentation to the Web browser; and

a translation manager that is operably coupled to the Non-IP Web server, the Web service executor, and the Web page generator, and is configured to provide service-to-user-interface and message-to-methods translation services.

6. The bridge as claimed in

claim 1

, wherein

the IP to Non-IP interface includes:

a Non-IP Web server that is operably coupled to the second network, and is configured to appear as an Internet server to the Web browser;

a Web service executor that is operably coupled to the Non-IP Web server and to the first network, and is configured to provide access to the Non-IP device entity;

a Web page generator that is operably coupled to the Non-IP Web server and to the first network, and is configured to generate web pages for presentation to the Web browser; and

a translation manager that is operably coupled to the Non-IP Web server, the Web service executor, and the Web page generator, and is configured to provide service-to-user-interface and message-to-methods translation services.

7. The bridge of

claim 6

, wherein

the Non-IP Web server is configured to selectively translate a first set of communications between the Web browser and the first network, and to pass a second set of communications between the Web browser and the first network without translation.

8. A Non-IP network comprising

at least one Non-IP-compatible device, and

a bridge that includes:

a Non-IP to IP interface that is configured to facilitate communications between

an application entity on the Non-IP network and a Web server on an IP network, and an IP to Non-IP interface that is configured to facilitate communications between a Web browser on the IP network and the at least one Non-IP-compatible device on the Non-IP network.

9. The Non-IP network as claimed in

claim 8

, wherein

the Non-IP to IP interface includes:

an IP Web client that is operably coupled to the IP network, and is configured to appear as a client to the Web server;

a Non-IP Web proxy that is operably coupled to the IP Web client and the Non-IP network, and is configured to make the IP Web client compliant with middleware that is associated with the Non-IP network; and

a Non-IP Web proxy client that is operably coupled to the Non-IP Web proxy and the Non-IP network, and is configured to allow the application entity to access the Web server.

10. The Non-IP network as claimed in

claim 9

, wherein

the IP Web client is configured to selectively translate a first set of communications between the Web server and the Non-IP network, and to pass a second set of communications between the Web server and the Non-IP network without translation.

11. The Non-IP network as claimed in

claim 8

, wherein

the IP to Non-IP interface includes:

a Non-IP Web server that is operably coupled to the IP network, and is configured to appear as an Internet server to the Web browser;

a Web service executor that is operably coupled to the Non-IP Web server and to the Non-IP network, and is configured to provide access to the at least one Non-IP-compatible device;

a Web page generator that is operably coupled to the Non-IP Web server and to the Non-IP network, and is configured to generate web pages for presentation to the Web browser; and

a translation manager that is operably coupled to the Non-IP Web server, to the Web service executor, and to the Web page generator, and is configured to provide service-to-user-interface and message-to-methods translation services.

12. The Non-IP network as claimed in

claim 11

, wherein

the Non-IP Web server is configured to selectively translate a first set of communications between the Web browser and the Non-IP network, and to pass a second set of communications between the Web browser and the Non-IP network without translation.

13. A method of enabling interactions between a Non-IP network and an IP network, comprising:

establishing an IP connection between a browser on the IP network and a server at a bridge element,

communicating a web page corresponding to the server to the browser,

receiving a user input from the browser to the server, based on the web page,

processing the user input to produce one or more commands related to an object on the Non-IP network, and

communicating the one or more commands to the object.

14. The method of

claim 13

, further including:

determining a status corresponding to the object on the Non-IP network, creating a web page corresponding to a status of the object, and communicating the web page from the server to the browser.

15. The method of

claim 13

, further including:

receiving an access request from a Non-IP-compatible application,

communicating the access request to a Web server on the IP network,

receiving a web page corresponding to the Web server, and

communicating messages corresponding to the web page to the Non-IP-compatible application.