US7359973B2 - Home-networking - Google Patents

Home-networking Download PDF

Info

Publication number
US7359973B2
US7359973B2 US09/810,421 US81042101A US7359973B2 US 7359973 B2 US7359973 B2 US 7359973B2 US 81042101 A US81042101 A US 81042101A US 7359973 B2 US7359973 B2 US 7359973B2
Authority
US
United States
Prior art keywords
gateway device
host system
client devices
home
home gateway
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime, expires
Application number
US09/810,421
Other versions
US20010036192A1 (en
Inventor
David Clyde Chiles
Eric Bosco
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Meta Platforms Inc
Original Assignee
AOL LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by AOL LLC filed Critical AOL LLC
Priority to US09/810,421 priority Critical patent/US7359973B2/en
Assigned to AMERICA ONLINE, INC. reassignment AMERICA ONLINE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BOSCO, ERIC, CHILES, DAVID CLYDE
Publication of US20010036192A1 publication Critical patent/US20010036192A1/en
Assigned to AOL LLC, A DELAWARE LIMITED LIABILITY COMPANY (FORMERLY KNOWN AS AMERICA ONLINE, INC.) reassignment AOL LLC, A DELAWARE LIMITED LIABILITY COMPANY (FORMERLY KNOWN AS AMERICA ONLINE, INC.) CONVERSION Assignors: BOSCO, ERIC, CHILES, DAVID CLYDE
Assigned to AOL LLC, A DELAWARE LIMITED LIABILITY COMPANY (FORMERLY KNOWN AS AMERICA ONLINE, INC.) reassignment AOL LLC, A DELAWARE LIMITED LIABILITY COMPANY (FORMERLY KNOWN AS AMERICA ONLINE, INC.) CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF THE ASSIGNOR PREVIOUSLY RECORDED ON REEL 020331 FRAME 0062. ASSIGNOR(S) HEREBY CONFIRMS THE NAME OF THE ASSIGNOR SHOULD BE AMERICA ONLINE, INC., NOT THE INVENTORS. Assignors: AMERICA ONLINE, INC.
Application granted granted Critical
Publication of US7359973B2 publication Critical patent/US7359973B2/en
Assigned to BANK OF AMERICAN, N.A. AS COLLATERAL AGENT reassignment BANK OF AMERICAN, N.A. AS COLLATERAL AGENT SECURITY AGREEMENT Assignors: AOL ADVERTISING INC., AOL INC., BEBO, INC., GOING, INC., ICQ LLC, LIGHTNINGCAST LLC, MAPQUEST, INC., NETSCAPE COMMUNICATIONS CORPORATION, QUIGO TECHNOLOGIES LLC, SPHERE SOURCE, INC., TACODA LLC, TRUVEO, INC., YEDDA, INC.
Assigned to AOL INC. reassignment AOL INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AOL LLC
Assigned to QUIGO TECHNOLOGIES LLC, MAPQUEST, INC, LIGHTNINGCAST LLC, YEDDA, INC, NETSCAPE COMMUNICATIONS CORPORATION, TACODA LLC, GOING INC, SPHERE SOURCE, INC, TRUVEO, INC, AOL ADVERTISING INC, AOL INC reassignment QUIGO TECHNOLOGIES LLC TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS Assignors: BANK OF AMERICA, N A
Assigned to FACEBOOK, INC. reassignment FACEBOOK, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AOL INC.
Assigned to META PLATFORMS, INC. reassignment META PLATFORMS, INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: FACEBOOK, INC.
Adjusted expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4633Interconnection of networks using encapsulation techniques, e.g. tunneling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/2514Translation of Internet protocol [IP] addresses between local and global IP addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5007Internet protocol [IP] addresses
    • H04L61/5014Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5038Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083Network architectures or network communication protocols for network security for authentication of entities using passwords
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803Home automation networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities

Definitions

  • This invention relates to connecting multiple home-networked client devices to a host system.
  • An increasing number of households have more than one personal computing device.
  • ISP Internet Service Provider
  • ISP Internet Service Provider
  • the host system may recognize the entire network as a single device rather than recognizing the individual devices within the network or users of those individual devices.
  • Failing to recognize and thus distinguish the individual devices or individual users of the devices may prevent the host system from enforcing or enabling preferences and features otherwise distinguishable among individual devices or users, such as parental access controls.
  • the individual client devices and users of the client devices may not be able to access and receive back from the host certain host-maintained preferences, such as personal identification settings, personal web pages, account information, wallet information, and financial information.
  • home-networked client devices are connected to a host system that assigns independent Internet addresses to the home-networked client devices using a home gateway device that is connected to the home-networked client devices through a network.
  • the home gateway device which may be physically located in a personal residence, generally includes a communication device to communicate with the host system over a single communication tunnel established between the home gateway device and the host system.
  • the home-networked client devices communicate with the host system through the home gateway device over the single communication tunnel.
  • the system configuration enables the host system to establish individual communication sessions with the home-networked client devices over the single communication tunnel and to assign independent Internet addresses to the home-networked client devices.
  • Implementations may include one or more of the following features.
  • the home gateway device and the home-networked client devices may be physically located in a personal residence.
  • the personal residence may include a single family dwelling.
  • the home-networked client devices may include wireless client devices that may be connected to the home gateway device through a wireless network such that the wireless client devices may operate outside of the personal residence.
  • the home-networked client devices may establish simultaneous individual communication sessions with the host system over the single communication tunnel.
  • Each home-networked client device may be assigned an independent Internet address by the host system, which may include an Internet Service Provider.
  • the home gateway device may communicate with the multiple home-networked client devices using a first protocol and may communicate with the host system using a second protocol.
  • the first protocol and the second protocol may be the same protocol, or the second protocol may differ from the first protocol.
  • the home gateway device may include one or more modules that are structured and arranged to convert between the first protocol and the second protocol.
  • the first protocol may include PPPoE and the second protocol may include L2TP.
  • the home-networked client devices may be PPP enabled.
  • the home gateway device may emulate a PPPoE access concentrator and an L2TP access concentrator.
  • the communication device may include a modem, such as a cable modem, a satellite modem, or a DSL modem.
  • the multiple home-networked client devices may include client devices having computer software that enables the client devices to interface with the home gateway and to communicate with the host system through the home gateway device, such that the host system is able to recognize independent client devices.
  • the independent client devices may be recognized by the host system through the use of unique identifiers assigned to each of the client devices by the host system during the established communication session.
  • the unique identifiers may be unique to the client devices and/or to users of the client devices.
  • a unique identifier may include an independent Internet address, and also may include a unique identifier for a user of a client device combined with an independent Internet address assigned to the client device.
  • a unique identifier may include a screen name for a user of the client devices.
  • the user When the user has a unique identifier that is combined with the independent Internet address assigned by the host system to the client device, the user may be enabled to access individual information maintained by the host system for that particular user. Additionally, the host system may be enabled to enforce host-based parental or other controls. Individual information maintained by the host system may include wallet information, calendar information, and personalized web page information.
  • the home gateway device may include a personal computer and/or a server.
  • the network between the home gateway device and the home-networked client devices may include a wired network, a wireless network, and/or any combination of a wired and a wireless network.
  • the network may include an Ethernet network.
  • the home gateway device may include a dynamic host configuration protocol module and an L2TP access concentrator. Multiple home-networked client devices may communicate with the home gateway device using the dynamic host configuration protocol module. The home gateway device and the home-networked client devices may communicate over the network using DHCP, and the home-networked client devices may be assigned a single address that is used in communications with the home gateway device and the host system. The single communication tunnel established between the home gateway device and the host system may be established over a broadband network.
  • the dynamic host configuration module may be configured to facilitate communications between the host system and the home-networked client devices to enable the host system to enforce host-based parental controls. The assignment of unique addresses to the home-networked client devices may be performed upon bootup of the client devices.
  • FIG. 1 is a block diagram of a home networking system.
  • FIG. 2 is a block diagram of a client device of the system of FIG. 1 .
  • FIG. 3 is a block diagram of a host system of the system of FIG. 1 .
  • FIG. 4 is a block diagram of an implementation of the home networking system of FIG. 1 .
  • FIG. 5 is a block diagram of the home networking system of FIG. 1 illustrating one protocol implementation.
  • FIG. 6 is a block diagram of the components which may be included in a client device of the system of FIG. 1 .
  • FIG. 7 is block diagram of the components which may be included in a home gateway device of the system of FIG. 1 .
  • FIG. 8 is a more detailed block diagram of the home gateway device of FIG. 7 .
  • FIG. 9 a is a flow chart of a process used to enable a home network.
  • FIG. 9 b is a flow chart of a process used to enable a home network.
  • FIGS. 10 a - 10 d are block diagrams of a protocol enabling communication between the components of the home networking system.
  • FIG. 11 is a block diagram of the home gateway device including a NAT module.
  • FIG. 12 is a block diagram of the home networking system using a NAT module.
  • FIG. 13 is a block diagram of the home gateway device including a DHCP module.
  • FIG. 14 is a flow chart of a process used to enable a home network.
  • a home networking system 100 typically includes multiple home-networked client devices 105 (“client devices”) connected through a network 110 to each other and to a home gateway device 115 .
  • the home gateway device 115 typically connects to the host system 130 through a communication device 120 over communication links 125 .
  • the home networking system 100 enables the client devices 105 to communicate with the host system 130 through the home gateway device 115 using the single communication device 120 .
  • the client devices 105 , the home gateway device 115 , and the communication device 120 may be physically located in a personal residence, as indicated by the dashed lines shown in FIG. 1 .
  • the home networking system 100 enables the host system 130 to assign unique identifiers (e.g., independent Internet addresses) to each of the client devices 105 through the home gateway device 115 over a single communication link 125 established between the home gateway device 115 and the host system 130 .
  • the home networking system 100 also enables the client devices 105 to access information maintained by the host system 130 for a particular client device 105 or a particular individual user of the client devices 105 .
  • the home networking system 100 enables the host system 130 to maintain and enforce individual preferences associated with a particular client device 105 or a user of the client devices 105 through using the host-assigned unique identifiers and/or some combination of the host-assigned unique identifiers with other identifiers (e.g., login name, account number, screen name, and password).
  • identifiers e.g., login name, account number, screen name, and password
  • the client devices 105 and the home gateway device 115 typically are located in a physical place that enables the home gateway device 115 to network with the client devices 105 .
  • the home gateway device 115 is physically located in a personal residence (e.g., a single-family dwelling, a house, a townhouse, an apartment, or a condominium).
  • the client devices 105 may be physically located such that communications over the network 110 with the home gateway device 115 are enabled and maintained.
  • the client devices 105 also may be physically located in the personal residence.
  • the location of the home gateway device 115 in the personal residence does not preclude one or more of the client devices 105 from being networked to the home gateway device 115 from a remote location. Nor does it preclude use of one or more of the client devices 105 from outside of the personal residence or communication by those devices with the host system 130 through the home gateway device 115 .
  • the client devices 105 may include one or more portable computing devices that may be taken outside of the personal residence and still remain connected to the home gateway device 115 located within the personal residence through a wireless network 110 .
  • the client devices 105 may include one or more general-purpose computers (e.g., personal computers), one or more special-purpose computers (e.g., devices specifically programmed to communicate with the home gateway device 115 and/or the host system 130 ), or a combination of one or more general-purpose computers and one or more special-purpose computers.
  • client devices 105 include a workstation, a server, an appliance (e.g., a refrigerator, a microwave, and an oven), an intelligent household device (e.g., a thermostat, a security system, an HVAC system, and a stereo system), a device, a component, other physical or virtual equipment, or some combination of these elements capable of responding to and executing instructions within the system architecture.
  • the client device 205 may include a general-purpose computer 240 having an internal or external storage 242 for storing data and programs such as an operating system 244 (e.g., DOS, WindowsTM, Windows 95TM, Windows 98TM, Windows 2000TM, WindowsNTTM, OS/2 and Linux) and one or more application programs.
  • an operating system 244 e.g., DOS, WindowsTM, Windows 95TM, Windows 98TM, Windows 2000TM, WindowsNTTM, OS/2 and Linux
  • application programs e.g., DOS, WindowsTM, Windows 95TM, Windows 98TM, Windows 2000TM, WindowsNTTM, OS/2 and Linux
  • Examples of application programs include authoring applications 246 (e.g., wordprocessing, database programs, spreadsheet programs, and graphic programs) capable of generating documents or other electronic content; client applications 248 (e.g., AOL client, COMPUSERVE client, AIM client, AOL TV client, and ISP client) capable of communicating with other computer users, accessing various computer resources, and viewing, creating, or otherwise manipulating electronic content; and browser applications 250 (e.g., Netscape's Navigator and Microsoft's Internet Explorer) capable of rendering standard Internet content.
  • authoring applications 246 e.g., wordprocessing, database programs, spreadsheet programs, and graphic programs
  • client applications 248 e.g., AOL client, COMPUSERVE client, AIM client, AOL TV client, and ISP client
  • browser applications 250 e.g., Netscape's Navigator and Microsoft's Internet Explorer
  • the general-purpose computer 240 also includes a central processing unit (CPU) 252 for executing instructions in response to commands from a client controller.
  • the client controller includes one or more of the application programs installed on the internal or external storage 242 of the general-purpose computer 240 .
  • the client controller includes application programs externally stored in and executed by one or more devices external to the general-purpose computer 240 .
  • the general-purpose computer 240 typically will include a communication device 254 for sending and receiving data.
  • a communication device 254 is a modem.
  • Other examples include a transceiver, a set-top box, a communication card, an xDSL modem (e.g., ADSL, CDSL, DSL Lite, HDSL, IDSL, RADSL, SDSL, UDSL, and VDSL), a cable modem, a satellite modem, a satellite dish, and an antenna, or another network adapter capable of transmitting and receiving data over a network through a wired or wireless data pathway.
  • xDSL modem e.g., ADSL, CDSL, DSL Lite, HDSL, IDSL, RADSL, SDSL, UDSL, and VDSL
  • a cable modem e.g., a satellite modem, a satellite dish, and an antenna
  • another network adapter capable of transmitting and receiving data over a network through a wired or wireless data pathway.
  • the general-purpose computer 240 may include a network interface card (NIC) 256 , which may provide a dedicated, full-time connection to a network.
  • NIC network interface card
  • Examples of NIC types include ISA, EISA, PCMCIA, PCI, Sbus, MCA, NuBus, and USB, which may support various types of networks, buses and connectivities.
  • the general-purpose computer 240 also may include a television (TV) tuner 258 for receiving television programming in the form of broadcast, satellite, and/or capable TV signals.
  • TV television
  • the client devices 205 can selectively and/or simultaneously display network content received by the communication device 254 and television programming content received by the TV tuner 258 .
  • the general-purpose computer typically will include an input/output interface 260 to enable a wired or wireless connection to various peripheral devices.
  • peripheral devices include, but are not limited to, a mouse 262 , a mobile phone 264 , a personal digital assistant (PDA) 266 , a keyboard 268 , a display monitor 270 with or without a touch screen input, and/or a remote control 272 for receiving information from and rendering information to subscribers.
  • PDA personal digital assistant
  • Other examples may include voice recognition and synthesis devices (not shown).
  • devices such as a mobile telephone 264 , a PDA 266 , and a TV remote control 272 may be considered peripheral with respect to the general-purpose computer 240 , in another implementation, such devices may themselves include the functionality of the general-purpose computer and may operate as a stand-alone client device 205 .
  • the mobile phone 264 or the PDA 266 may include computing and networking capabilities, and may function as the client device 205 .
  • the client devices 105 typically are connected to one another and to the home gateway device 15 through a network 110 , such as a Local Area Network (LAN).
  • the network 110 may include a wired and/or a wireless network.
  • one or more of the client devices 105 may be connected to the home gateway device 115 via a wired network 110 and, at the same time, one or more other client devices 105 may be connected to the home gateway device 115 via a wireless network 110 .
  • Examples of types of networks 110 include a token ring, an Ethernet, a Fast Ethernet, a Gigabit Ethernet, HomePNA, and powerline networking.
  • the client devices 105 access and communicate with the host system 130 through the home gateway device 115 .
  • the home gateway device 115 may include a general-purpose computer (e.g., personal computer), or a special-purpose computer.
  • Other examples of the home gateway device 115 may include a workstation, a server, a device, a component, other physical or virtual equipment, or some combination thereof capable of responding to and executing instructions in the manner defined to function as the home gateway device.
  • the home gateway device 115 may include internal or external storage for storing data and programs as described above with respect to the client devices 105 , such as an operating system, application programs, client applications, and browser applications. In addition to these programs and applications, the home gateway device 115 may include one or more special modules and programs (e.g., a Network Address Translation module, a PPPoE Access Concentrator module, an L2TP Access Concentrator module, a dialer module, and a DHCP module) or combinations of these modules and programs designed to allow the home gateway device 115 to communicate with the client devices 105 over the network 110 and to facilitate communications between the client devices 105 with the host system 130 through the home gateway device 115 . Additionally or alternatively, the home gateway device 115 may be embodied as part of a client device 105 with the functionality to perform as the home gateway device 115 .
  • modules and programs e.g., a Network Address Translation module, a PPPoE Access Concentrator module, an L2TP Access Concentrator module, a dialer module, and
  • the home gateway device 115 typically includes or has access to a communication device 120 .
  • Examples of the communication device 120 may include the communication devices described above with respect to the communication device 254 in FIG. 2 . Additionally or alternatively, the home gateway device 115 typically includes a network interface card such as described above with respect to the network interface card 256 in FIG. 2 . other subscribers with similar interests, get customized news and stock quotes, and search the Web.
  • the OSP host complex 370 supports different services, such as email, discussion groups, chat, news services, and Internet access.
  • the OSP host complex 370 generally is designed with an architecture that enables the machines within the OSP host complex 370 to communicate with each other, and to employ certain protocols (i.e., standards, formats, conventions, rules, and structures) to enable the transfer of data.
  • the OSP host complex 370 ordinarily employs one or more OSP protocols and custom dialing engines to enable access by selected client applications.
  • the OSP host complex 370 may define one or more specific protocols for each service based on a common, underlying proprietary protocol.
  • the IM host complex 380 may be independent of the OSP host complex 370 , and may support instant messaging services irrespective of a subscriber's network or Internet access. Thus, the IM host complex 380 may be configured to allow subscribers to send and receive instant messages, whether or not they have access to any particular ISP.
  • the IM host complex 380 may support associated services, such as administrative matters, advertising, directory services, chat, and interest groups related to the instant messaging.
  • the IM host complex 380 has an architecture that enables all of the machines within the IM host complex to communicate with each other. To transfer data, the IM host complex 380 employs one or more standard or exclusive IM protocols.
  • the host system 330 may include one or more gateways that connect and therefore link complexes, such as the OSP host complex gateway 375 and the IM host complex gateway 385 .
  • the OSP host complex gateway 375 and the IM host complex gateway 385 may directly or indirectly link the OSP host complex 370 with the IM host complex 380 through a wired or wireless pathway.
  • the OSP host complex gateway 375 and the IM host complex gateway 385 are privy to information regarding a protocol anticipated by a destination complex, which enables any necessary protocol conversion to be performed incident to the transfer of data from one complex to another.
  • the OSP host complex 370 and IM host complex 380 may use different protocols such that transferring data between the complexes requires protocol conversion by or at the request of the OSP host complex gateway 375 and/or the IM host complex gateway 385 .
  • the home gateway device 115 typically communicates with the host system 130 through communication links 125 .
  • the communication links 125 typically include a delivery network making a direct or indirect communication between the home gateway device 115 and the host system 130 , irrespective of physical separation.
  • Examples of a delivery network include the Internet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g., PSTN, ISDN, and xDSL), radio, television, cable, satellite, and/or any other delivery mechanism for carrying data.
  • the host system 330 typically includes one or more host devices 360 .
  • the host devices 360 may include hardware components and/or software components, such as one or more general-purpose computers (e.g., personal computers), one or more special-purpose computers (e.g., devices specifically programmed to communicate with the home gateway device 115 and/or the client devices 105 ), or a combination of one or more general-purpose computers and one or more special-purpose computers.
  • Other examples of host devices 360 include a workstation, a server, a component, a device, other physical or virtual equipment, or some combination of these elements that is capable of responding to and executing instructions within the system architecture.
  • a host device 360 within the host system 330 may include a login server for enabling access by subscribers and routing communications between other systems (e.g., client devices 105 and the home gateway device 115 from FIG. 1 ) and other elements of the host system 330 .
  • the host system 330 also may include various host complexes such as an OSP (“Online Service Provider”) host complex 370 and an IM (“Instant Messaging”) host complex 380 .
  • OSP Online Service Provider
  • IM Instant Messaging
  • the client devices e.g., 105 from FIG. 1
  • the home gateway device e.g., 115 from FIG. 1
  • the OSP and IM communication software applications are designed to facilitate the subscriber's interactions with the respective services and, in particular, may provide access to some or all of the services available within the respective host complexes.
  • Instant Messaging allows a subscriber to use the IM client application to view whether particular subscribers (“buddies”) are online, exchange instant messages with particular subscribers, participate in group chat rooms, trade files such as pictures, invitations or documents, find
  • the host system 130 may maintain information related to the client devices 105 or to a user of the client devices 105 .
  • information may include parental control settings, wallet settings, personal web pages, instant messaging user lists, and any other type of personal settings or features or information associated with a particular client device 105 or a user of client device 105 .
  • it may be important to enable recognition of or distinction between different client devices 105 and/or users accessing the host system so that the stored information is not rendered useless, or worse yet, inaccurately applied.
  • FIG. 4 shows several implementations and possible combinations of devices and systems used within the home networking system 420 .
  • the client devices 405 , the network 410 , the home gateway device 415 , the communication devices 420 , the communication links 425 , and the host system 430 typically correspond to their respective elements 105 , 110 , 115 , 120 , 125 , and 130 illustrated in FIG. 1 .
  • the elements in FIG. 4 which have corresponding elements in FIG. 1 , are not meant to limit the scope of the elements previously described with respect to FIG. 1 , but instead are merely some possible examples of these elements.
  • client devices 405 may include, but are not limited to, a personal computer with a WindowsTM operating system 405 a , a personal computer with a LinuxTM based operating system 405 b , a MacintoshTM personal computer 405 c , a television set-top box 405 d , a PDA 405 e , and an intelligent home appliance 405 f .
  • the client devices 405 are connected through a network 410 to the home gateway device 415 .
  • the home gateway device 415 typically includes a communication device 420 .
  • Examples of the communication device 420 may include a satellite modem 420 a , an analog modem 420 b , a cable modem 420 c , and an xDSL modem 420 d .
  • the home gateway device 415 uses the communication device 420 to communicate through communication links 425 with the host system 430 .
  • the communication links 425 may include various types of communication delivery systems that correspond to the type of communication device 420 being used. For example, if the home gateway device 415 includes a satellite modem 420 a , then the communications from the client devices 405 and the home gateway device 415 may be delivered to the host system 430 using a satellite dish 425 a and a satellite 425 b .
  • the analog modem 420 b may use one of several communications links 425 , such as the satellite dish 425 a and satellite 425 b , the Plain Old Telephone Service (POTS) 425 c , and the Cable Modem Termination System (CMTS) 425 d .
  • the cable modem 420 c typically uses the CMTS 425 d to deliver and receive communications from the host system 430 .
  • the xDSL modem 420 d typically delivers and receives communications with the host system 430 through a Digital Subscriber Line Access Multiplexer (DSLAM) 425 e and an Asynchronous Transfer Mode (ATM) network 425 f.
  • DSLAM Digital Subscriber Line Access Multiplexer
  • ATM Asynchronous Transfer Mode
  • the home networking system 400 may use various protocols to communicate between the client devices 405 and the home gateway device 415 and between the home gateway device 415 and the host system 430 .
  • a first protocol may be used to communicate between the client devices 405 and the home gateway device 415
  • a second protocol may be used to communicate between the home gateway device 415 and the host system 430 .
  • the first protocol and the second protocol may be the same.
  • the first protocol and the second protocol may be different.
  • the home gateway device 415 may include different hardware and/or software modules to implement different home networking system protocols. Various implementations and alternatives to the home networking system architecture are discussed below.
  • the elements 505 , 510 , 515 , 520 , 525 , and 530 typically correspond to the respective elements 105 , 110 , 115 , 120 , 125 , and 130 of FIG. 1 and to respective elements 405 , 410 , 415 , 420 , 425 , and 430 of FIG. 4 .
  • the client devices 505 communicate through the network 510 with the home gateway device 515 using Point-to-Point Protocol over Ethernet (PPPoE).
  • PPPoE Point-to-Point Protocol over Ethernet
  • the home gateway device 515 communicates with the host system 530 through the communication device 520 over communication links 525 .
  • the home gateway device 515 strips off the “oE” header from the PPPoE traffic used by the client devices 505 , encapsulates the PPP traffic in Layer Two Tunneling Protocol (L2TP), then encapsulates the L2TP traffic in User Datagram Protocol (UDP), and passes on the encapsulated PPP communications to the host system 530 .
  • L2TP Layer Two Tunneling Protocol
  • UDP User Datagram Protocol
  • This architecture enables multiple client devices 505 to communicate simultaneously with the host system 530 over a single communication tunnel established between the home gateway device 515 and the host system 530 while allowing the host system 530 to recognize independent Internet addresses with respect to each of the client devices 505 .
  • This architecture also enables a one-to-one mapping of a PPPoE session to an L2TP session.
  • the client device 605 may include one or more hardware and/or software modules, such as, for example, a client application 602 , a TCP/IP interface module 604 , a TCP/IP protocol implementation module 606 , a PPP protocol implementation module 608 , a PPP WAN driver SHIM module 612 , a PPPoE protocol module 613 , a real-time operating system (OS) 614 , a protocol interface module 616 , a standard Ethernet device driver interface module 618 , and a standard Ethernet hardware adapter 620 .
  • the client device may use one or more of these modules to facilitate communications with other devices (e.g., the home gateway device 515 and the host system 530 through the home gateway device 515 from FIG. 5 ).
  • the client application 602 may generate a request to initiate communications with the home gateway device (e.g., 515 from FIG. 5 ) and send outbound traffic (e.g., TCP/IP traffic going from the client device 605 to the home gateway device 515 from FIG. 5 ).
  • the request may pass from the client application 602 through the TCP/IP interface module 604 , which may allow for simultaneous support of multiple protocols between the client application level (e.g., User mode or Ring 3 ) and an operating system level (e.g., Kernel mode or Ring 0 ), and ultimately to the TCP/IP protocol implementation module 606 .
  • the client application level e.g., User mode or Ring 3
  • an operating system level e.g., Kernel mode or Ring 0
  • the TCP/IP protocol implementation module 606 typically operates in conjunction with the PPP protocol implementation module 608 and the PPP WAN driver SHIM module 612 to prepare and encapsulate the traffic in a protocol (e.g., encapsulate the TCP/IP traffic in PPP).
  • a protocol e.g., encapsulate the TCP/IP traffic in PPP.
  • the real-time OS 614 may manage real-time interprocess communications between various protocols (e.g., between PPPoE and L2TP and between user and Kernel mode modules), including buffer management and task scheduling.
  • the PPPoE protocol module 613 may add a header (e.g., an Ethernet header and a PPPoE header) to the traffic (e.g., TCP/IP traffic encapsulated in PPP) to enable the home gateway device (e.g., 515 from FIG. 5 ) to identify the particular client device 605 from which the traffic is originating.
  • the traffic may be considered PPPoE.
  • the header may include address information learned during the PPPoE discovery stage, which is discussed in more detail below, and may append the “oE” header to the PPP encapsulated traffic.
  • the real-time OS 614 typically calls the protocol interface module 616 , which is typically bound to a Network Interface Card (NIC) (e.g., 256 from FIG. 2 ) and allows for the exchange of traffic between the NIC and the PPPoE protocol module 613 .
  • NIC Network Interface Card
  • the traffic then is typically communicated to the home gateway device using the NIC, the standard Ethernet driver module 618 , and the Ethernet adapter 620 .
  • received traffic from the standard Ethernet driver module 618 is indicated to the protocol interface module 616 .
  • the PPPoE protocol module 613 receives the traffic from the protocol interface module 616 via the real-time OS 614 .
  • the PPPoE protocol module 613 strips off any header from the traffic (e.g., removing the “oE” header from the PPPoE traffic) and passes the traffic to the PPP WAN driver SHIM module 612 .
  • the PPP WAN driver SHIM module 612 then passes the traffic to the PPP protocol implementation module 608 for delivery to the TCP/IP protocol implementation module 606 .
  • the client application 602 receives traffic from the TCP/IP implementation module 606 via the TCP/IP interface module 604 .
  • the home gateway device 715 may include a PPPoE access concentrator 717 , an L2TP access concentrator 719 , and a dialer module 721 .
  • the home gateway device 715 uses L2TP to tunnel the PPP traffic from each client PPPoE session to the host system.
  • a single L2TP tunnel is established between the home gateway device and the host system to carry multiple PPP sessions because L2TP provides a method to multiplex multiple PPP sessions within a single tunnel (e.g., multiple L2TP sessions).
  • a first protocol is used between the client devices and the home gateway device 715
  • a second protocol is used between the home gateway device 715 and the host system to enable individual communication sessions between the client devices and the host system.
  • the first protocol includes PPPoE
  • the second protocol includes L2TP.
  • the dialer module 721 may be configured with a unique identifier (e.g., a login name combined with a password) that enables the host system to identify the home gateway device 715 .
  • FIG. 8 shows a more detailed block diagram of an exemplary home gateway device 815 .
  • the PPPoE access concentrator 817 and the L2TP access concentrator 819 include hardware and/or software which may be operated as user mode/Ring 3 applications.
  • the home gateway device 815 includes the PPPoE access concentrator 817 that enables communications with the client devices (e.g., 505 from FIG. 5 ).
  • the PPPoE access concentrator 817 is capable of handling multiple, simultaneous PPP sessions with the PPPoE enabled client devices 505 . Enabling each client device with its own PPP session permits the client device to receive its own unique identifier from the host system.
  • the unique identifier may include, for example, an Internet address.
  • a standard ethernet driver 823 is used to exchange Ethernet frames between the home gateway device 815 and the client devices 505 .
  • the home gateway device 815 employs a standard protocol driver 823 that, in conjunction with the real-time operating system (OS) 825 , allows the exchange of Ethernet traffic from the client devices 505 with the PPPoE access concentrator 817 .
  • the protocol driver 823 binds to Ethernet driver 827 to facilitate the exchange of traffic between the home gateway device 815 and the PPPoE access concentrator 817 .
  • the real-time OS 825 typically provides the interprocess communication capability between protocol driver 823 and PPPoE access concentrator 817 .
  • the PPPoE access concentrator 817 uses the PPPoE discovery phase to identify which particular Ethernet driver 823 will be used to exchange traffic with a particular client device 505 .
  • the L2TP access concentrator module 819 within the home gateway device 815 uses UDP over IP to exchange L2TP traffic with the host system (e.g., 530 from FIG. 5 ) using the standard TCP/IP module 829 .
  • the dialer module 821 establishes connectivity to the host system 530 prior to the exchange of L2TP traffic between the L2TP access concentrator module 819 and the host system 530 .
  • the dialer module 821 may calculate the host system 530 address, allowing the home gateway device 815 the potential to add a static route to the host system 530 in the home gateway device 815 routing table.
  • the real-time OS 825 maybe used to provide interprocess communications between the PPPoE access concentrator 817 and the L2TP access concentrator module 819 . Additionally or alternatively, the PPPoE access concentrator 817 and the L2TP access concentrator module 819 may be combined within the same module, as indicated by the dashed lines 840 .
  • FIG. 9 a illustrates one implementation of a process for enabling communications between a client device and the host system, through the home gateway device.
  • the client device typically initiates an action that indicates its desire to communicate with the host system, for example, by launching an application (e.g., a browser or a client application) or by sending a command and/or a request.
  • an application e.g., a browser or a client application
  • step 901 a It is determined whether communications are established between the client device and the home gateway device (step 901 a ). If communications are not already established between the client device and the home gateway device (step 901 a ), then the client device and the home gateway device establish communications (steps 901 - 905 ). The client device and the home gateway device may, for example, establish communications using PPPoE (steps 901 - 905 ).
  • step 907 a it is determined whether communications are established between the home gateway device and the host system. If communications are not already established between the home gateway device and the host system (step 907 a ), then the home gateway device activates the home gateway dialer module (steps 907 and 909 ). The home gateway device then establishes communications with the host using the home gateway dialer module (steps 911 - 915 ).
  • the home gateway device may, for example, establish communications using L2TP by setting up an L2TP tunnel over which multiple, individual L2TP sessions may be established.
  • the home gateway device establishes a communication session for the client device to communicate with the host system (steps 917 - 925 ).
  • the communication session may, for example, include an L2TP session created over the established L2TP tunnel.
  • the client device and the host system are enabled to communicate over the established communication session (step 927 ).
  • a client device initiates a communication with the host system by initiating the PPPoE discovery phase.
  • Discovery starts with a broadcast of the PPPoE Active Discovery Initiation (PADI) packet from the client device to the home gateway device (step 901 ).
  • PADI PPPoE Active Discovery Initiation
  • the home gateway device responds with a directed ethernet frame containing a PPPoE Active Discovery Offer (PADO) packet (step 903 ).
  • PADO PPPoE Active Discovery Offer
  • the client device typically responds to the PADO packet with a PPPoE Active Discovery Request (PADR) packet (i.e., a directed ethernet frame using the server's media access control (MAC) address as the destination address) (step 905 ).
  • PADR PPPoE Active Discovery Request
  • an L2TP tunnel is needed to the host system to enable the client device to begin sending PPP traffic, which will end up being tunneled through the L2TP session to the host system.
  • the L2TP tunnel typically is created between the home gateway device and an LNS, which is a component of the host system.
  • a dialer module within the home gateway device is triggered to send a command to establish a connection with the host system (step 907 ).
  • the connection type is based on the client device's configuration of the configurable home gateway dialer.
  • the home gateway dialer may support various types of connections such as, dial-up modem, xDSL, cable, satellite, and any other type of connection.
  • One process of establishing connections using or through the home gateway dialer is discussed further below.
  • the home gateway device begins sending messages to the host system to create the L2TP tunnel.
  • the process of creating the L2TP tunnel begins with the Start-Control-Request (SCCRQ) message (step 911 ).
  • the LNS responds with a Start-Control-Connection-Reply (SCCRP) message (step 913 ).
  • SCCRP Start-Control-Connection-Reply
  • the SCCRP message indicates the LNS is able to bring up and establish the L2TP tunnel.
  • the tunnel establishment is complete when the home gateway device sends a Start-Control-Connection-Connected (SCCCN) message (step 915 ).
  • SCCCN Start-Control-Connection-Connected
  • the home gateway device also sends a PPPoE Active Discovery Session-confirmation (PADS) message to the client device (step 917 ).
  • the PADS message indicates to the client device that it may begin sending PPP traffic to the host system.
  • the home gateway device receives PPP traffic from the client device (step 919 )
  • the home gateway device opens an L2TP session across the L2TP tunnel that was just created between the home gateway device and the host system.
  • the L2TP session is initiated when the home gateway device sends an incoming call request (ICRQ) (step 921 ).
  • the LNS within the host system responds with an incoming call reply (ICRP) (step 923 ).
  • the home gateway device completes the handshake by sending an incoming call connected (ICCN) message (step 925 ).
  • ICCN incoming call connected
  • PPPoE is used to deliver the PPP traffic from the client device to the home gateway device. More particularly, the PPPoE traffic is sent to the PPPoE access concentrator ( 817 from FIG. 8 ) within the home gateway device ( 815 from FIG. 8 ).
  • the home gateway device 815 strips off the PPPoE header leaving the PPP traffic.
  • the home gateway device 815 then replaces the PPPoE header with a valid L2TP session header so that the original PPP traffic is sent in the L2TP tunnel to the host system via the L2TP access concentrator ( 819 from FIG. 8 ).
  • Multiple L2TP sessions may be established simultaneously over the same L2TP tunnel.
  • FIG. 10 a illustrates a more detailed discussion of protocols that may be used to enable communications between the client devices (not shown), the home gateway device 1015 , and the host system 1030 .
  • the home gateway device 1015 initiates communications with the host system 1030 .
  • the home gateway device 1015 may use a communication device 1020 , such as a modem (e.g., analog modem or dial-up modem), a cable modem, a satellite modem, or a DSL modem, to communicate with the host system 1030 .
  • the dialer module within the home gateway device 1015 e.g., dialer module 821 of FIG.
  • L2TP enabled POP (“Point of Presence”)
  • the dialer module initiates a call with an L2TP access concentrator (LAC) 1032 , which is located within the POP and which may or may not reside within the host system 1030 (step 1000 - 1 of FIG. 10 a ).
  • LAC L2TP access concentrator
  • PPP is typically partially negotiated through the dialer module's dial-up network connection to the LAC 1032 (step 1000 - 2 of FIG. 10 b ).
  • the PPP Link Control Protocol (LCP) layer is negotiated and the process of authentication starts by communicating a login sequence from the home gateway device 1015 to the LAC 1032 .
  • LCP Link Control Protocol
  • the LAC 1032 notifies the L2TP Network Server (LNS) 1036 , which typically is a component of the host system 1030 , that a login sequence and authentication process has been initiated by the home gateway device 1015 .
  • the LAC 1032 may conduct a radius lookup to identify a particular LNS with which to communicate.
  • the LNS then restarts LCP negotiation with the dialer module (step 1000 - 3 a of FIG. 10 c ).
  • the LNS 1036 and the dialer module negotiate authentication and Internet Protocol Control Protocol (IPCP) (step 1000 - 3 b of FIG. 10 c ).
  • IPCP Internet Protocol Control Protocol
  • the POP's LAC 1032 first creates a tunnel 1038 , and then starts a session over that tunnel.
  • the home gateway device 1015 creates its own tunnel to the LNS 1036 , as illustrated in FIG. 10 d .
  • an end-to-end PPP session 1040 is established between the home gateway device 1015 and the LNS 1036 which is over the LAC/LNS L2TP tunnel 1038 .
  • the home gateway device 1015 will open a new L2TP session over its established tunnel 1040 .
  • the host system 1030 assigns the dialer module a unique identifier, such as an assigned Internet protocol address.
  • the dialer module typically includes software code to perform this function.
  • the dialer module may be configured with a unique identifier which allows the dialer module access to the host system 1030 through an authentication process.
  • the unique identifier may include a screen name and an associated password.
  • the home gateway device 1115 may include an L2TP access concentrator 1119 to communicate with the host system, a Network Address Translator (NAT) module 1121 that facilitates communications with the client devices, and a TCP/IP module 1123 .
  • the home gateway device 1115 which includes the NAT module 1121 , enables the host system to assign independent Internet addresses associated with each home-networked client device over a single communication tunnel that is established between the home gateway device and the host system.
  • the home gateway device 1115 uses the NAT module 1121 to map the host-assigned addresses to local addresses associated with each client device. This enables the client devices or a user of the client devices to access individual information maintained by the host system. This also enables the host system to enforce host-based controls (e.g., parental controls) for each individual client device and/or a user of each client device.
  • host-based controls e.g., parental controls
  • the home gateway device 1115 typically establishes a connection with the host system using the L2TP access concentrator 1119 .
  • the L2TP access concentrator 1119 establishes the L2TP tunnel with the LNS in the host system, as described above with respect to FIGS. 10 a - 10 d.
  • the home gateway device 1115 may assign the client devices local addresses to identify and facilitate individual communications between the home gateway device 1115 and the client devices.
  • the home gateway device may include a Dynamic Host Configuration Protocol (DHCP) module 1127 , which may assign the local addresses (e.g., local IP addresses) to the client devices.
  • the client devices typically include a DHCP client module (e.g., WindowsTM DHCP), which may seek a local address from the home gateway device 1115 (e.g., at startup or at some other time).
  • the DHCP module 1127 also may assign the home gateway device 1115 as the default route for each client device.
  • the client devices may be configured with manually assigned local addresses (e.g., static IP addresses) that are recognized by and made known to the home gateway device 1115 .
  • the home gateway device 1115 functions to map the locally assigned addresses between the client devices and the home gateway device 1115 to the host system assigned addresses between the host system and the client devices. In this manner, the host system is capable of recognizing the individual client device that is communicating with the host system.
  • the client devices 1205 typically include software that enables generation of IP traffic from the client devices 1205 to an outside entity.
  • the client device 1205 attempts to communicate with the host system 1230 .
  • the attempt generates IP traffic from the client device 1205 to the host system 1230 .
  • Information included within the IP traffic typically includes a destination address specifying a location within the host system 1230 .
  • the client device 1205 may be configured to route traffic destined for the host system 1230 or traffic destined outside of the home local network 1210 to a default routing table.
  • the traffic destined for the host system 1230 is sent to the home gateway device 1215 .
  • the home gateway device 1215 typically examines the traffic from the client devices 1205 and monitors for traffic from a new source.
  • the home gateway device 1215 When the home gateway device 1215 recognizes traffic destined for the host system 1230 from a new source, the home gateway device 1215 establishes communications with the host system 1230 , for example, by creating an L2TP tunnel with an LNS (not shown) and obtains an IP address for the home gateway device 1215 . In this manner, the home gateway device 1215 and the host system 1230 establish the L2TP tunnel over the communication links 1225 .
  • LNS not shown
  • the home gateway device 1215 and the host system 1230 establish an L2TP session over the L2TP tunnel, which is associated with the client device 1205 requesting access to the host system 1230 .
  • the host system 1230 assigns the home gateway device 1215 an IP address for that particular L2TP session.
  • the home gateway device 1215 maps the host-assigned IP address to the client device 1205 local address, thus allowing communications between the client device 1205 and the host system 1230 to occur using an independent host-assigned Internet address.
  • the home gateway device 1215 will continue mapping the Internet address provided by the host system 1230 to the client device's 1205 local address as long as the L2TP session remains connected.
  • the home gateway device 1215 maps 10.0.0.2 with 10.2.114.13. From the client's perspective, the home gateway device 1215 replaces the source IP address from client device A (10.0.0.2) with a valid host-assigned address (10.2.114.13) for all of client device A's 1205 outbound traffic. For inbound traffic, the home gateway device 1215 replaces the destination address 10.2.114.13) with (10.0.0.2) and then forwards the traffic on the network 1210 between the home gateway device 1215 and the client devices to client device A 1205 . Thus, a one-to-one mapping exists between IP address 10.0.0.2 and 10.2.114.13. From the perspective of the host system 1230 , the host system 1230 recognizes client device A 1205 as 10.2.114.13.
  • the network address translation mapping scheme enables the host system 1230 to provide the client device access to information maintained by the host system for that particular client device.
  • the mapping scheme also enables the user of the client device 1205 to access user specific information maintained by the host system 1230 .
  • Such information maintained by the host system 1230 may include, for example, parental control settings, wallet settings, and personal web page settings.
  • the network address translation module within the home gateway device 1215 enables the home gateway device 1215 to use this mapping scheme for multiple client devices 1205 over the single communication tunnel 1225 (e.g., by establishing multiple L2TP sessions over the single L2TP tunnel).
  • the home gateway device 1215 may process the mapping scheme for many unique addresses that the home gateway device 1215 senses over the network 1210 between the client devices 1205 and the home network device 1215 . Additionally or alternatively, the home gateway device 1215 may limit the number of simultaneous L2TP sessions it allows.
  • the client devices typically are TCP/IP enabled and may use various software components (e.g., MicrosoftTM TCP/IP stack) that enable TCP/IP communications.
  • the client devices 1205 may not need to be PPP enabled.
  • the home networking system may be implemented using a home gateway device 1315 , which includes a Dynamic Host Configuration Protocol (DHCP) module 1327 that enables the host system to recognize individual client devices ( 505 from FIG. 5 ).
  • the home gateway device 1315 also includes an L2TP access concentrator 1319 and a TCP/IP module 1323 , which facilitate communications with the host system ( 530 from FIG. 5 ).
  • DHCP Dynamic Host Configuration Protocol
  • the home gateway device 1315 and the host system 530 typically communicate over a broadband communications link (e.g., xDLS, satellite, and cable) ( 525 from FIG. 5 ) such that a continuous connection between the home gateway device 1315 and the host system 530 is possible.
  • a broadband communications link e.g., xDLS, satellite, and cable
  • a client device 505 that is DHCP capable is started (step 1405 ) and a determination is made as to whether a connection between the home gateway device 1315 and the host system 530 is already established (step 1410 ). If the connection is already established, the client device 505 is assigned an independent Internet address by the host system 530 (step 1415 ). The host-assigned independent address may function as both a local address for use on the network ( 510 from FIG. 5 ) between the client device 505 and the home gateway device 1315 , and as an external address for use between the client device 505 and the host system 530 . Multiple DHCP-capable client devices 505 may receive independent Internet addresses from the host system 530 using the single communication tunnel 525 between the home gateway device 1315 and the host system 530 .
  • step 1410 If the connection between the home gateway device 1315 and the host system 530 is not already established (step 1410 ), then the starting of the client device 505 triggers the home gateway device 1315 to establish a continuous connection with the host system 530 (step 1420 ). Once the connection between the home gateway device 1315 and the host system 530 is established, the host system 530 assigns the client device 505 the independent IP address (step 1415 ).
  • the described systems, methods, and techniques may be implemented in digital electronic circuitry, computer hardware, firmware, software, or in combinations of these elements. Apparatus embodying these techniques may include appropriate input and output devices, a computer processor, and a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor. A process embodying these techniques may be performed by a programmable processor executing a program of instructions to perform desired functions by operating on input data and generating appropriate output.
  • the techniques may be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device.
  • Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language.
  • Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory.
  • Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and Compact Disc Read-Only Memory (CD-ROM). Any of the foregoing may be supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated circuits).
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory

Abstract

Home-networked client devices are connected to a host system that assigns independent Internet addresses to the client devices using a home gateway device that is connected to the home-networked client devices through a network. The home gateway device, which may be physically located in a personal residence, generally includes a communication device to communicate with the host system over a single communication tunnel established between the home gateway device and the host system. The home gateway device also may include a PPPoE access concentrator and an L2TP access concentrator. The client devices communicate with the host system through the home gateway device over the single communication tunnel. This enables the host system to establish individual communication sessions with the client devices over the single communication tunnel and to assign independent Internet addresses to the client devices.

Description

CROSS REFERENCE TO RELATED APPLICATIONS
This application claims priority from U.S. Provisional Application No. 60/189,977, filed Mar. 17, 2000, and titled “Home-networking,” which is incorporated by reference.
TECHNICAL FIELD
This invention relates to connecting multiple home-networked client devices to a host system.
BACKGROUND
An increasing number of households have more than one personal computing device. As the number of personal computing devices within the home increases, there is a need and consumer demand for interconnectivity among these devices and for connectivity between these devices and host systems located outside of the home. For instance, in a household that includes more than one personal computing device, it may be desirable to enable connection between each device and an Internet Service Provider (ISP). It is possible to simply network several devices together in the home to enable interconnectivity among the devices and to enable a connection to outside host systems. However, with the devices networked together, the host system may recognize the entire network as a single device rather than recognizing the individual devices within the network or users of those individual devices.
Failing to recognize and thus distinguish the individual devices or individual users of the devices may prevent the host system from enforcing or enabling preferences and features otherwise distinguishable among individual devices or users, such as parental access controls. Similarly, without recognition of or distinction among devices and their users, the individual client devices and users of the client devices may not be able to access and receive back from the host certain host-maintained preferences, such as personal identification settings, personal web pages, account information, wallet information, and financial information.
SUMMARY
In one general aspect, home-networked client devices are connected to a host system that assigns independent Internet addresses to the home-networked client devices using a home gateway device that is connected to the home-networked client devices through a network. The home gateway device, which may be physically located in a personal residence, generally includes a communication device to communicate with the host system over a single communication tunnel established between the home gateway device and the host system. The home-networked client devices communicate with the host system through the home gateway device over the single communication tunnel. The system configuration enables the host system to establish individual communication sessions with the home-networked client devices over the single communication tunnel and to assign independent Internet addresses to the home-networked client devices.
Implementations may include one or more of the following features. For example, the home gateway device and the home-networked client devices may be physically located in a personal residence. The personal residence may include a single family dwelling. The home-networked client devices may include wireless client devices that may be connected to the home gateway device through a wireless network such that the wireless client devices may operate outside of the personal residence.
The home-networked client devices may establish simultaneous individual communication sessions with the host system over the single communication tunnel. Each home-networked client device may be assigned an independent Internet address by the host system, which may include an Internet Service Provider.
The home gateway device may communicate with the multiple home-networked client devices using a first protocol and may communicate with the host system using a second protocol. The first protocol and the second protocol may be the same protocol, or the second protocol may differ from the first protocol.
The home gateway device may include one or more modules that are structured and arranged to convert between the first protocol and the second protocol. The first protocol may include PPPoE and the second protocol may include L2TP. The home-networked client devices may be PPP enabled. The home gateway device may emulate a PPPoE access concentrator and an L2TP access concentrator. The communication device may include a modem, such as a cable modem, a satellite modem, or a DSL modem.
The multiple home-networked client devices may include client devices having computer software that enables the client devices to interface with the home gateway and to communicate with the host system through the home gateway device, such that the host system is able to recognize independent client devices. The independent client devices may be recognized by the host system through the use of unique identifiers assigned to each of the client devices by the host system during the established communication session. The unique identifiers may be unique to the client devices and/or to users of the client devices. A unique identifier may include an independent Internet address, and also may include a unique identifier for a user of a client device combined with an independent Internet address assigned to the client device. In addition, a unique identifier may include a screen name for a user of the client devices.
When the user has a unique identifier that is combined with the independent Internet address assigned by the host system to the client device, the user may be enabled to access individual information maintained by the host system for that particular user. Additionally, the host system may be enabled to enforce host-based parental or other controls. Individual information maintained by the host system may include wallet information, calendar information, and personalized web page information.
The home gateway device may include a personal computer and/or a server. The network between the home gateway device and the home-networked client devices may include a wired network, a wireless network, and/or any combination of a wired and a wireless network. The network may include an Ethernet network.
In one implementation, the home gateway device may include a dynamic host configuration protocol module and an L2TP access concentrator. Multiple home-networked client devices may communicate with the home gateway device using the dynamic host configuration protocol module. The home gateway device and the home-networked client devices may communicate over the network using DHCP, and the home-networked client devices may be assigned a single address that is used in communications with the home gateway device and the host system. The single communication tunnel established between the home gateway device and the host system may be established over a broadband network. The dynamic host configuration module may be configured to facilitate communications between the host system and the home-networked client devices to enable the host system to enforce host-based parental controls. The assignment of unique addresses to the home-networked client devices may be performed upon bootup of the client devices.
These general and specific aspects may be implemented using a system, a method, or a computer program, or any combination of systems, methods, and computer programs.
Other features and advantages will be apparent from the description and drawings, and from the claims.
DESCRIPTION OF DRAWINGS
FIG. 1 is a block diagram of a home networking system.
FIG. 2 is a block diagram of a client device of the system of FIG. 1.
FIG. 3 is a block diagram of a host system of the system of FIG. 1.
FIG. 4 is a block diagram of an implementation of the home networking system of FIG. 1.
FIG. 5 is a block diagram of the home networking system of FIG. 1 illustrating one protocol implementation.
FIG. 6 is a block diagram of the components which may be included in a client device of the system of FIG. 1.
FIG. 7 is block diagram of the components which may be included in a home gateway device of the system of FIG. 1.
FIG. 8 is a more detailed block diagram of the home gateway device of FIG. 7.
FIG. 9 a is a flow chart of a process used to enable a home network.
FIG. 9 b is a flow chart of a process used to enable a home network.
FIGS. 10 a-10 d are block diagrams of a protocol enabling communication between the components of the home networking system.
FIG. 11 is a block diagram of the home gateway device including a NAT module.
FIG. 12 is a block diagram of the home networking system using a NAT module.
FIG. 13 is a block diagram of the home gateway device including a DHCP module.
FIG. 14 is a flow chart of a process used to enable a home network.
Like reference symbols in the various drawings indicate like elements.
DETAILED DESCRIPTION
Referring to FIG. 1, a home networking system 100 typically includes multiple home-networked client devices 105 (“client devices”) connected through a network 110 to each other and to a home gateway device 115. The home gateway device 115 typically connects to the host system 130 through a communication device 120 over communication links 125. The home networking system 100 enables the client devices 105 to communicate with the host system 130 through the home gateway device 115 using the single communication device 120. The client devices 105, the home gateway device 115, and the communication device 120 may be physically located in a personal residence, as indicated by the dashed lines shown in FIG. 1.
The home networking system 100 enables the host system 130 to assign unique identifiers (e.g., independent Internet addresses) to each of the client devices 105 through the home gateway device 115 over a single communication link 125 established between the home gateway device 115 and the host system 130. The home networking system 100 also enables the client devices 105 to access information maintained by the host system 130 for a particular client device 105 or a particular individual user of the client devices 105. In addition, the home networking system 100 enables the host system 130 to maintain and enforce individual preferences associated with a particular client device 105 or a user of the client devices 105 through using the host-assigned unique identifiers and/or some combination of the host-assigned unique identifiers with other identifiers (e.g., login name, account number, screen name, and password).
The client devices 105 and the home gateway device 115 typically are located in a physical place that enables the home gateway device 115 to network with the client devices 105. In one implementation, for example, the home gateway device 115 is physically located in a personal residence (e.g., a single-family dwelling, a house, a townhouse, an apartment, or a condominium). The client devices 105 may be physically located such that communications over the network 110 with the home gateway device 115 are enabled and maintained. For instance, when the home gateway device 115 is physically located in a personal residence, the client devices 105 also may be physically located in the personal residence. However, the location of the home gateway device 115 in the personal residence does not preclude one or more of the client devices 105 from being networked to the home gateway device 115 from a remote location. Nor does it preclude use of one or more of the client devices 105 from outside of the personal residence or communication by those devices with the host system 130 through the home gateway device 115. For instance, the client devices 105 may include one or more portable computing devices that may be taken outside of the personal residence and still remain connected to the home gateway device 115 located within the personal residence through a wireless network 110.
The client devices 105 may include one or more general-purpose computers (e.g., personal computers), one or more special-purpose computers (e.g., devices specifically programmed to communicate with the home gateway device 115 and/or the host system 130), or a combination of one or more general-purpose computers and one or more special-purpose computers. Other examples of client devices 105 include a workstation, a server, an appliance (e.g., a refrigerator, a microwave, and an oven), an intelligent household device (e.g., a thermostat, a security system, an HVAC system, and a stereo system), a device, a component, other physical or virtual equipment, or some combination of these elements capable of responding to and executing instructions within the system architecture.
Referring to FIG. 2, components of a client device 205 are shown to illustrate one possible implementation of the client devices 105 of FIG. 1. The client device 205 may include a general-purpose computer 240 having an internal or external storage 242 for storing data and programs such as an operating system 244 (e.g., DOS, Windows™, Windows 95™, Windows 98™, Windows 2000™, WindowsNT™, OS/2 and Linux) and one or more application programs. Examples of application programs include authoring applications 246 (e.g., wordprocessing, database programs, spreadsheet programs, and graphic programs) capable of generating documents or other electronic content; client applications 248 (e.g., AOL client, COMPUSERVE client, AIM client, AOL TV client, and ISP client) capable of communicating with other computer users, accessing various computer resources, and viewing, creating, or otherwise manipulating electronic content; and browser applications 250 (e.g., Netscape's Navigator and Microsoft's Internet Explorer) capable of rendering standard Internet content.
The general-purpose computer 240 also includes a central processing unit (CPU) 252 for executing instructions in response to commands from a client controller. In one implementation, the client controller includes one or more of the application programs installed on the internal or external storage 242 of the general-purpose computer 240. In another implementation, the client controller includes application programs externally stored in and executed by one or more devices external to the general-purpose computer 240.
The general-purpose computer 240 typically will include a communication device 254 for sending and receiving data. One example of the communication device 254 is a modem. Other examples include a transceiver, a set-top box, a communication card, an xDSL modem (e.g., ADSL, CDSL, DSL Lite, HDSL, IDSL, RADSL, SDSL, UDSL, and VDSL), a cable modem, a satellite modem, a satellite dish, and an antenna, or another network adapter capable of transmitting and receiving data over a network through a wired or wireless data pathway.
In addition to or as an alternative to the communication device 254, the general-purpose computer 240 may include a network interface card (NIC) 256, which may provide a dedicated, full-time connection to a network. Examples of NIC types include ISA, EISA, PCMCIA, PCI, Sbus, MCA, NuBus, and USB, which may support various types of networks, buses and connectivities.
The general-purpose computer 240 also may include a television (TV) tuner 258 for receiving television programming in the form of broadcast, satellite, and/or capable TV signals. As a result, the client devices 205 can selectively and/or simultaneously display network content received by the communication device 254 and television programming content received by the TV tuner 258.
The general-purpose computer typically will include an input/output interface 260 to enable a wired or wireless connection to various peripheral devices. Examples of peripheral devices include, but are not limited to, a mouse 262, a mobile phone 264, a personal digital assistant (PDA) 266, a keyboard 268, a display monitor 270 with or without a touch screen input, and/or a remote control 272 for receiving information from and rendering information to subscribers. Other examples may include voice recognition and synthesis devices (not shown).
Although devices such as a mobile telephone 264, a PDA 266, and a TV remote control 272 may be considered peripheral with respect to the general-purpose computer 240, in another implementation, such devices may themselves include the functionality of the general-purpose computer and may operate as a stand-alone client device 205. For example, the mobile phone 264 or the PDA 266 may include computing and networking capabilities, and may function as the client device 205.
Referring again to FIG. 1, the client devices 105 typically are connected to one another and to the home gateway device 15 through a network 110, such as a Local Area Network (LAN). The network 110 may include a wired and/or a wireless network. For instance, one or more of the client devices 105 may be connected to the home gateway device 115 via a wired network 110 and, at the same time, one or more other client devices 105 may be connected to the home gateway device 115 via a wireless network 110. Examples of types of networks 110 include a token ring, an Ethernet, a Fast Ethernet, a Gigabit Ethernet, HomePNA, and powerline networking.
As mentioned above, the client devices 105 access and communicate with the host system 130 through the home gateway device 115. For example, the home gateway device 115 may include a general-purpose computer (e.g., personal computer), or a special-purpose computer. Other examples of the home gateway device 115 may include a workstation, a server, a device, a component, other physical or virtual equipment, or some combination thereof capable of responding to and executing instructions in the manner defined to function as the home gateway device.
The home gateway device 115 may include internal or external storage for storing data and programs as described above with respect to the client devices 105, such as an operating system, application programs, client applications, and browser applications. In addition to these programs and applications, the home gateway device 115 may include one or more special modules and programs (e.g., a Network Address Translation module, a PPPoE Access Concentrator module, an L2TP Access Concentrator module, a dialer module, and a DHCP module) or combinations of these modules and programs designed to allow the home gateway device 115 to communicate with the client devices 105 over the network 110 and to facilitate communications between the client devices 105 with the host system 130 through the home gateway device 115. Additionally or alternatively, the home gateway device 115 may be embodied as part of a client device 105 with the functionality to perform as the home gateway device 115.
The home gateway device 115 typically includes or has access to a communication device 120. Examples of the communication device 120 may include the communication devices described above with respect to the communication device 254 in FIG. 2. Additionally or alternatively, the home gateway device 115 typically includes a network interface card such as described above with respect to the network interface card 256 in FIG. 2. other subscribers with similar interests, get customized news and stock quotes, and search the Web.
Typically, the OSP host complex 370 supports different services, such as email, discussion groups, chat, news services, and Internet access. The OSP host complex 370 generally is designed with an architecture that enables the machines within the OSP host complex 370 to communicate with each other, and to employ certain protocols (i.e., standards, formats, conventions, rules, and structures) to enable the transfer of data. The OSP host complex 370 ordinarily employs one or more OSP protocols and custom dialing engines to enable access by selected client applications. The OSP host complex 370 may define one or more specific protocols for each service based on a common, underlying proprietary protocol.
The IM host complex 380 may be independent of the OSP host complex 370, and may support instant messaging services irrespective of a subscriber's network or Internet access. Thus, the IM host complex 380 may be configured to allow subscribers to send and receive instant messages, whether or not they have access to any particular ISP. The IM host complex 380 may support associated services, such as administrative matters, advertising, directory services, chat, and interest groups related to the instant messaging. The IM host complex 380 has an architecture that enables all of the machines within the IM host complex to communicate with each other. To transfer data, the IM host complex 380 employs one or more standard or exclusive IM protocols.
The host system 330 may include one or more gateways that connect and therefore link complexes, such as the OSP host complex gateway 375 and the IM host complex gateway 385. The OSP host complex gateway 375 and the IM host complex gateway 385 may directly or indirectly link the OSP host complex 370 with the IM host complex 380 through a wired or wireless pathway. Ordinarily, when used to facilitate a link between complexes, the OSP host complex gateway 375 and the IM host complex gateway 385 are privy to information regarding a protocol anticipated by a destination complex, which enables any necessary protocol conversion to be performed incident to the transfer of data from one complex to another. For instance, the OSP host complex 370 and IM host complex 380 may use different protocols such that transferring data between the complexes requires protocol conversion by or at the request of the OSP host complex gateway 375 and/or the IM host complex gateway 385.
The home gateway device 115 typically communicates with the host system 130 through communication links 125. The communication links 125 typically include a delivery network making a direct or indirect communication between the home gateway device 115 and the host system 130, irrespective of physical separation. Examples of a delivery network include the Internet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g., PSTN, ISDN, and xDSL), radio, television, cable, satellite, and/or any other delivery mechanism for carrying data.
Referring to FIG. 3, components of a host system 330 are shown to illustrate one possible implementation of the host system 130 of FIG. 1. The host system 330 typically includes one or more host devices 360. The host devices 360 may include hardware components and/or software components, such as one or more general-purpose computers (e.g., personal computers), one or more special-purpose computers (e.g., devices specifically programmed to communicate with the home gateway device 115 and/or the client devices 105), or a combination of one or more general-purpose computers and one or more special-purpose computers. Other examples of host devices 360 include a workstation, a server, a component, a device, other physical or virtual equipment, or some combination of these elements that is capable of responding to and executing instructions within the system architecture.
More specifically, a host device 360 within the host system 330 may include a login server for enabling access by subscribers and routing communications between other systems (e.g., client devices 105 and the home gateway device 115 from FIG. 1) and other elements of the host system 330. The host system 330 also may include various host complexes such as an OSP (“Online Service Provider”) host complex 370 and an IM (“Instant Messaging”) host complex 380. To enable access to these host complexes by subscribers, the client devices (e.g., 105 from FIG. 1) and the home gateway device (e.g., 115 from FIG. 1) may include communication software such as an OSP client application and an IM client application. The OSP and IM communication software applications are designed to facilitate the subscriber's interactions with the respective services and, in particular, may provide access to some or all of the services available within the respective host complexes. For example, Instant Messaging allows a subscriber to use the IM client application to view whether particular subscribers (“buddies”) are online, exchange instant messages with particular subscribers, participate in group chat rooms, trade files such as pictures, invitations or documents, find
In one implementation, the host system 130 may maintain information related to the client devices 105 or to a user of the client devices 105. For example, such information may include parental control settings, wallet settings, personal web pages, instant messaging user lists, and any other type of personal settings or features or information associated with a particular client device 105 or a user of client device 105. In this implementation, it may be important to enable recognition of or distinction between different client devices 105 and/or users accessing the host system so that the stored information is not rendered useless, or worse yet, inaccurately applied.
FIG. 4 shows several implementations and possible combinations of devices and systems used within the home networking system 420. The client devices 405, the network 410, the home gateway device 415, the communication devices 420, the communication links 425, and the host system 430 typically correspond to their respective elements 105, 110, 115, 120, 125, and 130 illustrated in FIG. 1. The elements in FIG. 4, which have corresponding elements in FIG. 1, are not meant to limit the scope of the elements previously described with respect to FIG. 1, but instead are merely some possible examples of these elements.
Examples of client devices 405 may include, but are not limited to, a personal computer with a Windows™ operating system 405 a, a personal computer with a Linux™ based operating system 405 b, a Macintosh™ personal computer 405 c, a television set-top box 405 d, a PDA 405 e, and an intelligent home appliance 405 f. As described above with respect to FIG. 1, the client devices 405 are connected through a network 410 to the home gateway device 415.
The home gateway device 415 typically includes a communication device 420. Examples of the communication device 420 may include a satellite modem 420 a, an analog modem 420 b, a cable modem 420 c, and an xDSL modem 420 d. The home gateway device 415 uses the communication device 420 to communicate through communication links 425 with the host system 430. The communication links 425 may include various types of communication delivery systems that correspond to the type of communication device 420 being used. For example, if the home gateway device 415 includes a satellite modem 420 a, then the communications from the client devices 405 and the home gateway device 415 may be delivered to the host system 430 using a satellite dish 425 a and a satellite 425 b. The analog modem 420 b may use one of several communications links 425, such as the satellite dish 425 a and satellite 425 b, the Plain Old Telephone Service (POTS) 425 c, and the Cable Modem Termination System (CMTS) 425 d. The cable modem 420 c typically uses the CMTS 425 d to deliver and receive communications from the host system 430. The xDSL modem 420 d typically delivers and receives communications with the host system 430 through a Digital Subscriber Line Access Multiplexer (DSLAM) 425 e and an Asynchronous Transfer Mode (ATM) network 425 f.
The home networking system 400 may use various protocols to communicate between the client devices 405 and the home gateway device 415 and between the home gateway device 415 and the host system 430. For example, a first protocol may be used to communicate between the client devices 405 and the home gateway device 415, and a second protocol may be used to communicate between the home gateway device 415 and the host system 430. In one implementation, the first protocol and the second protocol may be the same. In another implementation, the first protocol and the second protocol may be different. The home gateway device 415 may include different hardware and/or software modules to implement different home networking system protocols. Various implementations and alternatives to the home networking system architecture are discussed below.
PPPoE
Referring to FIG. 5, the elements 505, 510, 515, 520, 525, and 530 typically correspond to the respective elements 105, 110, 115, 120, 125, and 130 of FIG. 1 and to respective elements 405, 410, 415, 420, 425, and 430 of FIG. 4. In one implementation, the client devices 505 communicate through the network 510 with the home gateway device 515 using Point-to-Point Protocol over Ethernet (PPPoE). The home gateway device 515 communicates with the host system 530 through the communication device 520 over communication links 525. For communications between the client devices 505 and the host system 530, the home gateway device 515 strips off the “oE” header from the PPPoE traffic used by the client devices 505, encapsulates the PPP traffic in Layer Two Tunneling Protocol (L2TP), then encapsulates the L2TP traffic in User Datagram Protocol (UDP), and passes on the encapsulated PPP communications to the host system 530. This architecture enables multiple client devices 505 to communicate simultaneously with the host system 530 over a single communication tunnel established between the home gateway device 515 and the host system 530 while allowing the host system 530 to recognize independent Internet addresses with respect to each of the client devices 505. This architecture also enables a one-to-one mapping of a PPPoE session to an L2TP session.
Referring to FIG. 6, in one implementation, the client device 605 may include one or more hardware and/or software modules, such as, for example, a client application 602, a TCP/IP interface module 604, a TCP/IP protocol implementation module 606, a PPP protocol implementation module 608, a PPP WAN driver SHIM module 612, a PPPoE protocol module 613, a real-time operating system (OS) 614, a protocol interface module 616, a standard Ethernet device driver interface module 618, and a standard Ethernet hardware adapter 620. The client device may use one or more of these modules to facilitate communications with other devices (e.g., the home gateway device 515 and the host system 530 through the home gateway device 515 from FIG. 5).
For example, the client application 602 may generate a request to initiate communications with the home gateway device (e.g., 515 from FIG. 5) and send outbound traffic (e.g., TCP/IP traffic going from the client device 605 to the home gateway device 515 from FIG. 5). The request may pass from the client application 602 through the TCP/IP interface module 604, which may allow for simultaneous support of multiple protocols between the client application level (e.g., User mode or Ring 3) and an operating system level (e.g., Kernel mode or Ring 0), and ultimately to the TCP/IP protocol implementation module 606. The TCP/IP protocol implementation module 606 typically operates in conjunction with the PPP protocol implementation module 608 and the PPP WAN driver SHIM module 612 to prepare and encapsulate the traffic in a protocol (e.g., encapsulate the TCP/IP traffic in PPP).
The real-time OS 614 may manage real-time interprocess communications between various protocols (e.g., between PPPoE and L2TP and between user and Kernel mode modules), including buffer management and task scheduling. The PPPoE protocol module 613 may add a header (e.g., an Ethernet header and a PPPoE header) to the traffic (e.g., TCP/IP traffic encapsulated in PPP) to enable the home gateway device (e.g., 515 from FIG. 5) to identify the particular client device 605 from which the traffic is originating. Thus, the traffic may be considered PPPoE. More specifically, in one example, the header may include address information learned during the PPPoE discovery stage, which is discussed in more detail below, and may append the “oE” header to the PPP encapsulated traffic. The real-time OS 614 typically calls the protocol interface module 616, which is typically bound to a Network Interface Card (NIC) (e.g., 256 from FIG. 2) and allows for the exchange of traffic between the NIC and the PPPoE protocol module 613. The traffic then is typically communicated to the home gateway device using the NIC, the standard Ethernet driver module 618, and the Ethernet adapter 620.
For inbound traffic (e.g., PPP traffic coming from the home gateway device to the client device 605), received traffic from the standard Ethernet driver module 618 is indicated to the protocol interface module 616. The PPPoE protocol module 613 receives the traffic from the protocol interface module 616 via the real-time OS 614. The PPPoE protocol module 613 strips off any header from the traffic (e.g., removing the “oE” header from the PPPoE traffic) and passes the traffic to the PPP WAN driver SHIM module 612. The PPP WAN driver SHIM module 612 then passes the traffic to the PPP protocol implementation module 608 for delivery to the TCP/IP protocol implementation module 606. The client application 602 receives traffic from the TCP/IP implementation module 606 via the TCP/IP interface module 604.
Referring to FIG. 7, in one implementation, the home gateway device 715 may include a PPPoE access concentrator 717, an L2TP access concentrator 719, and a dialer module 721. The home gateway device 715 uses L2TP to tunnel the PPP traffic from each client PPPoE session to the host system. A single L2TP tunnel is established between the home gateway device and the host system to carry multiple PPP sessions because L2TP provides a method to multiplex multiple PPP sessions within a single tunnel (e.g., multiple L2TP sessions). Thus, in this implementation, a first protocol is used between the client devices and the home gateway device 715, and a second protocol is used between the home gateway device 715 and the host system to enable individual communication sessions between the client devices and the host system. In particular, the first protocol includes PPPoE and the second protocol includes L2TP. The dialer module 721 may be configured with a unique identifier (e.g., a login name combined with a password) that enables the host system to identify the home gateway device 715.
FIG. 8 shows a more detailed block diagram of an exemplary home gateway device 815. In this implementation, the PPPoE access concentrator 817 and the L2TP access concentrator 819 include hardware and/or software which may be operated as user mode/Ring 3 applications.
The home gateway device 815 includes the PPPoE access concentrator 817 that enables communications with the client devices (e.g., 505 from FIG. 5). The PPPoE access concentrator 817 is capable of handling multiple, simultaneous PPP sessions with the PPPoE enabled client devices 505. Enabling each client device with its own PPP session permits the client device to receive its own unique identifier from the host system. The unique identifier may include, for example, an Internet address.
When the home gateway device 815 communicates with the client devices 505, a standard ethernet driver 823 is used to exchange Ethernet frames between the home gateway device 815 and the client devices 505. The home gateway device 815 employs a standard protocol driver 823 that, in conjunction with the real-time operating system (OS) 825, allows the exchange of Ethernet traffic from the client devices 505 with the PPPoE access concentrator 817. The protocol driver 823 binds to Ethernet driver 827 to facilitate the exchange of traffic between the home gateway device 815 and the PPPoE access concentrator 817. The real-time OS 825 typically provides the interprocess communication capability between protocol driver 823 and PPPoE access concentrator 817. When the home gateway device includes more than one Ethernet driver 827, the PPPoE access concentrator 817 uses the PPPoE discovery phase to identify which particular Ethernet driver 823 will be used to exchange traffic with a particular client device 505.
The L2TP access concentrator module 819 within the home gateway device 815 uses UDP over IP to exchange L2TP traffic with the host system (e.g., 530 from FIG. 5) using the standard TCP/IP module 829. When connectivity needs to be established with the host system 530, the dialer module 821 establishes connectivity to the host system 530 prior to the exchange of L2TP traffic between the L2TP access concentrator module 819 and the host system 530. Additionally, the dialer module 821 may calculate the host system 530 address, allowing the home gateway device 815 the potential to add a static route to the host system 530 in the home gateway device 815 routing table. This may prevent a new default route from interfering with the tunnel traffic between the home gateway device 815 and the host system 530. The real-time OS 825 maybe used to provide interprocess communications between the PPPoE access concentrator 817 and the L2TP access concentrator module 819. Additionally or alternatively, the PPPoE access concentrator 817 and the L2TP access concentrator module 819 may be combined within the same module, as indicated by the dashed lines 840.
FIG. 9 a illustrates one implementation of a process for enabling communications between a client device and the host system, through the home gateway device. The client device typically initiates an action that indicates its desire to communicate with the host system, for example, by launching an application (e.g., a browser or a client application) or by sending a command and/or a request.
It is determined whether communications are established between the client device and the home gateway device (step 901 a). If communications are not already established between the client device and the home gateway device (step 901 a), then the client device and the home gateway device establish communications (steps 901-905). The client device and the home gateway device may, for example, establish communications using PPPoE (steps 901-905).
Once communications are established between the client device and the home gateway device (steps 901-905) or if communications between the client device and the home gateway device were already established (step 901 a), then it is determined whether communications are established between the home gateway device and the host system (step 907 a). If communications are not already established between the home gateway device and the host system (step 907 a), then the home gateway device activates the home gateway dialer module (steps 907 and 909). The home gateway device then establishes communications with the host using the home gateway dialer module (steps 911-915). The home gateway device may, for example, establish communications using L2TP by setting up an L2TP tunnel over which multiple, individual L2TP sessions may be established.
Once communications are established between the home gateway device and the host system (steps 911-915) or if communications between the home gateway device and the host system were already established (step 907 a), then the home gateway device establishes a communication session for the client device to communicate with the host system (steps 917-925). The communication session may, for example, include an L2TP session created over the established L2TP tunnel. Thus, the client device and the host system are enabled to communicate over the established communication session (step 927).
More particularly, one specific implementation of the process shown by FIG. 9 a is described with respect to FIG. 9 b. Referring to FIG. 9 b, a client device initiates a communication with the host system by initiating the PPPoE discovery phase. Discovery starts with a broadcast of the PPPoE Active Discovery Initiation (PADI) packet from the client device to the home gateway device (step 901). If the gateway device is present and the server software is running, the home gateway device responds with a directed ethernet frame containing a PPPoE Active Discovery Offer (PADO) packet (step 903). The client device typically responds to the PADO packet with a PPPoE Active Discovery Request (PADR) packet (i.e., a directed ethernet frame using the server's media access control (MAC) address as the destination address) (step 905).
When the home gateway device receives the PADR packet, an L2TP tunnel is needed to the host system to enable the client device to begin sending PPP traffic, which will end up being tunneled through the L2TP session to the host system. The L2TP tunnel typically is created between the home gateway device and an LNS, which is a component of the host system. When the home gateway device receives the PADR packet, a dialer module within the home gateway device is triggered to send a command to establish a connection with the host system (step 907). The connection type is based on the client device's configuration of the configurable home gateway dialer. For example, the home gateway dialer may support various types of connections such as, dial-up modem, xDSL, cable, satellite, and any other type of connection. One process of establishing connections using or through the home gateway dialer is discussed further below.
Once the dialer is connected (step 909), the home gateway device begins sending messages to the host system to create the L2TP tunnel. The process of creating the L2TP tunnel begins with the Start-Control-Request (SCCRQ) message (step 911). The LNS responds with a Start-Control-Connection-Reply (SCCRP) message (step 913). The SCCRP message indicates the LNS is able to bring up and establish the L2TP tunnel. The tunnel establishment is complete when the home gateway device sends a Start-Control-Connection-Connected (SCCCN) message (step 915).
At or about the same time that the home gateway device sends the SCCCN message, the home gateway device also sends a PPPoE Active Discovery Session-confirmation (PADS) message to the client device (step 917). The PADS message indicates to the client device that it may begin sending PPP traffic to the host system. When the home gateway device receives PPP traffic from the client device (step 919), the home gateway device opens an L2TP session across the L2TP tunnel that was just created between the home gateway device and the host system.
The L2TP session is initiated when the home gateway device sends an incoming call request (ICRQ) (step 921). The LNS within the host system responds with an incoming call reply (ICRP) (step 923). Finally, the home gateway device completes the handshake by sending an incoming call connected (ICCN) message (step 925). At that point, PPP traffic is tunneled by the home gateway device for an end-to-end exchange between the client device and the host system (step 927). Thus, PPPoE is used to deliver the PPP traffic from the client device to the home gateway device. More particularly, the PPPoE traffic is sent to the PPPoE access concentrator (817 from FIG. 8) within the home gateway device (815 from FIG. 8). The home gateway device 815 strips off the PPPoE header leaving the PPP traffic. The home gateway device 815 then replaces the PPPoE header with a valid L2TP session header so that the original PPP traffic is sent in the L2TP tunnel to the host system via the L2TP access concentrator (819 from FIG. 8). Multiple L2TP sessions may be established simultaneously over the same L2TP tunnel.
FIG. 10 a illustrates a more detailed discussion of protocols that may be used to enable communications between the client devices (not shown), the home gateway device 1015, and the host system 1030. After the client device initiates the PPP discovery phase with the home gateway device 1015, the home gateway device 1015 initiates communications with the host system 1030. The home gateway device 1015, as discussed above, may use a communication device 1020, such as a modem (e.g., analog modem or dial-up modem), a cable modem, a satellite modem, or a DSL modem, to communicate with the host system 1030. The dialer module within the home gateway device 1015 (e.g., dialer module 821 of FIG. 8) initiates communications with host system 1030 by making a call to an L2TP enabled POP (“Point of Presence”), which may or may not reside within the host system 1030. Specifically, the dialer module initiates a call with an L2TP access concentrator (LAC) 1032, which is located within the POP and which may or may not reside within the host system 1030 (step 1000-1 of FIG. 10 a).
Referring to FIG. 10 b, following the call from the dialer module to the LAC 1032, PPP is typically partially negotiated through the dialer module's dial-up network connection to the LAC 1032 (step 1000-2 of FIG. 10 b). The PPP Link Control Protocol (LCP) layer is negotiated and the process of authentication starts by communicating a login sequence from the home gateway device 1015 to the LAC 1032.
Referring to FIG. 10 c, the LAC 1032 notifies the L2TP Network Server (LNS) 1036, which typically is a component of the host system 1030, that a login sequence and authentication process has been initiated by the home gateway device 1015. The LAC 1032 may conduct a radius lookup to identify a particular LNS with which to communicate. The LNS then restarts LCP negotiation with the dialer module (step 1000-3 a of FIG. 10 c). After renegotiating LCP, as illustrated by FIG. 10 c, the LNS 1036 and the dialer module negotiate authentication and Internet Protocol Control Protocol (IPCP) (step 1000-3 b of FIG. 10 c).
Referring to FIG. 10 d, for the LNS 1036 to complete this PPP negotiation, the POP's LAC 1032 first creates a tunnel 1038, and then starts a session over that tunnel. Once the tunnel 1038 is established, the home gateway device 1015 creates its own tunnel to the LNS 1036, as illustrated in FIG. 10 d. As shown, an end-to-end PPP session 1040 is established between the home gateway device 1015 and the LNS 1036 which is over the LAC/LNS L2TP tunnel 1038. Thereafter, for each client device that requests connection to the host system 1030, the home gateway device 1015 will open a new L2TP session over its established tunnel 1040.
During the connectivity process between the dialer module within the home gateway device 1015 and the host system 1030, the host system 1030 assigns the dialer module a unique identifier, such as an assigned Internet protocol address. The dialer module typically includes software code to perform this function. For instance, the dialer module may be configured with a unique identifier which allows the dialer module access to the host system 1030 through an authentication process. The unique identifier may include a screen name and an associated password.
Network Address Translation
Referring to FIG. 11, in another implementation, the home gateway device 1115 may include an L2TP access concentrator 1119 to communicate with the host system, a Network Address Translator (NAT) module 1121 that facilitates communications with the client devices, and a TCP/IP module 1123. The home gateway device 1115, which includes the NAT module 1121, enables the host system to assign independent Internet addresses associated with each home-networked client device over a single communication tunnel that is established between the home gateway device and the host system. In one implementation, the home gateway device 1115 uses the NAT module 1121 to map the host-assigned addresses to local addresses associated with each client device. This enables the client devices or a user of the client devices to access individual information maintained by the host system. This also enables the host system to enforce host-based controls (e.g., parental controls) for each individual client device and/or a user of each client device.
As described above, the home gateway device 1115 typically establishes a connection with the host system using the L2TP access concentrator 1119. The L2TP access concentrator 1119 establishes the L2TP tunnel with the LNS in the host system, as described above with respect to FIGS. 10 a-10 d.
In one implementation, the home gateway device 1115 may assign the client devices local addresses to identify and facilitate individual communications between the home gateway device 1115 and the client devices. The home gateway device may include a Dynamic Host Configuration Protocol (DHCP) module 1127, which may assign the local addresses (e.g., local IP addresses) to the client devices. The client devices typically include a DHCP client module (e.g., Windows™ DHCP), which may seek a local address from the home gateway device 1115 (e.g., at startup or at some other time). The DHCP module 1127 also may assign the home gateway device 1115 as the default route for each client device.
Additionally or alternatively, the client devices may be configured with manually assigned local addresses (e.g., static IP addresses) that are recognized by and made known to the home gateway device 1115. The home gateway device 1115 functions to map the locally assigned addresses between the client devices and the home gateway device 1115 to the host system assigned addresses between the host system and the client devices. In this manner, the host system is capable of recognizing the individual client device that is communicating with the host system.
Referring to FIG. 12, the client devices 1205 typically include software that enables generation of IP traffic from the client devices 1205 to an outside entity. The client device 1205 attempts to communicate with the host system 1230. The attempt generates IP traffic from the client device 1205 to the host system 1230. Information included within the IP traffic typically includes a destination address specifying a location within the host system 1230. The client device 1205 may be configured to route traffic destined for the host system 1230 or traffic destined outside of the home local network 1210 to a default routing table. Thus, the traffic destined for the host system 1230 is sent to the home gateway device 1215. The home gateway device 1215 typically examines the traffic from the client devices 1205 and monitors for traffic from a new source. When the home gateway device 1215 recognizes traffic destined for the host system 1230 from a new source, the home gateway device 1215 establishes communications with the host system 1230, for example, by creating an L2TP tunnel with an LNS (not shown) and obtains an IP address for the home gateway device 1215. In this manner, the home gateway device 1215 and the host system 1230 establish the L2TP tunnel over the communication links 1225.
After the L2TP tunnel has been established, the home gateway device 1215 and the host system 1230 establish an L2TP session over the L2TP tunnel, which is associated with the client device 1205 requesting access to the host system 1230. Once the L2TP session is established, the host system 1230 assigns the home gateway device 1215 an IP address for that particular L2TP session. The home gateway device 1215 maps the host-assigned IP address to the client device 1205 local address, thus allowing communications between the client device 1205 and the host system 1230 to occur using an independent host-assigned Internet address. The home gateway device 1215 will continue mapping the Internet address provided by the host system 1230 to the client device's 1205 local address as long as the L2TP session remains connected.
For example, as shown in FIG. 12, if the client device A 1205 has a local address of 10.0.0.2 and the address assigned by host system 1205 to client device A is 10.2.114.13, then the home gateway device 1215 maps 10.0.0.2 with 10.2.114.13. From the client's perspective, the home gateway device 1215 replaces the source IP address from client device A (10.0.0.2) with a valid host-assigned address (10.2.114.13) for all of client device A's 1205 outbound traffic. For inbound traffic, the home gateway device 1215 replaces the destination address 10.2.114.13) with (10.0.0.2) and then forwards the traffic on the network 1210 between the home gateway device 1215 and the client devices to client device A 1205. Thus, a one-to-one mapping exists between IP address 10.0.0.2 and 10.2.114.13. From the perspective of the host system 1230, the host system 1230 recognizes client device A 1205 as 10.2.114.13.
The network address translation mapping scheme enables the host system 1230 to provide the client device access to information maintained by the host system for that particular client device. The mapping scheme also enables the user of the client device 1205 to access user specific information maintained by the host system 1230. Such information maintained by the host system 1230 may include, for example, parental control settings, wallet settings, and personal web page settings.
Additionally, the network address translation module within the home gateway device 1215 enables the home gateway device 1215 to use this mapping scheme for multiple client devices 1205 over the single communication tunnel 1225 (e.g., by establishing multiple L2TP sessions over the single L2TP tunnel). The home gateway device 1215 may process the mapping scheme for many unique addresses that the home gateway device 1215 senses over the network 1210 between the client devices 1205 and the home network device 1215. Additionally or alternatively, the home gateway device 1215 may limit the number of simultaneous L2TP sessions it allows.
In this implementation, the client devices typically are TCP/IP enabled and may use various software components (e.g., Microsoft™ TCP/IP stack) that enable TCP/IP communications. When using a NAT module within the home gateway device 1215, the client devices 1205 may not need to be PPP enabled.
Dynamic Host Configuration Protocol
Referring to FIG. 13, in another implementation, the home networking system may be implemented using a home gateway device 1315, which includes a Dynamic Host Configuration Protocol (DHCP) module 1327 that enables the host system to recognize individual client devices (505 from FIG. 5). The home gateway device 1315 also includes an L2TP access concentrator 1319 and a TCP/IP module 1323, which facilitate communications with the host system (530 from FIG. 5).
In this implementation, the home gateway device 1315 and the host system 530 typically communicate over a broadband communications link (e.g., xDLS, satellite, and cable) (525 from FIG. 5) such that a continuous connection between the home gateway device 1315 and the host system 530 is possible.
Referring to FIG. 14, in one example, when a client device 505 that is DHCP capable is started (step 1405) and a determination is made as to whether a connection between the home gateway device 1315 and the host system 530 is already established (step 1410). If the connection is already established, the client device 505 is assigned an independent Internet address by the host system 530 (step 1415). The host-assigned independent address may function as both a local address for use on the network (510 from FIG. 5) between the client device 505 and the home gateway device 1315, and as an external address for use between the client device 505 and the host system 530. Multiple DHCP-capable client devices 505 may receive independent Internet addresses from the host system 530 using the single communication tunnel 525 between the home gateway device 1315 and the host system 530.
If the connection between the home gateway device 1315 and the host system 530 is not already established (step 1410), then the starting of the client device 505 triggers the home gateway device 1315 to establish a continuous connection with the host system 530 (step 1420). Once the connection between the home gateway device 1315 and the host system 530 is established, the host system 530 assigns the client device 505 the independent IP address (step 1415).
The described systems, methods, and techniques may be implemented in digital electronic circuitry, computer hardware, firmware, software, or in combinations of these elements. Apparatus embodying these techniques may include appropriate input and output devices, a computer processor, and a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor. A process embodying these techniques may be performed by a programmable processor executing a program of instructions to perform desired functions by operating on input data and generating appropriate output. The techniques may be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and Compact Disc Read-Only Memory (CD-ROM). Any of the foregoing may be supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated circuits).
A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the claims. For example, advantageous results still could be achieved if steps of the disclosed techniques were performed in a different order and/or if components in the disclosed systems were combined in a different manner and/or replaced or supplemented by other components. Accordingly, other implementations are within the scope of the following claims.

Claims (72)

1. A system for connecting multiple home-networked client devices to a host system, wherein the host system assigns independent Internet addresses to the home-networked client devices, the system comprising:
a home gateway device which includes a communication device to communicate with the host system over a single communication tunnel established between the home gateway device and the host system; and
multiple home-networked client devices connected to the home gateway device via a network and that communicate with the host system through the home gateway device over the single communication tunnel,
wherein the host system is located at one end of the single communication tunnel and is configured to establish individual communication sessions with the multiple home-networked client devices over the single communication tunnel and to assign independent Internet addresses to each of the multiple home-networked client devices over the single communication tunnel.
2. The system of claim 1 wherein the home gateway device is physically located in a personal residence.
3. The system of claim 2 wherein the personal residence is a single family dwelling.
4. The system of claim 1 wherein the home gateway device and the multiple home-networked client devices are physically located in a personal residence.
5. The system of claim 4 wherein the personal residence is a single family dwelling.
6. The system of claim 2 wherein the multiple home-networked client devices include wireless client devices that are connected to the home gateway device via a wireless network.
7. The system of claim 6 wherein the wireless client devices operate outside of the personal residence.
8. The system of claim 1 wherein the multiple home-networked client devices establish simultaneous individual communication sessions with the host system over the single communication tunnel and each of the multiple home-networked client device is assigned an independent Internet address by the host system.
9. The system of claim 1 wherein the host system includes an Internet Service Provider.
10. The system of claim 1 wherein the home gateway device communicates with the multiple home-networked client devices using a first protocol and communicates with the host system using a second protocol.
11. The system of claim 10 wherein the first protocol and the second protocol are the same.
12. The system of claim 10 wherein the second protocol differs from the first protocol.
13. The system of claim 12 wherein the home gateway device includes one or more modules that are structured and arranged to convert between the first protocol and the second protocol.
14. The system of claim 12 wherein:
the home-networked client devices are PPP enabled;
the first protocol is PPPoE; and
the second protocol is L2TP.
15. The system of claim 14 wherein the home gateway device emulates a PPPoE access concentrator and an L2TP access concentrator.
16. The system of claim 1 wherein the communication device includes a modem.
17. The system of claim 16 wherein the communication device includes a cable modem.
18. The system of claim 16 wherein the communication device includes a satellite modem.
19. The system of claim 16 wherein the communication device includes a DSL modem.
20. The system of claim 1 wherein the multiple home-networked client devices include client devices having computer software that enable the client devices to interface with the home gateway device and to communicate with the host system through the home gateway device, such that the host system is able to recognize independent client devices.
21. The system of claim 20 wherein the independent client devices are recognized by the host system through the use of unique identifiers assigned to each of the client devices by the host system during the established communication session.
22. The system of claim 21 wherein the unique identifiers are unique to the client devices.
23. The system of claim 21 wherein the unique identifiers include independent Internet addresses.
24. The system of claim 21 wherein the unique identifiers are unique to users of the client devices.
25. The system of claim 24 wherein at least one of the unique identifiers includes a unique identifier for a user of the client devices combined with an independent Internet address assigned to a client device.
26. The system of claim 25 wherein at least one of the unique identifiers for the user of the client devices includes a screen name.
27. The system of claim 1 wherein the multiple home-networked client devices are each assigned an independent Internet address by the host system that enables the host system to recognize a user of a home-networked client device, the user having a unique identifier that is which combined with the independent Internet address to allow the user access to individual information maintained by the host system for that user.
28. The system of claim 27 wherein the user having the unique identifier combined with the independent Internet address allows the host system to enforce host-based parental controls.
29. The system of claim 27 wherein the individual information maintained by the host system includes wallet information.
30. The system of claim 27 wherein the individual information maintained by the host system includes calendar information.
31. The system of claim 27 wherein the individual information maintained by the host system includes personalized web page information.
32. The system of claim 1 wherein the home gateway device includes a personal computer.
33. The system of claim 1 wherein the home gateway device includes a server.
34. The system of claim 1 wherein the network includes a wired network.
35. The system of claim 1 wherein the network includes a wireless network.
36. The system of claim 1 wherein the network includes a wired and a wireless network.
37. The system of claim 1 wherein the network includes an Ethernet network.
38. The system of claim 1 wherein the home gateway device includes a dynamic host configuration protocol module.
39. The system of claim 1 wherein:
the home gateway device includes;
a dynamic host configuration protocol module; and
an L2TP access concentrator; and
the multiple home-networked client devices communicate with the home gateway device using the dynamic host configuration protocol module.
40. The system of claim 39 wherein:
the network between the home gateway device and the multiple home-networked client devices uses the dynamic host configuration protocol module to enable the home gateway device to assign unique addresses to the multiple home-networked client devices;
the single communication tunnel established between the home gateway device and the host system is established over a broadband network; and
the dynamic host configuration module is configured to facilitate communications between the host system and the multiple home-networked client devices to enable the host system to enforce host-based parental controls.
41. The system of claim 40 wherein the assignment of unique addresses is performed upon bootup of the multiple home-networked client devices.
42. The system of claim 1 wherein the home gateway device and the multiple home-networked client devices communicate over the network using DHCP and the multiple home-networked client devices are each assigned a single address that is used in communications with the home gateway device and the host system.
43. A method for connecting multiple home-networked client devices to a host system, wherein the host system assigns independent Internet addresses to the home-networked client devices, the method comprising:
using the home gateway device to receive a request from at least one of multiple home-networked client devices to communicate with the host system, wherein the multiple home-networked client devices are connected to the home gateway device via a network;
using the home gateway device to establish communications with the host system over a single communication tunnel;
using the home gateway device to receive independent Internet addresses from the host system, located at one end of the single communication tunnel, for each of the multiple home-networked client devices over the single communication tunnel;
using the home gateway device to establish with the host system an individual communication session over the single communication tunnel, wherein the individual communication session is based on an independent Internet address assigned by the host system to the at least one of the multiple home-networked client devices that requested to communicate with the host system; and
using the home gateway device to process communications between the at least one of the multiple home-networked client devices and the host system.
44. The method of claim 43 further comprising physically locating the home gateway device in a personal residence such that the request is received in the personal residence.
45. The method of claim 44 wherein the personal residence is a single family dwelling such that the request is received in the single family dwelling.
46. The method of claim 43 further comprising physically locating the home gateway device and the multiple home-networked client devices in a personal residence such that the request is received in the personal residence.
47. The method of claim 46 wherein the personal residence is a single family dwelling such that the request is received in the single family dwelling.
48. The method of claim 43 further comprising:
using the home gateway device to establish with the host system multiple simultaneous individual communication sessions over the single communication tunnel, wherein the multiple simultaneous individual communication sessions are each based on an independent Internet address assigned to the multiple home-networked client devices that request to communicate with the host system; and
using the home gateway device to process communications between the multiple home-networked client devices and the host system.
49. The method of claim 43 wherein the host system includes an Internet Service Provider.
50. The method of claim 43 wherein using the home gateway device to process communications between the at least one of the multiple home-networked client devices and the host system includes:
using the home gateway device to communicate with the at least one of the multiple home-networked client devices using a first protocol; and
using the home gateway device to communicate with the host system using a second protocol.
51. The method of claim 50 wherein the first protocol and the second protocol are the same.
52. The method of claim 50 wherein the second protocol differs from the first protocol.
53. The method of claim 50 wherein the first protocol includes PPPoE and the second protocol includes L2TP.
54. The method of claim 53 wherein the home gateway device includes a PPPoE access concentrator and an L2TP access concentrator.
55. The method of claim 50 wherein using the home gateway device to process communications includes:
removing a first header from the communications received from the at least one of the multiple home-networked client devices destined for the host system;
adding a second header to the communications; and
sending the communications with the second header to the host system.
56. The method of claim 55 wherein using the home gateway device to process communications includes:
removing a third header from the communications received from the host system destined for the home-networked client device;
adding a fourth header to the communications; and
sending the communications with the fourth header to the home-networked client device.
57. The method of claim 43 wherein the home gateway device includes a dynamic host configuration protocol module.
58. The method of claim 43 wherein using the home gateway device to process communications between the at least one of the multiple home-networked client devices and the host system includes:
using the home gateway device to communicate with the at least one of the multiple home-networked client devices using DHCP; and
using the home gateway device to communicate with the host system using L2TP.
59. The method of claim 43 wherein:
using the home gateway device to establish communications with the host system includes establishing communications with the host system over a broadband network; and
using the home gateway device to process communications between the at least one of the multiple home-networked client devices and the host system includes the home gateway device using the host-assigned independent Internet address to communicate over the network with the at least one of the multiple home-networked client devices.
60. The method of claim 59 wherein the independent Internet address is assigned to the at least one of the multiple home-networked client devices upon bootup.
61. A method for connecting multiple home-networked client devices to a host system, wherein the host system assigns independent Internet addresses to the home-networked client devices, the method comprising:
using a host system, located at one end of a single communication tunnel, to assign independent Internet addresses to each of multiple home-networked client devices over the single communication tunnel;
using the host system to receive a request for an individual communication session with at least one of the multiple home-networked client devices;
using the host system to establish communications with the home gateway device over the single communication tunnel;
using the host system to establish with the home gateway device the individual communication session over the single communication tunnel, wherein establishing the individual communication session includes using the host system to assign an independent Internet address to the at least one of the multiple home-networked client devices that requested to communicate with the host system; and
communicating between the host system and the at least one of the multiple home-networked client devices through the home gateway device over the individual communication session.
62. The method of claim 61 further comprising physically locating the home gateway device in a personal residence such that the request is received in the personal residence.
63. The method of claim 62 wherein the personal residence is a single family dwelling such that the request is received in the single family dwelling.
64. The method of claim 61 further comprising physically locating the home gateway device and the multiple home-networked client devices in a personal residence such that the request is received in the personal residence.
65. The method of claim 64 wherein the personal residence is a single family dwelling such that the request is received in the single family dwelling.
66. The method of claim 61 further comprising:
using the host system to establish multiple simultaneous individual communication sessions with the multiple home gateway devices over the single communication tunnel, wherein establishing the multiple simultaneous individual communication sessions includes assigning an independent Internet address to each of the multiple home-networked client devices that requests to communicate with the host system; and
communicating between the host system and the multiple home-networked client devices through the home gateway device over the multiple simultaneous individual communication sessions.
67. The method of claim 66 further comprising having the host system use the assigned independent Internet address to communicate individual information maintained by the host system to the multiple home-networked client devices.
68. The method of claim 67 wherein the individual information includes host-based parental controls.
69. The method of claim 67 wherein the individual information includes wallet information.
70. The method of claim 67 wherein the individual information includes calendar information.
71. The method of claim 67 wherein the individual information includes personalized web page information.
72. The method of claim 61 wherein the host system includes an Internet Service Provider.
US09/810,421 2000-03-17 2001-03-19 Home-networking Expired - Lifetime US7359973B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09/810,421 US7359973B2 (en) 2000-03-17 2001-03-19 Home-networking

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US18997700P 2000-03-17 2000-03-17
US09/810,421 US7359973B2 (en) 2000-03-17 2001-03-19 Home-networking

Publications (2)

Publication Number Publication Date
US20010036192A1 US20010036192A1 (en) 2001-11-01
US7359973B2 true US7359973B2 (en) 2008-04-15

Family

ID=22699551

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/810,511 Expired - Lifetime US7353280B2 (en) 2000-03-17 2001-03-19 Home-networking
US09/810,421 Expired - Lifetime US7359973B2 (en) 2000-03-17 2001-03-19 Home-networking

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/810,511 Expired - Lifetime US7353280B2 (en) 2000-03-17 2001-03-19 Home-networking

Country Status (9)

Country Link
US (2) US7353280B2 (en)
EP (1) EP1266507B1 (en)
JP (1) JP2003528539A (en)
CN (1) CN100337461C (en)
AT (1) ATE268529T1 (en)
AU (1) AU2001245827A1 (en)
CA (1) CA2403709C (en)
DE (1) DE60103625T2 (en)
WO (1) WO2001071977A2 (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050050161A1 (en) * 2003-08-29 2005-03-03 Arnold Erich C. Method and system for layer-3 subscriber login in a cable data network
US20050066056A1 (en) * 2003-09-22 2005-03-24 Anilkumar Dominic Group-to-group communication over a single connection
US20060193335A1 (en) * 2000-10-27 2006-08-31 Suhail Nanji Tunneling Ethernet
US20070002873A1 (en) * 2004-01-30 2007-01-04 Matsushita Electric Industrial Co., Ltd. Information processing device, server, communication system, address decision method, address modification method, and program
US20100332906A1 (en) * 2009-06-30 2010-12-30 International Business Machines Corporation Quality of Service Management of End User Devices in an End User Network
US9596240B2 (en) 2004-08-30 2017-03-14 Arris Enterprises, Inc. Method and system for layer-3 subscriber login in a cable data network
US9954948B2 (en) 2014-07-11 2018-04-24 Microsoft Technology Licensing, Llc Private content distribution network

Families Citing this family (232)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1266507B1 (en) * 2000-03-17 2004-06-02 America Online, Inc. Home-networking
EP1202507A1 (en) * 2000-10-31 2002-05-02 BRITISH TELECOMMUNICATIONS public limited company Telecommunications systems
US11204729B2 (en) 2000-11-01 2021-12-21 Flexiworld Technologies, Inc. Internet based digital content services for pervasively providing protected digital content to smart devices based on having subscribed to the digital content service
US7609402B2 (en) 2001-01-19 2009-10-27 Flexiworld, Inc. Methods for universal data output
US10915296B2 (en) * 2000-11-01 2021-02-09 Flexiworld Technologies, Inc. Information apparatus that includes a touch sensitive screen interface for managing or replying to e-mails
US10860290B2 (en) 2000-11-01 2020-12-08 Flexiworld Technologies, Inc. Mobile information apparatuses that include a digital camera, a touch sensitive screen interface, support for voice activated commands, and a wireless communication chip or chipset supporting IEEE 802.11
AU2002239325A1 (en) 2000-11-20 2002-05-27 Flexiworld Technologies, Inc. Systems and methods for mobile and pervasive output
US7184427B1 (en) * 2000-11-28 2007-02-27 Genband Inc. System and method for communicating telecommunication information from a broadband network to a telecommunication network
KR100396920B1 (en) * 2000-12-27 2003-09-02 한국전자통신연구원 Modular Type Home Gateway System Including ADSL Controller And HomePNA Controller
US7320036B1 (en) * 2001-04-13 2008-01-15 Redback Networks Inc. Method and apparatus for multiple communications sessions
FI120065B (en) * 2001-06-05 2009-06-15 Sanako Oy A system for managing online learning activities
US7117267B2 (en) * 2001-06-28 2006-10-03 Sun Microsystems, Inc. System and method for providing tunnel connections between entities in a messaging system
US7769838B2 (en) * 2001-08-23 2010-08-03 The Directv Group, Inc. Single-modem multi-user virtual private network
US7197550B2 (en) * 2001-08-23 2007-03-27 The Directv Group, Inc. Automated configuration of a virtual private network
US7099957B2 (en) 2001-08-23 2006-08-29 The Directtv Group, Inc. Domain name system resolution
KR20030024071A (en) * 2001-09-15 2003-03-26 삼성전자주식회사 Ineternet automatic connection method using digital subscriber line
US20030065757A1 (en) * 2001-10-01 2003-04-03 Duane Mentze Automatic networking device configuration method for home networking environments
US7408661B2 (en) * 2001-10-12 2008-08-05 Canon Kabushiki Kaisha Control apparatus and its method, and control program and storage medium holding it, with access designating second address being performed based on link to the second address included in display information
US7010661B2 (en) * 2002-02-13 2006-03-07 Matsushita Electric Industrial Co., Ltd. Efficient service management in home gateways
CN1280751C (en) * 2001-10-12 2006-10-18 松下电器产业株式会社 Efficient service management in home gateways
KR100407051B1 (en) * 2001-11-16 2003-11-28 삼성전자주식회사 Home network system
JP3692083B2 (en) * 2002-01-24 2005-09-07 株式会社東芝 Communication device with dial-up function
US7873028B2 (en) * 2002-01-25 2011-01-18 Quanta Computer, Inc. Method and apparatus for a flexible peripheral access router
US6658091B1 (en) 2002-02-01 2003-12-02 @Security Broadband Corp. LIfestyle multimedia security system
CN1299473C (en) * 2002-02-20 2007-02-07 贵州以太科技信息产业有限责任公司 Control method for household electrical apparatus of control network in Internet
AU2003212412B2 (en) * 2002-02-27 2009-01-08 Opentv, Inc. A method and apparatus for providing a hierarchical security profile object
US20030167338A1 (en) * 2002-03-01 2003-09-04 Globespanvirata Incorporated System and method to provide PPPoE connectivity to non-PPPoE clients
KR100420526B1 (en) * 2002-03-15 2004-03-02 엘지전자 주식회사 Home Appliance Network System and Controlling Method for the Same
US6738353B2 (en) * 2002-03-20 2004-05-18 Sunrise Telecom Incorporated System and method for monitoring a packet network
US7196085B2 (en) * 2002-04-30 2007-03-27 Kudos Pharmaceuticals Limited Phthalazinone derivatives
US20030233432A1 (en) * 2002-06-18 2003-12-18 John Davis Web-based interface for building management systems
US20040001496A1 (en) * 2002-06-21 2004-01-01 Jon Yusko Method and apparatus for PPP auto-connect
US7024256B2 (en) * 2002-06-27 2006-04-04 Openpeak Inc. Method, system, and computer program product for automatically managing components within a controlled environment
US6792323B2 (en) * 2002-06-27 2004-09-14 Openpeak Inc. Method, system, and computer program product for managing controlled residential or non-residential environments
US7933945B2 (en) 2002-06-27 2011-04-26 Openpeak Inc. Method, system, and computer program product for managing controlled residential or non-residential environments
US8116889B2 (en) 2002-06-27 2012-02-14 Openpeak Inc. Method, system, and computer program product for managing controlled residential or non-residential environments
US7383339B1 (en) 2002-07-31 2008-06-03 Aol Llc, A Delaware Limited Liability Company Local proxy server for establishing device controls
DE10241197A1 (en) * 2002-09-05 2004-03-25 Siemens Ag Signalization information forwarding method for data communications network with selective protocol conversion dependent on protocol required by target device
JP3895691B2 (en) * 2002-09-13 2007-03-22 富士通株式会社 Gateway card, gateway control program, and gateway device
US7489693B2 (en) * 2002-09-18 2009-02-10 Conexant Systems, Inc. Method and apparatus for automatically detecting virtual circuit settings and encapsulation types in a DSL network
DE10244710A1 (en) * 2002-09-25 2004-04-08 Siemens Ag Protocol selection procedure for transmission of data packets
DE10244612A1 (en) * 2002-09-25 2004-04-08 Siemens Ag Process for the transparent exchange of data packets
US20040071133A1 (en) * 2002-10-11 2004-04-15 Globespanvirata Incorporated Intelligent PPPOE initialization
DE10250201B4 (en) * 2002-10-28 2005-05-25 Siemens Ag Method and device for exchanging data by means of a tunnel connection
US20040105444A1 (en) * 2002-11-15 2004-06-03 Korotin Dmitry O. Auto-configuration of broadband service for one of a plurality of network communication protocols
US7444401B1 (en) * 2002-11-18 2008-10-28 Arkion Systems Llc Method and apparatus for inexpensively monitoring and controlling remotely distributed appliances
JP3826100B2 (en) * 2002-11-27 2006-09-27 株式会社東芝 Communication relay device, communication system and communication control program
WO2004051947A1 (en) 2002-11-29 2004-06-17 Freebit Co.,Ltd. Server for routing connection to client device
DE60311400T2 (en) * 2002-12-10 2007-11-29 Lg Electronics Inc. Multi-zone air conditioning system with integrated control system
US7987489B2 (en) * 2003-01-07 2011-07-26 Openpeak Inc. Legacy device bridge for residential or non-residential networks
AU2004200486B2 (en) * 2003-02-12 2007-06-07 Samsung Electronics Co., Ltd. Complex wireless service apparatus using wired and wireless communication systems and method thereof
US7525976B2 (en) * 2003-03-12 2009-04-28 The Directv Group, Inc. Adaptation of dial-up devices to broadband facilities
US7668990B2 (en) * 2003-03-14 2010-02-23 Openpeak Inc. Method of controlling a device to perform an activity-based or an experience-based operation
US8042049B2 (en) 2003-11-03 2011-10-18 Openpeak Inc. User interface for multi-device control
US7454615B2 (en) * 2003-05-08 2008-11-18 At&T Intellectual Property I, L.P. Centralized authentication system
US7337219B1 (en) 2003-05-30 2008-02-26 Aol Llc, A Delaware Limited Liability Company Classifying devices using a local proxy server
DE10329858A1 (en) * 2003-07-02 2005-01-27 Siemens Ag Method for configuring a device in a data network
EP1494433B1 (en) * 2003-07-03 2011-05-04 Alcatel Lucent Duplicate MAC address check and dynamic MAC address allocation
US7209957B2 (en) * 2003-09-15 2007-04-24 Sbc Knowledge Ventures, L.P. Downloadable control policies for instant messaging usage
KR100560744B1 (en) * 2003-09-25 2006-03-13 삼성전자주식회사 Apparatus and method for managing IP address based on DHCP
US7721329B2 (en) * 2003-11-18 2010-05-18 Aol Inc. Method and apparatus for trust-based, fine-grained rate limiting of network requests
KR20050050954A (en) * 2003-11-26 2005-06-01 삼성전자주식회사 Device for controlling network device on private network and method thereof
WO2005060611A2 (en) * 2003-12-10 2005-07-07 Alex Mashinsky Exchange of centralized control data
US7640066B2 (en) * 2004-02-05 2009-12-29 York International Corporation Transport of encapsulated serial data via instant messaging communication
US8654936B1 (en) * 2004-02-24 2014-02-18 At&T Intellectual Property I, L.P. Home control, monitoring and communication system using remote voice commands
KR100633666B1 (en) * 2004-02-25 2006-10-12 엘지전자 주식회사 Home network server device and the control method of the same
US11113950B2 (en) 2005-03-16 2021-09-07 Icontrol Networks, Inc. Gateway integrated with premises security system
US11677577B2 (en) 2004-03-16 2023-06-13 Icontrol Networks, Inc. Premises system management using status signal
US10313303B2 (en) 2007-06-12 2019-06-04 Icontrol Networks, Inc. Forming a security network including integrated security system components and network devices
US20050216302A1 (en) 2004-03-16 2005-09-29 Icontrol Networks, Inc. Business method for premises management
US11489812B2 (en) 2004-03-16 2022-11-01 Icontrol Networks, Inc. Forming a security network including integrated security system components and network devices
US11343380B2 (en) 2004-03-16 2022-05-24 Icontrol Networks, Inc. Premises system automation
US10522026B2 (en) 2008-08-11 2019-12-31 Icontrol Networks, Inc. Automation system user interface with three-dimensional display
US11811845B2 (en) 2004-03-16 2023-11-07 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US10237237B2 (en) * 2007-06-12 2019-03-19 Icontrol Networks, Inc. Communication protocols in integrated systems
US11244545B2 (en) 2004-03-16 2022-02-08 Icontrol Networks, Inc. Cross-client sensor user interface in an integrated security network
US11201755B2 (en) 2004-03-16 2021-12-14 Icontrol Networks, Inc. Premises system management using status signal
US9141276B2 (en) 2005-03-16 2015-09-22 Icontrol Networks, Inc. Integrated interface for mobile device
US10375253B2 (en) 2008-08-25 2019-08-06 Icontrol Networks, Inc. Security system with networked touchscreen and gateway
US8988221B2 (en) 2005-03-16 2015-03-24 Icontrol Networks, Inc. Integrated security system with parallel processing architecture
US10721087B2 (en) 2005-03-16 2020-07-21 Icontrol Networks, Inc. Method for networked touchscreen with integrated interfaces
US10200504B2 (en) 2007-06-12 2019-02-05 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US10444964B2 (en) 2007-06-12 2019-10-15 Icontrol Networks, Inc. Control system user interface
US11190578B2 (en) 2008-08-11 2021-11-30 Icontrol Networks, Inc. Integrated cloud system with lightweight gateway for premises automation
US10156959B2 (en) 2005-03-16 2018-12-18 Icontrol Networks, Inc. Cross-client sensor user interface in an integrated security network
US11916870B2 (en) 2004-03-16 2024-02-27 Icontrol Networks, Inc. Gateway registry methods and systems
US20090077623A1 (en) 2005-03-16 2009-03-19 Marc Baum Security Network Integrating Security System and Network Devices
US10339791B2 (en) 2007-06-12 2019-07-02 Icontrol Networks, Inc. Security network integrated with premise security system
US9191228B2 (en) 2005-03-16 2015-11-17 Icontrol Networks, Inc. Cross-client sensor user interface in an integrated security network
US11368429B2 (en) 2004-03-16 2022-06-21 Icontrol Networks, Inc. Premises management configuration and control
US10382452B1 (en) 2007-06-12 2019-08-13 Icontrol Networks, Inc. Communication protocols in integrated systems
US11316958B2 (en) 2008-08-11 2022-04-26 Icontrol Networks, Inc. Virtual device systems and methods
US10142392B2 (en) 2007-01-24 2018-11-27 Icontrol Networks, Inc. Methods and systems for improved system performance
US9531593B2 (en) 2007-06-12 2016-12-27 Icontrol Networks, Inc. Takeover processes in security network integrated with premise security system
US7711796B2 (en) 2006-06-12 2010-05-04 Icontrol Networks, Inc. Gateway registry methods and systems
US11159484B2 (en) 2004-03-16 2021-10-26 Icontrol Networks, Inc. Forming a security network including integrated security system components and network devices
US8635350B2 (en) 2006-06-12 2014-01-21 Icontrol Networks, Inc. IP device discovery systems and methods
US11277465B2 (en) 2004-03-16 2022-03-15 Icontrol Networks, Inc. Generating risk profile using data of home monitoring and security system
US20120066608A1 (en) 2005-03-16 2012-03-15 Ken Sundermeyer Control system user interface
US10348575B2 (en) 2013-06-27 2019-07-09 Icontrol Networks, Inc. Control system user interface
US9729342B2 (en) 2010-12-20 2017-08-08 Icontrol Networks, Inc. Defining and implementing sensor triggered response rules
US20170118037A1 (en) 2008-08-11 2017-04-27 Icontrol Networks, Inc. Integrated cloud system for premises automation
US8963713B2 (en) 2005-03-16 2015-02-24 Icontrol Networks, Inc. Integrated security network with security alarm signaling system
US11582065B2 (en) 2007-06-12 2023-02-14 Icontrol Networks, Inc. Systems and methods for device communication
US9609003B1 (en) 2007-06-12 2017-03-28 Icontrol Networks, Inc. Generating risk profile using data of home monitoring and security system
US20050216589A1 (en) * 2004-03-29 2005-09-29 Sbc Knowledge Ventures, L.P. System and method for indicating network connectivity and access to an information service offering
CA2567303C (en) 2004-05-20 2015-03-24 Freebit Co., Ltd. Server for routing connection to client device
US7756984B2 (en) * 2004-09-27 2010-07-13 Citrix Systems, Inc. Systems and methods for virtual host name roaming
US7603494B2 (en) * 2005-01-05 2009-10-13 At&T Intellectual Property I, L.P. Home networking resource management
US20110128378A1 (en) 2005-03-16 2011-06-02 Reza Raji Modular Electronic Display Platform
US11700142B2 (en) 2005-03-16 2023-07-11 Icontrol Networks, Inc. Security network integrating security system and network devices
US20120324566A1 (en) 2005-03-16 2012-12-20 Marc Baum Takeover Processes In Security Network Integrated With Premise Security System
US11496568B2 (en) 2005-03-16 2022-11-08 Icontrol Networks, Inc. Security system with networked touchscreen
US9306809B2 (en) 2007-06-12 2016-04-05 Icontrol Networks, Inc. Security system with networked touchscreen
US11615697B2 (en) 2005-03-16 2023-03-28 Icontrol Networks, Inc. Premise management systems and methods
US10999254B2 (en) 2005-03-16 2021-05-04 Icontrol Networks, Inc. System for data routing in networks
US20170180198A1 (en) 2008-08-11 2017-06-22 Marc Baum Forming a security network including integrated security system components
US8041824B1 (en) * 2005-04-14 2011-10-18 Strauss Acquisitions, L.L.C. System, device, method and software for providing a visitor access to a public network
EP1737161A1 (en) 2005-06-20 2006-12-27 Thomson Telecom Belgium Device and method for managing two types of devices
FR2888692B1 (en) * 2005-07-18 2007-08-31 Sagem Comm ARCHITECTURE OF A CONFIGURABLE DOMESTIC BRIDGE
FR2888693B1 (en) * 2005-07-18 2007-09-14 Sagem Comm ARCHITECTURE OF A MULTISERVICES ORIENTED DOMESTIC BRIDGE
WO2007036758A1 (en) * 2005-09-29 2007-04-05 Nortel Networks Limited Network media gateway
US8804695B2 (en) * 2005-09-30 2014-08-12 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for providing alerts and notifications
US8223938B2 (en) 2005-09-30 2012-07-17 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for providing caller identification services
US20070209065A1 (en) * 2005-09-30 2007-09-06 Bellsouth Intellectual Property Corporation Methods, systems, and computer program products for providing network convergence of applications and devices
US20070209054A1 (en) * 2005-09-30 2007-09-06 Bellsouth Intellectual Property Corporation Methods, systems, and computer program products for providing communications services
US20070208619A1 (en) * 2005-09-30 2007-09-06 Bellsouth Intellectual Property Corporation Methods, systems, and computer program products for providing targeted advertising to communications devices
US7890552B2 (en) * 2005-09-30 2011-02-15 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for implementing media content analysis, distribution, and re-allocation services
US9100284B2 (en) * 2005-11-29 2015-08-04 Bosch Security Systems, Inc. System and method for installation of network interface modules
JP4038221B2 (en) * 2005-12-08 2008-01-23 フリービット株式会社 Relay device and connection method between client device and server
US7957326B1 (en) 2005-12-29 2011-06-07 Nortel Networks Limited Integrated home service network
WO2007086026A2 (en) * 2006-01-27 2007-08-02 Nokia Siemens Networks Oy Automatic establishment of a network connection for automated network element configuration
US10326537B2 (en) 2006-01-31 2019-06-18 Silicon Laboratories Inc. Environmental change condition detection through antenna-based sensing of environmental change
US20150131485A1 (en) * 2006-01-31 2015-05-14 Sigma Designs, Inc. Mapping connected devices in a home area network to ip addresses in a local area network
US20150187209A1 (en) 2006-01-31 2015-07-02 Sigma Designs, Inc. Method and system for synchronization and remote control of controlling units
US10277519B2 (en) 2006-01-31 2019-04-30 Silicon Laboratories Inc. Response time for a gateway connecting a lower bandwidth network with a higher speed network
US20070214232A1 (en) * 2006-03-07 2007-09-13 Nokia Corporation System for Uniform Addressing of Home Resources Regardless of Remote Clients Network Location
US8001219B2 (en) * 2006-03-16 2011-08-16 Exceptional Innovation, Llc User control interface for convergence and automation system
US8725845B2 (en) 2006-03-16 2014-05-13 Exceptional Innovation Llc Automation control system having a configuration tool
US7496627B2 (en) 2006-03-16 2009-02-24 Exceptional Innovation, Llc Automation control system having digital logging
US7587464B2 (en) 2006-03-16 2009-09-08 Exceptional Innovation, Llc Device automation using networked device control having a web services for devices stack
US7966083B2 (en) 2006-03-16 2011-06-21 Exceptional Innovation Llc Automation control system having device scripting
US7509402B2 (en) * 2006-03-16 2009-03-24 Exceptional Innovation, Llc Automation control system having a configuration tool and two-way ethernet communication for web service messaging, discovery, description, and eventing that is controllable with a touch-screen display
US8155142B2 (en) * 2006-03-16 2012-04-10 Exceptional Innovation Llc Network based digital access point device
US8209398B2 (en) * 2006-03-16 2012-06-26 Exceptional Innovation Llc Internet protocol based media streaming solution
US7590703B2 (en) * 2006-03-27 2009-09-15 Exceptional Innovation, Llc Set top box for convergence and automation system
US8271881B2 (en) 2006-04-20 2012-09-18 Exceptional Innovation, Llc Touch screen for convergence and automation system
WO2007131169A2 (en) * 2006-05-04 2007-11-15 Capstone Mobile Technologies, Llc System and method for remotely monitoring and controlling a water meter
US8690117B2 (en) 2006-05-04 2014-04-08 Capstone Metering Llc Water meter
US7667968B2 (en) 2006-05-19 2010-02-23 Exceptional Innovation, Llc Air-cooling system configuration for touch screen
CN100440841C (en) * 2006-05-29 2008-12-03 中国移动通信集团公司 Method for distributing address for intelligent information household electronic equipments in household network
US10079839B1 (en) 2007-06-12 2018-09-18 Icontrol Networks, Inc. Activation of gateway device
CN101166141B (en) * 2006-10-20 2010-04-07 中国科学院声学研究所 Built-in network terminal with routing function and its routing function realization method
WO2008073658A2 (en) * 2006-11-09 2008-06-19 Exceptional Innovation, Llc. Portable device for convergence and automation solution
CN101179477B (en) * 2006-11-10 2010-12-08 中国科学院声学研究所 Method for implementing built-in router
US20100287287A1 (en) * 2006-12-21 2010-11-11 Daniele Trentini Network Apparatus and Method for Translating Media Access Control Addresses
US11706279B2 (en) 2007-01-24 2023-07-18 Icontrol Networks, Inc. Methods and systems for data communication
CN101247297B (en) * 2007-02-16 2010-07-14 华为技术有限公司 Device, system and method for automatically configuring application terminal in family network
US7633385B2 (en) 2007-02-28 2009-12-15 Ucontrol, Inc. Method and system for communicating with and controlling an alarm system from a remote server
US8451986B2 (en) 2007-04-23 2013-05-28 Icontrol Networks, Inc. Method and system for automatically providing alternate network access for telecommunications
US11601810B2 (en) 2007-06-12 2023-03-07 Icontrol Networks, Inc. Communication protocols in integrated systems
US10423309B2 (en) 2007-06-12 2019-09-24 Icontrol Networks, Inc. Device integration framework
US10666523B2 (en) 2007-06-12 2020-05-26 Icontrol Networks, Inc. Communication protocols in integrated systems
US11316753B2 (en) 2007-06-12 2022-04-26 Icontrol Networks, Inc. Communication protocols in integrated systems
US20180198788A1 (en) * 2007-06-12 2018-07-12 Icontrol Networks, Inc. Security system integrated with social media platform
US11423756B2 (en) 2007-06-12 2022-08-23 Icontrol Networks, Inc. Communication protocols in integrated systems
US11646907B2 (en) 2007-06-12 2023-05-09 Icontrol Networks, Inc. Communication protocols in integrated systems
US10498830B2 (en) 2007-06-12 2019-12-03 Icontrol Networks, Inc. Wi-Fi-to-serial encapsulation in systems
US11212192B2 (en) 2007-06-12 2021-12-28 Icontrol Networks, Inc. Communication protocols in integrated systems
US11089122B2 (en) 2007-06-12 2021-08-10 Icontrol Networks, Inc. Controlling data routing among networks
US10389736B2 (en) 2007-06-12 2019-08-20 Icontrol Networks, Inc. Communication protocols in integrated systems
US11218878B2 (en) 2007-06-12 2022-01-04 Icontrol Networks, Inc. Communication protocols in integrated systems
US11237714B2 (en) 2007-06-12 2022-02-01 Control Networks, Inc. Control system user interface
US10523689B2 (en) 2007-06-12 2019-12-31 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US10616075B2 (en) 2007-06-12 2020-04-07 Icontrol Networks, Inc. Communication protocols in integrated systems
US10051078B2 (en) 2007-06-12 2018-08-14 Icontrol Networks, Inc. WiFi-to-serial encapsulation in systems
US10223903B2 (en) 2010-09-28 2019-03-05 Icontrol Networks, Inc. Integrated security system with parallel processing architecture
US11831462B2 (en) 2007-08-24 2023-11-28 Icontrol Networks, Inc. Controlling data routing in premises management systems
US11916928B2 (en) 2008-01-24 2024-02-27 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US20170185278A1 (en) 2008-08-11 2017-06-29 Icontrol Networks, Inc. Automation system user interface
US11258625B2 (en) 2008-08-11 2022-02-22 Icontrol Networks, Inc. Mobile premises automation platform
US11792036B2 (en) 2008-08-11 2023-10-17 Icontrol Networks, Inc. Mobile premises automation platform
US11729255B2 (en) 2008-08-11 2023-08-15 Icontrol Networks, Inc. Integrated cloud system with lightweight gateway for premises automation
US11758026B2 (en) 2008-08-11 2023-09-12 Icontrol Networks, Inc. Virtual device systems and methods
MX2011004330A (en) 2008-10-27 2011-08-03 Mueller Int Llc Infrastructure monitoring system and method.
WO2010089677A1 (en) * 2009-02-05 2010-08-12 Koninklijke Philips Electronics N.V. Managing a home network
US8638211B2 (en) 2009-04-30 2014-01-28 Icontrol Networks, Inc. Configurable controller and interface for home SMA, phone and multimedia
CN101888396B (en) * 2009-05-12 2013-08-28 华为技术有限公司 Method for calling equipment capacity, micro technical equipment and server
AU2010249499B2 (en) * 2009-05-22 2015-01-29 Mueller International Llc Infrastructure monitoring devices, systems, and methods
FR2947407B1 (en) * 2009-06-25 2011-11-11 Philippe Couillabin INTERNET DOMOTIC SYSTEM.
US8510792B2 (en) * 2009-11-25 2013-08-13 At&T Intellectual Property I, L.P. Gated network service
US20110143769A1 (en) * 2009-12-16 2011-06-16 Microsoft Corporation Dual display mobile communication device
CN101754434A (en) * 2010-01-20 2010-06-23 中兴通讯股份有限公司 Access method, system and device
US8634873B2 (en) * 2010-03-17 2014-01-21 Microsoft Corporation Mobile communication device having multiple, interchangeable second devices
US20110276885A1 (en) * 2010-05-04 2011-11-10 Qwest Communications International Inc. Multi-client local network base station
MX348843B (en) 2010-06-16 2017-06-26 Mueller Int Llc * Infrastructure monitoring devices, systems, and methods.
US8836467B1 (en) 2010-09-28 2014-09-16 Icontrol Networks, Inc. Method, system and apparatus for automated reporting of account and sensor zone information to a central station
CN102480438B (en) * 2010-11-24 2014-04-09 中兴通讯股份有限公司 Domestic gateway equipment and upgrading method thereof
US11750414B2 (en) 2010-12-16 2023-09-05 Icontrol Networks, Inc. Bidirectional security sensor communication for a premises security system
US9147337B2 (en) 2010-12-17 2015-09-29 Icontrol Networks, Inc. Method and system for logging security event data
ES2386048B1 (en) * 2010-12-27 2013-05-07 Telefónica, S.A. DOMESTIC PASSENGER SYSTEM TO ACCESS WIDE BAND SERVICES
US9143480B2 (en) * 2011-01-10 2015-09-22 Secure Global Solutions, Llc Encrypted VPN connection
US8769060B2 (en) * 2011-01-28 2014-07-01 Nominum, Inc. Systems and methods for providing DNS services
US8833390B2 (en) 2011-05-31 2014-09-16 Mueller International, Llc Valve meter assembly and method
US8855569B2 (en) 2011-10-27 2014-10-07 Mueller International, Llc Systems and methods for dynamic squelching in radio frequency devices
US8660134B2 (en) 2011-10-27 2014-02-25 Mueller International, Llc Systems and methods for time-based hailing of radio frequency devices
US20130114582A1 (en) * 2011-11-03 2013-05-09 Digi International Inc. Wireless mesh network device protocol translation
US20140156844A1 (en) * 2012-11-30 2014-06-05 Alexandros Cavgalar Gateway device, system and method
AU2012345853B2 (en) * 2011-11-30 2016-09-29 Ulterius Technologies, Llc Gateway device, system and method
CN103581348A (en) * 2012-07-24 2014-02-12 深圳市腾讯计算机系统有限公司 Network address translation method and system
CA3128758A1 (en) 2013-03-15 2014-09-25 Mueller International, Llc System for measuring properties of water in a water distribution system
US10164989B2 (en) 2013-03-15 2018-12-25 Nominum, Inc. Distinguishing human-driven DNS queries from machine-to-machine DNS queries
CN103391226B (en) * 2013-07-31 2016-05-04 迈普通信技术股份有限公司 A kind of ppp link detects maintaining method and system
EP2884698A1 (en) * 2013-12-16 2015-06-17 Gemalto M2M GmbH Method for interaction of a device appliance and a communication unit
US9450915B1 (en) * 2014-01-02 2016-09-20 vIPtela Inc. Bi-directional NAT traversal using endpoint assigned discriminators
US11146637B2 (en) 2014-03-03 2021-10-12 Icontrol Networks, Inc. Media content management
US11405463B2 (en) 2014-03-03 2022-08-02 Icontrol Networks, Inc. Media content management
US10637681B2 (en) 2014-03-13 2020-04-28 Silicon Laboratories Inc. Method and system for synchronization and remote control of controlling units
US9494249B2 (en) 2014-05-09 2016-11-15 Mueller International, Llc Mechanical stop for actuator and orifice
WO2015174968A1 (en) * 2014-05-13 2015-11-19 Hewlett-Packard Development Company, L.P. Network access control at controller
US9565620B2 (en) 2014-09-02 2017-02-07 Mueller International, Llc Dynamic routing in a mesh network
US9870534B1 (en) 2014-11-06 2018-01-16 Nominum, Inc. Predicting network activities associated with a given site
CN104601379A (en) * 2015-01-29 2015-05-06 太仓市同维电子有限公司 Method for saving traffic and surfing internet for passive optical network (PON) home gateway unit
US10897451B2 (en) 2015-02-27 2021-01-19 Radio Ip Software Inc. System and method for transmitting over multiple simultaneous communication networks by using point-to-point protocol over ethernet
US11041839B2 (en) 2015-06-05 2021-06-22 Mueller International, Llc Distribution system monitoring
US10608985B2 (en) * 2015-08-14 2020-03-31 Oracle International Corporation Multihoming for tunneled encapsulated media
EP3297215B1 (en) * 2016-09-16 2021-06-30 Deutsche Telekom AG System and use of a supplementary access gateway device for providing an enhanced and/or supplementary network connectivity to at least one client device, method for providing an enhanced and/or supplementary network connectivity to at least one client device
EP3297216B1 (en) * 2016-09-16 2021-06-23 Deutsche Telekom AG System for providing an enhanced and/or supplementary network connectivity to at least one client device, use of a mobile phone or a mobile computing device, comprising a corresponding software application, as a supplementary access gateway device.
CN106713084B (en) * 2016-12-01 2020-06-09 杭州鸿信智能工程有限公司 Multi-gateway system of Internet of things
US10637673B2 (en) 2016-12-12 2020-04-28 Silicon Laboratories Inc. Energy harvesting nodes in a mesh network
US10776798B2 (en) * 2017-04-25 2020-09-15 Comscore, Inc. Device identification systems and methods
US11725366B2 (en) 2020-07-16 2023-08-15 Mueller International, Llc Remote-operated flushing system

Citations (95)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3375208A (en) 1967-07-26 1968-03-26 Esb Inc Method for preparing a microporous thermoplastic resin material
US4425410A (en) 1979-12-10 1984-01-10 American Can Company Drying agent in multi-layer polymeric structure
US4965798A (en) 1989-02-09 1990-10-23 Data General Corporation Apparatus for flexibly allocating bandwidth for a point-to-point, serial, bidirectional communication path
US5518761A (en) 1992-08-28 1996-05-21 Nippon Shokubai Co., Ltd. Absorbent material absorbent article, and method for production thereof
US5526357A (en) 1991-08-16 1996-06-11 Pinpoint Communications, Inc. Communication system and method for determining the location of a transponder unit
US5563882A (en) 1995-07-27 1996-10-08 At&T Process for converting a point-to-point multimedia call to a bridged multimedia call
US5577197A (en) 1992-10-29 1996-11-19 Mci Communications Corporation Test system for testing electronic transaction processing services at a common carrier network switch
US5602668A (en) 1994-11-30 1997-02-11 International Business Machines Corporation Data communications and illuminated light on the same optical fiber
US5606668A (en) 1993-12-15 1997-02-25 Checkpoint Software Technologies Ltd. System for securing inbound and outbound data packet flow in a computer network
US5706507A (en) 1995-07-05 1998-01-06 International Business Machines Corporation System and method for controlling access to data located on a content server
US5732071A (en) 1993-12-29 1998-03-24 Kabushiki Kaisha Toshiba ATM bridge device and ATM bridging scheme for realizing efficient ATM bridge interconnection
US5745884A (en) 1996-10-21 1998-04-28 Mobile Area Networks, Inc. System and method for billing data grade network use on a per connection basis
US5822523A (en) 1996-02-01 1998-10-13 Mpath Interactive, Inc. Server-group messaging system for interactive applications
US5826000A (en) 1996-02-29 1998-10-20 Sun Microsystems, Inc. System and method for automatic configuration of home network computers
EP0889668A2 (en) 1997-06-30 1999-01-07 Nec Corporation Communication control apparatus having a receiving section with an address filtering section
US5870386A (en) 1991-01-09 1999-02-09 Digital Equipment Corporation Method and apparatus for transparently bridging traffic across wide area networks
US5877724A (en) 1997-03-25 1999-03-02 Trimble Navigation Limited Combined position locating and cellular telephone system with a single shared microprocessor
WO1999019988A2 (en) 1997-10-09 1999-04-22 Infogear Technology Corporation Method and system for network access over a low bandwidth link
US5907831A (en) 1997-04-04 1999-05-25 Lotvin; Mikhail Computer apparatus and methods supporting different categories of users
US5918019A (en) 1996-07-29 1999-06-29 Cisco Technology, Inc. Virtual dial-up protocol for network communication
JPH11275083A (en) 1998-03-19 1999-10-08 Fujitsu Ltd Svc access system in atm-dslam
WO1999052244A1 (en) 1998-04-07 1999-10-14 3Com Corporation Point-to-point protocol with a signaling channel
US5973684A (en) 1995-07-06 1999-10-26 Bell Atlantic Network Services, Inc. Digital entertainment terminal providing dynamic execution in video dial tone networks
US5987611A (en) 1996-12-31 1999-11-16 Zone Labs, Inc. System and methodology for managing internet access on a per application basis for client computers connected to the internet
US6006272A (en) 1998-02-23 1999-12-21 Lucent Technologies Inc. Method for network address translation
US6052750A (en) 1998-01-06 2000-04-18 Sony Corporation Of Japan Home audio/video network for generating default control parameters for devices coupled to the network, and replacing updated control parameters therewith
US6055236A (en) 1998-03-05 2000-04-25 3Com Corporation Method and system for locating network services with distributed network address translation
US6085236A (en) 1998-01-06 2000-07-04 Sony Corporation Of Japan Home audio video network with device control modules for incorporating legacy devices
US6101543A (en) * 1996-10-25 2000-08-08 Digital Equipment Corporation Pseudo network adapter for frame capture, encapsulation and encryption
US6119165A (en) 1997-11-17 2000-09-12 Trend Micro, Inc. Controlled distribution of application programs in a computer network
WO2000072532A1 (en) 1999-05-24 2000-11-30 Rutgers, The State University Of New Jersey System and method for network packet reduction
US6167120A (en) * 1996-11-06 2000-12-26 Lextron Systems, Inc. Apparatus and methods for home networking
CA2312460A1 (en) 1999-08-26 2001-02-26 International Business Machines Corporation Method and system for algorithm-based address-evading network snoop avoider
US6198479B1 (en) 1997-06-25 2001-03-06 Samsung Electronics Co., Ltd Home network, browser based, command and control
WO2001022661A2 (en) 1999-09-20 2001-03-29 Thomson Licensing S.A. Method for device registration in a wireless home network
US6212192B1 (en) 1997-03-14 2001-04-03 Itxc, Inc. Method and apparatus for synchronizing information browsing among multiple systems
US6219706B1 (en) 1998-10-16 2001-04-17 Cisco Technology, Inc. Access control for networks
WO2001061897A2 (en) 2000-02-16 2001-08-23 Motorola Inc. Label-based multiplexing
WO2001060897A1 (en) 2000-02-14 2001-08-23 Capitol Specialty Plastics, Inc. A co-continuous interconnecting channel morphology composition
JP2001237898A (en) 2000-02-24 2001-08-31 Nippon Telegr & Teleph Corp <Ntt> Frame transfer method
US20010036192A1 (en) 2000-03-17 2001-11-01 Chiles David Clyde Home-networking
US6314459B1 (en) 1998-08-13 2001-11-06 U.S. Philips Corporation Home-network autoconfiguration
US6314447B1 (en) 1999-10-04 2001-11-06 Sony Corporation System uses local registry and load balancing procedure for identifying processing capabilities of a remote device to perform a processing task
US6337899B1 (en) 1998-03-31 2002-01-08 International Business Machines Corporation Speaker verification for authorizing updates to user subscription service received by internet service provider (ISP) using an intelligent peripheral (IP) in an advanced intelligent network (AIN)
US6349352B1 (en) 1998-01-06 2002-02-19 Sony Corporation Of Japan Home audio/video network with both generic and parameterized device control
US20020049806A1 (en) 2000-05-16 2002-04-25 Scott Gatz Parental control system for use in connection with account-based internet access server
US6381222B1 (en) 1998-04-28 2002-04-30 Genesys Telecommunications Laboratories, Inc. Noise reduction techniques and apparatus for enhancing wireless data network telephony
US20020071423A1 (en) 1997-03-14 2002-06-13 Mojtaba Mirashrafi Method and apparatus for value added content delivery
US6434596B1 (en) 1999-01-29 2002-08-13 Sony Corporation Method and system for distributed queues in a multimedia network with proxies
US20020116471A1 (en) 2001-02-20 2002-08-22 Koninklijke Philips Electronics N.V. Broadcast and processing of meta-information associated with content material
US6446128B1 (en) 1997-12-01 2002-09-03 Netselector, Inc. Site access via intervening control layer
US20020165860A1 (en) 2001-05-07 2002-11-07 Nec Research Insititute, Inc. Selective retrieval metasearch engine
US20020169764A1 (en) 2001-05-09 2002-11-14 Robert Kincaid Domain specific knowledge-based metasearch system and methods of using
US6487605B1 (en) * 1998-06-30 2002-11-26 Cisco Technology, Inc. Mobile IP mobility agent standby protocol
US6493875B1 (en) 1997-02-19 2002-12-10 Next Level Communications, Inc. In-home wireless
US6496867B1 (en) * 1999-08-27 2002-12-17 3Com Corporation System and method to negotiate private network addresses for initiating tunneling associations through private and/or public networks
US20020191572A1 (en) 2001-06-04 2002-12-19 Nec Usa, Inc. Apparatus for public access mobility lan and method of operation thereof
US20030005455A1 (en) 2001-06-29 2003-01-02 Bowers J. Rob Aggregation of streaming media to improve network performance
US20030009495A1 (en) 2001-06-29 2003-01-09 Akli Adjaoute Systems and methods for filtering electronic content
US6523068B1 (en) * 1999-08-27 2003-02-18 3Com Corporation Method for encapsulating and transmitting a message includes private and forwarding network addresses with payload to an end of a tunneling association
US6526581B1 (en) 1999-08-03 2003-02-25 Ucentric Holdings, Llc Multi-service in-home network with an open interface
US6535517B1 (en) 1997-06-20 2003-03-18 Telefonaktiebolaget L M Ericsson (Publ) Network access device monitoring
US6546419B1 (en) 1998-05-07 2003-04-08 Richard Humpleman Method and apparatus for user and device command and control in a network
US6557037B1 (en) 1998-05-29 2003-04-29 Sun Microsystems System and method for easing communications between devices connected respectively to public networks such as the internet and to private networks by facilitating resolution of human-readable addresses
US6564327B1 (en) 1998-12-23 2003-05-13 Worldcom, Inc. Method of and system for controlling internet access
US20030115345A1 (en) * 1999-06-23 2003-06-19 Herman Chien Methods and apparatus for masking destination addresses to reduce traffic over a communication link
US20030123465A1 (en) 2001-12-28 2003-07-03 Hughes Electronics Corporation System and method for content filtering using static source routes
US6603762B1 (en) 1999-03-12 2003-08-05 Lextron Systems, Inc. System for controlling processing of data passing through network gateway between two disparate communications network
US6606659B1 (en) 2000-01-28 2003-08-12 Websense, Inc. System and method for controlling access to internet sites
US6615357B1 (en) * 1999-01-29 2003-09-02 International Business Machines Corporation System and method for network address translation integration with IP security
US6631416B2 (en) * 2000-04-12 2003-10-07 Openreach Inc. Methods and systems for enabling a tunnel between two computers on a network
US6640251B1 (en) * 1999-03-12 2003-10-28 Nortel Networks Limited Multicast-enabled address resolution protocol (ME-ARP)
US6638415B1 (en) 1995-11-16 2003-10-28 Lifescan, Inc. Antioxidant sensor
US6643684B1 (en) 1998-10-08 2003-11-04 International Business Machines Corporation Sender- specified delivery customization
US6654373B1 (en) 2000-06-12 2003-11-25 Netrake Corporation Content aware network apparatus
US6654792B1 (en) * 2000-02-28 2003-11-25 3Com Corporation Method and architecture for logical aggregation of multiple servers
US6671739B1 (en) * 2000-07-10 2003-12-30 International Business Machines Corporation Controlling network access by modifying packet headers at a local hub
US20040006621A1 (en) 2002-06-27 2004-01-08 Bellinson Craig Adam Content filtering for web browsing
US20040019588A1 (en) 2002-07-23 2004-01-29 Doganata Yurdaer N. Method and apparatus for search optimization based on generation of context focused queries
US6693878B1 (en) * 1999-10-15 2004-02-17 Cisco Technology, Inc. Technique and apparatus for using node ID as virtual private network (VPN) identifiers
US6694349B1 (en) 1998-11-25 2004-02-17 Sony Corporation Method and system for message dispatching in a home audio/video network
US6697864B1 (en) * 1999-10-18 2004-02-24 Microsoft Corporation Login architecture for network access through a cable system
US6704031B1 (en) 2000-04-07 2004-03-09 America Online, Inc. Toolbar tracking
US6708219B1 (en) * 1999-10-26 2004-03-16 3Com Corporation Method and system for dual-network address utilization
US6738382B1 (en) * 1999-02-24 2004-05-18 Stsn General Holdings, Inc. Methods and apparatus for providing high speed connectivity to a hotel environment
US6745367B1 (en) 1999-09-27 2004-06-01 International Business Machines Corporation Method and computer program product for implementing parental supervision for internet browsing
US6754321B1 (en) 2000-02-22 2004-06-22 International Business Machines Corporation Naming convention for different types of device, and apparatus and methods using the naming convention
US6757836B1 (en) 2000-01-10 2004-06-29 Sun Microsystems, Inc. Method and apparatus for resolving partial connectivity in a clustered computing system
US6802068B1 (en) * 1996-10-16 2004-10-05 International Business Machines Corporation Addressless internetworking
US20050175020A1 (en) * 2004-02-05 2005-08-11 Samsung Electronics Co., Ltd. Tunneling service method and system
US6954861B2 (en) 2000-07-14 2005-10-11 America Online, Inc. Identifying unauthorized communication systems based on their memory contents
US7027652B1 (en) 1999-11-18 2006-04-11 Hewlett-Packard Company Information capture and processing
US7051116B1 (en) 2001-06-21 2006-05-23 America Online, Inc. Client device identification when communicating through a network address translator device
US7079499B1 (en) * 1999-09-08 2006-07-18 Nortel Networks Limited Internet protocol mobility architecture framework
US7124938B1 (en) 1999-03-24 2006-10-24 Microsoft Corporation Enhancing smart card usage for associating media content with households

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0676878A1 (en) 1994-04-07 1995-10-11 International Business Machines Corporation Efficient point to point and multi point routing mechanism for programmable packet switching nodes in high speed data transmission networks
US20020193301A1 (en) * 1999-08-19 2002-12-19 Stem Cell Pharmaceuticals, Inc. TGF-alpha polypeptides, functional fragments and methods of use therefor
US6658415B1 (en) 2000-04-28 2003-12-02 International Business Machines Corporation Monitoring and managing user access to content via a universally accessible database

Patent Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3375208A (en) 1967-07-26 1968-03-26 Esb Inc Method for preparing a microporous thermoplastic resin material
US4425410A (en) 1979-12-10 1984-01-10 American Can Company Drying agent in multi-layer polymeric structure
US4965798A (en) 1989-02-09 1990-10-23 Data General Corporation Apparatus for flexibly allocating bandwidth for a point-to-point, serial, bidirectional communication path
US5870386A (en) 1991-01-09 1999-02-09 Digital Equipment Corporation Method and apparatus for transparently bridging traffic across wide area networks
US5526357A (en) 1991-08-16 1996-06-11 Pinpoint Communications, Inc. Communication system and method for determining the location of a transponder unit
US5518761A (en) 1992-08-28 1996-05-21 Nippon Shokubai Co., Ltd. Absorbent material absorbent article, and method for production thereof
US5577197A (en) 1992-10-29 1996-11-19 Mci Communications Corporation Test system for testing electronic transaction processing services at a common carrier network switch
US5606668A (en) 1993-12-15 1997-02-25 Checkpoint Software Technologies Ltd. System for securing inbound and outbound data packet flow in a computer network
US5732071A (en) 1993-12-29 1998-03-24 Kabushiki Kaisha Toshiba ATM bridge device and ATM bridging scheme for realizing efficient ATM bridge interconnection
US5602668A (en) 1994-11-30 1997-02-11 International Business Machines Corporation Data communications and illuminated light on the same optical fiber
US5706507A (en) 1995-07-05 1998-01-06 International Business Machines Corporation System and method for controlling access to data located on a content server
US5973684A (en) 1995-07-06 1999-10-26 Bell Atlantic Network Services, Inc. Digital entertainment terminal providing dynamic execution in video dial tone networks
US5563882A (en) 1995-07-27 1996-10-08 At&T Process for converting a point-to-point multimedia call to a bridged multimedia call
US6638415B1 (en) 1995-11-16 2003-10-28 Lifescan, Inc. Antioxidant sensor
US5822523A (en) 1996-02-01 1998-10-13 Mpath Interactive, Inc. Server-group messaging system for interactive applications
US5826000A (en) 1996-02-29 1998-10-20 Sun Microsystems, Inc. System and method for automatic configuration of home network computers
US5852722A (en) 1996-02-29 1998-12-22 Sun Microsystems, Inc. System and method for automatic configuration of home network computers
US5918019A (en) 1996-07-29 1999-06-29 Cisco Technology, Inc. Virtual dial-up protocol for network communication
US6802068B1 (en) * 1996-10-16 2004-10-05 International Business Machines Corporation Addressless internetworking
US5745884A (en) 1996-10-21 1998-04-28 Mobile Area Networks, Inc. System and method for billing data grade network use on a per connection basis
US6101543A (en) * 1996-10-25 2000-08-08 Digital Equipment Corporation Pseudo network adapter for frame capture, encapsulation and encryption
US20010000707A1 (en) 1996-11-06 2001-05-03 Dan Kikinis Apparatus and methods for home networking
US6167120A (en) * 1996-11-06 2000-12-26 Lextron Systems, Inc. Apparatus and methods for home networking
US5987611A (en) 1996-12-31 1999-11-16 Zone Labs, Inc. System and methodology for managing internet access on a per application basis for client computers connected to the internet
US6493875B1 (en) 1997-02-19 2002-12-10 Next Level Communications, Inc. In-home wireless
US6212192B1 (en) 1997-03-14 2001-04-03 Itxc, Inc. Method and apparatus for synchronizing information browsing among multiple systems
US20020071423A1 (en) 1997-03-14 2002-06-13 Mojtaba Mirashrafi Method and apparatus for value added content delivery
US5877724A (en) 1997-03-25 1999-03-02 Trimble Navigation Limited Combined position locating and cellular telephone system with a single shared microprocessor
US5907831A (en) 1997-04-04 1999-05-25 Lotvin; Mikhail Computer apparatus and methods supporting different categories of users
US6535517B1 (en) 1997-06-20 2003-03-18 Telefonaktiebolaget L M Ericsson (Publ) Network access device monitoring
US6198479B1 (en) 1997-06-25 2001-03-06 Samsung Electronics Co., Ltd Home network, browser based, command and control
EP0889668A2 (en) 1997-06-30 1999-01-07 Nec Corporation Communication control apparatus having a receiving section with an address filtering section
WO1999019988A2 (en) 1997-10-09 1999-04-22 Infogear Technology Corporation Method and system for network access over a low bandwidth link
US6119165A (en) 1997-11-17 2000-09-12 Trend Micro, Inc. Controlled distribution of application programs in a computer network
US6446128B1 (en) 1997-12-01 2002-09-03 Netselector, Inc. Site access via intervening control layer
US6052750A (en) 1998-01-06 2000-04-18 Sony Corporation Of Japan Home audio/video network for generating default control parameters for devices coupled to the network, and replacing updated control parameters therewith
US6085236A (en) 1998-01-06 2000-07-04 Sony Corporation Of Japan Home audio video network with device control modules for incorporating legacy devices
US6349352B1 (en) 1998-01-06 2002-02-19 Sony Corporation Of Japan Home audio/video network with both generic and parameterized device control
US6006272A (en) 1998-02-23 1999-12-21 Lucent Technologies Inc. Method for network address translation
US6055236A (en) 1998-03-05 2000-04-25 3Com Corporation Method and system for locating network services with distributed network address translation
JPH11275083A (en) 1998-03-19 1999-10-08 Fujitsu Ltd Svc access system in atm-dslam
US6337899B1 (en) 1998-03-31 2002-01-08 International Business Machines Corporation Speaker verification for authorizing updates to user subscription service received by internet service provider (ISP) using an intelligent peripheral (IP) in an advanced intelligent network (AIN)
WO1999052244A1 (en) 1998-04-07 1999-10-14 3Com Corporation Point-to-point protocol with a signaling channel
US6381222B1 (en) 1998-04-28 2002-04-30 Genesys Telecommunications Laboratories, Inc. Noise reduction techniques and apparatus for enhancing wireless data network telephony
US6421325B1 (en) 1998-04-28 2002-07-16 Genesys Telecomm Lab Inc Methods and apparatus for enhancing wireless data network telephony including a personal router in a client
US6546419B1 (en) 1998-05-07 2003-04-08 Richard Humpleman Method and apparatus for user and device command and control in a network
US6557037B1 (en) 1998-05-29 2003-04-29 Sun Microsystems System and method for easing communications between devices connected respectively to public networks such as the internet and to private networks by facilitating resolution of human-readable addresses
US6487605B1 (en) * 1998-06-30 2002-11-26 Cisco Technology, Inc. Mobile IP mobility agent standby protocol
US6314459B1 (en) 1998-08-13 2001-11-06 U.S. Philips Corporation Home-network autoconfiguration
US6643684B1 (en) 1998-10-08 2003-11-04 International Business Machines Corporation Sender- specified delivery customization
US6219706B1 (en) 1998-10-16 2001-04-17 Cisco Technology, Inc. Access control for networks
US6694349B1 (en) 1998-11-25 2004-02-17 Sony Corporation Method and system for message dispatching in a home audio/video network
US6564327B1 (en) 1998-12-23 2003-05-13 Worldcom, Inc. Method of and system for controlling internet access
US6832322B1 (en) * 1999-01-29 2004-12-14 International Business Machines Corporation System and method for network address translation integration with IP security
US6434596B1 (en) 1999-01-29 2002-08-13 Sony Corporation Method and system for distributed queues in a multimedia network with proxies
US6615357B1 (en) * 1999-01-29 2003-09-02 International Business Machines Corporation System and method for network address translation integration with IP security
US6738382B1 (en) * 1999-02-24 2004-05-18 Stsn General Holdings, Inc. Methods and apparatus for providing high speed connectivity to a hotel environment
US6603762B1 (en) 1999-03-12 2003-08-05 Lextron Systems, Inc. System for controlling processing of data passing through network gateway between two disparate communications network
US6640251B1 (en) * 1999-03-12 2003-10-28 Nortel Networks Limited Multicast-enabled address resolution protocol (ME-ARP)
US7124938B1 (en) 1999-03-24 2006-10-24 Microsoft Corporation Enhancing smart card usage for associating media content with households
WO2000072532A1 (en) 1999-05-24 2000-11-30 Rutgers, The State University Of New Jersey System and method for network packet reduction
US20030115345A1 (en) * 1999-06-23 2003-06-19 Herman Chien Methods and apparatus for masking destination addresses to reduce traffic over a communication link
US6526581B1 (en) 1999-08-03 2003-02-25 Ucentric Holdings, Llc Multi-service in-home network with an open interface
CA2312460A1 (en) 1999-08-26 2001-02-26 International Business Machines Corporation Method and system for algorithm-based address-evading network snoop avoider
US6523068B1 (en) * 1999-08-27 2003-02-18 3Com Corporation Method for encapsulating and transmitting a message includes private and forwarding network addresses with payload to an end of a tunneling association
US6496867B1 (en) * 1999-08-27 2002-12-17 3Com Corporation System and method to negotiate private network addresses for initiating tunneling associations through private and/or public networks
US7079499B1 (en) * 1999-09-08 2006-07-18 Nortel Networks Limited Internet protocol mobility architecture framework
WO2001022661A2 (en) 1999-09-20 2001-03-29 Thomson Licensing S.A. Method for device registration in a wireless home network
US6745367B1 (en) 1999-09-27 2004-06-01 International Business Machines Corporation Method and computer program product for implementing parental supervision for internet browsing
US6314447B1 (en) 1999-10-04 2001-11-06 Sony Corporation System uses local registry and load balancing procedure for identifying processing capabilities of a remote device to perform a processing task
US6693878B1 (en) * 1999-10-15 2004-02-17 Cisco Technology, Inc. Technique and apparatus for using node ID as virtual private network (VPN) identifiers
US6697864B1 (en) * 1999-10-18 2004-02-24 Microsoft Corporation Login architecture for network access through a cable system
US6708219B1 (en) * 1999-10-26 2004-03-16 3Com Corporation Method and system for dual-network address utilization
US7027652B1 (en) 1999-11-18 2006-04-11 Hewlett-Packard Company Information capture and processing
US6757836B1 (en) 2000-01-10 2004-06-29 Sun Microsystems, Inc. Method and apparatus for resolving partial connectivity in a clustered computing system
US6606659B1 (en) 2000-01-28 2003-08-12 Websense, Inc. System and method for controlling access to internet sites
WO2001060897A1 (en) 2000-02-14 2001-08-23 Capitol Specialty Plastics, Inc. A co-continuous interconnecting channel morphology composition
WO2001061897A2 (en) 2000-02-16 2001-08-23 Motorola Inc. Label-based multiplexing
US6754321B1 (en) 2000-02-22 2004-06-22 International Business Machines Corporation Naming convention for different types of device, and apparatus and methods using the naming convention
JP2001237898A (en) 2000-02-24 2001-08-31 Nippon Telegr & Teleph Corp <Ntt> Frame transfer method
US6654792B1 (en) * 2000-02-28 2003-11-25 3Com Corporation Method and architecture for logical aggregation of multiple servers
US20010036192A1 (en) 2000-03-17 2001-11-01 Chiles David Clyde Home-networking
US6704031B1 (en) 2000-04-07 2004-03-09 America Online, Inc. Toolbar tracking
US6631416B2 (en) * 2000-04-12 2003-10-07 Openreach Inc. Methods and systems for enabling a tunnel between two computers on a network
US20020049806A1 (en) 2000-05-16 2002-04-25 Scott Gatz Parental control system for use in connection with account-based internet access server
US6654373B1 (en) 2000-06-12 2003-11-25 Netrake Corporation Content aware network apparatus
US6671739B1 (en) * 2000-07-10 2003-12-30 International Business Machines Corporation Controlling network access by modifying packet headers at a local hub
US6954861B2 (en) 2000-07-14 2005-10-11 America Online, Inc. Identifying unauthorized communication systems based on their memory contents
US20020116471A1 (en) 2001-02-20 2002-08-22 Koninklijke Philips Electronics N.V. Broadcast and processing of meta-information associated with content material
US20020165860A1 (en) 2001-05-07 2002-11-07 Nec Research Insititute, Inc. Selective retrieval metasearch engine
US20020169764A1 (en) 2001-05-09 2002-11-14 Robert Kincaid Domain specific knowledge-based metasearch system and methods of using
US20020191572A1 (en) 2001-06-04 2002-12-19 Nec Usa, Inc. Apparatus for public access mobility lan and method of operation thereof
US7051116B1 (en) 2001-06-21 2006-05-23 America Online, Inc. Client device identification when communicating through a network address translator device
US20030009495A1 (en) 2001-06-29 2003-01-09 Akli Adjaoute Systems and methods for filtering electronic content
US20030005455A1 (en) 2001-06-29 2003-01-02 Bowers J. Rob Aggregation of streaming media to improve network performance
US20030123465A1 (en) 2001-12-28 2003-07-03 Hughes Electronics Corporation System and method for content filtering using static source routes
US20040006621A1 (en) 2002-06-27 2004-01-08 Bellinson Craig Adam Content filtering for web browsing
US20040019588A1 (en) 2002-07-23 2004-01-29 Doganata Yurdaer N. Method and apparatus for search optimization based on generation of context focused queries
US20050175020A1 (en) * 2004-02-05 2005-08-11 Samsung Electronics Co., Ltd. Tunneling service method and system

Non-Patent Citations (56)

* Cited by examiner, † Cited by third party
Title
Advisory Action dated Apr. 19, 2007; U.S. Appl. No. 10/227,243; 3 pages.
Advisory Action dated Feb. 23, 2007; U.S. Appl. No. 10/208,203; 3 pages.
Advisory Action dated Jan. 17, 2007; U.S. Appl. No. 09/810,511; 2 pages.
Advisory Action dated Jan. 19, 2007; U.S. Appl. No. 09/810,511; 3 pages.
Advisory Action dated Jan. 22, 2007; U.S. Appl. No. 10/208,207; 3 pages.
Advisory Action dated Jul. 13, 2005; U.S. Appl. No. 09/810,511; 4 pages.
Advisory Action dated Jul. 24, 2006; U.S. Appl. No. 10/208,181; 3 pages.
Alexander, S. and Droms, R., "DHCP Options and BOOTP Vendor Extensions (Request for Comments: 2132)", The Internet Engineering Task Force, March 1997, pp. 1-32.
Brill, Pamela, Fast & Furious, Mar. 22, 1999, Network Computing, pp. 1-3. *
Business Wire, Feb. 10, 1998, Ramp Network Ships IP Tunneling Kit for WebRamp M3 Family, pp. 1-4. *
Evans, Shara: "Tunnelling through the web" Standards Watch, 'Online'; Mar. 1999; http://www.telsyte.com.au/standardswatch/tunnels.htm, pp. 1-6.
Fei-Yue Wang et al., "An Application Specific Knowledge Engine For Researches In Intelligent Transportation Systems," 2004 IEEE Intelligent Transportation Systems Conference, Washington, DC, Oct. 3-6, 2004, pp. 841-846.
Final Office Action dated Apr. 21, 2006; U.S. Appl. No. 10/208,181; 30 pages.
Final Office Action dated Dec. 22, 2006; U.S. Appl. No. 10/227,243; 12 pages.
Final Office Action dated Jul. 17, 2006; U.S. Appl. No. 09/810,511; 35 pages.
Final Office Action dated Jul. 3, 2007; U.S. Appl. No. 10/208,205; 16 pages.
Final Office Action dated Mar. 10, 2005; U.S. Appl. No. 09/810,511; 54 pages.
Final Office Action dated May 29, 2007; U.S. Appl. No. 10/208,181; 28 pages.
Final Office Action dated Oct. 26, 2006; U.S. Appl. No. 10/208,207; 12 pages.
Final Office Action dated Sep. 22, 2006; U.S. Appl. No. 10/227,243; 12 pages.
Fowler, Dennis, VPN's Become a Virtual Reality, Apr./May 1998, pp. 1-4. *
G. Montenegro et al., "RSIP Support for End-to-end IPsec," pp. 1-18 (Jul. 2000), available at http://www.ietf.org/internet-drafts/draft-ietf-nat-rsip-ipsec-04.txt.
L. Mamakos et al., "A Method for Transmitting PPP Over Ethernet (PPPoE)," pp. 1-15 (Feb. 1999), available at ftp://ftp.isi.edu/in-notes/rfc2516.txt.
M. Borella et al., "Realm Specific IP: Framework," pp. 1-30 (Jul. 2000), available at ftp://ftp.isi.edu/internet-drafts/draft-ietf-nat-rsip-framework-05.txt.
Network Telesystems, NTS Tunnel Builder User's Guide; Mar. 1999. *
Newswire Association Inc, Ramp Networks Announces Comprehensive Virtual Private Network Solution; Targets Corporate Branch Offices; Aug. 9, 1999. *
Non-Final Office Action dated Aug. 2, 2004; U.S. Appl. No. 09/810,511; 33 pages.
Non-Final Office Action dated Nov. 16, 2005; U.S. Appl. No. 09/810,511; 121 pages.
Notice of Allowance dated May 1, 2007; U.S. Appl. No. 09/810,511; 31 pages.
Notice of Allowance dated May 29, 2007; U.S. Appl. No. 10/447,958; 4 pages.
Office Action dated Apr. 13, 2007; U.S. Appl. No. 10/208,203; 22 pages.
Office Action dated Apr. 17, 2006; U.S. Appl. No. 10/227,243; 11 pages.
Office Action dated Apr. 19, 2007; U.S. Appl. No. 10/208,207; 12 pages.
Office Action dated Dec. 19, 2005; U.S. Appl. No. 10/208,205; 13 pages.
Office Action dated Dec. 4, 2006; U.S. Appl. No. 10/208,205; 13 pages.
Office Action dated Jun. 12, 2006; U.S. Appl. No. 10/208,205; 24 pages.
Office Action dated May 22, 2006; U.S. Appl. No. 10/208,203; 9 pages.
Office Action dated May 8, 2006; U.S. Appl. No. 10/208,207; 14 pages.
Office Action dated Nov. 2, 2006; U.S. Appl. No. 10/208,203; 20 pages.
Office Action dated Nov. 20, 2006; U.S. Appl. No. 10/447,958; 11 pages.
Office Action dated Nov. 27, 2006; U.S. Appl. No. 10/208,181; 26 pages.
Office Action dated Sep. 26, 2005; U.S. Appl. No. 10/208,181; 21 pages.
Oztekin B.U. and Karypis, G. and Kumar, V., "Expert Agreement And Content Based Reranking In A Meta Search Environment Using Mearf," Proceedings of the 11<SUP>th </SUP>International Conference on World Wide Web, May 7-11, 2002, Honolulu, Hawaii, pp. 333-344.
P. Srisuresh et al., "IP Network Address Translator (NAT) Terminology and Considerations," http://www.ietf.org/rfc/rfc2663.txt?number=2663, Aug. 1999, pp. 1-30.
P. Srisuresh et al., "Traditional IP Network Address Translator (Traditional NAT)," http://www.ietf.org/rfc/rfc3022.txt?number=3022, Jan. 2001, pp. 1-16.
Patel et al., "DHCP Configuration of IPSEC Tunnel Mode", IPSEC Working Group, Dec. 1999, 10 pages. *
Prosise, Jeff, "ASP.NET Security: An Introductory Guide to Building and Deploying More Secure Sites with ASP.NET and IIS," MSDN Magazine, vol. 17, No. 4, p. 54, Apr. 30, 2002.
R. Droms; Networking Group; Request For Comments: 1541; Oct. 1993. *
Rasolofo Y. et al., "Results Merging Strategies For A Current News Metasearcher," Informationn Processing & Management 39 (2003), Elsevier, Barking GB, pp. 581-609.
Red Creek; "Ravlin 7100, High Performance Virtual Private Network Device for the Enterprise Gateway and ISP"; "http://web.archive.org/web/20000303093640/www.redcreek.com/products/7100.html", Mar. 3, 2000. *
Redback Networks: "PPP over Ethernet" 'Online'; Mar. 1999; http://www.redback.com/en-US/whitepp/pdf/wp<SUB>-</SUB>pppoe<SUB>-</SUB>comparison.pdf, pp. 1-8.
SonicWall Inc., "Configuring DHCP over VPN" Nov. 12, 2002, 11 pages. *
Spoerri A., "Coordinated Views And Tight Coupling To Support Mega Searching," Proceedings of the Second International Conference on Coordinated and Multiple Views in Exploratory Visualization, 2004, pp. 39-48.
Srisuresh et al., RFC 2663-IP Network Address Translator (NAT) Terminology and Considerations, Aug. 1999, Lucent Technologies. *
W. Townsley et al.: Layer 2 Tunneling Protocol "L2TP" IETF, 'Online'; http://www.ietf.org/rfc/rfc2661.txt; Aug. 1999, pp. 1-80.
Zhang, J. and Cheung, C. "Meta-Search-Engine Feature Analysis," Online Information Review, vol. 27, No. 6, 2003, pp. 433-441.

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060193335A1 (en) * 2000-10-27 2006-08-31 Suhail Nanji Tunneling Ethernet
US7680134B2 (en) * 2000-10-27 2010-03-16 Redback Networks Inc. Tunneling Ethernet
US20050050161A1 (en) * 2003-08-29 2005-03-03 Arnold Erich C. Method and system for layer-3 subscriber login in a cable data network
US7653932B2 (en) * 2003-08-29 2010-01-26 Arris Group Method and system for layer-3 subscriber login in a cable data network
US20050066056A1 (en) * 2003-09-22 2005-03-24 Anilkumar Dominic Group-to-group communication over a single connection
US8086747B2 (en) * 2003-09-22 2011-12-27 Anilkumar Dominic Group-to-group communication over a single connection
US20070002873A1 (en) * 2004-01-30 2007-01-04 Matsushita Electric Industrial Co., Ltd. Information processing device, server, communication system, address decision method, address modification method, and program
US7860980B2 (en) * 2004-01-30 2010-12-28 Panasonic Corporation Information processing device, server, communication system, address decision method, address modification method, and program
US9596240B2 (en) 2004-08-30 2017-03-14 Arris Enterprises, Inc. Method and system for layer-3 subscriber login in a cable data network
US20100332906A1 (en) * 2009-06-30 2010-12-30 International Business Machines Corporation Quality of Service Management of End User Devices in an End User Network
US8495428B2 (en) 2009-06-30 2013-07-23 International Business Machines Corporation Quality of service management of end user devices in an end user network
US9954948B2 (en) 2014-07-11 2018-04-24 Microsoft Technology Licensing, Llc Private content distribution network

Also Published As

Publication number Publication date
US20010034759A1 (en) 2001-10-25
AU2001245827A1 (en) 2001-10-03
DE60103625D1 (en) 2004-07-08
EP1266507A2 (en) 2002-12-18
WO2001071977A3 (en) 2002-07-25
US20010036192A1 (en) 2001-11-01
WO2001071977A2 (en) 2001-09-27
CA2403709C (en) 2007-11-20
DE60103625T2 (en) 2005-06-09
EP1266507B1 (en) 2004-06-02
JP2003528539A (en) 2003-09-24
CN1425246A (en) 2003-06-18
CN100337461C (en) 2007-09-12
US7353280B2 (en) 2008-04-01
ATE268529T1 (en) 2004-06-15
CA2403709A1 (en) 2001-09-27

Similar Documents

Publication Publication Date Title
US7359973B2 (en) Home-networking
US7814230B2 (en) Client device identification when communicating through a network address translator device
US7769042B2 (en) Local protocol server
US7796616B2 (en) Apparatus and method for offering connections between network devices located in different home networks
US6801528B2 (en) System and method for dynamic simultaneous connection to multiple service providers
EP1441483B1 (en) Gateway for supporting communications between network devices of different private networks
US7856023B2 (en) Secure virtual private network having a gateway for managing global ip address and identification of devices
KR100424650B1 (en) PPPoA SPOOFING IN POINT-TO-POINT PROTOCOL OVER ATM USING AN xDSL MODEM
US8804562B2 (en) Broadband network system and implementation method thereof
WO2005083959A1 (en) Network access router, network access method, program, and recording medium
US6985935B1 (en) Method and system for providing network access to PPP clients
US20050157703A1 (en) xDSL modem of PPPoE method including DHCP spoofing server and mehtod of connecting to internet using the same
EP1940085A1 (en) Method and device for service binding
US7085836B1 (en) System and method for automatic private IP address selection
JP2003162462A (en) Communication network system
US7397769B2 (en) ADSL modem for providing IPoA, PPPoA, or PPPoE based dial-up networking service over Ethernet
US20060174029A1 (en) Method and device for exchanging data by means of tunnel connection
JP2004048235A (en) Relay apparatus and connection method
MIYAKAWA et al. Yet another mobility support for the Internet
TW201223221A (en) Network apparatus and method for assigning internet protocol addresses for clients

Legal Events

Date Code Title Description
AS Assignment

Owner name: AMERICA ONLINE, INC., VIRGINIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHILES, DAVID CLYDE;BOSCO, ERIC;REEL/FRAME:011822/0052;SIGNING DATES FROM 20010427 TO 20010508

AS Assignment

Owner name: AOL LLC, A DELAWARE LIMITED LIABILITY COMPANY (FOR

Free format text: CONVERSION;ASSIGNORS:CHILES, DAVID CLYDE;BOSCO, ERIC;REEL/FRAME:020331/0062;SIGNING DATES FROM 20010427 TO 20010508

AS Assignment

Owner name: AOL LLC, A DELAWARE LIMITED LIABILITY COMPANY (FOR

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF THE ASSIGNOR PREVIOUSLY RECORDED ON REEL 020331 FRAME 0062. ASSIGNOR(S) HEREBY CONFIRMS THE NAME OF THE ASSIGNOR SHOULD BE AMERICA ONLINE, INC., NOT THE INVENTORS.;ASSIGNOR:AMERICA ONLINE, INC.;REEL/FRAME:020357/0183

Effective date: 20060403

STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: BANK OF AMERICAN, N.A. AS COLLATERAL AGENT,TEXAS

Free format text: SECURITY AGREEMENT;ASSIGNORS:AOL INC.;AOL ADVERTISING INC.;BEBO, INC.;AND OTHERS;REEL/FRAME:023649/0061

Effective date: 20091209

Owner name: BANK OF AMERICAN, N.A. AS COLLATERAL AGENT, TEXAS

Free format text: SECURITY AGREEMENT;ASSIGNORS:AOL INC.;AOL ADVERTISING INC.;BEBO, INC.;AND OTHERS;REEL/FRAME:023649/0061

Effective date: 20091209

AS Assignment

Owner name: AOL INC.,VIRGINIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL LLC;REEL/FRAME:023720/0309

Effective date: 20091204

Owner name: AOL INC., VIRGINIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL LLC;REEL/FRAME:023720/0309

Effective date: 20091204

AS Assignment

Owner name: MAPQUEST, INC, COLORADO

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: AOL ADVERTISING INC, NEW YORK

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: SPHERE SOURCE, INC, VIRGINIA

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: AOL INC, VIRGINIA

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: QUIGO TECHNOLOGIES LLC, NEW YORK

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: TACODA LLC, NEW YORK

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: NETSCAPE COMMUNICATIONS CORPORATION, VIRGINIA

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: TRUVEO, INC, CALIFORNIA

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: LIGHTNINGCAST LLC, NEW YORK

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: YEDDA, INC, VIRGINIA

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

Owner name: GOING INC, MASSACHUSETTS

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416

Effective date: 20100930

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: FACEBOOK, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL INC.;REEL/FRAME:028487/0534

Effective date: 20120614

FPAY Fee payment

Year of fee payment: 8

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12

AS Assignment

Owner name: META PLATFORMS, INC., CALIFORNIA

Free format text: CHANGE OF NAME;ASSIGNOR:FACEBOOK, INC.;REEL/FRAME:058961/0436

Effective date: 20211028