Patent Grant
8572224
1. Field of the Invention
This invention is related in general to the field of network control systems. More particularly, the invention is related to an Internet control system communication protocol and method.
2. Discussion of the Background
In a fully automated environment, appliances that change the various parameters of the environment can be inked to a control area network (CAN) and a controller. The appliances may include heating, ventilation and air conditioning (HVAC) systems, lighting systems, audio-visual systems, telecommunications systems, security systems, surveillance systems, and fire protection systems, for example. One or more easy-to-use user interface, such as a touch panel, may be electronically linked to the control area network to accept user input and display current system status. AMX LLC of Dallas, Tex. designs and manufactures such networked appliance control systems.
In accordance with the present invention, a system and method of Internet control network is provided which eliminates or substantially reduces the disadvantages associated with prior control systems.
In one aspect of the invention, the boundaries between the Internet and the control area network are made transparent and the Internet becomes a device on the control area network. The Internet is controllable by user input entered on the user interface, such as touch panel. The Internet is further capable of receiving commands from the master controller in the control area network.
In another aspect of the invention, Internet applications such as web browsers and applications executing on web servers of information content providers become devices on the control area network. The Internet applications are capable of sending commands to and receiving commands from the control area network.
In yet another aspect of the present in invention, a communication protocol is provided. The communication protocol comprises a packet protocol. The packet protocol has a protocol field for indicating the type of protocol, a length of data field for listing the length in bytes of the data field, a data field containing sub protocol data, and, a checksum for determining the integrity of the packet.
In yet another aspect of the invention, a dynamic message protocol generator is provided to enable a scripting language such as VBScript or JavaScript capable of directly communicating on any TCP/IP network connection.
In yet a further aspect of the invention, a method for controlling communications between a control area network and a data network comprises receiving user input at a controller coupled to the control area network from a node coupled to the data network, receiving user input at the controller from a node coupled to the control area network, and instructing an internet appliance coupled to the control area network to perform a command based on at least one of the received user inputs.
In yet a another aspect of the invention, a controller for controlling communications between a control area network and a data network comprises a first module that receives user input from at least one of: a node coupled to the data network, and a node coupled to the control area network, and a second module that instructs an internet appliance coupled to the control area network to perform a command based on at least one of the received user inputs, wherein the controller is coupled to the control area network, and wherein the controller and the internet appliance are specified by a unique address.
In yet a further aspect of the invention, a computer readable medium comprises instructions for: receiving, by a web server, data from an internet appliance, instantiating, by the web server, one or more processes to handle the data, sending, by the process, a message containing the data to a recipient's software logical device, storing the sent data, by the software logical device, in an indexed position in a data structure, turning on, by the software logical device, an input channel associated with the indexed position, receiving, by a master controller, a state associated with the input channel, and sending, by the software logical device via an output channel, the stored data to the master controller.
For a better understanding of the present invention, reference may be made to the accompanying drawings, in which:
System 10 includes a control network portal 12 coupled between the Internet 22 and one or more control area networks 30 and 31. Control area networks 30 and 31 are local area networks operating under transport protocols such as Ethernet, and AXLink and PhastLink of AMX LLC (Dallas, Tex.), the assignee of the present invention, that interconnect a variety of devices, appliances and/or equipment. The underlying network connectivity 34 may be wired, wireless, power line carriers, or any suitable transmission medium. Coupled to control area networks 30 and 31 are a plurality of devices, appliances and/or equipment, including control area network user interfaces (CAN UI/F) 35, master controllers 36, and Internet appliances 37-39. Some devices may be coupled to control area networks 30 and 31 via additional intermediate communications devices, such as an RS 232 controller (not shown).
Control area network user interface device 35 is any device that is capable of receiving user input and displaying or indicating control network status. For example, a touch panel, a computer terminal with a monitor, keyboard and pointing device, and any device with similar functionalities may serve as control area network user interface 35. As described in detail below, with the use of control area network portal 12 of the present invention, Internet applications are also capable of functioning as control area network user interface devices without the use of custom and dedicated applications on the user's end.
Master controller 36 is generally a CPU-based controller that controls the communications among user interface 35 and Internet appliances 37-39. It is operable to receive user inputs received by user interface devices, such as commands, and instruct the appropriate Internet appliance to act according to the command. Master controller 36 may also poll each device in control area network 30 periodically to monitor its status. The system status and/or the status of each device may be sent to control area network user interface devices for display.
Internet appliances 37-39 are devices that can receive commands from master controller 36 and operate or act according to the command. Internet appliances 37-39 may include equipment that affect or monitor the various parameters of the premises. For example, Internet appliances 37-39 may include heating and air conditioning, lighting, video equipment, audio equipment, sprinklers, security cameras, infrared sensors, smoke detectors, etc. in a residential or commercial control area network. Household appliances, such as a hot tub, fireplace, microwave oven, coffee maker, etc. may also be Internet appliances coupled to the network. Internet appliances 37-39 may also be capable of providing a current status of its operational state to master controller 36, such as on/off, temperature settings, current ambient temperature, light intensity settings, volume settings, threshold settings, and predetermined alphanumeric strings reflective of operational states.
Master controller 36 is also operable to receive user input from nodes of the Internet 22 via control network portal 12. Connected to Internet 22 are content providers 25 and 26, which may also function as control area network user interface devices. Content providers 25 and 26 are typically web servers that generate and provide static and/or dynamic information and content in the form of web pages. Content provider applications executing on the web server are able to mine data stored in databases (not shown). The web pages are typically developed with hypertext markup language (HTML), and various other scripting languages and programming environments such as Microsoft® Active Server Pages (ASP), Common Gateway Interface (CGI), Internet Server Application Programming Interface (ISAPI), JAVA, ActiveX, Cold Fusion, etc. that make the web pages more dynamic and interactive.
Also connected to the Internet 22 are web browsers 23 and 24 that may also serve as control area network user interfaces. Web browsers 23 and 24 are application programs that can be used to request web pages from content providers 25 and 26 and decode the web pages. Web browser applications include NETSCAPE NAVIGATOR® and MICROSOFT INTERNET EXPLORER®, for example. Typically, a user executes a web browser application on her personal computer and accesses the World Wide Web via a dial-up connection to an Internet service provider. The Internet or World Wide Web may also be accessed via other means such as cable modems and digital subscriber lines (DSL). The user makes a request for a particular web page or particular web site by entering or specifying a uniform resource locator (URL). The URL is associated with an Internet protocol (IP) address of the specified web site. Every computer connected to the World Wide Web and Internet has a unique IP address. This address is used to route message packets to specific computers and users. Internet protocol or IP is the message transport and communications protocol of the Internet and World Wide Web.
When the web browser requests a certain URL, a connection is first established with a web server of a content provider that is addressed by the URL. A hypertext transport protocol (HTTP) request is then issued to the web server to download an HTML file. The web server receives the request and sends a web page file to the web browser, which decodes the file to display information in specified format on the screen. Web pages with dynamic content provided by gateway interfaces such as CGI and ISAPI are executable applications that are run by the web server upon user request. The executing gateway application is able to read parameter information associated with the request and generate an output in the form of an HTML file in response to the parameter values. Another way to add dynamic and interactive content to web pages uses ASP. ASP scripts are server-side executable scripts that are directly incorporated in the HTML web pages. Upon request for the page, the web server executes the ASP script in response to input parameter values and generates the web page with dynamic content.
Using control network portal 12, users may access control area networks 30 and 31 via web browsers 23 and 24 accessing web pages provided by control network portal 12 or value-added web pages provided by content providers 25 and 26. For example, a user who has a control area network deployed in her luxury residence to control various aspects of the home environment may use a web browser application to remotely monitor her home. She may change the temperature setting to decrease energy use, for example, because she will be leaving on a business trip straight from work. She may also use the surveillance cameras to visually ensure security has not been breached. She may even be able to remotely program her VCR to record certain favorite programs that will be broadcast while she is away.
An example of value-added web pages provided by content providers is the provision of an interactive version of the television programming web page, www.tvguide.com. A user may request this web page, determine available program choices, and click on a certain program. Options may be provided to enable the user to turn on the television and tune to a particular channel scheduled to broadcast the selected program or to program the VCR to record the selected program.
Another example of value-added web pages provided by content providers is the provision of a secured web page that an electric company may access to slightly raise the temperature settings of the air conditioning systems of its participating customers in anticipation of high demand brown out conditions. Yet another example is a web page that a security company may use to access, monitor and control the security, surveillance and fire protection systems of its customers.
It may be noted that control network portal 12 may be implemented by a single stand-alone system that has sufficient memory and processing power or several separate systems with distinct functions as shown in
IA server 14 includes a CGI handler 72, which communicates with CGI process 70, and an ASP handler 78, which communicates with ASP process 76. Handlers 72 and 78 are operable to provide a translation function from IP to a protocol used in the control area networks, such as PhastLink or AXLink in AMX LLC control area networks. IA server 14 is operable to spawn a software logical or virtual device that is representative of or associated with a physical device directly connected to a control area network or a content provider coupled to the Internet. Multiple software logical devices may be connected to a single control area network or content provider, if needed. Devices, whether physical or logical, are assigned a system identifier (system ID) and a unique device identification number (device ID) used to indicate the destination or origination of messages. One or more protocol converters 92 may be provided to translate from the protocol used internally in IA server, such as ICSP, to other protocols used in the control area networks, such as AxLink or PhastLink. A protocol converter is not necessary if the protocols employed in IA server 14 and a control area network 30 are the same.
By the use of software logical devices, Internet applications such as web content providers appear to IA server 14 no different than devices connected to a control area network. Therefore, it appears that Internet applications like content providers on the web are able to directly communicate with the master controllers of the control area networks to issue commands to devices in the control area networks. Similarly, Internet applications appear to be devices on the control area network that can be controlled by the master controller. The master controller is able to issue commands to the Internet applications.
Referring to
The master controller on that network receives the message and processes the message, as shown in block 160. An output channel state associated with the submit button of the user interface device is turned ON by the master controller to indicate that the data is being sent. The ON state of the output channel of the submit button is conveyed to the user interface, which may highlight the submit button or display a predetermined character string as a means of feedback to the user. In block 164, the master controller then forwards the message to the protocol converter associated with the recipient software logical device in the IA server. The protocol converter then translates the message from the sender protocol to the recipient protocol, as shown in block 166. Note that protocol conversion is not necessary or is null if the sender protocol is the same as the recipient protocol.
In block 168, the translated message is then sent or otherwise conveyed to the software logical device that represents the recipient convent provider. The recipient software logical device receives the message and stores the message content in a data structure at a specific location specified by an index value, such as a number, which corresponds to the channel number of the recipient software logical device, as shown in block 170. The stored message is accessible by specifying the index number. The software logical device then changes the state of an output channel of the same channel number to ON, as shown in block 172. It may be noted that each device, whether physical or logical, may have one or more channels, each indicative of a specific function, parameter or property. Further, each channel may have an input and an output channel state.
Periodically or at its discretion, the recipient Internet application checks the output channel states of the software logical device associated therewith, as shown in block 174. The Internet application recognizes that an output channel state is ON and therefore the data associated with that channel has been changed. In block 176, the Internet application queries the software logical device for the data by specifying the index value. In response, the software logical device sends the message to the Internet application, as shown in block 178. The Internet application receives the message and uses and acts according to the data in an appropriate manner. The software logical device turns OFF the input channel state, as shown in block 182, and turns ON the output channel state of the same index value, as shown in block 184.
The master controller recognizes a change in the input channel state of the software logical device representing the Internet application, as shown in block 186. In response, the master controller turns OFF the output channel of the user interface device, which is used to notify the user that the requested action has been completed, as shown in block 188. A change in the color or shade of the displayed button or the display of a predetermined string may be used to inform the user, as shown in block 190. The process ends in block 192.
The software logical device then stores the message content in an indexed position in a data structure, as shown in block 212. The software logical device turns ON the input channel associated with the index number, as shown in block 214. The master controller becomes aware of the input channel state change by periodically polling the channel states, as shown in block 216. The master controller may alternatively be triggered to query the channel states by some mechanism other than time. The master controller then requests the message content at the specified index number be sent to it, as shown in block 218. The software logical device then sends the message content to the master controller, which forwards the message content to the physical device in the control system, as shown in block 220. The device receives the data and acts accordingly, as shown in block 222. The master controller may also send the same data to a user interface in the control area network to update the display, as shown in block 224. The software logical device then turns OFF the input and output channels, as shown in block 226. The OFF states of the input and output channels notifies the Internet application, which may periodically poll the software logical device to determine the input and output channel states, that appropriate action has been taken in response to the entered data, as shown in block 228. The process ends in block 230.
It may be noted that the use of input and output channel states to notify the recipient that data is available and the sender that an action has been completed is merely provided herein as an example. Other means may be used for this function.
Internet 316 is coupled to an Internet appliance server 320. Internet appliance server 320 is coupled to a plurality of control area networks 322. Each control area network has one master 324 and a variety of control area network devices 326 which can include touch panels, audio/visual equipment, and the like. Control area network devices 326 are equivalent to the Internet appliances described previously.
Web servers 312 are computers having a processor, such as an INTEL or Motorola processor, and memory. Web server 312 runs a web server program operable to provide web pages to a requesting user, the requesting user typically using a web browser.
Databases 314 are operable to store information that can be used by web servers 312 to provide content that may be required by a control area network device 326. This can include information such as CD lists, television listings, sports data, stock information or any other type of information that may be used by control access network device 326.
Internet 316 is the collection of networks located across the world interconnected for user and computer communication, including the part of the Internet known as the World Wide Web. While system 310 shows web server 312 connected to the Internet 312, web servers 16 can be connected to any system of wide area networks, local area networks or Intranets.
Internet appliance server 320 is a device operable to act as a gateway between devices connected to the Internet 316 and control area network 322. Internet appliance server 320 is, in one embodiment operable to translate messages generated by web server 317 to messages useable by control area network devices 326.
In system 310, devices 326 communicate with other devices on the same control area network 322 or different control area networks 322. Devices 326 also receive messages generated outside the control area network 322 or generated by the master 324. All message sent by device 326 is routed through the master 324 on the control area network 322.
In operation, messages in the first protocol, such as Phastlink+, PL+ or ICSP developed by AMX LLC are received by a communication line 440 from a source such as a master controller 324. Message handler 444 receives the messages. Message handler 444 is responsible for receiving the message and sending the message to the appropriate port 448.
Port 448 is a control output or input on the device that is discreetly addressable. An example of a port could be an infrared generator device. There can be multiple ports in a device. Each port 448 would be numbered separately. Ports 448 can communicate with the outside world through an RS-232 interface 464, different interfaces or no interface at all.
As part of a port 448, channels 452 are provided. A channel is a part of port 448 and can take on a binary value of either on or off. In one embodiment, each port 448 can have up to 65,535 channels 452. Channels 452 are typically connected to relays 58 which can be in an on or off condition. Relay 458 is connected to a contact out 468, which allows on or off control of whatever port 448 is connected to. Channels 448 are bi-directional and can be input channels, output channels, or input/output channels.
Levels 450 are in some ways similar to channels. The main difference is that levels can take on any number of values instead of just a binary 0 or 1. Typical uses for levels include setting volume level, setting light level, etc.
Thus, the purpose of message in this protocol is to send and receive controls for devices, which are attached to control area network as well as send and receive status and routing information. For example, for the device shown above, a message could be sent to device 326, which would turn on a television, set a volume level for the television, and then perhaps scroll some information across television screen. This could be accomplished by a message sent to device 326 and interpreted by message handler 444. The message may have a command to turn the television set on and that would be sent to the channel, which would then control the relay to turn the television on. To set the volume level, the message command to set the level at a certain value is received at message handler 444. The command goes to level 450 and then to the voltage regulator 456 which in turn would then set the level by two-pin connector 462. The scrolling message might then go through the port 448 through the RS-232 port and displayed on the television connected to serial port DB-9 460.
A device can be a user interface or a controlling device, or both. User interfaces are things such as touch panels, one way wireless handheld transmitter, or custom panels. The controlling device provides the control methods for a device. For example, IR generators are controlling devices that can control a VCR, television, or other item. Each device in the system has its own unique device number, as well as port numbers and channels and levels that could be accessed.
Additionally, an RS-232 driver 514 is coupled to ICSP connection manager 530 via a PPP driver 518 coupled to a TCP/IP stack 524 and an EP port connection manager 526. ICSP connection manager 530 is coupled to ethernet driver 516 via TCP/IP stack 524 and IP port connection manager 526. RS-232 driver 514 provides connectivity to RS-232 devices and Ethernet driver 516 provides connectivity to devices attached to an Ethernet connection.
ICSP connection manager 530 is coupled to ICSP message dispatcher 532. ICSP message dispatcher 532 can send messages to different managers including a diagnostic manager 534, a device manager 536 or a configuration manager 538.
PL to ICSP protocol conversion 522 converts from phastlink (PL) to ICSP and vice versa. In some embodiments PL to ICSP protocol conversion 522 is operable to de-multiplex incoming multiple messages into multiple messages destined for ICSP connection managers and multiple outgoing messages into a single packet for PL devices. AXlink to ICSP protocol conversion 520 converts messages between devices that use the AXlink protocol to ICSP protocol and vice versa.
ICSP connection manager 530 is operable to provide routing functionality. ICSP connection manager can route to local masters, local devices, remote masters and remote devices. Routing is accomplished by first routing a message to the appropriate system master and then to the correct device. The destination will be contained in the header of the packet as discussed below.
IP port connection manager 526 is operable to manage all EP connections, except standard Internet protocols. Standard Internet protocol 528 provides for standard protocols such as HTTP, FTP, SMNP and SMTP.
ICSP message dispatcher 532 determines the category of the message, such as diagnostic message, device specific messages and configuration messages and routes them to their specific message managers. These include the diagnostic manager 534, the device manager 536, and the configuration manager 538 and any other managers.
Destination system field 676 allows for the addressing of the message to reach a specific system. A system is, in one embodiment, a complete control area network with a single master. Thus, message can be directed to one of many different control area networks. In one embodiment control system field is two bytes in size. Destination device field 678 lists the number the device that the message is being sent. The device range can be anywhere between 0 and 65,535. Destination port field 680 lists the specific port of the device that the message is destined for. In one embodiment the protocol supports up to 65,535 ports on the device.
Source system field 682 is the number of a system where the message originates. Source device field 684 lists the device that the message originated from. If the device number is 0, this indicates that the master of that control area network is the enunciator of the communication. Source port field 686 lists the port where the message originated.
An important aspect of addressing is the sequencing of messages. There are certain messages and circumstances under which messages must be delivered in the order intended. This requires that each device be guaranteed the correct order for delivery. However, while messages destined for a certain device must be delivered in the order intended, out of order messages are possible when destined for different devices.
Allowed hop count field 688 indicates how many hops can occur before the message is purged from the system. Each time a message passes through a master, the allowed hop count field is decremented by one and checked to see if it reaches zero. Once the count reaches zero, the master generates an error message indicating that the message has not reached the sender with an air. Message I.D. field 690 contains the unique identification number for a message. This message I.D. is used by low level communication algorithms to correlate in the original message with its acknowledge and response.
Message command field 692 and message data 694 represent the actual message being sent in the packet. Each packet is decoded by reading the message field 692 and performing the appropriate functions. Some commands are designed for communication between a device manager located in the master and other ones are intended for communication with the connection manager located in the master. TABLE A below lists exemplary messages that are valid between a device manager and the device or master. First column lists the command, the second column lists the value of the command, the third column lists the valid response from the device for that command, and the fourth column lists the valid response for the master of that command and the fifth column lists the description of the command. For example, command input channel OFF status is sent from a device to a master, which sends the input channel off status to the master. The value of the command sent in the command value of the command field 692 is 0x0085. Because the device is sending the message there is no response for the device. The master response is 0x0001, which is the command for acknowledge and the description of the command indicates that the input channel is in the off status. Thus, this command would be sent by a device after being queried by the master to say that its input channel is in the off status, or it can be sent unsolicited. The master would then send back an acknowledgment.
The “Value” field from TABLE A is placed in the “MC” (MessageCommand) field of the packet. Any Message Data required is placed in the variable length “MD” (MessageData) field.
The following is a more detailed description of exemplary commands.
Acknowledge
This message is generated by the master or device to confirm receipt of a message sent. The MessageID field must match the original message's MessageID and the Response bit should be set.
Message and Parameters:
Nak
This message is generated by the master when the destination system/device for the message does not exist. This message indicates that a previous message was not routable by the master. The MessageID field must match the original message's MessageID and the Response bit should be set.
Message and Parameters:
Input Channel ON Status (Device→Master)
The Input Channel ON message is generated when a button is PUSHed or Input channel is turned ON from a device/port or a master.
Message and Parameters:
Input Channel OFF Status (Device→Master)
The Input Channel OFF message is generated when a button is RELEASEd or Input channel is turned OFF from a device/port or a master.
Message and Parameters:
Output Channel ON (Master→Device)
The Output Channel ON message is generated when an Output channel is turned ON from a master.
Message and Parameters:
Output Channel ON Status (Device→Master)
The Output Channel ON Status message is generated when an Output channel is turned ON from a device/port. Note that when the master turns a channel ON, it assumes the channel is ON. Therefore, the device should not send this message in response to the channel being turned ON by the master.
Internally, this triggers an output event to occur in the Axcess language.
Message and Parameters:
Output Channel OFF (Master→Device)
The Output Channel OFF message is generated when an Output channel is turned OFF from a master.
Message and Parameters:
Output Channel OFF Status (Device→Master)
The Output Channel OFF Status message is generated when an Output channel is turned OFF from a device/port. Note that when the master turns a channel OFF, it assumes the channel is OFF. Therefore, the device should not send this message in response to the channel being turned OFF by the master.
Internally, this triggers an output event to occur in the Axcess language.
Message and Parameters:
Input/Output Channel ON Status (Device→Master)
The Input/Output Channel ON Status message is generated when an Input/Output channel is turned ON from a device/port.
Message and Parameters:
Input/Output Channel OFF Status (Device→Master)
The Input/Output Channel OFF Status message is generated when an Input/Output channel is turned OFF from a device/port.
Message and Parameters:
Feedback Channel ON
The Feedback Channel ON message is generated for diagnostic purposes only. See the Diagnostic Manager specification for more information.
Message and Parameters:
Feedback Channel OFF
The Feedback Channel OFF message is generated for diagnostic purposes only. See the Diagnostic Manager specification for more information.
Message and Parameters:
Level Value (Master→Device)
This message is used to force a level value change from the master.
Message and Parameters:
The Value Type Specifier field specifies how the following data (MD[10 . . . n]) is interpreted. The table below indicates the values of MD[9] as they correlate to data types.
ValueType Specifiers:
The LevelType command is used to query a device to determine the dynamic range supported by the device. This information is then used to generate messages appropriate to the device.
Level Value (Device→Master)
This message is used to indicate, to the master, that a device/port/level value has changed.
Message and Parameters:
String (Master→Device)
The String message is generated by the master to communicate a String. The format of a String is similar to a “C Language” string, however, the semantics are different. A String in a control system context is used to generate a “control” message. This “control” message could cause a laser disc player to begin playing a disc, display a message to the user of the system, or any number of any other uses. The string will be converted, as necessary, to any format that the device supports as determined by the StringSize message.
Message and Parameters:
String ValueType Specifiers:
String (Device→Master)
The String message is generated by a device, sent to the master, to communicate a String.
Message and Parameters:
String ValueType Specifiers:
Command (Master→Device)
The Command message is generated by the master to communicate a command string. The format of a Command is similar to a “C Language” string, however, the semantics are different. A Command in a control system context is used to generate a “control” message. This “control” message is generally intended to “command” the controlling device, not the controlled device. For example, a command to an RS232 port might enable XON/XOFF flow control. This command affected the controlling device, but not the controlled device.
Message and Parameters:
Command ValueType Specifiers:
Command (Device→Master)
The Command message is generated by a device, sent to the master, to communicate a Command string.
Message and Parameters:
Command ValueType Specifiers:
Request Level Value (Master→Master)
The Request Level Value message is generated by the master to request the level value of a level.
Message and Parameters:
Request Output Channel Status (Master→Master)
The Request Output Channel Status message is generated by the master to request the status of a single Output Channel or status of all Output Channels.
Message and Parameters:
Request Port Count (Master.→.Master)
This message requests, from the destination device, the number of ports supported by the device. The initial assumption that the master makes is that each device in the system has one port. If the device does not respond, the master assumes that it has one port.
Message and Parameters:
Port Count (Device→Master, Master→Master)
This message is the response from a master to the Request Port Count message above. It is sent by a device upon reporting if the device has more than one port.
Message and Parameters:
Request Output Channel Count (Master→Master)
This message requests from the destination device, the number of output channel supported by the specified device/port. The initial assumption that the master makes is that each device/port in the system has 256 channels.
Message and Parameters:
Output Channel Count (Device→Master, Master→Master)
This message is the response from a master to the Request Output Channel Count message above. It is sent by a device/port upon reporting if the device has more than 256 channels.
Message and Parameters:
Request Level Count (Master→Master)
This message requests, from the destination device, the number of levels supported by the specified device/port. The initial assumption that the master makes is that each device/port in the system has eight levels.
Message and Parameters:
Level Count (Device→Master,Master→Master)
This message is the response from a master to the Request Level Count message above. It is sent by a device/port upon reporting if the device has more than eight levels.
Message and Parameters:
Request String Size (Master→Master)
This message requests the number of elements per string and the string types supported by the device/port. The initial assumption that the master makes is that each device/port in the system supports 64 elements/string and only supports 8-bit character strings.
Message and Parameters:
String Size (Device→Master,Master→Master)
This message is the response from a master to the Request String Size message above. It is sent by a device/port upon reporting if the device/port supports more than 64 byte strings or more than 8-bit character strings. It returns the maximum number of elements/string the device supports and the types of strings supported.
Note that when transferring messages, the size of the message will be determined by the smaller of the maximum string size supported by the device and maximum packet size supported by the low-level bus protocol.
Message and Parameters:
String ValueType Specifiers:
Request Command Size (Master→Master)
This message requests the number of elements per command and the string types supported by the device/port. The initial assumption that the master makes is that each device/port in the system supports 64 elements/command and only supports 8-bit character arrays.
Message and Parameters:
Command Size (Device→Master)
This message is the response, from a device, to the Request Command Size message above. It is sent by a device/port upon reporting if the device/port supports more than 64 byte commands or more than 8-bit character commands. It returns the maximum number of elements/command the device supports and the types of strings supported.
Note that when transferring messages, the size of the message will be determined by the smaller of the maximum command size supported by the device and maximum packet size supported by the low-level bus protocol.
Message and Parameters:
String ValueType Specifiers:
Request Level Size (Master→Master)
This message requests a list of data types supported for the specified level. The initial assumption that the master makes is that each device/port/level only supports 8-bit unsigned values (BYTE Type 0x10).
Message and Parameters:
Level Size (Device→Master,Master→Master)
This message is the response from a master to the Request Level Size message above. It is sent by a device/port upon reporting if the device/port/level supports more BYTE (Type 0x10) levels. It returns a list of data types supported by Level.
Note that when transferring levels, the master will typecast from larger sized types to the largest type supported by the device. For example, if the users Axcess2 program sends a FLOAT to a device that supports only BYTE,CHAR, and INTEGER types, the master typecasts the FLOAT to an INTEGER before sending to the device.
Message and Parameters:
ValueType Specifiers:
Request Status (Master→Master)
This message requests, from the destination device, the status of the device or port.
Message and Parameters:
Status (Device→Master,Master→Master)
This message is the response from a master to the Request Status Code message above. It is sent by a device/port if the device/port needs to update the master of a status change.
Message and Parameters:
Request Device Info (Master→Device)
This message requests device specific information from the specified device.
Message and Parameters:
Device Info (Device→Master)
This message is the response to the Request Device Info message above.
Flag—A 16-bit bit field. Each bit indicates a unique aspect of functionality.
For each device and sub-device that contains re-programmable electronic components within the device, the following information is replied:
ObjectID—An 8-bit unique (within the device) identifier that identifies this structure of information. This is used to construct an internal device hierarchy for display to the user.
ParentID—An 8-bit value that references an existing ObjectID. If 0, then this object has no parent.
ManufactureID—A 16-bit value that uniquely identifies the manufacture of the device.
DeviceID—A 16-bit value that uniquely identifies the device type.
Serial number—A fixed length field 16 bytes long.
FWID (Firmware ID)—A 16-bit value that uniquely identifies the object code that the device requires.
Version—A NULL terminated text string that indicates the revision level of the re-programmable component.
DeviceID String—A NULL terminated text string that indicates the name or model number of the device.
Manufacturer String—A NULL terminated text string that indicates the name of the device manufacturer.
Extended Address Format—An 8-bit value that indicates the type of device specific addressing information to follow.
Extended Address Length—An 8-bit value that indicates the length of device specific addressing information to follow.
Extended Address—Extended Address as indicated by Extended Address Type and Length.
Message and Parameters:
Extended Address Type
Device Info EOT (Master→Device)
This message indicates that all data (Device Info messages) have been sent as a result of a Request Device Info message. This message indicates to the requesting device that all Device Info information has been provided.
Message and Parameters:
Request Master Status (Device→Master,Master→Master)
This message requests that the master respond with its status. Generally, Master Status message will be unsolicited, this message is included for completeness.
Message and Parameters:
Master Status (Master→Device,Master→Master)
This message is the response to the Request Master Status message above, but more commonly will be sent by the master unsolicited.
Message and Parameters:
Master Status is defined as follows:
Bits 1 & 0 are encoded as shown in the table below.
Bits 15-2: Undefined should be zero.
Diagnostic Manager
The following messages originate from or are destined for the Diagnostic Manager:
The Diagnostic Messages will be better specified during/after the Diagnostic Manager specification is complete.
Internal Diagnostic String
This message is used by tasks within the master to log/display error or diagnostic messages.
Message and Parameters:
Request Diagnostic Information
This message is used by the IDE to request that diagnostic information be sent to the requesting device. If any flag bits are set, unsolicited diagnostic messages of the specified type(s) will be sent to the device. If all bits are zero, then no diagnostic message will be sent to the device.
Message and Parameters:
Request Devices Online
This message is used by the IDE to request a list of online devices for the receiving NetLinx master. The master will respond with Device Info message(s) for each device currently online. In addition, it will generate a Port Count message for each device.
Message and Parameters:
Request Devices Online EOT
This message indicates that all requested devices from the Request Devices Online message have been sent. This message is used by the IDE to determine when all online device information has been received.
Message and Parameters:
Request Device Status
This message is used by the IDE to request the status of the specified device. The master responds with Output ON messages for each output channel that is on, Feedback ON messages for each feedback channel that is on, etc. See the Diagnostic Manager specification for more information.
Message and Parameters:
Request Device Status EOT
This message indicates that all of the Request Device Status information has been sent. This message is used by the IDE to determine when all device status information has been received.
Message and Parameters:
Request Asynchronous Notification List
This message is used by the IDE to request the current asynchronous notification list from the master. The master generates a series of Asynchronous Notification List messages, one for each entry in the list, to the requesting device.
Message and Parameters:
Asynchronous Notification List
This message is generated by the master in response to the Request Asynchronous Notification List message. For each entry in the master's list, one of these messages will be generated. If there are no entries, then the number of entries field will be zero. See the Diagnostic Manager specification for more information.
Message and Parameters:
Add/Modify Asynchronous Notification List
This message is used to add an entry into the Asynchronous Notification List or modify an existing entry. The master will generate a Completion Code (Configuration Manager message 0x0213) message indicating success or failure of this command. A special sentinel value of Device=0, Port=0, and System=0 indicates that the flags should be applied to the global filter.
Message and Parameters:
Delete Asynchronous Notification List
This message is used to delete an/all entr(y)/(ies) from the Asynchronous Notification List. The master will generate a Completion Code (Configuration Manager message 0x0213) message indicating success or failure of this command. A special sentinel value of Device=0, Port=0, and System=0 indicates that the global filter should be deleted. Another special sentinel value of Device=65535, Port=65535, and System=65535 indicates that all entries should be deleted.
Message and Parameters:
Connection Manager Messages
Table B lists commands between connection manager and devices. Again, the first column is the name of the command, the second column is the value of the command, the third column is the device response, the fourth column is the master response and the last column is the description of the command. For example, on the second row, if the blink command sent by a master to a device, the value of the command is 0x0502 and in response to that command the device says nothing nor does the master. The description of the command is given to all devices to make the LED blink. As this occurs, the master determines whether the device is online and sends back a visual indication.
Ping Request (Master→Device)
This message is sent by a master to request determine the presence of the specified device in the system.
Ping Response (Device→Master)
This message is the response to the Ping Request message above. The device responds with this message to inform the requester that the device is still on-line.
Extended Address Type
Blink (Master→Device)
The blink message is a broadcast message that is transmitted to every device periodically. The time period of the message may be dependent upon the medium in which the message will be sent.
Message and Parameters:
The time period for Blink messages is not determined at this time. Each device implementation may not require that the Blink message be periodically sent at any anticipated rate. The ideal rate will be determined based upon the quantity of bus traffic. It may, someday, even be determined dynamically.
The LED byte is a bit field. The LSB (bit 0) indicates the current status of the bus LED.
The MSB (Bit 7) is set when the master initially powers-up/on-line. In response to bit 7 being set, the receiving device should place itself in the off-line state, turn all channels off, and set all levels to zero (or prepare itself to send status updates as necessary to the master). The master shall send 3 consecutive blink messages with bit 7 set.
Request Blink (Device→Master)
This message requests from the destination master, a Blink message response. The response will not be a global response, it will be destined only to the requester.
Message and Parameters:
Dynamic Device Address (Master→Device)
This message is the response to the Request Dynamic Device Address message below. It returns a device number for “temporary” use by the requesting device.
The device can use this device number for as long as it has communication with the master. The returned device number may the one suggested by the device in the Request Dynamic Device Address message or may be different.
Message and Parameters:
Request Dynamic Device Address (Device→Master)
This message requests a device number from a master. The Newbee flag must be set in the message header.
Message and Parameters:
Extended Address Type
Pass Through
This message requests that the Connection manager redirect strings coming from the specified source device to the specified destination device. This will also prohibit strings from the source device getting sent to the interpreter until the PassThrough is disabled. This message will cause an ‘RXON’ message to be sent to the source AXLink device.
Message and Parameters:
Request Notification
This message is sent by a master to request notification of specific messages that are received from OR sent to the specified device. Typically, the notification messages are Device Manager messages (specified above).
The following message command values are not actual messages, but rather virtual “commands” to the Notification Manager that function as follows:
0xFFFF—deletes all existing notification requests for the device from this master.
Diagnostic Manager
The following messages originate from or are destined for the Diagnostic Manager:
Internal Diagnostic String
This message is used by tasks within the master to log/display error or diagnostic messages.
Message and Parameters:
Request Diagnostic Information
This message is used by the IDE to request that diagnostic information be sent to the requesting device. If any flag bits are set, unsolicited diagnostic messages of the specified type(s) will be sent to the device. If all bits are zero, then no diagnostic message will be sent to the device.
Message and Parameters:
Request Devices Online
This message is used by the IDE to request a list of online devices for the receiving NetLinx master. The master will respond with Device Info message(s) for each device currently online. In addition, it will generate a Port Count message for each device.
Message and Parameters:
Request Devices Online EOT
This message indicates that all requested devices from the Request Devices Online message have been sent. This message is used by the IDE to determine when all online device information has been received.
Message and Parameters:
Request Device Status
This message is used by the IDE to request the status of the specified device. The master responds with Output ON messages for each output channel that is on, Feedback ON messages for each feedback channel that is on, etc. See the Diagnostic Manager specification for more information.
Message and Parameters:
Request Device Status EOT
This message indicates that all of the Request Device Status information has been sent. This message is used by the IDE to determine when all device status information has been received.
Message and Parameters:
Request Asynchronous Notification List
This message is used by the IDE to request the current asynchronous notification list from the master. The master generates a series of Asynchronous Notification List messages, one for each entry in the list, to the requesting device.
Message and Parameters:
Asynchronous Notification List
This message is generated by the master in response to the Request Asynchronous Notification List message. For each entry in the master's list, one of these messages will be generated. If there are no entries, then the number of entries field will be zero. See the Diagnostic Manager specification for more information.
Message and Parameters:
Add/Modify Asynchronous Notification List
This message is used to add an entry into the Asynchronous Notification List or modify an existing entry. The master will generate a Completion Code (Configuration Manager message 0x0213) message indicating success or failure of this command. A special sentinel value of Device=0, Port=0, and System=0 indicates that the flags should be applied to the global filter.
Message and Parameters:
Delete Asynchronous Notification List
This message is used to delete an/all entr(y)/(ies) from the Asynchronous Notification List. The master will generate a Completion Code (Configuration Manager message 0x0213) message indicating success or failure of this command. A special sentinel value of Device=0, Port=0, and System=0 indicates that the global filter should be deleted. Another special sentinel value of Device=65535, Port=65535, and System=65535 indicates that all entries should be deleted.
Message and Parameters:
Configuration Manager
The following messages originate from or are destined for the Configuration Manager:
Set Device Number
Used to set the Device number of un-configured devices.
Configuration Flags
Set Identify Mode/Address
Places/removes the device into/from the Identify state. While the device is in the identify state, a press of the identify button causes the device to take on the specified Device/System. The device should respond with the Identify Mode/Address Response, report its old device as off-line, then report the new device as on-line.
Set Serial Number
Used to set the serial number of the specified device.
File Transfer
This command initiates the transfer of data for a device or master. It is intended that this transfer mechanism be common to all types of file transfers including firmware upgrades, IR data, touch panel design files.
Request IP address list
Requests for the device to respond with the list of IP addresses the device or master attempts to contact.
Request IP Address List
The response to the request above, one IP Address List message will be generated for each IP address in the list.
Add IP Address
Add a URL or IP address to the device's IP address list.
Delete IP Address
Delete one or all URLs or IP addresses from the device's IP address list.
Set DNS IP Addresses
Set the IP address(es) of the DNS servers and the domain name. A maximum of three (3) IP addresses may be specified. The search order is same as the order provided. A NULL must be provided for empty entries.
Request DNS IP Addresses
Request the IP address(es) of the DNS servers and the domain name of a device.
Get DNS IP Addresses
Get the IP address(es) of the DNS servers and the domain name.
Set Ethernet IP Address
Set the IP address, subnet mask, and gateway of the unit's Ethernet interface. A NULL must be provided for empty entries.
Request Ethernet IP Address
Request the device's Ethernet interface IP address, subnet mask, and gateway of the unit's Ethernet interface. The response to this message is the Get Ethernet IP Address message.
Get Ethernet IP Address
Get the IP address, subnet mask, and gateway of the unit's Ethernet interface.
Set Time and Date
Sets the Time and Date of the unit.
Request Current Time and Date
Request the device's current time and date. The response to this message is the Get Time and Date message.
Get Time and Date
Gets the devices time and date.
Restart
Restart the device or a subset of the device.
Completion Code
Indicates successful/unsuccessful completion of a previous message. In the case where the device settings, such as device number, are being modified, the completion code message is generate using the “old” device information before the new settings take effect.
Set Identify Mode/Address Response
Indicates that the device has received the Identify Mode/Address Enable and has had a button pressed on the device to indicate it should take on the ID Mode device and system number.
IP Port Connection Manager
The following messages originate from or are destined for the IP Port Connection Manager:
The included message protocol and its packet are designed to be sent independent of any transport protocol. Thus, this message can be sent by a TCP/IP protocol over any connection or by a lontalk protocol, which is based on the phastlink protocol developed by AMX Corporation. This protocol can also be carried over on RS232/PPP connections. This protocol supports master to master, PC to master and PC to device communication.
Communication components are usually represented using the seven-layer ISO model. Operating Systems such as Windows NT/9x provide most of these layers with a powerful object oriented abstraction at the application layer. Under Windows, at the application layer, the software developer is presented with a Berkley Sockets interface. With this interface, the developer can establish two-way communication using an object known as a “Socket”. Applications can choose to be clients or servers. Though this is a powerful abstraction, there is no facility to help the application developer formulate a protocol in terms of the packets of information sent back and forth on the wire. The services that are available deal with namespace resolution and sending and receiving of blocks of binary data. Typically, the client and server portions of the application are written to understand each other's messages on the wire. The messages consist of structures of binary information. To formulate such messages, the developer usually has to program in a low-level language such as C or C++.
The Internet has given rise to a whole new species of developers called “Web developers”. On an average, they are not low-level programmers who can code in C or C++ and instead use some combination of HTML, Java, JavaScript and VBScript. Except for the full Java language, the other languages are “scripting languages”.
They do not provide the developer with services and facilities of a full programming language.
The primary goal of the AMX Corporation dynamic messaging components invention is to make a scripting language such as VBScript or JavaScript (or even Visual Basic) capable of directly communicating on any TCP/IP network connection. This means that these dynamic messaging components have to give the script writer the ability to: (i) form binary messages and transmit them on a network connection; and (ii) receive binary messages from a network connection, understand their format and “unpack” them to extract individual fields in the message. As explained later in this document, it will be seen that apart from these two basic requirements, current communication protocols require more complex features that these components now provide.
To meet the primary goal explained above, the dynamic messaging components were chosen to be implemented using the Microsoft Component Object Model or COM. This is primarily because presently no other programming model allows a scripting language to use self-describing objects with such ease of use. COM objects are well-understood by the developer community and the model is mature and stable. However, other suitable programming models may be used if desired.
To effect the requirements enumerated above, three distinct objects or components are provided. They include a binary message descriptor/layout manager object, a message instance object that represents one network message, and a transport object that manages the buffered network transmission issues.
The message descriptor/layout manager object allows a script to define the structure of binary messages that represent packets of information sent back and forth on a network connection. The message structures are identified using unique names. Once defined, these structures can later be used to form instances of messages or define more complex structures, which contain embedded structures in them. Referring to
To further describe this message structure, two additional message structures are defined: the message header and the entire message. The entire message contains the header structure as an embedded structure within itself. The following pseudo-code shows the general format of the description:
The operations (methods) that the layout manager provides allow a script to define the individual components of a binary message. The operations generally take the form:
For example, to add the “PacketSize” element to the message, the “AddPrimitive” operation is used. The element type is specified as “LONG” meaning it is an integer 4 bytes in size. Adding elements to a message has to be done within a “BeginDefineLayout-EndDefineLayout” pair of operations. This indicates to the layout manager when a new message structure definition begins and ends. Once a message structure is defined completely, it may be used as an element type in further message definitions. In the example above, the “AddStruct” operation was used to make “Packet Header Structure” an element in the structure definition of message “Packet Type 1”. Embedding structures within structures allows for definition of very complex messages.
The example also illustrated yet another important concept. This is the ability to define variable length elements within a message structure. The element named “element 2” is of variable length. It is a byte (char) array whose length is specified within the message by the preceding element named “element 1”. Dynamically sized elements of this type are pretty common in many communication protocols.
Due to their very nature, some dynamically sized elements do not have to have an explicit element specify their size. An example of such an element type is a NULL terminated string. A NULL terminated string is a sequence of bytes in which the byte value of 0 is a special value indicating the end of the sequence. Since the end of the sequence is specified by this special value, its length does not have to be explicitly stored. The example shows that “element 3” is a NULL terminated string and the operation “AddSZString” is used to add it.
The following examples enumerate the operations (methods) provided by the layout manager.
Message Descriptor/Layout Manager Object Methods
BeginDefineLayout—starts definition of a new message (cannot be called while already defining a message).
EndDefineLayout—ends definition of a current message (cannot be called if not currently defining a message).
IsDefinedLayout—checks for existence of a message definition and returns TRUE/FALSE.
AddPrimitive—adds a primitive element to a message structure. Primitive elements form the basic entities of a binary message. Primitive elements includes characters (1 byte), 2 byte integers, 4 byte integers, floating point numbers (4 bytes) and double precision floating point numbers (8 bytes).
AddPrimitiveArray—adds an array of primitive elements to a message structure.
AddPrimitiveDynamicArray—adds a dynamic array of primitive elements to a message structure. The array does not have to be fixed in size, rather, the name of another (integer type) element is used to contain the actual length of this element inside a specific instance of this message structure. The size element has to have been already defined within the message structure. In other words, the length of this dynamic element is specified by an element within the message and that element should be stored in a position physically above the dynamic element.
AddStruct—adds a structure element to a message structure. The structure element must already have been defined.
AddStructArray—adds an array of structure elements to a message structure.
AddStructDynamicArray—adds a dynamic array of structure elements to a message structure. The same rules as that of AddPrimitiveDynamicArray applies to this method.
AddSZString—adds a NULL terminated string element to a message structure.
AddSZStringArray—adds an array of NULL terminated string elements to a message structure. The array does not have to be fixed in length, rather, the last string element of the array has to be terminated with two NULL characters rather than one NULL character.
AddPadding—adds padding of specified byte amount to a message structure after an element. This method is used to align individual elements of a structure to be on specific byte boundaries.
AddAlignmentPadding—adds padding to a message structure after an element to align to the specified alignment boundary. Byte alignments can be made to occur on 2, 4, 8 or 16 byte boundaries. This method is used to align individual elements on specific byte boundaries when the element sizes are not fixed. The message instance object of the dynamic messaging component allows a script to create an instance of a previously defined message in memory, fill the message with values for the individual fields of the message, and then with the help of transport object (which is described in the next section), transmit the message over a network connection. The message instance object also allows a script to receive an instance of a message over a network connection, unpack the message and access the values of the individual elements in the message.
The message structure previously defined will be used again to show how an instance of that message could be created in memory.
The following pseudo-code shows a typical sequence in creating the message instance:
In the pseudo-code above, a message instance object is created which is then used to set the various values for the elements within the message. The code to actually transmit the message is described below.
The first operation performed is the “CreateMessage” operation. This operation allows a script to create a message of a given type. The message type is previously defined within this (or some other) script using the message descriptor/layout manager object. The meaning of the second boolean argument (FALSE in this case) is explained below. Following the creation of the message, two operations are performed to set the lengths of the two dynamic fields within the message. The two fields are “element 2” and “element 3”. “element 2” is a dynamic array of characters and “element 3” is a NULL terminated string. After a message is created, sizes of all dynamic elements within the message have to be specified because that is how the Message Instance object knows how much memory this message will occupy. If there are no dynamic elements in the message, this step can be completely avoided.
The third step is actually setting the values of the various fields (elements) in the message. In this message, there are two parts: header and body. The various operations supported by the Message Instance object provide scripts extreme flexibility in writing values of elements into a message. In this instance, methods like “SetInt2”, “SetInt4”, “SetCharArray” and “SetSZString” are used. Also, once all dynamic elements have been explicitly sized, the Message Instance object knows what the entire size of the message is, so the “GetMessageSize” operation can be used to get the size. This operation is used in writing the message size into the “PacketSize” element of the header. The sequence of set operations has to be enclosed within a pair of “BeginSetLayout-EndSetLayout” operations so that the Message Instance knows when a message is ready to be transmitted.
Now that a complete example of a message instance has been illustrated, the following section enumerates all the operations (methods) provided by the Message Instance.
The message/layout instance object includes the following methods:
CreateMessage—creates an instance of a message, given its type. Optionally, this method can be used to transform a message of one type to another type.
SetDynamicArraySize—sets the size of a dynamic element inside a message.
SetSZStringLength—sets the length of a NULL terminated string. The string may be by itself an element in the message or could be part of a string array.
SetSZStringArraySize—sets the size of an array of strings in a message.
BeginSetLayout—notifies the message instance object that “Set” methods are about to be called which will write values to individual elements within the message.
SetChar—sets the value of a single byte (char) element.
SetInt2—sets the value of a 2-byte integer (short) element.
SetInt4—sets the value of a 4-byte integer (long) element.
SetFloat—sets the value of a floating point (4 byte) element.
SetDouble—sets the value of a double precision floating point (8 byte) element.
SetCharArray—copies an array of characters into an element.
SetSZString—copies a string into the NULL terminated string element.
EndSetLayout—notifies the Message Instance object that the message should now readied for transmission as all the individual element values have been set.
BeginGetLayout—notifies the Message Instance object that the message should be un-packaged so that individual elements can be “read” out of it.
GetChar—returns the value of a single byte (char) element.
GetInt2—returns the value of a 2-byte integer (short) element.
GetInt4—returns the value of a 4-byte integer (long) element.
GetFloat—returns the value of a floating point element.
GetDouble—returns the value of a double precision element.
GetCharArray—returns an array of chars from an char array element.
GetSZStringLength—returns the size of a NULL terminated string element in the message.
GetSZStringArraySize—returns the size of a string array in the message.
GetSZString—returns a string from the message.
EndGetLayout—notifies the Message Instance object that the script is done “reading” values out of the message.
ClearData—clears any message instance data within the object.
GetMessageSize—returns the size (in bytes) of the entire message instance.
Send—using an instance of the transport object, streams the message instance over a network connection.
Receive—using an instance of the transport object, receives a message instance from a network connection.
SetConvert—sets network to host and host to network byte swapping transformation mode. In this mode, all incoming messages are assumed to be in network format and all outgoing messages are converted to network format.
Pushback—allows for message overflow/underflow. When an incoming message is partially formed or contains more than a full message, the partial message bytes can be “pushed” back into the transport object which can be retrieved later.
Message layout and message instance creation are set forth above. The final step in network connectivity is the actual transport. Message layout and message instancing are actions that give rise to blocks of bytes in the memory of the web server (or wherever the script is being executed). To be able to communicate on a network, a live connection has to be made to be able to send and receive data. The third object inside the AMX Corporation dynamic messaging components module is a transport object implemented specifically to handle TCP/IP networks. The two previous objects do not in anyway assume what kind of a network connection they are communicating over. The transport object's interface is specified independent of the nature of the network. The transport object has a built-in asynchronous message handler that can fire scripts when messages arrive outside of a script's “Receive” method call.
Examples of the transport object methods includes:
Connect—connects to a given remote computer given its network address and end-point (port).
Close—closes an existing connection.
GetLastSocketError—returns the last error that occurred on the network connection.
SetScriptPath—Sets the path of the script that will be executed on incoming asynchronous messages.
DisableAsyncHandler—during some operations, it is desirable not to have the asynchronous message processor fire external scripts—this method allows a script to disable the asynchronous message processor, during which time all incoming messages are buffered up.
EnableAsyncHandler—enables the asynchronous message processor—from this point onward, every incoming asynchronous message will result in an external script being executed.
IsConnected—returns whether the transport object is connected to a remote computer or not.
GetHost—returns the network address of the remote computer to which the transport object is currently connected.
GetPort—returns the port on the remote computer to which the transport object is currently connected.
The sequence of operations to create and send a message instance is given in the exemplary pseudo-code below:
The dynamic messaging components are used in the communication between the ASP-based web server and the Internet appliance server. The various web pages that deal with controlling and administering the Internet appliance server use these objects to create and send TCP/IP messages to the IA server.
Although several embodiments of the present invention and their advantages have been described in detail, it should be understood that mutations, changes, substitutions, transformations, modifications, variations, and alterations can be made therein without departing from the teachings of the present invention, the spirit and scope of the invention being set forth by the appended claims.
The present application is a continuation of and claims priority to U.S. patent application Ser. No. 09/561,105, now U.S. Pat. No. 7,213,061, entitled “Internet Control System and Method,” filed in the U.S. Patent and Trademark Office on Apr. 28, 2000 and having a common inventor as the present document, which claims priority to U.S. provisional application Ser. No. 60/131,605 filed in the U.S. Patent and Trademark Office on Apr. 29, 1999. The present application is also related to U.S. patent application Ser. No. 09/561,102, now U.S. Pat. No. 6,763,040, entitled “Internet Control System Communication Protocol and Method,” filed in the U.S. Patent and Trademark Office on Apr. 28, 2000 and having a common inventor as the present document, which claims priority to U.S. provisional application Ser. No. 60/131,605 filed in the U.S. Patent and Trademark Office on Apr. 29, 1999. All of the above provisional and non-provisional patent applications are hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3597743 | Murphy et al. | Aug 1971 | A |
| 3778542 | Hanseman | Dec 1973 | A |
| 4024505 | Sperling | May 1977 | A |
| 4251858 | Cambigue et al. | Feb 1981 | A |
| 4489378 | Dixon et al. | Dec 1984 | A |
| 4503497 | Krygowski et al. | Mar 1985 | A |
| 4530069 | Desrochers | Jul 1985 | A |
| 4700230 | Pshtissky et al. | Oct 1987 | A |
| 4786847 | Daggett et al. | Nov 1988 | A |
| 4790003 | Kepley et al. | Dec 1988 | A |
| 4860193 | Bentley et al. | Aug 1989 | A |
| 4876651 | Dawson et al. | Oct 1989 | A |
| 4882747 | Williams | Nov 1989 | A |
| 4904993 | Sato | Feb 1990 | A |
| 4914527 | Asai et al. | Apr 1990 | A |
| 4953194 | Hansen et al. | Aug 1990 | A |
| 4989081 | Miyagawa et al. | Jan 1991 | A |
| 5014193 | Garner et al. | May 1991 | A |
| 5038277 | Altman et al. | Aug 1991 | A |
| 5039980 | Aggers et al. | Aug 1991 | A |
| 5051720 | Kittirutsunetorn | Sep 1991 | A |
| 5056001 | Sexton | Oct 1991 | A |
| 5072374 | Sexton et al. | Dec 1991 | A |
| 5086385 | Launey et al. | Feb 1992 | A |
| 5095480 | Fenner | Mar 1992 | A |
| 5103391 | Barrett | Apr 1992 | A |
| 5109222 | Welty | Apr 1992 | A |
| 5119479 | Arai et al. | Jun 1992 | A |
| 5144548 | Salandro | Sep 1992 | A |
| 5170466 | Rogan et al. | Dec 1992 | A |
| 5185693 | Loftis et al. | Feb 1993 | A |
| 5208810 | Park | May 1993 | A |
| 5222062 | Sharma et al. | Jun 1993 | A |
| 5226160 | Waldron et al. | Jul 1993 | A |
| 5233510 | Brueckner et al. | Aug 1993 | A |
| 5237567 | Nay et al. | Aug 1993 | A |
| 5265252 | Rawson, III et al. | Nov 1993 | A |
| 5271009 | Takano et al. | Dec 1993 | A |
| 5276630 | Baldwin et al. | Jan 1994 | A |
| 5276793 | Borgendale et al. | Jan 1994 | A |
| 5301350 | Rogan et al. | Apr 1994 | A |
| 5311451 | Barrett | May 1994 | A |
| 5317562 | Nardin et al. | May 1994 | A |
| 5347632 | Filepp et al. | Sep 1994 | A |
| 5371859 | Lennartsson | Dec 1994 | A |
| 5375248 | Lemay et al. | Dec 1994 | A |
| 5379431 | Lemon et al. | Jan 1995 | A |
| 5388213 | Oppenheimer et al. | Feb 1995 | A |
| 5410326 | Goldstein | Apr 1995 | A |
| 5428470 | Labriola, II | Jun 1995 | A |
| 5434982 | Calzi | Jul 1995 | A |
| 5440691 | Carrafiello et al. | Aug 1995 | A |
| 5444851 | Woest | Aug 1995 | A |
| 5446740 | Yien et al. | Aug 1995 | A |
| 5450359 | Sharma et al. | Sep 1995 | A |
| 5452291 | Eisenhandler et al. | Sep 1995 | A |
| 5455959 | Simmering | Oct 1995 | A |
| 5463735 | Pascucci et al. | Oct 1995 | A |
| 5467264 | Rauch et al. | Nov 1995 | A |
| 5475433 | Jeong | Dec 1995 | A |
| 5481750 | Parise et al. | Jan 1996 | A |
| 5491797 | Thompson et al. | Feb 1996 | A |
| 5491802 | Thompson et al. | Feb 1996 | A |
| 5500794 | Fujita et al. | Mar 1996 | A |
| 5510975 | Ziegler, Jr. | Apr 1996 | A |
| 5519707 | Subramanian et al. | May 1996 | A |
| 5519875 | Yokoyama et al. | May 1996 | A |
| 5528215 | Siu et al. | Jun 1996 | A |
| 5528739 | Lucas et al. | Jun 1996 | A |
| 5537142 | Fenouil | Jul 1996 | A |
| 5537663 | Belmont et al. | Jul 1996 | A |
| 5546543 | Yang et al. | Aug 1996 | A |
| 5557723 | Holt et al. | Sep 1996 | A |
| 5565855 | Knibbe | Oct 1996 | A |
| 5565908 | Ahmad | Oct 1996 | A |
| 5568367 | Park | Oct 1996 | A |
| 5568489 | Yien et al. | Oct 1996 | A |
| 5570085 | Bertsch | Oct 1996 | A |
| 5572643 | Judson | Nov 1996 | A |
| 5583994 | Rangan | Dec 1996 | A |
| 5586267 | Chatwani et al. | Dec 1996 | A |
| 5592626 | Papadimitriou et al. | Jan 1997 | A |
| 5594366 | Khong et al. | Jan 1997 | A |
| 5594889 | Colgate et al. | Jan 1997 | A |
| 5600635 | Hamaki et al. | Feb 1997 | A |
| 5621662 | Humphries et al. | Apr 1997 | A |
| 5630079 | McLaughlin | May 1997 | A |
| 5634011 | Auerbach et al. | May 1997 | A |
| 5648813 | Tanigawa et al. | Jul 1997 | A |
| 5657221 | Warman et al. | Aug 1997 | A |
| 5675756 | Benton et al. | Oct 1997 | A |
| 5678060 | Yokoyama et al. | Oct 1997 | A |
| 5687393 | Brown et al. | Nov 1997 | A |
| 5689353 | Darbee et al. | Nov 1997 | A |
| 5699532 | Barrett et al. | Dec 1997 | A |
| 5706455 | Benton et al. | Jan 1998 | A |
| 5710755 | Chen | Jan 1998 | A |
| 5720032 | Picazo, Jr. et al. | Feb 1998 | A |
| 5721878 | Ottesen et al. | Feb 1998 | A |
| 5724574 | Stratigos et al. | Mar 1998 | A |
| 5727212 | Dinallo | Mar 1998 | A |
| 5729704 | Stone et al. | Mar 1998 | A |
| 5732257 | Atkinson et al. | Mar 1998 | A |
| 5737529 | Dolin, Jr. et al. | Apr 1998 | A |
| 5737553 | Bartok | Apr 1998 | A |
| 5739648 | Ellis et al. | Apr 1998 | A |
| 5739760 | Hatakeyama | Apr 1998 | A |
| 5740231 | Cohn et al. | Apr 1998 | A |
| 5742762 | Scholl et al. | Apr 1998 | A |
| 5745669 | Hugard et al. | Apr 1998 | A |
| 5754255 | Takamori | May 1998 | A |
| 5764155 | Kertesz et al. | Jun 1998 | A |
| 5771354 | Crawford | Jun 1998 | A |
| 5772963 | Cantatore et al. | Jun 1998 | A |
| 5777624 | Munson | Jul 1998 | A |
| 5777870 | Takaku et al. | Jul 1998 | A |
| 5796411 | Cyman et al. | Aug 1998 | A |
| 5805812 | Fish et al. | Sep 1998 | A |
| 5812085 | Barraza et al. | Sep 1998 | A |
| 5812122 | Ng | Sep 1998 | A |
| 5812214 | Miller | Sep 1998 | A |
| 5812750 | Dev et al. | Sep 1998 | A |
| 5815516 | Aaker et al. | Sep 1998 | A |
| 5815703 | Copeland et al. | Sep 1998 | A |
| 5819294 | Chambers | Oct 1998 | A |
| 5831610 | Tonelli et al. | Nov 1998 | A |
| 5835126 | Lewis | Nov 1998 | A |
| 5844572 | Schott | Dec 1998 | A |
| 5848054 | Mosebrook et al. | Dec 1998 | A |
| 5857199 | Tamano et al. | Jan 1999 | A |
| 5867484 | Shaunfield | Feb 1999 | A |
| 5886894 | Rakoff | Mar 1999 | A |
| 5892924 | Lyon et al. | Apr 1999 | A |
| 5896382 | Davis et al. | Apr 1999 | A |
| 5907485 | Van Loo et al. | May 1999 | A |
| 5907837 | Ferrel et al. | May 1999 | A |
| 5909570 | Webber | Jun 1999 | A |
| 5910954 | Bronstein et al. | Jun 1999 | A |
| 5918022 | Batz et al. | Jun 1999 | A |
| 5920694 | Carleton et al. | Jul 1999 | A |
| 5922050 | Madany | Jul 1999 | A |
| 5926187 | Kim | Jul 1999 | A |
| 5933816 | Zeanah et al. | Aug 1999 | A |
| 5935003 | Stephens et al. | Aug 1999 | A |
| 5938728 | Dwork et al. | Aug 1999 | A |
| 5940387 | Humpleman | Aug 1999 | A |
| 5943064 | Hong et al. | Aug 1999 | A |
| 5949438 | Cyman et al. | Sep 1999 | A |
| 5956487 | Venkatraman et al. | Sep 1999 | A |
| 5957985 | Wong et al. | Sep 1999 | A |
| 5959536 | Chambers et al. | Sep 1999 | A |
| 5968116 | Day, II et al. | Oct 1999 | A |
| 5977989 | Lee et al. | Nov 1999 | A |
| 5982445 | Eyer et al. | Nov 1999 | A |
| 5995753 | Walker | Nov 1999 | A |
| 5996022 | Krueger et al. | Nov 1999 | A |
| 6005861 | Humpleman | Dec 1999 | A |
| 6008735 | Chiloyan et al. | Dec 1999 | A |
| 6012113 | Tuckner | Jan 2000 | A |
| 6021433 | Payne et al. | Feb 2000 | A |
| 6023762 | Dean et al. | Feb 2000 | A |
| 6029092 | Stein | Feb 2000 | A |
| 6032202 | Lea et al. | Feb 2000 | A |
| 6038668 | Chipman et al. | Mar 2000 | A |
| 6049821 | Theriault et al. | Apr 2000 | A |
| 6049828 | Dev et al. | Apr 2000 | A |
| 6052683 | Irwin | Apr 2000 | A |
| 6052750 | Lea | Apr 2000 | A |
| 6055236 | Nessett et al. | Apr 2000 | A |
| 6055368 | Kunioka | Apr 2000 | A |
| 6061602 | Meyer | May 2000 | A |
| 6061717 | Carleton et al. | May 2000 | A |
| 6065068 | Foote | May 2000 | A |
| 6075776 | Tanimoto et al. | Jun 2000 | A |
| 6078747 | Jewitt | Jun 2000 | A |
| 6078952 | Fielding et al. | Jun 2000 | A |
| 6085238 | Yuasa et al. | Jul 2000 | A |
| 6085243 | Fletcher et al. | Jul 2000 | A |
| 6088717 | Reed et al. | Jul 2000 | A |
| 6101189 | Tsuruoka | Aug 2000 | A |
| 6105055 | Pizano et al. | Aug 2000 | A |
| 6108696 | Mendhekar et al. | Aug 2000 | A |
| 6115713 | Pascucci et al. | Sep 2000 | A |
| 6118784 | Tsuchiya et al. | Sep 2000 | A |
| 6121593 | Mansbery et al. | Sep 2000 | A |
| 6128509 | Veijola et al. | Oct 2000 | A |
| 6131097 | Peurach et al. | Oct 2000 | A |
| 6133847 | Yang | Oct 2000 | A |
| 6134590 | Perlman | Oct 2000 | A |
| 6144993 | Fukunaga et al. | Nov 2000 | A |
| 6160796 | Zou et al. | Dec 2000 | A |
| 6161133 | Kikinis | Dec 2000 | A |
| 6161145 | Bainbridge et al. | Dec 2000 | A |
| 6167567 | Chiles et al. | Dec 2000 | A |
| 6175920 | Schanze | Jan 2001 | B1 |
| 6177945 | Pleyer | Jan 2001 | B1 |
| 6192282 | Smith et al. | Feb 2001 | B1 |
| 6195688 | Caldwell et al. | Feb 2001 | B1 |
| 6198479 | Humpleman et al. | Mar 2001 | B1 |
| 6199133 | Schnell | Mar 2001 | B1 |
| 6205465 | Schoening et al. | Mar 2001 | B1 |
| 6240554 | Fenouil | May 2001 | B1 |
| 6241156 | Kline et al. | Jun 2001 | B1 |
| 6247128 | Fisher et al. | Jun 2001 | B1 |
| 6259707 | Dara-Abrams et al. | Jul 2001 | B1 |
| 6260069 | Anglin | Jul 2001 | B1 |
| 6266339 | Donahue et al. | Jul 2001 | B1 |
| 6272134 | Bass et al. | Aug 2001 | B1 |
| 6272553 | Way et al. | Aug 2001 | B2 |
| 6282175 | Steele et al. | Aug 2001 | B1 |
| 6288716 | Humpleman et al. | Sep 2001 | B1 |
| 6292901 | Lys et al. | Sep 2001 | B1 |
| 6310879 | Zhou et al. | Oct 2001 | B2 |
| 6311149 | Ryan et al. | Oct 2001 | B1 |
| 6311320 | Jibbe | Oct 2001 | B1 |
| 6330238 | Ooe | Dec 2001 | B1 |
| 6338152 | Fera et al. | Jan 2002 | B1 |
| 6340977 | Lui et al. | Jan 2002 | B1 |
| 6342906 | Kumar et al. | Jan 2002 | B1 |
| 6360270 | Cherkasova et al. | Mar 2002 | B1 |
| 6363422 | Hunter et al. | Mar 2002 | B1 |
| 6374255 | Peurach et al. | Apr 2002 | B1 |
| 6415328 | Korst | Jul 2002 | B1 |
| 6434157 | Dube' et al. | Aug 2002 | B1 |
| 6434680 | Belknap et al. | Aug 2002 | B2 |
| 6437691 | Sandelman et al. | Aug 2002 | B1 |
| 6446130 | Grapes | Sep 2002 | B1 |
| 6456699 | Burg et al. | Sep 2002 | B1 |
| 6469695 | White | Oct 2002 | B1 |
| 6469987 | Rijhsinghani | Oct 2002 | B1 |
| 6477569 | Sayan et al. | Nov 2002 | B1 |
| 6484061 | Papadopoulos et al. | Nov 2002 | B2 |
| 6484149 | Jammes et al. | Nov 2002 | B1 |
| 6496927 | McGrane et al. | Dec 2002 | B1 |
| 6505146 | Blackmer | Jan 2003 | B1 |
| 6515680 | Hendricks et al. | Feb 2003 | B1 |
| 6523696 | Saito et al. | Feb 2003 | B1 |
| 6542165 | Ohkado | Apr 2003 | B1 |
| 6546405 | Gupta et al. | Apr 2003 | B2 |
| 6553418 | Collins et al. | Apr 2003 | B1 |
| 6574234 | Myer et al. | Jun 2003 | B1 |
| 6609127 | Lee et al. | Aug 2003 | B1 |
| 6615088 | Myer et al. | Sep 2003 | B1 |
| 6615285 | Schafranek et al. | Sep 2003 | B1 |
| 6657646 | Partridge et al. | Dec 2003 | B2 |
| 6680934 | Cain | Jan 2004 | B1 |
| 6697376 | Son et al. | Feb 2004 | B1 |
| 6744771 | Barber et al. | Jun 2004 | B1 |
| 6760760 | McGrane | Jul 2004 | B1 |
| 6763040 | Hite et al. | Jul 2004 | B1 |
| 6766519 | Burriss et al. | Jul 2004 | B1 |
| 6775654 | Yokoyama et al. | Aug 2004 | B1 |
| 6783040 | Batchelor | Aug 2004 | B2 |
| 6791554 | Mergard et al. | Sep 2004 | B1 |
| 6801331 | Motoyama | Oct 2004 | B1 |
| 6801529 | McGrane et al. | Oct 2004 | B1 |
| 6829368 | Meyer et al. | Dec 2004 | B2 |
| 6865596 | Barber et al. | Mar 2005 | B1 |
| 6868403 | Wiser et al. | Mar 2005 | B1 |
| 6934414 | Kondo et al. | Aug 2005 | B2 |
| 6937766 | Wilf et al. | Aug 2005 | B1 |
| 6959451 | Ramanathan | Oct 2005 | B1 |
| 7076153 | Ando et al. | Jul 2006 | B2 |
| 7213061 | Hite et al. | May 2007 | B1 |
| 7224366 | Kessler et al. | May 2007 | B2 |
| 7342584 | Kessler et al. | Mar 2008 | B2 |
| 7426702 | Partridge et al. | Sep 2008 | B2 |
| 7796641 | Wright et al. | Sep 2010 | B2 |
| 7797433 | Kennedy et al. | Sep 2010 | B2 |
| 7971151 | Nixon et al. | Jun 2011 | B2 |
| 20020013948 | Aguayo et al. | Jan 2002 | A1 |
| 20020056047 | Lehman | May 2002 | A1 |
| 20020109708 | Peurach et al. | Aug 2002 | A1 |
| 20020161828 | Edison et al. | Oct 2002 | A1 |
| 20020176601 | Rhoads | Nov 2002 | A1 |
| 20030035556 | Curtis et al. | Feb 2003 | A1 |
| 20030087629 | Juitt et al. | May 2003 | A1 |
| 20030149574 | Rudman | Aug 2003 | A1 |
| 20030163298 | Odom et al. | Aug 2003 | A1 |
| 20040034864 | Barrett et al. | Feb 2004 | A1 |
| 20040044742 | Evron et al. | Mar 2004 | A1 |
| 20040073707 | Dillon | Apr 2004 | A1 |
| 20040075694 | Partridge et al. | Apr 2004 | A1 |
| 20040085361 | Kessler et al. | May 2004 | A1 |
| 20040196255 | Cheng | Oct 2004 | A1 |
| 20050273700 | Champion et al. | Dec 2005 | A1 |
| 20060067341 | Barber et al. | Mar 2006 | A1 |
| 20070055976 | Ward et al. | Mar 2007 | A1 |
| 20070191986 | Van Breemen | Aug 2007 | A1 |
| 20070211691 | Barber et al. | Sep 2007 | A1 |
| 20080059622 | Hite et al. | Mar 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| 0449632 | Oct 1991 | EP |
| 0530973 | Mar 1993 | EP |
| 0626635 | Nov 1994 | EP |
| 0658899 | Jun 1995 | EP |
| 0743595 | Nov 1996 | EP |
| 0798894 | Oct 1997 | EP |
| 0812086 | Dec 1997 | EP |
| 0841615 | May 1998 | EP |
| 0841616 | May 1998 | EP |
| 0915469 | May 1999 | EP |
| 0939517 | Sep 1999 | EP |
| 1359482 | Nov 2003 | EP |
| 10040080 | Feb 1998 | JP |
| 10276478 | Oct 1998 | JP |
| WO-9521415 | Aug 1995 | WO |
| WO-9624231 | Aug 1996 | WO |
| WO-9718636 | May 1997 | WO |
| WO-9726587 | Jul 1997 | WO |
| WO-9744747 | Nov 1997 | WO |
| WO-9800788 | Jan 1998 | WO |
| WO-9811510 | Mar 1998 | WO |
| WO-9836335 | Aug 1998 | WO |
| WO-9836336 | Aug 1998 | WO |
| WO-9853581 | Nov 1998 | WO |
| WO-9903255 | Jan 1999 | WO |
| WO-9905584 | Feb 1999 | WO |
| WO-9924905 | May 1999 | WO |
| WO-0028403 | May 2000 | WO |
| WO-0067134 | Nov 2000 | WO |
| WO-0067135 | Nov 2000 | WO |
| WO-0067140 | Nov 2000 | WO |
| WO-0067141 | Nov 2000 | WO |
| WO-0075738 | Dec 2000 | WO |
| WO-0075767 | Dec 2000 | WO |
| WO-0075774 | Dec 2000 | WO |
| WO-0075870 | Dec 2000 | WO |
| WO-0075901 | Dec 2000 | WO |
| WO-0075903 | Dec 2000 | WO |
| WO-0076123 | Dec 2000 | WO |
| WO-0076127 | Dec 2000 | WO |
| WO-0076169 | Dec 2000 | WO |
| WO-0076174 | Dec 2000 | WO |
| WO-0076207 | Dec 2000 | WO |
| WO-0076208 | Dec 2000 | WO |
| WO-2006029391 | Mar 2006 | WO |
| WO-2007030421 | Mar 2007 | WO |
| Entry |
|---|
| 10.4″ Color LCD Tiltscreens, Oct. 1997, p. 1-2. |
| 8.5″ Touch Panels, Oct. 1995, p. 1-2. |
| Aether Software, “ScoutWebTM Web-Enabling the Mobile Enterprise,” http://www.riverbedtech.com/scoutware/index.phtml?i=sw, dated May 25, 2000; 11 pages. |
| AMX Celebrates Significant Dynamic Device Discovery Protocol Milestones at Infocomm 2006, Jun. 7, 2006, p. 1-2. |
| AMX Extends NetLinx™ With Java™ for Industry's First Dual Language Control, Sep. 10, 2004. |
| AMX Instruction Manual—Café Duet™—Integrated Development Environment for NetLinx Duet (Version 1.7)—Users Guide, Apr. 6, 2006, p. 1-2. |
| AMX Instruction Manual—Design XPress—Home Theater Version 1.2, Advanced Programmers Guide, 2003, p. 1-36. |
| AMX Instruction Manual—Design XPress—Home Theater Version 1.3, On-Site Installer's Guide, 2005, p. 1-30. |
| AMX Instruction Manual—Design XPress—Home Theater Version 1.3, Programmer's Guide, 2005, p. 109. |
| AMX Instruction Manual—Design XPress—Home Theater Version 1.3, User Interface Guide, 2005, p. 1-43. |
| AMX Instruction Manual—Design XPress—Professional Version 1.1, On-Site Installer's Guide, 2004, p. 1-16. |
| AMX Instruction Manual—Design XPress—Professional Version 1.1, Programmer's Guide, Aug. 11, 2004, p. 153. |
| AMX Instruction Manual—Design XPress—Professional Version 1.1, User-Interface Guide, 2004, p. 1-43. |
| AMX Instruction Manual—Design XPress for NetLinx Studio Version 1.5, Programmer's Guide, 2005, p. 1-68. |
| AMX Instruction Manual—Design XPress for NetLinx Studio Version 1.5, User Interface Guide, 2005, p. 1-53. |
| AMX Instruction Manual—Design XPress for NetLinx Studio, On-Site Installer's Guide, 2002, p. 1-16. |
| AMX Instruction Manual—Design XPress for NetLinx Studio, Step-by-Step User's Guide, 2002, p. 1-32. |
| AMX Instruction Manual—Design XPress for NetLinx Studio, Version 1.5, Installer's Guide, 2005, p. 1-43. |
| AMX Instruction Manual—Standard NetLinx API (SNAPI) R 1.6.0, Dec. 19, 2005, 1-190. |
| AMX Partners With Leading Manufacturers to Leverage Dynamic Device Discovery Technology, Jun. 8, 2005, p. 1-3. |
| AMX Revolutionizes Touch Panel Interaction with Launch of TakeNote™ Interactive Collaboration Tool, Jun. 9, 2004, p. 1-2. |
| AXB-TPI/3 Touch Panel Interface 3, May 1999, p. 1-2. |
| Axcess Language Tutorial—Version 2.1, Mar. 1993, p. 1-160. |
| Baier, et al., Multimedia Middleware for the Future Home, ACM, 2001, p. 48-51, entire reference. |
| Cellular Unlimited, “Cellular Unlimited Rogers AT&T..on Pagers and Wireless Web Browser,” http://www.cantel-amigo.com/blackberry.html, dated May 25, 2000, 5 pages. |
| Ceroview, “Touch Screens,” internet website article located at: www.ceroview.com/peripherals/touchspecs/touchtech.html, dated May 11, 2004, 3 pages. |
| Cisco and Infoseek Align With Panja to Bring Rich Internet Content to 2 Billion Consumer Devices, Jul. 19, 1999, p. 1-3. |
| Comer, Douglas E., “Internetworking With TCP/IP” vol. I, Principles, Protocols, and Architecture, published 1995, pp. 89-94, 203-207 and 291-292 (1995). |
| Corcoran, P.M., et al, “CEBus Network Access via the World Wide Web,” p. 236-237, IEE Transactions on Consumer Electronics, Aug. 1996. |
| Corcoran, Peter M., et al., “Browser-Style Interfaces to a Home Automation Network,” IEEE Transactions on Consumer Electronics, vol. 43 (No. 4), p. 1063-1069 (Nov. 1, 1997). |
| “Crestron SpectrumTM STX-3500C 2 Way RF Wireless Touchscreen Control Panel,” Crestron Remote Control Systems, Nov. 1997. |
| Cucos, Alexander, et al., “Real Time ATM for remote access to Home Automation and Digital Home A/V Networks,” IEEE, vol. 44 (No. 3) p. 482-489 (Jun. 17, 1998). |
| Desbonnet, Joe, et al., “System Architecture and Implementation of a CEBus/Internet Gateway,” IEEE Transactions on Consumer Electronics (New York), vol. 43 (No. 4), p. 1057-1062, XP-00076, Nov. 1, 1997. |
| Droms, R. “Dynamic Host Configuration Protocol,” RFC 1541, Oct. 1993, pp. 1-34. |
| Gagnon, F., et al., “On the Development of a Generic Interface for HLA and DIS Simulations,” IEEE 1998, pp. 52-59, XP-002138396. |
| Global Connectivity Global WebLinx, 2000, p. 1-2. |
| Global WebLinx, 1999, p. 1-2. |
| Goodman, D., Chapter 10: All About Buttons, The Complete Hypercard Handbook, Bantam Computer Books (US), pp. 161-183; Dec. 19, 1988. |
| Gopal, Inder S., et al., Dynamic Address Assignment in Broadcast Networks' IEEE Transactions on Communications, vol. COM-34, No. 1, Jan. 1986, pp. 31-37 XP000811899. |
| Halsall, F., “Data Communications, Computer Networks and Open Systems,” Addison-Wesley, p. 45-46 and 285-292 (1996)—XP-002162277. |
| Hedrick, C., “Routing Information Protocol,” RFC 1058, Jun. 1988, pp. 1-29. |
| Hill Associates, Inc., “Remote Access and TCP/IP,” Colchester, Vermont, dated Jan. 1998, pp. 616.3.1-616.3.11. |
| Instruction Manual—10.4″ Touch Panels (Firmware Version G3), Jun. 2003, p. 1-67. |
| Instruction Manual—Mio R-1 Remote Control Device, Sep. 2005, p. 1-25. |
| Instruction Manual—VPXPress—ViewPoint System Design/Programming Software Program (Version 1.1 or higher), Jul. 2001, p. 1-37. |
| International Preliminary Examination Report Dated Feb. 24, 2001 from WO 2000/67135 (International App. No. PCT/US00/11796). |
| International Preliminary Examination Report Dated Apr. 10, 2001 from WO 2000/67134 (International App. No. PCT/US00/11797). |
| International Preliminary Examination Report Dated Jun. 5, 2001 from WO 2000/67141 (International App. No. PCT/US00/11853). |
| International Preliminary Examination Report Dated Jul. 4, 2001 from WO 2000/76208 (International App. No. PCT/US00/40160). |
| International Preliminary Examination Report Dated Jul. 7, 2001 from WO 2000/67140 (International App. No. PCT/US00/11851). |
| International Preliminary Examination Report Dated Sep. 4, 2001 from WO 2000/75767 (International App. No. PCT/US00/40097). |
| International Preliminary Examination Report Mailed Sep. 13, 2001 from WO 2000/75870 (International App. No. PCT/US00/15045). |
| International Preliminary Report on Patentability Dated Mar. 13, 2007 from WO 2006/029391 (International App. No. PCT/US05/32389). |
| International Preliminary Report on Patentability Dated Mar. 17, 2009 from WO 2007/030421 (International App. No. PCT/US06/34445). |
| International Search Report Mailed Jan. 22, 2001 from WO 2000/76123 (International App. No. PCT/US00/15631). |
| International Search Report Mailed Feb. 21, 2001 from WO 2000/75774 (International App. No. PCT/US00/15528). |
| International Search Report Mailed Mar. 14, 2001 from WO 2000/75903 (International App. No. PCT/US00/15762). |
| International Search Report Mailed Mar. 14, 2001 from WO 2000/76169 (International App. No. PCT/US00/15745). |
| International Search Report Mailed Mar. 21, 2001 from WO 2000/75901 (International App. No. PCT/US00/15742). |
| International Search Report Mailed Jul. 6, 2000 from WO 2000/67140 (International App. No. PCT/US00/11851). |
| International Search Report Mailed Jul. 9, 2008 from WO 2007/030421 (International App. No. PCT/US06/34445). |
| International Search Report Mailed Jul. 28, 2000 from WO 2000/67134 (International App. No. PCT/US00/11797). |
| International Search Report Mailed Aug. 29, 2000 from WO 2000/67141 (International App. No. PCT/US00/11853). |
| International Search Report Mailed Sep. 14, 2000 from WO 2000/67135 (International App. No. PCT/US00/11796). |
| International Search Report Mailed Sep. 19, 2000 from WO 2000/76207 (International App. No. PCT/US00/15620). |
| International Search Report Mailed Sep. 26, 2000 from WO 2000/75738 (International App. No. PCT/US00/15485). |
| International Search Report Mailed Sep. 27, 2000 from WO 2000/75767 (International App. No. PCT/US00/40097). |
| International Search Report Mailed Oct. 23, 2000 from WO 2000/76127 (International App. No. PCT/US00/14908). |
| International Search Report Mailed Oct. 26, 2000 from WO 2000/76174 (International App. No. PCT/US00/14898). |
| International Search Report Mailed Nov. 14, 2006 from WO 2006/029391 (International App. No. PCT/US05/32389). |
| International Search Report Mailed Nov. 15, 2000 from WO 2000/75870 (International App. No. PCT/US00/15045). |
| International Search Report Mailed Dec. 1, 2000 from WO 2000/76208 (International App. No. PCT/US00/40160). |
| Khosia, R., “Human-centered virtual machine of problem solving agents, software agents, intelligent agents . . . ”, IEEE High-Assurance Sys. Eng. Symp., pp. 312-319, Nov. 1998. |
| Klesper, Tilo, “Der Internet-Zugriff aufs Lon/Weltweiter Zugriff auf die Sensorik and Aktorik von Automatisierungs—Projekten,” Elektronik (Germany), vol. 47 (No. 8), p. 60, 62, 64 and 66-68 (Aug. 1998), with unverified translation. |
| Landmark Designer—Instruction Manual—Preliminary, Oct. 2000, p. 1-225. |
| Landmark Designer 2.2 User Guide (Preliminary Copy), Mar. 1, 1999, p. 1-287. |
| Loucks, E. M., et al., “Implementation of a Dynamic Address Assignment Protocol in a Local Area Network” Computer networks and ISDN Sys., vol. 11, No. 2, Feb. 1986, pp. 133-146. |
| Mapquest Corporate: Copyright Information, internet website article located at: wysiwyg://89http://mapquest.c..ght&uid=udu49aj5i058jble:b51f7w5u2, dated May 25, 2000, 10 pages. |
| Microsoft WINHEC, Intel Development Tool for Implementing UPnP Devices, Microsoft Corp., 2003, p. 1-14, entire reference. |
| Mio R-1 Remote, Sep. 2005, p. 1-2. |
| NetLinx CardFrame, Control Cards, and NetModules—Instruction Manual—Preliminary May 2000, p. 1-49. |
| NetLinx Duet—Inconcert Partner Benefits, Sep. 2004. |
| NetLinx Duet, Sep. 2004. |
| NetLinx Hub Cards and Modules—Instruction Manual, Mar. 2000, p. 1-30. |
| NetLinx Master Cards and Modules—Instruction Manual—Preliminary, May 2000. |
| NetLinx Master Firmware—Version 3.0, Sep. 10, 2004, p. 1-34. |
| NetLinx Programming Language—Instruction Manual, May 2000, p. 1-184. |
| NetLinx Quick Setup Guide, Jun. 2000, p. 1-2. |
| New Products lnfocomm '98, Jun. 1998, p. 1-20. |
| Nusser, et al., The Java CAN API—a Java Gateway to Fieldbus Communication, Sep. 2000, IEEE. |
| NXI NetLinx Integrated Controller—Integrated Controllers—Instruction Manual—Preliminary, Nov. 2000, p. 1-35. |
| Omni Sky: Products and Services: Web “All the Web You Want,” http://secure.omnisky.com/products...d$LGPZLPIAAAJLTQFINQGSFEWAVBWAYIVO, dated May 25, 2000, 9 pages. |
| OSGI Alliance, “About the OSGi Service Platform—Technical Whitepaper” pamphlet dated Jul. 12, 2004, Revision 3.0, 17 pages. |
| OSGI Alliance, “OSGi Technology” internet website article located at: http://www.osgi.or/osgi—technology/index.asp?section=2, dated Aug. 6, 2004, 5 pages. |
| Palm OS®, “Web Clipping Development,” internet website article located at: http://www.palmos.com/dev/tech/webclipping/, dated May 25, 2000, 18 pages. |
| Palm, Inc., “Web Clipping, Not Web Browsing,” http://www.palm.com/products/palmvii/webclipping.html, dated May 25, 2000; 4 pages. |
| Panja Announces First Shipments of Panja 1000 Units, Jan. 24, 2000, p. 1-2. |
| Panja Ethernet Gateway, May 2000, p. 1-2. |
| Panja WebLinx Administrator Program (Version 1.0 or higher) Instruction Manual, Oct. 1999, p. 1-41. |
| Panja WebLinx Server and Internet Development Kit (IDK) (Version 1.02 or higher) Instruction Manual, Oct. 1999, p. 1-71. |
| Panja, “What is the Panja 1000?” internet website article located at: wysiwyg://33/http://www.buyapanja.com/, dated May 25, 2000, 3 pages. |
| Powered by AXlink, Oct. 1997, p. 1-16. |
| Quick Start Guide—AXB-TPI/3-Touch Panel Interface 3, Oct. 2002, p. 1-2. |
| Quick Start Guide—Mio R-1 Remote Control Device, Sep. 2005, p. 1-2. |
| Quick Start Guide, NCA-USBTN G4 USB Computer Control Stick with TakeNote, Jun. 9, 2004, p. 1-2. |
| Research in Motion Ltd., “BlackBerry Technical White Paper,” Version 1.0, dated 1998-1999, 17 pages. |
| Tanenbaum, Andrew, “Computer Networks,” Prentice Hall International (London), p. 345-403 (1996); XP-002155220. |
| TPDesign3—Touch Panel Design Program (Version 3.16), Dec. 2002, p. 1-47. |
| Tsuchiya, P.F., “Efficient Utilization of Two-Level Hierarchical Addresses,” IEEE, vol. -, Dec. 6, 1992, pp. 1016-1021, XP000357710 ISBN: 0-7803-0608-2. |
| U.S. Appl. No. 09/328,032 entitled, “Method and System for Dynamically Assigning . . . ” filed Jun. 8, 1999; Inventor: Barber et al., Abandoned. |
| U.S. Appl. No. 09/328,922 entitled “System and Method for Monitoring Video Inputs” filed Jun. 9, 1999; Inventor: Aaron Myer, Abandoned. |
| U.S. Appl. No. 09/328,923 entitled “System and Method for Integrating Multiple Video Switches into a Video Matrix” filed Jun. 9, 1999; Inventor: Aaron Myer et al., Abandoned. |
| U.S. Appl. No. 09/561,103 entitled “Dynamic Messaging System and Method” filed Apr. 28, 2000; Inventor: Thomas D. Hite et al., Abandoned. |
| U.S. Appl. No. 09/561,104 entitled “Internet Application Control System and Method” filed Apr. 28, 2000; Inventor: Thomas D. Hite, Abandoned. |
| U.S. Appl. No. 09/589,576 entitled “Method and System for Providing Access . . . ” filed Jun. 7, 2000; Inventor: Thomas D. Hite, Abandoned. |
| U.S. Appl. No. 09/696,802, entitled “System and Method of Mining World Wide Web Content” filed Oct. 25, 2000, Inventor: Subramanian et al., Abandoned. |
| U.S. Appl. No. 60/715,252 entitled “Method and Computer Program for Device Configuration” filed Sep. 7, 2005; Inventors: Robert D. Ward et al., Expired. |
| U.S. Appl. No. 60/715,330 entitled “Remote Control With Power Management” filed Sep. 7, 2005; Inventor: Michael S. Farmer et al., Expired. |
| U.S. Appl. No. 11/219,300 entitled “System and Method of Device Interface Configuration for Control System” filed Sep. 2, 2005; Inventor: Aaron L. Myer et al. |
| University of Michigan, The Device Builder Module, www.eecs.umich.edu, Jul. 1997, pp. 1-6, entire reference. |
| Viewpoint Wireless Touch Panel, Jun. 1998, p. 1-2. |
| Wang, Qunjie, et al., “EM—an environment manager for building networked virtual environments” IEEE Virtual Reality Annual Intern. Symp., pp. 11-18, Mar. 1995. |
| Written Opinion Mailed Mar. 13, 2001 from WO 2000/75870 (International App. No. PCT/US00/15045). |
| Written Opinion Mailed Jul. 9, 2008 from WO 2007/030421 (International App. No. PCT/US06/34445). |
| Written Opinion Mailed Nov. 14, 2006 from WO 2006/029391 (International App. No. PCT/US05/32389). |
| Yahoo! Terms of Service, internet website article located at: http://docs.yahoo.com/info.terms/, dated May 25, 2000, 9 pages. |
| Tindell, K., “Guaranteeing Message Latencies on Control Area Network (CAN),” Proceedings of the 1st CAN International Conference, p. 1-11, Sep. 1994. |
| Krist, et al., “Generic System for On-line Optimization & the Implementation in a Benzene Plant”, 1993, Process Development and Control Department, p. 517-524. |
| EP Supplemental Search Report and Written Opinion for EP06802916.4 mailed Jan. 6, 2012 (7 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20080313316 A1 | Dec 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60131605 | Apr 1999 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09561105 | Apr 2000 | US |
| Child | 11639097 | US |
