US 7,940,746 B2Grant

Method and system for locating a voice over internet protocol (VoIP) device connected to a network

Issue Date:2011-05-10

•27 Claims

•2 Drawing Sheets

Abstract

A method and system for locating a device connected to a network by determining a current network address for the device and comparing the current network address to a network address in a user profile. If the network addresses match, the device is located based on a physical address associated with the network address in the user profile.

Metadata

Assignee

Comcast Cable Holdings, LLC

Inventor

Jason D. Livingood

Application Information

Application Number:US 10/924,485

Filing Date:2004-08-24

Priority Date:2004-08-24

Art Unit:2614

Classifications

IPC:

H04L12/66

Patent Drawings (2 sheets)

Description

Background of the Invention

[0001] 1. Field of the Invention

[0002] The present invention relates to methods and systems for locating a device connected to a network, such as to locate a Voice Over Internet Protocol (VoIP) device.

[0003] 2. Background Art

[0004] Voice Over Internet Protocol (VoIP) or Internet Protocol (IP) Telephony is a technology that allows a user to make a telephone call over the Internet or a dedicated network in IP packets, instead of over dedicated voice transmission lines.

[0005] With a VoIP service, it is possible for a user to move their VoIP phone to virtually any IP network and have the ability to make and receive calls at their home phone number, which is commonly referred to as a personal telephone number (TN). This is, in fact, one of the benefits of VoIP service, whereby for example a user can take their VoIP phone with them to a hotel with broadband Internet service and have their home phone ring in their hotel room. By contrast, traditional telephone service is tied to a specific location by nature of the circuit-based telephone network.

[0006] The problem with this new capability of VoIP, however, is that the traditional approach utilized by emergency services personnel to locate an individual in the event of an emergency 911 call no longer works reliably in VoIP systems. For example, a VoIP customer's location is recorded as their billing address and all calls originating from the customer's VoIP phone are assumed to be originating from the home address of the customer. If the customer takes the VoIP phone to a second location, such as a shore vacation home for the weekend, and a life-threatening medical emergency prompts the customer to dial 911, then the 911 call would be routed to the Public Safety Answering Point (PSAP) in the area of the customer's billing address, not their current address at the shore vacation residence.

[0007] Some VoIP service providers have attempted to solve this by routing 911 calls on their VoIP network to an intermediate dispatch center that determines which PSAP to route the call to. The intermediate dispatch center includes an operator for answering the emergency 911 call. The operator interrogates the caller to determine their location and then routes the call to the PSAP in the location of the caller. However, this approach can add extra time to the emergency response that can be critical to safety. Moreover, it is a labor intensive and relatively expensive for the service provider to maintain.

Summary of the Invention

[0008] It is, therefore, an object of the present invention to provide a method and system for locating a VoIP customer.

[0009] The present invention contemplates a number of features for locating a VoIP customer, including a processing unit configured for operation on a network used to support VoIP calls. The processing unit preferably includes a processor and a memory configured for locating a VoIP customer by locating a VoIP device used by the customer.

[0010] The processing unit is configured to determine a current network address for the VoIP device on the network. Once the current network address is determined, the processing unit is configured to locate a user profile stored on the processing unit that is associated with the VoIP device. The user profile includes at least one physical address associated with a network address so that the processing unit can determine if the current network address matches with any of the network addresses in the user profile. The processing unit then determines a location of the VoIP device to be at the physical address associated with the network address that matches the current network address of the VoIP device.

[0011] The processing unit can be configured to provide the location of the VoIP device to a public safety answering point (PSAP) in the event of an emergency, such as if the VoIP customer using the VoIP device is making an emergency call.

[0012] One advantage of the present invention is that it permits emergency services to be provided without maintaining an emergency services dispatch center. This permits emergency calls to be routed to the appropriate authorities more quickly, leading to increased safety and security for customers, lower cost for the service provider, and better VoIP service features relative to competitors.

[0013] Another advantage of the present invention is that it is IP-network-based such that it can encompass other VoIP devices beyond telephones, such as instant messaging clients, and other real-time communication tools (text, audio, and/or video-based). In this manner, these non-telephone items can be used to make emergency calls over the VoIP system and have the location of the calling party determined.

Brief Description of the Drawings

[0014] FIG. 1 illustrates a network system in accordance with one aspect of the present invention; and

[0015] FIG. 2 illustrates a flowchart of a method for determining a location of a device connected to a network in accordance with one aspect of the present invention.

Detailed Description of the Preferred Embodiment(s)

[0016] FIG. 1 illustrates a network system 10 in accordance with one aspect of the present invention. The network system 10 generally includes a first access point 14, a second access point 16, and a network 20 such that data and signals communicated over the network 20 are accessible by connected a network device 24 to one of the access points 14 and 16.

[0017] The network device 24 can be any type of computer or other item that is capable of network communications, such as computers, servers, personal digital assistants (PDAs), and the like. In particular, the present invention contemplates that the network device 24 is a Voice Over Internet Protocol (VoIP) device that is configured to make VoIP telephone calls over the network 20. In support thereof, the system 10 further includes a VoIP unit 26, a VoIP emergency location application (VELA) or processing unit 28, and a Public Safety Answering Point (PSAP) 30.

[0018] The VoIP device 24 can relate to any device that is capable of making VoIP calls. Such devices can include a number of features, including a telephone with an analog terminal adapter (ATA), a software-based Session Initiation Protocol (SIP) phone, a stand-alone or embedded Message Transfer Agent (MTA) device, a videophone (whether hardware-based or software-based), a wireless phone (generally cellular phones), a Personal Digital Assistant (PDA) with VoIP software, and the like. Preferably, the VoIP device 24 includes a unique personal telephone number that allows the device 24 to receive VoIP telephone calls anytime that it is connected to the network 20.

[0019] The first and second access points 14 and 16 are nodes or other features that are configured to connect the network device 24 to the network 20. The system 10 shown in FIG. 1 only indicates two access points 14 and 16, but it is contemplated that the system 10 may include any number of access points in any number of geographical areas. Preferably, a network address, such as an IP address, is associated with each access point to identify its location on the network 20.

[0020] The network 20 generally relates to any configuration that permits network communication and VoIP calls, such as through the exchange or transfer of electronic signals and packets over private IP networks, the Internet, or public switching telephone network (PSTN). It can include servers, databases, softswitches, and the like which function to enable, route, and/or control voice, video, and text-based communications and can include items generally described as VoIP softswitches, PacketCable Call Management Servers (CMS), VoIP call servers, IP Public Branch Exchanges (PBXs), SIP Proxy servers, SIP Registrar servers, SIP switches, and the like.

[0021] The PSAP 30 generally relates to a dispatch office that routes incoming 911 calls, or directly dispatches a public service department, such as a fire, police, or other emergency department. Preferably, the PSAP can receive calls over a PSTN and electronically over the Internet or other IP networks, or through other communications means, such as satellite or other wireless communication. In particular, the PSAP may be an enhanced 911 (E911) dispatch center that is capable of exchanging signals through IP-network-based applications, such as instant messaging clients, real-time communication tools (text, audio, and/or video-based), and other non-telephone clients.

[0022] The VELA 28 is configured in accordance with the present invention to communicate with the network 20 and to determine the location of a user on the network 20 based on a location of the network device 24, such as by determining whether the network device 24 is at the first access point 14 or the second access point 16. This can be advantageous for locating the user in the event of an emergency, such as when the user makes an emergency 911 call using a VoIP device from one of the access points 14 and 16.

[0023] The VELA 28 preferably includes an interface 36 that is configured for exchanging signals and packets with the network 20, such as for communicating with the VoIP device 24 and/or the PSAP 30 by exchanging signals and packets over the network to one or more of the access points 14 and 16. Preferably, the interface 36 includes an Interactive Voice Response (IVR) unit, Text to Speech (TTS), and/or a Speech to Text (STT) unit, which enables the interface 36 to convert speech received by the interface to electronic signals and to similarly output electronic signals to speech, such as to communicate with the user through the VoIP device 24. In particular, the interface 36 is able to output and receive voice and touch-tone signals to and from the VoIP device 24 so that the VELA 28 can communicate verbally with the user through a dialogue and record the responses of the user thereto.

[0024] The VELA 28 can be configured to route calls to the PSAP 30 via the PSTN using legacy methods of call networking/termination, to route calls via the public Internet or private Internet Protocol (IP) peering point, and to route calls to multiple interfaces of the PSAP 30, such as a primary interface preference and one or more secondary interfaces, based upon the PSAP's capabilities and preferences or the service provider's preferences. In addition, the VELA 28 can contact the secondary interface if the primary interface is not reachable for some reason, such as network congestion, network failure, etc.

[0025] The VELA 28 preferably includes a processor 38 and a memory 40 for controlling operation of the interface 36 and for executing other applications and strategies, which preferably includes a 911 call routing/query response application for transferring 911 calls from the access point to the PSAP associated with a location of the user, as described below in more detail. The VELA 28 can include other optional features, such as a web interface application configured to enable user location configuration, selection, and/or confirmation, and a video/graphic interface application configured to enable user location configuration, selection, and/or confirmation via a textual or graphical interface on a particular type of device (cellular phone screen, video phone screen, etc.).

[0026] The VELA 28 can optionally detect the type of network device 24 based upon information derived from its connection to the network 20. When one of these devices with graphical capabilities is used, the VELA 28 can be configured to, instead of initiating an out-dial, initiate a multimedia message to the user's device or present that device with a graphical interface. The user can respond to that message by pressing buttons on their device, clicking on the interface, or otherwise interacting with the graphical user interface or multimedia message. This interface may take several forms in the future but may be HTML-based, XML-based, or VoiceXML-based using today's technologies.

[0027] The VoIP unit 26 is a processing unit configured to permit and/or control VoIP communications. It can include any number of features, including memory and processors (not shown) that communicate with the network 20 for executing a VoIP application, such as a VoIP telephone call. In general, the system is configured to route calls to the VoIP device 24 based on the telephone number assigned to it so that a user can receive calls on the telephony device at any access point 14 and 16 on the network 20 that is in communication with the VoIP unit 26.

[0028] The system 10 shown in FIG. 1 is only provided for exemplary purposes and is not intended to limit the scope of the present invention. Rather, the present invention contemplates that the system 10 may include more or less features than those shown in FIG. 1. In particular, the VoIP device 24 and each of the access points 14 and 16 are illustrated as separate items, however, the present invention contemplates that an access point may be integrated into the VoIP device 24 and, in addition, that these two items may be further integrated into a fixed or portable communications and/or computing device.

[0029] FIG. 2 illustrates a flowchart 50 of a method for locating the network device (VoIP device) when it is connected to a network. The method is advantageous in locating the user in the event of an emergency 911 call from the network device 24 and for routing the emergency 911 call to the PSAP 30 associated with the location of the user.

[0030] Block 54 relates to provisioning a user for operation with the VELA. The provisioning can include any number of features, and generally comprises creating and storing a user profile in the database of the VELA. The user profile can be created by an operator inputting the user's information into the VELA, by the user inputting the information themselves, such as through a graphical user interface (GUI) or web page, and/or automatically by querying the VoIP device when it is connected to the network, which is advantageous for determining the IP address and network hops associated with the access point to which the user connects the VoIP device, as it may be difficult for the user or operator to input this information. Optionally, block 54 can be skipped and the user profile can be created dynamically upon connecting the VoIP device to one of the access points.

[0031] The user profile preferably identifies the user with a telephone number and includes additional location information, such as a physical address (city, state, zip code, apartment number, etc.) and network address (IP address and network hops) for the access point from which the user intends to connect to the network for making VoIP telephone calls. The network address is associated with the physical address as the physical addresses are more unique than the network addresses. This is because the network addresses may not, by nature of them being shared across what may be a small or large area and one or many people, be at the same location as the user, or at least within a small enough area relative to the access point associated with the user that emergency personnel would be able to locate the user in an emergency. Network addresses may also be dynamically assigned, such that the same physical address will show up at different network addresses over time. The physical location indicates where the user is located when connecting to the access point associated with the current network address so that the user can be located in the event of an emergency 911 call.

[0032] Multiple entries can be made in the user profile if the user intends to use the VoIP device at multiple locations on the network. Preferably, a nickname or another unique identifier is provided if the user profile includes multiple residences or locations for the user so that each location can be easily distinguished. For example, the user may intend to use the VoIP device at home, at a beach vacation home, and at work. In which case, the user profile is provisioned with physical and network address for each of the locations.

[0033] Block 58 relates to connecting the VoIP device to the network, such as if the user intends to make a call or if the user is merely connecting the device to the network to receive calls, which may occur in the act of turning on or plugging in a device. Upon connecting to the network or in response to a message from the VELA, the VoIP device sends a message to the VELA that includes the telephone number assigned with the VoIP device. The VELA analyzes the message to determine the IP address of the access point to which the VoIP device is connected and to determine any network hops between the access point and the VELA, such as by tracerouting the IP address to determine the network hops. This information is then stored in the memory of the VELA for use in determining a location of the user. Depending upon the results of this transaction, the user may be queried by the VELA to confirm his/her correct physical location, select from a list of locations which may or may not be sorted based upon the VELA's best estimate of the location, or choose to configure a new location in the VELA.

[0034] Block 62 relates to determining a current location for the user based on the telephone number and network address determined in block 58. Initially, the VELA uses the telephone number to search the database for a user profile that includes the same telephone number, i.e. to match a user profile with the telephone number. Once the user profile is located, the VELA compares the network address determined in block 58 with the network addresses in the user profile. If one of the network addresses matches, the VELA pulls the associated physical address and controls the interface to contact the user, such as through an out-going call or other message to the user and/or their telephony device. The user is then asked whether the physical address corresponds with the current location of the user. If the user to determine their location. The location is denied, for example, if there is an error during the inputting of the physical location to the user profile, if the user intends to be at a different location but maintains the use of the same access point, and if the user failed to provide a physical address in the user profile. In response to the denial, the VELA interrogates the user further to determine the physical address that they desire to associate with the network address. This information is then stored in the user profile so that it is available the next time the user connects to the network and the current location of the user is noted.

[0035] If none of the network addresses in the user profile match the network address determined in block 58, then the user is in an unknown or new location. In which case, the VELA controls the interface to contact the user, such as through an out-going call or message, to create an entry for the unknown network ID. The entry is similar to those described above, in that the user is questioned by the VELA to determine a physical address and nickname for association with the unknown network address. Once the entry is complete, the physical address associated with the new entry is added to the user's profile and noted as the current location of the user.

[0036] The dialogue to determine the location of the user, as described above, can take any number of forms. For example, the VELA can be configured to provide the following sequential dialogue:

- [0037] 1. This is the 911 Service Application calling. We were unable to automatically determine your location. Please tell us where your phone is connected so that we can connect your call appropriately in case you have an emergency.
  - [0038] a. Press 1 now if you are calling from “Home.”
    - [0039] i. 1 pressed, You are calling from “Home.”
    - [0040] ii. If this is incorrect, press # to go back to the main menu.
    - [0041] iii. If this is correct, press 1 now or hangup.
    - [0042] i. 1 pressed, You are calling from “Home.”
    - [0043] ii. If this is incorrect, press # to go back to the main menu.
    - [0044] iii. If this is correct, press 1 now or hangup.
    - [0045] iv. If the address of this location has changed, press 2 now to record the new address.
  - [0046] b. Press 2 now if you are calling from “Beach House.”
    - [0047] i. 2 pressed, You are calling from “Beach House.”
    - [0048] ii. If this is incorrect, press # to go back to the main menu.
    - [0049] iii. If this is correct, press 1 now or hangup.
    - [0050] iv. If the address of this location has changed, press 2 now to record the new address. (Speech to Text engine invoked.)
  - [0051] c. Press 3 now if you are calling from “Work.”
    - [0052] i. 3 pressed, You are calling from “Work.”
    - [0053] ii. If this is incorrect, press # to go back to the main menu.
    - [0054] iii. If this is correct, press 1 now or hangup.
    - [0055] iv. If the address of this location has changed, press 2 now to record the new address.
  - [0056] d. Press 4 now if you are calling from a new location.
    - [0057] i. We need a nickname for this location, such as “Home” or “Beach House.” Please speak the nickname of your location now.
    - [0058] ii. We need a house number for this location. Please speak the number now or use your keypad.
    - [0059] iii. We need a street for this location. Please speak the street now.
    - [0060] iv. We need a city for this location. Please speak the city now.
    - [0061] v. We need a State for this location. Please speak the State now.
    - [0062] vi. We need a ZIP Code for this location. Please speak the ZIP Code now or use your keypad. (The ZIP Code could be used to avoid having to ask for the city and state, if desired.)

[0063] The VELA can also be configured with a location matching application (LMA) to facilitate locating the user. In general, the LMA is a process of matching network address determined upon connection of the VoIP device to the network addresses in the user profile when the network addresses fails to exactly match, such as if the user is at the same physical location but using a different access point or an access point the utilizes multiple network address. The VELA utilizes the LMA to predictively attempt to match the network address (location of the user) by executing the following logical operations:

- [0064] 1. Does the current network address detected match a network address in the user profile? If so, match the current network address to the corresponding network address in the user profile and dialogue with the user to determine that the physical address associated therewith corresponds with the current location of the user, if not, proceed to next step.
- [0065] 2. VELA performs a traceroute on the current network address and records every hop in the traceroute. Does the first hop of the traceroute match any of the hops (first or otherwise) for the other network addresses in the user profile. If so, match the current network address to the corresponding network address in the user profile and dialogue with the user to determine the physical address associated therewith corresponds with the current location of the user, if not, proceed to next step.
- [0066] 3. Does the second hop of the traceroute match any of the hops in the Location Database for the user. If so, match the current network address to the corresponding network address in the user profile and dialogue with the user to determine the physical address associated therewith corresponds with the current location of the user, if not, proceed to next step with the remainder of the hops recorded by the trace route.

[0067] As described above, the LMA utilizes intermediate network hops for the current network address of the user to locate the physical address of the user. This can be advantageous to narrow down a geographical area in which the user is located. For example, the physical address of the user can be approximated by the intermediate network hops if they match with any of the intermediate network hops in the user profile.

[0068] Block 66 relates to the user making an emergency 911 call. The emergency call is recognized by the VELA and routed to the appropriate PSAP based upon the location of the user determined in block 62. Each time the user connects their VoIP device to another access point, the process above is repeated to determine the location of the user. As such, anytime the user makes an emergency 911 call the VELA is able to locate the user and route the call to the appropriate PSAP. Preferably, the VELA includes logic or memory maps that facilitate locating the appropriate PSAP. For example, the VELA may include a database of PSAPs that are associated with either the physical address or the network address in the various user profiles.

[0069] When a user dials 911, the softswitch routes the call to the VELA, which routes the call to the appropriate PSAP (see PSAP Interface Technical Options below), based upon the user's current location. No call to an intermediate dispatch center is needed. Alternatively, the softswitch could perform a query to the VELA to obtain the current PSAP for the VoIP user's TN, passing this information back to the softswitch and enabling the softswitch to complete the call itself.

[0070] While embodiments of the invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention.

Claims

Certificate of Correction present

The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.

What is claimed is:

1. A method for locating a user making an emergency call over a network using a voice over Internet protocol (VoIP) device, the method comprising:

determining an emergency call origination network address for the VoIP device upon detecting the emergency call, the emergency call origination network address associated with a current access point on the network through which the VoIP device is making the emergency call;

locating a user profile associated with the VoIP device making the emergency call, the user profile including a physical address associated with a network address, the physical address detailing a location of the user when accessing the network from the network address;

determining if the network address in the located user profile matches with the emergency call origination network address; and

determining the VoIP device to be located at the physical address if the network addresses match.

2. The method of claim 1 further comprising routing the emergency call to a public safety answering point (PSAP) and including therewith the physical address of the VoIP device.

3. A method for locating a voice over Internet telephone (VoIP) device connected to a network, the method comprising:

determining a current network address for the VoIP device on the network;

locating a user profile associated with the VoIP device, the user profile including at least one physical address associated with a network address;

determining if the current network address for the VoIP device matches with any of the network addresses in the user profile; and

determining a location of the VoIP device to be at the physical address associated with the network address that matches the current network address of the VoIP device.

4. The method of claim 3 wherein the user profile is created dynamically upon connecting the VoIP device to the network.

5. The method of claim 4 wherein the user profile is created dynamically by delivering requests for information to the VoIP device and receiving a response thereto.

6. The method of claim 5 wherein the requests and responses thereto are made through speech commands.

7. The method of claim 3 wherein the user profile is created by a user inputting the physical and network addresses into the user profile.

8. The method of claim 3 further comprising associating a telephone number with the VoIP device and the user profile, the user profile being located based on the telephone number.

9. The method of claim 8 further comprising broadcasting the telephone number from the VoIP device upon connecting the VoIP device to the network.

10. The method of claim 3 further comprising confirming the location of the VoIP device.

11. The method of claim 10 wherein the location of the VoIP device is confirmed by contacting the VoIP device and interrogating a user thereof.

12. The method of claim 11 wherein the VoIP device is contacted through a VoIP call and the interrogation is conducted through speech commands.

13. The method of claim 3 further comprising providing the location of the VoIP device to a public safety answering point (PSAP).

14. The method of claim 13 further comprising determining an emergency call being made on the VoIP device and providing the location of the VoIP device to the PSAP in response thereto.

15. An apparatus comprising:

a processor;

a memory having stored therein computer executable instructions, that when executed by the processor, cause the apparatus to perform a method of:

determining a current network address for a VoIP device on a network;

locating a user profile associated with the VoIP device, the user profile stored on the memory and including at least one physical address associated with a network address;

determining if the current network address for the VoIP device matches with any of the network addresses in the user profile; and

determining a location of the VoIP device to be at the physical address associated with the network address that matches the current network address of the VoIP device.

16. The apparatus of claim 15 wherein the method further performs: creating the user profile dynamically upon the VoIP device connecting to the network.

17. The apparatus of claim 16 wherein the method further performs: communicating with the VoIP device and interrogating the VoIP device through the communication in order to dynamically create the user profile.

18. The apparatus of claim 17 wherein the method further performs: interrogating the VoIP device through speech commands.

19. The apparatus of claim 15 wherein the method further performs: receiving inputs for creating the user profile without requiring connection of the VoIP device to the network.

20. The apparatus of claim 15 wherein the method further performs: locating the user profile based on a telephone number assigned to the VoIP device.

21. The apparatus of claim 20 wherein the method further performs: receiving a broadcasted message having the telephone number from the VoIP device upon connection of the VoIP device to the network.

22. The apparatus of claim 15 wherein the method further performs: confirming the location of the VoIP device.

23. The apparatus of claim 22 wherein the method further performs: confirming the location of the VoIP device by contacting the VoIP device and interrogating a user thereof.

24. The apparatus of claim 23 wherein the method further performs: contacting the VoIP device through a VoIP call whereby the interrogation is conducted through speech commands.

25. The apparatus of claim 15 wherein the method further performs: providing the location of the VoIP device to a public safety answering point (PSAP).

26. The apparatus of claim 15 wherein the method further performs: determining an emergency call being made on the VoIP device and providing the location of the VoIP device to the PSAP in response thereto.

27. The apparatus of claim 26 wherein the method further performs: routing the emergency call to the PSAP.

Patent Citations (364)

Patent	Date	Inventor	Cited By
US4456925(A)	1984-06-01	Skerlos	Applicant
US4620289(A)	1986-10-01	Chauvel	Applicant
US4725694(A)	1988-02-01	Auer	Applicant
US4878048(A)	1989-10-01	Gottesman	Applicant
US4916441(A)	1990-04-01	Gombrich	Applicant
US4922529(A)	1990-05-01	Kiel	Applicant
US4995074(A)	1991-02-01	Goldman	Applicant
US5014267(A)	1991-05-01	Tompkins	Applicant
US5157717(A)	1992-10-01	Hitchcock	Applicant
US5187710(A)	1993-02-01	Chau	Applicant
US5253341(A)	1993-10-01	Rozmanith	Applicant
US5274700(A)	1993-12-01	Gechter	Applicant
US5276731(A)	1994-01-01	Arbel	Applicant
US5301050(A)	1994-04-01	Czerwiec	Applicant
US5335276(A)	1994-08-01	Thompson	Applicant
US5341425(A)	1994-08-01	Wasilewski	Applicant
US5349638(A)	1994-09-01	Pitroda	Applicant
US5363431(A)	1994-11-01	Schull	Applicant
US5375161(A)	1994-12-01	Fuller	Applicant
US5393964(A)	1995-02-01	Hamilton	Applicant
US5406557(A)	1995-04-01	Baudoin	Applicant
US5406564(A)	1995-04-01	Okita	Applicant
US5406615(A)	1995-04-01	Miller, II	Applicant
US5428608(A)	1995-06-01	Freeman	Applicant
US5449970(A)	1995-09-01	Kumar	Applicant
US5479411(A)	1995-12-01	Klein	Applicant
US5483588(A)	1996-01-01	Eaton	Applicant
US5488412(A)	1996-01-01	Majeti	Applicant
US5512935(A)	1996-04-01	Majeti	Applicant
US5533110(A)	1996-07-01	Pinard	Applicant
US5534913(A)	1996-07-01	Majeti	Applicant
US5537157(A)	1996-07-01	Washino	Applicant
US5546316(A)	1996-08-01	Buckley	Applicant
US5546447(A)	1996-08-01	Skarbo	Applicant
US5559800(A)	1996-09-01	Mousseau	Applicant
US5561604(A)	1996-10-01	Buckley	Applicant
US5572005(A)	1996-11-01	Hamilton	Applicant
US5583965(A)	1996-12-01	Douma	Applicant
US5584054(A)	1996-12-01	Tyneski	Applicant
US5587735(A)	1996-12-01	Ishida	Applicant
US5592529(A)	1997-01-01	Linsker	Applicant
US5610910(A)	1997-03-01	Focsaneanu	Applicant
US5612997(A)	1997-03-01	Vallelonga, Sr.	Applicant
US5615252(A)	1997-03-01	Sizer, II	Applicant
US5619684(A)	1997-04-01	Goodwin	Applicant
US5628005(A)	1997-05-01	Hurvig	Applicant
US5629978(A)	1997-05-01	Blumhardt	Applicant
US5642348(A)	1997-06-01	Barzegar	Applicant
US5644628(A)	1997-07-01	Schwarzer	Applicant
US5652789(A)	1997-07-01	Miner	Applicant
US5671267(A)	1997-09-01	August	Applicant
US5682195(A)	1997-10-01	Hendricks	Applicant
US5684918(A)	1997-11-01	Abecassis	Applicant
US5689501(A)	1997-11-01	Takase	Applicant
US5689553(A)	1997-11-01	Ahuja	Applicant
US5689555(A)	1997-11-01	Sonnenberg	Applicant
US5696815(A)	1997-12-01	Smyk	Applicant
US5706342(A)	1998-01-01	Baeder	Applicant
US5708961(A)	1998-01-01	Hylton	Applicant
US5712907(A)	1998-01-01	Wegner	Applicant
US5724355(A)	1998-03-01	Bruno	Applicant
US5724411(A)	1998-03-01	Eisdorfer	Applicant
US5724412(A)	1998-03-01	Srinivasan	Applicant
US5737333(A)	1998-04-01	Civanlar	Applicant
US5740230(A)	1998-04-01	Vaudreuil	Applicant
US5740231(A)	1998-04-01	Cohn	Applicant
US5742596(A)	1998-04-01	Baratz	Applicant
US5742905(A)	1998-04-01	Pepe	Applicant
US5745556(A)	1998-04-01	Ronen	Applicant
US5751706(A)	1998-05-01	Land	Applicant
US5751760(A)	1998-05-01	Fuller	Applicant
US5754775(A)	1998-05-01	Adamson	Applicant
US5764752(A)	1998-06-01	Waite	Applicant
US5768513(A)	1998-06-01	Kuthyar	Applicant
US5778173(A)	1998-07-01	Apte	Applicant
US5784444(A)	1998-07-01	Snyder	Applicant
US5790806(A)	1998-08-01	Koperda	Applicant
US5793413(A)	1998-08-01	Hylton	Applicant
US5796394(A)	1998-08-01	Wicks	Applicant
US5796424(A)	1998-08-01	Ely	Applicant
US5796718(A)	1998-08-01	Caterisano	Applicant
US5796952(A)	1998-08-01	Davis	Applicant
US5802045(A)	1998-09-01	Kos	Applicant
US5802160(A)	1998-09-01	Kugell	Applicant
US5802510(A)	1998-09-01	Jones	Applicant
US5805587(A)	1998-09-01	Norris	Applicant
US5809128(A)	1998-09-01	McMullin	Applicant
US5812786(A)	1998-09-01	Seazholtz	Applicant
US5825829(A)	1998-10-01	Borazjani	Applicant
US5825862(A)	1998-10-01	Voit	Applicant
US5832221(A)	1998-11-01	Jones	Applicant
US5850340(A)	1998-12-01	York	Applicant
US5850429(A)	1998-12-01	Joyce	Applicant
US5859895(A)	1999-01-01	Pomp	Applicant
US5859902(A)	1999-01-01	Freedman	Applicant
US5867495(A)	1999-02-01	Elliott	Applicant
US5870565(A)	1999-02-01	Glitho	Applicant
US5883677(A)	1999-03-01	Hofmann	Applicant
US5883942(A)	1999-03-01	Lim	Applicant
US5887259(A)	1999-03-01	Zicker	Applicant
US5894504(A)	1999-04-01	Alfred	Applicant
US5896444(A)	1999-04-01	Perlman	Applicant
US5898668(A)	1999-04-01	Shaffer	Applicant
US5898780(A)	1999-04-01	Liu	Applicant
US5907547(A)	1999-05-01	Foladare	Applicant
US5907598(A)	1999-05-01	Mandalia	Applicant
US5907604(A)	1999-05-01	Hsu	Applicant
US5912952(A)	1999-06-01	Brendzel	Applicant
US5912962(A)	1999-06-01	Bosco	Applicant
US5916302(A)	1999-06-01	Dunn	Applicant
US5917624(A)	1999-06-01	Wagner	Applicant
US5920705(A)	1999-07-01	Lyon	Applicant
US5923731(A)	1999-07-01	McClure	Applicant
US5928335(A)	1999-07-01	Morita	Applicant
US5930340(A)	1999-07-01	Bell	Applicant
US5944795(A)	1999-08-01	Civanlar	Applicant
US5946381(A)	1999-08-01	Danne	Applicant
US5946386(A)	1999-08-01	Rogers	Applicant
US5956717(A)	1999-09-01	Kraay	Applicant
US5970072(A)	1999-10-01	Gammenthaler, Jr.	Applicant
US5970473(A)	1999-10-01	Gerszberg	Applicant
US5978470(A)	1999-11-01	Shaffer	Applicant
US5982774(A)	1999-11-01	Foladare	Applicant
US5982784(A)	1999-11-01	Bell	Applicant
US5987100(A)	1999-11-01	Fortman	Applicant
US5987508(A)	1999-11-01	Agraharam	Applicant
US5991380(A)	1999-11-01	Bruno	Applicant
US5995606(A)	1999-11-01	Civanlar	Applicant
US5999525(A)	1999-12-01	Krishnaswamy	Applicant
US5999598(A)	1999-12-01	Henrick	Applicant
US5999602(A)	1999-12-01	Yang	Applicant
US5999612(A)	1999-12-01	Dunn	Applicant
US6005861(A)	1999-12-01	Humpleman	Applicant
US6005873(A)	1999-12-01	Amit	Applicant
US6006253(A)	1999-12-01	Kumar	Applicant
US6009410(A)	1999-12-01	LeMole	Applicant
US6011909(A)	2000-01-01	Newlin	Applicant
US6014427(A)	2000-01-01	Hanson	Applicant
US6016336(A)	2000-01-01	Hanson	Applicant
US6020915(A)	2000-02-01	Bruno	Applicant
US6023724(A)	2000-02-01	Bhatia	Applicant
US6026441(A)	2000-02-01	Ronen	Applicant
US6028848(A)	2000-02-01	Bhatia	Applicant
US6028867(A)	2000-02-01	Rawson	Applicant
US6031896(A)	2000-02-01	Gardell	Applicant
US6031899(A)	2000-02-01	Wu	Applicant
US6031906(A)	2000-02-01	Rao	Applicant
US6038233(A)	2000-03-01	Hamamoto	Applicant
US6044403(A)	2000-03-01	Gerszberg	Applicant
US6047063(A)	2000-04-01	Perry	Applicant
US6049594(A)	2000-04-01	Furman	Applicant
US6052444(A)	2000-04-01	Ferry	Applicant
US6052594(A)	2000-04-01	Chuang	Applicant
US6052725(A)	2000-04-01	McCann	Applicant
US6061434(A)	2000-05-01	Corbett	Applicant
US6069879(A)	2000-05-01	Chatter	Applicant
US6075796(A)	2000-06-01	Katseff	Applicant
US6078886(A)	2000-06-01	Dragosh	Applicant
US6084292(A)	2000-07-01	Shinohara	Applicant
US6085231(A)	2000-07-01	Agraharam	Applicant
US6088368(A)	2000-07-01	Rubinstain	Applicant
US6101246(A)	2000-08-01	Heinmiller	Applicant
US6104704(A)	2000-08-01	Buhler	Applicant
US6104800(A)	2000-08-01	Benson	Applicant
US6108330(A)	2000-08-01	Bhatia	Applicant
US6115393(A)	2000-09-01	Engel	Applicant
US6118432(A)	2000-09-01	Kotorov	Applicant
US6118768(A)	2000-09-01	Bhatia	Applicant
US6118778(A)	2000-09-01	Amin	Applicant
US6118784(A)	2000-09-01	Tsuchiya	Applicant
US6122357(A)	2000-09-01	Farris	Applicant
US6125376(A)	2000-09-01	Klarlund	Applicant
US6128304(A)	2000-10-01	Gardell	Applicant
US6134235(A)	2000-10-01	Goldman	Applicant
US6137870(A)	2000-10-01	Scherer	Applicant
US6138100(A)	2000-10-01	Dutton	Applicant
US6144401(A)	2000-11-01	Casement	Applicant
US6144667(A)	2000-11-01	Doshi	Applicant
US6148067(A)	2000-11-01	Leipow	Applicant
US6154531(A)	2000-11-01	Clapper	Applicant
US6160880(A)	2000-12-01	Allen	Applicant
US6163531(A)	2000-12-01	Kumar	Applicant
US6167043(A)	2000-12-01	Frantz	Applicant
US6173250(B1)	2001-01-01	Jong	Applicant
US6175619(B1)	2001-01-01	DeSimone	Applicant
US6185288(B1)	2001-02-01	Wong	Applicant
US6188756(B1)	2001-02-01	Mashinsky	Applicant
US6192116(B1)	2001-02-01	Mayak	Applicant
US6201797(B1)	2001-03-01	Leuca	Applicant
US6229810(B1)	2001-05-01	Gerszberg	Applicant
US6229887(B1)	2001-05-01	Albers	Applicant
US6233235(B1)	2001-05-01	Burke	Applicant
US6233313(B1)	2001-05-01	Farris	Applicant
US6243388(B1)	2001-06-01	Mussman	Applicant
US6243445(B1)	2001-06-01	Begeja	Applicant
US6252952(B1)	2001-06-01	Kung	Applicant
US6262979(B1)	2001-07-01	Anderson	Applicant
US6263065(B1)	2001-07-01	Durinovic-Johri	Applicant
US6263503(B1)	2001-07-01	Margulis	Applicant
US6266340(B1)	2001-07-01	Pickett	Applicant
US6266405(B1)	2001-07-01	Madour	Applicant
US6285750(B1)	2001-09-01	Brachman	Applicant
US6289025(B1)	2001-09-01	Pang	Applicant
US6292553(B1)	2001-09-01	Fellingham	Applicant
US6295298(B1)	2001-09-01	Hrastar	Applicant
US6298120(B1)	2001-10-01	Civanlar	Applicant
US6300947(B1)	2001-10-01	Kanevsky	Applicant
US6304566(B1)	2001-10-01	Schessel	Applicant
US6304573(B1)	2001-10-01	Hicks, III	Applicant
US6304636(B1)	2001-10-01	Goldberg	Applicant
US6310889(B1)	2001-10-01	Parsons	Applicant
US6317684(B1)	2001-11-01	Roeseler	Applicant
US6317884(B1)	2001-11-01	Eames	Applicant
US6324279(B1)	2001-11-01	Kalmanek, Jr.	Applicant
US6327346(B1)	2001-12-01	Infosino	Applicant
US6332139(B1)	2001-12-01	Kaneko	Applicant
US6333931(B1)	2001-12-01	LaPier	Applicant
US6339594(B1)	2002-01-01	Civanlar	Applicant
US6343074(B1)	2002-01-01	Pickett	Applicant
US6343115(B1)	2002-01-01	Foladare	Applicant
US6347075(B1)	2002-02-01	Barzegar	Applicant
US6351464(B1)	2002-02-01	Galvin	Applicant
US6353611(B1)	2002-03-01	Norris	Applicant
US6356546(B1)	2002-03-01	Beshai	Applicant
US6359881(B1)	2002-03-01	Gerszberg	Applicant
US6363411(B1)	2002-03-01	Dugan	Applicant
US6366578(B1)	2002-04-01	Johnson	Applicant
US6373817(B1)	2002-04-01	Kung	Applicant
US6374124(B1)	2002-04-01	Slabinski	Applicant
US6385202(B1)	2002-05-01	Katseff	Applicant
US6385646(B1)	2002-05-01	Brown	Applicant
US6389114(B1)	2002-05-01	Dowens	Applicant
US6393014(B1)	2002-05-01	Daly	Applicant
US6393017(B1)	2002-05-01	Galvin	Applicant
US6404735(B1)	2002-06-01	Beshai	Applicant
US6418139(B1)	2002-07-01	Akhtar	Applicant
US6418146(B1)	2002-07-01	Miloslavsky	Applicant
US6421425(B1)	2002-07-01	Bossi	Applicant
US6424646(B1)	2002-07-01	Gerszberg	Applicant
US6425131(B2)	2002-07-01	Crandall	Applicant
US6437692(B1)	2002-08-01	Petite	Applicant
US6438222(B1)	2002-08-01	Burg	Applicant
US6438223(B1)	2002-08-01	Eskafi	Applicant
US6442266(B1)	2002-08-01	Wu	Applicant
US6449766(B1)	2002-09-01	Fleming	Applicant
US6452923(B1)	2002-09-01	Gerszberg	Applicant
US6456699(B1)	2002-09-01	Burg	Applicant
US6459913(B2)	2002-10-01	Cloutier	Applicant
US6467090(B1)	2002-10-01	Brodigan	Applicant
US6480748(B1)	2002-11-01	Gerszberg	Applicant
US6490274(B1)	2002-12-01	Kim	Applicant
US6493324(B1)	2002-12-01	Truetken	Applicant
US6501740(B1)	2002-12-01	Sun	Applicant
US6505348(B1)	2003-01-01	Knowles	Applicant
US6510152(B1)	2003-01-01	Gerszberg	Applicant
US6519246(B1)	2003-02-01	Strahs	Applicant
US6519249(B1)	2003-02-01	Bennefeld	Applicant
US6522628(B1)	2003-02-01	Patel	Applicant
US6532286(B1)	2003-03-01	Burg	Applicant
US6542500(B1)	2003-04-01	Gerszberg	Applicant
US6560222(B1)	2003-05-01	Pounds	Applicant
US6570855(B1)	2003-05-01	Kung	Applicant
US6570974(B1)	2003-05-01	Gerszberg	Applicant
US6590867(B1)	2003-07-01	Ash	Applicant
US6633635(B2)	2003-10-01	Kung	Applicant
US6633848(B1)	2003-10-01	Johnson	Applicant
US6640239(B1)	2003-10-01	Gidwani	Applicant
US6650901(B1)	2003-11-01	Schuster et al.	Examiner
US6687360(B2)	2004-02-01	Kung	Applicant
US6690675(B1)	2004-02-01	Kung	Applicant
US6744767(B1)	2004-06-01	Chiu	Applicant
US6771742(B2)	2004-08-01	Mathis et al.	Examiner
US6775267(B1)	2004-08-01	Kung	Applicant
US6826173(B1)	2004-11-01	Kung	Applicant
US6836476(B1)	2004-12-01	Dunn et al.	Examiner
US6940950(B2)	2005-09-01	Dickinson	Applicant
US7006614(B2)	2006-02-01	Feinberg	Applicant
US7027564(B2)	2006-04-01	James	Examiner
US7042985(B1)	2006-05-01	Wright	Examiner
US7054313(B1)	2006-05-01	Gerszberg	Applicant
US7099443(B2)	2006-08-01	Phillips	Applicant
US7110395(B1)	2006-09-01	Blair	Examiner
US7149499(B1)	2006-12-01	Oran et al.	Examiner
US7180988(B2)	2007-02-01	Phillips	Applicant
US7181401(B2)	2007-02-01	Johnson	Applicant
US7239698(B2)	2007-07-01	Phillips	Applicant
US7257387(B2)	2007-08-01	Laliberte	Examiner
US7260186(B2)	2007-08-01	Zhu et al.	Examiner
US7379436(B2)	2008-05-01	Jiang	Examiner
US7379455(B2)	2008-05-01	Pickett	Applicant
US7391761(B1)	2008-06-01	Ruckart	Applicant
US7453990(B2)	2008-11-01	Welenson et al.	Examiner
US7474742(B2)	2009-01-01	Cook	Applicant
US7496360(B2)	2009-02-01	Sindhwani et al.	Examiner
US7508928(B1)	2009-03-01	Everson et al.	Examiner
US7573988(B2)	2009-08-01	Lee et al.	Examiner
US7580405(B2)	2009-08-01	Laliberte	Examiner
US7586902(B2)	2009-09-01	Epley	Examiner
US7746905(B2)	2010-06-01	Binder	Applicant
US2001/0004382(A1)	2001-06-01	Van Wonterghem	Applicant
US2002/0013941(A1)	2002-01-01	Ward, III	Applicant
US2002/0056112(A1)	2002-05-01	Dureau	Applicant
US2002/0065935(A1)	2002-05-01	Koperda	Applicant
US2003/0081377(A1)	2003-05-01	Lin	Applicant
US2003/0204393(A1)	2003-10-01	Czerwiec	Applicant
US2003/0214939(A1)	2003-11-01	Eldumiati	Applicant
US2004/0001479(A1)	2004-01-01	Pounds	Applicant
US2004/0001501(A1)	2004-01-01	Delveaux	Applicant
US2004/0057425(A1)	2004-03-01	Brouwer et al.	Examiner
US2004/0073597(A1)	2004-04-01	Caveney	Applicant
US2004/0125819(A1)	2004-07-01	Binder	Applicant
US2004/0140928(A1)	2004-07-01	Cleghorn	Applicant
US2004/0151168(A1)	2004-08-01	Phillips	Applicant
US2004/0151290(A1)	2004-08-01	Magarasevic	Applicant
US2004/0153577(A1)	2004-08-01	Phillips	Applicant
US2004/0176085(A1)	2004-09-01	Phillips	Applicant
US2005/0083912(A1)	2005-04-01	Afshar et al.	Examiner
US2005/0141431(A1)	2005-06-01	Caveney	Applicant
US2005/0144645(A1)	2005-06-01	Casey	Applicant
US2005/0213565(A1)	2005-09-01	Barclay et al.	Examiner
US2005/0213716(A1)	2005-09-01	Zhu et al.	Examiner
US2005/0243973(A1)	2005-11-01	Laliberte	Examiner
US2006/0120517(A1)	2006-06-01	Moon et al.	Examiner
US2006/0188073(A1)	2006-08-01	Wright	Examiner
US2006/0293024(A1)	2006-12-01	Benco	Applicant
US2007/0013516(A1)	2007-01-01	Freitag	Applicant
US2007/0092070(A1)	2007-04-01	Croy	Applicant
US2007/0147345(A1)	2007-06-01	Lowmaster	Applicant
US2007/0259645(A1)	2007-11-01	Laliberte	Examiner
US2009/0274145(A1)	2009-11-01	Laliberte	Examiner
US2010/0029246(A1)	2010-02-01	Binning	Examiner
AU199859680	1998-09-01		Applicant
EP758175	1997-02-01		Applicant
EP848560	1997-06-01		Applicant
EP794643	1997-09-01		Applicant
EP800325	1997-10-01		Applicant
EP856981	1998-08-01		Applicant
EP905959	1999-03-01		Applicant
WO9518501	1995-07-01		Applicant
WO9714238	1997-04-01		Applicant
WO9716007	1997-05-01		Applicant
WO9737483	1997-10-01		Applicant
WO9746073	1997-12-01		Applicant
WO9747118	1997-12-01		Applicant
WO9747119	1997-12-01		Applicant
WO9747127	1997-12-01		Applicant
WO9801985	1998-01-01		Applicant
WO9807266	1998-02-01		Applicant
WO9819240	1998-05-01		Applicant
WO9819448	1998-05-01		Applicant
WO9819471	1998-05-01		Applicant
WO9824224	1998-06-01		Applicant
WO9830002	1998-07-01		Applicant
WO9836551	1998-08-01		Applicant
WO9841032	1998-09-01		Applicant
WO9851063	1998-11-01		Applicant
WO9852332	1998-11-01		Applicant
WO9852339	1998-11-01		Applicant
WO9853617	1998-11-01		Applicant
WO9854871	1998-12-01		Applicant
WO9914924	1999-03-01		Applicant
WO9916201	1999-04-01		Applicant
WO9944352	1999-09-01		Applicant
WO9953719	1999-10-01		Applicant

Non-Patent Literature (11)

Bodamer, Charging in Multi—Service Networks, University of Stuttgart, 16 pages, Nov. 12, 1998.Applicant
Odlyzko, et al., A Modest Proposal for Preventing Internet Congestion, Dimacs Technical Report, pp. 1-25, Sep. 1997.Applicant
PKT-TR-ARCH-V01-991201, Packetcable 1.0 Architecture Framework Technical Report, CableLabs, pp. 1-64, Dec. 1, 1999.Applicant
Rupp et al., “Index: A Platform for Determining How People Value the Quality of their Internet Access”, Proceedings of the Sixth IEEE/IFIP International Workshop on Quality of Service, Napa CA, pp. 85-90, May 1998.Applicant
Holliday, Clifford R., “The Residential Gateway”, IEEE Spectrum Magazine; May 1997, pp. 29-31.Applicant
Meggers, J. et al., “Providing Video Conferencing for the Mobile User”, Local Computer Networks, Proceedings 21st IEEE Conference, 1996, pp. 526-534.Applicant
Umehira, M., et al. “Wireless and IP Integrated System Architectures for Broadband Mobile Multimedia Services”, Wireless Communications and Networking Conference, WCNC, 1999 IEEE, 1999, pp. 593-597.Applicant
Albrecht, Markus, et al., “IP Services Over Bluetooth: Leading the Way to a New Mobility”, IEEE 1999, 10 pages.Applicant
Perkins, Charles E., “Mobile-IP, Ad-Hoc Networking, and Nomadicity”, IEEE 1996, pp. 472-476.Applicant
Jacobs, Stuart, “Security of Current Mobile IP Solutions”, IEEE 1997, pp. 1122-1128.Applicant
Deering, S., Internet RFC/STD/FYI/BCP Archives, Internet Protocol, Version 6 specification, Dec. 1995, Xerox PARC, 38 pages.Applicant