Voice Over Internet Protocol (VoIP) location based conferencing

A Voice Over Internet Protocol (VoIP) device uses its location to narrow down known and unknown potential VoIP third parties meeting the user's criteria, based on their physical proximity to the initial caller and other pre-determined characteristics, to join in a phone conference. A VoIP soft switch includes conference bridges that eliminate the conventional requirement that they dial digits for a direct link with another specific VoIP communications device. Instead, location information relating to the initial VoIP user is passed to the VoIP conference bridge, either from the user's VoIP communication device or from their respective location server. The location information is then compared by the VoIP soft switch against other VoIP devices to find potential VoIP users within a defined geographic region surrounding the initial VoIP user. Those VoIP users matching the criteria are sent an Invite message to join the conference, which they may or may not accept.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description

This application is related to and claims priority from a U.S. Provisional Application No. 60/723,960, entitled “Voice Over Internet Protocol (VoIP) Location Based Conferencing”, filed on Oct. 6, 2005; U.S. Provisional Application No. 60/733,789, entitled “Voice Over Internet Protocol (VoIP) Multi-User Conferencing”, filed on Nov. 7, 2005; and U.S. Provisional Application No. 60/723,961, entitled “Voice Over Internet Protocol (VoIP) Location Based 911 Conferencing”, filed on Oct. 6, 2005; the entirety of all three of which are expressly incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to Voice Over Internet (VoIP) protocols and architectures. More particularly, it relates to location based conferencing services using VoIP.

2. Background of the Related Art

Voice-Over-Internet Protocol (VoIP) is a technology that emulates a phone call, but instead of using a circuit based system such as the telephone network, utilizes packetized data transmission techniques most notably implemented in the Internet.

The use of VoIP technology is growing quickly. Given VoIP technology, there are at least three VoIP scenarios:

    • 1. A VoIP UA that is physically connected to a static data cable at a “home” address. For instance, an Analog Telephone Adapter (ATA) that is connected to the “home” data cable and uses traditional telephone devices.
    • 2. A VoIP UA that is physically connected to a data cable at a location different than its “home” address. For instance, a laptop computer device utilized away from home as a VoIP software telephone would be a VoIP ‘visitor’ device as described by this scenario.
    • 3. A VoIP UA that is wireless, physically disconnected from any data cable.

In this situation, the VoIP UA connects to the VoIP service provider via either a wide-are wireless technology (e.g., cellular, PCS, WiMAX) or via a local-area wireless technology (e.g., Wireless Fidelity (WiFi), UWB, etc.) Using a laptop computer or handheld device.

VoIP phone calls are routed to a VoIP voice gateway, from which they are passed on to their destination. A VoIP voice gateway or soft switch is a programmable network switch that can process the signaling for all types of packet protocols. Also known as a ‘media gateway controller,’ ‘call agent,’ or ‘call server,’ such devices are used by carriers that support converged communications services by integrating SS7 telephone signaling with packet networks. Softswitches can support, e.g., IP, DSL, ATM and frame relay.

VoIP telephone technology is quickly replacing conventional switched telephone technology. A location of a given VoIP device may be provisioned to be at a given geographic location, or queried from a home location register (HLR) in a mobile system.

With given VoIP technologies, a VoIP user must know the specific phone number of an individual, business, or other entity that they wish to call. There is no conventional technique for allowing a conference call between two or more VoIP users. In the Internet venue, users can find each other using a “chat room”, but the burden nevertheless remains on the user to search for, identify, and use a specific phone number or Universal Resource Identifier (URI) information to reach specific entities. This creates inefficiency and lack of flexibility with respect to the desire to establish a conference call, preventing VoIP users from managing their own communication needs and preferences. Generally, voice communication using VoIP technologies is limited to only point-to-point direct links between familiar or previously identified parties.

There is a need for an architecture and methodology that simplifies the complexity of conferencing VoIP calls.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a Voice Over Internet Protocol (VoIP) conference bridge comprises a conference bridge application active in a location addressed using Internet Protocol. A module determines a geographic boundary of a given conference. A plurality of Internet interfaces are provided to the conference bridge application, to accept a respective plurality of VoIP telephone users. Wherein a conference is established between the plurality of VoIP telephone users, each of the plurality of VoIP telephone users being within the geographic boundary.

A method of conferencing Voice Over Internet Protocol (VoIP) voice communications devices in accordance with another aspect of the present invention comprises establishing at least one conference bridge. At least one criteria is defined for participation in the given conference bridge. A VoIP call to the conference bridge is received from an initial VoIP user. A location of the initial VoIP is compared to a location of at least one other VoIP user. An invite message is issued to another VoIP user based on a match of the location of the at least one other VoIP user being within a desired proximity to the location of the initial VoIP user.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary architecture of a VoIP conference bridge application operating in a soft switch of a VoIP provider to provide VoIP location based conferencing, in accordance with the principles of the present invention.

FIG. 2 shows an exemplary message flow diagram for establishing a VoIP location based conference, in accordance with the principles of the present invention.

FIG. 3 shows a VoIP user originating an invitation to join a conference bridge in a VoIP soft switch, in a business to business or business to consumer scenario, in accordance with the principles of the present invention.

FIG. 4 shows exemplary signal/call flow for a VoIP user originating an invitation to join a conference bridge sent to other VoIP users as shown in FIG. 3.

FIG. 5 shows a VoIP user originating the transmission of a series of Invitations to join a conference bridge in a VoIP soft switch, in a peer to peer or consumer to consumer scenario, in accordance with the principles of the present invention.

FIG. 6 shows exemplary signal/call flow for a VoIP user originating an invitation to join a conference bridge sent to other VoIP users as shown in FIG. 5.

 DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

A VoIP user from time to time might wish to initiate a conversation with other (known or unknown) VoIP users based on location and other shared attributes/criteria. The need may be for a single point-to-point type connection, or it may extend to the desire for a multi-user conference with other VoIP users.

Existing conferencing systems for putting VoIP users in touch with one another relies upon prior knowledge and contact information existing between the specified users. The present invention provides a way for VoIP users to use VoIP technology to form temporary or permanent “VoIP Communities” or VoIP conferences by initiating an interaction based on location and other shared attributes, supply/demand relationships, or other criteria.

Currently, there is no existing mechanism to create a voice link between VoIP communication devices based on the location of each VoIP user (and potentially other preferences or attributes). Existing VoIP technology does not address this problem for VoIP calls nor does it for any conference established based on location. For instance, while Internet text chat rooms provide a means of communication between party's, Internet text chat rooms do not utilize the user's location to find and invite available individuals/businesses/entities.

The present invention provides the ability for a VoIP user to utilize their own geographic position to narrow down or pinpoint known and even unknown potential VoIP third parties meeting the user's criteria based on their physical location to join in on a phone conference.

FIG. 1 shows an exemplary architecture of a VoIP conference bridge application operating in a VoIP soft switch of a VoIP provider to provide VoIP location based conferencing, in accordance with the principles of the present invention.

In particular, as shown in FIG. 1, a VoIP communications device 104 is serviced by their service provider's soft switch 102. A positioning center 106 provides location data upon request from the soft switch 102. Other VoIP users 110, 112, 114 etc. are potential members of any given conference.

Conference bridges 100 are implemented on the VoIP soft switch 102 located, e.g., at the VoIP service provider's VoIP network.

While the VoIP soft switch 102 is preferably capable of being provisioned with as many VoIP conference bridges 100 as are required in any particular application, only one conference bridge 100 is shown in FIG. 1 for simplicity of explanation.

Also, while the conference bridge 100 is shown implemented in the soft switch 102, it can be embodied within another suitable network element having an Internet Protocol (IP) type connection (e.g., TCP/IP) with the initial user 104 as well as with the potential conferees 110, 112, 114.

The use of a conference bridge 100 eliminates the otherwise conventional requirement that the VoIP user 104 dial digits for a direct link with another specific VoIP communications device 110, 112 or 114. Instead, in accordance with the principles of the present invention, location information relating to the initial VoIP user 104 is passed to the VoIP conference bridge 100, either from the user's VoIP communication device 104 or from their respective location server 106. The location information is then compared by the VoIP soft switch 102 against other VoIP devices 110, 112, 114 etc. to find matching predetermined location-based criteria, e.g., within a geographic vicinity of the user's VoIP communication device 104.

The VoIP soft switch 102 makes use of the location information. Based on the location, the VoIP conference bridge 100 identifies potential other participants to be asked to join the conference currently established by the initial VoIP user 104 on the conference bridge 100, and outputs invites or requests 204 to join that conference 100 to the specific URLs, phone numbers and/or other identifying address information relating to VoIP communications equipment 110, 112, 114 of the potential other participants.

The soft switch 102 also maintains the attributes and rules from other communication devices 110, 112, 114 etc. for receiving conference bridge calls, as well as the fixed location (e.g., a place of business) or the ability to query for a current location (e.g., for mobile communication devices such as mobile phones) for each device. Based on this information, with or without other user input (e.g., to select or prioritize among a list of available third parties), the soft switch 102 invites one or more other communication devices 110, 112, 114, etc. to join the conference bridge. This creates a voice link between the first user 104 and the other third parties 110, 112, 114 without requiring the first user 104 to know the contact information or name of the third parties 110, 112, 114.

FIG. 2 shows an exemplary message flow diagram for establishing a VoIP location based conference, in accordance with the principles of the present invention.

In particular, as shown in FIG. 2, the initial VoIP user 104 sends a request for conference bridge call to the soft switch 102. Preferably the initial VoIP user 104 includes location information with the conference request call 201. However, as depicted in FIG. 1, location information can be obtained from an appropriate positioning server 106 if not available from the initial VoIP user 104.

Subsequent to the incoming conference call 201, suitable potential conferees are determined, and those that are within the geographic boundary pre-set or pre-provisioned into the conference bridge are invited with respective invite messages 204, 206.

In operation, the user's VoIP communication device 104 dials a pre-determined phone number (or URL) to initiate a conference bridge 100 on the relevant VoIP soft switch 102. Various phone numbers (or URL's) may be made available at the VoIP conference bridge 100, each corresponding to a respective VoIP conference bridge 100 each with its own pre-established profile of who will be invited once the conference bridge 100 is first entered by the initiating VoIP user 104.

For instance, one VoIP conference bridge 100 may be profiled to invite all other VoIP users within a geographic boundary of, e.g., 1 mile radius from a center point formed by the location of the initiating VoIP user 104. A geographic boundary need not be merely a distance range. For instance, a geographic boundary may comprise, e.g., the grounds of a college or schoolyard, a workplace, etc., or be as specific as those VoIP users within a given room (e.g., gym) at the college or schoolyard. Another VoIP conference bridge 100 with its own phone number may correspond to invites to all other VoIP users 110, 112, 114 etc. currently located in, e.g., a given sports stadium.

The profiles used to identify the potential other VoIP conference participants may provide additional filtering characteristics beyond the location based information, e.g., other VoIP users who are contained not only within the pre-established geographic boundaries set for a given conference bridge 100, but also listed within a ‘conference buddy’ list pre-listed by the user. Thus, as a result, ‘buddies’ that a user has pre-listed that are within the sports stadium at the time of the user's call will be invited to join a VoIP conference bridge.

FIG. 1 shows use of a VoIP positioning center (VPC) 106. The VoIP soft switch 102 may receive the user's location information either from each of the VoIP communication devices 104, 110, 112, 114 etc., or from the VPC 106.

The VoIP soft switch 102 preferably uses both the location information of the initiating VoIP user 104, together with any profile criteria set for a given conference bridge 100, to determine a list of potential other conferees to be sent Invite messages inviting them to join the established VoIP conference bridge 100. The profile information for the conference bridge 100 is preferably either pre-established by the VoIP service provider (e.g., to set a geographic boundary within a sports stadium), and/or may be input by the initiating user through keypad entry or voice response on the communications device. Alternatively, profile information for a particular conference bridge may be pre-established via an appropriate web page and transmitted via the Internet to the soft switch 102 or other host gateway.

The VoIP soft switch 102 preferably also maintains the attributes and rules from other VoIP communication devices 110, 112, 114 for receiving conference bridge calls, as well as the fixed location (e.g., a place of business) or the ability to query for a current location (e.g., for mobile communication devices such as mobile phones) for each device. Based on this information, with or without other user input (e.g., to select or prioritize among a list of available third parties), the VoIP soft switch 102 invites one or more other VoIP communication devices 110, 112, 114, etc. to join the VoIP conference bridge 100. This creates a voice link between the first VoIP user 104 that initially called into the VoIP conference bridge 100, and the other potential, third party conferees 110, 112, 114, etc., without requiring the first VoIP user 104 to know the name or even the contact information of the other potential, third party conferees 110, 112, 114, etc.

Upon receipt of an invite to a VoIP conference bridge 204, 206, the potential other VoIP users 110, 112, 114, etc. are preferably notified similar to an incoming telephone call, e.g. with a ring signal, though it may be customized to be distinguished from the sound of an otherwise ordinary incoming phone call. For instance, a given unique phone tone may be activated upon receipt of an invite 204, 206 to a conference bridge 100.

In accordance with the principles of the present invention, the VoIP user(s) 110, 112, 114 receiving invitations to join a VoIP conference 100 may be provided with a filter that automatically rejects any/all invite requests not meeting their own specific criteria (e.g., maintained on their VoIP devices 110, 112, 114 themselves, though such filtering may alternatively be performed at a network level, e.g., at the VoIP soft switch 102 or other centralized location.

Benefits of the invention include that there is no effective limit to the number of participants in the conference VoIP call, there are no cold transfers of a call as VoIP invitees enter or leave the conference bridge 100, and there is the ability to continue the conference call even after the initial VoIP user 104 disconnects.

The present invention has particular applicability with any/all VoIP users, VoIP service providers, and/or even Public Safety Access Points (PSAPs).

FIG. 3 shows a VoIP user 104 originating an invitation to join a conference bridge 100 in a VoIP soft switch 102, in a business to business or business to consumer scenario, in accordance with the principles of the present invention.

In particular, as shown in FIG. 3, a VoIP user 104 initiates an invitation or request 204 based on certain pre-defined criteria for a service provider or a peer attribute. The VoIP service provider acquires the user's location information, either directly from the VoIP communications device 104 or by request to the LIS 106, and initiates a conference on the conference bridge 100. The conference bridge 100 issues invitations or notifications to one or more potential VoIP conferee users 110, 112, 114 etc. based on the location of the original user 104 and the specified criteria, by comparison to attribute or provider data for the other VoIP users 110, 112, 114 etc. The conference bridge 100 enables participation by multiple parties and does not depend on the participants' knowledge of or current access to each other's contact information, profile/attributes/business type, or location. In addition, VoIP users can elect when to receive notifications based on their current status (away, available, business hours, etc.)

For instance, the VoIP user 104 would initiate a call to the conference bridge 100, thus initiating the sending of invitations or requests to potential conferees 110, 112, 114 etc. based on certain criteria (e.g., “tow truck drivers currently in Seattle”). Upon receipt of the initial call from the initiating VoIP user 104, the VoIP service provider initiates a conference bridge 100 and issues an Invite or other notification to one or more VoIP users 110, 112, 114 etc. who have selected or subscribed to receive such conference notifications for this particular conference topic (as defined by its criteria). Subscriptions may be semi-permanent criteria for that particular conference bridge 100 (e.g., occupations or interests of the registered user of the relevant VoIP device) or temporary criteria (e.g., passengers on a specific airline flight, ticket agents with extra tickets for a specific event, etc.)

The conference bridge 100 enables participation by multiple parties and does not depend on the participants' knowledge of or current access to each other's contact information. In addition, VoIP users can elect when to receive notifications based on their current status (e.g., away, available).

More sophisticated implementations of the invention include adaptation of the criteria for a given conference bridge 100 to correspond to a particular live auction. For instance, in such application, the matchmaking database 300 functions as an automated auction tool by accepting as criteria for the auction data such as the proposed cost of service, and then connect the lowest bidder of those potential bidders 110, 112, 114 to the conference bridge 100.

Preferably, the initiating VoIP user 104 is allowed to pre-define given criteria for the conference bridge 100, e.g., a maximum number of participants (e.g., the first 4 providers or peers who accept the conference invitation), or other criteria for choosing among multiple users (e.g., to select the VoIP user(s) 110, 112, 114 etc. whose location is closest to the initiating VoIP user 104 who initiated the conference invitation in the first place).

FIG. 4 shows exemplary signal/call flow for an initiating VoIP user 104 calling to establish a conference bridge 100, causing invitations to be transmitted to each potential VoIP conferee using IP protocol (e.g., TCP/IP) to join the conference bridge 100 as shown in FIG. 3. In response, each invited VoIP user 110, 112, 114 may accept or reject the invitation with an Accept or Reject message transmitted via Internet Protocol back to the VoIP soft switch 102 that transmitted the initial invite messages 204, 206.

Offline activity also occurs, separate from the call flow, e.g., to update location data (be it permanent or temporary) and criteria or attributes for the conference bridge 200 itself. Availability data may also be maintained and updated offline, e.g., relating to pre-defined times for the conference bridge 100 to be established, and/or to the current status of the conference bridge 100.

FIG. 5 shows a VoIP user 104 originating the transmission of a series of Invitations 504 to join a conference bridge 100 in a VoIP soft switch 102, in a peer to peer or consumer to consumer scenario, in accordance with the principles of the present invention.

In particular, as shown in FIG. 5, the VoIP user 104 can call a conference bridge 100 and provide particular, customized criteria for the conference. In a peer-to-peer scenario as shown in FIG. 5, the VoIP user 104 issues a peer-to-peer request 550 such as a call searching for tickets to a specific public event (e.g., “Falcons Tickets”), searching for others with a similar hobby or interest (e.g., “Chess Players”), matchmaking services forming a personal add (e.g., “Male 30-35”), etc.

In the disclosed embodiment, the peer-to-peer conference is initiated by a call by an initiating VoIP user 104. The conference bridge 100 may be pre-established with pre-determined criteria, and the initiating VoIP user 104 merely calls the appropriate conference bridge 100. In such case, the VoIP service provider may establish network-wide criteria itself, or may allow customized conference bridges as a service to their subscribers. Alternatively, the criteria for the conference bridge may be established by the initiating VoIP user 104. The criteria may be transmitted to the soft switch to establish the relevant conference bridge 100 preferably with data contained within the call from the initiating VoIP user 104.

The peer attributes and desired geographical boundaries of the conference are maintained in a matchmaking database 500 in communication with the VoIP soft switch 102 or other gateway that hosts the conference bridge 100.

The VoIP soft switch 102 issues a Peer Request 504 with location data to any/all VoIP users 110, 112 and/or 114 fitting the criteria for the conference. In response, those VoIP users 110, 112 and/or 114 who accept entry into the conference (e.g., by activating an ‘Accept’ button on the VoIP communications device), return an Accept message 505 to the inviting VoIP soft switch 102. Those VoIP users 110, 112 and/or 114 that don't accept the Invite (either by activating a ‘Reject’ button on the VoIP communications device, or simply by not responding to the Invite message 204 within a given period of time) return a Reject message 505 to the inviting VoIP soft switch 102.

The invited VoIP users 110, 112, 114 may include a filter allowing through only acceptable Invite messages based on criteria established by or on the receiving VoIP users 110, 112, 114.

FIG. 6 shows exemplary signal/call flow for a VoIP user originating an invitation to join a conference bridge sent to other VoIP users as shown in FIG. 5.

In particular, the peer-to-peer request 550 issued by the VoIP user 104 is depicted in FIG. 6, as are the respective Invite messages 504 and Accept or Reject messages 505 from each of the invited VoIP users 110, 112, 114.

The present invention allows VoIP users to find their most appropriate conferees, provider or peer match with minimal user interaction. This is particularly helpful for mobile VoIP users (e.g., while driving, walking, etc.) Moreover, there is no effective limit to the number of participants in the conference call (within network hardware limits of the conference bridge itself). There is also no risk of cold transfers of a VoIP telephone call as participants aren't handled in point-to-point connections that are transferred but rather join or exit an established conference at will. Furthermore, participants in the conference call can continue in the conference even after the initial user disconnects.

Potential markets for the present invention include VoIP service providers who may implement the inventive VoIP multi-user conferencing as a value added services for users. Other uses of the invention include consumer and business VoIP users with respect to commercial, government, educational activities, and Public Safety Access Points (PSAPs), to name a few.

VoIP location based conferencing in accordance with the principles of the present invention has particular applicability with any/all VoIP users, VoIP service providers, and/or Public Safety Access Points (PSAPs).

While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims

1. A Voice Over Internet Protocol (VoIP) conference bridge, comprising:

a conference bridge application addressable by an Internet Protocol, said conference bridge application adapted to receive a request to establish a conference comprising at least one user entered customized criteria text string for limiting participation in said establishment of said conference;
a module to establish a geographic boundary of a given conference; and
a plurality of Internet interfaces interfaced to said conference bridge application, said plurality of Internet Interfaces accepting communications from a respective plurality of VoIP users;
wherein said conference is established between said plurality of VoIP users based on said geographic boundary and said user entered customized criteria text string.

2. A method of conferencing Voice Over Internet Protocol (VoIP) voice communications devices, comprising:

establishing at least one conference bridge;
receiving at least one user entered customized criteria text string for limiting participation in said given conference bridge;
receiving a VoIP call to said conference bridge from an initial VoIP user;
comparing a location of said initial VoIP user to a location of at least one other VoIP user to establish a proximate distance there between; and
establishing said at least one conference bridge between said VoIP voice communications devices based on said proximate distance and said user entered customized criteria text string.

3. The method of conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 2, further comprising:

requesting a location of said initial VoIP user from a positioning center.

4. The method of conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 2, further comprising:

obtaining a location of said initial VoIP user from said initial VoIP user.

5. The method of conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 2, wherein:

a plurality of conference bridges are established.

6. The method of conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 5, wherein:

said plurality of conference bridges are established on a soft switch.

7. The method of conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 6, wherein:

said soft switch is located in a VoIP service provider's network.

8. The method of conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 2, further comprising:

issuing an invite message to another VoIP user based on a match of said location of said at least one other VoIP user being within a desired proximity to said location of said initial VoIP user.

9. Apparatus for conferencing Voice Over Internet Protocol (VoIP) voice communications devices, comprising:

means for establishing at least one conference bridge;
means for receiving at least one user entered customized criteria text string for limiting participation in said given conference bridge;
means for receiving a VoIP call to said conference bridge from an initial VoIP user;
means for comparing a location of said initial VoIP user to a location of at least one other VoIP user to establish a proximate distance there between; and
means for establishing said at least one conference bridge between said VoIP voice communications devices based on said proximate distance and said user entered customized criteria text string.

10. The apparatus for conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 9, further comprising:

means for requesting a location of said initial VoIP user from a positioning center.

11. The apparatus for conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 9, further comprising:

means for obtaining a location of said initial VoIP user from said initial VoIP user.

12. The apparatus for conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 9, wherein:

said means for establishing at least one conference bridge establishes a plurality of conference bridges.

13. The apparatus for conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 12, wherein:

said plurality of conference bridges are established on a soft switch.

14. The apparatus for conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 13, wherein:

said soft switch is located in a VoIP service provider's network.

15. The apparatus for conferencing Voice Over Internet Protocol (VoIP) voice communications device according to claim 9, further comprising:

means for issuing an invite message to another VoIP user based on a match of said location of said at least one other VoIP user being within a desired proximity to said location of said initial VoIP user.
Referenced Cited
U.S. Patent Documents
1103073 July 1914 O'Connell
4445118 April 24, 1984 Taylor et al.
4494119 January 15, 1985 Wimbush
4651156 March 17, 1987 Martinez
4706275 November 10, 1987 Kamil
4891638 January 2, 1990 Davis
4891650 January 2, 1990 Sheffer
4952928 August 28, 1990 Carroll et al.
4972484 November 20, 1990 Theile et al.
5014206 May 7, 1991 Scribner et al.
5043736 August 27, 1991 Darnell et al.
5055851 October 8, 1991 Sheffer
5068656 November 26, 1991 Sutherland
5068891 November 26, 1991 Marshall
5070329 December 3, 1991 Jasinaki
5081667 January 14, 1992 Drori et al.
5119104 June 2, 1992 Heller
5126722 June 30, 1992 Kamis
5144283 September 1, 1992 Arens et al.
5161180 November 3, 1992 Chavous
5166972 November 24, 1992 Smith
5177478 January 5, 1993 Wagai et al.
5193215 March 9, 1993 Olmer
5208756 May 4, 1993 Song
5214789 May 25, 1993 George
5218367 June 8, 1993 Sheffer et al.
5223844 June 29, 1993 Mansell et al.
5239570 August 24, 1993 Koster et al.
5265630 November 30, 1993 Hartman et al.
5266944 November 30, 1993 Carroll et al.
5283570 February 1, 1994 DeLuca et al.
5289527 February 22, 1994 Tiedemann, Jr.
5293642 March 8, 1994 Lo
5299132 March 29, 1994 Wortham
5301354 April 5, 1994 Schwendeman et al.
5311516 May 10, 1994 Kuznicki et al.
5325302 June 28, 1994 Izidon et al.
5327529 July 5, 1994 Fults et al.
5334974 August 2, 1994 Simms et al.
5335246 August 2, 1994 Yokev et al.
5343493 August 30, 1994 Karimullah
5347568 September 13, 1994 Moody et al.
5351235 September 27, 1994 Lahtinen
5361212 November 1, 1994 Class et al.
5363425 November 8, 1994 Mufti et al.
5365451 November 15, 1994 Wang et al.
5374936 December 20, 1994 Feng
5379451 January 3, 1995 Nakagoshi et al.
5381338 January 10, 1995 Wysocki et al.
5387993 February 7, 1995 Heller et al.
5388147 February 7, 1995 Grimes
5390339 February 14, 1995 Bruckert et al.
5394158 February 28, 1995 Chia
5396227 March 7, 1995 Carroll et al.
5398190 March 14, 1995 Wortham
5406614 April 11, 1995 Hara
5418537 May 23, 1995 Bird
5422813 June 6, 1995 Schuchman et al.
5423076 June 6, 1995 Westergren et al.
5432841 July 11, 1995 Rimer
5434789 July 18, 1995 Fraker et al.
5454024 September 26, 1995 Lebowitz
5461390 October 24, 1995 Hoshen
5470233 November 28, 1995 Fruchterman et al.
5479408 December 26, 1995 Will
5479482 December 26, 1995 Grimes
5485161 January 16, 1996 Vaughn
5485163 January 16, 1996 Singer et al.
5488563 January 30, 1996 Chazelle et al.
5494091 February 27, 1996 Freeman et al.
5497149 March 5, 1996 Fast
5504491 April 2, 1996 Chapman
5506886 April 9, 1996 Maine et al.
5508931 April 16, 1996 Snider
5513243 April 30, 1996 Kage
5515287 May 7, 1996 Hakoyama et al.
5517199 May 14, 1996 DiMattei
5519403 May 21, 1996 Bickley et al.
5530655 June 25, 1996 Lokhoff et al.
5530914 June 25, 1996 McPheters
5532690 July 2, 1996 Hertel
5535434 July 9, 1996 Siddoway et al.
5539395 July 23, 1996 Buss et al.
5539398 July 23, 1996 Hall et al.
5539829 July 23, 1996 Lokhoff et al.
5543776 August 6, 1996 L'Esperance et al.
5546445 August 13, 1996 Dennison et al.
5552772 September 3, 1996 Janky et al.
5555286 September 10, 1996 Tendler
5568119 October 22, 1996 Schipper et al.
5568153 October 22, 1996 Beliveau
5574648 November 12, 1996 Pilley
5579372 November 26, 1996 ÅStröm
5588009 December 24, 1996 Will
5592535 January 7, 1997 Klotz
5594780 January 14, 1997 Wiedeman et al.
5604486 February 18, 1997 Lauro et al.
5606313 February 25, 1997 Allen et al.
5606618 February 25, 1997 Lokhoff et al.
5606850 March 4, 1997 Nakamura
5610815 March 11, 1997 Gudat et al.
5614890 March 25, 1997 Fox
5615116 March 25, 1997 Gudat et al.
5621793 April 15, 1997 Bednarek et al.
5628051 May 6, 1997 Salin
5629693 May 13, 1997 Janky
5633912 May 27, 1997 Tsoi
5636276 June 3, 1997 Brugger
5661652 August 26, 1997 Sprague et al.
5661755 August 26, 1997 Van De Kerkhof et al.
5682600 October 28, 1997 Salin
5689245 November 18, 1997 Noreen et al.
5699053 December 16, 1997 Jonsson
5704029 December 30, 1997 Wright, Jr.
5721781 February 24, 1998 Deo et al.
5731785 March 24, 1998 Lemelson et al.
5740534 April 14, 1998 Ayerst et al.
5761618 June 2, 1998 Lynch et al.
5765152 June 9, 1998 Erickson
5767795 June 16, 1998 Schaphorst
5768509 June 16, 1998 Gunluk
5771353 June 23, 1998 Eggleston et al.
5774533 June 30, 1998 Patel
5774670 June 30, 1998 Montulli
5787357 July 28, 1998 Salin
5794142 August 11, 1998 Vanttila et al.
5797094 August 18, 1998 Houde et al.
5797096 August 18, 1998 Lupien et al.
5802492 September 1, 1998 DeLorme et al.
5806000 September 8, 1998 Vo et al.
5809415 September 15, 1998 Rossmann
5812086 September 22, 1998 Bertiger et al.
5812087 September 22, 1998 Krasner
5822700 October 13, 1998 Hult et al.
5828740 October 27, 1998 Khuc et al.
5835907 November 10, 1998 Newman
5841396 November 24, 1998 Krasner
5857201 January 5, 1999 Wright, Jr. et al.
5864667 January 26, 1999 Barkan
5874914 February 23, 1999 Krasner
5896369 April 20, 1999 Warsta et al.
5920821 July 6, 1999 Seazholtz et al.
5922074 July 13, 1999 Richard et al.
5930250 July 27, 1999 Klok et al.
5930701 July 27, 1999 Skog
5943399 August 24, 1999 Bannister et al.
5945944 August 31, 1999 Krasner
5946629 August 31, 1999 Sawyer et al.
5946630 August 31, 1999 Willars et al.
5950130 September 7, 1999 Coursey
5950137 September 7, 1999 Kim
5953398 September 14, 1999 Hill
5960362 September 28, 1999 Grob et al.
5974054 October 26, 1999 Couts et al.
5978685 November 2, 1999 Laiho
5983099 November 9, 1999 Yao et al.
5987323 November 16, 1999 Huotari
5998111 December 7, 1999 Abe
5999124 December 7, 1999 Sheynblat
6014602 January 11, 2000 Kithil et al.
6032051 February 29, 2000 Hall
6035025 March 7, 2000 Hanson
6049710 April 11, 2000 Nilsson
6052081 April 18, 2000 Krasner
6058300 May 2, 2000 Hanson
6058338 May 2, 2000 Agashe et al.
6061018 May 9, 2000 Sheynblat
6061346 May 9, 2000 Nordman
6064336 May 16, 2000 Krasner
6064875 May 16, 2000 Morgan
6067045 May 23, 2000 Castelloe et al.
6070067 May 30, 2000 Nguyen et al.
6075982 June 13, 2000 Donovan et al.
6081229 June 27, 2000 Soliman et al.
6081508 June 27, 2000 West et al.
6085320 July 4, 2000 Kaliski, Jr.
6101378 August 8, 2000 Barabash et al.
6104931 August 15, 2000 Havinis et al.
6122503 September 19, 2000 Daly
6122520 September 19, 2000 Want et al.
6124810 September 26, 2000 Segal et al.
6131067 October 10, 2000 Girerd et al.
6133874 October 17, 2000 Krasner
6134483 October 17, 2000 Vayanos et al.
6138003 October 24, 2000 Kingdon et al.
6148197 November 14, 2000 Bridges et al.
6148198 November 14, 2000 Anderson et al.
6149353 November 21, 2000 Nilsson
6150980 November 21, 2000 Krasner
6154172 November 28, 2000 Piccionelli et al.
6169891 January 2, 2001 Gorham et al.
6169901 January 2, 2001 Boucher
6169902 January 2, 2001 Kawamoto
6173181 January 9, 2001 Losh
6178505 January 23, 2001 Schneider et al.
6178506 January 23, 2001 Quick, Jr.
6181935 January 30, 2001 Gossman et al.
6185427 February 6, 2001 Krasner et al.
6188354 February 13, 2001 Soliman et al.
6188752 February 13, 2001 Lesley
6188909 February 13, 2001 Alanara et al.
6189098 February 13, 2001 Kaliski, Jr.
6195557 February 27, 2001 Havinis et al.
6198431 March 6, 2001 Gibson
6199045 March 6, 2001 Giniger et al.
6199113 March 6, 2001 Alegre et al.
6205330 March 20, 2001 Winbladh
6208290 March 27, 2001 Krasner
6208854 March 27, 2001 Roberts et al.
6215441 April 10, 2001 Moeglein et al.
6219557 April 17, 2001 Havinis
6223046 April 24, 2001 Hamill-Keays et al.
6226529 May 1, 2001 Bruno et al.
6239742 May 29, 2001 Krasner
6247135 June 12, 2001 Feague
6249680 June 19, 2001 Wax et al.
6249744 June 19, 2001 Morita
6249873 June 19, 2001 Richard et al.
6253203 June 26, 2001 O'Flaherty et al.
6260147 July 10, 2001 Quick, Jr.
6266614 July 24, 2001 Alumbaugh
6275692 August 14, 2001 Skog
6275849 August 14, 2001 Ludwig
6278701 August 21, 2001 Ayyagari
6289373 September 11, 2001 Dezonno
6297768 October 2, 2001 Allen, Jr.
6307504 October 23, 2001 Sheynblat
6308269 October 23, 2001 Proidl
6313786 November 6, 2001 Sheynblat et al.
6317594 November 13, 2001 Gossman et al.
6321091 November 20, 2001 Holland
6321092 November 20, 2001 Fitch
6321257 November 20, 2001 Kotola et al.
6324542 November 27, 2001 Wright, Jr. et al.
6327473 December 4, 2001 Soliman et al.
6327479 December 4, 2001 Mikkola
6330454 December 11, 2001 Verdonk
6333919 December 25, 2001 Gaffney
6360093 March 19, 2002 Ross et al.
6360102 March 19, 2002 Havinis
6363254 March 26, 2002 Jones et al.
6367019 April 2, 2002 Ansell et al.
6370389 April 9, 2002 Isomursu et al.
6377209 April 23, 2002 Krasner
6377810 April 23, 2002 Geiger et al.
6400314 June 4, 2002 Krasner
6400958 June 4, 2002 Isomursu et al.
6411254 June 25, 2002 Moeglein et al.
6421002 July 16, 2002 Krasner
6433734 August 13, 2002 Krasner
6434381 August 13, 2002 Moore et al.
6442391 August 27, 2002 Johansson et al.
6449473 September 10, 2002 Raivisto
6449476 September 10, 2002 Hutchison, IV et al.
6456852 September 24, 2002 Bar et al.
6463272 October 8, 2002 Wallace et al.
6477150 November 5, 2002 Maggenti et al.
6504491 January 7, 2003 Christians
6505049 January 7, 2003 Dorenbosch
6510387 January 21, 2003 Fuchs et al.
6512922 January 28, 2003 Burg et al.
6512930 January 28, 2003 Sandegren
6515623 February 4, 2003 Johnson
6519466 February 11, 2003 Pande et al.
6522682 February 18, 2003 Kohli et al.
6529829 March 4, 2003 Turetzky et al.
6531982 March 11, 2003 White et al.
6538757 March 25, 2003 Sansone
6539200 March 25, 2003 Schiff
6539232 March 25, 2003 Hendrey et al.
6539304 March 25, 2003 Chansarkar
6542464 April 1, 2003 Takeda et al.
6542734 April 1, 2003 Abrol et al.
6542743 April 1, 2003 Soliman
6549776 April 15, 2003 Joong
6549844 April 15, 2003 Egberts
6553236 April 22, 2003 Dunko et al.
6556832 April 29, 2003 Soliman
6560461 May 6, 2003 Fomukong et al.
6560534 May 6, 2003 Abraham et al.
6570530 May 27, 2003 Gaal et al.
6571095 May 27, 2003 Koodli
6574558 June 3, 2003 Kohli
6580390 June 17, 2003 Hay
6584552 June 24, 2003 Kuno et al.
6600927 July 29, 2003 Hamilton
6609004 August 19, 2003 Morse et al.
6611757 August 26, 2003 Brodie
6618593 September 9, 2003 Drutman et al.
6618670 September 9, 2003 Chansarkar
6621452 September 16, 2003 Knockeart et al.
6628233 September 30, 2003 Knockeart et al.
6633255 October 14, 2003 Krasner
6640184 October 28, 2003 Rabe
6650288 November 18, 2003 Pitt et al.
6661372 December 9, 2003 Girerd et al.
6665539 December 16, 2003 Sih et al.
6665541 December 16, 2003 Krasner et al.
6671620 December 30, 2003 Garin et al.
6677894 January 13, 2004 Sheynblat et al.
6680694 January 20, 2004 Knockeart et al.
6680695 January 20, 2004 Turetzky et al.
6691019 February 10, 2004 Seeley et al.
6694258 February 17, 2004 Johnson et al.
6697629 February 24, 2004 Grilli et al.
6698195 March 2, 2004 Hellinger
6701144 March 2, 2004 Kirbas et al.
6703971 March 9, 2004 Pande et al.
6703972 March 9, 2004 van Diggelen
6704651 March 9, 2004 van Diggelen
6707421 March 16, 2004 Drury et al.
6714793 March 30, 2004 Carey et al.
6718174 April 6, 2004 Vayanos
6720915 April 13, 2004 Sheynblat
6721578 April 13, 2004 Minear et al.
6721871 April 13, 2004 Piispanen et al.
6724342 April 20, 2004 Bloebaum et al.
6725159 April 20, 2004 Krasner
6728701 April 27, 2004 Stoica
6731940 May 4, 2004 Nagendran
6734821 May 11, 2004 van Diggelen
6738013 May 18, 2004 Orler et al.
6738800 May 18, 2004 Aquilon et al.
6741842 May 25, 2004 Goldberg et al.
6744856 June 1, 2004 Karnik et al.
6744858 June 1, 2004 Ryan et al.
6745038 June 1, 2004 Callaway, Jr. et al.
6747596 June 8, 2004 Orler et al.
6748195 June 8, 2004 Phillips
6751464 June 15, 2004 Burg et al.
6756938 June 29, 2004 Zhao et al.
6757544 June 29, 2004 Rangarajan et al.
6757545 June 29, 2004 Nowak et al.
6771639 August 3, 2004 Holden
6771742 August 3, 2004 McCalmont et al.
6771971 August 3, 2004 Smith
6772340 August 3, 2004 Peinado et al.
6775255 August 10, 2004 Roy
6775655 August 10, 2004 Peinado et al.
6775802 August 10, 2004 Gaal
6778136 August 17, 2004 Gronemeyer
6778885 August 17, 2004 Agashe et al.
6781963 August 24, 2004 Crockett et al.
6788249 September 7, 2004 Farmer et al.
6795699 September 21, 2004 McCraw et al.
6799049 September 28, 2004 Zellner et al.
6799050 September 28, 2004 Krasner
6801159 October 5, 2004 Swope et al.
6804524 October 12, 2004 Vandermeijden
6807534 October 19, 2004 Erickson
6810323 October 26, 2004 Bullock et al.
6813264 November 2, 2004 Vassilovski
6813560 November 2, 2004 van Diggelen et al.
6816111 November 9, 2004 Krasner
6816710 November 9, 2004 Krasner
6816719 November 9, 2004 Heinonen et al.
6816734 November 9, 2004 Wong et al.
6820269 November 16, 2004 Baucke et al.
6829475 December 7, 2004 Lee et al.
6832373 December 14, 2004 O'Neill
6839020 January 4, 2005 Geier et al.
6839021 January 4, 2005 Sheynblat et al.
6839417 January 4, 2005 Weisman et al.
6842715 January 11, 2005 Gaal
6847822 January 25, 2005 Dennison et al.
6853916 February 8, 2005 Fuchs et al.
6856282 February 15, 2005 Mauro et al.
6861980 March 1, 2005 Rowitch et al.
6865171 March 8, 2005 Nilsson
6865395 March 8, 2005 Riley
6867733 March 15, 2005 Sandhu et al.
6867734 March 15, 2005 Voor et al.
6873854 March 29, 2005 Crockett et al.
6882850 April 19, 2005 McConnell et al.
6885874 April 26, 2005 Grube et al.
6885940 April 26, 2005 Brodie et al.
6888497 May 3, 2005 King et al.
6888932 May 3, 2005 Snip et al.
6895238 May 17, 2005 Newell et al.
6895249 May 17, 2005 Gaal
6900758 May 31, 2005 Mann et al.
6903684 June 7, 2005 Simic et al.
6904029 June 7, 2005 Fors et al.
6907224 June 14, 2005 Younis
6907238 June 14, 2005 Leung
6912230 June 28, 2005 Salkini
6912395 June 28, 2005 Benes et al.
6912545 June 28, 2005 Lundy et al.
6915208 July 5, 2005 Garin et al.
6917331 July 12, 2005 Gronemeyer
6930634 August 16, 2005 Peng et al.
6937187 August 30, 2005 van Diggelen et al.
6937872 August 30, 2005 Krasner
6940950 September 6, 2005 Dickinson et al.
6941144 September 6, 2005 Stein
6944540 September 13, 2005 King et al.
6947772 September 20, 2005 Minear et al.
6950058 September 27, 2005 Davis et al.
6957073 October 18, 2005 Bye
6961562 November 1, 2005 Ross
6963557 November 8, 2005 Knox
6965754 November 15, 2005 King
6965767 November 15, 2005 Maggenti et al.
6970917 November 29, 2005 Kushwaha et al.
6973320 December 6, 2005 Brown et al.
6975266 December 13, 2005 Abraham et al.
6978453 December 20, 2005 Rao et al.
6980816 December 27, 2005 Rohles et al.
6985747 January 10, 2006 Chithambaram
6990081 January 24, 2006 Schaefer et al.
6993355 January 31, 2006 Pershan
6996720 February 7, 2006 DeMello et al.
6999782 February 14, 2006 Shaughnessy et al.
7024321 April 4, 2006 Deninger et al.
7024393 April 4, 2006 Peinado et al.
7047411 May 16, 2006 DeMello et al.
7065351 June 20, 2006 Carter et al.
7072667 July 4, 2006 Olrik
7079857 July 18, 2006 Maggenti et al.
7103018 September 5, 2006 Hansen et al.
7103574 September 5, 2006 Peinado et al.
7106717 September 12, 2006 Rousseau et al.
7110773 September 19, 2006 Wallace
7136838 November 14, 2006 Peinado et al.
7151946 December 19, 2006 Maggenti et al.
7177397 February 13, 2007 McCalmont
7177399 February 13, 2007 Dawson
7209758 April 24, 2007 Moll et al.
7209969 April 24, 2007 Lahti et al.
7218940 May 15, 2007 Niemenmaa et al.
7221959 May 22, 2007 Lindqvist et al.
7245900 July 17, 2007 Lamb
7260384 August 21, 2007 Bales et al.
7333480 February 19, 2008 Clarke
7428571 September 23, 2008 Ichimura
7440442 October 21, 2008 Grabelsky et al.
20010011247 August 2, 2001 O'Flaherty et al.
20010021646 September 13, 2001 Antonucci et al.
20020037735 March 28, 2002 Maggenti et al.
20020052214 May 2, 2002 Maggenti et al.
20020061760 May 23, 2002 Maggenti et al.
20020069529 June 13, 2002 Wieres
20020098832 July 25, 2002 Fleischer et al.
20020102996 August 1, 2002 Jenkins
20020102999 August 1, 2002 Maggenti et al.
20020111172 August 15, 2002 DeWolf et al.
20020112047 August 15, 2002 Kushwaha et al.
20020138650 September 26, 2002 Yamamoto et al.
20020173317 November 21, 2002 Nykanen
20020191595 December 19, 2002 Mar
20030009602 January 9, 2003 Jacobs et al.
20030013449 January 16, 2003 Hose et al.
20030016804 January 23, 2003 Sheha et al.
20030037163 February 20, 2003 Kitada et al.
20030040272 February 27, 2003 Lelievre et al.
20030065788 April 3, 2003 Salomaki
20030069002 April 10, 2003 Hunter et al.
20030072318 April 17, 2003 Lam et al.
20030078064 April 24, 2003 Chan
20030081557 May 1, 2003 Mettala et al.
20030101329 May 29, 2003 Lahti et al.
20030101341 May 29, 2003 Kettler, III et al.
20030103484 June 5, 2003 Oommen et al.
20030114157 June 19, 2003 Spitz et al.
20030119521 June 26, 2003 Tipnis et al.
20030119528 June 26, 2003 Pew et al.
20030137961 July 24, 2003 Tsirtsis et al.
20030153340 August 14, 2003 Crockett et al.
20030153341 August 14, 2003 Crockett et al.
20030153342 August 14, 2003 Crockett et al.
20030153343 August 14, 2003 Crockett et al.
20030161298 August 28, 2003 Bergman et al.
20030196105 October 16, 2003 Fineberg
20030204640 October 30, 2003 Sahinoja et al.
20030223381 December 4, 2003 Schroderus
20040002326 January 1, 2004 Maher
20040032485 February 19, 2004 Stephens, Jr.
20040043775 March 4, 2004 Kennedy
20040044623 March 4, 2004 Wake et al.
20040047342 March 11, 2004 Gavish
20040047461 March 11, 2004 Weisman et al.
20040068724 April 8, 2004 Gardner, III et al.
20040098497 May 20, 2004 Banet et al.
20040132465 July 8, 2004 Mattila et al.
20040150518 August 5, 2004 Phillips et al.
20040184584 September 23, 2004 McCalmont
20040185875 September 23, 2004 Diacakis et al.
20040198332 October 7, 2004 Lundsgaard
20040198386 October 7, 2004 Dupray
20040203568 October 14, 2004 Kirtland
20040205151 October 14, 2004 Sprigg et al.
20040229632 November 18, 2004 Flynn et al.
20040242238 December 2, 2004 Wang et al.
20050028034 February 3, 2005 Gantman et al.
20050030977 February 10, 2005 Casey et al.
20050039178 February 17, 2005 Marolia et al.
20050041578 February 24, 2005 Huotari et al.
20050043037 February 24, 2005 Loppe
20050086467 April 21, 2005 Asokan et al.
20050090236 April 28, 2005 Schwinke et al.
20050107673 May 19, 2005 Ball
20050112030 May 26, 2005 Gaus
20050134504 June 23, 2005 Harwood et al.
20050190746 September 1, 2005 Xiong
20050209995 September 22, 2005 Aksu et al.
20050232252 October 20, 2005 Hoover
20050259675 November 24, 2005 Tuohino et al.
20050271029 December 8, 2005 Iffland
20060008065 January 12, 2006 Longman et al.
20060023747 February 2, 2006 Koren et al.
20060053225 March 9, 2006 Poikselka et al.
20060072729 April 6, 2006 Lee et al.
20060193447 August 31, 2006 Schwartz
20060212558 September 21, 2006 Sahinoja et al.
20060212562 September 21, 2006 Kushwaha et al.
20060233338 October 19, 2006 Venkata
20060234639 October 19, 2006 Kushwaha et al.
20060234698 October 19, 2006 Fok et al.
20060258380 November 16, 2006 Liebowitz
20060259365 November 16, 2006 Agarwal et al.
20070003024 January 4, 2007 Olivier
20070014282 January 18, 2007 Mitchell
20070019614 January 25, 2007 Hoffmann
20070022011 January 25, 2007 Altberg et al.
20070026854 February 1, 2007 Nath et al.
20070030539 February 8, 2007 Nath et al.
20070049288 March 1, 2007 Lamprecht
20070115941 May 24, 2007 Patel
20070263610 November 15, 2007 Mitchell
20080214202 September 4, 2008 Toomey
Foreign Patent Documents
WO9921380 April 1999 WO
PCTUS9928848 December 1999 WO
PCTUS0146666 November 2001 WO
WO2005/051033 June 2005 WO
WO2007027166 March 2007 WO
Other references
  • Le-Pond Chin Jyh-Hong Wen Ting-Way Liu, The study of the interconnection of GSM mobile communication system over IP based network, May 6, 2001, IEEE, Vehicular Technology Conference, vol. 3, pp. 2219-2223.
  • International Search Report in PCT/US2008/01441dated May 16, 2008.
  • International Search Report in counterpart application PCT/US06/38947 dated Mar. 6, 2008.
  • Qualcomm CDMA Technologies, LBS Control Plane/User Plane Overview—80-VD378-1NP B, 2006, pp. 1-36.
  • Bhalla et al, TELUS, Technology Strategy—LBS Roaming Summit, Sep. 19, 2006.
  • Alfredo Aguirre, Ilusacell, First and Only Carrier in Mexico with a 3G CDMA Network, 2007.
  • Mike McMullen, Sprint, LBS Roaming Summit, Sep. 19, 2006.
  • Andrew Yeow, BCE, LBS Roaming Summit, Sep. 19, 2006, pp. 1-8.
  • Nars Haran, U.S. Cellular, Packet Data—Roaming and LBS Overview, Nov. 2, 2007, pp. 1-15.
  • Qualcomm CDMA Technologies, LBS Control Plane Roaming—80-VD377-1NP A, 2006, pp. 1-10.
  • Qualcomm CDMA Technologies, MS Resident User Plane LBS Roaming—80-VC718-1 E, 2006, pp. 1-37.
  • Intrado Inc., Qwest Detailed SR/ALI to MPC/GMLC Interface Specification for TCP/IP Implementation of TIA/EIA/J-STD-036 E2 with Phase I Location Description Addition, Intrado Informed Response; Apr. 2004; Issue 1.11; pp. 1-57.
  • International Search Report in PCT/US2007/23243 dated Apr. 2, 2008.
Patent History
Patent number: 7626951
Type: Grant
Filed: Aug 15, 2006
Date of Patent: Dec 1, 2009
Patent Publication Number: 20070091906
Assignee: TeleCommunication Systems, Inc. (Annapolis, MD)
Inventors: Jon Croy (Seattle, WA), John Gordon Hines (Kirkland, WA)
Primary Examiner: Jayanti K Patel
Assistant Examiner: Hooman Houshmand
Attorney: William H. Bollman
Application Number: 11/503,908
Classifications
Current U.S. Class: Technique For Setting Up A Conference Call (370/261); Bridge Or Gateway Between Networks (370/401)
International Classification: H04L 12/16 (20060101);