Voice Over Internet Protocol (VoIP) location based conferencing

Information

  • Patent Grant
  • 7626951
  • Patent Number
    7,626,951
  • Date Filed
    Tuesday, August 15, 2006
    18 years ago
  • Date Issued
    Tuesday, December 1, 2009
    14 years ago
Abstract
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.
Description
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; anda 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; andestablishing 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; andmeans 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.
Parent Case Info

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.

US Referenced Citations (530)
Number Name Date Kind
1103073 O'Connell Jul 1914 A
4445118 Taylor et al. Apr 1984 A
4494119 Wimbush Jan 1985 A
4651156 Martinez Mar 1987 A
4706275 Kamil Nov 1987 A
4891638 Davis Jan 1990 A
4891650 Sheffer Jan 1990 A
4952928 Carroll et al. Aug 1990 A
4972484 Theile et al. Nov 1990 A
5014206 Scribner et al. May 1991 A
5043736 Darnell et al. Aug 1991 A
5055851 Sheffer Oct 1991 A
5068656 Sutherland Nov 1991 A
5068891 Marshall Nov 1991 A
5070329 Jasinaki Dec 1991 A
5081667 Drori et al. Jan 1992 A
5119104 Heller Jun 1992 A
5126722 Kamis Jun 1992 A
5144283 Arens et al. Sep 1992 A
5161180 Chavous Nov 1992 A
5166972 Smith Nov 1992 A
5177478 Wagai et al. Jan 1993 A
5193215 Olmer Mar 1993 A
5208756 Song May 1993 A
5214789 George May 1993 A
5218367 Sheffer et al. Jun 1993 A
5223844 Mansell et al. Jun 1993 A
5239570 Koster et al. Aug 1993 A
5265630 Hartman et al. Nov 1993 A
5266944 Carroll et al. Nov 1993 A
5283570 DeLuca et al. Feb 1994 A
5289527 Tiedemann, Jr. Feb 1994 A
5293642 Lo Mar 1994 A
5299132 Wortham Mar 1994 A
5301354 Schwendeman et al. Apr 1994 A
5311516 Kuznicki et al. May 1994 A
5325302 Izidon et al. Jun 1994 A
5327529 Fults et al. Jul 1994 A
5334974 Simms et al. Aug 1994 A
5335246 Yokev et al. Aug 1994 A
5343493 Karimullah Aug 1994 A
5347568 Moody et al. Sep 1994 A
5351235 Lahtinen Sep 1994 A
5361212 Class et al. Nov 1994 A
5363425 Mufti et al. Nov 1994 A
5365451 Wang et al. Nov 1994 A
5374936 Feng Dec 1994 A
5379451 Nakagoshi et al. Jan 1995 A
5381338 Wysocki et al. Jan 1995 A
5387993 Heller et al. Feb 1995 A
5388147 Grimes Feb 1995 A
5390339 Bruckert et al. Feb 1995 A
5394158 Chia Feb 1995 A
5396227 Carroll et al. Mar 1995 A
5398190 Wortham Mar 1995 A
5406614 Hara Apr 1995 A
5418537 Bird May 1995 A
5422813 Schuchman et al. Jun 1995 A
5423076 Westergren et al. Jun 1995 A
5432841 Rimer Jul 1995 A
5434789 Fraker et al. Jul 1995 A
5454024 Lebowitz Sep 1995 A
5461390 Hoshen Oct 1995 A
5470233 Fruchterman et al. Nov 1995 A
5479408 Will Dec 1995 A
5479482 Grimes Dec 1995 A
5485161 Vaughn Jan 1996 A
5485163 Singer et al. Jan 1996 A
5488563 Chazelle et al. Jan 1996 A
5494091 Freeman et al. Feb 1996 A
5497149 Fast Mar 1996 A
5504491 Chapman Apr 1996 A
5506886 Maine et al. Apr 1996 A
5508931 Snider Apr 1996 A
5513243 Kage Apr 1996 A
5515287 Hakoyama et al. May 1996 A
5517199 DiMattei May 1996 A
5519403 Bickley et al. May 1996 A
5530655 Lokhoff et al. Jun 1996 A
5530914 McPheters Jun 1996 A
5532690 Hertel Jul 1996 A
5535434 Siddoway et al. Jul 1996 A
5539395 Buss et al. Jul 1996 A
5539398 Hall et al. Jul 1996 A
5539829 Lokhoff et al. Jul 1996 A
5543776 L'Esperance et al. Aug 1996 A
5546445 Dennison et al. Aug 1996 A
5552772 Janky et al. Sep 1996 A
5555286 Tendler Sep 1996 A
5568119 Schipper et al. Oct 1996 A
5568153 Beliveau Oct 1996 A
5574648 Pilley Nov 1996 A
5579372 ÅStröm Nov 1996 A
5588009 Will Dec 1996 A
5592535 Klotz Jan 1997 A
5594780 Wiedeman et al. Jan 1997 A
5604486 Lauro et al. Feb 1997 A
5606313 Allen et al. Feb 1997 A
5606618 Lokhoff et al. Feb 1997 A
5606850 Nakamura Mar 1997 A
5610815 Gudat et al. Mar 1997 A
5614890 Fox Mar 1997 A
5615116 Gudat et al. Mar 1997 A
5621793 Bednarek et al. Apr 1997 A
5628051 Salin May 1997 A
5629693 Janky May 1997 A
5633912 Tsoi May 1997 A
5636276 Brugger Jun 1997 A
5661652 Sprague et al. Aug 1997 A
5661755 Van De Kerkhof et al. Aug 1997 A
5682600 Salin Oct 1997 A
5689245 Noreen et al. Nov 1997 A
5699053 Jonsson Dec 1997 A
5704029 Wright, Jr. Dec 1997 A
5721781 Deo et al. Feb 1998 A
5731785 Lemelson et al. Mar 1998 A
5740534 Ayerst et al. Apr 1998 A
5761618 Lynch et al. Jun 1998 A
5765152 Erickson Jun 1998 A
5767795 Schaphorst Jun 1998 A
5768509 Gunluk Jun 1998 A
5771353 Eggleston et al. Jun 1998 A
5774533 Patel Jun 1998 A
5774670 Montulli Jun 1998 A
5787357 Salin Jul 1998 A
5794142 Vanttila et al. Aug 1998 A
5797094 Houde et al. Aug 1998 A
5797096 Lupien et al. Aug 1998 A
5802492 DeLorme et al. Sep 1998 A
5806000 Vo et al. Sep 1998 A
5809415 Rossmann Sep 1998 A
5812086 Bertiger et al. Sep 1998 A
5812087 Krasner Sep 1998 A
5822700 Hult et al. Oct 1998 A
5828740 Khuc et al. Oct 1998 A
5835907 Newman Nov 1998 A
5841396 Krasner Nov 1998 A
5857201 Wright, Jr. et al. Jan 1999 A
5864667 Barkan Jan 1999 A
5874914 Krasner Feb 1999 A
5896369 Warsta et al. Apr 1999 A
5920821 Seazholtz et al. Jul 1999 A
5922074 Richard et al. Jul 1999 A
5930250 Klok et al. Jul 1999 A
5930701 Skog Jul 1999 A
5943399 Bannister et al. Aug 1999 A
5945944 Krasner Aug 1999 A
5946629 Sawyer et al. Aug 1999 A
5946630 Willars et al. Aug 1999 A
5950130 Coursey Sep 1999 A
5950137 Kim Sep 1999 A
5953398 Hill Sep 1999 A
5960362 Grob et al. Sep 1999 A
5974054 Couts et al. Oct 1999 A
5978685 Laiho Nov 1999 A
5983099 Yao et al. Nov 1999 A
5987323 Huotari Nov 1999 A
5998111 Abe Dec 1999 A
5999124 Sheynblat Dec 1999 A
6014602 Kithil et al. Jan 2000 A
6032051 Hall Feb 2000 A
6035025 Hanson Mar 2000 A
6049710 Nilsson Apr 2000 A
6052081 Krasner Apr 2000 A
6058300 Hanson May 2000 A
6058338 Agashe et al. May 2000 A
6061018 Sheynblat May 2000 A
6061346 Nordman May 2000 A
6064336 Krasner May 2000 A
6064875 Morgan May 2000 A
6067045 Castelloe et al. May 2000 A
6070067 Nguyen et al. May 2000 A
6075982 Donovan et al. Jun 2000 A
6081229 Soliman et al. Jun 2000 A
6081508 West et al. Jun 2000 A
6085320 Kaliski, Jr. Jul 2000 A
6101378 Barabash et al. Aug 2000 A
6104931 Havinis et al. Aug 2000 A
6122503 Daly Sep 2000 A
6122520 Want et al. Sep 2000 A
6124810 Segal et al. Sep 2000 A
6131067 Girerd et al. Oct 2000 A
6133874 Krasner Oct 2000 A
6134483 Vayanos et al. Oct 2000 A
6138003 Kingdon et al. Oct 2000 A
6148197 Bridges et al. Nov 2000 A
6148198 Anderson et al. Nov 2000 A
6149353 Nilsson Nov 2000 A
6150980 Krasner Nov 2000 A
6154172 Piccionelli et al. Nov 2000 A
6169891 Gorham et al. Jan 2001 B1
6169901 Boucher Jan 2001 B1
6169902 Kawamoto Jan 2001 B1
6173181 Losh Jan 2001 B1
6178505 Schneider et al. Jan 2001 B1
6178506 Quick, Jr. Jan 2001 B1
6181935 Gossman et al. Jan 2001 B1
6185427 Krasner et al. Feb 2001 B1
6188354 Soliman et al. Feb 2001 B1
6188752 Lesley Feb 2001 B1
6188909 Alanara et al. Feb 2001 B1
6189098 Kaliski, Jr. Feb 2001 B1
6195557 Havinis et al. Feb 2001 B1
6198431 Gibson Mar 2001 B1
6199045 Giniger et al. Mar 2001 B1
6199113 Alegre et al. Mar 2001 B1
6205330 Winbladh Mar 2001 B1
6208290 Krasner Mar 2001 B1
6208854 Roberts et al. Mar 2001 B1
6215441 Moeglein et al. Apr 2001 B1
6219557 Havinis Apr 2001 B1
6223046 Hamill-Keays et al. Apr 2001 B1
6226529 Bruno et al. May 2001 B1
6239742 Krasner May 2001 B1
6247135 Feague Jun 2001 B1
6249680 Wax et al. Jun 2001 B1
6249744 Morita Jun 2001 B1
6249873 Richard et al. Jun 2001 B1
6253203 O'Flaherty et al. Jun 2001 B1
6260147 Quick, Jr. Jul 2001 B1
6266614 Alumbaugh Jul 2001 B1
6275692 Skog Aug 2001 B1
6275849 Ludwig Aug 2001 B1
6278701 Ayyagari Aug 2001 B1
6289373 Dezonno Sep 2001 B1
6297768 Allen, Jr. Oct 2001 B1
6307504 Sheynblat Oct 2001 B1
6308269 Proidl Oct 2001 B2
6313786 Sheynblat et al. Nov 2001 B1
6317594 Gossman et al. Nov 2001 B1
6321091 Holland Nov 2001 B1
6321092 Fitch Nov 2001 B1
6321257 Kotola et al. Nov 2001 B1
6324542 Wright, Jr. et al. Nov 2001 B1
6327473 Soliman et al. Dec 2001 B1
6327479 Mikkola Dec 2001 B1
6330454 Verdonk Dec 2001 B1
6333919 Gaffney Dec 2001 B2
6360093 Ross et al. Mar 2002 B1
6360102 Havinis Mar 2002 B1
6363254 Jones et al. Mar 2002 B1
6367019 Ansell et al. Apr 2002 B1
6370389 Isomursu et al. Apr 2002 B1
6377209 Krasner Apr 2002 B1
6377810 Geiger et al. Apr 2002 B1
6400314 Krasner Jun 2002 B1
6400958 Isomursu et al. Jun 2002 B1
6411254 Moeglein et al. Jun 2002 B1
6421002 Krasner Jul 2002 B2
6433734 Krasner Aug 2002 B1
6434381 Moore et al. Aug 2002 B1
6442391 Johansson et al. Aug 2002 B1
6449473 Raivisto Sep 2002 B1
6449476 Hutchison, IV et al. Sep 2002 B1
6456852 Bar et al. Sep 2002 B2
6463272 Wallace et al. Oct 2002 B1
6477150 Maggenti et al. Nov 2002 B1
6504491 Christians Jan 2003 B1
6505049 Dorenbosch Jan 2003 B1
6510387 Fuchs et al. Jan 2003 B2
6512922 Burg et al. Jan 2003 B1
6512930 Sandegren Jan 2003 B2
6515623 Johnson Feb 2003 B2
6519466 Pande et al. Feb 2003 B2
6522682 Kohli et al. Feb 2003 B1
6529829 Turetzky et al. Mar 2003 B2
6531982 White et al. Mar 2003 B1
6538757 Sansone Mar 2003 B1
6539200 Schiff Mar 2003 B1
6539232 Hendrey et al. Mar 2003 B2
6539304 Chansarkar Mar 2003 B1
6542464 Takeda et al. Apr 2003 B1
6542734 Abrol et al. Apr 2003 B1
6542743 Soliman Apr 2003 B1
6549776 Joong Apr 2003 B1
6549844 Egberts Apr 2003 B1
6553236 Dunko et al. Apr 2003 B1
6556832 Soliman Apr 2003 B1
6560461 Fomukong et al. May 2003 B1
6560534 Abraham et al. May 2003 B2
6570530 Gaal et al. May 2003 B2
6571095 Koodli May 2003 B1
6574558 Kohli Jun 2003 B2
6580390 Hay Jun 2003 B1
6584552 Kuno et al. Jun 2003 B1
6600927 Hamilton Jul 2003 B2
6609004 Morse et al. Aug 2003 B1
6611757 Brodie Aug 2003 B2
6618593 Drutman et al. Sep 2003 B1
6618670 Chansarkar Sep 2003 B1
6621452 Knockeart et al. Sep 2003 B2
6628233 Knockeart et al. Sep 2003 B2
6633255 Krasner Oct 2003 B2
6640184 Rabe Oct 2003 B1
6650288 Pitt et al. Nov 2003 B1
6661372 Girerd et al. Dec 2003 B1
6665539 Sih et al. Dec 2003 B2
6665541 Krasner et al. Dec 2003 B1
6671620 Garin et al. Dec 2003 B1
6677894 Sheynblat et al. Jan 2004 B2
6680694 Knockeart et al. Jan 2004 B1
6680695 Turetzky et al. Jan 2004 B2
6691019 Seeley et al. Feb 2004 B2
6694258 Johnson et al. Feb 2004 B2
6697629 Grilli et al. Feb 2004 B1
6698195 Hellinger Mar 2004 B1
6701144 Kirbas et al. Mar 2004 B2
6703971 Pande et al. Mar 2004 B2
6703972 van Diggelen Mar 2004 B2
6704651 van Diggelen Mar 2004 B2
6707421 Drury et al. Mar 2004 B1
6714793 Carey et al. Mar 2004 B1
6718174 Vayanos Apr 2004 B2
6720915 Sheynblat Apr 2004 B2
6721578 Minear et al. Apr 2004 B2
6721871 Piispanen et al. Apr 2004 B2
6724342 Bloebaum et al. Apr 2004 B2
6725159 Krasner Apr 2004 B2
6728701 Stoica Apr 2004 B1
6731940 Nagendran May 2004 B1
6734821 van Diggelen May 2004 B2
6738013 Orler et al. May 2004 B2
6738800 Aquilon et al. May 2004 B1
6741842 Goldberg et al. May 2004 B2
6744856 Karnik et al. Jun 2004 B2
6744858 Ryan et al. Jun 2004 B1
6745038 Callaway, Jr. et al. Jun 2004 B2
6747596 Orler et al. Jun 2004 B2
6748195 Phillips Jun 2004 B1
6751464 Burg et al. Jun 2004 B1
6756938 Zhao et al. Jun 2004 B2
6757544 Rangarajan et al. Jun 2004 B2
6757545 Nowak et al. Jun 2004 B2
6771639 Holden Aug 2004 B1
6771742 McCalmont et al. Aug 2004 B2
6771971 Smith Aug 2004 B2
6772340 Peinado et al. Aug 2004 B1
6775255 Roy Aug 2004 B1
6775655 Peinado et al. Aug 2004 B1
6775802 Gaal Aug 2004 B2
6778136 Gronemeyer Aug 2004 B2
6778885 Agashe et al. Aug 2004 B2
6781963 Crockett et al. Aug 2004 B2
6788249 Farmer et al. Sep 2004 B1
6795699 McCraw et al. Sep 2004 B1
6799049 Zellner et al. Sep 2004 B1
6799050 Krasner Sep 2004 B1
6801159 Swope et al. Oct 2004 B2
6804524 Vandermeijden Oct 2004 B1
6807534 Erickson Oct 2004 B1
6810323 Bullock et al. Oct 2004 B1
6813264 Vassilovski Nov 2004 B2
6813560 van Diggelen et al. Nov 2004 B2
6816111 Krasner Nov 2004 B2
6816710 Krasner Nov 2004 B2
6816719 Heinonen et al. Nov 2004 B1
6816734 Wong et al. Nov 2004 B2
6820269 Baucke et al. Nov 2004 B2
6829475 Lee et al. Dec 2004 B1
6832373 O'Neill Dec 2004 B2
6839020 Geier et al. Jan 2005 B2
6839021 Sheynblat et al. Jan 2005 B2
6839417 Weisman et al. Jan 2005 B2
6842715 Gaal Jan 2005 B1
6847822 Dennison et al. Jan 2005 B1
6853916 Fuchs et al. Feb 2005 B2
6856282 Mauro et al. Feb 2005 B2
6861980 Rowitch et al. Mar 2005 B1
6865171 Nilsson Mar 2005 B1
6865395 Riley Mar 2005 B2
6867733 Sandhu et al. Mar 2005 B2
6867734 Voor et al. Mar 2005 B2
6873854 Crockett et al. Mar 2005 B2
6882850 McConnell et al. Apr 2005 B2
6885874 Grube et al. Apr 2005 B2
6885940 Brodie et al. Apr 2005 B2
6888497 King et al. May 2005 B2
6888932 Snip et al. May 2005 B2
6895238 Newell et al. May 2005 B2
6895249 Gaal May 2005 B2
6900758 Mann et al. May 2005 B1
6903684 Simic et al. Jun 2005 B1
6904029 Fors et al. Jun 2005 B2
6907224 Younis Jun 2005 B2
6907238 Leung Jun 2005 B2
6912230 Salkini Jun 2005 B1
6912395 Benes et al. Jun 2005 B2
6912545 Lundy et al. Jun 2005 B1
6915208 Garin et al. Jul 2005 B2
6917331 Gronemeyer Jul 2005 B2
6930634 Peng et al. Aug 2005 B2
6937187 van Diggelen et al. Aug 2005 B2
6937872 Krasner Aug 2005 B2
6940950 Dickinson et al. Sep 2005 B2
6941144 Stein Sep 2005 B2
6944540 King et al. Sep 2005 B2
6947772 Minear et al. Sep 2005 B2
6950058 Davis et al. Sep 2005 B1
6957073 Bye Oct 2005 B2
6961562 Ross Nov 2005 B2
6963557 Knox Nov 2005 B2
6965754 King Nov 2005 B2
6965767 Maggenti et al. Nov 2005 B2
6970917 Kushwaha et al. Nov 2005 B1
6973320 Brown et al. Dec 2005 B2
6975266 Abraham et al. Dec 2005 B2
6978453 Rao et al. Dec 2005 B2
6980816 Rohles et al. Dec 2005 B2
6985747 Chithambaram Jan 2006 B2
6990081 Schaefer et al. Jan 2006 B2
6993355 Pershan Jan 2006 B1
6996720 DeMello et al. Feb 2006 B1
6999782 Shaughnessy et al. Feb 2006 B2
7024321 Deninger et al. Apr 2006 B1
7024393 Peinado et al. Apr 2006 B1
7047411 DeMello et al. May 2006 B1
7065351 Carter et al. Jun 2006 B2
7072667 Olrik Jul 2006 B2
7079857 Maggenti et al. Jul 2006 B2
7103018 Hansen et al. Sep 2006 B1
7103574 Peinado et al. Sep 2006 B1
7106717 Rousseau et al. Sep 2006 B2
7110773 Wallace Sep 2006 B1
7136838 Peinado et al. Nov 2006 B1
7151946 Maggenti et al. Dec 2006 B2
7177397 McCalmont Feb 2007 B2
7177399 Dawson Feb 2007 B2
7209758 Moll et al. Apr 2007 B1
7209969 Lahti et al. Apr 2007 B2
7218940 Niemenmaa et al. May 2007 B2
7221959 Lindqvist et al. May 2007 B2
7245900 Lamb Jul 2007 B1
7260384 Bales et al. Aug 2007 B2
7333480 Clarke Feb 2008 B1
7428571 Ichimura Sep 2008 B2
7440442 Grabelsky et al. Oct 2008 B2
20010011247 O'Flaherty et al. Aug 2001 A1
20010021646 Antonucci et al. Sep 2001 A1
20020037735 Maggenti et al. Mar 2002 A1
20020052214 Maggenti et al. May 2002 A1
20020061760 Maggenti et al. May 2002 A1
20020069529 Wieres Jun 2002 A1
20020098832 Fleischer et al. Jul 2002 A1
20020102996 Jenkins Aug 2002 A1
20020102999 Maggenti et al. Aug 2002 A1
20020111172 DeWolf et al. Aug 2002 A1
20020112047 Kushwaha et al. Aug 2002 A1
20020138650 Yamamoto et al. Sep 2002 A1
20020173317 Nykanen Nov 2002 A1
20020191595 Mar Dec 2002 A1
20030009602 Jacobs et al. Jan 2003 A1
20030013449 Hose et al. Jan 2003 A1
20030016804 Sheha et al. Jan 2003 A1
20030037163 Kitada et al. Feb 2003 A1
20030040272 Lelievre et al. Feb 2003 A1
20030065788 Salomaki Apr 2003 A1
20030069002 Hunter et al. Apr 2003 A1
20030072318 Lam et al. Apr 2003 A1
20030078064 Chan Apr 2003 A1
20030081557 Mettala et al. May 2003 A1
20030101329 Lahti et al. May 2003 A1
20030101341 Kettler, III et al. May 2003 A1
20030103484 Oommen et al. Jun 2003 A1
20030114157 Spitz et al. Jun 2003 A1
20030119521 Tipnis et al. Jun 2003 A1
20030119528 Pew et al. Jun 2003 A1
20030137961 Tsirtsis et al. Jul 2003 A1
20030153340 Crockett et al. Aug 2003 A1
20030153341 Crockett et al. Aug 2003 A1
20030153342 Crockett et al. Aug 2003 A1
20030153343 Crockett et al. Aug 2003 A1
20030161298 Bergman et al. Aug 2003 A1
20030196105 Fineberg Oct 2003 A1
20030204640 Sahinoja et al. Oct 2003 A1
20030223381 Schroderus Dec 2003 A1
20040002326 Maher Jan 2004 A1
20040032485 Stephens, Jr. Feb 2004 A1
20040043775 Kennedy Mar 2004 A1
20040044623 Wake et al. Mar 2004 A1
20040047342 Gavish Mar 2004 A1
20040047461 Weisman et al. Mar 2004 A1
20040068724 Gardner, III et al. Apr 2004 A1
20040098497 Banet et al. May 2004 A1
20040132465 Mattila et al. Jul 2004 A1
20040150518 Phillips et al. Aug 2004 A1
20040184584 McCalmont Sep 2004 A1
20040185875 Diacakis et al. Sep 2004 A1
20040198332 Lundsgaard Oct 2004 A1
20040198386 Dupray Oct 2004 A1
20040203568 Kirtland Oct 2004 A1
20040205151 Sprigg et al. Oct 2004 A1
20040229632 Flynn et al. Nov 2004 A1
20040242238 Wang et al. Dec 2004 A1
20050028034 Gantman et al. Feb 2005 A1
20050030977 Casey et al. Feb 2005 A1
20050039178 Marolia et al. Feb 2005 A1
20050041578 Huotari et al. Feb 2005 A1
20050043037 Loppe Feb 2005 A1
20050086467 Asokan et al. Apr 2005 A1
20050090236 Schwinke et al. Apr 2005 A1
20050107673 Ball May 2005 A1
20050112030 Gaus May 2005 A1
20050134504 Harwood et al. Jun 2005 A1
20050190746 Xiong Sep 2005 A1
20050209995 Aksu et al. Sep 2005 A1
20050232252 Hoover Oct 2005 A1
20050259675 Tuohino et al. Nov 2005 A1
20050271029 Iffland Dec 2005 A1
20060008065 Longman et al. Jan 2006 A1
20060023747 Koren et al. Feb 2006 A1
20060053225 Poikselka et al. Mar 2006 A1
20060072729 Lee et al. Apr 2006 A1
20060193447 Schwartz Aug 2006 A1
20060212558 Sahinoja et al. Sep 2006 A1
20060212562 Kushwaha et al. Sep 2006 A1
20060233338 Venkata Oct 2006 A1
20060234639 Kushwaha et al. Oct 2006 A1
20060234698 Fok et al. Oct 2006 A1
20060258380 Liebowitz Nov 2006 A1
20060259365 Agarwal et al. Nov 2006 A1
20070003024 Olivier Jan 2007 A1
20070014282 Mitchell Jan 2007 A1
20070019614 Hoffmann Jan 2007 A1
20070022011 Altberg et al. Jan 2007 A1
20070026854 Nath et al. Feb 2007 A1
20070030539 Nath et al. Feb 2007 A1
20070049288 Lamprecht Mar 2007 A1
20070115941 Patel May 2007 A1
20070263610 Mitchell Nov 2007 A1
20080214202 Toomey Sep 2008 A1
Foreign Referenced Citations (5)
Number Date Country
WO9921380 Apr 1999 WO
PCTUS9928848 Dec 1999 WO
PCTUS0146666 Nov 2001 WO
WO2005051033 Jun 2005 WO
WO2007027166 Mar 2007 WO
Related Publications (1)
Number Date Country
20070091906 A1 Apr 2007 US
Provisional Applications (3)
Number Date Country
60733789 Nov 2005 US
60723961 Oct 2005 US
60723960 Oct 2005 US