IP Library Patent Application 11590672
Patent Application
App. No. 11/590,672

Protocol independent application layer for an automation network

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
11/590,672
Abstract

A software architecture for an automation network is disclosed that implements a high level, protocol-independent interface for a network system. The software architecture includes a system layer interface to maintain a protocol-independent interface with a transport layer and an application layer of the automation network. The system layer interface includes command libraries to route data within the network system, a node map to store data related to locations of network nodes, and a bridge table to store data related to network bridges. Using the software architecture, a programmer may not need to understand the network protocols run by nodes within the network system.

Claims (53)

1 . A software architecture for an automation network, the software architecture encoded in a computer-readable medium and configured to interface with a network system including networks each running a network protocol and including a network node and a network bridge coupling the networks, the software architecture comprising:

a system layer interface retained in the computer-readable medium and configured to maintain a protocol-independent interface with a transport layer and an application layer of the automation network, where the system layer interface comprises:

a command library that include functions to route data within the network system;

a node map configured to store data related to locations of the network node; and

a bridge table configured to store data related to the network bridge.

2 . The software architecture of claim 1 , where the system layer interface is further configured to maintain a network interface mapping related to the network system.

3 . The software architecture of claim 1 , where the system layer interface is configured to route data between network nodes using the node map, the bridge table, and at least one command selected from the command library.

4 . The software architecture of claim 1 , where the system level interface comprises a high-level language that describes interactions between the networks in the network system.

5 . The software architecture of claim 1 , where at least one of the networks runs a network protocol different from another network protocol run by another network of the at least one networks.

6 . The software architecture of claim 1 , where the command library includes functions related to at least one of transport layer functions, data encapsulation, data formatting, frequency conversion between networks, data encryption, or packetization.

7 . The software architecture of claim 1 , where the network system comprises a home automation network, a commercial automation network, an industrial automation network, or a medical automation network.

8 . The software architecture of claim 7 , where all the network nodes running each of the different network protocols are included in the node map.

9 . The software architecture of claim 8 , where the network nodes are not built on the software architecture.

10 . A method for maintaining cohesion within a network system, the network system including networks each running a network protocol and including a network node and a network bridge coupling the networks, the method comprising:

accessing a system level interface, where the system layer interface is configured to maintain a protocol-independent interface with a transport layer and an application layer of the network system, the system level interface including a command library that include functions to route data within the network system, a node map configured to store data related to locations of the network node, and a bridge table configured to store data related to the network bridge; and

determining a network interface mapping using an interface command from the command library.

11 . The method of claim 10 , where determining the network interface mapping. comprises determining a network interface mapping between at least one network running a first network protocol and at least one network running a second network protocol different from the first network protocol.

12 . The method of claim 10 , further comprising:

storing data related to locations of the network node in a node map in communication with the system level interface; and

storing data related to the network bridge in a bridge table in communication with the system level interface.

13 . The method of claim 12 , further comprising determining a routing path of data between network nodes using a portion of the data stored the node map and a portion of the data stored in the bridge table.

14 . The method of claim 10 , where determining the network interface mapping comprises determining a command related to at least one of transport layer functions, data encapsulation, data formatting, frequency conversion between networks, data encryption, or packetization.

15 . The method of claim 10 , where the method is configured for use in a home automation network, a commercial automation network, an industrial automation network, or a medical automation network.

16 . The method of claim 15 , further comprising including all the network nodes of each of the different network protocols in the node map.

17 . The method of claim 16 , where including all the network nodes comprises including network nodes that do not implement the system level interface.

18 . A method for routing data in a network system, the network system including networks each running a network protocol and including a network node and a network bridge coupling the networks, the method comprising:

accessing a system level interface, where the system layer interface is configured to maintain a protocol-independent interface with a transport layer and an application layer of the network system, the system level interface including a command library that includes a function to route data within the network system, a node map configured to store data related to locations of the network node, and a bridge table configured to store data related to the network bridge;

determining a routing path of data between network nodes using a portion of the data stored the node map and a portion of the data stored in the bridge table; and

transmitting the data between the network nodes based on the routing path of data.

19 . The method of claim 18 , where determining the network interface mapping comprises determining a network interface mapping between at least one network running a first network protocol and at least one network running a second network protocol different from the first network protocol.

20 . The method of claim 18 , where determining the network interface mapping comprises determining a command related to transport layer functions, data encapsulation, data formatting, frequency conversion between networks, data encryption, or packetization.

21 . The method of claim 18 , where the method is configured for use in a home automation network, a commercial automation network, an industrial automation network, or a medical automation network.

22 . The method of claim 21 , further comprising including all the network nodes of each of the different network protocols in the node map.

23 . The method of claim 22 , where including all the network nodes comprises including network nodes that do not implement the system level interface.

24 . A computer program product for maintaining cohesion within a network system, the network system including networks each running a network protocol and including a network node and a network bridge coupling the networks, the computer program product comprising a computer-readable medium comprising:

computer-executable code means executable to access a system level interface, where the system layer interface is configured to maintain a protocol-independent interface with a transport layer and an application layer of the network system, the system level interface including a command library that include functions to route data within the network system, a node map configured to store data related to locations of the network node, and a bridge table configured to store data related to the network bridge; and

computer-executable code means executable to determine a network interface mapping using an interface command from the command library.

25 . The computer program product of claim 24 , where the computer-executable code means executable to determine the network interface mapping comprises computer-executable code means executable to determine a network interface mapping between at least one network running a first network protocol and at least one network running a second network protocol different from the first network protocol.

26 . The computer program product of claim 24 , further comprising:

computer-executable code means executable to store data related to locations of the network node in a node map in communication with the system level interface; and

computer-executable code means executable to store data related to the network bridge in a bridge table in communication with the system level interface.

27 . The computer program product of claim 26 , further comprising computer-executable code means executable to determine a routing path of data between network nodes using a portion of the data stored the node map and a portion of the data stored in the bridge table.

28 . The computer program product of claim 25 , where the computer-executable code means executable to determine the network interface mapping comprises computer-executable code means executable to determine a command related to transport layer functions, data encapsulation, data formatting, frequency conversion between networks, data encryption, or packetization.

29 . A computer program product for routing data in a network system, the network system including networks each running a network protocol and including a network node and a network bridge coupling the networks, the computer program product comprising a computer-readable medium comprising:

computer-executable code means executable to access a system level interface, where the system layer interface is configured to maintain a protocol-independent interface with a transport layer and an application layer of the network system, the system level interface including a command library that includes functions to route data within the network system, a node map configured to store data related to locations of the network node, and a bridge table configured to store data related to the network bridge; and

computer-executable code means executable to determine a network interface mapping using an interface command from the command library.

computer-executable code means executable to determine a routing path of data between network nodes using a portion of the data stored the node map and a portion of the data stored in the bridge table; and

computer-executable code means executable to transmit the data between the network nodes based on the routing path of data.

30 . The computer program product of claim 29 , where the computer-executable code means executable to determine the network interface mapping comprises computer-executable code means executable to determine a network interface mapping between at least one network running a first network protocol and at least one network running a second network protocol different from the first network protocol.

31 . The computer program product of claim 29 , where the computer-executable code means executable to determine the network interface mapping comprises computer-executable code means executable to determine a command related to transport layer functions, data encapsulation, data formatting, frequency conversion between networks, data encryption, or packetization.

32 . The computer program product of claim 29 , where the computer program product is configured for use in a home automation network, a commercial automation network, an industrial automation network, or a medical automation network.

33 . The computer program product of claim 32 , where all the network nodes running each of the different network protocols are included in the node map.

34 . The method of claim 33 , where the network nodes include network nodes that do not implement the system level interface.

Assignments (3)
RELEASE OF SECURITY INTEREST Recorded Mar 10, 2014
From: BANK OF AMERICA, N.A.
To: INTERMATIC INCORPORATED
Reel/Frame 032422/0879 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Jun 20, 2008
From: INTERMATIC INCORPORATED
To: BANK OF AMERICA, N.A., AS AGENT
Reel/Frame 021118/0815 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 23, 2007
From: RECKAMP, STEVEN R.; DINESCU, MIKY; MAZZA, JOSEPH; APER, GREGORY J.; PELLAND, MICHAEL; DOORHY, BRENDAN; GAZA, BRIAN; BOVEE, JEFFREY K.; DUITSMAN, TIM
To: INTERMATIC INCORPORATED
Reel/Frame 018790/0602 →