Patent Application
20210370957
Many mapping, navigation, and/or other location-based services rely on knowing the speed or velocity of a vehicle. Generally, speed can be measured by or inferred from using Global Positioning System (GPS) data or other equivalent positioning technologies (e.g., other Global Navigation Satellite Systems—GNSS), location technologies such as cellular or Wi-Fi triangulation, and/or by using dedicated speed sensors. However, satellite-based positioning may become unavailable because of signal interference, loss of line-of-sight to orbiting satellites, etc., triangulation methods are generally inaccurate, and dedicated speed sensors may not be available or accessible to portable or mobile devices that execute applications to provide such mapping, navigation, and/or other location-based services. As a result, service providers face significant technical challenges to determine the speed or velocity of a vehicle when traditional speed sensors (e.g., GPS or dedicated speed sensors) are not available.
Therefore, there is a need for an approach for determining vehicle speed and/or other vehicle information using alternative sensor technologies, such as ones that are commonly present, but not limited to, cellular phones.
According to one embodiment, a method comprises determining, by a processor, sensor data from a magnetometer, an accelerometer, or a combination (e.g., via using an inertial measurement unit—IMU) thereof associated with a vehicle (e.g., associated directly with the vehicle or with a mobile device co-located with the vehicle). The method also comprises processing, by the processor, the sensor data to determine a rotational frequency of at least one tire of the vehicle. The method further comprises calculating, by the processor, a speed, a tire/wheel diameter, a safety condition, and/or a maintenance condition of the vehicle based on the rotational frequency. The method further comprises providing, by the processor, the speed, the tire/wheel diameter, the safety condition, and/or the maintenance condition as an output.
According to another embodiment, an apparatus comprises at least one processor, and at least one memory including computer program code for one or more computer programs, the at least one memory and the computer program code configured to, with the at least one processor, cause, at least in part, the apparatus to determine sensor data from a magnetometer, an accelerometer, or a combination (e.g., via an inertial measurement unit—IMU) thereof associated with a vehicle (e.g., associated directly with the vehicle or with a mobile device co-located with the vehicle). The apparatus is also caused to process the sensor data to determine a rotational frequency of at least one tire of the vehicle. The apparatus is further caused to calculate a speed, a tire/wheel diameter, a safety condition, and/or a maintenance condition of the vehicle based on the rotational frequency. The apparatus is further caused to provide the speed, the tire/wheel diameter, the safety condition, and/or the maintenance condition as an output.
According to another embodiment, a computer-readable storage medium carries one or more sequences of one or more instructions which, when executed by one or more processors, cause, at least in part, an apparatus to determine sensor data from a magnetometer, an accelerometer, or a combination (e.g., via an inertial measurement unit—IMU) thereof associated with a vehicle (e.g., associated directly with the vehicle or with a mobile device co-located with the vehicle). The apparatus is also caused to process the sensor data to determine a rotational frequency of at least one tire of the vehicle. The apparatus is further caused to calculate a speed, a tire/wheel diameter, a safety condition, and/or a maintenance condition of the vehicle based on the rotational frequency. The apparatus is further caused to provide the speed, the tire/wheel diameter, the safety condition, and/or the maintenance condition as an output.
According to another embodiment, an apparatus comprises means for determining sensor data from a magnetometer, an accelerometer, or a combination (e.g., via an inertial measurement unit—IMU) thereof associated with a vehicle (e.g., associated directly with the vehicle or with a mobile device co-located with the vehicle). The apparatus also comprises means for processing the sensor data to determine a rotational frequency of at least one tire of the vehicle. The apparatus further comprises means for calculating a speed, a tire/wheel diameter, a safety condition, and/or a maintenance condition of the vehicle based on the rotational frequency. The apparatus further comprises means for providing the speed, the tire/wheel diameter, the safety condition, and/or the maintenance condition as an output.
In addition, for various example embodiments of the invention, the following is applicable: a method comprising facilitating a processing of and/or processing (1) data and/or (2) information and/or (3) at least one signal, the (1) data and/or (2) information and/or (3) at least one signal based, at least in part, on (or derived at least in part from) any one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention.
For various example embodiments of the invention, the following is also applicable: a method comprising facilitating access to at least one interface configured to allow access to at least one service, the at least one service configured to perform any one or any combination of network or service provider methods (or processes) disclosed in this application.
For various example embodiments of the invention, the following is also applicable: a method comprising facilitating creating and/or facilitating modifying (1) at least one device user interface element and/or (2) at least one device user interface functionality, the (1) at least one device user interface element and/or (2) at least one device user interface functionality based, at least in part, on data and/or information resulting from one or any combination of methods or processes disclosed in this application as relevant to any embodiment of the invention, and/or at least one signal resulting from one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention.
For various example embodiments of the invention, the following is also applicable: a method comprising creating and/or modifying (1) at least one device user interface element and/or (2) at least one device user interface functionality, the (1) at least one device user interface element and/or (2) at least one device user interface functionality based at least in part on data and/or information resulting from one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention, and/or at least one signal resulting from one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention.
In various example embodiments, the methods (or processes) can be accomplished on the service provider side or on the mobile device side or in any shared way between service provider and mobile device with actions being performed on both sides.
For various example embodiments, the following is applicable: An apparatus comprising means for performing a method of any of the claims.
Still other aspects, features, and advantages of the invention are readily apparent from the following detailed description, simply by illustrating a number of particular embodiments and implementations, including the best mode contemplated for carrying out the invention. The invention is also capable of other and different embodiments, and its several details can be modified in various obvious respects, all without departing from the spirit and scope of the invention. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive. In particular, “speed” and “velocity” are used and can be used interchangeably along this manuscript.
The embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings:
Examples of a method, apparatus, and computer program for determining vehicle information (e.g., speed, tire/wheel diameter, safety/maintenance condition) are disclosed. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention. It is apparent, however, to one skilled in the art that the embodiments of the invention may be practiced without these specific details or with an equivalent or similar arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the invention.
Generally, modern mobile devices or UEs 105 are equipped with multiple sensing units such as GNSS, IMU, pressure sensors, etc. These sensors allow for determination of position, acceleration, magnetic field, angular rotation rate, and in theory, one can use those measurement to know the exact position, velocity, acceleration, and orientation of the device at any time. However, in practice, knowledge of position, velocity, etc. can be limited by the accuracy of the sensors, and the availability of reliable data.
One such situation is when GNSS data become unavailable (e.g., in tunnels, underground parking) or inaccurate (e.g., nearby high-rise buildings) or sparse (e.g., keep low sampling rate to save on power consumption). In theory, one “just” has to use the last known state (e.g., position and velocity) and integrate once over the acceleration to get the updated velocity and integrate for a second time to get the updated location. In practice, one cannot do it because the measurement error of the accelerometer is such that it induces a very rapid drift in velocity and location estimation. The result is that the trajectory can be estimated only for a few seconds before the error accumulation makes it useless. Moreover, acceleration integration produces only the change in velocity, and if the initial velocity is unknown or inaccurate, the resulting position estimation is even poorer. In addition, one component that is often missing is a sensor (e.g., a dedicated speed sensor) that measures directly the linear velocity of the device (e.g., the UE 105).
Accordingly, in one embodiment, the system 100 can use existing sensing components of the IMU 111 or equivalent (e.g., the magnetometer 107, accelerometer 109, or equivalent) to measure directly the speed (e.g., magnitude of the velocity vector) or other characteristics/information (e.g., tire/wheel diameter, vehicle type, safety/maintenance condition, etc.) of a vehicle 101 or other moving body. Historically, the existing components in IMU 111's or other equivalent sensors are not designed to measure the linear velocity of the device (e.g., 105) or other characteristics of a vehicle 101 associated with the device 105 (e.g., tire/wheel diameter, vehicle type, safety/maintenance condition). Such data or information generally have been detected using sensors designed to directly measure those parameters. However, in one embodiment (e.g., in a vehicle setting where the UE 105 is mounted in or otherwise associated with the vehicle 101), the sensor data (e.g., the power spectrum) of the magnetometer 107 and/or accelerometer 109 contain information which is related to the vehicle 101's speed (velocity magnitude) or other vehicle information so that the speed or other vehicle information can be calculated or derived from the sensor data.
For example, in one embodiment, the magnetometer 107 is sensitive to changes in the magnetic field. In most cases, the tires 113a-113n (also collectively referred to as tires 113) of the vehicle 101 are steel-belted radial tires that tend to be magnetized. The net effect is that tires 113 behave as rotating magnets. The rotational frequency can be measured with the magnetometer 107 as magnetic signals 115. The system 100 (e.g., via a speed module 117 local to the UE and/or via a speed platform 119 on the network side) can then process sensor data to calculate the speed from the rotational frequency to generate speed/vehicle data 121 for the vehicle 101. The speed/vehicle data 121 represents, for instance, one or more speed measurements determined according to the embodiments described herein.
In another example embodiment, the accelerometer 109 can also be used alone or in combination with the magnetometer to determine rotational frequency of the tires 113 of the vehicle 101. For example, vehicle tires 113 generally have some level of imbalance. At high speeds, even a tiny imbalance in weight can become a large imbalance in centrifugal force, causing the wheel/tire assembly to spin with a kind of “galumphing” motion. This usually translates into a vibration in the vehicle 101 as well as irregular and damaging wear on the tires 113. This galumphing motion has the same frequency as the tire rotation and is captured by the accelerometer 109 as vibrational signals 115. As described above, the rotational frequency determined from the vibrational signals 115 can then be used to generate speed/vehicle data 121 for the vehicle 101.
It is noted that the magnetometer 107 and/or accelerometer 109 discussed with respect to the embodiments described herein are provided by way of illustration and not as limitations. It is contemplated that any other type of sensor (e.g., other than dedicated speed sensors or GNSS/GPS) that can provide surrogate information for deriving speed can be used. For example, microphones or other acoustic sensors can be used to record tire sounds resulting from “galumphing” motion of imbalanced tires 113 can be processed to determine rotational frequency and ultimately speed.
In summary, location and velocity information traditionally can be obtained in a few ways:
Under certain scenarios, there are additional technical challenges associated with using the magnetometer 107 and/or accelerometer 109 for speed measurements according to the embodiments described herein. These include but are not limited to:
To address these additional challenges, in some embodiment, the system 100 can apply additional signal processing for signal cleanup, remove background signals, apply filtering, and/or the like. These additional embodiments are described in more detail further below.
In one embodiment, the various embodiments described herein opens the way for much more accurate navigation and/or other location-based services by providing speed or other vehicle data 121 (e.g., information derived from sensors not normally used for the purpose of speed detection but generally available in most modern phones and mobile devices), especially when GNSS data is unavailable or sparse. For example, the speed/vehicle data 121 can be provided by the system 100 as an output over a communications network 123 to a service platform 125 including one or more services 127a-127k (also referred to as services 127). As discussed above, the services 127 can include, but are not limited to, mapping services, navigation services, and/or the like that can combine the speed/vehicle data 121 with digital map data (e.g., a geographic database 131) to provide location-based services. It is also contemplated that the services 127 can include any service that uses the speed/vehicle data 121 to provide or perform any function. In one embodiment, the speed/vehicle data output 121 can also be used by one or more content providers 129a-129j (also collectively referred to as content providers 129). These content providers 129 can aggregate and/or process the speed/vehicle data 121 to provide the processed data to its users such as the service platform 125 and/or services 127.
As discussed above, existing components (e.g., magnetometers 107, accelerometers 109, etc.) in traditional IMU 111's are not designed to measure the linear velocity of the device (e.g., a UE 105 in which the IMU 111 is installed) or other characteristics of a vehicle 101 associated with the device (e.g., tire/wheel diameter, vehicle type, safety/maintenance condition, etc.). In one embodiment, the process 300 provides a practical approach for measuring vehicle velocity and/or other vehicle information (e.g., tire/wheel diameter, vehicle type, safety/maintenance condition, etc.) using the magnetometer 107 and/or accelerometer 109 components of the IMU 111, taking advantage of mechanical and material properties of the tires 113 of the vehicle 101.
For example, in step 301, the data ingestion module 201 determines sensor data 103 from a magnetometer 107, an accelerometer 109, or a combination thereof (or from equivalent sensors) associated with a vehicle 101. The sensor data 103, for instance, include measurements of signals 115 representing changes in the magnetic field (e.g., magnetic measurements), acceleration, and/or mechanical/vibrational oscillations of the vehicle 101 caused by the rotation of the tires 113 of the vehicle 101. In one embodiment, the magnetometer 107, accelerometer 109, and/or equivalent sensors can be installed within a mobile device or smartphone (e.g., a UE 105) mounted or otherwise traveling within the vehicle 101. For example, the UE 105 can be mounted to the dashboard or other fixed position within the vehicle 101 or carried by a driver/passenger of the vehicle 101. The sensors can be standalone sensors within the UE 105 or part of an IMU 111 within the UE 105. It is noted, however, that embodiments in which the sensors are included within the UE 105 are provided by way of illustration and not as a limitation. In other embodiments, it is contemplated that the sensors (e.g., the magnetometer 107 and/or accelerometer 109) may be mounted externally to the UE 105 (e.g., as a component of the vehicle 101 or other device within the vehicle 101). In addition, the speed module 117 for calculating the speed or other characteristic/information of the vehicle 101 according to the embodiments described herein need not reside within the UE 105 and can also be included as a component of the vehicle 101 and/or any other device internal or external to the vehicle 101.
As discussed above, in one embodiment, the sensor data 103 includes magnetic measurements or magnetic signals from the tires 113 of the vehicle 101. Generally, the most prevalent car tire technology has been steel-belted radial tires (SBRT). The steel, for instance, is used to improve the strength and reduce wearing of the tires 113. In addition, SBRT usually have some degree of non-uniform magnetization that is the result of the manufacturing process. The net result is that the tires 113 can act as weak magnets, and tire rotation induces a time dependent magnetic field whose frequency (e.g., rotational frequency) is directly proportional to the speed of the vehicle 101. This relationship is illustrated in the following speed/frequency relationship equation:
s=|{right arrow over (v)}|=πdf
tire
where, s is the speed, v is the vehicle velocity, d is the tire diameter, and ftire is the rotational frequency of the tire.
Accordingly, in step 303, the signal processing module 203 can process the sensor data 103 (e.g., determined according to step 301 or equivalent) to determine a rotational frequency of at least one tire 113 of the vehicle 101. In one embodiment, signal processing module 203 can determine the rotational frequency from the magnetic and/or acceleration/vibrational signals 115.
According to an embodiment of using magnetic signals 115, the signal processing module 203 determines a magnetic signal 115 from the sensor data 103 from the magnetometer 107. Then, the rotational frequency (e.g., of the tire 113) is determined based on the magnetic signal 115. The magnetic signal 115, for instance, represents one or more changes in a magnetic field (e.g., as described below with respect to
In one embodiment, the signal processing module 203 can process the magnetic signal 115 of the sensor data 103 to determine the power spectral density of magnetic field changes of the tires 113 over time. This power spectral density over time can be represented using a spectrogram as shown in
For comparison, direct speed data measured for the vehicle 101 (e.g., using GNSS) over the same time period is presented in the velocity graph 521 of
While multiple tires 113 of the vehicle 101 generally will have the same rotational frequency, there can be situations where the tires 113 are rotating at different frequencies (e.g., failure or malfunctioning of an axle, differential, or other component of the vehicle 101). Under this possible scenario, multiple ridgelines over the same time period may be apparent (not the case in the examples of
The embodiments described herein take advantage of surrogate magnetic signal data to measure vehicle velocity, but under some scenarios, these magnetic signals 115 can be obscured or suffer from interference. Therefore, there are additional technical challenges associated with getting a clean measurement of the power spectrum and identifying the right peak among many that are present.
In one embodiment, the signal processing module 203 can apply one or more optional signal processing or preprocessing procedures. In the description below, it is assumed that the mobile device (e.g., UE 105) collecting the sensor data 103 is fixed and stationary within the vehicle 101 to reduce potential interference or noise in the signal data. However, it is also contemplated that the embodiments described herein are also applicable when the UE 105 is not in a fixed location (e.g., held by a driver or passenger, placed on a surface in the vehicle without mounting, etc.). In the case of the non-fixed mounting of the UE 105, the signal processing module 203 can apply more preprocessing steps to reduce noise or error in the signals. Examples of the various signal processing or preprocessing steps of the magnetic signal 115 can include but are not limited to the various embodiments described below.
In one embodiment, the magnetic signal processing can include signal cleanup (e.g., median filter, low-pass, etc.). For example, the signal processing module 203 can apply different filters or equivalent processes/algorithms to remove noise, detect outliers, etc. from the magnetic signal 115 of the sensor data 103 to improve data quality.
In one embodiment, the magnetic signal processing module 203 can perform additional processing options such as but not limited to:
In some scenarios, the magnetic signal 115 picked up in the sensor data 103 can be susceptible to interference from other magnetic and/or electrical fields in the vehicle 101 itself. The magnetic background in the vehicle 101 can then be assessed. Accordingly, in one embodiment, the signal processing module 203 can optionally measure of the magnetic background in or near the vehicle 101. The signal processing module 203 can then subtract or otherwise account for the magnetic background when processing the sensor data 103.
In one embodiment, the signal processing module 203 can also identify peaks in the power spectrum of the measured magnetic energy density. As described above, the peaks represent the likely rotational frequency of the tires 113 of the vehicle 101 based on the detected magnetic energy densities. The identification of the peaks can be based on distinguishing the peak from background noise in the magnetic signal 115. For example, the signal processing module 203 can apply criteria such as identifying only those peaks that are statistically different from the background noise (e.g., peak height greater than n standard deviations from the background noise level).
In yet another embodiment, the signal processing module 203 can apply various filtering criteria for selecting the peak or peaks that correspond to the rotational frequency of the tires 113 of the vehicle 101. By way of example, the processing of the sensor data 103 can include or otherwise be based on at least one of the following criteria or processes:
In one embodiment, the sensor data 103 and signal 115 can represent a mechanical measurement (e.g., measurement of the accelerations/vibrations of the vehicle 101) indicative of rotational frequency of the tires. Accordingly, in one embodiment of the step 303 of the process 300, the signal processing module 203 determine a vibrational signal 115 from the sensor data 103 of the accelerometer 109. The rotational frequency can then be determined based on the vibrational signal 115 alone or in combination with the magnetic signal 115 described in the embodiments above.
As previously described, vehicle tires 113 generally have some level of unbalancing. At high speeds, a tiny imbalance in weight can easily become a large imbalance in centrifugal force, causing the wheel/tire assembly to spin with a kind of “galumphing” motion. This usually translates into a vibration in the vehicle 101 as well as some very irregular and damaging wear on the tires 113. This galumphing motion has the same rotational frequency as the tire rotation and is captured by the accelerometer 109, mainly at high velocities. In one embodiment, to determine the rotational frequency of the tires 113, the signal processing module 203 can generate a power spectrum of the vibrational signal 115 (e.g., according to an analogous process as described in the embodiments that process the magnetic signal 115), and identify one or more peaks of the power spectrum. The rotational frequency can then be determined based on the one or more peaks.
In one embodiment, the power spectrum is represented as an accelerometer spectrogram.
As with the magnetic signal 115, the vibrational signals 115 can also be obscured or suffer from interference. Therefore, there are additional technical challenges associated with getting a clean measurement of the vibrational power spectrum and identifying the right peak among many that are present.
In one embodiment, the signal processing module 203 can apply one or more optional signal processing or preprocessing procedures to the vibrational signal 115. Examples of the various signal processing or preprocessing steps of the magnetic signal 115 can include but are not limited to the various embodiments described below.
In one embodiment, the magnetic signal processing can include signal cleanup (e.g., median filter, low-pass, etc.). For example, the signal processing module 203 can apply different filters or equivalent processes/algorithms to remove noise, detect outliers, etc. from the magnetic signal 115 of the sensor data 103 to improve data quality. In another embodiment, the signal processing module 203 can also calculate an energy time series of the vibrational spectrogram over time. For example, the vibrational signal data 115 can be broken into a series of chunks of a time domain and then the resulting rotational frequencies (e.g., based on energy densities) can be compared over the chunks to determine signal changes over time.
In some scenarios, the acceleration/vibrational signal 115 picked up in the sensor data 103 can be susceptible to interference from other accelerations/vibrations in the vehicle 101 not caused by tire imbalance. The vibrational background in the vehicle 101 can then be assessed. Accordingly, in one embodiment, the signal processing module 203 can optionally measure of the vibrational background in or near the vehicle 101. The signal processing module 203 can then subtract or otherwise account for the vibrational background when processing the sensor data 103.
In one embodiment, the signal processing module 203 can also identify peaks in the power spectrum of the measured magnetic energy density. As described above, the peaks represent the likely rotational frequency of the tires 113 of the vehicle 101 based on the detected magnetic energy densities. The identification of the peaks can be based on distinguishing the peak from background noise in the magnetic signal 115. For example, the signal processing module 203 can apply criteria such as identifying only those peaks that are statistically different from the background noise (e.g., peak height greater than n standard deviations from the background noise level).
In yet another embodiment, the signal processing module 203 can apply various filtering criteria for selecting the peak or peaks of the vibrational signal 115 that correspond to the rotational frequency of the tires 113 of the vehicle 101. By way of example, the processing of the sensor data 103 can include or otherwise be based on at least one of the following criteria or processes:
In step 305, after determining the rotational frequency of the tires 113 of a vehicle 101 according to the embodiments described with respect to step 303, the data calculation module 205 can calculate a speed of the vehicle based on the rotational frequency. In one embodiment, the speed can be calculated according to the speed/frequency relationship equation described above and presented again below:
s=|{right arrow over (v)}|=πdf
tire
where, s is the speed, v is the vehicle velocity, d is the tire diameter, and ftire is the rotational frequency of the tire. In this case, ftire is determined according to the embodiments described above. The data calculation module 205 can then determine the diameter of the at least one tire 113 of the vehicle 101 for which the speed is being calculated, so that the speed can be calculated further based on the diameter. The data calculation module 205, for instance, can determine the diameter based on specification data associated with the make and model of the vehicle 101, based on user input, based on reading the diameter from the tires 113, and/or any other equivalent means. In one embodiment, when the actual diameter of the tires 113 is not known or otherwise available, the data calculation module 205 can use a default tire diameter value to approximate the true diameter.
In one embodiment, if the speed s is known (e.g., a speed determined from available GNSS measurements or other available speed sensors) and the tire diameter d is not known, the data calculation module 205 can instead calculate the diameter d of at least one tire 113 of the vehicle 103 based on the rotational frequency. The calculation, for instance, can be based on the following equation:
wherein, d is the tire diameter, s is the speed and ftire is the rotational frequency of the tire.
In one embodiment, the data calculation module 205 can used the determined the calculated tire diameter d to classify or infer the type of vehicle 101 from which the sensor data was collected. The data calculation module 205, for instance, can classify the vehicle type based on a range of tire diameter values associated with each vehicle type. Table 1 below illustrates example ranges for classifying different types of vehicles based on tire diameter d sizes. As shown, if a calculated tire diameter d for a vehicle of interest falls within the range specified for a given vehicle type, the vehicle of interest can be classified as the corresponding vehicle type.
It is noted that the above example of classifying a vehicle type based on a calculated tire diameter d is provided by way of illustration and is not intended as a limitation. It is contemplated that the data calculation module 205 can use any means to determine a vehicle type based on the tire diameter d as an input (e.g., machine learning algorithms or other predictive models).
In another embodiment, the data calculation module 205 can calculate a safety condition, maintenance condition, or a combination thereof of the vehicle 101 based on the rotational frequency and/or the speed/vehicle information derived therefrom. By way of example, a safety condition refers to any condition of the vehicle 101 that can cause to operation of the vehicle to fall outside of manufacturer specified safety parameters, and a maintenance condition refers to any condition of the vehicle 101 that can indicate a need for repair or service. In one embodiment, the data calculation module 205 can determine whether the tires 113 of the vehicle 101 are rotating at different frequencies. As described above, tires 113 that are rotating at different frequencies can be identified based on the appearance of multiple ridgelines in a power spectrum of the magnetic/acceleration/vibrational signals 113 of the sensor data 103. Accordingly, the data calculation module 205 can apply threshold ranges for determining when detected rotational differences between the tires 113 a maintenance condition and/or a safety condition. For example, the threshold rotational difference for a safety condition can be set higher than a maintenance condition, so that repairs or service can be performed before the condition escalates from a maintenance condition (e.g., a vehicle 101 can still be operated but service should be performed) to a safety condition (e.g., a vehicle 101 should not be operated until service/repairs are performed).
In one embodiment, the data calculation module 205 can process sensor data, determined rotational frequencies, and/or other derived values (e.g., speed, tire diameter, etc.) to identify a more specific issue creating the determined safety/maintenance condition. For example, the detected safety/maintenance conditions can include but are not limited to a wheel balancing, a low air pressure, and/or other general anomaly of the vehicle 101. To detect a wheel balancing issue that rises to a safety/maintenance condition, the data calculation module 205 can determine whether the detected vibrational signal 115 is above a threshold value or has increased beyond the threshold value over time. As another example, a detected change (e.g., a decrease) in the diameter of a tire 113 over time by more than a threshold value can indicate a low air pressure condition of a tire 113. As a more general embodiment, the data calculation module 205 can monitor the rotational frequencies, signals 115, and/or any corresponding derived values (e.g., speed, tire diameter, vehicle type, etc.) over a time and/or frequency domain. If the monitored values change by more than a threshold value over the monitoring period, the data calculation module can identify that there is a safety/maintenance condition.
In step 307, the output module 207 can provide the speed or other vehicle information (e.g., tire diameter, vehicle type, safety/maintenance condition, etc.) of the vehicle 101 as an output. The output, for instance, can be provided or transmitted to any service, application, function, component, system, device, or equivalent that requests the speed/vehicle data 121. For example, the speed/vehicle data output can be provided to the service platform 125, any of the services 127, any of the content providers 129, and/or the like.
In one embodiment, the speed platform 119 can output the tire diameter and/or vehicle type determined from the rotational frequency of the IMU sensor data 103 for applications or services 127 in which determining vehicle class or type is used. For instance, a safety application or service 127 can use the vehicle type data to make sure that a passenger took the right ride-sharing vehicle or taxi. In this case, the service 127 can assume that the vehicle type of the correct vehicle has a known or expected tire diameter or vehicle type. The service 127 can then match the expected tire diameter or vehicle type with the measure value to confirm whether the passenger is in the correct vehicle.
In another embodiment, the safety application or service 127 can also provide warnings to passengers of potential maintenance issues in the vehicles in which they are riding. When a passenger boards a vehicle (e.g., ride-sharing vehicle or taxi), the service 127 can begin detecting potential safety/maintenance issues (e.g., wheel imbalance, low air pressure, other anomalies) with the vehicle according to the embodiments described herein. If a safety/maintenance condition is detected, then a warning message can be presented.
Returning to
The UEs 105 and/or vehicles 101 may be configured with multiple sensors of different types for acquiring and/or generating sensor data according to the embodiments described herein. For example, sensors may be used as GPS or other positioning receivers for interacting with one or more location satellites to determine and track the current speed, position and location of a vehicle travelling along a roadway. In addition, the sensors may gather IMU data, NFC data, Bluetooth data, acoustic data, barometric data, tilt data (e.g., a degree of incline or decline of the vehicle during travel), motion data, light data, sound data, image data, weather data, temporal data and other data associated with the vehicle and/or UEs 105 thereof. Still further, the sensors may detect local or transient network and/or wireless signals, such as those transmitted by nearby devices during navigation of a vehicle along a roadway. This may include, for example, network routers configured within a premise (e.g., home or business), another UE 105 or vehicle 101 or a communicable traffic system (e.g., traffic lights, traffic cameras, traffic signals, digital signage).
By way of example, the speed module 117 and/or speed platform 119 may be implemented as a cloud-based service, hosted solution or the like for performing the above described functions. Alternatively, the speed module 117 and/or speed platform 119 may be directly integrated for processing data generated and/or provided by the service platform 125, one or more services 127, and/or content providers 129. Per this integration, the speed platform 119 may perform client-side state computation of vehicle speed data.
By way of example, the communications network 123 of system 100 includes one or more networks such as a data network, a wireless network, a telephony network, or any combination thereof. It is contemplated that the data network may be any local area network (LAN), metropolitan area network (MAN), wide area network (WAN), a public data network (e.g., the Internet), short range wireless network, or any other suitable packet-switched network, such as a commercially owned, proprietary packet-switched network, e.g., a proprietary cable or fiber-optic network, and the like, or any combination thereof. In addition, the wireless network may be, for example, a cellular network and may employ various technologies including enhanced data rates for global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (UMTS), etc., as well as any other suitable wireless medium, e.g., worldwide interoperability for microwave access (WiMAX), Long Term Evolution (LTE) networks, code division multiple access (CDMA), wideband code division multiple access (WCDMA), wireless fidelity (WiFi), wireless LAN (WLAN), Bluetooth®, Internet Protocol (IP) data casting, satellite, mobile ad-hoc network (MANET), and the like, or any combination thereof.
A UE 105 is any type of mobile terminal, fixed terminal, or portable terminal including a mobile handset, station, unit, device, multimedia computer, multimedia tablet, Internet node, communicator, desktop computer, laptop computer, notebook computer, netbook computer, tablet computer, personal communication system (PCS) device, personal navigation device, personal digital assistants (PDAs), audio/video player, digital camera/camcorder, positioning device, television receiver, radio broadcast receiver, electronic book device, game device, or any combination thereof, including the accessories and peripherals of these devices, or any combination thereof. It is also contemplated that a UE 105 can support any type of interface to the user (such as “wearable” circuitry, etc.).
By way of example, the UE 105s, the speed module 117/speed platform 119, the service platform 125, and the content providers 129 communicate with each other and other components of the communications network 123 using well known, new or still developing protocols. In this context, a protocol includes a set of rules defining how the network nodes within the communications network 123 interact with each other based on information sent over the communication links. The protocols are effective at different layers of operation within each node, from generating and receiving physical signals of various types, to selecting a link for transferring those signals, to the format of information indicated by those signals, to identifying which software application executing on a computer system sends or receives the information. The conceptually different layers of protocols for exchanging information over a network are described in the Open Systems Interconnection (OSI) Reference Model.
Communications between the network nodes are typically effected by exchanging discrete packets of data. Each packet typically comprises (1) header information associated with a particular protocol, and (2) payload information that follows the header information and contains information that may be processed independently of that particular protocol. In some protocols, the packet includes (3) trailer information following the payload and indicating the end of the payload information. The header includes information such as the source of the packet, its destination, the length of the payload, and other properties used by the protocol. Often, the data in the payload for the particular protocol includes a header and payload for a different protocol associated with a different, higher layer of the OSI Reference Model. The header for a particular protocol typically indicates a type for the next protocol contained in its payload. The higher layer protocol is said to be encapsulated in the lower layer protocol. The headers included in a packet traversing multiple heterogeneous networks, such as the Internet, typically include a physical (layer 1) header, a data-link (layer 2) header, an internetwork (layer 3) header and a transport (layer 4) header, and various application (layer 5, layer 6 and layer 7) headers as defined by the OSI Reference Model.
In one embodiment, geographic features (e.g., two-dimensional or three-dimensional features) are represented using polylines and/or polygons (e.g., two-dimensional features) or polygon extrusions (e.g., three-dimensional features). In one embodiment, these polylines/polygons can also represent ground truth or reference features or objects (e.g., signs, road markings, lane lines, landmarks, etc.) used for visual odometry. For example, the polylines or polygons can correspond to the boundaries or edges of the respective geographic features. In the case of a building, a two-dimensional polygon can be used to represent a footprint of the building, and a three-dimensional polygon extrusion can be used to represent the three-dimensional surfaces of the building. Accordingly, the terms polygons and polygon extrusions as used herein can be used interchangeably.
In one embodiment, the following terminology applies to the representation of geographic features in the geographic database 131.
“Node”—A point that terminates a link.
“Line segment”—A straight line connecting two points.
“Link” (or “edge”) —A contiguous, non-branching string of one or more line segments terminating in a node at each end.
“Shape point”—A point along a link between two nodes (e.g., used to alter a shape of the link without defining new nodes).
“Oriented link”—A link that has a starting node (referred to as the “reference node”) and an ending node (referred to as the “non reference node”).
“Simple polygon”—An interior area of an outer boundary formed by a string of oriented links that begins and ends in one node. In one embodiment, a simple polygon does not cross itself.
“Polygon”—An area bounded by an outer boundary and none or at least one interior boundary (e.g., a hole or island). In one embodiment, a polygon is constructed from one outer simple polygon and none or at least one inner simple polygon. A polygon is simple if it just consists of one simple polygon, or complex if it has at least one inner simple polygon.
In one embodiment, the geographic database 131 follows certain conventions. For example, links do not cross themselves and do not cross each other except at a node. Also, there are no duplicated shape points, nodes, or links. Two links that connect each other have a common node. In the geographic database 131, overlapping geographic features are represented by overlapping polygons. When polygons overlap, the boundary of one polygon crosses the boundary of the other polygon. In the geographic database 131, the location at which the boundary of one polygon intersects they boundary of another polygon is represented by a node. In one embodiment, a node may be used to represent other locations along the boundary of a polygon than a location at which the boundary of the polygon intersects the boundary of another polygon. In one embodiment, a shape point is not used to represent a point at which the boundary of a polygon intersects the boundary of another polygon.
As shown, the geographic database 131 includes node data records 803, road segment or link data records 805, POI data records 807, vehicle speed data records 809, HD mapping data records 811, and indexes 813, for example. More, fewer or different data records can be provided. In one embodiment, additional data records (not shown) can include cartographic (“carto”) data records, routing data, and maneuver data. In one embodiment, the indexes 813 may improve the speed of data retrieval operations in the geographic database 131. In one embodiment, the indexes 813 may be used to quickly locate data without having to search every row in the geographic database 131 every time it is accessed. For example, in one embodiment, the indexes 813 can be a spatial index of the polygon points associated with stored feature polygons.
In exemplary embodiments, the road segment data records 805 are links or segments representing roads, streets, or paths, as can be used in the calculated route or recorded route information for determination of one or more personalized routes. The node data records 803 are end points corresponding to the respective links or segments of the road segment data records 805. The road link data records 805 and the node data records 803 represent a road network, such as used by vehicles, cars, and/or other entities. Alternatively, the geographic database 131 can contain path segment and node data records or other data that represent pedestrian paths or areas in addition to or instead of the vehicle road record data, for example. In one embodiment, the nodes and links can make up the base map and that base map can be associated with an HD layer including more detailed information, like lane level details for each road segment or link and how those lanes connect via intersections. Furthermore, another layer may also be provided, such as an HD live map, where road objects are provided in detail in regard to positioning, which can be used for localization. The HD layers can be arranged in a tile format.
The road/link segments and nodes can be associated with attributes, such as geographic coordinates, street names, address ranges, speed limits, turn restrictions at intersections, and other navigation related attributes, as well as POIs, such as gasoline stations, hotels, restaurants, museums, stadiums, offices, automobile dealerships, auto repair shops, buildings, stores, parks, etc. The geographic database 131 can include data about the POIs and their respective locations in the POI data records 807. The geographic database 131 can also include data about places, such as cities, towns, or other communities, and other geographic features, such as bodies of water, mountain ranges, etc. Such place or feature data can be part of the POI data records 807 or can be associated with POIs or POI data records 807 (such as a data point used for displaying or representing a position of a city).
In one embodiment, the geographic database 131 can also include vehicle speed data records 809 for storing speed data determined from IMU sensor data 103 according to the embodiments described herein. The vehicle speed data records 809 can also store related data including but not limited to sensor data 103, magnetic/vibrational signal data, spectrograms, determine rotational frequencies, and/or any other data used or generated according to the embodiments described herein. By way of example, the vehicle speed data records 809 can be associated with one or more of the node records 803, road segment records 805, and/or POI data records 807 to associate the determined vehicle speed data with specific geographic areas or features.
In one embodiment, as discussed above, the HD mapping data records 811 model road surfaces and other map features to centimeter-level or better accuracy (e.g., including centimeter-level accuracy for ground truth objects used for visual odometry based on polyline homogeneity according to the embodiments described herein). The HD mapping data records 811 also include ground truth object models that provide the precise object geometry with polylines or polygonal boundaries, as well as rich attributes of the models. These rich attributes include, but are not limited to, object type, object location, lane traversal information, lane types, lane marking types, lane level speed limit information, and/or the like. In one embodiment, the HD mapping data records 811 are divided into spatial partitions of varying sizes to provide HD mapping data to end user devices with near real-time speed without overloading the available resources of the devices (e.g., computational, memory, bandwidth, etc. resources).
In one embodiment, the HD mapping data records 811 are created from high-resolution 3D mesh or point-cloud data generated, for instance, from LiDAR-equipped vehicles. The 3D mesh or point-cloud data are processed to create 3D representations of a street or geographic environment at centimeter-level accuracy for storage in the HD mapping data records 811.
In one embodiment, the HD mapping data records 811 also include real-time sensor data collected from probe vehicles in the field. The real-time sensor data, for instance, integrates real-time traffic information, weather, and road conditions (e.g., potholes, road friction, road wear, etc.) with highly detailed 3D representations of street and geographic features to provide precise real-time data (e.g., including probe trajectories) also at centimeter-level accuracy. Other sensor data can include vehicle telemetry or operational data such as windshield wiper activation state, braking state, steering angle, accelerator position, and/or the like. The HD mapping data records may be provided as a separate map layer.
In one embodiment, the geographic database 131 can be maintained by the content provider 129 in association with the services platform 117 (e.g., a map developer). The map developer can collect geographic data to generate and enhance the geographic database 131. There can be different ways used by the map developer to collect data. These ways can include obtaining data from other sources, such as municipalities or respective geographic authorities. In addition, the map developer can employ field personnel to travel by vehicle along roads throughout the geographic region to observe features and/or record information about them, for example. Also, remote sensing, such as aerial or satellite photography, can be used.
The geographic database 131 can be a master geographic database stored in a format that facilitates updating, maintenance, and development. For example, the master geographic database or data in the master geographic database can be in an Oracle spatial format or other spatial format, such as for development or production purposes. The Oracle spatial format or development/production database can be compiled into a delivery format, such as a geographic data files (GDF) format. Other formats including tile structures for different map layers may be used for different delivery techniques. The data in the production and/or delivery formats can be compiled or further compiled to form geographic database products or databases, which can be used in end user navigation devices or systems.
For example, geographic data is compiled (such as into a platform specification format (PSF)) to organize and/or configure the data for performing navigation-related functions and/or services, such as route calculation, route guidance, map display, speed calculation, distance and travel time functions, and other functions, by a navigation device, such as by a vehicle 101 and/or UE 105. The navigation-related functions can correspond to vehicle navigation, pedestrian navigation, or other types of navigation. The compilation to produce the end user databases can be performed by a party or entity separate from the map developer. For example, a customer of the map developer, such as a navigation device developer or other end user device developer, can perform compilation on a received geographic database in a delivery format to produce one or more compiled navigation databases.
The processes described herein for determining vehicle speed based on IMU sensor data 103 may be advantageously implemented via software, hardware (e.g., general processor, Digital Signal Processing (DSP) chip, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Arrays (FPGAs), etc.), firmware or a combination thereof. Such exemplary hardware for performing the described functions is detailed below.
A bus 910 includes one or more parallel conductors of information so that information is transferred quickly among devices coupled to the bus 910. One or more processors 902 for processing information are coupled with the bus 910.
A processor 902 performs a set of operations on information as specified by computer program code related to determining vehicle speed based on IMU sensor data 103. The computer program code is a set of instructions or statements providing instructions for the operation of the processor and/or the computer system to perform specified functions. The code, for example, may be written in a computer programming language that is compiled into a native instruction set of the processor. The code may also be written directly using the native instruction set (e.g., machine language). The set of operations include bringing information in from the bus 910 and placing information on the bus 910. The set of operations also typically include comparing two or more units of information, shifting positions of units of information, and combining two or more units of information, such as by addition or multiplication or logical operations like OR, exclusive OR (XOR), and AND. Each operation of the set of operations that can be performed by the processor is represented to the processor by information called instructions, such as an operation code of one or more digits. A sequence of operations to be executed by the processor 902, such as a sequence of operation codes, constitute processor instructions, also called computer system instructions or, simply, computer instructions. Processors may be implemented as mechanical, electrical, magnetic, optical, chemical or quantum components, among others, alone or in combination.
Computer system 900 also includes a memory 904 coupled to bus 910. The memory 904, such as a random access memory (RAM) or other dynamic storage device, stores information including processor instructions for determining vehicle speed based on IMU sensor data 103. Dynamic memory allows information stored therein to be changed by the computer system 900. RAM allows a unit of information stored at a location called a memory address to be stored and retrieved independently of information at neighboring addresses. The memory 904 is also used by the processor 902 to store temporary values during execution of processor instructions. The computer system 900 also includes a read only memory (ROM) 906 or other static storage device coupled to the bus 910 for storing static information, including instructions, that is not changed by the computer system 900. Some memory is composed of volatile storage that loses the information stored thereon when power is lost. Also coupled to bus 910 is a non-volatile (persistent) storage device 908, such as a magnetic disk, optical disk or flash card, for storing information, including instructions, that persists even when the computer system 900 is turned off or otherwise loses power.
Information, including instructions for determining vehicle speed based on IMU sensor data 103, is provided to the bus 910 for use by the processor from an external input device 912, such as a keyboard containing alphanumeric keys operated by a human user, or a sensor. A sensor detects conditions in its vicinity and transforms those detections into physical expression compatible with the measurable phenomenon used to represent information in computer system 900. Other external devices coupled to bus 910, used primarily for interacting with humans, include a display device 914, such as a cathode ray tube (CRT) or a liquid crystal display (LCD), or plasma screen or printer for presenting text or images, and a pointing device 916, such as a mouse or a trackball or cursor direction keys, or motion sensor, for controlling a position of a small cursor image presented on the display 914 and issuing commands associated with graphical elements presented on the display 914. In some embodiments, for example, in embodiments in which the computer system 900 performs all functions automatically without human input, one or more of external input device 912, display device 914 and pointing device 916 is omitted.
In the illustrated embodiment, special purpose hardware, such as an application specific integrated circuit (ASIC) 920, is coupled to bus 910. The special purpose hardware is configured to perform operations not performed by processor 902 quickly enough for special purposes. Examples of application specific ICs include graphics accelerator cards for generating images for display 914, cryptographic boards for encrypting and decrypting messages sent over a network, speech recognition, and interfaces to special external devices, such as robotic arms and medical scanning equipment that repeatedly perform some complex sequence of operations that are more efficiently implemented in hardware.
Computer system 900 also includes one or more instances of a communications interface 970 coupled to bus 910. Communication interface 970 provides a one-way or two-way communication coupling to a variety of external devices that operate with their own processors, such as printers, scanners and external disks. In general the coupling is with a network link 978 that is connected to a local network 980 to which a variety of external devices with their own processors are connected. For example, communication interface 970 may be a parallel port or a serial port or a universal serial bus (USB) port on a personal computer. In some embodiments, communications interface 970 is an integrated services digital network (ISDN) card or a digital subscriber line (DSL) card or a telephone modem that provides an information communication connection to a corresponding type of telephone line. In some embodiments, a communication interface 970 is a cable modem that converts signals on bus 910 into signals for a communication connection over a coaxial cable or into optical signals for a communication connection over a fiber optic cable. As another example, communications interface 970 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN, such as Ethernet. Wireless links may also be implemented. For wireless links, the communications interface 970 sends or receives or both sends and receives electrical, acoustic or electromagnetic signals, including infrared and optical signals, that carry information streams, such as digital data. For example, in wireless handheld devices, such as mobile telephones like cell phones, the communications interface 970 includes a radio band electromagnetic transmitter and receiver called a radio transceiver. In certain embodiments, the communications interface 970 enables connection to the communication network 123 for determining vehicle speed based on IMU sensor data 103.
The term computer-readable medium is used herein to refer to any medium that participates in providing information to processor 902, including instructions for execution. Such a medium may take many forms, including, but not limited to, non-volatile media, volatile media and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as storage device 908. Volatile media include, for example, dynamic memory 904. Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and carrier waves that travel through space without wires or cables, such as acoustic waves and electromagnetic waves, including radio, optical and infrared waves. Signals include man-made transient variations in amplitude, frequency, phase, polarization or other physical properties transmitted through the transmission media. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, CDRW, DVD, any other optical medium, punch cards, paper tape, optical mark sheets, any other physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read.
Network link 978 typically provides information communication using transmission media through one or more networks to other devices that use or process the information. For example, network link 978 may provide a connection through local network 980 to a host computer 982 or to equipment 984 operated by an Internet Service Provider (ISP). ISP equipment 984 in turn provides data communication services through the public, world-wide packet-switching communication network of networks now commonly referred to as the Internet 990.
A computer called a server host 992 connected to the Internet hosts a process that provides a service in response to information received over the Internet. For example, server host 992 hosts a process that provides information representing video data for presentation at display 914. It is contemplated that the components of system can be deployed in various configurations within other computer systems, e.g., host 982 and server 992.
In one embodiment, the chip set 1000 includes a communication mechanism such as a bus 1001 for passing information among the components of the chip set 1000. A processor 1003 has connectivity to the bus 1001 to execute instructions and process information stored in, for example, a memory 1005. The processor 1003 may include one or more processing cores with each core configured to perform independently. A multi-core processor enables multiprocessing within a single physical package. Examples of a multi-core processor include two, four, eight, or greater numbers of processing cores. Alternatively or in addition, the processor 1003 may include one or more microprocessors configured in tandem via the bus 1001 to enable independent execution of instructions, pipelining, and multithreading. The processor 1003 may also be accompanied with one or more specialized components to perform certain processing functions and tasks such as one or more digital signal processors (DSP) 1007, or one or more application-specific integrated circuits (ASIC) 1009. A DSP 1007 typically is configured to process real-world signals (e.g., sound) in real time independently of the processor 1003. Similarly, an ASIC 1009 can be configured to performed specialized functions not easily performed by a general purposed processor. Other specialized components to aid in performing the inventive functions described herein include one or more field programmable gate arrays (FPGA) (not shown), one or more controllers (not shown), or one or more other special-purpose computer chips.
The processor 1003 and accompanying components have connectivity to the memory 1005 via the bus 1001. The memory 1005 includes both dynamic memory (e.g., RAM, magnetic disk, writable optical disk, etc.) and static memory (e.g., ROM, CD-ROM, etc.) for storing executable instructions that when executed perform the inventive steps described herein to determine vehicle speed based on IMU sensor data 103. The memory 1005 also stores the data associated with or generated by the execution of the inventive steps.
A radio section 1115 amplifies power and converts frequency in order to communicate with a base station, which is included in a mobile communication system, via antenna 1117. The power amplifier (PA) 1119 and the transmitter/modulation circuitry are operationally responsive to the MCU 1103, with an output from the PA 1119 coupled to the duplexer 1121 or circulator or antenna switch, as known in the art. The PA 1119 also couples to a battery interface and power control unit 1120.
In use, a user of mobile station 1101 speaks into the microphone 1111 and his or her voice along with any detected background noise is converted into an analog voltage. The analog voltage is then converted into a digital signal through the Analog to Digital Converter (ADC) 1123. The control unit 1103 routes the digital signal into the DSP 1105 for processing therein, such as speech encoding, channel encoding, encrypting, and interleaving. In one embodiment, the processed voice signals are encoded, by units not separately shown, using a cellular transmission protocol such as global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (UMTS), etc., as well as any other suitable wireless medium, e.g., microwave access (WiMAX), Long Term Evolution (LTE) networks, code division multiple access (CDMA), wireless fidelity (WiFi), satellite, and the like.
The encoded signals are then routed to an equalizer 1125 for compensation of any frequency-dependent impairments that occur during transmission though the air such as phase and amplitude distortion. After equalizing the bit stream, the modulator 1127 combines the signal with a RF signal generated in the RF interface 1129. The modulator 1127 generates a sine wave by way of frequency or phase modulation. In order to prepare the signal for transmission, an up-converter 1131 combines the sine wave output from the modulator 1127 with another sine wave generated by a synthesizer 1133 to achieve the desired frequency of transmission. The signal is then sent through a PA 1119 to increase the signal to an appropriate power level. In practical systems, the PA 1119 acts as a variable gain amplifier whose gain is controlled by the DSP 1105 from information received from a network base station. The signal is then filtered within the duplexer 1121 and optionally sent to an antenna coupler 1135 to match impedances to provide maximum power transfer. Finally, the signal is transmitted via antenna 1117 to a local base station. An automatic gain control (AGC) can be supplied to control the gain of the final stages of the receiver. The signals may be forwarded from there to a remote telephone which may be another cellular telephone, other mobile phone or a land-line connected to a Public Switched Telephone Network (PSTN), or other telephony networks.
Voice signals transmitted to the mobile station 1101 are received via antenna 1117 and immediately amplified by a low noise amplifier (LNA) 1137. A down-converter 1139 lowers the carrier frequency while the demodulator 1141 strips away the RF leaving only a digital bit stream. The signal then goes through the equalizer 1125 and is processed by the DSP 1105. A Digital to Analog Converter (DAC) 1143 converts the signal and the resulting output is transmitted to the user through the speaker 1145, all under control of a Main Control Unit (MCU) 1103—which can be implemented as a Central Processing Unit (CPU) (not shown).
The MCU 1103 receives various signals including input signals from the keyboard 1147. The keyboard 1147 and/or the MCU 1103 in combination with other user input components (e.g., the microphone 1111) comprise a user interface circuitry for managing user input. The MCU 1103 runs a user interface software to facilitate user control of at least some functions of the mobile station 1101 to determine vehicle speed based on IMU sensor data 103. The MCU 1103 also delivers a display command and a switch command to the display 1107 and to the speech output switching controller, respectively. Further, the MCU 1103 exchanges information with the DSP 1105 and can access an optionally incorporated SIM card 1149 and a memory 1151. In addition, the MCU 1103 executes various control functions required of the station. The DSP 1105 may, depending upon the implementation, perform any of a variety of conventional digital processing functions on the voice signals. Additionally, DSP 1105 determines the background noise level of the local environment from the signals detected by microphone 1111 and sets the gain of microphone 1111 to a level selected to compensate for the natural tendency of the user of the mobile station 1101.
The CODEC 1113 includes the ADC 1123 and DAC 1143. The memory 1151 stores various data including call incoming tone data and is capable of storing other data including music data received via, e.g., the global Internet. The software module could reside in RAM memory, flash memory, registers, or any other form of writable computer-readable storage medium known in the art including non-transitory computer-readable storage medium. For example, the memory device 1151 may be, but not limited to, a single memory, CD, DVD, ROM, RAM, EEPROM, optical storage, or any other non-volatile or non-transitory storage medium capable of storing digital data.
An optionally incorporated SIM card 1149 carries, for instance, important information, such as the cellular phone number, the carrier supplying service, subscription details, and security information. The SIM card 1149 serves primarily to identify the mobile station 1101 on a radio network. The card 1149 also contains a memory for storing a personal telephone number registry, text messages, and user specific mobile station settings.
While the invention has been described in connection with a number of embodiments and implementations, the invention is not so limited but covers various obvious modifications and equivalent arrangements, which fall within the purview of the appended claims. Although features of the invention are expressed in certain combinations among the claims, it is contemplated that these features can be arranged in any combination and order.
