Systems and methods of communicating using XML

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to a network gateway device and, more particularly, to a network gateway device having an XML interface for communicating with external devices, such as billing and content servers, via XML commands and responses.

2. Description of the Related Art

In order to connect the computer of a user/subscriber to one or more networks or other online services, a variety of gateway devices have been developed. For example, one advantageous gateway device is described by U.S. patent application Ser. No. 08/816,174 and U.S. Provisional Patent Application No. 60/111,497, the contents of both of which are incorporated herein by reference. The gateway device can serve as a gateway to the Internet, an enterprise network, or other networks and/or on-line services. In addition to serving as a gateway, the gateway device can automatically adapt to the protocols and other parameters utilized by the host computer, in order that the host computer may communicate with the network in a manner that is transparent both to the user/subscriber and the network. Once the gateway device has appropriately adapted to the packets coming from the user's computer, the computer can appropriately communicate via the network, such as the network at a hotel, at home, at an airport, or any other location, in order to access other networks, such as the enterprise network, or other online services, such as the internet. In this fashion, the gateway device is capable of providing more efficient network access and network maintenance to the user/subscriber and the network operator.

Gateway devices must therefore communicate with a variety of external devices. For example, gateway devices typically communicate with billing and content servers which present customizable billing options and content pages for every subscriber of the gateway device. With respect to content, billing and content servers can present different log-on screens and pricing to a subscriber based upon one or more attributes associated with the subscriber. For example, a billing and content server can present different log-on screens and pricing based upon the location from which the subscriber accesses the network. In this regard, a subscriber in a suite may be presented with a different log-on screen and pricing options than a subscriber in a regular room or a conference room. Additionally, billing and content servers can present subscribers with customized web content based upon one or more attributes associated with the subscriber. By way of example, a billing and content server can customize the web content based upon the location from which the subscriber accesses the network. In this respect, different fire escape route maps can be presented to the subscriber based upon the room location from which the subscriber accesses the network. Additionally, guests in suites may have access to different web content than subscribers residing in a standard room.

With respect to billing, billing and content servers typically interface with a credit card authorization server in order to obtain credit card information and authorization regarding the various subscribers. Depending upon the billing arrangement of a particular subscriber, the billing and content server can communicate directly with the credit card authorization service in order to appropriately charge the subscriber's credit card account for the various services that the subscriber accesses via the gateway device. Alternatively, the billing and content server can communicate via the gateway device with a network management system, such as the property management system of a hotel, in order to appropriately charge the subscriber's account for the various services that the subscriber accesses via the gateway device.

Billing and content servers can also perform other functions, such as distributing email based upon mailing lists configured according to subscriber-specific information. Billing and content servers can also maintain and update membership records, such as frequent users clubs or frequent visitors clubs.

As briefly mentioned above, gateway devices may also communicate with a network management system, such as the property management system maintained by a hotel or the like. The functions performed by a network management system typically vary based upon the installation and application. For example, typical hotel property management systems automate operations such as room reservations, room assignments, guest check-in and check-out, and other front desk activities. Furthermore, typical hotel property management systems can maintain a log of telephone calls and telephone charges for each guest room, and can be in communication with the Internet to facilitate on-line reservations. As described in a provisional application entitled Systems And Methods For Enabling Network Gateway Devices To Communicate With Management Systems To Facilitate Subscriber Management bearing application No. 60/160,973 filed Oct. 22, 1999 and in a utility patent application entitled Systems and Methods for Integrating A Network Gateway Device with Management Systems filed concurrently herewith, gateway devices oftentimes communicate with network management systems, such as in instances in which the subscriber's access to various networks or on-line services is to be charged to their account that is administered by the network management system. The contents of these applications are also incorporated herein by reference.

Upon requesting access to a particular computer system or on-line service, the gateway device typically determines if the subscriber is entitled to access the computer system, the level of access and/or the type of services to which the subscriber is entitled according to an Authentication, Authorization, and Accounting (AAA) procedure that is described by U.S. patent application Ser. No. 09/458,602 entitled Systems and Methods for Authorizing, Authenticating and Accounting Users Having Transparent Computer Access to a Network Using a Gateway Device filed Dec. 8, 1999, and a patent application entitled Systems and Methods for Providing Dynamic Network Authorization, Authentication and Accounting filed concurrently herewith, the contents of each of which are incorporated herein by reference. An AAA server, which is a database of subscriber records, may be remote to the gateway device or the AAA database may be incorporated into the physical embodiment housing the gateway device. As such, in instances in which the AAA server is remote to the gateway device, the gateway device must also frequently communicate with the AAA server.

In addition to the external devices described above with which the gateway device frequently communicates, gateway devices may also communicate with a wide variety of other external devices depending upon the application. Unfortunately, communications with any of these external devices may be limited due to the particular format in which the external devices are designed to transmit and receive information. Since the external devices are typically designed by a number of different vendors, each of which may prefer a different format for communications, this problem is compounded by the lack of uniformity in the format with which the external devices communicate. In this regard, one external device may be designed to communicate according to one format, while another external device may be required to communicate according to another format. Since the subscriber gateway may be required to communicate with a variety of different external devices, the gateway device would seemingly have to communicate with each external device according to the particular format that is acceptable to the external device. This requirement can quickly prove cumbersome to the design, implementation and efficient operation of a gateway device since it will be forced to communicate according to a number of different formats. While this requirement is a current concern for the efficient utilization of gateway devices that must communicate with multiple external devices, this concern is expected to grow as the variety of applications in which gateway devices are employed increases and the number of different types of external devices with which the gateway device must communicate also grows.

SUMMARY OF THE INVENTION

An embodiment is a method of providing services to users. The method may be performed at a network system. The system provides a subscriber computer with access to at least one network. The system receives an XML command at the network system from a service provider system. The system parses the XML command to determine a type of operation requested by the service provider system and to determine a user associated with the XML command. The system translates at least a portion of the XML command to produce data in a specialized data format configured to be compatible with a protocol associated with a service usage accounting system. The system transmits the data in the specialized data format to the service usage accounting system, the data in the specialized data format configured to authorize and bill an account associated with the user. The system receives an authorization result from the service usage accounting system. The system translates the authorization result to produce an XML response indicating that the XML command was received and processed appropriately. The system transmits the XML response from the network system to the service provider system. The XML response comprises a confirmation identifier based on the authorization result.

In an embodiment, the protocol associated with the service usage accounting system includes a telephone number, and translating at least a portion of the XML command to produce data in the specialized data format comprises including descriptive data in the place of the telephone number.

In an embodiment, the XML command comprises an identifier of a hotel room number associated with the user, and the data in the specialized data format comprises an identifier of the hotel room number included in the XML command.

In an embodiment, communicating with the service usage accounting system comprises transmitting a second XML command to the service usage accounting system.

An embodiment is a computing system configured to manage services provided to users. The computing system includes one or more communications interfaces configured to communicate with a guest service and with an accounting system. The computing system includes a subscriber interface configured to provide a subscriber computer with access to at least one network and to adapt to the subscriber computer to facilitate communications between the subscriber computer and the at least one network. The computing system includes an XML processing module, executed on at least one processor. The XML processing module receives an XML command from the guest service, and parses the XML command to determine a type of operation requested by the guest service and to determine a user associated with the XML command. XML processing module transmits data, in a format specific to the accounting system, to the accounting system to authorize and bill an account associated with the user in accordance with data in the XML command. The XML processing module receives an authorization result from the accounting system, and transmits an XML response to the guest service. The XML response comprises a confirmation identifier based on the authorization result.

In an embodiment, communicating with the accounting system comprises transmitting a second XML command to the accounting system.

In an embodiment, the XML command includes data representing a payment amount and a room number.

In an embodiment, the format specific to the accounting system is a call accounting record format.

In an embodiment, the XML processing module is further configured to generate data in a plurality of formats each specific to a type of accounting system, to thereby enable communication with the plurality of types of accounting systems.

In an embodiment, the XML command comprises an identifier of a hotel room number associated with the user, and wherein the data in the format specific to the accounting system comprises an identifier of a hotel room number based on the hotel room number included in the XML command.

An embodiment is a non-transitory computer-readable medium, comprising instructions configured to cause a computer processor to perform operations such as the following. The processor parses a first XML command received from a first server, to determine a type of operation requested by the first server and to determine a user associated with the XML comm. The processor translates at least a portion of the XML command to produce a command configured to be interoperable with a protocol associated with a second server. The command is different from the XML command. The command comprises an identifier of the user associated with the XML command and further comprising billing information. The processor transmits the command to the second server. The processor receives an authorization result from the second server. The processor generates an XML response based on the received authorization result. The XML response indicates that the XML command was received and processed appropriately. The processor transmits the XML response to the first server.

In an embodiment, the command is configured to appear to originate from a Private Branch Telephone System (PBX).

In an embodiment, the protocol associated with the second server requires a telephone number record, and the command comprises a descriptive record in the place of a telephone number record.

In an embodiment, the computer-readable medium also includes instructions configured to cause the computer processor to produce commands specific to a plurality of protocols, to thereby enable communication with a plurality of types of servers.

In an embodiment, determining the user associated with the XML command comprises determining a MAC address associated with the XML command and identifying, in an authorization database, a user associated with the MAC address.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a computer system that includes a gateway device for facilitating communications between one or more computers and various other networks or on-line services in a manner that is transparent to both the user/subscribers and the network administrators and internet service providers.

FIG. 2 is a block diagram illustrating the format and protocol of messages transmitted to and from a gateway device according to one embodiment of the present invention, including messages transmitted between the gateway device and a billing and content server.

FIG. 3 is a block diagram illustrating an XML interface of a gateway device according to one embodiment of the present invention, as well as the various devices with which the XML interface communicates.

FIG. 4 is a stack representation of the XML interface of FIG. 3 as well as the various devices with which the XML interface communicates so as to illustrate the relative hierarchy between the respective devices.

FIG. 5 is a block diagram of a computer system that includes a gateway device for automatically configuring one or more computers to communicate via the gateway device with other networks or other online services, according to one embodiment of the present invention.

FIG. 6 shows a block diagram of the computer system of FIG. 5, implemented in a hotel computer system, according to one embodiment of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

According to the present invention, a gateway device and associated method are therefore provided that facilitate communications with external devices by utilizing a uniform communications format. As such, the gateway device is not required to communicate with each external device according to a unique format defined by the respective external device. Accordingly, the gateway device and associated method of the present invention improve communications between the subscriber computer, gateway device and various external devices, such as billing and content servers, property management systems, external AAA servers and the like.

According to one aspect of the present invention, a gateway device is provided that includes a subscriber interface for adapting to a subscriber computer that is connected to the gateway device. The subscriber interface facilitates communications between the subscriber computer and at least one network or on-line service without requiring the subscriber computer to be reconfigured and, in particular, without requiring the subscriber computer to support XML commands and responses. According to the present invention, the gateway device also includes an XML interface for communicating with an external device via a series of XML commands and responses. The XML commands and responses can relate to a variety of matters, including various subscriber management matters.

Typically, the XML interface includes a parser front end, a parser section and a building section for appropriately handling XML commands that are received by the gateway device and for sending appropriate responses. The parser front end determines the type of operation requested by the external device. The parser section is responsive to the parser front and organizes elements parsed from either an XML command or an XML response. Once parsed, the XML command is executed. Typically, the parser section passes at least some of the elements to a requested application. Prior to passing the elements to a requested application, however, the parser section typically nests the elements to be passed within an application programming interface (API) wrapper. The building section prepares responses to requests received by the gateway device. Typically, the building section assembles results returned by requested application into an XML response. The gateway device of the present invention can also include an internal web server for communicating with both the XML interface and the internet to thereby facilitate XML-based communications between the gateway device and external devices connected to the internet. As such, the gateway device supports communications involving the subscriber computer and the external devices without ever requiring the subscriber computer to support XML commands and responses.

The present invention also provides a method for communicating between the gateway device and external device via the internet. According to this aspect of the present invention, an XML command is initially received at the gateway device from the external device, such as the billing and content server. The XML command is then parsed, and the parsed XML command is executed, such as by being passed to a respective application program, such as the AAA server for performing the requested function, such as a subscriber management function. Prior to passing the parsed XML command to the respective application program, however, the elements to be passed to the requested application are preferably nested within an API wrapper. Upon completion of the requested function, the application program issues a response that is received by the gateway device and that is then included within an XML response transmitted from the gateway device to the external device.

As such, the gateway device and associated method of the present invention facilitate communications between the subscriber computer, the gateway device and a variety of external devices, such as external billing and content servers, property management systems and external AAA servers. In this regard, the gateway device can communicate with each of these various external devices in a uniform manner via a series of XML commands and responses, thereby dramatically reducing, if not eliminating, the instances in which the gateway device would have to communicate with an external device according to the unique format established by the external device. As a result, the design, implementation and operation of the gateway device should be considerably simplified. However, the gateway device and associated method of the present invention permit the subscriber computer to enjoy the benefits of the common XML command and response format without ever having to be reconfigured to support XML.

The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.

Referring now to FIG. 1, there is shown in block diagram form a computer system 10 including a plurality of computers 14 that can communicate with one or more online services 22 or networks via a gateway device 12 that provides the interface between the computers and the various networks 20 or online services. One embodiment of such a gateway device has been described in U.S. patent application Ser. No. 08/816,174 and U.S. Provisional Application No. 60/111,497 (collectively referred to herein as the Gateway Device Applications), the contents of which have been incorporated herein by reference. Briefly, the gateway device facilitates transparent computer access to the online services or networks, such that the computers can access any networks via the gateway device regardless of their network configurations. The gateway device includes a subscriber interface that adapts to the computer of a user to facilitate communication between the computer and a network or other online service without requiring the computer to be reconfigured. In this regard, the subscriber interface of the gateway device has the ability to recognize computers attempting to access a network, the location of computers attempting to access a network, the identity of users attempting to gain network access, and additional attributes, as is discussed in the Gateway Device Applications.

As illustrated in FIG. 1, the computer system 10 also includes an access concentrator 16 positioned between the computers 14 and the gateway device 12 for multiplexing the signals received from the plurality of computers onto a link to the gateway device. Depending upon the medium by which the computers 14 are connected to the access concentrator, the access concentrator 16 can be configured in different manners. For example, the access concentrator can be a digital subscriber line access multiplexer (DSLAM) for signals transmitted via regular telephone lines, a cable head end (a Cable Modem Termination Shelf (CMTS)) for signals transmitted via coaxial cables, a wireless access point (WAP) for signals transmitted via a wireless network, a switch or the like.

The computer system 10 further includes one or more routers 18 and/or servers (not shown in FIG. 1) to control or direct traffic to and from a plurality of computer networks 20 or other online services 22. While the computer system is depicted to have a single router, the computer system can have a plurality of routers, switches, bridges, or the like that are arranged in some hierarchical fashion in order to appropriately route traffic to and from the various networks or online services. In this regard, the gateway device 12 typically establishes a link with one or more routers. The routers, in turn, establish links with the servers of the networks or online services, based upon the user's selection. It will be appreciated by one of ordinary skill in the art that one or more devices illustrated in FIG. 1 may be combinable. For example, although not shown, the router may be located entirely within the gateway device. Furthermore, additional elements may be included in the computer system, such as elements disclosed in the Gateway Device Application, or network elements known to those of ordinary skill in the art.

As described above, gateway devices 14 must typically communicate with a variety of external devices. For example, gateway devices typically communicate with billing and content servers 26 as depicted in FIGS. 1 and 2. As also described above, hilling and content servers present customized billing options and content pages for every subscriber of a gateway device. As such, gateway devices must communicate on a frequent basis with the billing and content server.

The gateway device 12 may also communicate with a management system 28, such as the property management system of a hotel or the like. In this regard, FIG. 2 shows a block diagram of the computer system of FIG. 1, integrated with a hotel computer system, according to one embodiment of the present invention. It will be appreciated by those of skill in the art that the embodiment shown in FIG. 2 is for illustrative purposes, and that the computer system may be integrated with virtually any network or network management system, such as computer networks established in corporate offices, airports, arenas, apartment complexes, office buildings or the like. As a result, the embodiment shown in FIG. 2 is for illustrative purposes only, and is not intended to limit the scope of the present invention.

While the functions performed by network management systems 28 vary based upon the installation and the application, typical hotel property management systems automate operations such as room reservations, room assignments, guest check-in and check-out and other front desk activities as described above. In addition, typical hotel property management systems can maintain a log of telephone calls and telephone charges for application to the bill for each guest room. Accordingly, the gateway device 12 of the present invention can communicate with a property management system in order to place charges for the various services that a subscriber accessed via the gateway device upon the appropriate bill that is maintained by the property management system.

Moreover, while the AAA functionality is typically physically embodied within the gateway device 12, the gateway device can be configured to communicate with external AAA servers in order to authenticate a subscriber, to obtain authorization for the services requested by the subscriber and to appropriately account for their usage. In addition, gateway devices may communicate with a wide variety of other external devices, particularly as gateway devices are deployed in new applications or installations.

In order to avoid the overhead associated with communicating with each of these external devices according to the unique format in which the external device is designed to communicate, the gateway device 12 of the present invention communicates with the external devices with a series of commands and responses formatted according to the extensible markup language (XML). As known to those skilled in the art, XML is defined as an application profile of the standard generalized markup language (SGML) that is defined by ISO 8879. While SGML has been the standard, vendor-independent technique to maintain repositories of structured documentation for more than a decade, SGML is not well suited to serving documents over the world wide web. While XML is designed to enable the use of SGML on the world wide web, XML is not a single, predefined markup language. Instead, XML allows the system designer to design their own markup language. In this regard, a predefined markup language, such as hypertext markup language (HTML), defines one manner in which to describe information in one specific class of documents. In contrast, XML allows the system designer to define its own customized markup languages for different classes of documents. As such, XML specifies neither semantics nor a tag set. However, XML provides a facility to define tags and the structural relationships between them. See XML specification 1.0 for further details regarding XML.

XML has conventionally been utilized to facilitate communications between servers, such as for billing purposes, and not to facilitate communications with a user, either directly with a user's computer 14 or through an intermediary such as a gateway device 12. As such, computers are not generally configured to communicate in or to support XML. In order to provide a user with the advantages of XML including the ability to communicate in a common language with a wide variety of network devices without requiring that each computer be reconfigured to support XML, the gateway device 12 of the present invention serves as a proxy for the user's computer and utilizes XML to communicate with a variety of external devices, including the billing and content server 26 and the property management system 28. In addition, in instances in which the AAA functionality resides in an external AAA server, the gateway device can also communicate with the external AAA server via XML. In particular, the gateway device is designed to communicate with the network devices according to a set of XML commands and XML responses, thereby affording the user's computer the advantages offered by XML without requiring the user's computer to be reconfigured to support XML. Since the XML format is not specific to any particular external device, the gateway device can advantageously communicate with a variety of external devices via a common format, i.e., XML, and need not format messages differently based upon the format with which the external device is otherwise designed to communicate.

For example, a user can submit a request to purchase a product from an online provider. According to the present invention and as described in the following examples, the gateway device 12 can then communicate in a common XML format with various network devices, including billing and content servers, to authenticate and authorize the user, to order the product and to account for the user's payment for the product, without ever requiring the user's computer 14 to support XML.

As depicted in FIG. 3, the gateway device 12 typically includes an internal web server 30 that processes HTTP streams that are received from external devices. In instances in which the external device and the gateway device will communicate via the XML protocol, the HTTP string will have XML as the content type, while the content itself will consist of tags, attributes and data. As known to those skilled in the art, tags serve as field identifiers and attributes contain the values of input parameters that are used as record keys or search arguments, i.e., a MAC address. In addition, data elements are values that are to be stored in the tables and authorization files of the gateway device. Data is also returned in response streams sent by the gateway device to the external devices.

In order to handle XML commands that are received from an external device, the gateway device 12 includes an XML interface, also known as an XML parser 32, that is typically comprised of software, that is compliant with the world wide web consortium (W3C) standards to validate the XML command strings and the attributes and data derived from an XML query string. As depicted in FIG. 3, an XML interface typically includes a parser front end 34 that is also typically comprised of software and that invokes the core of a parser and determines the type of operation being requested. For example, in one common embodiment, the gateway device will receive an XML command from the billing and content server 26 requesting a specific AAA operation. As such, the following description of the XML interface as well as accompanying FIGS. 3 and 4 will be in terms of XML commands from the billing and content server requesting an AAA operation. However, the XML interface can facilitate XML-based communications between a wide variety of other devices without departing from the spirit and scope of the present invention. In this regard, the only requirement is that the external device has an XML interface, i.e., an XML parser, and be adapted to support the same XML command protocol as the gateway device. One example of an XML protocol for communications between a gateway device and a billing and content server is provided below, although other XML command protocols can be established without departing from the spirit and scope of the present invention.

The XML interface 32 of the gateway device 12 also includes a parser section 36, typically comprised of software, to handle elements as they are parsed from the XML stream. In this regard, parsed elements are organized into separate parameters that are passed to the requested application, such as the AAA server, via an appropriate application program interface (API). As shown in FIG. 3, the sets of parameters that are to be passed to the requested application are typically nested inside or wrapped within a record structure having an appropriate protocol as indicated by block 38 designated as the API “wrapper”, that also provides any necessary translation of data elements, e.g. those that need to be converted from string format to some numeric format for internal processing reasons. Once properly wrapped, the sets of parameters are passed via the appropriate API 40 to the requested application, such as the AAA 42. The requested application then responds to the request and provides the requested data via the API to the XML interface of the gateway device.

The gateway device 12 therefore also includes a building section 44 that is also comprised of software and that prepares responses to requests received by the gateway device. In this regard, the building section of the XML interface 32 assembles the results returned by the requested application into a new XML string that will be part of the HTTP response stream returned to the external device via a component such as the aforementioned go-ahead server. With respect to a HTTP response stream sent back to a billing and content server 26 via the world wide web, the HTTP response stream is typically nested inside a TCP/IP packet in order to be appropriately transmitted and received by the billing and content server. See, for example, FIG. 2 that depicts the relative protocols and formats for signals transmitted between different elements of the overall computer system 10. However, other protocols can be utilized without departing from the spirit and scope of the present invention.

A response that is returned by the gateway device 12 can be one of two types. First, a standard “OK” response can be returned that typically includes the data, if any, requested by the external device. Alternatively, an error response can be returned that typically consists of a numeric error code and a textual description of the error. In either instance, the XML interface 32 generally creates a standard header consisting of the status, such as “OK” or “ERROR”, the ID of the gateway device and the gateway device's IP address. This response is then placed onto the world wide web by the internal web server 30 of the gateway device for delivery to the external device.

While the XML interface 32 of the gateway device 12 of the present invention will be primarily described hereinafter in conjunction with XML commands received by the gateway device from an external device, followed by XML responses sent by the gateway device to the external device, the gateway device of the present invention can be constructed so as to initiate XML-based communications by issuing XML commands to various external devices and awaiting appropriate responses. In addition, while the gateway device including an XML interface will primarily be described in conjunction with communications involving an external billing and content server 26 that requests information from the AAA server; the gateway device can establish XML-based communications with other external devices, such as a property management system 28 or, in instances in which the AAA server is external to the gateway device, with the AAA server itself. In any of these instances, the gateway device is able to communicate with the external device or server according to a common protocol, i.e., XML, without having to communicate with each external device in the format unique to the respective external device. As such, the only requirement of the external device is that the external device has an XML interface and be adapted to support the same XML command protocol as the gateway device.

While various XML command protocols can be established depending upon the external device and the nature of the communication between the external device and the gateway device 12, one command protocol established between an external billing and content server 26 and a gateway device is hereinafter provided by way of example and not by way of limitation. In this example, the billing and content server sends XML commands to the gateway device which, in turn, responds to the billing and content server. In one example, the XML commands transmitted by the billing and content server to the gateway device are sent using an HTTP form POST in which the information is placed in packets sent after the HTTP header. In this example, the command text will generally follow the following format:

<USG COMMAND=“(command)” [(attr)=“(attr_data)”]>

<(tag_n) [tag_n_attr = “(tag_n_attr_data)”]>(data_n)</(tag_n)>

</USG>

where: (command) is a gateway device command;

(attr) is an optional attribute associated with a command;

(attr_data) is the data associated with the optional attribute tag;

(tag_n) is a data name tag used for specifying command parameter names;

(tag_n_attr) is an optional attribute name tag;

(tag_n_attr_data) is optional attribute data, and

(data_n) is the data associated with a data name tag.

In addition, the typical XML response from the gateway device 12 to a billing and content server 28 following receipt of an XML command from the billing and content server is typically formatted as follows:

HTTP/1.1 200 OK
(specifies request understood)

Server: UI 3A4B6D
(use the gateway device ID as the

server name)

Date: Fri, 23 Jul 1999 00:09:55
(current date/time)

GMT

Content-Type: text/xml
(specifies XML content)

Last-Modified: Fri, 23 Jul
(current date/time)

1999 00:09:55 GMT

Content-Length: 560
(size of message body in characters)

(this must be a blank line)

(series of XML tag/data pairs)

(end of message body)

In this regard, while the series of XML tag/data pairs referenced in the above exemplary XML response format will depend upon the particular command as described below, one series of XML tag/data pairs typically follow the following format:

<USG RESULT=“(RESULTCODE)” ID=“(UI)”

IP=“(USG_IP_ADDR)”>

[<ERROR_NUM>(error number)</ERROR_NUM>]

[<ERROR_DESC>(error description)</ERROR_DESC>]

<(tag_n) [tag_n_attr = “tag_n_attr_data”]>(data_n)</(tag_n)>

</USG>

where: (RESULTCODE) is either “OK” or “ERROR”;

(UI) is the gateway device ID;

(USG_IP_ADDR) is the IP address of the gateway device;

(tag_n) is a data name tag;

(tag_n_attr) is an optional attribute name tag;

(tag_n_attr_data) is optional attribute data; and

(data_n) is the data associated with a data name tag.

As indicated, all XML responses returned following an XML command will contain error information. In this regard, the attribute RESULT will be assigned either “OK” or “ERROR”. If an error did occur, two additional tag/data pairs will be added as part of the response form, namely, error_num and error_desc. The error number data will contain an integer number representing the error that occurred, while the error description data will be a readable textual description of the error.

While a variety of commands and responses can be established based upon the foregoing, XML command and response formats, examples of several particular commands that could be issued by a billing and content server 26 to the gateway device 12, requesting either room administration or user administration, are provided below. The resulting responses provided by the gateway device are also provided. However, the following commands and responses are for purposes of illustration only and should not be construed as limitations of the type of XML commands and responses that can be formulated.

Regarding room administration, the billing and content server 28 can issue an XML command to set the access mode of a specified room that includes the following command, command attribute, command attribute data, and tag/data pair:

Command:
“ROOM_SET_ACCESS”

Command attr:
“ROOM_NUMBER”

Command attr_data:
Room number (8 char. max string)

tag_1:
“ACCESS_MODE”

data_1:
“ROOM_OPEN,” “ROOM_CHARGE,” or

“ROOM_BLOCK”

In response, the gateway device 12 would typically issue a standard XML response indicating that the command was received and implemented appropriately or that an error occurred.

Also with respect to room administration, a billing and content server 26 can issue a command querying the gateway device 12 regarding the access mode of a specified room. In this regard, the query room status command could include the following command, command attribute, and command attribute data:

Command:
“ROOM_QUERY_ACCESS”

Command attr:
“ROOM_NUMBER”

Command attr_data:
Room number (8 char. max string)

In response, the gateway device 12 could return a standard response, including the following tags and data in which the room access mode is selected from one of “room_open”, “room_charge” or the “room_block”:

tag_1 =
“ROOM_NUMBER”

data_1 =
(room number)

tag_2 =
“ACCESS_MODE”

data_2 =
(room access mode)

With respect to user administration, the billing and content server 26 can issue a command to add or update a user that has been authorized for access and should now be added to the MAC or some other type of authorization table, that is, a memory table maintained by the gateway device 12. In this regard, one example of an XML command to add/update a user typically includes the following command, command attribute, command attribute data, and tag/data pair:

Command:
“USER_ADD”

Command attr:
“MAC_ADDR”

Command attr_data:
user MAC address (string)

tag_1:
“USER NAME”

data_1:
(user name)

tag_2:
“PASSWORD”

tag_2_attr:
“ENCRYPT”

tag_2_attr_data:
“TRUE” or “FALSE”

data_2:
(user password)

tag_3:
“EXPIRY_TIME”

tag_3_attr:
“UNITS”

tag_3_attr_data:
“SECONDS,” “HOURS,” “DAYS”

data_3:
(number of expiry units)

tag_4:
“ROOM_NUMBER”

data_4:
(user's room number)

tag_5:
“PAYMENT_METHOD”

data_5:
“RADIUS,” “PMS,” “CREDIT_CARD,” or

“ROOM_OPEN”

tag_6:
“CONFIRMATION”

data_6:
(confirmation code/ID)

tag_7:
“PAYMENT”

data_7:
(amount paid for access)

In response, the gateway device 12 would typically issue a standard XML response indicating that the command was received and processed appropriately or that an error occurred.

The billing and content server 26 can also issue an XML command to delete a user who is identified by a Subscriber Identifier, such as a MAC address, a user name or an IP address. In this regard, one example of a delete user command typically includes the following command, tag and data:

Command:
“USER_DELETE”

tag_1:
“USER”

tag_1_attr:
“ID_TYPE”

tag_1_attr_data:
“MAC_ADDR,” “USER_NAME” or “IP_ADDR”

data_1:
if ID_TYPE=“MAC_ADDR” then (user MAC

address)

if ID_TYPE=“USER_NAME” then (user name)

if ID_TYPE=“IP_ADDR” then (user IP address)

In response, the gateway device 12 would typically issue a standard XML response indicating that the command was received and processed appropriately or that an error occurred.

The billing and content server 26 can also query the gateway device 12 for the current user data by issuing an XML command that, in one, example, includes the following command, tag and data:

Command:
“USER_QUERY”

tag_1:
“USER”

tag_1_attr:
“ID_TYPE”

tag_1_attr_data:
“MAC_ADDR,” “USER_NAME” or “IP_ADDR”

data_1:
if ID_TYPE=“MAC_ADDR” then (user MAC

address)

if ID_TYPE=“USER_NAME” then (user name)

if ID_TYPE=“IP_ADDR” then (user IP address)

In response, the gateway device 12 typically uses a standard XML response with the following tags/data pairs:

tag_1 =
“MAC_ADDR”

data_1 =
user MAC address (string)

tag_2 =
“USER NAME”

data_2 =
(user name)

tag_3 =
“IP_ADDR”

date_3 =
(user IP address)

tag_4 =
“PASSWORD”

data_4 =
(user password)

tag_5 =
“EXPIRY_TIME”

tag_5_attr =
“UNITS”

tag_5_attr_data =
“SECONDS,” “HOURS,” “DAYS”

data_5 =
(number of expiry units)

tag_6 =
“ROOM_NUMBER”

data_6 =
(user's room number)

tag_7 =
“PAYMENT_METHOD”

data_7 =
“RADIUS,” “PMS,” “CREDIT_CARD,” or

“ROOM”

tag_8 =
“DATA_VOLUME”

data_8 =
(data transferred by user in Kbytes)

The billing and content server 26 can also issue a command to check a user's identity, as specified by a MAC address, as one example, against the authorization tables maintained by the gateway device 12 or the associated AAA server. If the user is found either in the MAC or room authorization table of this example, VALID_USER is returned along with the user authorization method, such as RADIUS, property management system (PMS) (in instances in which the fee is to be billed to the user's account), credit card or room (in instances in which the room is opened up for free internet access). If the user was not found in the MAC or room authorization tables, INVALID_USER will be returned. In any event, the XML command issued by the billing and content server typically includes the following command, command attribute and command attribute data:

Command:
“USER_AUTHORIZE”

Command attr:
“MAC_ADDR”

Command attr_data:
user MAC address (string)

In response, the gateway device 12 typically issues a standard XML response indicating that the command was received and processed appropriately or that an error occurred, and that includes the following tag and data pairs:

tag_1 =
“STATUS”

data_1 =
“VALID_USER” or “INVALID_USER”

tag_2 =
“PAYMENT_METHOD”

data_2 =
“RADIUS,” “PMS,” “CREDIT_CARD,” or “ROOM”

The billing and content server 26 can also issue an XML command requesting user authorization and payment. If the authorization method that the user has selected is RADIUS, then the gateway device 12 will establish communication with the RADIUS server, authenticate the user, charge the user's account, and return the result of the authorization to the billing and content server. If the authorization method chosen by the user is PMS, the gateway device will establish communication with the PMS 28, authenticate the user, have an access fee added to the user's room bill, and return the result of the authorization to the billing and content server. In either event, the XML command issued by the billing and content server to request user authorization payment includes the following command, command attribute, command attribute data and tag and data pairs:

Command:
“USER_PAYMENT”

Command attr:
“PAYMENT_METHOD”

Command attr_data:
“RADIUS” OR “PMS”

tag_1:
“USER NAME”

data_1:
(user name)

tag_2:
“PASSWORD”

tag_2_attr:
“ENCRYPT”

tag_2_attr_data:
“TRUE” or “FALSE”

data_2:
(user password)

tag_3:
“EXPIRY_TIME”
- only if METHOD=“PMS”

tag_3_attr:
“UNITS”

tag_3_attr_data:
“SECONDS,” “HOURS,” “DAYS”

data_3:
(number of expiry units)
- only if METHOD=“PMS”

tag_4:
“ROOM_NUMBER”

data_4:
(user's room number)

tag_5:
“PAYMENT”
- only if METHOD=“PMS”

data_5:
(amount charged for access)
- only if METHOD=“PMS”

In response, the gateway device 12 issues a standard XML response indicating that the command was received and processed appropriately or that an error occurred, and that includes the following tag and data:

tag_1 =
“CONFIRMATION”

data_1 =
(confirmation number/ID)

The billing and content server 26 can also issue an XML command in instances in which a user makes an e-commerce or special service purchase that is to be charged, such as to the user's bill via the property management system 28. In this regard, the billing and content server issues an XML command that includes the following command, command attribute, command attribute data and tag and data pairs.

Command:
“USER_PURCHASE”

Command attr:
“ROOM_NUMBER”

Command attr_data:
(room number)

tag_1:
“ITEM_CODE”

data_1:
(item code)

tag_2:
“ITEM_DESCRIPTION”

data_2:
(description of purchase)

tag_3:
“ITEM_AMOUNT”

data_3:
(amount of item without tax)

tag_4:
“ITEM_TAX”

data_4:
(tax charged on item)

tag_5:
“ITEM_TOTAL”

data_5:
(total amount charged including tax)

In response, the gateway device will issue a standard XML response indicating that the command was received and processed appropriately or that an error occurred.

Finally, the billing and content server 26 can issue an XML command in order to update cache memory by changing the status of an entry in the memory authorization table, as identified by the MAC address by way of example, from “pending” to “authorized.” In this regard, the XML command can include the following command, command attribute, command attribute date and tag and data pair:

Command:
“CACHE_UPDATE”

Command attr:
“MAC_ADDR”

Command attr_data:
user MAC address (string)

tag_1:
“PAYMENT_METHOD”

data_1:
“RADIUS,” “PMS,” “CREDIT_CARD,” or

“ROOM_OPEN”

In response, the gateway device will issue a standard XML response indicating that the command was received and processed appropriately or that an error occurred.

While the foregoing XML commands and XML responses that would flow between a billing and content server 26 and a gateway device 12 have been provided by way of example in order to illustrate one particular application of the XML interface 32 or XML parser of a gateway device, the gateway device that includes an XML interface according to the present invention can be employed to communicate with the billing and content server according to a wide variety of other commands and responses depending upon the application. In addition, a gateway device that includes an XML interface can also be employed to communicate with a wide variety of other external devices, including a property management system 28, an external AAA server, or other external devices. In addition, the gateway device can be configured to issue the XML commands and to receive XML responses if necessary for the particular application. In any event, a gateway device that includes an XML interface facilitates communication between the gateway device and various external devices in a uniform manner, thereby avoiding having to communicate with each of the external devices according to a unique format established by the vendor of the external device. As a result, the design, implementation operation of the gateway device is greatly simplified and the user is able to reap the advantages provided by XML without having to reconfigure their computer 14 to support XML.

Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Enabling Network Gateway Devices to Communicate with Management Systems to Facilitate Subscriber Management

A system and method for enabling a management system to communicate with a network gateway device to automatically bill a computer operator for access to a computer network, such as a local network. The system includes a computer, and a network gateway device in communication with the computer for connecting the computer to a computer network, wherein the network gateway device maintains data representative of the computer operator's access to the computer network and wherein the network gateway device reconfigures the data. The system also includes a management system connected to said network gateway device for automatically billing the computer operator based upon usage of the computer network, wherein the management system is configured to communicate according to at least one predetermined protocol. The network gateway device reconfigures the data to meet one of the predetermined protocols supported by the management system, and the management system receives the data reconfigured by the network gateway device and utilizes the data reconfigured by the network gateway device for automatic billing purposes. The method for enabling a management system to communicate with a network gateway device to automatically bill a customer for network access includes allowing a computer operator to access a computer network via a network gateway device, collecting data corresponding to a customer's local network access in the network gateway device, storing the data in the network gateway device, reconfiguring the data to a predetermined data format received from a management system, and transmitting the reconfigured data to the management system.

In order for a computer to function properly, the computer must be appropriately configured. Among other things, this configuration process establishes the protocol and other parameters by which the computer transmits and receives data. In one common example, a plurality of computers is networked to create a local area network (LAN). In the LAN, each computer must be appropriately configured in order to exchange data over the network. Since most networks are customized to meet a unique set of requirements, computers that are part of different networks are generally configured in different manners in order to appropriately communicate with their respective networks

While desktop computers generally remain a part of the same network for a substantial period of time, laptops or other portable computers are specifically designed to be transportable. As such, portable computers are connected to different networks at different times depending upon the location of the computer. In a common example in which the portable computer serves as an employee's desktop computer, the portable computer is configured to communicate with their employer's network, i.e., the enterprise network. When the employee travels, however, the portable computer may be connected to different networks that communicate in different manners. In this regard, the employee may connect the portable computer to the network maintained by an airport or by a hotel in order to access the enterprise network, the internet or some other on-line service. Since these other networks are configured somewhat differently, however, the portable computer must also be reconfigured in order to properly communicate with these other networks. Typically, this configuration is performed by the user each time that the portable computer is connected to a different network. As will be apparent, this repeated reconfiguration of the portable computer is not only quite time consuming, but is also prone to errors.

As described by U.S. patent application Ser. No. 08/816,174 and U.S. Prov. Pat. App. No. 60/111,497, a universal subscriber gateway has been developed by Nomadix, Inc. of Santa Monica, Calif. The contents of both of these applications are incorporated herein by reference. The gateway device serves as a gateway to a number of networks or other online services. For example, the gateway device can serve as a gateway to the internet, the enterprise network, or other on-line services. In addition to serving as a gateway, the gateway device automatically configures a computer to communicate with the new network in a manner that is transparent to the user. In this regard, the gateway device will download the necessary protocols and other parameters to the computer without any intervention by the operator and without loading any additional software on the computer.

Because high speed access to enterprise networks, the internet and on-line services is a desirable commodity, like long distance telephone service, costs associated with the service are typically passed on to the remote user/subscriber. Therefore, in many instances the remote user/subscriber is concerned with being able to acquire network access and service in the most cost efficient and convenient manner. In this regard, subscriber remote service concerns parallel those concerns of customers utilizing internet service providers for conventional telephone line dial-up internet access. In both cases, computer operators typically want inexpensive, flexible and customer friendly service options. Correspondingly, the gateway device administrator desires the capability to be able to offer the user/subscriber numerous and different service and billing rate options, like those available in conventional dial-up internet access. For example, the remote user in a hotel environment may desire a subscription for only a day, or for the duration of their stay at the hotel. The user/subscriber may be charged on an hourly rate, a daily rate, a weekly rate, or at any other interval. Such flexible plans offer cost savings to consumers and are an attractive incentive to lure customers into buying access time to the enterprise network, online services or the internet.

Unlike conventional dial-up internet access, however, gateway devices permit remote users to access various computer networks and on-line services without having a prior service contract or an ongoing relationship with the service provider. Therefore, unlike conventional dial up access plans, which can bill subscribers on a set monthly schedule, gateway devices make recouping remote access charges more challenging. This is especially true for nomadic users, who may utilize a remote connection to a network only once before relocating. Once the traveler has moved onward, the network provider may have difficulty in collecting any unpaid service charges. Furthermore, billing of nomadic users is another hurdle to fast and easy access to the enterprise network, on-line services and the internet. The benefits of remote plug and play access therefore may be overshadowed by time consuming payment methods. For example, where a computer operator is required to complete an onerous billing procedure to pre-purchase local network time or to pay for the network use after each session, the computer operator may decide not to use the network.

Thus, any convenience provided by the computer network is superseded by the inconvenient billing method. Gateway device administrators also desire convenient methods in which to bill users/subscribers. Because the gateway device enables subscribers immediate plug and play connections to computer networks, such as hotel or airport networks, the computer network provider and/or service provider of the high speed network would like to quickly and immediately bill the users/subscribers. This billing should be able to easily track a user/subscriber's usage of the network so as to recoup costs for the network hardware and network connection. Furthermore, such billing should be automated such that system administrators do not need to individually bill each remote user.

Therefore, it is desirable for customers, network providers and service providers to implement automatic billing through the computer network so that users may be billed automatically. Such automatic billing of remote and nomadic users would benefit customers by facilitating fast and easy access, and also would benefit network providers who could appropriately charge customers for obtaining remote access.

The present invention relates generally to a network gateway device and, more particularly, to network gateway devices communicating with management systems, such as hotel property management systems, to facilitate subscriber management. The connection of the users to the system can be transparent for billing purposes, although the computer network may also provide services to the users through the management system.

According to one embodiment of the invention, there is provided a system for enabling a management system to communicate with a network gateway device on order to automatically bill a computer operator for access to a computer network such as a local network. The system includes a computer, and a network gateway device in communication with the computer for connecting the computer to a computer network and for maintaining data representative of the computer operator's access to the computer network. The system also includes a management system connected to the network gateway device that is designed to automatically bill the computer operator based upon their access to the computer network. The management system is also designed to communicate with a third party device according to at least one predetermined protocol. According to the present invention, the gateway device is therefore designed to supply billing data using one of the predetermined protocols supported by the management system. As such, the management system receives the billing data supplied by the network gateway device and utilizes the data for automatic billing purposes.

Furthermore, in the system for enabling a management system to communicate with a network gateway device to automatically bill a computer operator for access to a computer network, the management system can be located within the computer network. Additionally, the system can include a translator in communication with the gateway device and management system for receiving the data supplied by the network gateway device. The translator can further reconfigured the supplied billing data received from the network gateway device, and can transmit the further reconfigured data to the management system. The data representative of the computer operator's access to the computer network can include data representative of the computer operator's location, access time, date which access was obtained, billing rate, and other pertinent information.

According to another embodiment of the invention, a method for enabling a management system to communicate with a network gateway device in order to automatically bill a customer for access to a computer network, such as a local network, is provided. The method comprises allowing a network administrator to access a computer network via a network gateway device, and collecting data corresponding to a customer's local network access in the network gateway device. Furthermore, the method of the present invention comprises storing the data in the network gateway device, reconfiguring the data to one of the predetermined data formats which may be received by a management system, and transmitting the reconfigured data to the management system.

The ability to bill customers for service automatically and track customers without system intervention allows the local network service provisioning to be done economically and efficiently. This invention provides an incentive for hotels, airports, and other computer networks to provide network connections to users because the computer network has a captive customer base. Furthermore, automatic billing can enable usage-based billing for network access and services, which is desirable to customers. Finally, automatic billing can reduce the risk of network use by an unauthorized user.

Referring now to FIG. 5, the computer system 10 that includes a gateway device 12 is depicted in block diagram form. The computer system 10 typically includes a plurality of computers 14 that access a computer network in order to gain access to networks 20 or other online services 22. For example, the computers 14 can be plugged into ports that are located in different rooms of a hotel or a multi-dwelling unit. Alternatively, the computers 14 can be plugged into ports in an airport, an arena, or the like. The gateway device 12 provides an interface between the plurality of computers 14 and the various networks 20 or other online services 22.

Most commonly, the gateway device 12 is located near the computers 14 at a relatively low position in the overall network (i.e., the gateway will be located within the hotel, multi-unit residence, airport, etc.). However, the gateway device 12 can be located at a higher position in the system by being located closer to the various networks 20 or other online services 22, if so desired. Although the gateway device 12 can be physically embodied in many different fashions, the gateway device 12 typically includes a controller and a memory device in which software is stored that defines the operational characteristics of the gateway device 12. Alternatively, the gateway device 12 can be embedded within another network device, such as an access controller 16 or a router 18. Moreover, the software that defines the functioning of the gateway device 12 can be stored on a PCMCIA card that can be inserted into a computer of the plurality of computers 14 in order to automatically reconfigure the computer to communicate with a different computer system, such as the networks 20 and online services 22.

The computer system 10 typically includes an access controller 16 positioned between the computers 14 and the gateway device 12 for multiplexing the signals received from the plurality of computers onto a link to the gateway device 12. Depending upon the medium by which the computers 14 are connected to the access controller, the access controller 16 can be configured in different manners. For example, the access controller can be a digital subscriber line access module (DSLAM) for signals transmitted via regular telephone lines, a cable head end for signals transmitted via coaxial cables, a wireless access point (WAP) for signals transmitted via a wireless network, a CMPS, a switch or the like. As also shown in FIG. 5, the computer system 10 typically includes one or more routers 18 and/or servers (not shown in FIG. 5) of a plurality of computer networks 20 or other online services 22. While the computer system 10 is depicted to have a single router, the computer system 10 can have a plurality of routers, switches, bridges, or the like that are arranged in some hierarchical fashion in order to appropriately route traffic to and from the various networks 20 or other online services 22. In this regard, the gateway device 12 typically establishes a link with one or more routers. The routers, in turn, establish links with the servers of other networks or other online service providers, such as internet service providers, based upon the subscriber's selection. It will be appreciated by one of ordinary skill in the art that one or more devices illustrated in FIG. 5 may be combinable. For example, although not shown, the router 18 may be located entirely within the gateway device 12.

The gateway device 12 is specifically designed to allow computers to log onto the computer network in a manner that is transparent to the subscriber In the typical computer network that employs dynamic host configuration protocol (DHCP) service, the DHCP server 24 will initially assign an IP address to a computer that is logging onto the computer network. Upon opening their web browser or otherwise attempting to access an on-line service, the gateway device 12 will direct the subscriber to enter their ID and password. The gateway device 12 then determines if the subscriber is entitled to access the computer system, the level of access and/or the type of services to which the subscriber is entitled according to an authentication, authorization and accounting procedure that is described by U.S. patent application Ser. No. 08/816,174 and U.S. Provisional Application No. 60/111,497. Assuming that the subscriber has been authenticated and has authorization, the gateway device 12 typically presents new subscribers with a home page or control panel that identifies, among other things, the online services or other computer networks that are accessible via the gateway device 12. In addition, the home page presented by the gateway device 12 can provide information regarding the current parameters or settings that will govern the access provided to the particular subscriber. As such, the operator can readily alter the parameters or other settings in order to tailor the service according to their particular application. Typically, changes in the parameters or other settings that will potentially utilize additional resources of the computer system will come at a cost, such that the gateway device 12 will charge the subscriber a higher rate for their service. For example, a subscriber may elect to increase the transfer rate at which signals are transmitted across the computer network and pay a correspondingly higher price for the expedited service.

The home page also permits the subscriber to select the computer network 20 or other online service 22 that the subscriber wishes to access. For example, the subscriber can access the enterprise network on which the computer is typically resident. Alternatively, the subscriber can access the internet or other on-line services. Once the subscriber elects to access a computer network or other online service, the gateway device 12 establishes the appropriate links via one or more routers 18 to the desired computer network or online service.

Thereafter, the subscriber can communicate freely with the desired computer network 20 or other online service 22. In order to support this communication, the gateway device 14 generally performs a packet translation function that is transparent to the subscriber. In this regard, for outbound traffic from the computer 12 to the computer network or other on-line service, the gateway device 12 changes the content of the packet, such as the source address, checksum, and application specific parameters, such that all outgoing packets will be directed back to the gateway device 12 rather than to the computer. In contrast, the inbound traffic from the computer network or other online service that arrives at the gateway device 12, which is really intended for the computer, is passed through the translation function so the packets eventually delivered to the computer appear to have been sent directly to the computer. As such, the computer will be completely unaware of the translation being performed by the gateway device. Additional information regarding the translation function is provided by U.S. patent application Ser. No. 08/816,714. By utilizing the gateway device 12 to communicate with the computer network or other online service, however, the subscriber will never have had to configure their computer 12 since the gateway device automatically adopts the computer in a manner that is transparent to the subscriber.

FIG. 6 shows a block diagram of the computer system 10 of FIG. 5, implemented in a hotel computer system 50, according to one embodiment of the present invention. It will be appreciated by those of skill in the art that the embodiment shown in FIG. 6 is for illustrative purposes, and that the computer system 10 may be implemented with respect to computer networks established in airports, arenas, apartment complexes, office buildings or the like. The hotel computer system 50 is essentially identical to the computer system 10 shown in FIG. 6, except that the gateway device 12 is also connected to a property management system 56. The gateway device 12 may be connected to the property management system 56 through a translator 53, which is illustrated with phantom lines because the translator 53 is an optional component in the hotel computer system 50, as will be explained in detail below. Because the hotel computer system 50 comprises similar components to the system illustrated in FIG. 5, it will be appreciated that the systems can be implemented in like manners with like components. Furthermore, additional embodiments of the present invention discussed with respect to FIG. 5 may be implemented in the system 50 shown in FIG. 6.

As shown in FIG. 6, each of the plurality of computers 14 is located in a different hotel room 60, 70, 80 and 90 to allow multiple guests to access the hotel's computer network. The computers 14 are connected to the access controller 16 through a communications port in each room using a communications device such as a DSL modem, an ethernet card, a coaxial cable, or another well known communication device. Most preferably, the connection between the computers 14 and the access controller 16 is a high speed connection, so that the computers 14 can receive data as fast as the gateway device 12 can forward the data. The data transmitted from the gateway device 12 to the computers may originate from any devices located within the computer network or any devices in communication with the computer network, such as the internet. As with any multiple link communication system, the rate at which data is received by the computers 14 will be no higher than the slowest baud rate over any link in the system.

The gateway device 50 is in direct communication with the management system 56. Management systems may include any well known computer based systems implemented in hotels, airports, arenas or other venues to manage operations. In the embodiment of FIG. 6, the management system is a property management system located within a hotel. Typical hotel property management systems automate operations such as room reservations, room assignments, guest check-in and check-out, and other front desk activities. Furthermore, typical hotel property management systems can maintain a log of telephone calls and telephone charges for each guest room, and can be in communication with the internet to facilitate on-line reservations. Such management systems are typically implemented through the use of one or more conventional computers that are interconnected to form a network. The management system 56 shown in FIG. 6 is illustrative of one such system. As will be appreciated by those of skill in the art, the management system can be located within, and in direct communication with, the computer network.

In the embodiment of FIG. 6, the gateway device 50 is in communication with the property management system 56 such that each user/subscriber's access and connection to the hotel network via the gateway device 12 can be easily monitored by the property management system 56. Preferably, the gateway device 12 is connected to the property management system 56 through a serial port interface. The connection may operate at a variety of baud rates, although 2400 or 9600 bits per second are typical. The main purpose for the connection is to allow the hotel to bill each specific user/subscriber for their use and connection to the hotel's network, and to automatically bill such use directly to the room from which access was obtained. The property management system 56 can monitor and record information such as the identity of the user, the room from which the user obtained access, the amount of time that the user utilized the network, the cost of each network access, the time, date and duration of the network access, and other additional information. As a result, the present invention offers user/subscribers of a computer network convenient payment plans in which a user does not have to pre-pay for network access or physically pay each time the network is accessed.

As will be appreciated by those of skill in the art, the information passed from the gateway device 12 can be, in most respects, identical to information received by the property management system 56 from a private branch telephone system (PBX), which are commonly utilized in hotels. PBX systems allow room to room, local and long distance telephone calls to be made by guests, and are typically connected to hotel property management systems to facilitate billing of hotel guests based upon the room in which the call is made. Charges for such use can then be paid by the guest upon checkout, automatically billed to the guest's credit card or automatically billed to the guest with room charges.

As can be appreciated with reference to FIG. 6, the property management system 56 can be in communication with additional devices other than the computer gateway system 10 of the present invention. As noted above, the property management system 56 can be directly connected to a PBX, which is, in turn, connected to each telephone located in every hotel room. Additionally, although not illustrated, the property management system 56 can be connected to additional third party components, such as pay per view television, credit card authorization systems and point of sale systems. These connections may be through serial ports, modem communications, or through other well known communication means. Such connections allow the management system to function as a fully integrated system, which allows customers to use a variety of hotel resources, while transparently being billed for each transaction.

Through the property management systems, a user/subscriber's account may be billed directly to that user's hotel bill. For example, where the management system receives data representing a computer operator's access to the local system, the management system can automatically bill the operator through the use of a credit card authorization system in communication with the property management system. In this manner, the customer's payment can be fast, easy, automated and transparent to the user.

Traditional hotel property management systems are configured to communicate with various third party systems, such as point of sale systems, PBX systems, pay per view systems, and credit card authorization servers, as noted above. Hotel property management systems are generally configured to receive such communications because these third party systems are typically used in the vast majority of hotels. To receive data from each of these third party systems, management systems typically include software for communicating with the third party systems based upon the data protocol and data structure implemented by the management system. The software allows data from third party systems to be received and reconfigured, if necessary, so that the data is in a format appropriate to be utilized by the management system 56. However, because typical management systems that are currently deployed are not designed to receive data from a gateway device 12, the gateway device 12 is preferably designed to interface with the management system 56 without requiring additional programming of the management system software.

The gateway device 12 of the present invention formats data such that the data has the same data protocol and data structure as that of a third party service, such as a PBX, that the management system 56 is already designed to receive. The management system 56 is adapted to communicate using different protocols, through technology known as COM objects. Thus, the gateway device 12 can masquerade as a PBX or another third party system. The gateway device 12 receives a data record corresponding to an individual user/subscriber's use of the computer system, including the user/subscriber's location (room number), access time, and additional information, as discussed above. The gateway device 12 stores this information and modifies the data record to fit the proper format required by the property management system vendor. Although the format of the data is changed, no data is changed in the modification. The reconfigured data is then transmitted to the management system 56. This data can be in a call accounting record (CAR) and low level protocol (LLC) format, data formats typical of third party systems such as PBXs. Such formats are well known to those of skill in the art of property management system design.

Because management systems can differ, each system utilizing different user interfaces, variables, and operating systems, the gateway device should communicate data to the property management system 56 using data formats acceptable to a large number of management systems. In this manner, the gateway device 12 may be compatible with a majority of property management systems. For example, the gateway device 12 may be preconfigured to operate with the most popular management systems and formats, such as Micros Fidelio (manufactured by MICROS Systems, Inc., Beltsville, Md.), HOBIC, AutoClerk (manufactured by AutoClerk, Inc., Lafayette, Calif.), and other well known systems and formats.

However, there are many different management system standards, none of which are universal and implemented in all property management systems. As a result, although the gateway device 12 can configure data to conform to a large number of differing management systems, the gateway device 12 may not be able to conform to some systems. As a result, a translator 53 may be optionally used to manipulate the data output by the gateway device 12 in such a manner as to allow the data to be utilized by the property management system 56. In one embodiment, the translator may comprise a Lodging Link II device (LL) (manufactured by Protocol Technologies, Inc., Scottsdale, Ariz.) to convert incoming data from the gateway device 12 to data acceptable to the property management system device, such as UHALL protocol. Additionally, the translator may also be connected to one or more devices or systems in communication with the property management system, such as the pay per view system or credit card authorization system, to format data output by any system or component having data protocols which differ from those of the management system 56.

Because data may be transferred to the management system in a CAR format, data typically within such format must be altered to accurately reflect the computer network service being provided to the user/subscriber. For example, in PBX systems, CAR format usually includes the phone number to which a telephone call is being made. However, when a user/subscriber is obtaining access to the hotel network via the gateway device 12, no telephone number is dialed or called. Therefore, when possible, data within the CAR format (i.e., telephone record), such as telephone numbers, may be replaced with a descriptive record that indicates some other data that the property management systems wish to track or record. On the other hand, where the CAR records cannot be replaced, a bogus field, such as a bogus telephone number, may be included so that the property management system receives the entire record it is programmed to receive. Thereafter, the bogus number is not utilized by the management system 56. Additional problems may also exist, for example, where the management system 56 is not devised to support the non-numeric ASCII characters typically transmitted by the gateway device 12. In this situation, the gateway device can be configured to replace the ASCII characters with numeral designations.

Once the data transmitted by the gateway device is received by the property management system 56, the property management system can display the data using a management system interface. Preferably, the data may be displayed in an easily readable and printable form to allow a user/subscriber to view a summary of access information. Additionally, the data should be accessible to the user/subscriber's accounting record. In this manner, charges due to network access may be automatically placed on a customer's pre-existing bill, such as a hotel bill. Where access is obtained at another location, such as at an airport, the airport system manager (i.e., equivalent to the hotel property management system in the above example) may automatically bill the customer, can automatically charge the customer's credit card, or can add the charges to an account which the customer maintains. In this regard, while the property management system 56 has primarily been described in conjunction with a hotel computer network, the property management system can be utilized in a variety of other applications in which a user/subscriber obtains access to a computer network or other on-line service via a gateway device.

Claims

1. A method of providing services to users, the method being performed at a network system, the method comprising: providing a subscriber computer with access to at least one network via a network system;receiving an XML command at the network system from a service provider system;parsing the XML command to determine a type of operation requested by the service provider system and to determine a user associated with the XML command;translating at least a portion of the XML command to produce data in a specialized data format configured to be compatible with a protocol associated with a service usage accounting system;transmitting the data in the specialized data format to the service usage accounting system, the data in the specialized data format configured to authorize and bill an account associated with the user;receiving an authorization result from the service usage accounting system;translating the authorization result to produce an XML response indicating that the XML command was received and processed appropriately; andtransmitting the XML response from the network system to the service provider system, the XML response comprising a confirmation identifier based on the authorization result.
2. The method of claim 1, wherein the protocol associated with the service usage accounting system includes a telephone number, and wherein translating at least a portion of the XML command to produce data in the specialized data format comprises including descriptive data in the place of the telephone number.
3. The method of claim 1, wherein the XML command comprises an identifier of a hotel room number associated with the user, and wherein the data in the specialized data format comprises an identifier of the hotel room number included in the XML command.
4. The method of claim 1, wherein communicating with the service usage accounting system comprises transmitting a second XML command to the service usage accounting system.
5. A computing system configured to manage services provided to users, the system comprising: one or more communications interfaces configured to communicate with a guest service and with an accounting system;a subscriber interface configured to provide a subscriber computer with access to at least one network and to adapt to the subscriber computer to facilitate communications between the subscriber computer and the at least one network; andone or more computer processors configured to receive an XML command from the guest service;parse the XML command to determine a type of operation requested by the guest service and to determine a user associated with the XML command;transmit data, in a format specific to the accounting system, to the accounting system to authorize and bill an account associated with the user in accordance with data in the XML command;receive an authorization result from the accounting system; andtransmit an XML response to the guest service, the XML response comprising a confirmation identifier based on the authorization result.
6. The computing system of claim 5, wherein communicating with the accounting system comprises transmitting a second XML command to the accounting system.
7. The computing system of claim 5, wherein the XML command includes data representing a payment amount and a room number.
8. The computing system of claim 5, wherein the format specific to the accounting system is a call accounting record format.
9. The computing system of claim 5, wherein the one or more computer processors are further configured to generate data in a plurality of formats each specific to a type of accounting system, to thereby enable communication with the plurality of types of accounting systems.
10. The computing system of claim 5, wherein the XML command comprises an identifier of a hotel room number associated with the user, and wherein the data in the format specific to the accounting system comprises an identifier of a hotel room number based on the hotel room number included in the XML command.
11. A non-transitory computer-readable medium, comprising instructions configured to cause a computer processor to perform operations comprising: parsing a first XML command received from a first server, to determine a type of operation requested by the first server and to determine a user associated with the XML command;translating at least a portion of the XML command to produce a command configured to be interoperable with a protocol associated with a second server, the command being different from the XML command, the command comprising an identifier of the user associated with the XML command and further comprising billing information;transmitting the command to the second server;receiving an authorization result from the second server;generating an XML response based on the received authorization result, the XML response indicating that the XML command was received and processed appropriately; andtransmitting the XML response to the first server.
12. The non-transitory computer-readable medium of claim 11, wherein the command is configured to appear to originate from a Private Branch Telephone System (PBX).
13. The non-transitory computer-readable medium of claim 11, wherein the protocol associated with the second server requires a telephone number record, and the command comprises a descriptive record in the place of a telephone number record.
14. The non-transitory computer-readable medium of claim 11, further comprising instructions configured to cause the computer processor to produce commands specific to a plurality of protocols, to thereby enable communication with a plurality of types of servers.
15. The non-transitory computer-readable medium of claim 11, wherein determining the user associated with the XML command comprises determining a MAC address associated with the XML command and identifying, in an authorization database, a user associated with the MAC address.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 09/693,512, filed Oct. 20, 2000, now U.S. Pat. No. 8,190,708, which claims priority from U.S. Prov. Pat. App. No. 60/161,181, filed Oct. 22, 1999. The aforementioned patent applications are hereby incorporated by reference as if set forth herein in their entireties.

US Referenced Citations (455)

Number	Name	Date	Kind
4677588	Benjamin	Jun 1987	A
4811011	Sollinger	Mar 1989	A
5065393	Sibbitt	Nov 1991	A
5124984	Engel	Jun 1992	A
5142622	Owens	Aug 1992	A
5185860	Wu	Feb 1993	A
5258906	Kroll	Nov 1993	A
5293488	Riley	Mar 1994	A
5329619	Page	Jul 1994	A
5369705	Bird	Nov 1994	A
5406555	Yoshida	Apr 1995	A
5420862	Perlman	May 1995	A
5481542	Logston	Jan 1996	A
5490252	Macera	Feb 1996	A
5526489	Nilakantan	Jun 1996	A
5533026	Ahmadi	Jul 1996	A
5548646	Aziz	Aug 1996	A
5550984	Gelb	Aug 1996	A
5553223	Greenlee et al.	Sep 1996	A
5574779	Ely	Nov 1996	A
5583864	Lightfoot	Dec 1996	A
5592537	Moen	Jan 1997	A
5598536	Slaughter	Jan 1997	A
5602991	Berteau	Feb 1997	A
5604896	Duxbury	Feb 1997	A
5606668	Shwed	Feb 1997	A
5615339	Ban	Mar 1997	A
5617540	Civanlar et al.	Apr 1997	A
5633999	Clowes	May 1997	A
5636216	Fox et al.	Jun 1997	A
5636371	Yu	Jun 1997	A
5644719	Aridas	Jul 1997	A
5649001	Thomas	Jul 1997	A
5652908	Douglas	Jul 1997	A
5657452	Kralowetz	Aug 1997	A
5659684	Giovannoni	Aug 1997	A
5664102	Faynberg	Sep 1997	A
5678041	Baker	Oct 1997	A
5696899	Kalwitz	Dec 1997	A
5699520	Hodgson	Dec 1997	A
5708654	Arndt	Jan 1998	A
5717737	Doviak	Feb 1998	A
5724510	Arndt	Mar 1998	A
5745699	Lynn et al.	Apr 1998	A
5751961	Smyk	May 1998	A
5757784	Liebowitz	May 1998	A
5758083	Singh et al.	May 1998	A
5758186	Hamilton	May 1998	A
5764890	Glasser	Jun 1998	A
5774668	Choquier	Jun 1998	A
5774869	Toader	Jun 1998	A
5790548	Sistanizadeh	Aug 1998	A
5793762	Penners et al.	Aug 1998	A
5794221	Egendorf	Aug 1998	A
5796952	Davis et al.	Aug 1998	A
5802047	Kinoshita	Sep 1998	A
5802285	Hirviniemi	Sep 1998	A
5802310	Rajaraman	Sep 1998	A
5805803	Birrell et al.	Sep 1998	A
5806043	Toader	Sep 1998	A
5812786	Seazholtz	Sep 1998	A
5812819	Rodwin	Sep 1998	A
5815664	Asano	Sep 1998	A
5818845	Moura et al.	Oct 1998	A
5832229	Tomoda	Nov 1998	A
5835061	Stewart	Nov 1998	A
5835720	Nelson et al.	Nov 1998	A
5835724	Smith	Nov 1998	A
5835725	Chiang	Nov 1998	A
5835727	Wong	Nov 1998	A
5844973	Venkatraman	Dec 1998	A
5848233	Radia	Dec 1998	A
5856974	Gervais	Jan 1999	A
5862325	Reed et al.	Jan 1999	A
5862328	Colyer	Jan 1999	A
5864683	Boebert	Jan 1999	A
5881234	Schwob	Mar 1999	A
5884035	Butman et al.	Mar 1999	A
5889958	Willens	Mar 1999	A
5894321	Downs	Apr 1999	A
5894479	Mohammed	Apr 1999	A
5901287	Bull et al.	May 1999	A
5903732	Reed et al.	May 1999	A
5909441	Alexander, Jr. et al.	Jun 1999	A
5915093	Berlin	Jun 1999	A
5916302	Dunn	Jun 1999	A
5918018	Gooderum	Jun 1999	A
5922049	Radia	Jul 1999	A
5923853	Danneels	Jul 1999	A
5930255	Tsukamoto et al.	Jul 1999	A
5931917	Nguyen	Aug 1999	A
5940394	Killian	Aug 1999	A
5941947	Brown	Aug 1999	A
5941988	Bhagwat et al.	Aug 1999	A
5946687	Gehani	Aug 1999	A
5949875	Walker	Sep 1999	A
5951694	Choquier	Sep 1999	A
5958015	Dascalu	Sep 1999	A
5958018	Eng	Sep 1999	A
5968126	Ekstrom	Oct 1999	A
5969678	Stewart	Oct 1999	A
5970490	Morgenstern	Oct 1999	A
5982773	Nishimura	Nov 1999	A
5987523	Hind	Nov 1999	A
5987611	Freund	Nov 1999	A
5999536	Kawafuji	Dec 1999	A
5999912	Wodraz	Dec 1999	A
6006258	Kalajan	Dec 1999	A
6011782	DeSimone	Jan 2000	A
6012083	Savitzky	Jan 2000	A
6018771	Hayden	Jan 2000	A
6028848	Bhatia	Feb 2000	A
6035281	Crosskey	Mar 2000	A
6038233	Hamamoto	Mar 2000	A
6044062	Brownrigg	Mar 2000	A
6055236	Nessett	Apr 2000	A
6055243	Vincent et al.	Apr 2000	A
6058418	Kobata	May 2000	A
6061349	Coile	May 2000	A
6061650	Malkin	May 2000	A
6061739	Reed	May 2000	A
6064674	Doidge et al.	May 2000	A
6070191	Narendran et al.	May 2000	A
6070243	See	May 2000	A
6073160	Grantham	Jun 2000	A
6073175	Tavs	Jun 2000	A
6088451	He	Jul 2000	A
6091732	Alexander	Jul 2000	A
6092196	Reiche	Jul 2000	A
6094659	Bhatia	Jul 2000	A
6101543	Alden	Aug 2000	A
6108330	Bhatia	Aug 2000	A
6112239	Kenner et al.	Aug 2000	A
6115376	Sherer et al.	Sep 2000	A
6115545	Mellquist	Sep 2000	A
6119161	Lita et al.	Sep 2000	A
6122268	Okanoue	Sep 2000	A
6128298	Wootton	Oct 2000	A
6130892	Short et al.	Oct 2000	A
6137791	Frid et al.	Oct 2000	A
6137869	Voit	Oct 2000	A
6138142	Linsk	Oct 2000	A
6138144	DeSimone	Oct 2000	A
6138162	Pistriotto et al.	Oct 2000	A
6141010	Hoyle	Oct 2000	A
6141653	Conklin	Oct 2000	A
6141686	Jackowski et al.	Oct 2000	A
6141690	Weiman	Oct 2000	A
6144991	England	Nov 2000	A
6147976	Shand	Nov 2000	A
6148336	Thomas et al.	Nov 2000	A
6154172	Piccionelli	Nov 2000	A
6154764	Nitta	Nov 2000	A
6154775	Coss	Nov 2000	A
6154839	Arrow	Nov 2000	A
6157377	Shah-Nazaroff	Dec 2000	A
6157647	Husak	Dec 2000	A
6157925	Jenkins et al.	Dec 2000	A
6157953	Chang	Dec 2000	A
6158008	Maria	Dec 2000	A
6160874	Dickerman	Dec 2000	A
6166730	Goode	Dec 2000	A
6167513	Inoue	Dec 2000	A
6173322	Hu	Jan 2001	B1
6175869	Ahuia et al.	Jan 2001	B1
6182154	Campagnoni	Jan 2001	B1
6189030	Kirsch et al.	Feb 2001	B1
6194992	Short et al.	Feb 2001	B1
6199100	Filepp	Mar 2001	B1
6201962	Sturniolo	Mar 2001	B1
6202169	Razzaghe-Ashrafi	Mar 2001	B1
6205148	Takahashi	Mar 2001	B1
6205481	Heddaya et al.	Mar 2001	B1
6219786	Cunningham	Apr 2001	B1
6219790	Lloyd	Apr 2001	B1
6223205	Harchol-Balter et al.	Apr 2001	B1
6223286	Hashimoto	Apr 2001	B1
6226675	Meltzer et al.	May 2001	B1
6233618	Shannon	May 2001	B1
6233686	Zenchelsky et al.	May 2001	B1
6237026	Prasad	May 2001	B1
6237037	Larsson	May 2001	B1
6240091	Ginzboorg	May 2001	B1
6240402	Lynch-Aird	May 2001	B1
6240513	Friedman	May 2001	B1
6240533	Slemmer	May 2001	B1
6247054	Malkin	Jun 2001	B1
6249820	Dobbins	Jun 2001	B1
6256307	Salmonson	Jul 2001	B1
6259405	Stewart	Jul 2001	B1
6266335	Bhaskaran	Jul 2001	B1
6282180	Paneth	Aug 2001	B1
6288739	Hales	Sep 2001	B1
6292478	Farris	Sep 2001	B1
6295291	Larkins	Sep 2001	B1
6298383	Gutman	Oct 2001	B1
6304857	Heindel	Oct 2001	B1
6308212	Besaw	Oct 2001	B1
6311275	Jin	Oct 2001	B1
6321336	Applegate	Nov 2001	B1
6326918	Stewart	Dec 2001	B1
6327242	Amicangioli et al.	Dec 2001	B1
6330586	Yates	Dec 2001	B1
6345291	Murphy, Jr. et al.	Feb 2002	B2
6359892	Szlam	Mar 2002	B1
6366893	Hannula	Apr 2002	B2
6377982	Rai	Apr 2002	B1
6381646	Zhang	Apr 2002	B2
6381650	Peacock	Apr 2002	B1
6385644	Devine et al.	May 2002	B1
6389462	Cohen	May 2002	B1
6393484	Massarani	May 2002	B1
6397255	Nurenberg et al.	May 2002	B1
6408336	Schneider	Jun 2002	B1
6412073	Rangan	Jun 2002	B1
6414635	Stewart et al.	Jul 2002	B1
6418324	Doviak	Jul 2002	B1
6424636	Seazholtz	Jul 2002	B1
6427170	Sitaraman et al.	Jul 2002	B1
6438125	Brothers	Aug 2002	B1
6438528	Jensen	Aug 2002	B1
6438578	Schmid	Aug 2002	B1
6452498	Stewart	Sep 2002	B2
6453353	Win	Sep 2002	B1
6453361	Morris	Sep 2002	B1
6463473	Gubbi	Oct 2002	B1
6463474	Fuh	Oct 2002	B1
6466076	Yoshikawa	Oct 2002	B2
6466976	Alles	Oct 2002	B1
6466981	Levy	Oct 2002	B1
6470027	Birrell	Oct 2002	B1
6470386	Combar	Oct 2002	B1
6473411	Kumaki	Oct 2002	B1
6480486	Kikinis	Nov 2002	B2
6487538	Gupta	Nov 2002	B1
6487605	Leung	Nov 2002	B1
6496704	Yuan et al.	Dec 2002	B2
6515968	Combar et al.	Feb 2003	B1
6515989	Ronneke	Feb 2003	B1
6516416	Gregg et al.	Feb 2003	B2
6519636	Engel	Feb 2003	B2
6519643	Foulkes	Feb 2003	B1
6523028	DiDomizio	Feb 2003	B1
6535511	Rao	Mar 2003	B1
6539395	Gjerdingen et al.	Mar 2003	B1
6546392	Bahlmann	Apr 2003	B1
6549220	Hsu	Apr 2003	B1
6553178	Abecassis	Apr 2003	B2
6557038	Becker	Apr 2003	B1
6571221	Stewart	May 2003	B1
6574664	Liu	Jun 2003	B1
6577642	Fijolek	Jun 2003	B1
6578078	Smith et al.	Jun 2003	B1
6580717	Higuchi	Jun 2003	B1
6584505	Howard	Jun 2003	B1
6587880	Saigo	Jul 2003	B1
6597693	Leung	Jul 2003	B1
6601065	Nelson et al.	Jul 2003	B1
6609154	Fuh	Aug 2003	B1
6615212	Dutta et al.	Sep 2003	B1
6622128	Bedell et al.	Sep 2003	B1
6625645	Van Horne	Sep 2003	B1
6626957	Lippert et al.	Sep 2003	B1
6633899	Coward	Oct 2003	B1
6636504	Albers	Oct 2003	B1
6636894	Short et al.	Oct 2003	B1
6643701	Aziz et al.	Nov 2003	B1
6658625	Allen	Dec 2003	B1
6665718	Chuah	Dec 2003	B1
6667968	Tran	Dec 2003	B1
6671379	Nemirovski	Dec 2003	B2
6671739	Reed	Dec 2003	B1
6687732	Bector	Feb 2004	B1
6697018	Stewart	Feb 2004	B2
6697103	Fernandez et al.	Feb 2004	B1
6701350	Mitchell	Mar 2004	B1
6701361	Meier	Mar 2004	B1
6711146	Yegoshin	Mar 2004	B2
6714987	Amin	Mar 2004	B1
6717943	Schwering	Apr 2004	B1
6728884	Lim	Apr 2004	B1
6731612	Koss	May 2004	B1
6732176	Stewart	May 2004	B1
6735633	Welch et al.	May 2004	B1
6735691	Capps	May 2004	B1
6738382	West	May 2004	B1
6751677	Ilnicki	Jun 2004	B1
6757740	Parekh et al.	Jun 2004	B1
6759960	Stewart	Jul 2004	B2
6760416	Banks et al.	Jul 2004	B1
6760444	Leung	Jul 2004	B1
6771609	Gudat et al.	Aug 2004	B1
6771661	Chawla	Aug 2004	B1
6775267	Kung	Aug 2004	B1
6779035	Gbadegesin	Aug 2004	B1
6785704	McCanne	Aug 2004	B1
6789110	Short	Sep 2004	B1
6795852	Kleinrock et al.	Sep 2004	B1
6810426	Mysore et al.	Oct 2004	B2
6822955	Brothers	Nov 2004	B1
6823059	Kalmanek	Nov 2004	B2
6826694	Dutta et al.	Nov 2004	B1
6834341	Bahl	Dec 2004	B1
6839757	Romano	Jan 2005	B1
6850532	Thubert	Feb 2005	B2
6856800	Henry et al.	Feb 2005	B1
6857009	Ferreria et al.	Feb 2005	B1
6859212	Kumar et al.	Feb 2005	B2
6868399	Short et al.	Mar 2005	B1
6876668	Chawla	Apr 2005	B1
6892226	Tso	May 2005	B1
6901433	San Andres	May 2005	B2
6907449	Srinivasan	Jun 2005	B2
6915345	Tummala	Jul 2005	B1
6922672	Hailpern	Jul 2005	B1
6934754	West et al.	Aug 2005	B2
6937597	Rosenberg et al.	Aug 2005	B1
6944661	Moore et al.	Sep 2005	B2
6947398	Ahmed	Sep 2005	B1
6950433	Okamoto	Sep 2005	B1
6950628	Meier et al.	Sep 2005	B1
6961762	Yeap	Nov 2005	B1
6970927	Stewart	Nov 2005	B1
6983327	Koperda	Jan 2006	B2
6985479	Leung et al.	Jan 2006	B2
6996073	West et al.	Feb 2006	B2
7003578	Kanada et al.	Feb 2006	B2
7007080	Wilson	Feb 2006	B2
7009556	Stewart	Mar 2006	B2
7016960	Howard	Mar 2006	B2
7017046	Doyle et al.	Mar 2006	B2
7020082	Bhagavath et al.	Mar 2006	B2
7020681	Ayyagari et al.	Mar 2006	B1
7032243	Leerssen et al.	Apr 2006	B2
7035248	Wengrovitz	Apr 2006	B2
7043532	Humpleman et al.	May 2006	B1
7043563	Vange et al.	May 2006	B2
7047415	Doyle et al.	May 2006	B2
7058594	Stewart	Jun 2006	B2
7072056	Greaves et al.	Jul 2006	B1
7080077	Ramamurthy	Jul 2006	B2
7086077	Giammaressi	Aug 2006	B2
7088727	Short et al.	Aug 2006	B1
7093020	McCarty et al.	Aug 2006	B1
7117526	Short	Oct 2006	B1
7120678	Greuel	Oct 2006	B2
7120701	Warrier et al.	Oct 2006	B2
7124437	Byrne	Oct 2006	B2
7126915	Lu	Oct 2006	B1
7139268	Bhagwat et al.	Nov 2006	B1
7145898	Elliott	Dec 2006	B1
7151758	Kumaki et al.	Dec 2006	B2
7159035	Garcia-Luna-Aceves et al.	Jan 2007	B2
7185360	Anton et al.	Feb 2007	B1
7188085	Pelletier	Mar 2007	B2
7194554	Short et al.	Mar 2007	B1
7197556	Short et al.	Mar 2007	B1
7200578	Paltenghe et al.	Apr 2007	B2
7210035	Doyle et al.	Apr 2007	B2
7216043	Ransom et al.	May 2007	B2
7216152	Short et al.	May 2007	B2
7225249	Barry	May 2007	B1
7240106	Cochran et al.	Jul 2007	B2
7269653	Mentze et al.	Sep 2007	B2
7272639	Levergood et al.	Sep 2007	B1
7283542	Mitchell	Oct 2007	B2
7287071	MacLean	Oct 2007	B2
7289763	Denninson et al.	Oct 2007	B2
7293077	Teo	Nov 2007	B1
7319673	Briscoe	Jan 2008	B1
7324972	Oliver	Jan 2008	B1
7325063	Dillon	Jan 2008	B2
7333500	Roshko	Feb 2008	B2
7333942	Cowles	Feb 2008	B1
7336960	Zavalkovsky et al.	Feb 2008	B2
7349982	Hannum et al.	Mar 2008	B2
7356841	Wilson et al.	Apr 2008	B2
7376113	Taylor et al.	May 2008	B2
7401120	Walbeck	Jul 2008	B2
7428413	Fink	Sep 2008	B2
7437474	Iyer et al.	Oct 2008	B2
7457397	Saylor et al.	Nov 2008	B1
7472191	Stewart	Dec 2008	B2
7474617	Molen et al.	Jan 2009	B2
7483871	Herz	Jan 2009	B2
7493084	Meier et al.	Feb 2009	B2
7493402	McCarty et al.	Feb 2009	B2
7512136	Korotin	Mar 2009	B2
7526538	Wilson	Apr 2009	B2
7536714	Yuan	May 2009	B2
7539291	D'Angelo et al.	May 2009	B2
7552090	Barber	Jun 2009	B1
7554995	Short	Jun 2009	B2
7555542	Ayers et al.	Jun 2009	B1
7580376	West	Aug 2009	B2
7602782	Doviak	Oct 2009	B2
7685311	Friedman et al.	Mar 2010	B2
7685525	Kumar et al.	Mar 2010	B2
7689716	Short et al.	Mar 2010	B2
7698377	Parekh et al.	Apr 2010	B2
7698432	Short et al.	Apr 2010	B2
7734541	Kumar et al.	Jun 2010	B2
7739383	Short et al.	Jun 2010	B1
7743404	Deutschmann et al.	Jun 2010	B1
7752334	Paunikar et al.	Jul 2010	B2
7774612	Deutschmann et al.	Aug 2010	B1
7813741	Hendrey et al.	Oct 2010	B2
7818454	Kim et al.	Oct 2010	B2
7822871	Stolorz et al.	Oct 2010	B2
7822873	Paunikar	Oct 2010	B1
7844729	Friedman et al.	Nov 2010	B1
7953857	Short et al.	May 2011	B2
8051206	Paunikar et al.	Nov 2011	B2
20010003823	Mighdoll et al.	Jun 2001	A1
20010041571	Yuan	Nov 2001	A1
20010044818	Liang	Nov 2001	A1
20010054020	Barth et al.	Dec 2001	A1
20020006788	Knutsson et al.	Jan 2002	A1
20020016736	Cannon et al.	Feb 2002	A1
20020021689	Robbins	Feb 2002	A1
20020095651	Kumar et al.	Jul 2002	A1
20020133412	Oliver et al.	Sep 2002	A1
20020178070	Leveridge	Nov 2002	A1
20030067911	Kikinis	Apr 2003	A1
20030069991	Brescia	Apr 2003	A1
20030083889	Macklin	May 2003	A1
20040015572	Kang	Jan 2004	A1
20040030797	Akinlar et al.	Feb 2004	A1
20040039798	Hotz et al.	Feb 2004	A1
20040076144	Ishidoshiro	Apr 2004	A1
20040203752	Wojaczynski et al.	Oct 2004	A1
20050021943	Ikudome	Jan 2005	A1
20050102205	Yamamoto	May 2005	A1
20050143065	Pathan et al.	Jun 2005	A1
20050148342	Sylvain	Jul 2005	A1
20050240620	Danner et al.	Oct 2005	A1
20050260973	van de Groenendaal	Nov 2005	A1
20060026170	Kreitler et al.	Feb 2006	A1
20060080446	Bahl	Apr 2006	A1
20060089122	Zavalkovsky et al.	Apr 2006	A1
20060135155	Chung et al.	Jun 2006	A1
20060174019	Ikudome	Aug 2006	A1
20070011268	Banga et al.	Jan 2007	A1
20070162598	Gorodyansky	Jul 2007	A1
20070201702	Hendricks	Aug 2007	A1
20070266125	Lu et al.	Nov 2007	A1
20070271598	Chen et al.	Nov 2007	A1
20070294417	Ikudome	Dec 2007	A1
20080148383	Pitchaikani et al.	Jun 2008	A1
20080271109	Singh et al.	Oct 2008	A1
20090024745	Short et al.	Jan 2009	A1
20100115113	Short et al.	May 2010	A1
20100332615	Short et al.	Dec 2010	A1
20110030037	Olshansky et al.	Feb 2011	A1
20110131339	Brown et al.	Jun 2011	A1

Foreign Referenced Citations (51)

Number	Date	Country
2003255101	Mar 2004	AU
2330857	Nov 1999	CA
2296937	Jul 2000	CA
0573739	Dec 1993	EP
0742657	Nov 1996	EP
0767595	Apr 1997	EP
0873037	Oct 1998	EP
0901301	Mar 1999	EP
0912026	Apr 1999	EP
0946027	Sep 1999	EP
1076975	Nov 1999	EP
1111872	Jun 2001	EP
1026853	Dec 2007	EP
2283645	May 1995	GB
2311439	Sep 1997	GB
2326306	Dec 1998	GB
6-209319	Jul 1994	JP
06-348625	Dec 1994	JP
7-030575	Jan 1995	JP
7-202931	Aug 1995	JP
8-265372	Oct 1996	JP
08-265372	Nov 1996	JP
9-046352	Feb 1997	JP
10-105516	Apr 1998	JP
10-107839	Apr 1998	JP
11-055326	Feb 1999	JP
11-055726	Feb 1999	JP
11-282804	Oct 1999	JP
2002-514802	Nov 1999	JP
2000-059416	Feb 2000	JP
2000-354127	Dec 2000	JP
2002-111870	Apr 2002	JP
WO 9605549	Feb 1996	WO
WO 9702687	Jan 1997	WO
WO 9709672	Mar 1997	WO
WO 9722936	Jun 1997	WO
WO 9727546	Jul 1997	WO
WO9741586	Nov 1997	WO
WO 9748210	Dec 1997	WO
WO 9915995	Apr 1999	WO
WO 9928819	Jun 1999	WO
WO 9938303	Jul 1999	WO
WO 9946890	Sep 1999	WO
WO 9957837	Nov 1999	WO
WO 0027092	May 2000	WO
WO 0058804	Oct 2000	WO
WO 0079406	Dec 2000	WO
WO 0103011	Jan 2001	WO
WO 0163835	Aug 2001	WO
WO 2004017658	Feb 2004	WO
WO 2004100499	Nov 2004	WO

Non-Patent Literature Citations (352)

Entry
Aceves, Wireless Internet Gateways (Wings), Proc. IEEE MILCOM '97, Monterey, California, Nov. 1997.
Agrawal, SWAN: A Mobile Multimedia Wireless Network, IEEE Personal Communications, Apr. 1996.
Alexander, Active Bridging, University of Pennsylvania Technical Report No. MS-CIS-97-02, Jan. 1997.
Alonso, Database system issues in nomadic computing; Proceedings of the 1993 ACM SIGMOD International Conference on Management of Data, May 26, 1993.
Altmann, (Workshop '99) Assisting Users in Complex Purchasing Decisions, Jan. 12, 1999.
Altmann, Index Project: User support for buying QoS with regard to user's preferences, Sixth International Workshop on Quality of Service, May 18, 1998.
Amadio, Modelling IP Mobility, Nov. 1997.
Anderson, et al., The Magicrouter, an Application of Fast Packet Interposing, dated May 17, 1996 in 12 pages.
Aoyama, The Cost of Adaptivity and Virtual Lanes in a Wormhole Router, Jan. 1995, vol. 2. No. 4.
Appenzeller, et al., “User-Friendly Access Control for Public Network Ports,” Department of Computer Science, Stanford University, dated Aug. 31, 1998 in 16 pages.
Apostolopoulos, G., et al.: “IBM Research Report L5: A Self Learning Layer-5 Switch”, Computer Science/Mathematics, RC 21461(96867)Apr. 29, 1999, pp. 1-19.
Arar, Y., Prepaid Internet Access Cards: Instant ISP, http://www.pcworld.com/article/5045/prepaid—internet—access—cards—instant—isp.html, PC World, Jul. 14, 1997, 2 pages.
ATCOM/INFO and Microsoft Plan Large-Scale Deployment of IPORT for Mid-1998, available at http://www.microsoft.com/ presspass/press/1998/mar98/ipttrlpr.mspx.
ATCOM/INFO to Display High-Speed Plug- And-Play Internet Access Software with Microsoft at HITEC, Jul. 22, 1999.
ATCOM/INFO'S IPORT Brings High Speed Internet Access to Hotels in Japan and Mexico; ATCOM and Tut Systems Partner to Expand International Presence of ‘Plug and Play’ Internet Access, May 11, 1999.
Atkins, Internet Security Professional Reference; IP Spoofing and Sniffing, Ch. 6, Dec. 28, 1996.
Auric Web Systems, InterACS: Internet Access Control System: Solutions for the Internet Service Provider, http://web.archive.org/web/19970708234615/http:/www.auricweb.com/InterACS.html, Jul. 8, 1997, 5 pages.
Auric Web Systems, The Intercard System Prepaid Internet Access Cards, http://web.archive.org/web/19970708234054/http:/www.auricweb.com/Accesscard.html, Auric Web Systems, Jul. 8, 1997, 4 pages.
“Auric Web Systems Unveils Software to Reduce The Operating Costs of Internet Service Providers”, http://www.allbusiness.com/technology/software-services-applications-internet/6971623-1.html, AllBusiness, Mar. 25, 1997, 2 pages.
Auric Web Systems, WebGate Card: FAQ, http://web.archive.org/web/19980520083043/http:/www.auricweb.com/faq.html, May 20, 1998, 5 pages.
Babbage, Internet phone—changing the telephony paradigm?, BT Technology Journal, vol. 15, Iss. 2, Apr. 1997.
Badrinath, To Send or not to Send: Implementing Deferred Transmissions in a Mobile Host, Proceedings of 16th International Conference on Distributed Computing Systems, May 27, 1996.
Bagrodia, Vision, Issues, and Architecture for Nomadic Computing, IEEE Personal Communications, Dec. 1995.
Baker, Local Control Over Filtered WWW Access, Fourth International World Wide Web Conference, Dec. 13, 1995.
Baker, M., et al.: Supporting Mobility in MosquitoNet, Proceedings of the 1996 USENIX Technical Conference, San Diego, CA Jan. 1996.
Baker, RFC 1812; Requirements for IP Version 4 Routers, Jun. 1995.
Barnes, Defense Data Network Usage Accounting Enhancement Approaches, Apr. 1989.
Beigl, System Support for Mobile Computing, Computers & Graphics, vol. 20, Iss. 5, Sep. 1996.
Berkowitz, Howard C.: PIER Working Group, Router Renumbering Guide, Aug. 1996, http://tools.ietf.org/pdf/draft-ietf-pier-rr-02.pdf.
Bestavros, A. and Michael J. Ocean, Chapter 12: “Virtualization and Programming Support for Video Sensor Networks with Application to Wireless and Physical Security,” Distributed Video Sensor Networks, 2011, pp. 179-192.
Bieszczad, Towards plug-and-play networks with mobile code, Proceedings of the International Conference for Computer Communications ICCC'97, Mar. 1997.
Bjorn, The Case for Quality of Service on Demand Empirical Evidence from the INDEX Project, ISQE'99, Workshop on Internet Service Quality Economics, Cambridge, MA, USA, Dec. 1999.
Blackwell, Secure Short-Cut Routing for Mobile IP, Proceedings of the USENIX Summer 1994 Technical Conference on USENIX Summer 1994 Technical Conference, Jun. 10, 1994.
Bojorquez, Victor, CheckPoint Software Tech. Ltd., How to Configure Firewall-1 With Connect Control, Oct. 10, 1999.
Borella et al., IETF Internet-Draft—Distributed Network Address Translation, Internet Engineering Task Force, Oct. 1998.
Boutell, CGI Programming in C & Perl, Apr. 19, 1996.
Braden, RFC 1122 Requirements for Internet Hosts—Communication Layers, Oct. 1989.
Brattli, The Software Network, Providing Continuous Network Connectivity for Multihoming Mobile Computers, Dec. 16, 1996.
Broman, Implementation and Analyses of the Mobile-IP Protocol, Jan. 25, 1996.
Brown, A Strategic Plan for Ubiquitous Laptop computing, vol. 41, No. 1, Communications of the ACM, Jan. 1998.
Brown, M-TCP: TCP for Mobile Cellular Networks, Jul. 29, 1997.
Bush, S.F., et al., A control and management network for wireless ATM systems, pp. 459-463 vol. 1, ICC Conference Proceeding Jun. 23-27, 1996. (also listed as—Bush, Mobile ATM Orderwire and Network Configuration 1996.).
Caceres, Fast & Scalable Handoffs for Wireless Internetworks, Proceedings of the 2nd annual international conference on Mobile computing and networking, Nov. 1996.
Caronni et al., Efficient Security for Large and Dynamic Multicast Groups, Jun. 1998.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Plaintiffs Reply to Defendant's First Amended Answer and Counterclaims, Demand for Jury Trial, 6 pages; filed Jul. 31, 2007.
Case No. 07-1946 GPS (VBK) Nomadix, Inc. v. Second Rule LLC, Plaintiff's Reply to Defendant's First Amended Answer and Counterclaims and Demand for Jury Trial, Jul. 31, 2007.
Case No. 07-1946 GPS (VBK) Nomadix, Inc. v. Second Rule LLC, Defendant's First Supplemental Response to Plaintiffs Claim Chart dated Apr. 18, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Declaration of Don P. Foster re: Second Rule LLC's Opening Claim Construction Brief, dated Aug. 4, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Declaration of Mark Lezama in Support of Nomadix, Inc.'s Opening Claim Construction Brief, dated Aug. 4, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Defendant's Opening Claim Construction Brief, dated Aug. 4, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Plaintiffs Opening Claim Construction Brief, Redacted Public Version, dated Aug. 4, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Amended Claim Construction Order (Motion filed on Aug. 4, 2008).
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Declaration of Don P. Foster Re: Second Rule LLC's Reply to Plaintiffs Opening Claim Construction Brief, dated Aug. 22, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Declaration of Douglas G. Muehlhauser in Support of Nomadix Inc.'s Claim Construction Brief, dated Aug. 22, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Declaration of Mark Lezama in Support of Nomadix, Inc.'s Reply Claim Construction Brief, dated Aug. 22, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Defendant's Reply to Plaintiffs Opening Claim Construction Brief, dated Aug. 22, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Reply Claim Construction Brief, dated Aug. 22, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Declaration of Peter Alexander, Ph.D. in Support of Second Rule, LLC for Partial Summary Judgement dated Sep. 4, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Notice of Motion and Motion of Second Rule LLC for Partial Summary Judgment; Sep. 5, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Declaration of Don P. Foster Re: Motion of Second Rule, LLC for Partial Summary Judgement dated Sep. 5, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Defendant's Statement of Uncontroverted Facts and Conclusions of Law in Support of Defendant's Partial Summary Judgement dated Sep. 5, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Memorandum of Law in Support of Motion of Second Rule, LLC for Partial Summary Judgement dated Sep. 5, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Defendant's Supplemental Post-Hearing Claim Construction Brief, dated Sep. 26, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Nomadix, Inc.'s Supplemental Claim Construction Brief, dated Sep. 26, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Order Requesting Supplemental Briefing re: Second Rule LLC's Motion for Partial Summary Judgment, dated Oct. 21, 2008.
Case No. 07-1946 DDP (VBKx) Nomadix, Inc. v. Second Rule LLC, Claim Construction Order dated Oct. 3, 2008.
Case No. 07-1946 GP (VBKx) Nomadix, Inc. v. Second Rule LLC, Expert Report of Peter Alexander, Ph.D.; Oct. 31, 2008.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Defendants' Patent Local Rule 4-2 Preliminary Constructions and Extrinsic Evidence, filed Jan. 21, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Best Western's Supplemental Claim Construction Brief, filed Apr. 16, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Claim Construction Brief of Defendants, filed Apr. 16, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Declaration of Kevin Jeffay, Ph.D., filed Apr. 16, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Declaration of Noah A. Levine in Support of Claim Construction Brief of Defendants filed Apr. 16, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Defendant Barnes & Noble Booksellers, Inc.'s First Amended Answer to Plaintiffs Complaint, filed Apr. 22, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Defendant Mail Boxes Etc., Inc.'s First Amended Answer to Plaintiffs Complaint, filed Apr. 22, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Defendants' SBC (AT&T), Wayport, McDonalds, Barnes & Noble and Mail Boxes etc. Joint Unopposed Motion For Leave to Amend Their Respective First Answers and Counterclaims, filed Apr. 22, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Defendant SBC Internet Services, Inc. D/B/A AT&T Internet Services's (“AT&T”) First Amended Answer to Plaintiffs Complaint, Linksmart Wireless Technology, filed Apr. 22, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., McDonald's Corp.'s First Amended Answer, Defenses, and Counterclaims to Complaint, filed Apr. 22, 2010.
Case No. 2:08-cv-00264-DF-CE, Linksmart Wireless Technology, LLC, v. T-Mobile USA, Inc., et al., Wayport, Inc.'s First Amended Answer, Defenses, and Counterclaims to Complaint, filed Apr. 22, 2010.
Nomadix, Inc.'s Disclosure of Asserted Claims and Infringement Contentions, Nomadix, Inc. v. Hewlett-Packard Company et al., No. CV09-08441 DDP (VBKx), May 24, 2010.
Defendants' Joint Invalidity Contentions, Nomadix, Inc. v. Hewlett-Packard Company et al., No. CV09-08441 DDP (VBKx), Jul. 1, 2010.
Plaintiff's Preliminary Invalidity Contentions and Accompanying Document Production, Nomadix, Inc. v. Hewlett-Packard Company et al., No. CV09-08441 DDP (VBKx), Jul. 1, 2010.
Defendants' Supplemental Joint Invalidity Contentions, Nomadix, Inc. v. Hewlett-Packard Company et al., No. CV09-08441 DDP (VBKx), Jul. 15, 2010.
Plaintiff's Preliminary Invalidity Contentions and Accompanying Document Production Regarding U.S. Patent Nos. 6,996,073 and 7,580,316, Nomadix, Inc. v. Hewlett-Packard Company et al., No. CV09-08441 DDP (VBKx), Jul. 15, 2010.
Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011.
Exhibit A, Asserted Claims, filed in Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011, in 2 pages.
Exhibit B, Supplemental Prior Art List filed in Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011, in 2 pages.
Exhibit Cl, Claim Comparison for U.S. Patent No. 6,130,892 filed in Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011, in 4 pages.
Exhibit C2, Claim Comparison for U.S. Patent No. 7,088,727 filed in Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011, in 7 pages.
Exhibit C3, Claim Comparison for U.S. Patent No. 7,554,995 filed in Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011, in 25 pages.
Exhibit C4, Claim Comparison for U.S. Patent No. 6,636,894, filed in Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011, in 18 pages.
Exhibit C5, Claim Comparison for U.S. Patent No. 7,194,554 filed in Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011, in 18 pages.
Exhibit C6, Claim Comparison for U.S. Patent No. 6,868,399 filed in Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011, in 22 pages.
Exhibit C7, U.S. Patent No. 7,689,716 filed in Defendants' Supplemental Joint Invalidity Contentions, NOMADIX, Inc. v. Hewlett-Packard Company, et al., Case No. 09-CV-8441 DDP (VBKx) and NOMADIX, Inc. v. Solutionic Technologies Limited, Case No. 2:10-CV-00381 DDP (VBKx), (Central District of California, Western Division, and dated Jul. 22, 2011, in 11 pages.
First Claim Construction Order, Nomadix, Inc. v. Hewlett-Packard Company et al., No. CV-09-08441 DDP (VBKx), filed Aug. 31, 2011 in 17 pages.
Second Claim Construction Order, Nomadix, Inc. v. Hewlett-Packard Company, et al., No. CV-09-08441 DDP (VBKx), filed Oct. 24, 2011 in 19 pages.
Case No. 09-CV-8441 DDP (VBKx), Nomadix, Inc. v. Hewlett-Packard Co. et al., Defendants' Supplemental Invalidity Contentions Regarding the Prior Art Work of Mr. Ko Ikudome, dated Nov. 4, 2011, 21 pages including Exhibits I1-I3.
Case No. 09-CV-8441 DDP (VBKx), Nomadix, Inc. v. Hewlett-Packard Co. et al., Defendants' Supplemental Invalidity Contentions Regarding the SPINACH Prior Art and the Vos Publication, dated Nov. 21, 2011, 64 pages including Exhibits I4, S1-S3, and V1-V3.
Case No. 09-CV-8841 DDP (VBKx), Defendants' Supplemental Invalidity Contentions Regarding John Birrell, Jr., received Dec. 23, 2011, 37 pages.
Case No. CV 09-8441 (C.D. Cal. 2009), Nomadix, Inc. v. Hewlett-Packard Co., Complaint filed Nov. 17, 2009.
Case No. CV 10-0381 (C.D. Cal. 2010), Nomadix, Inc. v. SolutionInc Technologies Ltd., Complaint filed Jan. 19, 2010.
Casey, Realizing Mobile Computing Personae, Ph.D. Thesis, Oct. 1995.
Chapman, D. B., et al.: “Building Internet Firewalls,” O'Reilly & Associates, Inc., 103 Morris Street, Suite A Sebastopol, CA 95472, IP3 002885-002944; dated Sep. 1995.
Chapman, Network (In)Security Through IP Packet Filtering, Proceedings of the Third USENIX UNIX Security Symposium, Sep. 1992.
Check Point Ad, Sep. 14, 1998.
Check Point FireWall-I White Paper, v.3, Jun. 1997.
Check Point Software Delivers Breakthrough Security Advancements with Firewall-1 3.0, Oct. 7, 1996.
Check Point SoftwareCheck Point Firewall-I 4.0 Gains Int'l Recognized ITSEC Security Cert., Nov. 9, 1998.
Cheshire, Internet Mobility 4×4, Mobility: Processes, Computers, and Agents, SIGCOMM '96, Aug. 30, 1996.
Cheswick, The Design of a Secure Internet Gateway, Apr. 20, 1990.
Chikarmane, Multicast Support for Mobile Hosts Using Mobile IP, May 16, 1997.
Chikarmane, Network Support for Mobile Hosts in a TCP/IP internetwork, Aug. 1995.
Cho, An Efficient Location and Routing Scheme for Mobile Computing Environments, IEEE Journal on Selected Areas in Communications, Jun. 1995, vol. 13, No. 5, pp. 868-879.
Cisco, “Single-User Network Access Security TACACS+”, Mar. 30, 1995, 9 pages, Cisco White Paper; XP992124521.
Cisco Systems, Inc., LocalDirector Quick Start Guide and User Reference Manual, Version 1.0, Jul. 1996.
Cisco, High-Performance Stateful Firewall Delivers Unparalleled Security, PIX Firewall Data Sheet, 1996.
Cobb, Universal Mobile Addressing, IEEE Workshop on Mobile Computing Systems and Applications, Dec. 8-9, 1994 pp. 24-31.
Collier, Netlets: The Future of Networking, Apr. 4, 1998.
Comer, An Architecture for a Campus-Scale Wireless Mobile Internet, Purdue University Department of Computer Science Technical Report No. CSD-TR 95-058, Sep. 1995.
Comer, “Internetworking with TCP/IP vol. 1, Chapter 10, Principles, Protocols, and Architecture,” 3rd ed., Prentice Hall Mar. 24, 1995.
Complaint for Patent Infringement of U.S. Patent Nos. 6,130,892; 7,088,727; 6,636,894; 6,857,009 and 6,868,399 Unknown Date.
Connection Methods and Concepts for IPORT v2.x, Nov. 1998.
Copper Mountain Introduces CopperPowered Hotel Initiative to Deliver Cost-effective Always-on or Usage-based Broadband Access to Hotel Guests, Dec. 6, 1999, Business Wire.
Dahm, Redirecting your visitors, May 1999.
Damani, ONE-IP: techniques for Hosting a Service on a Cluster of Machines, Jun. 29, 2004.
Data Communication Over the Telephone Network Procedures for Starting Sessions of Data Transmission Over the General Switched Telephone Network, ITU-T Recommendation V.8, approved on Sep. 20, 1994.
Deering et al., Network Working Group RFC 966—Host Groups: A Multicast Extension to the Internet Protocol, Dec. 1985.
Desrosiers, Transparent Access of Remote Resources, IBM Technical Disclosure Bulletin, vol. 27, No. 7B, p. 4230, Dec. 1984.
Devivo, Internet Security Attacks at the Basic Levels, ACP SIGOPS Operating Systems Review, vol. 32, Iss. 2, Apr. 1998.
Droms, R., Dynamic Host Configuration Protocol, Oct. 1993, 1 page, Network Working Group, Request for Comments 1541.
Droms, R., Dynamic Host Configuration Protocol, Mar. 1997, 1 page, Network Working Group, Request for Comments 2131.
Duda, Mobile Agent Architecture for Nomadic Computing, International Conference on Computer Communications, Cannes, Nov. 18-21, 1997, pp. 245-254, Edit. 13.
Edell, R. J. et al., “Billing Using and Pricing for TCP”, IEEE Journal on selected areas in communications, US, IEEE Inc. New York, vol. 13, NR . 7, pp. 1162-1175; XP000525655; ISSN: 0733-8716, Apr. 15, 1995.
Edell, Demand for Internet Access: What we learn from the INDEX trial, Mar. 13, 1999.
Edell, Internet Demand Experiment: Technology and Market Trial, Ph.D. Thesis, Spring, 2001.
Elastic Networks Unveils YesWare; Mobility Software Solution Target Visitor-Based Networking; PRNewswire, Apr. 12, 1999.
Elton, Peter: “Linux as a Proxy Server”, Linus Journal Archive, vol. 1997, Issue 44 (Dec. 1997) Article 3, ISSN: 1075-3583, (“Eldon07”) See http://portal.acm.org/citation.cfm?id=327077.327080.
Estrin, Inter-organization networks: implications of access control: requirements for interconnection protocol, ACM SIGCOMM Computer Communication Review, vol. 16, Iss. 3, Aug. 1986.
Eventou, A., Anywhere Online Access, Auric Web Systems find many applications for its WEBGate card that's a prepaid key to Internet, Dec. 22, 1997, 1 page.
Felten, Web Spoofing: An Internet Con Game, Princeton University Technical Report No. 540-96, Feb. 1997.
Fielding, RFC 2068 Hypertext Transfer Protocol HTTP 1.1, Jan. 1997.
Ford, Securing a Mobile Internet, Oct. 7, 1999.
Furnell et al., A Security Framework for Online Distance Learning and Training, Mar. 1, 1998, vol. 8, No. 3, pp. 236-242.
Giovanardi, Transparent Mobile IP: an Approach and Implementation, Global Telecommunications Conference, 1997, Nov. 3, 1997.
Google Groups: “home network” laptop; Aug. 3, 2004; IP3 002769-70; Newsgroups: comp.sys.sun.admin. Newsgroups: comp.sys.sun.admin.
Google Groups: netswitcher; Aug. 2, 2004; IP3 002516; Newsgroups: comp.os.ms-windows.networking.win95.
Google Groups: network configuration laptop packets; Aug. 2, 2004 IP3 002765-66; Newsgroups: comp.protocols.tcp-ip.
Google Groups: network laptop settings, Jul. 30, 2004; IP# 002467-68; Laptop on Dual Networks; Newsgroups: comp.os.ms-windows.nt.admin.networking.
Google Groups: network settings DHCP mobile, Aug. 3, 2004 IP3 002511-15; Newsgroups: comp.sys.mac.comrn.
Google Groups: redirect “login page” Jul. 28, 2004; IP 3 002873-74; Newsgroups: microsoft.public.inetserver.iis.activeserverpages.
Google Groups: View Thread, Aug. 2, 2004, IP3 002505-06; Newsgroups: microsoft, public.win95.networking.
Google Groups: View Thread, Aug. 2, 2004, IP3 002507-10; Newsgroups: comp.os.os2.networking.tcp-ip.
Grant, TACACS+ Protocol Version 1.75 Internet Draft (TACACS+)/RFC1492, Oct. 1996.
Gray, Mobile Agents for Mobile Computing, May 2, 1996.
Guerin, RadioNet Driver Implementation for the Mobile Internet Router, Jun. 1994.
Gupta, A Client Oriented IP Level Redirection, M.S. Thesis, Aug. 1998.
Gupta, Firewall Traversal for Mobile IP, Mar. 17, 1997.
Gupta, Secure and mobile networking, Mobile Networks and Applications, vol. 3, Iss. 4, Jan. 1998, pp. 381-390.
Gupta, Solaris Mobile IP: Design and Implementation, Feb. 17, 1998.
Haas, Mobile-TCP: An Asymmetric Transport, Proceedings of ICC'97—International Conference on Communications, Jun. 1997.
Hance, Product Information—Netswitcher, the ultimate windows network setup utility; IP 3 002517; Netswitcher.TM., Developed and Marketed by: J.W. Hance, 1950-18 E. Greyhound Pass, Suite 305, Carmel, Indiana 46033 USA, Aug. 2, 2004.
Harrison, Mobile Multicaset (MoM) Protocol, Proceedings of the 3rd annual ACM/IEEE international conference on Mobile computing and networking, Sep. 26, 1997.
Heberlein, Attack Class: Address Spoofing, Proceedings of the Nineteenth National Information Systems Security Conference, Oct. 1996.
Heilbronner, S.: “Requirements for Policy-Based Management of Nomadic Computing Infrastructions,” Proc. Of the Sixth Workshop of the HP Openview University Association (HPOVUA '99), Bologna, Italy, Jun. 1999.
Heilbronner, Nomadic Computing Systems on the Internet—Infrastructure and Management Requirements, Mar. 31, 1997.
Hills, Wireless Data Network Infrastructure at Carnegie Mellon University, Feb. 1996.
Hluchyj, M. G. et al., Queueing Disciplines for Integrated Fast Packet Networks, IEEE 1992, 7 pages.
Hodes, Composable Ad-hoc Mobile Services for Universal Interaction, Aug. 2, 1997.
Hotelier, ATCOM/INFO Makes High-Speed Internet Access to Corporate Networks Secure for Business Travelers, Jul. 17, 1999.
Housel, WebExpress: A Client/intercept based system for optimizing Web browsing in a wireless environment, Mobile Networks & Applications, vol. 3, No. 4, Jan. 1999.
How to Determine the Version of Windows 95/98/Me in Use, http://support.microsoft.com/kb/158238, Jan. 21, 2010.
Internet is the Key, as the Integration of Locations and their Information begins, Nikkei Electronics, Jul. 13, 1998.
Hubbard, Firewalling the Net, BT Technology Journal, vol. 15, Iss. 2, Apr. 1997.
Industry-Leading Internet Access System Now Makes Plug and Play—High-Speed Internet Access for the Road Warrior Easier Than Ever, Jul. 20, 1998.
Inouye, Dynamic Network Reconfiguration Support for Mobile Computers, Proceedings of the 3rd annual ACM/IEEE international conference on Mobile computing and networking, Sep. 26, 1997.
Inouye, Physical Media Independence: System Support for Dynamically Available Network Interfaces, Jan. 20, 1997.
Internet Access: ATCOM/INFO Releases IPORT Central Office Solution. IPORT-CO Makes Plug & Play High-Speed Internet Access Possible too Multiple Properties from a Single Server-Product Announcement, ATCOM-IPORT Press Release Oct. 26, 1998.
Internet Technologies Handbook, Chapter 15, Dial-up Technology, Cisco Systems, Indianapolis: Cisco Press, 1998.
Ioannidis, IP-based Protocols for Mobile Internetworking, Proceedings of the Conference on Communications Architecture & Protocols, Sep. 3, 1991.
Ioannidis, Protocols for Supporting Mobile IP Hosts, Jul. 1992.
ipfwadm-2.3.0, source code module ipfwadm.c, Jul. 30, 1996.
IPORT Central Office Solution, Nov. 1998, pp. 1-20.
Jain, PC-notebook based mobile networking: Algorithms, architectures and implementations; 1CC95 vol. 2, Jun. 1995.
Johnson, D. B., “Ubiquitous Mobile Host Internetworking”, 0-8186-4000-6/93 1993 IEEE, pp. 85-90.
Johnson, Mobile Host Internetworking Using IP Loose Source Routing, Carnegie Mellon University Technical Report No. CS-93-128, Feb. 1993.
Johnson, Protocols for Adaptive Wireless and Mobile Networking, Feb. 1996.
Johnson, Scalable and robust internetwork routing for mobile hosts, Proceedings of the 14th International Conference on Distributed Computing Systems, Jun. 21, 1994.
Johnson, Scalable Support for Transparent Mobile Host Internetworking, Wireless Networks, vol. 1, Iss. 3, Sep. 1995.
Kaashoek et al., Efficient Reliable Group Communication for Distributed Systems, Jul. 1992.
Kalkbrenner, et al., Quality of Service (QoS) in Distributed Hypermedia-Systems, Jul. 1995, IEEE, v 10-8186-7180, pp. 529-534.
Kausar, et al., A Charging Model for Sessions on the Internet, European conference on Multimedia Applications, Services and Techniques, Department of Computer Science, University College London, 1999. pp. 246-261.
Katz, The Bay Area Research Wireless Access Network (BARWAN), Proceedings of the 279 KATZ, The Bay Area Research Wireless Access Network (BARWAN), Proceedings of the 41st IEEE International Computer Conference, Feb. 25-28, 1996.
Kent et al., RFC 2401—Security Architecture for the Internet Protocol, Network Working Group, Nov. 1998.
Kleinrock, L.: “Nomadicity in the NII”, Computer Science Department, UCLA, Los Angeles, CA; Cross-Industry Working Team Papers & Reports, Pub. Date: Jun. 1995.
Kleinrock, L.: “Nomadic Computing”, Computer Science Department, UCLA, Los Angeles, CA; Information Network and Data Communication' IFIP/ICCC International Conference on Information Network and Data Communication Pub. Date: Jun. 1996, Trondheim, Norway.
Kleinrock, L.: “Nomadicity: Anytime, Anywhere in a Disconnected World”, Computer Science Department, UCLA, Los Angeles, CA; Mobile Network and Applications, Special Issue on Mobile Computing and System Services Pub. Date Dec. 1996, vol. 1, Issue 4.
Kleinrock, L.: “Nomadic Computing—An Opportunity”, Computer Science Department, UCLA, Los Angeles, CA; ACM SIGCOMM, Computer Communications Review, Pub. Date: Jan. 1995, vol. 25, Issue 1.
Kleinrock, L.: “Nomadic Computing” (Keynote address) Int'l Conf. on Mobile Computing and Networking, Nov. 1995, Berkley, California, ACM.
Koblas, Socks, Proceedings of the Third USENIX UNIX Security Symposium (Baltimore, MD: USENIX Association), Sep. 1992.
Korba, Larry, “Security System for Wireless Local Area Networks,” Ninth IEEE International Symposium on Personal, Indoor and Mobile Radio Communications, Sep. 8, 1998, pp. 1550-1554.
Kostick, Building a Linux Firewall (Linux Journal 24), Apr. 1, 1996.
Kostick, C.: “IP Masquerading with Linux”, Linux Journal Issue 27, Jul. 1996 (“Kostic96”) See http://delivery.acm.org/10.1145/330000/325560/a3-kostick.html?key1=325560&key2=59 . . . Oct. 16, 2008.
Kostick, “System Administration, IP Masquerading Code Follow-up, vol. 1997, Iss. 43, Nov. 1997 (This is a follow-up article to the author's ‘IP Masquerading with Linux’, in Linux Journal Issue 27)”.
Kruus, Peter S., A Survey of Multicast Security Issues and Architectures, Oct. 5-8, 1998.
Kuri, Jurgen, Gruppenreise Ins Internet Gemeinsamer Internet—Zugang durch das LAN, Aug. 17, 1998, pp. 118-122.
Kunzinger, Network Layer Mobility: Comparison of CDPD and Mobile-IP, IBM Technical Report 29.2003, 1995.
La Porta, Challenges for nomadic computing: Mobility management and wireless communications, Mobile Networks and Applications, vol. 1, Iss. 1, Aug. 1996.
Lain Langdon, Education for Changing Times—An Online Learning Framework, Oct. 15, 1996.
Lear, RFC 1627, Network 10 Considered Harmful, Jul. 1994.
Lee, Adaptive Network Support for Mobile Multimedia, Proceedings of the 1st annual international conference on Mobile computing and networking, Nov. 13, 1995.
Lee, Chooi-Tian and J.W. Harris, “Designing a Virtual Access Control Configuration Protocol for Implementation over ISDN and Shared-Media Networks,” Proceedings 21st IEEE Conference on Local Computer Networks, Oct. 13, 1996, pp. 116-125.
Leech, RFC 1928; SOCKS Protocol Version 5, Mar. 1996.
Leu, Implementation considerations for Mobile IP, Proceedings of the 21st International Computer Software and Applications Conference, Nov. 11, 1997.
Levene, Mark and Loizou, George, A Guided Tour of Relational Databases and Beyond, Springer-Verlag London Limited, Great Britain, 1999.
Leveridge, Campus World and BT's On-Line Education Services, BT Technology Journal, Apr. 1997.
Li and Leung, Supporting Personal Mobility for Nomadic Computing Over the Internet, ACM SIGMOBILE Mobile Computing and Communications Review, Apr. 1997.
Lin, An Architecture for a Campus-Sized Wireless Mobile Network, Ph.D. Thesis, Dec. 1996.
Lioy, Providing TCP-Level Services to Mobile Computers, M.S. Thesis, University of Waterloo, Waterloo, Ontario, Canada, Aug. 1997.
Livingston Enterprises, Inc., ChoiceNet Administrator's Guide, Jan. 1997, Pleasanton, CA, available at http://portmasters.com/tech/docs/pdf/choice.pdf.
Lo et al., IETF Internet-Draft—Realm Specific IP: A Framework, Internet Engineering Task Force, Feb. 1999.
Loon, Alleviating the Latency and Bandwidth Problems in WWW Browsing, Proceedings of the USENIX Symposium on Internet Technologies and Systems on USENIX Symposium on Internet Technologies and Systems, Dec. 8, 1997.
Maciel, Dynamic Gateways: a novel approach to improve networking performance and availability on parallel servers, Apr. 21, 1998.
Macker, Mobile Ad Hoc Networking and the IETF, ACM SIGMOBILE Mobile Computing and Communications Review, vol. 3, Iss. 1, Jan. 1999.
Major telecom Company Launches Education Internet Service for Schools, Sep. 20, 1995.
Making the Most of Home Pages, E-mail, The Internet and Presentation Graphics, The Journal, Aug. 1, 1998.
Manuel Gunter, Virtual Private Networks over the Internet, Aug. 3, 1998.
Maruyama et al. “A secure LAN sockets system for everyone which need not modify existing DHCP clients”, Study Report of Information Processing Society of Japan, Jul. 16, 1999, vol. 99, No. 56, pp. 131-136.
McKinley, R., Prepaid Internet Access Cards, http://www.cardtrak.com/news/1997/07/14/prepaid—internet—access—cards, CardTrak.com, Jul. 14, 1997, 1 page.
Messmer, “Gateway Handles Thorny Problems with Addressing IP Networks”, Network World, p. No. 8, Nov. 28, 1994.
Messmer, New room-service fare: High-speed Internet access, Dec. 7, 1998.
Michard, A. et al.; The Aquare/le resource discovery system; Computer Networks and ISDN Systems; 1998; pp. 1185-1200; vol. 30, NR. 13; North Holland Publishing; Amsterdam, NL; XP004147404; ISSN: 0169-7552.
Microsoft TechNet: Dial-Up Networking and Mobile Computing: The Basics, http://technet.microsoft.com/en-us/library/cc751107, 2010.
Microsoft WindowsNT ResourceKit, Version 4.0, Supplement One, Microsoft Press, 1997.
Microsoft WindowsNT Workstation ResourceKit: Comprehensive Resource Guide and Utilities for Windows NT Workstation Version 4.0, Microsoft Press, 1996.
Microsoft Computer Dictionary, Fourth Edition, Microsoft Press, 1999.
Moby Dick, The Mobile Digital Companion, LTR 20422, Jul. 1997.
Mogul, RFC 950; Internet Standard Subnetting Procedure, Network Working Group, Aug. 1985.
Moore, Campus World, 1998.
Myles, Comparison of Mobile Host Protocols for IP, Apr. 14, 1993.
Mysore, A New Multicasting-based Architecture for Internet Host Mobility, Sep. 26, 1997.
Nelson, Context-Aware and Location Systems, Jan. 1998.
Network Working Group Request for Comments: 1009—Requirements for Internet Gateways (Jun. 1987).
Network Working Group Request for Comments: 1027—Using ARP to Implement Transparent Subnet Gateways (Oct. 1987).
Network Working Group Request for Comments: 1034—Domain Names—Concepts and Facilities (Nov. 1987).
Network Working Group Request for Comments: 1531—Dynamic Host Confirmation Protocol (Oct. 1993).
Network Working Group Request for Comments: 1919—Classical Versus Transparent IP Proxies (Mar. 1996).
Network Working Group Request for Comments: 1945—Hypertext Transfer Protocol—HTTP/1.0 (May 1996).
Network Working Group Request for Comments: 826—Ehternet Address Resolution Protocol (Nov. 1982).
Network Working Group Request for Comments: 894—Standards for Transmission of IP Datagrams Over Ethernet Networks (Apr. 1984).
Network Working Group Request for Comments: 925—Multi-LAN Address Resolution (Oct. 1984).
Networking Working Group, Radius Accounting, Request for Comments: 2139, Obsoletes: 2059; Category: Informational, C. Rigney, Livingston, Apr. 1997; IP 3 002991-003013.
Neves, Adaptive Recovery for Mobile Environments, Communications of the ACM, vol. 40, Iss. 1, Jan. 1997.
Newman, Flow Labeled IP: A Connectionless Approach to ATM, Proceedings of the Conference on Computer Communications (IEEE Infocom), Mar. 24, 1996.
Newton, Harry, Newton's Telecom Dictionary, p. 206, Telecom Books and Flatiron Publishing, Miller Freeman, Inc., New York, NY, 1998.
Nomadicity in the National Information Infrastructure, a white paper published by the Cross-Industry Working Team (XIWT) at http://www.xiwt.org/documents/Nomadicity.html.
Nomadix Joins Copper Mountain Networks to Provide High-Speed Internet Access to Hotels Guests, Dec. 6, 1999, Business Wire.
Office Action mailed Oct. 5, 2005 for U.S. Appl. No. 09/684,937, filed Oct. 5, 2005.
Official Communication mailed Nov. 22, 2005 for EP Patent Application No. EP 98 909 121.0, Nov. 22, 2005.
PCT Application and its English translation for Chinese patent Application No. 98805023.4., Jan. 12, 2005.
Peine, An Introduction to Mobile Agent Programming and the Ara System, University of Kaiserslautern Technical Report ZRI-Report Jan. 1997.
Perkins, C. E. et al.: “DHCP for mobile networking with TCP/IP” Proceeding IEEE International Symposium on Computer and Communications, Jun. 27, 1995, pp. 255-261, XP002132695.
Perkins, “Providing Continuous Network Access to Mobile Hosts Using TCP/IP.” Computer Networks and ISDN Systems, Nov. 1993.
Perkins, A Mobile Networking System Based on Internet Protocol (IP) In USENIX Symposium on Mobile and Location-Independent Computing, Aug. 2, 1993.
Perkins, C. E. Ed—Institute of Electrical and Electronics Engineers: “Mobile-AP, AD-HOC Networking, and Nomadicity” Proceedings of the 20th Annual International Computer Software and Applications Conference (COMPSAC). Seoul, Aug. 21-23, 1996, Proceedings of the Annual International Computer Software and Applications Conference (COMPSAC), Los Alamitos, IEEE COMP, vol. Conf. 20, Aug. 21, 1996, pp. 472-476, XO 000684381, ISBN 0-8186-7579-9.
Perkins, Highly Dynamic Destination-Sequenced Distance-Vector Routing (DSDV) for Mobile Computers, ACM SIGCOMM Computer Communication Review, vol. 24, Iss. 4, Oct. 1994.
Perkins, Internet Mobile Host Protocol (IMHP), Jun. 13, 1994.
Perkins, Mobile IP; Communications Magazine, IEEE vol. 35, Issue 5, May 1997.
Perkins, Mobile networking through Mobile IP, IEEE Internet Computing, Jan. 1998.
Perkins, Mobile-IP, AD-HOC Networking, and Nomadicity; Proceedings of the 20th Annual International Computer Software and Applications Conference (COMPSAC), Seoul, Aug. 21, 1996.
Perkins, RFC 2002: IP Mobility Support, Oct. 1996.
Perkins, Mobility Support in IPv6, Proceedings of the 2nd annual international conference on Mobile computing and networking, Nov. 10, 1996.
Perkins, et al., Resource discovery protocol for mobile computing, Mobile Networks and Applications 1 (1996) 447-455.
Person, et al., Using Windows 95, Platinum Edition, pp. 205-209,812-813, Que Corporation, 1996.
Pissinou, A middleware-based architecture to support transparent data access by mobile users in heterogeneous environments, Research Issues in Data Engineering, Feb. 28, 2000.
Pitoura, Building Information Systems for Mobile Environments, Proceedings of the third international conference on Information and knowledge management, Nov. 29, 1994.
Pitoura, Dealing with Mobility: Issues and Research Challenges; Purdue University Computer Science Department Technical Report CSD-TR-93-070, Nov. 1993.
Pix, Network Translation Inc., Private Internet Exchange (PIX) Technical White Paper (Network Address Translation and the Private Internet Exchange, May 16, 1995.
Pix, Network Translation Inc., Private Internet Exchange (PIX) Brochure, 1994.
Pix, Network Translation Inc., Private Internet Exchange (PIX) Technical White Paper, May 16, 1995.
Pix, Network Translation Inc., Private Internet Exchange Reference Manual, Oct. 5, 1995.
Plummer, D., An Ethernet Address Resolution Protocol or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware; Nov. 1982; 8 pages; Network Working Group, Request for Comments 826.
Poger, Secure Public Internet Access Handler (SPINACH), Proceedings of the USENIX Symposium on Internet Technologies and Systems, Dec. 8, 1997.
Polydorou, Performance Analysis and Comparison of Two Wireless Wide Area Networks, Dec. 1996.
Poslad, Software Agents for Future Communication Systems—Chapter 9: Agent-Oriented Middleware for Integrating Customer Network Services, Jun. 11, 1999, pp. 221-242.
Postel, RFC 793, Transmission Control Protocol, Sep. 1981.
Rajagopalan, An Adaptive Location Management Strategy for Mobile IP, Proceedings of the 1st annual international conference on Mobile computing and networking, Nov. 13, 1995.
Rajagopalan, Mobile Internetworking Protocols for Wireless Networks with ATM Backbones, MILCOM '97 Conference Proceedings, Nov. 2, 1997.
Rao, A Proxy-Based Personal Portal, Proceedings of the WebNet99 Conference, Hawaii, Oct. 1999, p. 913.
Rao, iProxy: A Programmable Proxy Server, Poster Proceedings of the WebNet99 Conference, Oct. 1999, p. 1676.
Rao, A Proxy-Based Personal Web Archiving Service, ACM SIGOPS Operating Systems Review, Jan. 2001.
Redi, Mobile IP: A Solution for Transparent, Seamless Mobile Computer Communications, Upcoming Trends in Mobile Computing and Communications, Jul. 1998.
Rekhter, RFC 1597, Address Allocation for Private Internets, Mar. 1994.
Rekhter, RFC 1918, Address Allocation for Private Internets, Feb. 1996.
Request for Reexamination for U.S. Patent No. 6,130,892, Feb. 15, 2005.
Richards, et al., Mapping User Level QOS from a Single Parameter, 1988, pp. 1-15.
Rigney, RFC 2138, Remote Authentication Dial In User Service (RADIUS), Apr. 1997.
Rigney, RFC 2058, Remote Authentication Dial In User Service (RADIUS), Jan. 1997.
Rigney, RFC 2059, RADIUS Accounting, Jan. 1997.
Rizzo, A Dynamic Pricing Framework to Support a Scalable, Usage-based Charging Model for Packet-switched Networks, May 7, 1999.
Robinet, An implementation of a gateway for hierarchically encoded video across ATM and IP networks, Proceedings of the IFIP TC-6 Eighth International Conference on High Performance Networking, Sep. 21, 1998.
Rowe, Reliability of WWW Name Servers, Computer Networks and ISDN Systems, Apr. 1995.
Rupp, INDEX: A Platform for Determining how People Value the Quality of their Internet Access, INDEX Project Report #98-010P, May 1998.
Salifu, Abdul-Mumin, “Detection of Man-in-the-Middle Attack in IEEE 802.11 Networks,” M.S. Thesis, Kwame Nkrumah University of Science and Technology, May 2011, 79 pages.
Sandhu et al., Decentralized Group Hierarchies in UNIX: An Experiment and Lessons Learned, Oct. 1998.
Sato, Yutaka: “Details of Functions of Multi-purpose Proxy Server DeleGate-Access/Route Control and Protocol Conversion”, Interface vol. 21, No. 9, p. 130-146, Sep. 1995.
Scale, How to Cost-Effectively Scale Web Servers, Packet Magazine, Third Quarter, Sep. 1996.
Schilit, A System Architecture for Context-Aware Mobile Computing, Ph.D. Thesis, May 1995.
Schooler, A Distributed Architecture for Multimedia Conference Control, Nov. 1991.
Shamsuddin, Positioning of Wireless Broadband, Jun. 1996.
Short, Joel E.: “Auto-Porting and Rapid Prototyping with Application to Wireless and Nomadic Network Algorithms, A dissertation submitted in partial satisfaction of the requirement for the degree of Doctor of Philosophy in Computer Science,” University of California, Los Angeles, Published Oct. 26, 1996; pp. xv, 118-124; Co+B343pyright Jan. 16, 1977.
Short, Mobile Wireless Network System Simulation, Wireless Networks, vol. 1, Iss. 4, Nov. 1995.
Simpson and Weiner, The Oxford English Dictionary, 2nd Edition, vol. III, pp. 514-515, Oxford University Press, 1989.
Simpson and Weiner, The Oxford English Dictionary, 2nd Edition, vol. VII, p. 881, Oxford University Press, 1989.
Single-User Network Access Security TACACS+ http://www.cisco.com/warp/public/614/7.html IP3 002876-002884; dated Aug. 10, 2005.
Srisuresh et al., RFC 2663—IP Network Address Translator (NAT) Terminology and Considerations, Network Working Group, Aug. 1999.
Stevens, ARP: Address Resolution Protocol; TCP Illustrated, Addison-Wesley Professional, Jan. 10, 1994.
Stevens, R, TCP Connection Handshake, Addison-Wesley Professional, Jan. 10, 1994.
Stevens, W. R.; TCP/IP Illustrated, vol. 1—The Protocols; Addison-Wesley Professional Computing Series; pp. 53-62 and 231-235 (Printed Jul. 2001).
Stoll, Frank, “The Need for Decentralization and Privacy in Mobile Communications Networks,” Computers & Security vol. 14 iss. 6, 1995, pp. 527-539.
Sudan, Gateway Based Approach for Conducting Multiparty Multimedia Sessions over Heterogeneous Signaling Domains, Proceedings of the INFOCOM '97 Sixteenth Annual Joint Conference of the IEEE Computer and Communications Societies, Apr. 9, 1997.
Tanenbaum, Andrew S.: “Computer Networks”, 1996, pp. 420-424, 3rd edition, Prentice Hall of India, New Delhi, India.
Tantawy, Ahmed N. and Martina Zitterbart, “A Scheme for High-Performance LAN Interconnection Across Public MAN's,” IEEE Journal on Selected Areas in Communications, vol. 11, No. 8, Oct. 1993, pp. 1133-1144.
Taylor, Internetwork Mobility The CDPD Approach, Jun. 11, 1996.
Team Internet Technical Specifications, Infomine Network Solutions and Services, Helena, Montana, Sep. 7, 1998.
Teraoka, A Network Architecture Providing Host Migration Transparency, ACM SIGCOMM Computer Communication Review, Sep. 1991.
Teraoka, Host Migration Transparency in IP Networks: The VIP Approach; ACM SIGCOMM Computer Communication Review, vol. 23, Iss. 1, Jan. 1993.
Teraoka, VIP: A Protocol Providing Host Mobility, Communications of the ACM, Aug. 1994.
The ‘Security Digest’ Archives, TCP-IP Distribution List, Aug. 1994, http://securitydigest.org/tcp-ip/archive/1994/08.
The Independent, Hardware hustle hits the classroom, May 20, 1996.
Thomsen, Mobile Agents—The new paradigm in computing, ICL Systems Journal, vol. 12, Issue 1, pp. 14-40, May 1997.
TIS Firewall Toolkit Overview, Jun. 30, 1994.
Troy, Timothy N., “Servicing with Software,” Hotel & Motel Management, Sep. 20, 1993, p. 28, vol. 208, No. 16, Advanstar Communications, Inc.
Tsuchiya et al., Extending the IP Internet Through Address Reuse, ACM SIGCOMM Computer Communication Review, Jan. 1993, vol. 23, Issue 1.
Tut Systems Launches Hotel Internet Management System, PublicPort (TM) Latest Addition to Multi-Tenant Unit Product Line Allows Hotel Owners to Use Existing Copper Infrastructure to Provide ‘Plug and Play’ Internet Services, Jun. 23, 1999.
Valencia, RFC 2341, Cisco Layer Two Forwarding (Protocol) “L2F”, May 1998.
Varaiya, INDEX Project Proposal—Executive Summary, INDEX Project Report #98-005P, Aug. 6, 1996.
Venema, TCP Wrapper; Network monitoring, access control, and booby traps, Proc. of the Third Usenix UNIX Security Symposium, USENIX Association, Sep. 1992.
Vos, Jos and Willy Konijnenberg, Linux Firewall Facilities for Kernel-level Packet Screening, Nov. 18, 1996, 19 pages.
Wahl, RFC 2256, A Summary of the X.500(96) User Schema for use with LDAPv3, Dec. 1997.
Webb, Automatic Redirection, Jun. 8, 1997.
Windows History: Windows Desktop Timeline, Jun. 30, 2003, available at http://www.microsoft.com/windows/ WinHistoryProGraphic.mspx on Jan. 21, 2010, Microsoft, pp. 1-2.
Xylomenos, IP Multicast for Mobile Hosts, IEEE Communications Magazine, vol. 35, Iss. 1, Jan. 1997.
Yeom, IP Multiplexing by Transparent Port-Address Translator, USENIX Tenth System Administration Conference, Sep. 29, 1996.
Zhao, Flexible Connectivity Management for Mobile Hosts, Stanford University Technical Report No. CSL-TR-97-735, Sep. 1997.
U.S. Appl. No. 09/295,966, filed Apr. 21, 1999.
U.S. Appl. No. 10/919,214, filed Aug. 16, 2004-file history of U.S. Publication No. 2005/0021943, published Jan. 27, 2005.
U.S. Appl. No. 11/375,740, filed Mar. 14, 2006-file history of U.S. Publication No. 2006/0174019, published Aug. 3, 2006.
U.S. Appl. No. 11/645,924, filed Dec. 26, 2006- file history of U.S. Publication No. 2007/0294417, published Dec. 20, 2007.
U.S. Appl. No. 60/072,175 by Brothers, filed Jan. 22, 1998.
U.S. Appl. No. 60/111,497 by Kleinrock, filed Dec. 8, 1998.
Worcester, Barbara A., “Interfacing Isolated Information”, Hotel and Motel Management (H&MM), Apr. 6, 1998, vol. 213 Issue 6, p. 40-42.
American Hotel & Motel Association, “HITIS Posting Interface with POS Extensions—Executive Summary”, pulication date unknown, downloaded on Dec. 4, 2012 from http://web.archive.org/web/19970701082202/http://www.hitis.org/postopms/posovrvw1.doc.
American Hotel & Motel Association, “AH&MA Sanctions Mapping the HITIS Interface Protocol to XML”, publication date unknown, downloaded on Dec. 4, 2012 from http://web.archive.org/web/20000817191827/http://www.hitis.org/announce-calendar/xmlmapp.

Related Publications (1)

	Number	Date	Country
	20120278494 A1	Nov 2012	US

Provisional Applications (1)

	Number	Date	Country
	60161181	Oct 1999	US

Continuations (1)

	Number	Date	Country
Parent	09693512	Oct 2000	US
Child	13462585		US

Systems and methods of communicating using XML

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

US Classifications

Field of Search

US

International Classifications

Disclaimer

Abstract