The present disclosure is generally related to a communications network, and more particularly to a system, method, and computer readable medium for providing audio announcement of communications to a called party on the communications network.
Automatic Number Identification (ANI) is a system utilized by telephone companies to identify the Directory Number (DN) of a calling subscriber. ANI serves a function similar to Caller ID, but may utilize different underlying technology. It is possible that the Caller ID can be blocked by prefixing a call with *67. ANI was originally developed for telephone company billing purposes and is now offered to commercial customers who may benefit from knowing who is calling them. In addition, ANI is one of the core technologies behind the 911 emergency services.
In commercial applications, a user may have an integrated or extraneous display affixed to a telephone. Such a display presents the ANI or telephone number of the calling party. In addition, the display may present the caller's name or calling name, also known as CNAM. Similarly, in case of a Short Messaging Service (SMS), the display may present a sender's name. However, the user may prefer to hear the audio of the information rather then watching the display. As such, a need exists for providing audio announcement along with other information to the user.
The present disclosure describes a system, method, and computer-readable medium for providing audio announcement of communications to a called party in a communication network. The method includes receiving communication from a calling party and performing a lookup of information relating to the calling party in a database via an Internet Protocol connection based on an identifier of at least one of the calling party and the called party. The information comprises one or more audio files. The method then provides the audio announcement to a called party based on the audio files.
The system for providing audio announcement of communication to a called party in a communication network comprises at least one device for receiving communication from a calling party. The system comprising at least one database for storing information associated with the calling party. The at least one device is operable to perform a lookup of information relating to the calling party in a database via an Internet Protocol connection based on an identifier of at least one of the calling party and the called party, wherein the information comprises one or more audio files, and provide an audio announcement to a called party based on the audio files.
A computer-readable medium comprising instructions executable by a device for providing audio announcement of communications to a called party in a communication network. The computer-readable medium comprising instructions for receiving communication from a calling party; performing a lookup of information relating to the calling party in a database via an Internet Protocol connection based on an identifier of at least one of the calling party and the called party, wherein the information comprises one or more audio files; and providing an audio announcement to a called party based on the audio files.
The present disclosure provides audio announcement of communications to a called party. In the context of the present disclosure, a calling party is a party initiating or sending a call or a message. A called party is a party receiving the call or the message. Such a process is initiated when a calling party contacts or communicates a called party wherein the calling party and the called party each use at least one electronic device and the called party is able to receive ANI or Caller ID service and is able to display/play related information to such service. The message comprises a text message or a multimedia message. The at least one electronic device is at least one of a computer, a audio file database, a wireless phone, an Internet Protocol (IP) enabled phone, a wireless IP-enabled phone, or a device that can receive and/or transmit information. The computer readable medium (or software) of the present disclosure is stored on and/or runs on at least one of the above-mentioned electronic devices.
In addition, device 102 may receive information from a plurality of sources including but not limited to a communications network 110 such as a public switched telephone network (PSTN), a code division multiple access (CDMA), a global system for mobile communication (GSM). For example, a public switched telephone network (PSTN) that includes a central office 112 that is coupled to a calling party device 114. The information may be received through at least a RJ11 (telephone wire) communication address 106 of device 102. Other sources include a wireless network or data network (not shown) supporting other devices such as a computer or IP enabled phones.
Aspects of the present disclosure provide information to the called parties, such as the called party device 104, by providing an ability to retrieve information of a calling party from a CNAM database 116 and/or an other database 118. The CNAM database 116 and the other database 118 comprise information relating to the calling party, for example, calling party name, telephone number, messages, location, and other information associated with the calling party. In addition, the information relating to the calling party may be a city, a state, an address, a hyperlink, a photo, a video, and any information that can be sent via an Internet Protocol (IP) connection. The device 102 communicates with the CNAM database 116 and/or the other database 118 via an IP connection. The CNAM database 116 and the other database 118 comprise information relating to the calling party, for example, calling party name, telephone number, messages, location, and other information associated with the calling party. In addition, the information relating to the calling party may be a city, a state, an address, a hyperlink, a photo, a video, an announcement, a short film, one or more audio files and any information that can be sent via an Internet Protocol (IP) connection.
When a calling party communicates by calling or sending a message using the calling party device 114, the device 102 receives a caller ID, Automatic Number Identification (ANI) or other identifier from the calling party. An example of the identifier may include an IP address of the calling party device 114 or a unique identifier of the calling party that can be received and transmitted by the calling party device 114. The identifier may include information related to at least one of a calling party and a called party.
In response to receiving the caller ID, ANI or other identifier, the device 102 sends a query for the calling party name to the CNAM database 116 and/or the other database 118. The query may be sent via at least one communication address such as 106, 120, and 130 (the communication address may include but not limited to a wired communication and/or a wireless communication such as a cellular device, a Wi-Fi connection, a PDA, a Bluetooth connection, or the like) of the device 102 to the CNAM database 116 and/or the other database 118 via a direct connection or via a data network (not shown). Once the query is received, a lookup is performed in the CNAM database 116 and/or the other database 118 for the calling party name and other information. If the calling party name is found, the CNAM database 116 and/or the other database 118 returns the calling party name and other information associated with the calling party to the device 102. Thereafter, the device 102 may store the information associated with the calling party in cache 131. In an embodiment, the cache 131 may be implemented as a local storage on the device 102. Further, the information may be stored based on configurable parameters such as, but not limited to, a number of audio files, a time duration, size and so forth. Moreover, the cache 131 may not include any duplicate information or records. For example, the information may be maintained for a total of 100 non-duplicate audio files for names of calling parties. In an embodiment of the invention, the size of the cache 131 may be limited to a predefined limit. For example, the predefined limit may be 200 KB. Further, the cache 131 may be maintained on a rolling basis. For example, after the size of the cache 131 reaches the predefined limit, and when new information is received, then a previous or the earliest information in the cache 131 may be deleted.
The device 102 can maintain the cache 131 by adding, deleting or modifying information corresponding to a calling party or a called party. For example, the device 102 may delete audio files after a predefined number of days. Alternatively, the device 102 may allow a calling party or called party to modify or delete a file or clear data stored on the cache 131. Also, the device 102 ensures the integrity of the data stored in the cache 131. To maintain integrity, the device 102 may generate a key on the fly using attributes of the calling party/called party and encrypt the information including audio response with the key. Alternatively, the device 102 may include software that detects and prevents malicious attack and ensure data safety.
Therefore, when a new communication such as a call or a message is received, the device 102 checks the cache 131 to determine whether the calling party information is located in the cache 131. If the information is present in the cache 131, then the device 102 verifies the status of an indicator for audio announcement. The indicator can be set by a called party or configured by the device 102 to an active or an inactive state. In case the status of the indicator is active, for example, then the device 102 looks up for audio file included in information on the cache 131. Subsequently, audio announcement is played based on the audio file. For example, at least the name of the calling party may be announced as the audio. Otherwise, in case the indicator is inactive then the device 102 looks up for the information excluding the audio file in the cache 131. Thereafter, the information is displayed on the display 108 of the device 102.
In one embodiment of the invention, if the information is not available in the cache 131, then the device 102 verifies the status of an indicator. Thereafter, if the status of the indicator is active, then the device 102 sends a query, for example, with the calling party number or other identifier to the CNAM database 116 and/or the other database 118 for lookup of information including the audio file. The CNAM database 116 and/or the other database 118 return calling party information to the device 102 if the calling party name/number and corresponding audio file is found in the respective database. Thereafter, the audio announcement is played based on the audio file. In an embodiment of the invention, the audio file is streamed to the device 102 for playing the audio announcement. For example, the audio announcement may be played when the audio file is being downloaded and/or stored on the device 102. In another embodiment of the invention, the audio file is downloaded and stored in the cache 131. Therefore, the device 102 may not be required to connect to the CNAM database 116 and/or the other database 118 when the information is available in the cache 131. However, if the status of the indicator is set as inactive, then the device 102 looks up for the information excluding the audio file in the CNAM database 116 and/or the other database 118. Thereafter, the information is displayed on the display 108 of the device 102.
The device 102 may provide a playback preference to the called party for selecting a module for playback of the audio announcement. The modules include for example, but not limited to, a headset, a speaker or a Bluetooth device, such as an external device capable of playing audio through Bluetooth pairing. The device 102 captures the playback preference of a module for the called party. For example, the playback preference option may include language control/selection option from the service provider site 408 but the language control/selection option may further include the central office 112, the device 102, the calling party, and the called party. In another embodiment of the invention, the CNAM request can also include the language indicator to let the service provider site 408 and/or the central office 112 informs the spoken language to generate the audio file. Further, the device 102 may have a default module in case a module as selected by the user is not available. For example, the default module may be the speaker 109 of the device 102. Thereafter, the audio announcement may be played through the module. However, in case the selected module is not available then the default module may be selected for playback. For example, the called party device 104 may enable the audio response to be played over “Bluetooth” and over the ringer speaker with a ringer interrupt. Alternatively, the called party device 104 may enable the textual name to be displayed over “Bluetooth” to external displays such as in automobiles.
In addition to displaying/playing the information and audio response, device 102 may send the information to other user devices, such as called party devices 104, 122, and 126, to be contemporaneously displayed on displays 109, 124, and 128 respectively and played on their speakers 111, 123 and 129 respectively. In an embodiment, while the audio announcement is played, the audio announcement may refer to links that are displayed on the display 108. Further, the links displayed may be clickable. For this, a URL may be embedded with the information displayed on the display 108. Further, when the called party clicks the URL, a browser is launched with relevant information of the called party.
In this example, displays 109, 124, and 128 are implemented as standalone devices. In other embodiments, the displays 109, 124, and 128 or speakers 111, 123 and 129 can be communicably coupled to called party devices 104, 122, and 126 or may be integrated with called party devices 104, 122 and 126 without departing from the spirit and scope of the present disclosure. For example, display 128 may be integrated as part of the called party device 126 and the device 102 may send information directly to the called party device 126 to be displayed on display 128. The information may be sent from at least one communication address such as 106, 120, 130 of the device 102 or via wireless connection 130.
The information/audio response received at the device 102 may include number(s) that indicates the sender's phone number, as well as the sender's name, city, and/or state. In addition, the information/audio response includes for example alerts in response to an occurrence of an event, informative and promotional information from a service provider, and situational information from an emergency service provider. Furthermore, the information/audio response may include information relating to the calling party, such as an address, a hyperlink, a photo, a video, and any information that can be sent via an Internet Protocol connection.
Referring to
At step 212, a lookup is performed in the cache 131 of the device 102 for the audio files corresponding to the identifier. Thereafter, at step 214 if the audio file is available in the cache 131 then the audio announcement is played at step 216. Otherwise, if the information or the audio files is not available, then the process 200 continues to step 218. At step 218, a lookup is performed in the CNAM database 116 and/or the other database 118. Subsequently, at step 220, the information is downloaded and stored in the cache 131. Further, the audio announcement is played based on the audio file at step 216. In an embodiment of the invention, the audio announcement is streamed or played while being downloaded. As a result, the waiting time for the download and then playing the file is reduced. In another embodiment of the invention, the audio file is downloaded on the device 102 and then the announcement is played.
As discussed above, if the audio indicator status is not set to active, then the lookup is performed in the cache 131 for information excluding the audio file. For example, the lookup may be performed for text data such as name of the called party, but excluding the audio file. The process 200 then continues to step 208, where it is determined whether the information is available in the cache 131. In case, the information is available then the information is displayed on the device 102 at step 210. Otherwise, the process continues to step 222, where the information is looked up excluding the audio file. Subsequently, the information is displayed at step 210. In an embodiment of the invention, the information displayed at step 210 is clickable. For example, the text displayed from the information can be clicked to open a browser for additional information.
Referring to
In case, the selected module is available, then the audio announcement is played through the selected module at step 306. Otherwise, if the selected module is not available, then a default module is selected at step 308. For example, a default module may be the speaker of the device 102. Subsequently, the audio announcement is played through the default module at step 310.
Referring to
In one embodiment of the present disclosure, a calling party device 114 connects to a receiving party device such as a mobile phone 402, a smart phone 404, or a PDA 406. At least one of the receiving party devices includes software to obtain information based on the caller ID, ANI or other identifier. The receiving party devices such as 402, 404, and 406 may receive calling party 114 phone number via a service provider 408. The receiving party device, such as the mobile phone 402, retrieves the phone number through the software and sends it to the service provider 408 through internet connectivity including but not limited to FTP, HTTP, TELNET, etc. The service provider 408 may function as a web server, listening information and requests from the software. When the service provider 408 receives a request with calling party 114 phone number, it sends the request to at least the CNAM DB 116 for name or Message DB 132 for message. In another embodiment of the present disclosure, at least the calling party 114 name or other information is returned by at least the CNAM database 116, an audio file is generated based on at least the name from the CNAM database 116. The generated file may then be stored at least in the mobile phone 402 as a table for later matching at the name requests or other information. The information gathered from at least the 116 and 132 by the service provider 408 is sends to the receiving party device such as the mobile phone 402 (not shown).
In accordance with one embodiment of the present disclosure, aspects of the present disclosure are provided within the called party devices. Thus, when a calling party communicates by calling or sending a message using the calling party device 114, the calling party device such as mobile device 402 receives a caller ID, Automatic Number Identification (ANI) or other identifier from the calling party. An example of the identifier may include an IP address of the calling party device 114 or a unique identifier of the calling party that can be received and transmitted by the calling party device 114. The identifier may include information related to at least one of a calling party and a called party.
In response to receiving the caller ID, ANI or other identifier, the called party device 402 sends a query for the calling party name to the CNAM database 116 and/or the other database 118. The query may be sent wirelessly from the called party device 402 to the CNAM database 116 and/or the other database 118 via a direct connection or via a data network (not shown). Once the query is received, a lookup is performed in the CNAM database 116 and/or the other database 118 for the calling party name and other information. If the calling party name is found, the CNAM database 116 and/or the other database 118 returns the calling party name and other information associated with the calling party to the called party device 402. Thereafter, the called party device 402 may store the information associated with the calling party in cache 131. In an embodiment, the cache 131 may be implemented as a local storage on the called party device 402. Further, the information may be stored based on configurable parameters such as, but not limited to, a number of audio files, a time duration, size and so forth. Moreover, the cache 131 may not include any duplicate information or records. For example, the information may be maintained for a total of 100 non-duplicate audio files for names of calling parties. In an embodiment of the invention, the size of the cache 131 may be limited to a predefined limit. For example, the predefined limit may be 200 KB. Further, the cache 131 may be maintained on a rolling basis. For example, after the size of the cache 131 reaches the predefined limit, and when new information is received, then a previous or the earliest information in the cache 131 may be deleted.
The called party device 402 can maintain the cache 131 by adding, deleting or modifying information corresponding to a calling party or a called party. For example, the called party device 402 may delete audio files after a predefined number of days. Alternatively, the called party device 402 may allow a calling party or called party to modify or delete a file or clear data stored on the cache 131. Also, the called party device 402 ensures the integrity of the data stored in the cache 131. To maintain integrity, the called party device 402 may generate a key on the fly using attributes of the calling party/called party and encrypt the information including audio response with the key. Alternatively, the called party device 402 may include software that detects and prevents malicious attack and ensure data safety.
Therefore, when a new communication such as a call or a message is received, the called party device 402 checks the cache 131 to determine whether the calling party information is located in the cache 131. If the information is present in the cache 131, then the called party device 402 verifies the status of an indicator for audio announcement. The indicator can be set by a called party or configured by the called party device 402 to an active or an inactive state. In case the status of the indicator is active, for example, then the called party device 402 looks up for audio file included in information on the cache 131. Subsequently, audio announcement is played based on the audio file. For example, the name of the calling party may be announced as the audio. Otherwise, in case the indicator is inactive then the called party device 402 looks up for the information excluding the audio file in the cache 131. Thereafter, the information is displayed on the called party device 402.
In one embodiment of the invention, if the information is not available in the cache 131, then the called party device 402 verifies the status of an indicator. Thereafter, if the status of the indicator is active, then the called party device 402 sends a query, for example, with the calling party number or other identifier to the CNAM database 116 and/or the other database 118 for lookup of information including the audio file. The CNAM database 116 and/or the other database 118 return calling party information to the called party device 402 if the calling party name/number and corresponding audio file is found in the respective database. Thereafter, the audio announcement is played based on the audio file. In an embodiment of the invention, the audio file is streamed to the called party device 402 for playing the audio announcement. For example, the audio announcement may be played when the audio file is being downloaded and/or stored on the called party device 402. In another embodiment of the invention, the audio file is downloaded and stored in the cache 131. Therefore, the called party device 402 may not be required to connect to the CNAM database 116 and/or the other database 118 when the information is available in the cache 131. However, if the status of the indicator is set as inactive, then the called party device 402 looks up for the information excluding the audio file in the CNAM database 116 and/or the other database 118. Thereafter, the information is displayed on the called party device 402.
Referring to
At step 512, a lookup is performed in the cache 131 of the called party device 402 for the audio files corresponding to the identifier. Thereafter, at step 514 if the audio file is available in the cache 131 then the audio announcement is played at step 516. Otherwise, if the information or the audio files is not available, then the process 500 continues to step 518. At step 518, a lookup is performed in the CNAM database 116 and/or the other database 118. Subsequently, at step 520, the information is downloaded and stored in the cache 131. Further, the audio announcement is played based on the audio file at step 516. In an embodiment of the invention, the audio announcement is streamed or played while being downloaded. As a result, the waiting time for the download and then playing the file is reduced. In another embodiment of the invention, the audio file is downloaded on the called party device 402 and then the announcement is played.
As discussed above, if the audio indicator status is not set to active, then the lookup is performed in the cache 131 for information excluding the audio file. For example, the lookup may be performed for text data such as name of the called party, but excluding the audio file. The process 500 then continues to step 508, where it is determined whether the information is available in the cache 131. In case, the information is available then the information is displayed on the called party device 402 at step 510. Otherwise, the process continues to step 522, where the information is looked up excluding the audio file. Subsequently, the information is displayed at step 510. In an embodiment of the invention, the information displayed at step 510 is clickable. For example, the text displayed from the information can be clicked to open a browser for additional information.
Although an exemplary embodiment of the system, method, and computer readable medium of the present disclosure has been illustrated in the accompanied drawings and described in the foregoing detailed description, it will be understood that the invention is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions without departing from the spirit and scope of the present disclosure as set forth and defined by the following claims. For example, a greater or lesser numbers of elements, modules, hardware, software, and/or firmware can be used to provide information delivery without departing from the spirit and scope of the present disclosure. Also, the device 102 may be a wireless mobile phone, a personal digital assistant, a cellular phone, an IP-enabled caller ID device, or a wired telephone that has IP communication capabilities. Further, the device 102 may include a memory (not shown) and a processor (not shown) to execute the process or the instructions. The memory may be for example, a Read Only Memory (ROM), a Random Access Memory (RAM), a disc media or any other computer readable medium comprising instruction executable by the processor. Although the device 102 is shown separate from the receiving party device 104, a person skilled in the art will appreciate that they can be co-located. Moreover, the receiving party device 104 may include all the functionalities of the device 102, without departing from the scope of this invention.
The embodiments of the invention are described above with reference to block diagrams and schematic illustrations of methods and systems according to embodiments of the invention. It will be understood that each block of the diagrams and combinations of blocks in the diagrams can be implemented by computer program instructions. These computer program instructions can be loaded onto one or more general purpose computers, or other programmable data processing apparatus to produce machines, such that the instructions which execute on the computers or other programmable data processing apparatus create means for implementing the functions specified in the block or blocks. Such computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the block or blocks.
Number | Name | Date | Kind |
---|---|---|---|
5165095 | Borcherding | Nov 1992 | A |
5311569 | Brozovich et al. | May 1994 | A |
5651055 | Argade | Jul 1997 | A |
5940484 | DeFazio et al. | Aug 1999 | A |
5970143 | Schneier et al. | Oct 1999 | A |
6014426 | Drysdale et al. | Jan 2000 | A |
6240175 | Barber | May 2001 | B1 |
6298128 | Ramey et al. | Oct 2001 | B1 |
6341161 | Latter et al. | Jan 2002 | B1 |
6353664 | Cannon et al. | Mar 2002 | B1 |
6459782 | Bedrosian et al. | Oct 2002 | B1 |
6496569 | Pelletier et al. | Dec 2002 | B2 |
6539080 | Bruce et al. | Mar 2003 | B1 |
6608886 | Contractor | Aug 2003 | B1 |
6658455 | Weinman | Dec 2003 | B1 |
6721406 | Contractor | Apr 2004 | B1 |
6920206 | Basore et al. | Jul 2005 | B2 |
6940954 | Toebes | Sep 2005 | B1 |
6950504 | Marx et al. | Sep 2005 | B1 |
6970543 | Lautenschlager et al. | Nov 2005 | B2 |
7024556 | Hadjinikitas et al. | Apr 2006 | B1 |
7127237 | Naruse et al. | Oct 2006 | B2 |
7200212 | Gosselin | Apr 2007 | B2 |
7248677 | Randall et al. | Jul 2007 | B2 |
7269413 | Kraft | Sep 2007 | B2 |
7840689 | Stewart | Nov 2010 | B2 |
7864940 | Harvey | Jan 2011 | B1 |
7869792 | Zhou et al. | Jan 2011 | B1 |
7899921 | Hill et al. | Mar 2011 | B2 |
8005195 | Luneau et al. | Aug 2011 | B2 |
8068825 | Mikan et al. | Nov 2011 | B2 |
8081992 | Book | Dec 2011 | B2 |
8095647 | Stewart | Jan 2012 | B2 |
8099780 | Lu | Jan 2012 | B2 |
8103868 | Christensen | Jan 2012 | B2 |
8199733 | Stewart | Jun 2012 | B2 |
8250204 | Stewart | Aug 2012 | B2 |
8255539 | Pierlot et al. | Aug 2012 | B2 |
8295819 | Kaplan et al. | Oct 2012 | B1 |
8300787 | Frank | Oct 2012 | B2 |
8331899 | Broms | Dec 2012 | B2 |
8417763 | Stewart | Apr 2013 | B2 |
8437460 | Daniell et al. | May 2013 | B2 |
8447018 | Martino et al. | May 2013 | B2 |
8548140 | Martino et al. | Oct 2013 | B2 |
8861697 | Martino et al. | Oct 2014 | B2 |
8879702 | White et al. | Nov 2014 | B1 |
9008292 | Martino et al. | Apr 2015 | B2 |
9036797 | Martino et al. | May 2015 | B2 |
9197740 | White et al. | Nov 2015 | B2 |
9392107 | Martino et al. | Jul 2016 | B2 |
9496569 | Gangwar | Nov 2016 | B2 |
9497306 | Martino et al. | Nov 2016 | B2 |
9674346 | White et al. | Jun 2017 | B2 |
9838535 | Martino et al. | Dec 2017 | B2 |
10091342 | Martino et al. | Oct 2018 | B2 |
10148813 | White et al. | Dec 2018 | B2 |
10257348 | White et al. | Apr 2019 | B2 |
10262281 | Vitek et al. | Apr 2019 | B1 |
10397387 | Martino et al. | Aug 2019 | B2 |
10455083 | White et al. | Oct 2019 | B2 |
10805446 | Martino | Oct 2020 | B2 |
10819846 | White et al. | Oct 2020 | B2 |
20020018546 | Horne | Feb 2002 | A1 |
20020057764 | Salvucci et al. | May 2002 | A1 |
20020067807 | Danner et al. | Jun 2002 | A1 |
20020120505 | Henkin et al. | Aug 2002 | A1 |
20020172336 | Postma et al. | Nov 2002 | A1 |
20030027559 | Umstetter et al. | Feb 2003 | A1 |
20030086558 | Seelig et al. | May 2003 | A1 |
20030112938 | Kanakubo et al. | Jun 2003 | A1 |
20030128821 | Luneau et al. | Jul 2003 | A1 |
20030144876 | Kosinski et al. | Jul 2003 | A1 |
20030177347 | Schneier et al. | Sep 2003 | A1 |
20030198323 | Watanabe | Oct 2003 | A1 |
20040044912 | Connary et al. | Mar 2004 | A1 |
20040067751 | Vandermeijden | Apr 2004 | A1 |
20040096042 | Orwick et al. | May 2004 | A1 |
20040148342 | Cotte | Jul 2004 | A1 |
20040228456 | Glynn et al. | Nov 2004 | A1 |
20040261126 | Addington et al. | Dec 2004 | A1 |
20050074109 | Hanson et al. | Apr 2005 | A1 |
20050084085 | Silver et al. | Apr 2005 | A1 |
20050160144 | Bhatia | Jul 2005 | A1 |
20050198099 | Motsinger et al. | Sep 2005 | A1 |
20050240432 | Jensen | Oct 2005 | A1 |
20050243975 | Reich et al. | Nov 2005 | A1 |
20050286687 | Sanmugasuntharam et al. | Dec 2005 | A1 |
20050286691 | Taylor et al. | Dec 2005 | A1 |
20060025112 | Hamanaga et al. | Feb 2006 | A1 |
20060026277 | Sutcliffe | Feb 2006 | A1 |
20060031553 | Kim | Feb 2006 | A1 |
20060072713 | Fernandes et al. | Apr 2006 | A1 |
20060085519 | Goode et al. | Apr 2006 | A1 |
20060123119 | Hill et al. | Jun 2006 | A1 |
20060166658 | Bennett et al. | Jul 2006 | A1 |
20060184684 | Weiss et al. | Aug 2006 | A1 |
20060293057 | Mazerski et al. | Dec 2006 | A1 |
20060294465 | Ronen et al. | Dec 2006 | A1 |
20070033419 | Kocher et al. | Feb 2007 | A1 |
20070064886 | Chiu et al. | Mar 2007 | A1 |
20070071201 | Pettus et al. | Mar 2007 | A1 |
20070127656 | Citron et al. | Jun 2007 | A1 |
20070133771 | Stifelman et al. | Jun 2007 | A1 |
20070154009 | Cameron | Jul 2007 | A1 |
20070195942 | Woodring | Aug 2007 | A1 |
20070206736 | Sprigg et al. | Sep 2007 | A1 |
20070207781 | Sprigg et al. | Sep 2007 | A1 |
20070248221 | Chatterjee et al. | Oct 2007 | A1 |
20070271596 | Boubion et al. | Nov 2007 | A1 |
20070280445 | Shkedi | Dec 2007 | A1 |
20080005325 | Wynn et al. | Jan 2008 | A1 |
20080070609 | Ackley | Mar 2008 | A1 |
20080084975 | Schwartz | Apr 2008 | A1 |
20080091796 | Story et al. | Apr 2008 | A1 |
20080101298 | Tasker | May 2008 | A1 |
20080140714 | Rhoads et al. | Jun 2008 | A1 |
20080159318 | Pierlot et al. | Jul 2008 | A1 |
20080177616 | Nemirofsky et al. | Jul 2008 | A1 |
20080246605 | Pfeffer et al. | Oct 2008 | A1 |
20080260135 | Siegrist | Oct 2008 | A1 |
20090234578 | Newby et al. | Sep 2009 | A1 |
20110007885 | Kirchhoff et al. | Jan 2011 | A1 |
20110013755 | Martino et al. | Jan 2011 | A1 |
20110087744 | Deluca et al. | Apr 2011 | A1 |
20110105091 | Jones | May 2011 | A1 |
20120226756 | Lindquist et al. | Sep 2012 | A1 |
20120230479 | Martin | Sep 2012 | A1 |
20120243675 | Diroo et al. | Sep 2012 | A1 |
20140003589 | Martino et al. | Jan 2014 | A1 |
20140122506 | Jebara et al. | May 2014 | A1 |
20140282759 | Harvey et al. | Sep 2014 | A1 |
Number | Date | Country | |
---|---|---|---|
20210029235 A1 | Jan 2021 | US |
Number | Date | Country | |
---|---|---|---|
60934407 | Jun 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16552811 | Aug 2019 | US |
Child | 17069831 | US | |
Parent | 16140858 | Sep 2018 | US |
Child | 16552811 | US | |
Parent | 15439724 | Feb 2017 | US |
Child | 16140858 | US | |
Parent | 15345840 | Nov 2016 | US |
Child | 15439724 | US | |
Parent | 14685915 | Apr 2015 | US |
Child | 15345840 | US | |
Parent | 14315618 | Jun 2014 | US |
Child | 14685915 | US | |
Parent | 14013466 | Aug 2013 | US |
Child | 14315618 | US | |
Parent | 12890829 | Sep 2010 | US |
Child | 14013466 | US | |
Parent | 11974983 | Oct 2007 | US |
Child | 12890829 | US |