The subject matter disclosed herein relates generally to mobile communicators. More particularly, the subject matter relates to a mobile communicator having a user attentiveness detector that determines a user's attentiveness toward the mobile communicator, and a system and software for implementing such a mobile communicator.
Mobile communicators such as cell phones, BLACKBERRIES®, IPHONES®, netbooks, laptop computers, notepads, GPS devices, personal digital assistants (PDA) and the like are becoming increasingly utilized in today's society. However, these devices may also become an undesirable distraction in many situations. For example, many people choose to use their mobile communicators while driving. Text messaging, web surfing, and emailing functions may be particularly undesirable when driving because a person must constantly utilize at least one hand to input these types of communications, and must often look down to draft a text message. Studies have been undergone which show that this behavior significantly increases the likelihood of causing a traffic accident. Yet, people continue to text message with their mobile communicators while driving with increasing regularity. In light of this, many states attempting to pass legislation aimed at making it illegal to text while driving. However, governmentally regulated penalties alone may not be a sufficient enough deterrent to cause people to drastically change their behavior.
Thus, a mobile communicator having a user attentiveness detector that determines a user's attentiveness toward the mobile communicator, and a system and software for implementing such a mobile communicator would be well received in the art.
According to one embodiment, a mobile communicator comprises: a speed detection system for determining whether the mobile communicator is moving faster than a threshold speed; a user attentiveness detector configured determine whether a user is inattentive; and a circuit configured to ensure that a functionality of the mobile communicator is in a turned off state when the speed detection system determines that the mobile communicator is moving faster than the threshold speed and the user attentiveness detector determines that the user is inattentive.
According to another embodiment, a mobile communicator comprises: a speed detection system for determining whether the mobile communicator is moving faster than a threshold speed; a user attentiveness detector configured determine whether a user is inattentive; and a circuit configured to disable a functionality of the mobile communicator when the speed detection system determines that the mobile communicator is moving faster than the threshold speed and the user attentiveness detector determines that the user is inattentive.
According to another embodiment, a computer program product, comprising a non-transitory computer-readable storage medium having a computer-readable program code stored therein, said computer-readable program code contains instructions configured to be executed by a processor of a mobile communicator to implement a method of restricting the functionality of the mobile communicator, the method comprising: the processor determining whether the mobile communicator is moving faster than a threshold speed; the processor determining whether a user is inattentive; and the processor disabling a functionality of the mobile communicator if the mobile communicator is moving faster than the threshold speed and the user is inattentive.
According to another embodiment, a computer system comprises: a processor; and a computer-readable memory unit coupled to the processor, the memory unit containing instructions that when executed by the processor implement a method of restricting the functionality of the computer system, the method comprising: determining whether the computer system is moving faster than a threshold speed; determining whether a user is inattentive; and disabling a functionality of the computer system if the speed is greater than a threshold speed and the user is inattentive.
According to another embodiment, a mobile communicator comprises: a functionality including a default turned off state; a speed detection system for determining whether the mobile communicator is moving faster than a threshold speed; a user attentiveness detector configured to determine whether a user is attentive; and a circuit configured to enable the functionality of the mobile communicator when the speed detection system determines that the mobile communicator is moving slower than the threshold speed, wherein the circuit is further configured to enable the functionality of the mobile communicator when the user attentiveness detector determines that the user is attentive.
According to another embodiment, a computer program product, comprising a non-transitory computer-readable storage medium having a computer-readable program code stored therein, said computer-readable program code contains instructions configured to be executed by a processor of a mobile communicator to implement a method of restricting the functionality of the mobile communicator, the method comprising: the processor determining whether the mobile communicator is moving slower than a threshold speed; the processor determining whether a user is attentive; the processor enabling a functionality of the mobile communicator if the mobile communicator is moving slower than the threshold speed; and the processor enabling a functionality of the mobile communicator if the user is attentive.
According to another embodiment, a computer system comprises: a processor; and a computer-readable memory unit coupled to the processor, the memory unit containing instructions that when executed by the processor implement a method of restricting the functionality of the computer system, the method comprising: determining whether the mobile communicator is moving slower than a threshold speed; determining whether a user is attentive; enabling a functionality of the mobile communicator if the mobile communicator is moving slower than the threshold speed; and enabling a functionality of the mobile communicator if the user is attentive.
The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
A detailed description of the hereinafter described embodiments of the disclosed apparatus and method are presented herein by way of exemplification and not limitation with reference to the Figures.
Referring to
While
It should be noted that the embodiments described hereinbelow illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various described and depicted embodiments. In this regard, each block in the block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagram illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Referring back to
Likewise, the user notification mechanism 20 of the mobile communicator 10 may be a noise notification element, such as a speaker that emits a ring or “ring-tone” that alerts the user 60. For example, when the mobile communicator 10 receives a transmission signal, a speaker may emit a pre-programmed audible ring that alerts the user 60 of the incoming transmission. Alternately, the notification mechanism 20 may be a change found on the display 18. For example, the display 18 may light up when a transmission is incoming. Still further, the mobile communicator 10 may vibrate, as is known in the art. The user notification mechanism 20 may be any mechanism for alerting the user 60 of a communication event. Additionally, the notification mechanism 20 may be preprogrammed to alert the user 60 of a predetermined event, such as when a time of day is reached (in the case of an alarm clock notification). It should further be understood that the mobile communicator 10 may include a plurality of user notification mechanisms 20.
The user interface 16 may be configured for allowing the user 60 to enter a plurality of identity inputs associated with an alphanumeric combination of numbers and letters. For example, the user interface 16 may be a touch screen, a keyboard, or a simple number pad. Alternately, the user interface 16 may be a voice receiver that allows the user 60 to enter a plurality of identity inputs by voice. In one embodiment, the user interface 16 may be a text messaging interface. The user interface may thus be configured for web browsing and video watching. The text messaging interface may be a telephone text messaging interface, or another “chat” functionality such as email, Google Talk®, AIM®, Skype®, Facebook®, Myspace®, Twitter® or any other communication application that allows the user 60 to communicate via text-based messages. In other embodiments, the user interface 16 is a telephone number dialing interface. It should therefore be understood that the mobile communicator 10 may include any type of user interface 16 that would be apparent to those skilled in the art such as a voice input user interface. It should further be understood that the mobile communicator 10 may include a plurality of different user interfaces 16, for example, both a touch screen and a keypad.
The transmitter 12 of the mobile communicator 10 may be in operable communication with the user interface 16 and configured to send a transmission from the mobile communicator 10 to an output device having an identity corresponding with the identity input that is inputted into the mobile communicator 10 via the user interface 16. The transmitter 12 may be configured to communicate typical electromagnetic and/or sonic transmissions such as a cell phone voice transmission, an email, a video or picture message, or a transmission that interacts with the internet. For example, the transmitter 12 may be a network adapter or card that is configured to transmit signals through a router or local area network. Alternately, the transmitter 12 of the mobile communicator 10 may be configured to send a transmission on a 3rd or 4th generation wireless network, or any future wireless networks. It should further be understood that the mobile communicator 10 may include a plurality of transmitters 12.
Likewise, the receiver 14 of the mobile communicator 10 may be capable of receiving a transmission from a transmitting device. The mobile communicator may be configured to receive any type of transmission such as a cell phone voice transmission, an email, a text, video or picture message, or a transmission from a laptop or computer. For example, the receiver 14 of the mobile communicator may be configured to receive local signals from a router, switch or other local area network. Alternately, the receiver 14 of the mobile communicator 1000 may be configured to receive transmissions from 3rd or 4th generation wireless networks, or any future wireless networks. It should further be understood that the mobile communicator 10 may include a plurality of different receivers 14.
The present invention contemplates that the velocity of the mobile communicator 10 is determinable by at least one speed detection system 36. For example, the mobile communicator 10 may include an internal GPS system for determining velocity. Alternately, the mobile communicator 10 may use another speed detection system such as cell tower triangulation, multilateration, or the like. Furthermore, the speed detection mechanism may be an accelerometer or may be included in a kit such as the kit 400 described herein below. In one embodiment, the speed detection system may actually be a retrieval system for retrieving the speed of the mobile communicator from another device. For example, the speed detection system of the mobile communicator 10 may retrieve the speed from the speedometer of the vehicle that the mobile communicator 10 is located within. Thus, the speed of the mobile communicator 10 may be determined internally by the mobile communicator 10 or may be determined by a third party such as a cell phone service provider (not shown), a vehicle or a kit. It should be understood that the speed detection system 36 may store the speed in the memory device 30 for processing by the processor 22. The speed detection system 36 may further be in operable communication with the vehicle speed detector, such as the speedometer. In this embodiment, the speed detection may be attached to 36, or may actually be the speed detection system of the vehicle. For example, the mobile communicator may be operably connected to the speed detection system of an automobile in order to determine velocity.
Further, in one embodiment, the speed detection system 36 may include a hierarchy system. For example, the GPS system may be activated first. If there is no GPS signal, a secondary system such as cell tower triangulation may be utilized. If this is unavailable, multilateration may be used. The speed detection system 36 may determine which form of speed determination means is best from a battery life, data transfer requirement, or usability perspective.
The mobile communicator 10 may include a circuit 38 that is configured to bring a restricted functionality into a “turned off” state or a “turned on” state depending on the determination that is made by the speed detection system 36. It should be understood that the circuit 38 may be included in the processor 22. Hereinafter, it should be understood that “restricted functionality” may refer to any functionality that is “enabled” or “disabled,” by the circuit 38 based at least partially on the speed detected by the speed detection system 36. Hereinafter, it should be understood that the word “disable,” or “disabled” refers to the actual process or method by which the circuit 38 disables the restricted functionality of the mobile communicator 10. Likewise, “enable” or “enabled” refers to the actual process or method by which the circuit 38 enables the restricted functionality of the mobile communicator 10. In contrast, when the restricted functionality has been “disabled” by the circuit 38, the restricted functionality will be referred to as being in a “turned off” state. The “turned off” state may refer to any state where the restricted functionality is turned off, disabled, blocked, restricted, or the like. When the restricted functionality has been “enabled” by the circuit 38, the restricted functionality will be referred to as being in a “turned on” state. The “turned on” state may refer to any state where the restricted functionality is turned on, enabled, allowed, unrestricted, or the like.
In a first embodiment, restricted functionality may be in a turned on state by default. In this case, the circuit 38 may disable the restricted functionality of the mobile communicator 10 when the speed detection system 36 determines that the mobile communicator 10 is moving at a speed that is greater than or equal to a certain threshold speed. The threshold speed may be five miles per hour, ten miles per hour, twenty miles per hour or any other suitable speed. Whatever the threshold speed, the circuit 38 may disable the restricted functionality of the mobile communicator 10 when it is determined that there is a potential that the user 60 of the mobile communicator 10 is operating a moving vehicle.
In this embodiment, the restricted functionality may be the text messaging interface of the mobile communicator 10. The circuit 38 may thus disable the text messaging interface when the speed detection system 36 determines that the mobile communicator 10 is moving above the threshold speed. In this embodiment, the mobile communicator 10 may also display a message to the user 60 when the text messaging interface is accessed by the user 60 that tells the user 60 to stop texting or that texting has been disabled and is turned off. The circuit 38 may also be configured to disable any of the receiver 14, the transmitter 12, the user interface 16, the user notification mechanism 20, the display 18 or any of the other various functionalities that the mobile communicator may include, described hereinabove. The circuit 38 may be configured to disable more than one of these functionalities in one or more embodiments. Furthermore, the circuit 38 may be configured to disable the preprogrammed functionalities if the speed detection system 36 is tampered with or does not have any determination of speed. For example, in the case that the speed detection system 36 is a GPS and the mobile communicator 10 is moving through a tunnel, the circuit 38 may be configured to disable texting or phone calls despite that there is no speed determination being made by the speed detection system 36. The mobile communicator 10 may also notify the user 60 via the display 18 when the speed detection system 36 determines that the mobile communicator is moving at a speed that is above a threshold speed. Alternately, the mobile communicator 10 may notify a third party device (not shown), for example, by sending an email to the third party device.
In this embodiment, either or both of the circuit 38 and the speed detection system 36 may not always be in operation. The circuit 38 and the speed detection system 36 may instead be dormant until, for example, the restricted functionality of the mobile communicator 10 is accessed by the user 60. In this situation, the speed detection system 36 and then the circuit 38 may then be activated in order to disable the restricted functionality until an enabling event occurs. It should be understood that restricted applications may include text messaging applications, as described hereinabove. Alternately, either or both of the speed detection system 36 and the circuit 38 may always be in operation. In this embodiment, the speed detection system 36 may be activated constantly or at regular intervals in order to make a determination as to whether the mobile communicator 10 is moving above the threshold speed. The circuit 38 may then disable the restricted functionalities of the mobile communicator 10 if the speed is greater than the threshold speed. It should further be understood that the speed detection system 36 may be activated at more frequent intervals when it is determined that the speed is greater than the threshold speed. However, even in this scenario, the speed detection system 36 may not be constantly in operation, but may instead be activated at regular predetermined intervals in order to conserve battery life of the mobile communicator 10.
Referring still to the embodiment where the restricted functionality is turned on by default, the mobile communicator 10 may further include a user attentiveness detector 40 that is utilized in determining whether the user 60 is in an attentive state. Hereinafter, “attentiveness” will refer to a user's attentiveness toward the mobile communicator 10. For example, a user referred to in an “attentive” state means that the user is attentive to the mobile communicator 10 according to one of the various ways described herein. On the other hand, a user referred to in an “inattentive” state means that the user is not attentive to the mobile communicator 10 because the user is distracted or doing something else such as driving a vehicle.
In one example, the user attentiveness detector 40 may include an image capture device 42, such as a camera or a video capturer. In this embodiment, the image capturer device 42 may provide images that may be used by the processor 22 to determine if the user 60 is looking at the display 18 of the mobile communicator 10. The images may be stored in the memory device 30, for example, and then analyzed by the processor 22 to determine if the user 60 is looking at the display 18, or looking at the image capturer device 42 that may be located on or near the display 18 on the same face of the mobile communicator 10. The image capturing device 42 may further be a beam of infrared radiation that scans the user's face 62 or eyes 64 (shown more particularly in
Referring to
The processor 22 may analyze the movements of the user's head or face 62 to determine attentiveness. Particularly, the processor 22 may be configured to take the images gathered by the image capture device 42 and make a determination as to whether a user's head 62 is facing the display 18 or looking in a direction that is not in the vicinity of the display 18. Like the eye focusing technology, the mobile communicator 10 may include software that is stored on one of the memory devices 28, 30 and is configured to provide the processor 22 with the capability of making this determination. The user attentiveness detector 40 may further include a laser that is configured to determine the distance from the mobile communicator 10 to the user 60. The laser may be a range finder. A constantly changing distance may be a factor that is utilized by the processor 22 in interpreting whether the user 60 is in an attentive of inattentive state. For example, if the user 60 is constantly varying moving the mobile communicator 10 with respect to his or her face 62, this may indicate to the processor 22 that the user 60 is in an inattentive state.
The mobile communicator 10 may further be programmed with an algorithm to determine whether the user 60 is in an attentive state or an inattentive state. This program may be configured to determine if the user 60 is actually attentive over a period of time. For example, the user attentiveness detector 40 may provide information to the processor 10 regarding a user's pupil movements multiple times in a second. In one embodiment, the user attentiveness detector 40 or the image capture device 42 may provide the processor 22 analyzable frames at a rate of twenty or more frames per second. It should be understood that the number of individual frames provided by the user attentiveness detector 40 or the image capture device 42 per second may be any appropriate amount. The processor 22 may be configured to analyze each frame to make a determination whether the user 60 is looking at the display 18 in that frame. Then, the processor 22 may be configured to compile the information about each frame and make a determination of the overall attentiveness level of the user 60. Namely, the processor 22 may determine whether the user 60 is currently attentive or currently inattentive. If, for example, it is determined that the user 60 is attentive for a high percentage of frames over a predetermined period of time, the mobile communicator 10 may determine that the user 60 is in an attentive state. Alternately, the mobile communicator 10 may determine that the user 60 is looking at the display 18 only briefly before looking away and that the user 60 is attentive for only a low percentage of frames over a predetermined period of time. The mobile communicator 10 may thus determine that the user 60 is not in an inattentive state.
In one embodiment, the user attentiveness detector 40 may operate completely separately from the speed detection system 36. The embodiments of the user attentiveness detector 40 described herein may be utilized to determine user attentiveness for any appropriate purpose, and may affect any appropriate functionality of the mobile communicator 10 based on the determination of user attentiveness as described herein. For example, the mobile communicator 10 may disable a functionality if it is determined that a user is inattentive, regardless of the speed of the mobile communicator 10 and even if the mobile communicator does not include a speed detection mechanism.
Again referring to the first embodiment where the restricted functionality is turned on by default and then the restricted functionality is then disabled by the circuit 38, if the user attentiveness detector 40 in combination with the processor 22 determines that the user 60 is in an attentive state, the mobile communicator 10 may be programmed such that the processor 22 enables the previously disabled functionality. For example, if the user 60 is driving in the automobile 70 instead of being a passenger, then the text messaging functionality of the mobile communicator 10 may be disabled by the disabling circuit 34 as described hereinabove. However, if the image capture device 38 determines that the user 60 is in an attentive state and looking at the display 18 of the mobile communicator 10, the mobile communicator 10 may be configured to enable the text messaging functionality, or other functionality.
Alternately, if the restricted functionality is turned on by default, the circuit 38 may not immediately disable the restricted functionality if the speed determined by the speed detection system 36 to be greater than the threshold speed. Instead, the processor 22 may be configured to query the user attentiveness detector 40 to determine if a user is attentive. If the user 60 is determined by the processor 22 to be attentive, the circuit 38 may then keep restricted functionality in a turned on state. In contrast, if the user 60 is determined by the processor 22 to be inattentive, the circuit 38 may then disable the restricted functionality so that it is then in a turned off state.
Whatever the embodiment, a predetermined period of inattentive time may result in the processor 22 concluding that the user 60 is in an inattentive state. If the user 60 is determined to be in an inattentive state, the mobile communicator 10 may be placed into a disabled state whereby one or more functionalities, such as text messaging, are disabled. In this embodiment, the processor 22 may be configured to determine that the user 60 is in an inattentive state when, for example, the user 60 is not looking at the display 18 for two consecutive seconds. This duration of inattentiveness may be greater or less than two seconds depending on the embodiment.
In an illustrative example meant to further clarify the first embodiment described above, if the user 60 is traveling in the automobile 70 at a speed greater than the certain threshold speed, the circuit 38 may disable at least one function (such as one or more text messaging interfaces) of the mobile communicator 10. If it is determined that the user 60 is attentive by the user attentiveness detector 40 and the processor 22, the mobile communicator 10 may then enable the previously disabled functionality. If, however, at any point during the turned on text messaging session, the mobile communicator 10 determines that a predetermined period of inattentive time passes, then the circuit 38 may once again disable the restricted functionalities. Alternately, if at any point during a enabled text messaging session the mobile communicator 10 determines that a low percentage of frames over a predetermined period of time show an attentive user 60, the circuit 38 may once again disable the restricted functionalities. Thus, the mobile communicator 10 may be configured to ensure that the restricted functionalities are in a turned off state whenever the user attentiveness detector 26 determines that the user 60 is not attentive, even if it was previously determined that a user was in an attentive state during the restricted functionality session. In other words, the user attentiveness detector 40 and the processor 22 may be configured to constantly monitor the attentiveness state of the user 60 during operation of a restricted function such as text messaging.
In another illustrative example, the user 60 may attempt to use a restricted functionality while traveling at a speed greater than the threshold speed. This may activate the speed detection system 36 and the user attentiveness detector 40. During the gathering of information by these systems, the mobile communicator 10 may be configured to display a message to the user 60 on the display 18, indicating that the mobile communicator is checking the availability of the restricted function. The mobile communicator 10 may include a message stating that the restricted function requires the full attention of the user 60. During this stage, the user 60 may be required to be directly looking at the mobile communicator 10 in order to ensure that the restricted functionality is in a turned on state. If the user 60 is determined to be inattentive, the processor 22 may ensure that the restricted functionality is in a turned off state.
Referring still to
It should be understood that the various functionalities of the mobile communicator 10 described herein may be provided as an inherent property programmed into a mobile communicator such as the mobile communicator 10. Alternately, the embodiments may be provided by one or more downloadable or installable programs, applications or other software. These applications, downloadable or installable programs or other software may turn a typical mobile communicator into the mobile communicator 10 having one or more embodiments of the present invention, described hereinabove. Furthermore, various methods are also contemplated to accomplish the various embodiments of the mobile communicator 10 described herein.
Referring now to
If at any point, the user attempts to access a restricted functionality, shown at step 118, the mobile communicator 10 may determine whether the user 60 is in an attentive state, shown at step 120. The determination of attentiveness may be made by the user attentiveness detector 40 and the processor 22 as described in the various embodiments hereinabove. If it is determined that the user 60 is not in an attentive state, the mobile communicator 10 may be configured to keep the restricted functionalities in the turned off state, shown at step 112. If, however, the user 60 is in an attentive state, the mobile communicator 10 may be re-enabled such that the restricted functionalities are turned on, shown at step 122. If the mobile communicator 10 has been re-enabled due to user attentiveness, the method 100 may then include continuously determining if the user remains in an attentive state for the entirety of the restricted functionality session, or alternately whether the user ever becomes inattentive. This is shown in step 124. If the user 60 remains attentive, the restricted functionality of the mobile communicator 10 may remain in a turned on state for the entirety of the restricted functionality session, shown in step 126. If however, the user 60 ever becomes inattentive during the restricted functionality session, the mobile communicator 10 may revert back to the turned off state of step 112.
Referring now to
The embodiments described hereinabove assume that the mobile communicator 10 has one or more restricted functionalities, such as text messaging interface, which is in a default turned on state. Thus, it has been described that the restricted functionality is disabled by the circuit 38 when the speed detection system 36 determines that the speed is greater than a certain threshold speed and a user is attentive. However, it should be understood that the restricted functionality of the mobile communicator 10 may initially be in a default turned off state. In other words, the mobile communicator 10 may be turned off by default, and be enabled by the circuit 38 if the speed detection system 36 determines that the speed is less than a certain threshold. Further, the restricted functionality may remain in the default turned off state if the speed detection system 36 determines that the speed is greater than a certain threshold. Then, if the user attentiveness detector 40 and the processor 22 determine that a user is attentive, the circuit 38 may be configured to enable the restricted functionality such that it is in a turned on state. Whatever the embodiment, it should be understood that the restricted functionality of the mobile communicator 10 may be configured to be in a turned off state if a user is inattentive and that the speed detection system 36 determines that the speed is greater than the threshold speed (or if the speed detection system 36 determines that the speed isn't less than the threshold speed).
Shown in
Furthermore, in another embodiment, one or more of the functionalities described herein may be provided in the form of one or more kits, such as a kit 400 for a mobile communicator 410, as shown in
Furthermore, the kit 400 may generate a signal that may enable the mobile communicator 410. The kit 400 may be portable, or built into a vehicle or structure. The kit 400 may be utilized to enable the mobile communicator 410 when, for example, there is no GPS signal available for the speed detection system 36 of the mobile communicator 10. The kit 400 may include an independent means of detecting motion or movement so that if the kit 400 was moving, the signal may be disabled to prevent a user from bringing the kit 400 into a car to allow them to utilize the restricted functionality in a manner that would not otherwise be enabled. Alternately, kits 400 may be integrated into vehicles such that their enabling signals are only accessible to areas of the vehicle where passengers are located. For example, the back seat of a passenger vehicle may include the kit 400 for enabling this area of the vehicle. The kit 400 is shown being powered from an outlet 420. However, it should be understood that the kit 400 may include its own internal battery or may be plugged into an automobile as would be known to those skilled in the art.
Elements of the embodiments have been introduced with either the articles “a” or “an.” The articles are intended to mean that there are one or more of the elements. The terms “including” and “having” and their derivatives are intended to be inclusive such that there may be additional elements other than the elements listed. The conjunction “or” when used with a list of at least two terms is intended to mean any term or combination of terms. The terms “first” and “second” are used to distinguish elements and are not used to denote a particular order.
While the invention has been described in detail in connection with only a limited number of embodiments, it should be readily understood that the invention is not limited to such disclosed embodiments. Rather, the invention can be modified to incorporate any number of variations, alterations, substitutions or equivalent arrangements not heretofore described, but which are commensurate with the spirit and scope of the invention. Additionally, while various embodiments of the invention have been described, it is to be understood that aspects of the invention may include only some of the described embodiments. Accordingly, the invention is not to be seen as limited by the foregoing description, but is only limited by the scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
5844544 | Kahn et al. | Dec 1998 | A |
5886683 | Tognazzini et al. | Mar 1999 | A |
5892447 | Wilkinson | Apr 1999 | A |
6108532 | Matsuda et al. | Aug 2000 | A |
6115607 | Holcman | Sep 2000 | A |
6282553 | Flickner et al. | Aug 2001 | B1 |
6377813 | Kansakoski et al. | Apr 2002 | B1 |
6496703 | Da Silva | Dec 2002 | B1 |
6556810 | Suzuki | Apr 2003 | B2 |
6633762 | Brown et al. | Oct 2003 | B1 |
6633950 | Brown et al. | Oct 2003 | B1 |
6636732 | Boling et al. | Oct 2003 | B1 |
6662023 | Helle | Dec 2003 | B1 |
6687497 | Parvulescu et al. | Feb 2004 | B1 |
6690940 | Brown et al. | Feb 2004 | B1 |
6694143 | Beamish et al. | Feb 2004 | B1 |
6771946 | Oyaski | Aug 2004 | B1 |
6782240 | Tabe | Aug 2004 | B1 |
6823199 | Gough | Nov 2004 | B2 |
6871063 | Schiffer | Mar 2005 | B1 |
6934547 | Suzuki | Aug 2005 | B2 |
6967580 | Schulze | Nov 2005 | B1 |
6973333 | O'Neil | Dec 2005 | B1 |
7065349 | Nath et al. | Jun 2006 | B2 |
7088225 | Yoshioka | Aug 2006 | B2 |
7113170 | Lauper et al. | Sep 2006 | B2 |
7123874 | Brennan | Oct 2006 | B1 |
7187953 | Bauchot et al. | Mar 2007 | B2 |
7260390 | Skinner et al. | Aug 2007 | B1 |
7308247 | Thompson et al. | Dec 2007 | B2 |
7343148 | O'Neil | Mar 2008 | B1 |
7505784 | Barbera | Mar 2009 | B2 |
7590405 | Ewell, Jr. | Sep 2009 | B2 |
7719520 | Singh et al. | May 2010 | B2 |
7762665 | Vertegaal et al. | Jul 2010 | B2 |
8131848 | Denise | Mar 2012 | B1 |
8380161 | Ewell, Jr. et al. | Feb 2013 | B2 |
8385880 | Ewell, Jr. et al. | Feb 2013 | B2 |
8417268 | Halferty et al. | Apr 2013 | B1 |
8538158 | Denise | Sep 2013 | B1 |
8995945 | Ewell, Jr. et al. | Mar 2015 | B2 |
9026779 | Ewell, Jr. et al. | May 2015 | B2 |
9026780 | Ewell, Jr. et al. | May 2015 | B2 |
9196239 | Taylor | Nov 2015 | B1 |
20010051514 | Lindholm | Dec 2001 | A1 |
20020090919 | Hofman | Jul 2002 | A1 |
20020128000 | do Nascimento, Jr. | Sep 2002 | A1 |
20020164979 | Mooney et al. | Nov 2002 | A1 |
20020173301 | Ikeda | Nov 2002 | A1 |
20020193107 | Nascimento, Jr. | Dec 2002 | A1 |
20020198005 | Hilton et al. | Dec 2002 | A1 |
20030045322 | Baer et al. | Mar 2003 | A1 |
20030050039 | Baba et al. | Mar 2003 | A1 |
20030171133 | Mizuta et al. | Sep 2003 | A1 |
20040077339 | Martens | Apr 2004 | A1 |
20040110421 | Takamura et al. | Jun 2004 | A1 |
20040171407 | Ninomiya | Sep 2004 | A1 |
20040176083 | Shiao et al. | Sep 2004 | A1 |
20040198306 | Singh et al. | Oct 2004 | A1 |
20040201520 | Flick | Oct 2004 | A1 |
20040203554 | Simon | Oct 2004 | A1 |
20040204003 | Soerensen et al. | Oct 2004 | A1 |
20040204021 | Cocita | Oct 2004 | A1 |
20040229645 | Montgomery | Nov 2004 | A1 |
20050026644 | Lien | Feb 2005 | A1 |
20050239479 | Bednasz | Oct 2005 | A1 |
20050255874 | Stewart-Baxter et al. | Nov 2005 | A1 |
20060003809 | Boling et al. | Jan 2006 | A1 |
20060066567 | Scharenbroch et al. | Mar 2006 | A1 |
20060099940 | Pfleging et al. | May 2006 | A1 |
20060148490 | Bates et al. | Jul 2006 | A1 |
20060240860 | Benco et al. | Oct 2006 | A1 |
20060258376 | Ewell, Jr. | Nov 2006 | A1 |
20070024579 | Rosenberg | Feb 2007 | A1 |
20070072553 | Barbera | Mar 2007 | A1 |
20070078552 | Rosenberg | Apr 2007 | A1 |
20070111756 | Reed | May 2007 | A1 |
20070164990 | Bjorklund et al. | Jul 2007 | A1 |
20070213092 | Geelen | Sep 2007 | A1 |
20070270122 | Ewell, Jr. | Nov 2007 | A1 |
20080075056 | Thome | Mar 2008 | A1 |
20080169914 | Albertson et al. | Jul 2008 | A1 |
20080200166 | McCamon | Aug 2008 | A1 |
20080299900 | Lesyna | Dec 2008 | A1 |
20080299954 | Wright et al. | Dec 2008 | A1 |
20080305735 | Farnsworth et al. | Dec 2008 | A1 |
20080316181 | Nurmi | Dec 2008 | A1 |
20090029675 | Steinmetz et al. | Jan 2009 | A1 |
20090055896 | Aoki et al. | Feb 2009 | A1 |
20090070798 | Lee | Mar 2009 | A1 |
20090117919 | Hershenson | May 2009 | A1 |
20090163243 | Barbera | Jun 2009 | A1 |
20090215466 | Ahl et al. | Aug 2009 | A1 |
20090253423 | Kullberg | Oct 2009 | A1 |
20090258676 | Tanaka | Oct 2009 | A1 |
20090270143 | Bury | Oct 2009 | A1 |
20090282127 | Leblanc | Nov 2009 | A1 |
20090295562 | Shuster | Dec 2009 | A1 |
20100009658 | Wu et al. | Jan 2010 | A1 |
20100042911 | Wormald et al. | Feb 2010 | A1 |
20100088047 | Campbell et al. | Apr 2010 | A1 |
20100093405 | Ewell, Jr. et al. | Apr 2010 | A1 |
20100113073 | Schlesener et al. | May 2010 | A1 |
20100130170 | Liu et al. | May 2010 | A1 |
20100132040 | Bhagwat et al. | May 2010 | A1 |
20100156781 | Fahn | Jun 2010 | A1 |
20100182243 | Singh et al. | Jul 2010 | A1 |
20100197351 | Ewell, Jr. et al. | Aug 2010 | A1 |
20100207721 | Nakajima et al. | Aug 2010 | A1 |
20100216509 | Riemer et al. | Aug 2010 | A1 |
20100229217 | Bhatia | Sep 2010 | A1 |
20100248642 | Howard et al. | Sep 2010 | A1 |
20100295839 | Nagaya et al. | Nov 2010 | A1 |
20100304712 | Sweeney et al. | Dec 2010 | A1 |
20100323657 | Barnard et al. | Dec 2010 | A1 |
20110009107 | Guba et al. | Jan 2011 | A1 |
20110028139 | Odom | Feb 2011 | A1 |
20110065456 | Brennan et al. | Mar 2011 | A1 |
20110082790 | Baker et al. | Apr 2011 | A1 |
20110235443 | Lee et al. | Sep 2011 | A1 |
20110244824 | Ewell, Jr. | Oct 2011 | A1 |
20110262887 | Cleveland | Oct 2011 | A1 |
20110298924 | Miller et al. | Dec 2011 | A1 |
20120021717 | Schmidt | Jan 2012 | A1 |
20120129544 | Hodis et al. | May 2012 | A1 |
20120129545 | Hodis et al. | May 2012 | A1 |
20120140015 | DeGrazia | Jun 2012 | A1 |
20120158918 | Leblanc et al. | Jun 2012 | A1 |
20120166788 | Racha et al. | Jun 2012 | A1 |
20120206254 | Morris | Aug 2012 | A1 |
20120214463 | Smith et al. | Aug 2012 | A1 |
20120231773 | Lipovski | Sep 2012 | A1 |
20120244883 | Tibbitts et al. | Sep 2012 | A1 |
20120289217 | Riemer et al. | Nov 2012 | A1 |
20120309296 | Tieman et al. | Dec 2012 | A1 |
20120327225 | Barley et al. | Dec 2012 | A1 |
20130035117 | Litkouhi et al. | Feb 2013 | A1 |
20130052945 | Ewell, Jr. et al. | Feb 2013 | A1 |
20130150004 | Rosen | Jun 2013 | A1 |
20130252575 | Ewell, Jr. et al. | Sep 2013 | A1 |
20130303143 | Schrader et al. | Nov 2013 | A1 |
20140004840 | Ewell, Jr. et al. | Jan 2014 | A1 |
20140045477 | Ewell, Jr. et al. | Feb 2014 | A1 |
20140118597 | Tabak et al. | May 2014 | A1 |
20160191995 | el Kaliouby | Jun 2016 | A1 |
Number | Date | Country |
---|---|---|
2005303384 | Oct 2005 | JP |
Entry |
---|
International Search Report; PCT/US2012/33181; International File Date: Apr. 12, 2012; Mobile Communication Technologies, LLC; 20 pages. |
Office Action (dated Jun. 3, 2014) for U.S. Appl. No. 13/834,744, filed Mar. 15, 2013. |
Office Action (dated Jun. 3, 2014) for U.S. Appl. No. 13/914,007, filed Jun. 10, 2013. |
Number | Date | Country | |
---|---|---|---|
20120265977 A1 | Oct 2012 | US |