Layout design of proximity sensors to enable shortcuts
Claim Score by NHIP
Abstract
A mobile platform includes a plurality of proximity sensors coupled to a housing including on the sides, front and back of the housing. Signals from the proximity sensors are analyzed to determine configuration of the proximity sensors that are activated. The configuration may be a sequence of proximity sensors that are activated, e.g., when a gesture is detected, or the locations of the proximity sensors that are activated when the mobile platform is held in different manners. Mobile platform applications associated with the configuration are determined and automatically launched. For example, the applications may include a camera application or short message service (SMS) application, as well as controlling telephony operations, controlling a music player, and providing status information. Information from an orientation sensor and/or ambient light detector may also be used to assist in determining the applications to be launched.

Term
6.5 yearsto projected expiry
Projected expiry 5 April 2033, counted from filing; an application has no term until it is granted.
- Priority and filed
- Published
- Today
- Projected expiry
55 claims: 4 independent, 51 dependent
- 1A mobile platform comprising:a housing having a front, back, first side, second side, top side and a bottom side;a touch screen display on the front of the housing;a plurality of proximity sensors coupled to the housing, each proximity sensor is activated when an object passes through a field produced by the proximity sensor, the plurality of proximity sensors having a configuration on the housing, the configuration comprising: at least one proximity sensor mounted on the first side and at least one proximity sensor mounted on the second side;at least one proximity sensor mounted on the back of the housing;a processor connected to the plurality of proximity sensors;memory connected to the processor;and software held in the memory and run in the processor to determine a configuration of activated proximity sensors and to control the mobile platform based on the configuration of activated proximity sensors.
- 26A method comprising:monitoring for signals from a plurality of proximity sensors coupled to a housing of a mobile platform;analyzing signals received from the plurality of proximity sensors to determine a configuration of activated proximity sensors;determining a mobile platform application associated with the configuration of activated proximity sensors;and controlling an operation of the mobile platform to run the mobile platform application associated with the configuration of activated proximity sensors.
- 43Broadest claimClaim Score 80, broad(NHIP)A system for controlling an operation of a mobile platform comprising:means for capacitively sensing a proximity of an object to a housing of the mobile platform, the means for capacitively sensing being located at multiple locations on the housing including a first side, a second side, and a back side;means for determining a configuration of the means for capacitively sensing that are activated by the proximity of the object to the housing;means for determining a function associated with the configuration;means for controlling the operation of the mobile platform to perform the function associated with the configuration.
- 52A computer-readable medium including program code stored thereon, comprising:program code to analyze signals received from a plurality of proximity sensors to determine a configuration of activated proximity sensors;program code to determine a mobile platform application associated with the configuration of activated proximity sensors;program code to automatically run a mobile platform application associated with the configuration of activated proximity sensors.
Independent claims4
56 paragraphs in 4 sections, as filed
CLAIM OF PRIORITY UNDER 35 U.S.C. §119
p-0002This U.S. Nonprovisional patent application claims the benefit of U.S. Provisional Patent Application No. 61/355,452, filed Jun. 16, 2010, which is assigned to the assignee hereof and expressly incorporated by reference herein.
BACKGROUND
p-0003Portable electronic devices, such as cellular telephones or smart phones, have become increasingly complex over time, adding many disparate features such as web browser, music (MP3) player, camera, texting, as well as serving as a telephone. The selection of these different functions typically require the user to navigate a user interface, which may include physical or virtual push buttons, as well as a display that requires that user's attention while selecting the desired function. Typical, such user interfaces are distracting, requiring the user's attention to make the appropriate selection and can be frustrating when the wrong function is inadvertently selected. Accordingly, an improved user-interface is desired.
SUMMARY
p-0004A mobile platform includes a plurality of proximity sensors coupled to a housing that are used to automatically detect how the user is holding the mobile platform or to detect gestures made near the mobile platform and to launch associate applications in response. For example, capacitive proximity sensors may be positioned at different locations on the housing, including the sides, front and back. Signals from the capacitive proximity sensors are analyzed to determine the configuration of the capacitive proximity sensors that are activated, e.g., by the user's finger or hand. The configuration may be a sequence of capacitive proximity sensors that are activated, e.g., when a gesture is detected, or the locations of the capacitive proximity sensors that are activated when the mobile platform is held. Mobile platform applications associated with the configuration are determined and automatically launched. For example, the applications may include a camera application or short message service (SMS) application, as well as controlling telephony operations, controlling a music player, and providing status information. Information from an orientation sensor and/or ambient light detector may also be used to assist in determining the applications to be launched.
BRIEF DESCRIPTION OF THE DRAWING
p-0005<figref idrefs="DRAWINGS">FIGS. 1A and 1B</figref> illustrate a front side and a back side, respectively, of a mobile platform with capacitive proximity sensors on the housing.
p-0006<figref idrefs="DRAWINGS">FIGS. 2A</figref>, <b>2</b>B, and <b>2</b>C illustrate different types of capacitive proximity sensors.
p-0007<figref idrefs="DRAWINGS">FIGS. 3A</figref>, <b>3</b>B, <b>3</b>C, <b>3</b>D, and <b>3</b>E illustrate a different configuration of proximity sensors that may be used on the front side, left side, back side, and right side, respectively, of the housing of the mobile platform.
p-0008<figref idrefs="DRAWINGS">FIGS. 4A and 4B</figref> illustrate the front and back of a mobile platform with another configuration of proximity sensors that may be used on the front side and back side of the housing, respectively.
p-0009<figref idrefs="DRAWINGS">FIGS. 5A and 5B</figref> illustrate the front and back of a mobile platform with another configuration of proximity sensors that may be used on the front side and back side of the housing, respectively.
p-0010<figref idrefs="DRAWINGS">FIG. 6</figref> illustrates another configuration of proximity sensors on the housing of the mobile platform.
p-0011<figref idrefs="DRAWINGS">FIG. 7</figref> is a block diagram of a mobile platform that may provide a user interface using proximity sensors.
p-0012<figref idrefs="DRAWINGS">FIG. 8</figref> is a flow chart illustrating using a plurality of capacitive proximity sensors on the housing of the mobile platform as a user interface to automatically control the operation of the mobile platform.
p-0013<figref idrefs="DRAWINGS">FIG. 9</figref> is a flow chart illustrating a possible wake up function that may be implemented using the capacitive proximity sensors.
p-0014<figref idrefs="DRAWINGS">FIG. 10</figref> is a flow chart illustrating a possible low power (sleep) function that may be implemented using the capacitive proximity sensors.
p-0015<figref idrefs="DRAWINGS">FIG. 11</figref> is a flow chart illustrating a function in which the touch screen display is disabled based on signals from the capacitive proximity sensors.
p-0016<figref idrefs="DRAWINGS">FIG. 12</figref> is a flow chart illustrating controlling the operation of the mobile platform to run an application that is associated with a configuration of activated proximity sensors.
p-0017<figref idrefs="DRAWINGS">FIG. 13</figref> is a flow chart illustrating an operation in which the mobile platform <b>100</b> can determine the position of the mobile platform in a low power mode based on the configuration of activated proximity sensors.
p-0018<figref idrefs="DRAWINGS">FIG. 14</figref> is a flow chart that illustrates controlling the operation of the mobile platform <b>100</b> to run specific applications based on gestures detected by proximity sensors.
p-0019<figref idrefs="DRAWINGS">FIGS. 15 and 16</figref>, by way of example, illustrate the signature of such a sequence of taps, in which a user is sitting and standing, respectively, while the mobile platform is held in the user's pocket.
p-0020<figref idrefs="DRAWINGS">FIG. 17</figref> illustrates a user double tapping the mobile platform through a protector, such as fabric or plastic that may be part of a pocket or mobile platform holder.
p-0021<figref idrefs="DRAWINGS">FIG. 18</figref> illustrates a user producing a counter-clockwise “C” gesture over the mobile platform through a protector, such as fabric or plastic that may be part of a pocket or mobile platform holder.
p-0022<figref idrefs="DRAWINGS">FIG. 19</figref> is a state diagram illustrating one possible analysis of the proximity sensors and the function or operation associated with the different configurations.
p-0023<figref idrefs="DRAWINGS">FIG. 20</figref> is similar to <figref idrefs="DRAWINGS">FIG. 19</figref>, but shows a state diagram illustrating a possible analysis of the configurations of proximity sensors shown in <figref idrefs="DRAWINGS">FIG. 6</figref> and the function or operation associated with the different configurations.
DETAILED DESCRIPTION
p-0024<figref idrefs="DRAWINGS">FIGS. 1A and 1B</figref> illustrate a front side and a back side, respectively, of a portable electronic device, referred to herein as a mobile platform <b>100</b>. The mobile platform <b>100</b> is illustrated as including a housing <b>101</b> and a touch screen display <b>102</b> on the front, as well as a speaker <b>104</b> and microphone <b>106</b>, which may be used when the mobile platform is a cellular telephone. The mobile platform <b>100</b> may include orientation sensor <b>108</b>, such as accelerometers as well as a camera <b>110</b> or ambient light detector, shown in <figref idrefs="DRAWINGS">FIG. 1B</figref>. The mobile platform <b>100</b> further includes a plurality of proximity sensors, generally labeled <b>120</b>, mounted on the housing <b>101</b> of the mobile platform. <figref idrefs="DRAWINGS">FIGS. 1A and 1B</figref> illustrate a plurality of proximity sensors <b>120</b>, i.e., five sensors, mounted on the back side of the housing (proximity sensors labeled <b>120</b><sub>gtl</sub>, <b>120</b><sub>gtr</sub>, <b>120</b><sub>gbl</sub>, <b>120</b><sub>gbr</sub>, and <b>120</b><sub>gbase</sub>.). The mobile platform <b>100</b> is also shown as including two proximity sensors on the left side (when viewed from the back as illustrated in <figref idrefs="DRAWINGS">FIG. 1B</figref>) (proximity sensors labeled <b>120</b><sub>stl </sub>and <b>120</b><sub>sbl</sub>) and two proximity sensors on the right side (proximity sensors labeled <b>120</b><sub>str </sub>and <b>120</b><sub>sbr</sub>), and one proximity sensor on the front side (proximity sensors labeled <b>120</b><sub>ftc</sub>). <figref idrefs="DRAWINGS">FIG. 1A</figref> also illustrates X, Y, and Z axes of the mobile platform <b>100</b>. As used herein, portrait and landscape refer to orientations of the mobile platform <b>100</b> when the Y axis and the X axis, respectively, are approximately aligned vertically, i.e., the direction of gravity. Moreover, as used herein, a horizontal orientation and a vertical orientation of the mobile platform <b>100</b> respectively refer to holding the mobile platform <b>100</b> with the Z axis approximately parallel with and perpendicular to the direction of gravity.
p-0025As used herein, a mobile platform refers to any portable electronic device such as a cellular or other wireless communication device, personal communication system (PCS) device, personal navigation device (PND), Personal Information Manager (PIM), Personal Digital Assistant (PDA), laptop or other suitable mobile device. The mobile platform may be capable of receiving wireless communication and/or navigation signals, such as navigation positioning signals. The term “mobile platform” is also intended to include devices which communicate with a personal navigation device (PND), such as by short-range wireless, infrared, wireline connection, or other connection—regardless of whether satellite signal reception, assistance data reception, and/or position-related processing occurs at the device or at the PND. Also, “mobile platform” is intended to include all devices, including wireless communication devices, computers, laptops, etc. which are capable of communication with a server, such as via the Internet, WiFi, or other network, and regardless of whether satellite signal reception, assistance data reception, and/or position-related processing occurs at the device, at a server, or at another device associated with the network. Any operable combination of the above are also considered a “mobile platform.”
p-0026The proximity sensors <b>120</b> may be capacitive proximity sensors, such as Ultra Low Power Proximity (ULPP) by Ident Technology AG, in Germany, or Capacitive Sensing with MCU C8051F70x plus PCB traces by Silicon Laboratories, Inc., in Austin, Tex. Capacitive proximity sensors may create an electric field by alternating the charge on a conductive plate and use electrodes to measure disturbances in that field. For example, as illustrated in <figref idrefs="DRAWINGS">FIG. 2A</figref>, two electrodes <b>92</b> and <b>94</b> are used in the form of concentric circles. The electrodes <b>92</b> and <b>94</b> are oppositely charged to form a capacitor with an electrostatic field <b>96</b>. When user <b>91</b> nears the electrodes <b>92</b> and <b>94</b>, a disruption in the electrostatic field <b>96</b> can be detected. Other shapes of electrodes, as well as other relationships between the electrodes may be used. For example, <figref idrefs="DRAWINGS">FIG. 2B</figref> illustrates two separated electrodes <b>93</b> and <b>95</b> with field lines <b>97</b> between them. User <b>91</b> is detected when the user disrupts the electrostatic field <b>97</b>. The sensitivity of the proximity sensor may be adjusted as desired to detect the presence of a user up to several inches away from the electrodes <b>93</b> and <b>94</b>. However, it may be desirable to limit the sensitivity of the proximity sensors <b>120</b> used with mobile platform <b>100</b> to detect a user from 0-3 cm. As illustrated in <figref idrefs="DRAWINGS">FIG. 2B</figref>, the user <b>91</b> is detected when the user is near both of the electrodes <b>93</b> and <b>94</b>. Thus, each electrode <b>93</b> and <b>95</b> acts as a proximity sensor, i.e., detecting the presence of the user <b>91</b> when near the electrode, however, both electrodes in the pair must be activated by the presence of the user <b>91</b> to “close the circuit” between the pair of electrodes in order to trigger a signal. Accordingly, the separated electrodes <b>93</b> and <b>95</b> are each sometimes referred to herein as proximity sensors. <figref idrefs="DRAWINGS">FIG. 2C</figref> illustrates an example of a surface capacitive proximity sensor that includes a single electrode <b>98</b> with a positive charge. When user <b>91</b> nears the electrode <b>98</b>, the effect of the small negative charge on the user <b>91</b> on the positively charged electrode <b>98</b> can be detected. The electrodes can be created using wires, metallic foil, conductive paint, and other conductive material which can create an electrostatic field <b>96</b>, which allows such system to be placed anywhere on the housing <b>101</b> of the mobile platform <b>100</b>. Moreover, the electrodes may be placed inside the housing <b>101</b> or on a thin layer on the outside of the housing <b>101</b> so that the user cannot feel the electrodes of the proximity sensors <b>120</b>. Thus, it should be understood that proximity sensors <b>120</b> are shown herein as objects raised from the housing <b>101</b> in order to illustrate possible placement of the proximity sensors <b>120</b> on the housing <b>101</b> and that the proximity sensors <b>120</b> in fact may not be seen or felt by a user.
p-0027When an object nears the surface, but not necessarily contacts the surface, the object serves as a dielectric and modifies the measured capacitance. Thus, objects such as human skin that pass through the field are detected and activate the capacitive proximity sensor. The closer the object comes to the electrodes, the greater the effect on the capacitive proximity sensor, but contact is not always necessary. Thus, objects such as fingers may be detected at a distance, e.g., 0-3 cm or more, from the capacitive proximity sensor. Moreover, with calibration, a conductive object, such as a finger, may be detected through clothing, plastic or similar materials, permitting detection of the object when the mobile platform <b>100</b> is held in a pocket or holder.
p-0028While capacitive proximity sensors are discussed herein, it should be understood that non-capacitive based proximity sensors may be used as well. For example, proximity sensors <b>120</b> may be based on light, such as infra-red based proximity sensors QuickSense™ Si1102 by Silicon Laboratories, Inc., temperature, sound, such as ultrasound, or pressure, e.g., such as push buttons. Thus, while proximity sensors <b>120</b> will sometimes referred to herein as capacitive proximity sensors, it should be understood that other types of proximity sensors may be used, unless specifically stated otherwise.
p-0029A different number of proximity sensors <b>120</b> or a different configuration of proximity sensors <b>120</b> on the housing <b>101</b> may be used if desired. For example, <figref idrefs="DRAWINGS">FIGS. 3A</figref>, <b>3</b>B, <b>3</b>C, and <b>3</b>D illustrate a different configuration of proximity sensors <b>120</b> that may be used on the front side, left side, back side, and right side, respectively. As can be seen in <figref idrefs="DRAWINGS">FIG. 3A</figref>, the mobile platform <b>100</b> may have no proximity sensor mounted on the front side. If desired, the proximity sensors mounted on the left side (proximity sensors labeled <b>120</b><sub>stl </sub>and <b>120</b><sub>sbl </sub>in <figref idrefs="DRAWINGS">FIG. 3B</figref>) and the right side (proximity sensor labeled <b>120</b><sub>scr </sub>in <figref idrefs="DRAWINGS">FIG. 3D</figref>) may have a slight forward bias so that the side proximity sensors <b>120</b> may be used for proximity sensing in the forward direction as well. Moreover, instead of five proximity sensors on the back side of the housing <b>101</b>, as illustrated in <figref idrefs="DRAWINGS">FIG. 1B</figref>, only three proximity sensors (labeled <b>120</b><sub>gtr</sub>, <b>120</b><sub>gbr</sub>, and <b>120</b><sub>gcl</sub>) may be used, as illustrated in <figref idrefs="DRAWINGS">FIG. 3C</figref>. If desired, fewer proximity sensors or a different configuration of proximity sensors may be mounted on the back side of the housing <b>101</b> of the mobile platform <b>100</b>, as illustrated by proximity sensors <b>120</b><sub>gt </sub>and <b>120</b><sub>gb </sub>in <figref idrefs="DRAWINGS">FIG. 3E</figref>. In the example shown in <figref idrefs="DRAWINGS">FIG. 3E</figref>, a vertical line gesture down the center of the mobile platform <b>100</b> would be detected as serial activation of proximity sensors <b>120</b><sub>gt</sub>, <b>120</b><sub>gb</sub>, <b>120</b><sub>gt</sub>, and <b>120</b><sub>gb</sub>, while a horizontal line gesture from left to right across the center of the mobile platform would be detected as activation of proximity sensor <b>120</b><sub>gb </sub>followed by proximity sensor <b>120</b><sub>gt</sub>.
p-0030<figref idrefs="DRAWINGS">FIGS. 4A and 4B</figref> illustrate the front and back of a mobile platform <b>100</b> with another configuration of proximity sensors <b>120</b> that may be used on the front side and back side of the housing <b>101</b>, respectively. As illustrated the proximity sensors <b>120</b><sub>str </sub>and <b>120</b><sub>stl </sub>may be positioned on the sides near the corners and proximity sensors <b>120</b><sub>scr </sub>and <b>120</b><sub>scl </sub>may be positioned on the sides near the center. If desired, an additional sensor may be included, such as a proximity sensor <b>120</b><sub>t </sub>positioned on the top side of the mobile platform <b>100</b>. The proximity sensor <b>120</b><sub>t </sub>may be positioned at a location that is not near the camera <b>110</b>, as illustrated in <figref idrefs="DRAWINGS">FIG. 4B</figref>, so that when a user activates proximity sensor <b>120</b><sub>t</sub>, the camera <b>110</b> is not blocked by the user's finger. The configuration of proximity sensors <b>120</b> that are activated may be used to quickly identify how the user wishes to use the mobile platform <b>100</b>, e.g., in a camera application (or in any other configured application). For example, with the corner proximity sensors <b>120</b><sub>str </sub>and <b>120</b><sub>stl </sub>both activated, without activation of side proximity sensors <b>120</b><sub>scr </sub>or <b>120</b><sub>scl</sub>, the mobile platform <b>100</b> is being held by at least the top corners, which is a normal way to hold a mobile platform during use as a camera in landscape mode. If the top proximity sensor <b>120</b><sub>t </sub>is activated, without activation of corner proximity sensors <b>120</b><sub>str </sub>or <b>120</b><sub>stl</sub>, the mobile platform <b>100</b> is being in a manner consistent with a camera application in portrait mode. Accordingly, when either the top proximity sensor <b>120</b><sub>t </sub>is activated or the corner proximity sensors <b>120</b><sub>str </sub>and <b>120</b><sub>stl </sub>are both activated, without activation of other proximity sensors <b>120</b>, the camera application may be automatically launched. Additionally, if the side proximity sensors <b>120</b><sub>scr </sub>and <b>120</b><sub>scl </sub>are activated, along with the front proximity sensor <b>120</b><sub>ftc</sub>, the mobile platform is likely being used in a telephone type application, and appropriate applications or functions may be automatically launched, such as dimming or disabling the display <b>102</b>, altering the ringer, etc.
p-0031<figref idrefs="DRAWINGS">FIGS. 5A and 5B</figref> illustrate the front and back of a mobile platform <b>100</b> with another configuration of proximity sensors <b>120</b> that may be used on the front side and back side respectively. The proximity sensors illustrated in <figref idrefs="DRAWINGS">FIGS. 5A and 5B</figref> are similar to the capacitive proximity sensors illustrated in <figref idrefs="DRAWINGS">FIG. 2B</figref>. with the electrode plates of separated with one electrode labeled “-tx” and the electrode labeled “-rx”. Each electrode acts as a proximity sensor, i.e., detecting the presence of the user's hand/finger at the electrode, however, both electrodes in the pair must be activated by the presence of the user to “close the circuit” between the pair of electrodes in order to trigger a signal. For example, in the center of both sides, electrodes forming proximity sensors <b>120</b><sub>B-tx</sub>, and <b>120</b><sub>B1-rx</sub>, are paired, while on the upper corners of the sides, electrodes forming proximity sensors <b>120</b><sub>A-tx </sub>and <b>120</b><sub>A1-rx </sub>are paired. Additionally, the electrode forming proximity sensor <b>120</b><sub>A2-rx </sub>on the top corner may also be paired with proximity sensor <b>120</b><sub>A-tx</sub>, so that touching proximity sensor <b>120</b><sub>A-tx </sub>along with either proximity sensor <b>120</b><sub>A1-rx </sub>or <b>120</b><sub>A2-rx </sub>will result in the triggering a signal. Similarly, the front of the housing <b>101</b> may include electrodes forming paired proximity sensors <b>120</b><sub>F-tx </sub>and <b>120</b><sub>F-rx</sub>, which are paired, as well as another proximity sensor <b>120</b><sub>B2-rx</sub>, that is paired with proximity sensor <b>120</b><sub>B-tx</sub>, on the side of the housing <b>101</b>. On the back side of the housing <b>101</b>, as shown in <figref idrefs="DRAWINGS">FIG. 5B</figref>, one proximity sensor <b>120</b><sub>G-tx </sub>is paired with both proximity sensors <b>120</b><sub>G1-rx </sub>and <b>120</b><sub>G2-rx</sub>. Other combinations or pairs of proximity sensors are possible, for example, the back surface of the mobile platform may include additional proximity sensors. The benefit of the sensors shown in <figref idrefs="DRAWINGS">FIGS. 5A and 5B</figref> is that keys and coins in the pocket will not falsely activate the proximity sensors.
p-0032<figref idrefs="DRAWINGS">FIG. 6</figref> illustrates another configuration of proximity sensors <b>120</b> on the housing <b>101</b> of the mobile platform <b>100</b>. <figref idrefs="DRAWINGS">FIG. 6</figref> is similar to <figref idrefs="DRAWINGS">FIGS. 5A and 5B</figref>, with the electrodes for the proximity sensors separated, where each electrode acts as a proximity sensor, but requires the presence of the user's hand/finger at each electrode to trigger a signal. <figref idrefs="DRAWINGS">FIG. 6</figref> illustrates paired proximity sensors on the same side i.e., left side and right side, of the housing <b>101</b> of the mobile platform <b>100</b>. For example, paired proximity sensors <b>120</b><sub>A-tx</sub>, and <b>120</b><sub>A-rx </sub>(sometimes collectively referred to as proximity sensors <b>120</b><sub>A</sub>) are located on the upper corners of the housing <b>101</b>, while paired proximity sensors <b>120</b><sub>C-tx </sub>and <b>120</b><sub>C-rx</sub>, (sometimes collectively referred to as proximity sensors <b>120</b>) are located on the lower corners of the housing <b>101</b>. If desired, additional proximity sensor pairs may be present, such as paired proximity sensors <b>120</b><sub>B-tx</sub>, and <b>120</b><sub>B-rx </sub>(sometimes collectively referred to as proximity sensors <b>120</b><sub>B</sub>) located in the center of the sides and front proximity sensors <b>120</b><sub>F-tx</sub>, and <b>120</b><sub>F-rx </sub>(sometimes collectively referred to as proximity sensors <b>120</b><sub>F</sub>). The back side may have a configuration of proximity sensors similar to that shown in <figref idrefs="DRAWINGS">FIG. 5B</figref>, or any other configuration, such as shown in <figref idrefs="DRAWINGS">FIG. 1B</figref>, <b>3</b>C, or <b>3</b>E. The configuration of proximity sensors <b>120</b> and, optionally, data from the orientation sensor <b>108</b> may be used together to quickly identify how the user wishes to use the mobile platform <b>100</b>, e.g., in a camera application or in an SMS or texting type application (or in any other configured application) based on the configuration of activated proximity sensors <b>120</b>. For example, with the corner proximity sensors <b>120</b><sub>A </sub>and <b>120</b><sub>C </sub>activated, without activation of side proximity sensors <b>120</b>, it is known that the mobile platform <b>100</b> is being held by the corners, which is a normal way to hold a mobile platform during use as a camera or SMS application. With the addition of data from the orientation sensor <b>108</b>, it can be determined if the mobile platform <b>100</b> is being used as a camera or for texting, i.e., if the mobile platform <b>100</b> is held approximately vertically (with the Z axis shown in <figref idrefs="DRAWINGS">FIG. 1A</figref> perpendicular to the direction of gravity), the mobile platform <b>100</b> is most likely being used as a camera, and if the mobile platform <b>100</b> is held approximately horizontally (with the Z axis shown in <figref idrefs="DRAWINGS">FIG. 1A</figref> parallel to the direction of gravity), the mobile platform <b>100</b> is most likely being used for texting. Accordingly, the camera or SMS applications can be automatically launched based on the configuration of activated proximity sensors <b>120</b>. Which applications are launched in response to a particular configuration may be user configurable. For example, the camera application may be automatically launched when the mobile platform is held in one or both of landscape mode or portrait mode. It may be desirable to limit the automatic launch of the camera application to landscape mode to prevent an inadvertent launch of the camera application while, e.g., holding the mobile platform as a telephone. If desired, in camera mode, an image may be captured automatically after a pre-defined time, e.g., 3 seconds, so that the user does not need to remove a finger from the mobile platform <b>100</b>. Additionally or alternatively, once the camera application or SMS application is launched, the mobile platform <b>100</b> may remain in the application for a pre-defined period of time, e.g., 3 seconds, after one or more of the proximity sensors <b>120</b> are deactivated, which permits a user to remove a finger from a proximity sensor <b>120</b> to interface with the mobile platform <b>100</b>, e.g., to capture an image by tapping the display <b>102</b>. If the side proximity sensors <b>120</b><sub>C </sub>are activated along with the corner proximity sensors <b>120</b><sub>A </sub>and <b>120</b><sub>C</sub>, then the mobile platform <b>100</b> is not held by the corners, and accordingly, the camera or SMS applications are not automatically launched.
p-0033Moreover, using multiple proximity sensors, e.g., on the back of the housing <b>101</b> as illustrated, e.g., in <figref idrefs="DRAWINGS">FIG. 1B</figref>, and by monitoring which proximity sensors <b>120</b> are activated and when (i.e., the order that the proximity sensors <b>120</b> are activated), gestures may be detected with the proximity sensors. For example, referring to <figref idrefs="DRAWINGS">FIG. 1B</figref>, a clockwise circle gesture can be detected when proximity sensors <b>120</b><sub>gtl</sub>, <b>120</b><sub>gtr</sub>, <b>120</b><sub>gbr</sub>, <b>120</b><sub>gbl </sub>and <b>120</b><sub>gtl </sub>are sequentially activated. Examples of possible gestures that may be detected using proximity sensors <b>120</b> on the back side of the housing <b>101</b> and examples of mobile platform <b>100</b> functions that may be associated with the gestures are shown in the following Table.
p-0034<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="28pt" align="left" /><colspec colname="1" colwidth="91pt" align="left" /><colspec colname="2" colwidth="98pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="2" rowsep="1">TABLE 1</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>Gesture</entry><entry>Function</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>Clockwise</entry><entry>Increase volume</entry></row><row><entry /><entry>Counter-Clockwise</entry><entry>Decrease volume</entry></row><row><entry /><entry>Swipe Up</entry><entry>Provide number of emails</entry></row><row><entry /><entry /><entry>in inbox</entry></row><row><entry /><entry>Swipe Down</entry><entry>Provide number of SMSs</entry></row><row><entry /><entry>Swipe Left</entry><entry>Mute Call</entry></row><row><entry /><entry>Swipe Right</entry><entry>Answer Call</entry></row><row><entry /><entry>FIG. 8</entry><entry>Email people with</entry></row><row><entry /><entry /><entry>message, e.g., people</entry></row><row><entry /><entry /><entry>attending current meeting</entry></row><row><entry /><entry /><entry>that will be late</entry></row><row><entry /><entry>Letter “C” followed by</entry><entry>Call person designated by</entry></row><row><entry /><entry>additional gesture</entry><entry>additional gesture</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
p-0035<figref idrefs="DRAWINGS">FIG. 7</figref> is a block diagram of a mobile platform <b>100</b> that may provide a user interface using proximity sensors. The mobile platform <b>100</b> includes a means for sensing gestures, such as proximity sensors <b>120</b>, which may be multiple capacitive proximity sensors or other types of proximity sensors, mounted on the housing <b>101</b> of the mobile platform <b>100</b> as described above. The mobile platform <b>100</b> may also include a means for determining the orientation of the mobile platform <b>100</b>, i.e., whether the mobile platform <b>100</b> is being held vertically, horizontally, in portrait mode, in landscape mode etc, such as orientation sensor <b>108</b>, which may be, e.g., accelerometers and/or gyroscopes. Mobile platform <b>100</b> may also include a camera or ambient light detector <b>110</b>. Mobile platform <b>100</b> may also include a wireless transceiver <b>140</b>, which may be, e.g., a cellular modem or a wireless network radio receiver/transmitter that is capable of sending and receiving communications to and from a cellular tower. Mobile platform <b>100</b> also includes a user interface that includes a display <b>102</b>, which may be a touch screen display, and may include a keypad <b>107</b> or other input device through which the user can input information into the mobile platform <b>100</b>. In one embodiment, the keypad <b>107</b> may be integrated into the display <b>102</b>, such as a touch screen display. The user interface may also include, e.g., a speaker <b>104</b> and microphone <b>106</b>, e.g., when the mobile platform <b>100</b> is a cellular telephone. Additionally, the orientation sensor <b>108</b> may be used as the user interface by detecting user commands in the form of gestures.
p-0036The proximity sensors <b>120</b>, orientation sensor <b>108</b>, ambient light detector <b>110</b>, display <b>102</b>, and wireless transceiver <b>140</b> are connected to and communicate with a mobile platform control unit <b>150</b>. The mobile platform control unit <b>150</b> accepts and processes data from the proximity sensors <b>120</b>, orientation sensor <b>108</b>, ambient light detector <b>110</b>, display <b>102</b> and wireless transceiver <b>140</b> and controls the operation of the devices. The mobile platform control unit <b>150</b> may be provided by a processor <b>152</b> and associated memory <b>154</b>, hardware <b>156</b>, software <b>158</b>, and firmware <b>157</b>. The mobile platform control unit <b>150</b> may also include display controller <b>160</b> that controls the data shown on the display <b>102</b>, a touch screen controller <b>162</b> that accepts data and controls the function of the touch screen function of the display <b>102</b> (if included), and a proximity sensor controller <b>164</b> that accepts data from and controls the function of the proximity sensors <b>120</b>. Additionally, the mobile platform control unit <b>150</b> may include a low power microcontroller <b>166</b>, which is coupled to the proximity sensors <b>120</b>. The low power microcontroller <b>166</b> monitors the proximity sensors <b>120</b>, e.g., while the mobile platform <b>100</b> is in low power mode, i.e., sleep mode, until proximity sensor <b>120</b> is activated. Once low power microcontroller <b>166</b> determines that a proximity sensor <b>120</b> is activated, the low power microcontroller <b>166</b> wakes the system to begin monitoring any other desired sensors that are more power intensive, such as the light detector <b>110</b>, orientation sensor <b>108</b>, touch screen display <b>102</b>, etc. The controllers <b>160</b>, <b>162</b>, <b>164</b>, <b>166</b> are illustrated separately from each other and processor <b>152</b> for clarity, but, it should be understood that one or more of the controllers may be combined or may be within the processor <b>152</b>, implemented via software <b>158</b>, hardware <b>156</b>, or firmware <b>157</b>. It will be understood as used herein that the processor <b>152</b> can, but need not necessarily include, one or more microprocessors, embedded processors, controllers, application specific integrated circuits (ASICs), digital signal processors (DSPs), and the like. The term processor is intended to describe the functions implemented by the system rather than specific hardware. Moreover, as used herein the term “memory” refers to any type of computer storage medium, including long term, short term, or other memory associated with the mobile platform, and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.
p-0037The methodologies described herein may be implemented by various means depending upon the application. For example, these methodologies may be implemented in hardware <b>156</b>, firmware <b>157</b>, software <b>158</b>, or any combination thereof. For a hardware implementation, the processing units may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or a combination thereof.
p-0038For a firmware and/or software implementation, the methodologies may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine-readable medium tangibly embodying instructions may be used in implementing the methodologies described herein. For example, software codes may be stored in memory <b>154</b> and executed by the processor <b>152</b>. Memory may be implemented within the processor unit or external to the processor unit. As used herein the term “memory” refers to any type of long term, short term, volatile, nonvolatile, or other memory and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.
p-0039For example, software <b>158</b> codes may be stored in memory <b>154</b> and executed by the processor <b>152</b> and may be used to run the processor and to control the operation of the mobile platform <b>100</b> as described herein. A program code stored in a computer-readable medium, such as memory <b>154</b>, may include program code to determine a configuration of activated capacitive proximity sensors and to control the operation of the mobile platform based on the determined configuration including but not limited to any of the methodologies described herein. If implemented in firmware and/or software, the functions may be stored as one or more instructions or code on a computer-readable medium. Examples include computer-readable media encoded with a data structure and computer-readable media encoded with a computer program. Computer-readable media includes physical computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer; disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
p-0040With proximity sensors <b>120</b> configured on the housing <b>101</b> of the mobile platform <b>100</b>, as described herein, many different functions or applications may be controlled based on which proximity sensors <b>120</b> are activated and when they are activated. For example, power saving functions are possible, such as placing the mobile platform <b>100</b> in low power mode (sleep mode) when the device is not held or awakening when held. Moreover, the intended use of the mobile platform <b>100</b> may be determined based on how the mobile platform <b>100</b> is being held (as determined by the activated proximity sensors <b>120</b> as well as orientation sensor <b>108</b>, if desired) and running the appropriate application. Further, a user may be permitted to control device functions, such as volume control, answering phone, etc., while the mobile platform <b>100</b> is in the user's pocket or a holder. Cost savings can be achieved by eliminating other elements, such as an IR based proximity sensor to detect the user's ear during a telephone call or a mute button, which can be enabled based on the status and position of the mobile platform <b>100</b> as determined by the capacitive proximity sensors.
p-0041<figref idrefs="DRAWINGS">FIG. 8</figref> is a flow chart illustrating using a plurality of proximity sensors on the housing of the mobile platform as a user interface to automatically control the operation of the mobile platform. As illustrated, signals from a plurality of proximity sensors coupled to a housing of a mobile platform are monitored (<b>190</b>). When signals are detected, indicated that one or more of the proximity sensors have been activated by the presence of, e.g., the user's hand or finger, the signals are analyzed to determine the configuration of the activated proximity sensors (<b>192</b>). The configuration of activated proximity sensors may be based on the location of the proximity sensors, e.g., proximity sensors located near the corners of the housing are activated indicating that the mobile platform is being used as a camera or in an SMS or texting application, or proximity sensors along the center of the sides and on the front of the housing are activated indicating that the mobile platform is being used as a phone. Other configurations are possible, including configurations that provide information with respect to the orientation of the mobile platform when held in the user's pocket or a mobile platform holder. Additionally, or alternatively, the configuration of activated proximity sensors may be based on the sequence of activation of the proximity sensors. For example, by determining the sequence that proximity sensors are activated on the back of the housing, simple gestures can be detected. Additionally, signals from other sensors, such as the orientation sensor <b>108</b> or light detector <b>110</b> may be analyzed. It is then determined if a mobile platform application is associated with the configuration of activated proximity sensors (<b>194</b>) and if so, the mobile platform is controlled to run the application associated with the configuration (<b>196</b>). Applications that may be run include a camera application or SMS application, as well as controlling telephony operation (e.g., answering or controlling the volume), controlling a music player (e.g., controlling the volume, changing songs, repeating), and providing status information (e.g., how many voice mails or emails). The applications that may be automatically launched in response to the configuration of activated proximity sensors may be user configurable.
p-0042By way of example, referring to <figref idrefs="DRAWINGS">FIG. 6</figref>, if the configuration of activated proximity sensors includes proximity sensors <b>120</b><sub>A </sub>and <b>120</b><sub>C</sub>, but not of side proximity sensors <b>120</b><sub>B</sub>, the configuration indicates that the mobile platform <b>100</b> is held by the corners. Typically, a mobile platform <b>100</b> is held by the corners during camera or SMS type applications. Thus, a camera application and/or SMS application may be associated with this configuration of activated proximity sensors. Additionally, data from other sensors, such as the orientation sensor may be used to assist in determining which application to run. For example, if the mobile platform <b>100</b> is held approximately horizontally (with the Z axis shown in <figref idrefs="DRAWINGS">FIG. 1A</figref> parallel to the direction of gravity), the SMS application may be associated with the configuration of activated proximity sensors. On the other hand, if the mobile platform <b>100</b> is held approximately vertically (with the Z axis shown in <figref idrefs="DRAWINGS">FIG. 1A</figref> perpendicular to the direction of gravity), the camera application may be associated with the configuration of activated proximity sensors. While running the camera (or any other desired) application, the mobile platform may continue to run the application despite a change in the configuration of activated proximity sensors. For example, in a camera application, the user may move a finger from a corner of the mobile platform <b>100</b> in order to manually capture an image, e.g., by tapping the touch screen display <b>102</b>. Accordingly, the mobile platform <b>100</b> should remain in the camera mode until manually deactivated or for a pre-defined period of time, e.g., 3-5 seconds, which may be user configurable, which is sufficient for the user to complete the desired action and re-grip the mobile platform <b>100</b>. Additionally, if desired, the camera application may include an automatic image capture, i.e., a counter internal to, e.g., processor <b>152</b>, is automatically started along with the camera application and the image is captured after the elapse of a pre-defined period of time, e.g., 3 seconds, which may be user configurable. Thus, after launching the camera application in response to the configuration of activated proximity sensors, the mobile platform automatically captures an image without requiring user interaction. Thus, an image may be captured easily and quickly.
p-0043Another example, again referring to <figref idrefs="DRAWINGS">FIG. 6</figref>, is where the side proximity sensors <b>120</b><sub>C-tx</sub>, <b>120</b><sub>C-rx</sub>, and the front proximity sensors <b>120</b><sub>F </sub>are activated. In this configuration of activated proximity sensors, it is likely that a user is using the mobile platform <b>100</b> as a telephone. Thus, telephony type operations, such as controlling the volume or the ringer, or turning off the display or disabling the touch screen sensors, may be associated with this configuration of activated proximity sensors.
p-0044<figref idrefs="DRAWINGS">FIG. 9</figref> is a flow chart illustrating a possible wake up function that may be implemented using the capacitive proximity sensors <b>120</b>. As illustrated, while the mobile platform is in low power (sleep mode), signals from the proximity sensors <b>120</b> are monitored (<b>202</b>) e.g., using the low power microcontroller <b>166</b> shown in <figref idrefs="DRAWINGS">FIG. 7</figref>. If signals from at least two side sensors are detected (<b>204</b>) (e.g., <b>120</b><sub>sbl </sub>and <b>120</b><sub>sbr </sub>in <figref idrefs="DRAWINGS">FIG. 1A</figref> or <b>120</b><sub>scr </sub>and <b>120</b><sub>sbl </sub>in <figref idrefs="DRAWINGS">FIG. 3A</figref>, or <b>120</b><sub>scr </sub>and <b>120</b><sub>scl </sub>in <figref idrefs="DRAWINGS">FIG. 4A</figref>, <b>120</b><sub>B-tx </sub>and <b>120</b><sub>B1-rx</sub>, in <figref idrefs="DRAWINGS">FIG. 5A</figref>, or <b>120</b><sub>B </sub>in <figref idrefs="DRAWINGS">FIG. 6</figref>) the mobile platform wakes up (206), i.e., comes out of low power mode, otherwise, the mobile platform continues to monitor for signals from the proximity sensors <b>120</b>.
p-0045<figref idrefs="DRAWINGS">FIG. 10</figref> is a flow chart illustrating a possible low power (sleep) function that may be implemented using the capacitive proximity sensors <b>120</b>. As illustrated, while the mobile platform <b>100</b> is in wake mode, signals from the proximity sensors <b>120</b> are monitored (<b>212</b>). If signals from at least two side sensors are detected (<b>214</b>), the mobile platform remains in wake mode and continues to monitor signals from the proximity sensors <b>120</b>; otherwise, the mobile platform goes into low power (sleep) mode (<b>216</b>). If desired, the sleep mode may be activated immediately when signals from the side sensors are no longer detected or after a designated amount of time, e.g., 5 seconds, 30 seconds, 1 minute, etc.
p-0046<figref idrefs="DRAWINGS">FIG. 11</figref> is a flow chart illustrating a function in which the touch screen display <b>102</b> is disabled based on signals from the capacitive proximity sensors <b>120</b>, while the mobile platform is used as a phone. As illustrated, while the mobile platform <b>100</b> is in use, e.g., as a phone, signals from the proximity sensors <b>120</b> are monitored (<b>222</b>). If a signal is detected from the front proximity sensor, e.g., <b>120</b><sub>ftc </sub>shown in <figref idrefs="DRAWINGS">FIG. 1A</figref>, (<b>224</b>), the touch screen display <b>102</b> is disabled (<b>226</b>). If desired, additional proximity sensors <b>120</b> may need to be activated to deactivate the touch screen display <b>102</b>. For example, the touch screen display <b>102</b> may be disabled if signals are detected from a front proximity sensor as well as at least two side proximity sensors.
p-0047<figref idrefs="DRAWINGS">FIG. 12</figref> is a flow chart illustrating controlling the operation of the mobile platform <b>100</b> to run an application that is associated with a configuration of activated proximity sensors <b>120</b>. As illustrated, while the mobile platform <b>100</b> is in wake mode, signals from the proximity sensors <b>120</b> are monitored (<b>232</b>). If signals from proximity sensors <b>120</b> are received, i.e., proximity sensors are activated, the configuration of the activated proximity sensors <b>120</b> is analyzed to determine if the configuration is associated with an application (<b>234</b>). Additional information may be used as well, such as data from the orientation sensor <b>108</b>, which may indicate the position that the mobile platform is held, i.e., vertically, horizontally, landscape, portrait, etc. For example, a camera application may be associated with the activation of the proximity sensors on the sides of the mobile platform (e.g., <b>120</b><sub>stl</sub>, <b>120</b><sub>sbl</sub>, <b>120</b><sub>str</sub>, and <b>120</b><sub>sbr </sub>in <figref idrefs="DRAWINGS">FIG. 1A</figref> or proximity sensor <b>120</b><sub>A </sub>and <b>120</b><sub>C </sub>as shown in <figref idrefs="DRAWINGS">FIG. 6</figref>), while no other proximity sensors <b>120</b> are activated, and optionally, if the orientation sensor <b>108</b> indicates that the mobile platform <b>100</b> is held vertically in, e.g., landscape or portrait mode. If desired, the camera may be associated with only two proximity sensors <b>120</b> on the sides of the mobile platform <b>100</b> activated (one proximity sensor on each side) while in landscape mode, e.g., <b>120</b><sub>stl </sub>and <b>120</b><sub>str </sub>in <figref idrefs="DRAWINGS">FIGS. 1A and 4A</figref> or <b>120</b><sub>A-tx</sub>, and <b>120</b><sub>A1-rx</sub>, in <figref idrefs="DRAWINGS">FIG. 5A</figref>. Where four proximity sensors <b>120</b> on the sides are used, the camera application should not disable when the user removes a finger from a proximity sensor <b>120</b> to touch the touch screen display <b>102</b>. If desired, when the mobile platform <b>100</b> is held vertically in portrait mode, as indicated by orientation sensor <b>108</b>, activation of proximity sensors <b>120</b> on the top side along with activation of left and/or right side proximity sensors (e.g., proximity censors <b>120</b><sub>t</sub>, <b>120</b><sub>str</sub>, and <b>120</b><sub>stl </sub>in <figref idrefs="DRAWINGS">FIG. 4A</figref> or proximity sensors <b>120</b><sub>A2-rx</sub>, <b>120</b><sub>A-tx </sub>and (optionally <b>120</b><sub>A-rx</sub>) in <figref idrefs="DRAWINGS">FIG. 5A</figref>) may be associated with the camera application as well. Additionally, with information from the orientation sensor <b>108</b> indicating that the mobile platform <b>100</b> is held approximately horizontally in landscape (or portrait mode), along with activation of proximity sensors on the sides, such as <b>120</b><sub>stl</sub>, <b>120</b><sub>sbl</sub>, <b>120</b><sub>str</sub>, and <b>120</b><sub>sbr </sub>in <figref idrefs="DRAWINGS">FIG. 1A</figref> or proximity sensors <b>120</b><sub>A </sub>and <b>120</b><sub>C </sub>as shown in <figref idrefs="DRAWINGS">FIG. 6</figref>, may launch an associated short message service (SMS) application. Additionally, or alternatively, the activation of another proximity sensor <b>120</b> on the back of the housing <b>101</b> of the mobile platform <b>100</b>, along with the activation of the side proximity sensors <b>120</b>, may be used to launch the SMS application without information from the orientation sensor <b>108</b>. Referring back to <figref idrefs="DRAWINGS">FIG. 12</figref>, if the configuration of activated proximity sensors is associated with an application (<b>236</b>) that application is run (<b>238</b>) on the mobile platform <b>100</b>, otherwise monitoring of the proximity sensors <b>120</b> is continued. Other applications to be automatically launched based on the configuration of activated proximity sensors may be used as well.
p-0048<figref idrefs="DRAWINGS">FIG. 13</figref> is a flow chart illustrating an operation in which the mobile platform <b>100</b> can determine the position of the mobile platform <b>100</b>, e.g., in a low power mode, based on the configuration of activated proximity sensors <b>120</b>. The position of the mobile platform may be determined in response to a trigger event, such as a telephone call or incoming message, which brings the mobile platform out of a low power mode. Alternatively, the position of the mobile platform may be determined while in low power mode using, e.g., the low power microcontroller <b>166</b> shown in <figref idrefs="DRAWINGS">FIG. 7</figref> to poll the proximity sensors <b>120</b> and write the results in memory <b>154</b>, which may be obtained by the processor <b>152</b> in response to a trigger event. As illustrated, signals from the proximity sensors <b>120</b> are monitored (<b>242</b>), e.g., while the mobile platform <b>100</b> is in low power (sleep) mode or in response to a trigger event. The position of the mobile platform may be determined based on active proximity sensors (<b>244</b>). Additional information may be used as well, such as data from an ambient light detector <b>110</b> in <figref idrefs="DRAWINGS">FIG. 7</figref>, which may be used to indicate whether the mobile platform is held in a pocket. For example, if a front proximity sensor (<b>120</b><sub>ftc </sub>in <figref idrefs="DRAWINGS">FIG. 1A</figref>) is activated and no other proximity sensors are activated, it is probable that the mobile platform <b>100</b> is held in a user's pocket or a holder with the front side, e.g., touch screen display <b>102</b>, facing the user's body. If the ambient light detector <b>110</b> indicates little or no light (e.g., 10-15 lux), the certainty that the mobile platform <b>100</b> is held in a pocket is increased. Similarly, if the back proximity sensors (<b>120</b><sub>gtl</sub>, <b>120</b><sub>gtr</sub>, <b>120</b><sub>gbl</sub>, <b>120</b><sub>gbr</sub>, and <b>120</b><sub>gbase</sub>) are activated and no other proximity sensors <b>120</b> are activated, it is probable that the mobile platform <b>100</b> is held in a user's pocket or holder with the back side facing the user's body. Additionally, information from the orientation sensor <b>108</b> may be used to determine the orientation of the mobile platform <b>100</b> in the user's pocket, e.g., top up or top down. With the position of the mobile platform <b>100</b> identified, the mobile platform may automatically perform a predefined function in response to an incoming call or message or other stimulus (<b>246</b>). For example, if the mobile platform <b>100</b> is determined to be top-down in a pocket with the touch screen display <b>102</b> facing the user, the mobile platform <b>100</b> may behave as normal for incoming calls or messages. If, however, the device is top-down in a pocket, with the back of the mobile platform <b>100</b> facing the user, then all incoming calls may be sent directly to voice mail. If the mobile platform <b>100</b> is determined to be bottom-up in a pocket with the touch screen display <b>102</b> facing the user, then any incoming calls may be automatically answered with an SMS message, e.g., saying the user is in meeting. If the mobile platform <b>100</b> is determined to be bottom-up in a pocket and the back of the mobile platform <b>100</b> facing the user, incoming calls may be answered with a different SMS message, e.g., requesting that callers contact the user through a different means such as instant messaging. The predefined function that is performed in response to an incoming call or message, or other stimulus, may be user defined, along with the specific positions of the mobile platform <b>100</b> that are associated with each response.
p-0049<figref idrefs="DRAWINGS">FIG. 14</figref> is a flow chart that illustrates controlling the operation of the mobile platform <b>100</b> to run specific applications based on gestures detected by proximity sensors <b>120</b>. As illustrated, signals from the proximity sensors <b>120</b> on the back of the mobile platform are monitored (<b>252</b>). If desired, monitoring of the back proximity sensors may be performed when the mobile platform is determined to in a user's pocket or holder with the touch screen display <b>102</b> facing the user, e.g., when the front proximity sensor is active and optionally the ambient light detector <b>110</b> indicates little or no light (e.g., 10-15 lux), as discussed above. Moreover, if desired, monitoring of the back proximity sensors may be performed in response to a trigger event, such as when a predefined signal from the orientation sensors is received, e.g., the user taps the mobile platform in a specific sequence that is detected by orientation sensor <b>108</b> or one or more of the proximity sensors <b>120</b>. Taps, for example, may be a pre-designated sequence of taps, such as three sets of two taps. <figref idrefs="DRAWINGS">FIGS. 15 and 16</figref>, by way of example, illustrate the signature of such a sequence of taps, in which a user is sitting and standing, respectively, while the mobile platform <b>100</b> is held in the user's pocket. <figref idrefs="DRAWINGS">FIGS. 15 and 16</figref> each include four graphs illustrating the magnitude of acceleration over time in planes defined by the X axis (width of the mobile platform), Y axis (height of the mobile platform), Z axis (depth of the mobile platform) (as illustrated in <figref idrefs="DRAWINGS">FIG. 1A</figref>, and combined axes. The predefined signal from the orientation sensor <b>108</b> may be detected using, e.g., a 40 Hz, sample rate from a <b>3</b>-axis accelerometer, where: 1) a number of samples N have low motion, 2) a smaller number of samples M have high motion, and 3) the magnitude in the Z axis during a tap portion is at least 3× greater than the magnitude on any other axis. Low motion may be determined, e.g., when the magnitude on each of the X, Y, and Z axes is less than a baseline for each of the axes determined over a time period, such as 2-60 seconds. High motion may be determined, e.g., when the magnitude of the combined axes, i.e., sqrt(X<sup>2</sup>+Y<sup>2</sup>+Z<sup>2</sup>) crosses a threshold, e.g., 12 m/s<sup>2</sup>, a desired number of times, e.g., more than 2 times.
p-0050<figref idrefs="DRAWINGS">FIGS. 15 and 16</figref> show that a sequence of three sets of double taps can be clearly identified and used to prompt gesture monitoring. Moreover, a sequence of three sets of double taps avoids false positives that may be caused by normal activity while the mobile platform is in the user's pocket. <figref idrefs="DRAWINGS">FIG. 17</figref> illustrates a user double tapping <b>402</b> the mobile platform <b>100</b> through a protector <b>410</b>, such as fabric or plastic that may be part of a pocket or mobile platform holder. If desired, a proximity sensor, e.g., <b>120</b><sub>gbase</sub>, may be required to be activated in order to monitor for gestures. In the embodiment shown in <figref idrefs="DRAWINGS">FIG. 5B</figref>, <b>120</b><sub>G-tx </sub>must be used in conjunction with <b>120</b><sub>G1-rx</sub>, and <b>120</b><sub>G2-rx</sub>. The use of <b>120</b><sub>gbase </sub>(or <b>120</b><sub>G-tx</sub>) is beneficial as it can be used to hold the mobile platform stationary during gesturing and the user can determine the relative position of the mobile platform.
p-0051The user may produce a gesture over the mobile platform without touching the mobile platform, if desired, with a hand or one or more fingers or other object that will activate the capacitive proximity sensors. The proximity sensors are activated by the presence of the user's fingers and transmit appropriate signals. The signals that are received from the proximity sensors are analyzed to determine the gesture produced, e.g., by determining the configuration of activated proximity sensors including the positions of the proximity sensors and the order in which they are activated. For example, gestures that may be detected include a clockwise circle, counter-clockwise circle, <figref idrefs="DRAWINGS">FIG. 8</figref>, vertical lines, horizontal lines, and large letters, depending on the positions and number of proximity sensors. <figref idrefs="DRAWINGS">FIG. 18</figref>, by way of example, illustrates a user producing a counter-clockwise “C” gesture <b>412</b> over the mobile platform <b>100</b> through a protector <b>410</b>, such as fabric or plastic that may be part of a pocket or mobile platform holder, while activating proximity sensor <b>120</b><sub>gbase</sub>. The configuration of activated proximity sensors <b>120</b>, i.e., the positions of the proximity sensors <b>120</b> and the order in which they are activated, is analyzed to determine if the configuration is associated with a function (<b>254</b>). If the configuration is associated with a function (<b>256</b>), the function is permitted and is performed or launched (<b>258</b>); otherwise, the mobile platform <b>100</b> continues to monitor for signals from the proximity sensors. By way of example, as described in Table 1 above, the volume of the mobile platform may be increased by producing a clockwise circle or decreased with a counter-clockwise circle. The mobile platform may skip to the next song with a swipe in one direction, or re-play the last song with a swipe in another direction. Of course, other gestures and applications may be used, including controlling telephony operation, controlling a music player, and providing status information.
p-0052If desired, one or more of the above described processes may be combined. For example, <figref idrefs="DRAWINGS">FIG. 19</figref> is a state diagram illustrating one possible analysis of the proximity sensors <b>120</b> (as illustrated in <figref idrefs="DRAWINGS">FIGS. 4A and 4B</figref>) and the function or operation associated with the different configurations of activated proximity sensors <b>120</b>. As illustrated, while the mobile platform is asleep (<b>302</b>) if at least one proximity sensor <b>120</b> is activated on each side, e.g., <b>120</b><sub>scr</sub>+<b>120</b><sub>scl </sub>or <b>120</b><sub>str</sub>+<b>120</b><sub>stl </sub>or some combination thereof, the mobile platform <b>100</b> is awoken (<b>304</b>). Otherwise, if the front proximity sensor, e.g., <b>120</b>, is activated and one or more of the back sensors (collectively referred to as <b>120</b><sub>g</sub>) are activated (and optionally requiring activation of <b>120</b><sub>gbase</sub>), the mobile platform <b>100</b> detects gestures (<b>306</b>). Otherwise, if the front proximity sensor, e.g., <b>120</b><sub>ftc</sub>, is activated, but no back sensor <b>120</b><sub>g </sub>is activated (nor are the side sensors activated or the mobile platform will wake as per state <b>304</b>) and optionally requiring that the ambient light detector <b>110</b> indicates little or no light, the mobile platform <b>100</b> is identified as being in a pocket with the display <b>102</b> facing the user (<b>308</b>). Otherwise, if one or more back sensors <b>120</b><sub>g </sub>are activated and the front side proximity sensor <b>120</b><sub>ftc </sub>is not activated and optionally the ambient light detector <b>110</b> indicates little or no light, the mobile platform is identified as being in a pocket with the display <b>102</b> facing away from the user (<b>310</b>).
p-0053When the mobile platform is awake, if at least one proximity sensor from each side is not activated, the mobile platform is put in low power (sleep) mode (<b>312</b>), which may occur immediately or after a desired time delay. If the top proximity sensors (<b>120</b><sub>scr </sub>and <b>120</b><sub>scl</sub>) are activated or the top side proximity sensor <b>120</b><sub>t </sub>is activated while the mobile platform <b>100</b> is held in an approximately vertical orientation, i.e., the Z axis is approximately perpendicular to the direction of gravity, in either landscape or portrait orientations, and no other proximity sensors are activated, the mobile platform <b>100</b> activates the camera application (<b>314</b>). If the top proximity sensors (<b>120</b><sub>scr </sub>and <b>120</b><sub>scl </sub>are activated or the top side proximity sensor <b>120</b><sub>t </sub>is activated while the mobile platform <b>100</b> is held in an approximately horizontal orientation, i.e., the Z axis is approximately perpendicular to the direction of gravity, in either landscape or portrait orientations, and no other proximity sensors are activated, the mobile platform <b>100</b> activates the SMS application (<b>316</b>). If not, and the front proximity sensor <b>120</b><sub>ftc </sub>is activated and the phone is in use, the display <b>102</b> is turned off (<b>318</b>).
p-0054<figref idrefs="DRAWINGS">FIG. 20</figref> is similar to <figref idrefs="DRAWINGS">FIG. 19</figref>, but shows a state diagram illustrating a possible analysis of the configurations of proximity sensors <b>120</b> shown in <figref idrefs="DRAWINGS">FIGS. 5A and 5B</figref> and the function or operation associated with the different configurations. As illustrated, while the mobile platform is asleep (<b>352</b>), if at least one pair of proximity sensors <b>120</b> on the side is activated, e.g., <b>120</b><sub>A</sub>, <b>120</b><sub>B </sub>or <b>120</b><sub>C </sub>or some combination thereof, the mobile platform <b>100</b> is awoken (<b>354</b>). Otherwise, if the front proximity sensors, e.g., <b>120</b><sub>F</sub>, are activated and one or more of the back sensors (illustrated in <figref idrefs="DRAWINGS">FIG. 1B</figref> and collectively referred to as <b>120</b><sub>g</sub>) are activated (and optionally requiring activation of <b>120</b><sub>gbase</sub>), the mobile platform <b>100</b> detects gestures (<b>356</b>). Otherwise, if the front proximity sensors, e.g., <b>120</b><sub>F</sub>, are activated, but no back sensor <b>120</b><sub>g </sub>is activated (nor are the side sensors activated or the mobile platform will wake as per state <b>354</b>) and optionally requiring that the ambient light detector <b>110</b> indicates little or no light, the mobile platform <b>100</b> is identified as being in a pocket with the display <b>102</b> facing the user (<b>358</b>). Otherwise, if one or more back sensors <b>120</b><sub>g </sub>are activated and the front side proximity sensor <b>120</b><sub>F </sub>is not activated and optionally the ambient light detector <b>110</b> indicates little or no light, the mobile platform is identified as being in a pocket with the display <b>102</b> facing away from the user (<b>360</b>).
p-0055When the mobile platform <b>100</b> is awake, if at least one pair of proximity sensors on the sides is not activated, the mobile platform is put in low power (sleep) mode (<b>362</b>), which may occur immediately or after a desired time delay. If the corner proximity sensors (<b>120</b><sub>A </sub>and <b>120</b><sub>C</sub>) are activated while the mobile platform <b>100</b> is held in an approximately vertical orientation, i.e., the Z axis is approximately perpendicular to the direction of gravity, in either landscape or portrait orientations as determined by the orientation sensor <b>108</b>, and no other proximity sensors are activated (e.g., proximity sensors <b>120</b><sub>B </sub>are not activated), the mobile platform <b>100</b> activates the camera application (<b>364</b>). If the corner proximity sensors (<b>120</b><sub>A </sub>and <b>120</b><sub>C</sub>) are activated while the mobile platform <b>100</b> is held in an approximately horizontal orientation, i.e., the Z axis is approximately parallel to the direction of gravity, in either landscape or portrait orientations as determined by the orientation sensor <b>108</b>, and no other proximity sensors are activated, the mobile platform <b>100</b> activates an SMS camera application (<b>366</b>). If not, and the front proximity sensors <b>120</b><sub>F </sub>are activated while the phone is in use, the display <b>102</b> is turned off (<b>368</b>).
p-0056Although the present invention is illustrated in connection with specific embodiments for instructional purposes, the present invention is not limited thereto. Various adaptations and modifications may be made without departing from the scope of the invention. Therefore, the spirit and scope of the appended claims should not be limited to the foregoing description.
Contents4
14 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2012170177A1 | Cited by | United States of America | Pre-grant |
| AU2013257523B2 | Cited by | Australia | Search report |
| US2013162513A1 | Cited by | United States of America | Pre-grant |
| WO2020177834A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2019141419A1 | Cited by | United States of America | Search report |
| US8725197B2 | Cited by | United States of America | Search report |
| US9195349B2 | Cited by | United States of America | Search report |
| CN103513893A | Cited by | China | Search report |
| US10228768B2 | Cited by | United States of America | Applicant |
| US2017108919A1 | Cited by | United States of America | Pre-grant |
| US9733763B2 | Cited by | United States of America | Applicant |
| US2014281962A1 | Cited by | United States of America | Pre-grant |
| US9292045B2 | Cited by | United States of America | Search report |
| US9448637B2 | Cited by | United States of America | Applicant |
| US2014176447A1 | Cited by | United States of America | Pre-grant |
| US2017235365A1 | Cited by | United States of America | Search report |
| US2013190054A1 | Cited by | United States of America | Pre-grant |
| US9288390B2 | Cited by | United States of America | Applicant |
| US2015126246A1 | Cited by | United States of America | Pre-grant |
| WO2014169036A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2018266805A1 | Cited by | United States of America | Search report |
| US2015277492A1 | Cited by | United States of America | Pre-grant |
| US2017235365A1 | Cited by | United States of America | Search report |
| US2013026350A1 | Cited by | United States of America | Pre-grant |
| US9727154B2 | Cited by | United States of America | Search report |
| US8855966B2 | Cited by | United States of America | Search report |
| US9411446B2 | Cited by | United States of America | Search report |
| US9692968B2 | Cited by | United States of America | Search report |
| WO2014085649A2 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2020110566A1 | Cited by | United States of America | Search report |
| US10048766B2 | Cited by | United States of America | Applicant |
| US2017010705A1 | Cited by | United States of America | Pre-grant |
| US2013190042A1 | Cited by | United States of America | Pre-grant |
| US9976841B2 | Cited by | United States of America | Search report |
| US2019025958A1 | Cited by | United States of America | Search report |
| US12093468B1 | Cited by | United States of America | Applicant |
| US10775896B2 | Cited by | United States of America | Applicant |
| US9940884B1 | Cited by | United States of America | Search report |
| US10620701B2 | Cited by | United States of America | Search report |
| US11681281B2 | Cited by | United States of America | Search report |
| US2015199554A1 | Cited by | United States of America | Pre-grant |
| US2018307366A1 | Cited by | United States of America | Search report |
| US2016212710A1 | Cited by | United States of America | Pre-grant |
| CN108733250A | Cited by | China | Search report |
| US10883811B2 | Cited by | United States of America | Search report |
| US11701585B2 | Cited by | United States of America | Search report |
| US2016095072A1 | Cited by | United States of America | Pre-grant |
| US9748995B2 | Cited by | United States of America | Applicant |
| US8933877B2 | Cited by | United States of America | Search report |
| US8560004B1 | Cited by | United States of America | Search report |
| WO2016053838A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US11709582B2 | Cited by | United States of America | Applicant |
| US2015379915A1 | Cited by | United States of America | Pre-grant |
| US2013154955A1 | Cited by | United States of America | Pre-grant |
| US9159294B2 | Cited by | United States of America | Search report |
| CN105264711A | Cited by | China | Search report |
| EP3540592A1 | Cited by | European Patent Office (EPO) | Search report |
| US2015296065A1 | Cited by | United States of America | Pre-grant |
| US9709509B1 | Cited by | United States of America | Applicant |
| EP2743795A3 | Cited by | European Patent Office (EPO) | Search report |
| US11115576B2 | Cited by | United States of America | Search report |
| CN104516472A | Cited by | China | Search report |
| US2011081923A1 | Cited by | United States of America | Pre-grant |
| US2024337746A1 | Cited by | United States of America | Search report |
| US2012172681A1 | Cited by | United States of America | Search report |
| US8760294B2 | Cited by | United States of America | Search report |
| US10877609B2 | Cited by | United States of America | Search report |
| US10971938B2 | Cited by | United States of America | Search report |
| US9628982B2 | Cited by | United States of America | Search report |
| US10345967B2 | Cited by | United States of America | Search report |
| US9836637B2 | Cited by | United States of America | Search report |
| US2024343398A1 | Cited by | United States of America | Search report |
| US9915997B2 | Cited by | United States of America | Search report |
| US2013088411A1 | Cited by | United States of America | Pre-grant |
| US9632179B2 | Cited by | United States of America | Search report |
| WO2014168558A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9979886B2 | Cited by | United States of America | Search report |
| US9354698B2 | Cited by | United States of America | Search report |
| US2021400178A1 | Cited by | United States of America | Search report |
| US2012040711A1 | Cited by | United States of America | Pre-grant |
| US9942384B2 | Cited by | United States of America | Applicant |
| US9037199B1 | Cited by | United States of America | Applicant |
| US9571714B2 | Cited by | United States of America | Applicant |
| US9317156B2 | Cited by | United States of America | Applicant |
| DE102014117345B4 | Cited by | Germany | Search report |
| US10306044B2 | Cited by | United States of America | Applicant |
| US2017269579A1 | Cited by | United States of America | Search report |
| US2015169133A1 | Cited by | United States of America | Pre-grant |
| US11216050B2 | Cited by | United States of America | Search report |
| US2018224891A1 | Cited by | United States of America | Pre-grant |
| US2018266805A1 | Cited by | United States of America | Pre-grant |
| EP2926213A4 | Cited by | European Patent Office (EPO) | Search report |
| US2019141419A1 | Cited by | United States of America | Search report |
| CN113574847A | Cited by | China | Search report |
| US12201898B2 | Cited by | United States of America | Applicant |
| US2014281631A1 | Cited by | United States of America | Pre-grant |
| US2015201065A1 | Cited by | United States of America | Pre-grant |
| US2015192989A1 | Cited by | United States of America | Pre-grant |
| US2008134102A1 | Cited by | United States of America | Pre-grant |
| US2014166867A1 | Cited by | United States of America | Pre-grant |
3 members in 2 offices; this record represents the family
Members3
| Document | Office | Kind | |
|---|---|---|---|
| US2011312349A1 | United States of America | A1 | |
| WO2011159947A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US8954099B2 | United States of America | B2 |
86 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 2 RCEs.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 2
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Response to 312 Amendment (PTO-271)MN271 | MN271 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Response to Amendment under Rule 312N271 | N271 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Amendment after Notice of Allowance (Rule 312)AllowedA.NA | A.NA | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| PILOT- Request for After Final Consideration ProgramRAFC | RAFC | |
| Response after Final ActionA.NE | A.NE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Interview Summary - Examiner InitiatedEXIE | EXIE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Sent to Classification ContractorPGPC | PGPC | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Cleared by OIPE CSRL194 | L194 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
5 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 20110312349
- Application
- 89162510
Titles
- English
- LAYOUT DESIGN OF PROXIMITY SENSORS TO ENABLE SHORTCUTS
Patent term adjustment
- A delay
- +653 daysthe office missed an examination deadline
- B delay
- +392 dayspendency past three years
- Overlap
- −124 daysdelays counted once
- Net adjustment
- 921 days
Classification
- CPC, 9
- G06F1/1626
- H04M1/72403
- G06F1/163
- G06F1/3231
- H04M2250/22
- G06F3/017
- Y02D10/00
- H04M1/72442
- H04M1/72436
- IPC, 6
- G06F3 045
- H04M1 72403
- H04M1 00
- H04M1 72436
- H04M1 72442
- H04W4 14
- USPC, 4
- 455466000
- 345174000
- 455556100
- 455566000