Automatic gain control in a personal navigation device

Information

  • Patent Grant
  • 8073440
  • Patent Number
    8,073,440
  • Date Filed
    Thursday, April 1, 2010
    14 years ago
  • Date Issued
    Tuesday, December 6, 2011
    12 years ago
Abstract
In one example, a Bluetooth enabled navigation device pairs with a mobile phone and then sends a plurality of tuning transmissions, each at a different transmission power gain amount, to a remote server using the mobile phone. These tuning transmissions are encoded using frequency tones that synthesize speech for transmission through the mobile phone and a voice channel of its wireless telecommunications network. The navigation device then tunes transmit power settings according to a received response to the tuning transmissions and uses the tuned transmit power settings for subsequent transmission to the remote server using this particular mobile phone.
Description

This application is a non-provisional of U.S. Provisional Application No. 61/173,059 filed on Apr. 27, 2009, entitled: AUTOMATIC GAIN CONTROL IN A PERSONAL NAVIGATION DEVICE which is herein incorporated by reference in its entirety.


COPYRIGHT NOTICE

©2010 Airbiquity, Inc. A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. 37 CFR §1.71(d).


BACKGROUND OF THE INVENTION

Navigation devices (including Personal Navigation Devices (PNDs) and in-car electronic devices) output information to a user based on a location of the navigation devices. These navigation devices generally utilize the Global Positioning System (GPS) to determine the location, and then use speakers and/or displays to output map information, directions, etc.


To continue expanding and/or improving the features provided by navigation devices, there is a need to maximize opportunities for navigation devices to obtain network access, such as to the Internet. The disclosure that follows solves this and other problems.


SUMMARY OF THE INVENTION

The following is a summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not intended to identify key/critical elements of the invention or to delineate the scope of the invention. Its sole purpose is to present some concepts of the invention in a simplified form as a prelude to the more detailed description that is presented later.


In one example, a Bluetooth enabled navigation device pairs with a mobile phone and then sends a plurality of tuning transmissions, each at a different transmission power gain amount, to a remote server using the mobile phone. These tuning transmissions are encoded using frequency tones that synthesize speech for transmission through the mobile phone and a voice channel of its wireless telecommunications network. The navigation device then tunes transmit power settings according to a received response to the tuning transmissions and uses the tuned transmit power settings for subsequent transmission to the remote server using this particular mobile phone. Additional aspects and advantages of this invention will be apparent from the following detailed description of preferred embodiments, which proceeds with reference to the accompanying drawings.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates a system for accessing a remote server with a navigation device using a Bluetooth capable mobile phone.



FIG. 2 illustrates the navigation device shown in FIG. 1 as well as interactions between the navigation device and the remote server for tuning transmit power gain.



FIG. 3 illustrates how the navigation device shown in FIGS. 1 and 2 tunes transmit power gain.



FIG. 4 illustrates how the server shown in FIGS. 1 and 2 tunes transmit power gain.





DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS


FIG. 1 illustrates a system for accessing a remote server with a navigation device using a Bluetooth capable mobile phone.


The system 100 includes a navigation device 5 configured to upload data to the remote Internet Protocol (IP) server 15 through an available one of the mobile phones 1A-B. The software 8 exchanges tuning communications with the software 18 to tune transmit power gain on at least a per-phone basis, and then subsequently uses the tuned transmit power gain amounts according to which one of the mobile phones 1A-B is currently available. This tuning on at least a per-phone basis allows the navigation device 5 to communicate with the remote server 15 over a wide variety of mobile phones and wireless telecommunications networks, which in turn maximizes communication opportunities for the navigation device 5.


To appreciate how such tuning maximizes opportunities for the navigation device 5 to communicate with the server 15, consider how communications transmitted from the navigation device 5 to the server 15 are processed differently depending on which mobile phone 1A or 1B is used. Initially, depending on which one of the mobile phones 1A and 1B are used, the communications will be processed by different communication circuitry such as vocoders 20 and 21. Each of the vocoders 20 and 21 could affect the power gain of the signal differently, such as by changing the power gain by different amounts. Furthermore, the different wireless telecommunications networks 26 and 27 respectively associated with the mobile phones 1A and 1B can also have different vocoders 22 and 23, which can also affect signals differently. As a result of these differences, in the absence of tuning on at least a per-phone basis, a receiver can receive a signal that is too weak or too strong depending on which combination of vocoders process transmissions. While it is possible for the server 15 and/or its In-Band Signaling (IBS) modem 19 to detect errors resulting from recovery of a signal that is too weak or too strong and request retransmission, such retransmission takes time and can still result in a signal that is too weak or too strong.


In contrast, the system 100 tunes transmit power gain on at least a per-phone basis, which allows a transmission 29A from the navigation device 5 to be received and recovered by the IBS 19 with no errors or minimal errors regardless of which transmission path 30A or 30B is used by the navigation device 5. In other words, transmissions 29B and 29C can have substantially similar power gains despite the differences between the paths 30A and 30B.


This tuning on at least a per-phone basis means that transmit power gain can be set according to the specific available phone, not just tuned to the particular make or model of the available phone. Two mobile phones of the same make or model can also affect signal strength differently because the components within the mobile phones can have different operational characteristics. For example, electronic components are typically rated for performance within a range of values. Accordingly, some of these electronic components operate at the high end of the range while others operate at the low end of the range, which can result in two vocoders of the same model amplifying a signal differently during processing. For example, two resistors of the same model can exhibit different resistances, and these differences in turn affect power gain. For this reason, the software 8 and 18 tunes transmit power on at least a per-phone basis rather than a per-model basis.


Although the software 8 and 18 tunes transmit power on at least a per-phone basis, it should be noted that such tuning can be even more granular in some examples. This will be discussed later in greater detail with reference to FIG. 2.


Referring still to FIG. 1, it should be appreciated that the system 100 thus maximizes upload opportunities for the navigation device 5. Stated another way, the navigation device 5 is not restricted to communicate with the IP server 15 using any particular designated phone but rather can access server 15 when in range of nearly any Bluetooth enabled mobile phone.


Further to the point made in the previous paragraph, it is preferable for the navigation device 5 to utilize a mobile phone for uploads to the IP server 15 without regard to whether the available mobile phone supports a packet data connection over its wireless telecommunication network. For example, the illustrated mobile phones 1A-B do not support packet data connections over the wireless telecommunications networks 26 and 27, yet can be utilized by the navigation device 5 for IP network access, as will be described in the next paragraph.


For this and other reasons, transmissions from the navigation device 5 to the server 15, including the tuning transmissions that will be discussed later in greater detail, are modulated by the IBS modem 9 for transmission across a voice channel of the wireless telecommunication network. The IBS modem 9 modulates received digital data into audio frequency tones. These frequency tones are selected to synthesize speech so that the frequency tones will pass with minimal attenuation or corruption through the vocoder 20/21 of the available one of the mobile phones 1A-B and any vocoders 22/23 in the available wireless telecommunication network 26/27 (other networks between network 26/27 and the server 15 could operate vocoders as well). Before encoding and modulation into audio tones, the digital data preferably is formatted into one or more packets. A packet formatter may prepend, for example, a header and a sync pattern prior to the payload. Error correction bits, checksums and other enhancements to the packet may be added as well. The navigation device 5 can then transmit the IBS modulated communications 29A over a Bluetooth connection for voice data, to be forwarded over a voice channel of the wireless telecommunications network, through any intervening networks such as the IP network 28, received and demodulated by the IBS modem 19 (recovered into a bitstream), and then finally processed by the server 15.


It should be understood that reliable access to the server 15, or for that matter any remote network, can enable a wide variety of applications for the navigation device. Applications on the navigation device 5 that are part of the navigation system can obtain location-based information in real time can obtain real-time location based information. For example, the navigation device 5 could obtain real-time information about traffic accidents near a current location determined via GPS. The navigation device 5 can also download updates to an internal navigation database, e.g. updating a stored map to information about a new route.


Furthermore, any other type of application on the navigation device 5 can also be provided with remotely stored data using the tuned transmissions described herein. This allows the feature set of the navigation device 5 to be expanded to other applications not necessarily related to navigation. For example, an application on the navigation device 5 could be used to obtain stock quotes or other information available via the Internet. It should be understood it is possible for any type of application operating on the navigation device 5 to obtain access to any type of network as well.


It should be understood that the principles described herein can be applied to any Bluetooth capable mobile device regardless of whether such device has any navigation capabilities. Also, the principles described above can be applied regardless of whether the communication between the device and the mobile phone uses Bluetooth or some other wireless protocol.


It should be understood that power gain is based on the ratio of the signal output of a system to the signal input of the system. When the term transmit power gain is used, the relevant system is the navigation device 5 (or another device configured to upload data to a server). When the term receive power gain is used, the relevant system is the server 15.


Transmit power gain can be adjusted on the navigation device 15 using any known method for adjusting gain. This can include adjusting amplifiers, variable resistors, or other circuit components, in either an input stage or an output stage of a circuit on the navigation device 15.



FIG. 2 illustrates the navigation device shown in FIG. 1 as well as interactions between the navigation device and the remote server for tuning transmit power gain.


The navigation device 5 includes a table 38 to be updated by the software 8. The table 38 is later used to set a power gain used for transmitting data based at least in part on the available mobile phone.


In the example, the navigation device 5 pairs 41 with mobile phone 31 to establish a Bluetooth connection between the navigation device 5 and the mobile phone 31. This Bluetooth connection can be established according to the principles described in U.S. patent application Ser. No. 12/752,911, “USING A BLUETOOTH CAPABLE MOBILE PHONE TO ACCESS A REMOTE NETWORK”, which is herein incorporated by reference in its entirety for all purposes. Also, the pairing can be triggered by a request from an application operating on the navigation device 15 or from a user interface of the navigation device 15.


During pairing, the software 8 learns a Bluetooth client ID for the mobile phone 31. This Bluetooth client ID is a globally unique identifier that will be used to uniquely identify the mobile phone 31 in the table 38.


The mobile phone 31 receives a session initiation request from the IP server 15. The navigation device 5 processes the request 43 and then the software 8 uses a mechanism to delay session initiation. For example, the software 8 can causes the session initiation to be delayed by using a bit setting 44 in the acknowledgement or any other mechanism for delaying the session initiation. The software 18 is configured to observe the bit setting 44 and delay the session initiation accordingly.


The software 8 then generates test data 45 to be transmitted by modulating received digital data into audio frequency tones using IBS modem 9. These frequency tones are selected to synthesize speech so that the frequency tones will pass with minimal attenuation or corruption through any intervening vocoders. Before encoding and modulation into audio tones, the digital data may be formatted into one or more packets. A packet formatter may prepend, for example, a header and a sync pattern prior to the payload. Error correction bits, checksums and other enhancements to the packet may be added as well.


The software 8 then transmits the modulated test data 45 a plurality of times with each transmission 51 being at a different transmit power gain amount. For example, the test data 45 may be transmitted three times with each transmission being at a different power gain amount.


On the server 15 the software 18 receives the transmissions and determines a receive power gain. The software 18 sends back response 52 to indicate the determined receive power gain.


On the navigation device 5 the software 8 correlates the receive power gain for each transmission of the test data with the transmit power gain for that transmission. This correlation may be conducted according to information included in the response 52.


The software 8 then analyzes the receive power gain amounts. This analysis can include generating a graph containing receive power gain on one axis and transmit power gain on another axis. If the graph is used, the software 8 can connect points on the graph to generate a line graph. The line on the generated graph can then be used to interpolate transmit power gain that will generate a desired receive transmit power gain at the server 15. It should be apparent that the analysis of the receive power gain can operate completely independently of graphs but in any case a transmit power gain is interpolated based on the analysis of the receive transmit power gain. The interpolated transmit power gain will typically be a different value than the transmit power gain used in transmission 51, but it is possible to simply select from one of the transmit power gain amounts used in transmission 51.


The software 8 configures the navigation device 5 so that transmission will be at the power gain identified during the analysis. This can include setting a Bluetooth transceiver on the navigation device 5 or controlling any other software or hardware component on the navigation device 5. Accordingly, when delayed session initiation 61 occurs, transmissions 66 are at the set transmit power gain.


As discussed previously, the IBS modem 9 is used to modulate the packet data 67 of the transmissions 66. The IBS modem 19 recovers the data from the received communications, which are at a tuned receive power gain.


The software 8 also stores the interpolated transmit power gain in table 38 in association with the unique Bluetooth client identifier for the mobile phone 31. The table 38 shows entries in the mobile phone column and the transmit power gain column to illustrate such association. Thereafter, the transmit power gain amounts from the table 38 are used when transmitting data according to which mobile phone is used for the transmission.


The illustrated table 38 also includes the optional column including a network identifier to specify the wireless telecommunications network used during the tuning. This column can be used to provide additional granularity to the tuning. As discussed previously, different wireless telecommunication networks utilize different vocoders, which in at least some cases will have a significant effect on the receive power gain. Therefore, in some examples the tuning can be on a per-phone and per-network basis. This is illustrated in the table 38 where the Bluetooth client ID C is associated with two different transmit power gain amounts, 2.5 dB and 3.1 dB.


It should be understood that the principles described above can be used to add even more granularity to the tuning, e.g. further columns in the table. For example, the same phone/network vocoder combination can be associated with a plurality of tuned power gain amounts depending on the currently utilized mode of the vocoders. Vocoders can operate in different modes, e.g. full rate and half rate, and depending on which mode is used receive power gain can be affected differently. Accordingly, in one example the navigation device 5 determines a current mode of the vocoders and selects between the transmit power gain for this particular phone/network combination based on the current mode. Other possible columns include time of day, the identity of other networks intervening between the wireless telecommunications network and the server 15 (other networks such as IP networks can include vocoders), etc.


Thereafter, the software 8 can compare the Bluetooth client ID of an available mobile phone (and possibly other variables such as the network ID) to the table 38 and identify transmit power gain amounts. The software 8 then sets the Bluetooth transceiver on the mobile phone using the identified transmit power gain amount.


Once the transmit power gain has been set, the software 18 on the server 15 can continually monitor received transmissions from the navigation device. It is possible that receive power gain can “drift” or otherwise change over time despite the navigation device 5 continuing to use the same transmission settings with the same mobile phone. This can occur for many reasons such as the navigation device 5 and the available mobile phone roaming between networks, simply changing a distance from a tower, entering or leaving a power saving mode, etc. In any case, the software 18 can trigger the software 8 on the navigation device 5 to initiate a new tuning process at any time.


The software 18 can determine when a new tuning process is needed using any process. In one example, the software 18 continuously monitors receive power gain of transmissions from the navigation device and triggers initiation of a new tuning process if this receive power gain falls outside a threshold range. In another example, the software 18 monitors a rate of transmission errors over time and triggers initiation of a new tuning process if this transmission error rate exceeds a threshold. Since transmission errors can be related to other factors besides power gain, the software 18 could do some minimal troubleshooting to exclude transmission errors that are unlikely to be caused by power gain from this transmission error rate.


Although the session initiation request 43 was sent by the server 15 in the above described example, in other examples the navigation device 5 can send the session initiation request with the tuning performed before, after, or during the sending. In such an example it may not be necessary for the software 8 to cause a delay in session initiation.



FIG. 3 illustrates how the navigation device shown in FIGS. 1 and 2 tunes transmit power gain.


In block 301, the navigation device establishes a Bluetooth connection with a mobile phone for communicating with a remote server. The Bluetooth connection can be established as described in U.S. patent application Ser. No. 12/752,911, “USING A BLUETOOTH CAPABLE MOBILE PHONE TO ACCESS A REMOTE NETWORK”.


In block 302, the navigation device compares a unique identifier for the mobile phone (and possibly other attributes such as a network identifier) with a table that correlates mobile phones to tuned transmit power gain amounts. If there is an entry for the mobile phone in the table in diamond 303, then in block 304A the navigation device sets a Bluetooth transceiver according to the tuned transmit power gain for the mobile phone. The navigation device initiates a session with the remote server for uploading data at the set transmit power gain in block 305.


If there is no entry in the table in diamond 303, then in block 304B the navigation device delays initiation of a session with the remote server. In block 306, the navigation device modulates a received digital bit sequence into an audio signal that has different frequency tones for different bit values where the frequency tones are selected to pass through a wireless voice channel. The navigation device transmits the audio signals using different transmit power gain amounts in block 307.


In block 308, the navigation device receives back a response to the transmissions indicating receive power gain amounts at a remote server. In block 309, the navigation device determines a tuned transmit power gain for the mobile phone by analyzing the receive power gain amounts. The navigation device generates an entry in the table for the mobile phone to associate the tuned transmit power gain with the mobile device in block 310. The process then returns to block 304A.



FIG. 4 illustrates how the server shown in FIGS. 1 and 2 tunes transmit power gain.


In block 401, the server receives a plurality of transmissions of an audio signal. In block 402, the server determines a receive power gain for each of these transmissions and sends a communication identifying the receive power gain to a navigation device.


Thereafter, the server receives a transmission having a tuned receive power gain in block 403. If a subsequently received transmission has a receive power gain outside a threshold range, in block 404 the server can signal the navigation device to conduct a new tuning process. The process then returns to block 401.


It will be obvious to those having skill in the art that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the invention. The scope of the present invention should, therefore, be determined only by the following claims.


Most of the equipment discussed above comprises hardware and associated software. For example, the typical navigation device is likely to include one or more processors and software executable on those processors to carry out the operations described. We use the term software herein in its commonly understood sense to refer to programs or routines (subroutines, objects, plug-ins, etc.), as well as data, usable by a machine or processor. As is well known, computer programs generally comprise instructions that are stored in machine-readable or computer-readable storage media. Some embodiments of the present invention may include executable programs or instructions that are stored in machine-readable or computer-readable storage media, such as a digital memory. We do not imply that a “computer” in the conventional sense is required in any particular embodiment. For example, various processors, embedded or otherwise, may be used in equipment such as the components described herein.


Memory for storing software again is well known. In some embodiments, memory associated with a given processor may be stored in the same physical device as the processor (“on-board” memory); for example, RAM or FLASH memory disposed within an integrated circuit microprocessor or the like. In other examples, the memory comprises an independent device, such as an external disk drive, storage array, or portable FLASH key fob. In such cases, the memory becomes “associated” with the digital processor when the two are operatively coupled together, or in communication with each other, for example by an PO port, network connection, etc. such that the processor can read a file stored on the memory. Associated memory may be “read only” by design (ROM) or by virtue of permission settings, or not. Other examples include but are not limited to WORM, EPROM, EEPROM, FLASH, etc. Those technologies often are implemented in solid state semiconductor devices. Other memories may comprise moving parts, such as a conventional rotating disk drive. All such memories are “machine readable” or “computer-readable” and may be used to store executable instructions for implementing the functions described herein.


A “software product” refers to a memory device in which a series of executable instructions are stored in a machine-readable form so that a suitable machine or processor, with appropriate access to the software product, can execute the instructions to carry out a process implemented by the instructions. Software products are sometimes used to distribute software. Any type of machine-readable memory, including without limitation those summarized above, may be used to make a software product. That said, it is also known that software can be distributed via electronic transmission (“download”), in which case there will typically be a corresponding software product at the transmitting end of the transmission, or the receiving end, or both.


Having described and illustrated the principles of the invention in a preferred embodiment thereof, it should be apparent that the invention may be modified in arrangement and detail without departing from such principles. We claim all modifications and variations coming within the spirit and scope of the following claims.

Claims
  • 1. A memory device having instructions stored thereon that, in response to execution by a processing device, cause the processing device to perform operations comprising: communicating with a remote server, the communications passing through a Bluetooth connection between a navigation device and a mobile phone and a wireless voice channel of a wireless telecommunications network associated with the mobile phone;modulating a received digital bit sequence into an audio signal that has different frequency tones for different bit values, wherein the frequency tones are selected to pass through the wireless voice channel unobstructed by vocoders operating within the wireless telecommunications network;transmitting the audio signal a first time using a first transmit power gain amount and a second time using a second different transmit power gain amount;receiving back a response indicating receive power gain amounts at the remote server for the first and second transmissions; anddetermining a third transmit power gain amount by analyzing the response and using the third transmit power gain amount to transmit data to the remote server using the mobile phone.
  • 2. The memory device of claim 1, wherein execution of the instructions causes the processing device to perform operations further comprising: discovering a Bluetooth client identifier for the mobile phone; andgenerating an entry in a navigation device table to associate the discovered Bluetooth client identifier with the third transmit power gain amount.
  • 3. The memory device of claim 2, wherein the navigation device table includes a plurality of entries each associating a custom transmit power gain amount with a Bluetooth enabled mobile phone.
  • 4. The memory device of claim 1, wherein execution of the instructions causes the processing device to perform operations further comprising: discovering a Bluetooth client identifier for the mobile phone;identifying the wireless telecommunications network; andgenerating an entry in a navigation device table to associate a combination of the discovered Bluetooth client identifier and the wireless telecommunications network identification with the third transmit power gain amount.
  • 5. The memory device of claim 4, wherein the navigation device table includes a plurality of entries each associating a custom transmit power gain amount with a combination of a Bluetooth enabled mobile phone and a mobile network.
  • 6. The memory device of claim 1, wherein execution of the instructions causes the processing device to perform operations further comprising: receiving a communication indicating that a receive power gain at the remote server is outside a predetermined range; andin response to receiving the communication, sending a plurality of modulated transmissions at different power gain amounts to identify a new transmit power gain amount for use with the mobile phone.
  • 7. A method, comprising: communicating with a remote server, the communications passing through a Bluetooth connection between a navigation device and a mobile phone and a wireless voice channel of a wireless telecommunications network associated with the mobile phone;sending a plurality of tuning transmissions to the remote server, wherein the tuning transmissions are modulated using frequency tones that are selected to pass through the wireless voice channel unobstructed by vocoders operating within the wireless telecommunications network, and wherein the tuning transmissions are transmitted using different transmit power gain amounts;receiving back a response indicating receive power gain amounts at the remote server and correlating each receive power gain amount to a respective one of the tuning transmissions; anddetermining a tuned transmit power gain amount by analyzing the receive power gain amounts and using the tuned transmit power gain amount when uploading data to the remote server using the mobile phone.
  • 8. The method of claim 7, further comprising: identifying a currently available mobile phone in response to a request for transmitting to the remote server;comparing a unique identifier for the currently available mobile phone to a table associating mobile phones with the tuned transmit power gain amounts;setting a Bluetooth transceiver on the navigation device according to the comparison; anduploading the data to the remote server through the currently available mobile phone after setting the Bluetooth transceiver.
  • 9. The method of claim 8, wherein the request is received over a user interface of the navigation device.
  • 10. The method of claim 7, further comprising: receiving a session initiation request from the remote server;setting a bit in an acknowledgement message to cause a delay in initiating the session; andsending the acknowledgement with the set bit.
  • 11. The method of claim 10, wherein the tuning transmissions are sent after or in conjunction with sending the acknowledgement and before a delayed session initiation.
  • 12. The method of claim 7, further comprising sending another plurality of tuning transmissions whenever requested by the remote server and changing transmission settings according to a most recent tuning.
  • 13. The method of claim 7, further comprising: determining a mode of operation of a vocoder of the mobile phone or a vocoder of the wireless telecommunications network;generating an entry in a navigation device table to associate the tuned transmit power gain amount with the mobile phone; andin the generated entry, recording the determined mode of operation such that the tuned transmit power gain amount is associated with the determined mode of operation.
  • 14. The method of claim 13, further comprising: generating another entry in the navigation device table to associate the mobile phone with a different tuned transmit power gain amount; andin the generated another entry, recording a different mode of operation.
  • 15. A server having a processor readable medium encoded with instructions that, if executed, result in: communicating with a remote navigation device, the communications passing through a wireless voice channel extending to a mobile phone and a Bluetooth connection extending between the mobile phone and a navigation device;determining power gain amounts of a plurality of received audio signals originating from the navigation device;transmitting a communication that identifies the receive power gain amounts and correlating each receive power gain amount with a transmission from the navigation device; andreceiving an upload from the navigation device, wherein a receive power gain amount of the received upload is tuned for In-Band Signaling (IBS) demodulation on the server.
  • 16. The server of claim 15, wherein the instructions, if executed, result in: identifying a newly received transmission having a receive power gain amount that is outside a threshold range of receive power gain; andin response to the identification, causing the navigation device to transmit the plurality of audio signals at the different power gain amounts.
  • 17. The server of claim 15, wherein the instructions, if executed, result in: requesting a session with the navigation device;analyzing an acknowledgement from the navigation device for a bit setting requesting a delayed initiation of the session; anddelaying session initiation for a predetermined time period associated with the power gain amount determination.
  • 18. A system, comprising: a navigation device configured to establish a Bluetooth connection with an available mobile phone;the navigation device configured to compare a unique identifier for the available mobile phone to a table that maps unique identifiers to transmit power gain amounts;if the comparison identifies an entry, the navigation device configured to upload data to a remote server through the available mobile phone at a transmit power gain amount indicated in the identified entry;if the comparison does not identify an entry, the navigation device configured to transmit an audio signal at a plurality of different transmit power gain amounts and receive back a response from the remote server indicating receive power gain amounts for the transmissions; andthe navigation device to determine a transmit power gain amount according to the response and to generate an entry in the table to associate the determined transmit power gain amount with the unique identifier for the available mobile phone.
  • 19. The system of claim 18, further comprising: the server configured to determine the receive power gain amounts according to an analysis of the audio signal transmissions; andthe server configured to generate and send a communication to be used by the navigation device to optimize subsequent transmissions with the available mobile phone.
  • 20. The system of claim 18, further comprising: the navigation device configured to tune transmit power settings according to the determined transmit power gain amount; andthe server configured to trigger the navigation device to send a new plurality of audio signal transmissions used for re-tuning transmit power settings on the navigation device.
US Referenced Citations (412)
Number Name Date Kind
3742197 Pommerening Jun 1973 A
3742463 Haselwood Jun 1973 A
3971888 Ching Jul 1976 A
3984814 Bailey, Jr. Oct 1976 A
3985965 Field et al. Oct 1976 A
4158748 En Jun 1979 A
4218654 Ogawa Aug 1980 A
4310722 Schaible Jan 1982 A
4355310 Belaigues Oct 1982 A
4368987 Waters Jan 1983 A
4494114 Kaish Jan 1985 A
4494211 Schwartz Jan 1985 A
4539557 Redshaw Sep 1985 A
4577343 Oura Mar 1986 A
4595950 Lofberg Jun 1986 A
4598272 Cox Jul 1986 A
4599583 Shimozono et al. Jul 1986 A
4607257 Noguchi Aug 1986 A
4630301 Hohl Dec 1986 A
4641323 Tsang Feb 1987 A
4651157 Gray Mar 1987 A
4656463 Anders Apr 1987 A
4675656 Narcisse Jun 1987 A
4685131 Horne Aug 1987 A
4750197 Denekamp Jun 1988 A
4754255 Sanders Jun 1988 A
4766589 Fisher Aug 1988 A
4776003 Harris Oct 1988 A
4831647 D'Avello et al. May 1989 A
4860336 D'Avello et al. Aug 1989 A
4914651 Lusignan Apr 1990 A
4918425 Greenberg Apr 1990 A
4918717 Bissonnette Apr 1990 A
4926444 Hamilton et al. May 1990 A
4941155 Chuang Jul 1990 A
4965821 Bishop et al. Oct 1990 A
4977609 McClure Dec 1990 A
4984238 Watanabe Jan 1991 A
5014344 Goldberg May 1991 A
5025455 Nguyen Jun 1991 A
5036537 Jeffers et al. Jul 1991 A
5040214 Grossberg et al. Aug 1991 A
5043736 Darnell et al. Aug 1991 A
5081667 Drori Jan 1992 A
5095307 Shimura Mar 1992 A
5119403 Krishnan Jun 1992 A
5119504 Durboraw, III Jun 1992 A
5134644 Garton Jul 1992 A
5155689 Wortham Oct 1992 A
5191611 Lang Mar 1993 A
5201071 Webb Apr 1993 A
5203012 Patsiokas Apr 1993 A
5208446 Martinez May 1993 A
5212831 Chuang May 1993 A
5214556 Kilbel May 1993 A
5218618 Sagey Jun 1993 A
5223844 Mansell Jun 1993 A
5227776 Starefoss Jul 1993 A
5235633 Dennison et al. Aug 1993 A
5245634 Averbuch Sep 1993 A
5245647 Grouffal Sep 1993 A
5272747 Meads Dec 1993 A
5282204 Shpancer Jan 1994 A
5289372 Guthrie Feb 1994 A
5301353 Borras Apr 1994 A
5301359 Van Den Heuvel Apr 1994 A
5305384 Ashby, III Apr 1994 A
5317309 Vercellotti May 1994 A
5331635 Ota Jul 1994 A
5333175 Ariyavisitakul Jul 1994 A
5334974 Simms Aug 1994 A
5347272 Ota Sep 1994 A
5363375 Chuang Nov 1994 A
5363376 Chuang Nov 1994 A
5365450 Schuchman et al. Nov 1994 A
5365577 Davis Nov 1994 A
5379224 Brown Jan 1995 A
5381129 Boardman Jan 1995 A
5388147 Grimes Feb 1995 A
5388247 Goodwin Feb 1995 A
5389934 Kass Feb 1995 A
5390216 Bilitza Feb 1995 A
5396539 Slekys Mar 1995 A
5396653 Kivari Mar 1995 A
5408684 Yunoki Apr 1995 A
5410541 Hotto Apr 1995 A
5410739 Hart Apr 1995 A
5414432 Penny, Jr. May 1995 A
5418537 Bird May 1995 A
5420592 Johnson May 1995 A
5422816 Sprague et al. Jun 1995 A
5428636 Meier Jun 1995 A
5438337 Aguado Aug 1995 A
5440491 Kawano Aug 1995 A
5448622 Huttunen Sep 1995 A
5450130 Foley Sep 1995 A
5459469 Schuchman Oct 1995 A
5461390 Hoshen Oct 1995 A
5475864 Hamabe Dec 1995 A
5475868 Duque-Anton Dec 1995 A
5479480 Scott Dec 1995 A
5479482 Grimes Dec 1995 A
5483549 Weinberg et al. Jan 1996 A
5491690 Alfonsi Feb 1996 A
5497149 Fast Mar 1996 A
5504491 Chapman Apr 1996 A
5506888 Hayes Apr 1996 A
5509035 Teidemann, Jr. Apr 1996 A
5510797 Abraham Apr 1996 A
5513111 Wortham Apr 1996 A
5515043 Berard May 1996 A
5519403 Bickley et al. May 1996 A
5519621 Wortham May 1996 A
5528232 Verma Jun 1996 A
5530701 Stillman Jun 1996 A
5537458 Suomi Jul 1996 A
5539810 Kennedy, III et al. Jul 1996 A
5543789 Behr Aug 1996 A
5544222 Robinson Aug 1996 A
5544225 Kennedy, III Aug 1996 A
5546445 Dennison et al. Aug 1996 A
5550551 Alesio Aug 1996 A
5551066 Stillman Aug 1996 A
5555286 Tendler Sep 1996 A
5555520 Sudo Sep 1996 A
5557254 Johnson Sep 1996 A
5565858 Guthrie Oct 1996 A
5566173 Steinbrecher Oct 1996 A
5572204 Timm et al. Nov 1996 A
5576716 Sadler Nov 1996 A
5587715 Lewis Dec 1996 A
5590396 Henry Dec 1996 A
5594425 Ladner Jan 1997 A
RE35498 Barnard Apr 1997 E
5619684 Goodwin Apr 1997 A
5621388 Sherburne Apr 1997 A
5625668 Loomis Apr 1997 A
5627517 Theimer May 1997 A
5630206 Urban et al. May 1997 A
5635450 Mayer Jun 1997 A
5637355 Stanforth Jun 1997 A
5640444 O'Sullivan Jun 1997 A
5650770 Schlager Jul 1997 A
5663734 Krasner Sep 1997 A
5666357 Jangi Sep 1997 A
5668803 Tymes Sep 1997 A
5673305 Ross Sep 1997 A
5680439 Aguilera Oct 1997 A
5686910 Timm et al. Nov 1997 A
5687215 Timm et al. Nov 1997 A
5687216 Svensson Nov 1997 A
5691980 Welles, II Nov 1997 A
5703598 Emmons Dec 1997 A
5711013 Collett Jan 1998 A
5712619 Simkin Jan 1998 A
5712899 Pace, II Jan 1998 A
5724243 Westerlage Mar 1998 A
5726893 Schuchman et al. Mar 1998 A
5726984 Kubler et al. Mar 1998 A
5731757 Layson, Jr. Mar 1998 A
5732326 Maruyama Mar 1998 A
5734981 Kennedy, III Mar 1998 A
5742233 Hoffman Apr 1998 A
5748083 Rietkerk May 1998 A
5748084 Isikoff May 1998 A
5751246 Hertel May 1998 A
5752186 Malackowski May 1998 A
5752193 Scholefield May 1998 A
5752195 Tsuji May 1998 A
5754554 Nakahara May 1998 A
D395250 Kabler et al. Jun 1998 S
5761204 Grob Jun 1998 A
5761292 Wagner Jun 1998 A
5771001 Cobb Jun 1998 A
5771455 Kennedy, III Jun 1998 A
5774876 Woolley Jun 1998 A
5781156 Krasner Jul 1998 A
5784422 Heermann Jul 1998 A
5786789 Janky Jul 1998 A
5790842 Charles Aug 1998 A
5794124 Ito Aug 1998 A
5796808 Scott et al. Aug 1998 A
5797091 Clise Aug 1998 A
5804810 Woolley Sep 1998 A
5805576 Worley, III Sep 1998 A
5812087 Krasner Sep 1998 A
5812522 Lee Sep 1998 A
5815114 Speasl Sep 1998 A
RE35916 Dennison et al. Oct 1998 E
5825283 Camhi Oct 1998 A
5825327 Krasner Oct 1998 A
5826188 Tayloe Oct 1998 A
5831574 Krasner Nov 1998 A
5832394 Wortham Nov 1998 A
5835907 Newman Nov 1998 A
5838237 Revell Nov 1998 A
5841396 Krasner Nov 1998 A
5841842 Baum Nov 1998 A
5842141 Vaihoja Nov 1998 A
5850392 Wang Dec 1998 A
5856986 Sobey Jan 1999 A
5864578 Yuen Jan 1999 A
5864763 Leung Jan 1999 A
5870675 Tuutijarvi Feb 1999 A
5874914 Krasner Feb 1999 A
5881069 Cannon Mar 1999 A
5881373 Elofsson Mar 1999 A
5884214 Krasner Mar 1999 A
5886634 Muhme Mar 1999 A
5890108 Yeldener Mar 1999 A
5892441 Woolley Apr 1999 A
5892454 Schipper Apr 1999 A
5901179 Urabe May 1999 A
5911129 Towell Jun 1999 A
5912886 Takahashi Jun 1999 A
5913170 Wortham Jun 1999 A
5917449 Sanderford Jun 1999 A
5918180 Dimino Jun 1999 A
5930340 Bell Jul 1999 A
5930722 Han Jul 1999 A
5933468 Kingdon Aug 1999 A
5936526 Klein Aug 1999 A
5937355 Joong Aug 1999 A
5940598 Strauss Aug 1999 A
5945944 Krasner Aug 1999 A
5946304 Chapman Aug 1999 A
5946611 Dennison et al. Aug 1999 A
5949335 Maynard Sep 1999 A
5953694 Pillekamp Sep 1999 A
5960363 Mizikovsky Sep 1999 A
5961608 Onosaka Oct 1999 A
5963130 Schlager Oct 1999 A
5963134 Bowers Oct 1999 A
5970130 Katko Oct 1999 A
5978676 Guidri Nov 1999 A
5991279 Haugli Nov 1999 A
5999124 Sheynblat Dec 1999 A
5999126 Ito Dec 1999 A
6002363 Krasner Dec 1999 A
6006189 Strawczynski Dec 1999 A
6009325 Retzer Dec 1999 A
6009338 Iwata Dec 1999 A
6011973 Valentine Jan 2000 A
6014089 Tracy Jan 2000 A
6014376 Abreu Jan 2000 A
6018654 Valentine Jan 2000 A
6021163 Hoshi Feb 2000 A
6024142 Bates Feb 2000 A
6031489 Wyrwas Feb 2000 A
6032037 Jeffers Feb 2000 A
6038310 Hollywood Mar 2000 A
6038595 Ortony Mar 2000 A
6041124 Sugita Mar 2000 A
6044257 Boling Mar 2000 A
6049971 Petit Apr 2000 A
6055434 Seraj Apr 2000 A
6057756 Engellenner May 2000 A
6067044 Whelan May 2000 A
6067457 Erickson May 2000 A
6069570 Herring May 2000 A
6070089 Brophy May 2000 A
6075458 Ladner Jun 2000 A
6076099 Chen Jun 2000 A
6081523 Merchant Jun 2000 A
6091969 Brophy Jul 2000 A
6097760 Spicer Aug 2000 A
6101395 Keshavachar Aug 2000 A
6121922 Mohan Sep 2000 A
6122271 McDonald Sep 2000 A
6122514 Spaur Sep 2000 A
6131067 Girerd Oct 2000 A
6131366 Fukuda Oct 2000 A
6133874 Krasner Oct 2000 A
6140956 Hillman et al. Oct 2000 A
6144336 Preston et al. Nov 2000 A
6151493 Sasakura Nov 2000 A
6154658 Caci Nov 2000 A
6166688 Cromer Dec 2000 A
6169497 Robert Jan 2001 B1
6173194 Vanttila Jan 2001 B1
6175307 Peterson Jan 2001 B1
6181253 Eschenbach Jan 2001 B1
6195736 Lisle Feb 2001 B1
6208959 Jonsson Mar 2001 B1
6212207 Nicholas Apr 2001 B1
6226529 Bruno et al. May 2001 B1
6236652 Preston May 2001 B1
6249227 Brady Jun 2001 B1
6266008 Huston Jul 2001 B1
6269392 Cotichini Jul 2001 B1
6272315 Chang Aug 2001 B1
6275990 Dapper Aug 2001 B1
6282430 Young Aug 2001 B1
6288645 McCall Sep 2001 B1
6295461 Palmer Sep 2001 B1
6300863 Cotichini Oct 2001 B1
6300875 Schafer Oct 2001 B1
6301480 Kennedy, III Oct 2001 B1
6304186 Rabanne Oct 2001 B1
6304637 Mirashrafi Oct 2001 B1
6307471 Xydis Oct 2001 B1
6308060 Wortham Oct 2001 B2
6320535 Hillman Nov 2001 B1
6321091 Holland Nov 2001 B1
6326736 Kang Dec 2001 B1
6327533 Chou Dec 2001 B1
6343217 Borland Jan 2002 B1
6345251 Jansson Feb 2002 B1
6351495 Tarraf Feb 2002 B1
6358145 Wong Mar 2002 B1
6359923 Agee Mar 2002 B1
6362736 Gehlot Mar 2002 B1
6373842 Coverdale Apr 2002 B1
6405033 Kennedy, III Jun 2002 B1
6430176 Christie, IV Aug 2002 B1
6434198 Tarraf Aug 2002 B1
6466582 Venters Oct 2002 B2
6470046 Scott Oct 2002 B1
6477633 Grimmett Nov 2002 B1
6493338 Preston et al. Dec 2002 B1
6516198 Tendler Feb 2003 B1
6519260 Galyas Feb 2003 B1
6522265 Hillman Feb 2003 B1
6526026 Menon Feb 2003 B1
6529744 Birkler Mar 2003 B1
6611804 Dorbecker Aug 2003 B1
6614349 Proctor Sep 2003 B1
6617979 Yoshioka Sep 2003 B2
6628967 Yue Sep 2003 B1
6665333 McCrady Dec 2003 B2
6677894 Sheynblat Jan 2004 B2
6681121 Preston Jan 2004 B1
6683855 Bordogna Jan 2004 B1
6690681 Preston et al. Feb 2004 B1
6690922 Lindemann Feb 2004 B1
6697987 Lee Feb 2004 B2
6700867 Classon Mar 2004 B2
6707421 Drury Mar 2004 B1
6747571 Fierro Jun 2004 B2
6754265 Lindemann Jun 2004 B1
6771629 Preston Aug 2004 B1
6778645 Rao Aug 2004 B1
6799050 Krasner Sep 2004 B1
6836515 Kay Dec 2004 B1
6845153 Tiburtius Jan 2005 B2
6917449 Nakajima Jul 2005 B2
6940809 Sun Sep 2005 B2
6981022 Boundy Dec 2005 B2
6993362 Aberg Jan 2006 B1
7092370 Jiang Aug 2006 B2
7103550 Gallagher Sep 2006 B2
7151768 Preston Dec 2006 B2
7164662 Preston Jan 2007 B2
7206305 Preston Apr 2007 B2
7206574 Bright Apr 2007 B2
7215965 Fournier et al. May 2007 B2
7221669 Preston May 2007 B2
7269188 Smith Sep 2007 B2
7283904 Benjamin Oct 2007 B2
7286522 Preston Oct 2007 B2
7317696 Preston Jan 2008 B2
7372833 Kyronaho May 2008 B2
7398100 Harris Jul 2008 B2
7426466 Ananthapadmanabhan Sep 2008 B2
7430428 Van Bosch Sep 2008 B2
7477906 Radic Jan 2009 B2
7483418 Maurer Jan 2009 B2
7511611 Sabino Mar 2009 B2
7512098 Jiang Mar 2009 B2
7562393 Buddhikot Jul 2009 B2
7583959 Holmes Sep 2009 B2
7593449 Shattil Sep 2009 B2
7606555 Walsh Oct 2009 B2
7653383 Natarajan Jan 2010 B2
7701954 Rabenko Apr 2010 B2
7856240 Gunn Dec 2010 B2
20020111167 Nguyen Aug 2002 A1
20020122401 Xiang Sep 2002 A1
20030016639 Kransmo Jan 2003 A1
20030227939 Yukie Dec 2003 A1
20040034529 Hooper, III Feb 2004 A1
20040192345 Osborn Sep 2004 A1
20050090225 Muehleisen Apr 2005 A1
20050111563 Tseng May 2005 A1
20050147057 LaDue Jul 2005 A1
20050187882 Sovio Aug 2005 A1
20050207511 Madhavan Sep 2005 A1
20050215228 Fostick Sep 2005 A1
20050226202 Zhang Oct 2005 A1
20060171368 Moinzadeh et al. Aug 2006 A1
20060246910 Petermann Nov 2006 A1
20070087756 Hoffberg Apr 2007 A1
20070124625 Hassan May 2007 A1
20070211624 Schmidt Sep 2007 A1
20070258398 Chestnutt Nov 2007 A1
20070264964 Birmingham Nov 2007 A1
20080025295 Elliott Jan 2008 A1
20080039017 Kim Feb 2008 A1
20080056469 Preston Mar 2008 A1
20080107094 Borella May 2008 A1
20080132200 Shinoda Jun 2008 A1
20080143497 Wasson Jun 2008 A1
20080182570 Kuhl Jul 2008 A1
20080212820 Park Sep 2008 A1
20080266064 Curran Oct 2008 A1
20080294340 Schmidt Nov 2008 A1
20090055516 Zhodzishsky Feb 2009 A1
20090110033 Shattil Apr 2009 A1
20090265173 Madhavan Oct 2009 A1
20090298428 Shin Dec 2009 A1
20090306976 Joetten Dec 2009 A1
20100211660 Kiss Aug 2010 A1
Foreign Referenced Citations (48)
Number Date Country
2242495 Jan 2000 CA
4424412 Jan 1996 DE
0242099 Oct 1987 EP
0 528 090 Aug 1991 EP
0 512 789 May 1992 EP
0 501 058 Sep 1992 EP
0512789 Nov 1992 EP
0528090 Feb 1993 EP
0 545 753 Jun 1993 EP
0 545 783 Jun 1993 EP
0545783 Jun 1993 EP
0 580 397 Jan 1994 EP
0 889 610 Jan 1999 EP
0 896 442 Feb 1999 EP
01 950 402 Dec 2004 EP
1 843 503 Oct 2007 EP
2 290 005 May 1994 GB
03232349 Oct 1991 JP
5130008 May 1993 JP
05-207107 Aug 1993 JP
5252099 Sep 1993 JP
6077887 Mar 1994 JP
11109062 Apr 1999 JP
P3044064 Mar 2000 JP
201018163 May 2010 TW
8912835 Dec 1989 WO
WO 9107044 May 1991 WO
9521511 Aug 1995 WO
WO 9607110 Mar 1996 WO
WO 9615636 May 1996 WO
9618275 Jun 1996 WO
WO 9834164 Aug 1998 WO
WO 9834359 Aug 1998 WO
9853573 Nov 1998 WO
WO 9859256 Dec 1998 WO
WO 9859257 Dec 1998 WO
WO 9914885 Mar 1999 WO
WO 9956143 Apr 1999 WO
WO 9956144 Apr 1999 WO
WO 9936795 Jul 1999 WO
9949677 Sep 1999 WO
0011893 Mar 2000 WO
WO 0178249 Oct 2001 WO
WO 0199295 Dec 2001 WO
WO 02054694 Jul 2002 WO
WO 03034235 Apr 2003 WO
WO 03081373 Oct 2003 WO
WO 2009149356 Dec 2009 WO
Related Publications (1)
Number Date Country
20100273470 A1 Oct 2010 US
Provisional Applications (1)
Number Date Country
61173059 Apr 2009 US