Mobile Phone Accessory

Abstract

The subject matter of this specification can be embodied in, among other things, a mobile accessory device that includes a housing having a collapsible grip and defining an attachment surface that is configured to adhere to, attach to, or engage with another surface, a user input apparatus arranged at least partly within the housing and configured to activate in response to input by a user, and a controller arranged at least partly within the housing and configured to activate in response to activation of the user input apparatus and trigger one or more predetermined functions including causing a mobile device to perform one or more predetermined mobile device functions.

Description

TECHNICAL FIELD

The present disclosure relates to a mobile accessory device, for example, one that includes an alarm device for personal protection purposes.

BACKGROUND

Personal safety remains a challenge for essentially all people. Over the course of one's life, there may be situations in which he or she feels that his or her personal safety is at risk. Because many people now routinely carry a mobile device (e.g., a mobile phone), a person who believes that his or her personal safety is at risk can use the device to manually contact (e.g., by text message or phone call) someone else, for example, the police or other entity, to alert them to the person's current situation. In this way, help can be summoned to assist the person whose safety is at risk.

SUMMARY

In general, this document describes a mobile accessory device that includes, e.g., an alarm device for personal protection purposes.

In an example aspect, a mobile accessory device includes a housing having a collapsible grip and defining an attachment surface that is configured to adhere to, attach to, or engage with another surface, a user input apparatus arranged at least partly within the housing and configured to activate in response to input by a user, and a controller arranged at least partly within the housing and configured to activate in response to activation of the user input apparatus and trigger one or more predetermined functions including causing a mobile device to perform one or more predetermined mobile device functions.

Various aspects can include some, all, or none of the following features. The collapsible grip can include a body movable between an expanded configuration and a collapsed configuration. The collapsible grip can be configured to adhere to the mobile device. The collapsible grip can be configured to mechanically engage the mobile device. The user input apparatus can include one or more of (a) a first button at least partly defining a major surface of the housing, (b) at least one second button arranged on a lateral surface defined by the housing, and (c) a sound detection circuit configured to activate in response to one or more predetermined sounds. The one or more predetermined sounds can include one or more utterances that can be recognized when spoken by the user. The user input apparatus can include a first button arranged on a first lateral surface defined by the housing, and a second button arranged on a second lateral surface opposite the first button. The mobile accessory device can include an alarm device having (i) an audio output device, (ii) a light output device, or (iii) both, configured to activate in response to activation of the user input apparatus. Activation of the controller can cause a software application to be executed on the mobile device. The one or more predetermined mobile device functions can include (i) causing an audible alarm to be emitted by the mobile device, or (ii) causing a software application to be executed on the mobile device, or (iii) both.

In another example aspect, a method of using a mobile accessory device includes providing a mobile accessory device having a housing having a collapsible grip and defining an attachment surface that is configured to adhere to, attach to, or engage with another surface, a user input apparatus arranged at least partly within the housing and configured to activate in response to input by a user, and a controller arranged at least partly within the housing and configured to activate in response to activation of the user input apparatus and trigger one or more predetermined functions including causing a mobile device to perform one or more predetermined mobile device functions, and engaging the mobile accessory device to a surface of a mobile device.

Various aspects can include some, all, or none of the following features. The method can include, in response to input by the user, (i) causing an audible alarm to be emitted by an audio output device, or (ii) causing a software application to be executed on the mobile device, or (iii) both. The method can include expanding or collapsing the collapsible grip, where the collapsible grip has a body movable between an expanded configuration and a collapsed configuration. Engaging the mobile accessory device to a surface of a mobile device can include adhering the collapsible grip to the mobile device, mechanically engaging the collapsible grip to the mobile device, or magnetically attaching the collapsible grip to the mobile device. The mobile accessory device can include one or more of (a) a first button at least partly defining a major surface of the housing, (b) at least one second button arranged on a lateral surface defined by the housing, and (c) a sound detection circuit configured to activate in response to one or more predetermined sounds. The method can include receiving, by the sound detection circuit, a sound, identifying, by the sound detection circuit, the sound as corresponding to a predetermined sound, and activating the user input apparatus based on the identifying. The method can include detecting, by the controller, user input based on activation of a user input apparatus, establishing a communications connection from the controller to a communication circuit of the mobile device, and communicating with the communication circuit. Activation of the user input apparatus can include substantially simultaneous actuation of a first button arranged on a first lateral surface defined by the housing, and a second button arranged on a second lateral surface opposite the first button. The user input apparatus can include a button, and activation of the user input apparatus can include detecting a predetermined pattern of presses of the button. The method can include activating, in response to input by the user, an alarm device having (i) an audio output device, (ii) a light output device, or (iii) both. The method can include performing one or more predetermined mobile device functions including (i) causing an audible alarm to be emitted by the mobile device, or (ii) causing a software application to be executed on the mobile device, or (iii) both.

The systems and techniques described here may provide one or more of the following potential advantages. For example, the mobile accessory device as described herein may provide protection for a user of the accessory who comes under attack or assault by another entity (e.g., another human or an animal) by performing one or more of the following actions upon activation of the accessory: causing the mobile device to perform an operation such as sending a message or call for help, turning on the mobile device's camera, microphone, speaker, light or the like, and/or emitting a human perceptible alarm designed to draw attention to the user and/or scare off the attacker.

Details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and potential advantages will be apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a perspective view of a mobile accessory device coupled to a mobile device.

FIG. 2 illustrates a side view of the mobile accessory device and mobile device of FIG. 1.

FIG. 3 illustrates an alternate perspective view of the mobile accessory device and mobile device of FIG. 1.

FIG. 4 illustrates an alternate perspective view of the mobile accessory device and mobile device of FIG. 1 wherein a power source of the mobile accessory device is removed.

FIG. 5 illustrates an alternate perspective view of the mobile accessory device and mobile device of FIG. 1 wherein a wrist strap of the mobile accessory device is in use.

FIG. 6 illustrates an alternate perspective view of the mobile accessory device and mobile device of FIG. 1 wherein a user separation sensor arrangement activates an alarm device.

FIG. 7 schematically illustrates components of the mobile device and the mobile accessory device of FIG. 1.

FIG. 8 illustrates an enlarged view of the switch of the mobile accessory device of FIG. 1.

FIG. 9 schematically illustrates components of the alarm device of FIG. 7.

FIG. 10 illustrates an embodiment of the mobile accessory device including the switch of FIG. 8.

FIG. 11 illustrates a mobile accessory device provided in the form of a case.

FIG. 12 illustrates a mobile accessory device wherein the mobile accessory device is substantially rectangular with rounded comers.

FIG. 13 illustrates a mobile accessory device wherein the mobile accessory device is round.

FIG. 14 illustrates a mobile accessory device wherein the user separation sensor arrangement includes a wireless wearable component.

FIGS. 15-18 illustrate a mobile accessory device wherein the mobile accessory device is ovular.

FIG. 19 illustrates a mobile accessory device wherein a wearable component of the user separation sensor arrangement is not attached for illustration purposes.

FIG. 20 illustrates a mobile accessory device wherein a mobile device is not attached for illustration purposes.

FIG. 21 illustrates a mobile accessory device wherein the mobile accessory device is attached to a case for the mobile device.

FIGS. 22A-F illustrate steps associated with usage of a wrist strap of the mobile accessory device of FIG. 21.

FIG. 23 illustrates a personal safety device that does not require usage of a separate mobile device.

FIG. 24 illustrates a rear view of a mobile accessory device coupled to a mobile device and including a nail slot.

FIG. 25 illustrates a perspective view of a mobile accessory device and mobile device of FIG. 24.

FIG. 26 illustrates an alternate perspective view of the mobile accessory device and mobile device of FIG. 24.

FIG. 27 illustrates a rear view of a mobile accessory device coupled to a mobile device and including an enlarged nail slot.

FIG. 28 illustrates a perspective view of the mobile accessory device and mobile device of FIG. 27.

FIG. 29 illustrates a perspective side view of another example mobile accessory device.

FIG. 30 illustrates a front view of the example mobile accessory device of FIG. 29.

FIG. 31 illustrates a top perspective view of the example mobile accessory device of FIG. 29.

FIG. 32 illustrates an alternate top perspective view of the example mobile accessory device of FIG. 29.

FIG. 33 illustrates a bottom perspective view of the example mobile accessory device of FIG. 29.

FIG. 34 illustrates an alternate bottom perspective view of the example mobile accessory device of FIG. 29.

FIG. 35 illustrates a perspective rear view of the example mobile accessory device of FIG. 29.

FIG. 36 is a flow chart of an example process for using an example mobile accessory device.

FIGS. 37a and 37b illustrate a personal safety device that engages a portion of a mobile device or a companion mobile accessory.

FIG. 38 illustrates a perspective view of the example personal safety device and companion mobile accessory of FIGS. 37a-37b.

FIG. 39 illustrates a front view of the example personal safety device and companion mobile accessory of FIGS. 37a-37b.

FIG. 40 illustrates a rear perspective view of the example personal safety device and companion mobile accessory of FIGS. 37a-37b.

FIG. 41 illustrates a perspective front view of the example personal safety device of FIGS. 37a-37b.

FIG. 42 illustrates an alternate perspective front view of the example personal safety device of FIGS. 37a-37b.

FIG. 43 illustrates a perspective rear view of the example personal safety device of FIGS. 37a-37b.

FIG. 44 illustrates a perspective front view of the companion mobile accessory of FIGS. 37a-37b.

FIG. 45 illustrates a perspective rear view of the companion mobile accessory of FIGS. 37a-37b.

FIG. 46 is a flow chart of an example process for using an example mobile accessory device.

FIG. 47 illustrates a perspective front view of a mobile accessory device that engages a portion of a mobile device or a companion mobile accessory.

FIG. 48 illustrates a perspective rear view of the mobile accessory device of FIG. 47.

FIGS. 49A and 49B illustrate a sectional view of the mobile accessory device of FIG. 47.

FIG. 50 illustrates a perspective from view of the example mobile accessory device of FIG. 74 and an example companion mobile accessory.

FIG. 51 illustrates a perspective rear view of the example mobile accessory device and companion mobile accessory of FIG. 50.

FIG. 52 illustrates a partially exploded perspective side view of the example mobile accessory device and companion mobile accessory of FIG. 50.

FIGS. 53 and 54 illustrate an example mobile accessory device having magnetic features.

FIGS. 55A and 55B illustrate perspective and side views of an example of a mobile accessory device button.

FIGS. 56A and 56B illustrate perspective and side views of another example of a mobile accessory device button.

FIG. 57 is a flow chart of an example process using an example mobile accessory device.

FIGS. 58A and 58B illustrate perspective and side views of an example mobile device and an example mobile accessory device in an expanded configuration.

FIGS. 59A and 59B illustrate perspective and side views of the example mobile device and the example mobile accessory device in a collapsed configuration.

FIG. 60 is a flow chart of an example process using an example mobile accessory device.

FIG. 61 is a block diagram of computing devices that may be used to implement the systems and methods described in this document.

DETAILED DESCRIPTION

This document describes systems and techniques for providing personal protection in the form of an alarm accessory for a mobile device. In general, a mobile device, e.g., a cellular telephone (phone) or a mobile phone, can be modified (e.g., attached to an accessory and/or through the use of specialized software on the mobile device), to respond to one or more predetermined conditions to automatically, and/or with user interaction, trigger an alarm and thereby draw attention to that person's present circumstances in order to seek help and/or scare away a potential threat. Accordingly, this document describes, among other things, an accessory that can be attached to the mobile device and provide enhanced safety functionality to a user of the mobile device. Various configurations of such a mobile accessory device and its use are described herein, and may include various combinations of the following features and/or functionality. The accessory may be embodied in many different forms and should not be construed as limited to the implementations set forth herein. As used in the specification, and in the appended claims, the singular forms “a”, “an”, “the”, include plural variations unless the context clearly dictates otherwise.

As illustrated in FIGS. 1-6, the present disclosure relates to a mobile accessory device 100, also referred to a mobile accessory device. The mobile accessory device 100 may be configured for use with a mobile device such as a mobile phone 200 or other mobile device (e.g., tablet computer, notebook computer, etc.). In particular, the mobile accessory device 100 may be configured to engage (e.g., adhere to or otherwise be physically joined to) the mobile phone 200. The mobile accessory device 100 may be configured to engage any portion of the mobile phone 200, such as the rear surface of the housing of the mobile phone 200. In some embodiments, the mobile accessory device 100 may be a stand-alone device that does not physically engage to a mobile device.

In one implementation, the mobile accessory device 100 may include a housing 102. The housing 102 may define an attachment (e.g., locking) surface 104 (see, FIG. 2) and an outer surface 106 (see, e.g., FIG. 1). As illustrated in FIG. 2, the attachment surface 104 may be configured to engage a rear surface 202 of the mobile phone 200 opposite from a front surface 204 at which a display is positioned. Thereby, the mobile accessory device 100 does not block the display in this configuration. Further, the mobile accessory device 100 may occupy less than an entirety of an area of the rear surface 202 of the mobile phone 200. Thereby, the mobile accessory device 100 may not block any rear-facing camera thereon. Further, by providing the mobile accessory device 100 with a relatively small size, the mobile accessory may be attached to mobile phones with differing sizes and shapes. Further, the mobile accessory device 100 may be configured to not extend to the edges of the mobile phone 200, such that an edge protecting case may be employed with the mobile phone. As may be understood, the mobile accessory may also be configured to engage a case for the mobile phone that includes a rear portion that covers the rear surface (see, e.g., FIGS. 21 and 22). In another embodiment, the mobile accessory may itself include a case for the mobile phone (see, e.g., FIG. 11).

The attachment surface 104 of the housing 102 may be configured to substantially permanently engage the rear surface 202 of the mobile phone 200, or a case positioned at the rear surface as noted above. For example, the mobile accessory device 100 may include an adhesive at the attachment surface 104 configured to adhere to the rear surface 202 of the mobile phone 200. Thereby, the mobile accessory device 100 may be configured for use over the lifetime of the mobile phone 200, thereby ensuring that the mobile accessory is available at all times the mobile phone is in the user's possession. Alternatively, the attachment surface 104 of the housing 102 may be configured to releasably engage (e.g., using a slot-tab arrangement, or hook and loop connecting surfaces such as VELCRO®) the rear surface 202 of the mobile phone 200, or a case positioned at the rear surface as noted above.

As illustrated in FIG. 4, the mobile accessory device 100 may include a power source 108, which may be a battery. Further, the housing 102 may include a battery portion 110 that is configured to receive the power source 108. The battery portion 110 may be removable to allow for replacement of the power source 108. The power source 108 may be configured to provide electrical power to each of the components of the mobile accessory device 100 such that the mobile accessory is self-powered. However, as may be understood, in another implementation the mobile accessory may be configured to receive electrical power from the mobile phone. For example, the mobile accessory may include a connector that engages a power port or a headphone jack on the mobile phone. Alternatively, or in addition, the mobile accessory may draw power from the phone wirelessly via a technique akin to QI® inductive charging, but in reverse (e.g., reverse wireless charging, wireless power sharing).

Additional control circuitry components of the mobile accessory device 100 and the mobile phone 200 are schematically illustrated in FIG. 7. As illustrated, the mobile accessory device 100 includes a controller 112, which may be arranged at least partially within the housing 102. The controller 112 is in communication with the mobile phone 200 (e.g., a communications connection, BLUETOOTH, USB) for providing signals to the mobile phone 200, for example, to request, trigger, command, or otherwise control operation of at least some operation or actions of the mobile phone 200. The controller 112 may include an audio output device 114 such as a speaker and a light output device 116 such as a light emitting diode (LED) or xenon strobe. Example positions and configurations of the audio output device 114 and the light output device 116 are illustrated in FIGS. 1 and 3-6.

As further illustrated in FIG. 7, the control circuitry of the mobile accessory device 100 includes a user separation sensor arrangement 118 (e.g., proximity detector). The user separation sensor arrangement 118 may include a wearable component 120 configured to engage (e.g., donned by, worn by) a user and a user input sensor 122 (e.g., a user input apparatus) engaged with the housing 102 and in communication with the controller 112. The controller 112 may be configured to activate and/or perform one or more predetermined operations in response to the user input sensor 122's determining that the wearable component 120 exceeds a threshold separation distance therefrom, and/or has become detached (e.g., mechanically separated) from the mobile accessory device 100, e.g., providing an alarm signal to indicate that separation between the mobile accessory device 100 and the wearable component 120 has occurred, in response to which one or more actions can occur—e.g., sounding an audible alarm on the accessory, emitting light from a light source on the accessory, cause the attached phone's flash light to turn on or strobe, cause the attached phone to transmit a message via text and/or phone call, cause the mobile phone to emit sound, cause the mobile phone to take photos or begin recording video, either through the forward-facing camera or the rearward-facing camera or the both, or otherwise any operation within the attached phone's functionalities. Note that any phone-based action could be achieved by the accessory's transmitting to the mobile phone that an alarm condition has been detected, e.g., in response to the user's pushing a button on the accessory, or in response to the proximity between the accessory and the wearable component being exceeded and/or in response to the wearable component being mechanically disconnected from the accessory.

As further illustrated in FIG. 7, the control circuitry of the mobile accessory device 100 includes a sound detector arrangement 150 (e.g., a sound detection circuit). The sound detector arrangement 150 includes circuitry that is configured to receive sound signals from a microphone 152 and identify one or more predetermined sounds. The controller 112 is configured to provide one or more predetermined actions in response to the identification of one or more corresponding sounds. In some implementations, the sound detector arrangement 150 can be configured to recognize one or more utterances (e.g., words, phrases, or other sounds produced by a user). In some implementations, the sound detector arrangement 150 can be configured to recognize one or more non-spoken sounds (e.g., screams or other sounds of distress, smoke alarms, glass breakage, car crash sounds). The controller 112 may be configured to activate and/or perform one or more predetermined operations in response to the sound detector arrangement identification of a predetermined command or sound, e.g., providing an alarm signal in response to the user saying “help!” or “call 911!” or screaming, in response to which one or more actions can occur—e.g., sounding an audible alarm on the accessory, emitting light from a light source on the accessory, causing the attached phone's flash light to turn on or strobe, causing the attached phone to transmit a message via text and/or phone call, causing the mobile phone to emit sound, causing the mobile phone to take photos or begin recording video, either through the forward-facing camera or the rearward-facing camera or the both, or otherwise any operation within the attached phone's functionalities. Note that any phone-based action could be achieved by the accessory's transmitting to the mobile phone that an alarm condition has been detected, e.g., in response to the user's pushing a button on the accessory, or in response to the proximity between the accessory and the wearable component being exceeded and/or in response to the wearable component being mechanically disconnected from the accessory, and/or in response to detection of a predetermined sound.

In some implementations, the controller 112 may be configured to activate a function of the mobile phone 200 in response to the sound detector arrangement identification of a predetermined sound. For example, the mobile phone 200 may be configured with a voice assistant (e.g., GOOGLE ASSISTANT, SIRI, ALEXA, CORTANA, BIXBY), and the sound detector arrangement 150 can be configured to recognize one or more “wake up” phrases associated with voice assistants that are installed on the mobile phone 200 (e.g., “ok Google”, “hey Siri”, “Alexa”, “hey Cortana”, “hi Bixby”), and the accessory 100 can send a command to the mobile phone 200 that will activate the corresponding voice assistant to process the rest of the user's command. In some implementations, the microphone 152 may be configured as a supplement or substitute for the microphone 211. In some implementations, the mobile accessory device 100 can unlock access to a voice assistant on the mobile phone 200. For example, some configurations of mobile phones and/or voice assistants may require the user to first unlock the mobile phone or perform some other preliminary action before a voice assistant can respond to verbal commands. The mobile accessory device 100 can recognize a “wake up” word/phrase and send a command to the mobile phone 200, where an application running in the background on the mobile phone 200 can receive the command and respond by unlocking the mobile phone 200 and/or otherwise placing the voice assistant in condition to respond to the user. In some implementations, the user can choose to opt-in to grant the phone application sufficient security privileges to bypass or otherwise release phone security features (e.g., screen locks) that need to be dismissed in order to make the voice assistant responsive and/or useful.

With regard to wearable components, as illustrated in FIG. 5, in one embodiment the wearable component 120 may include a wrist strap. Initially, the user input sensor 122 and the wearable component 120 of the user separation sensor arrangement 118 may be physically connected. For example, as illustrated in FIG. 5, a lanyard 124 (e.g., mechanical tether) may connect the wearable component 120 to the housing 102 via a connector 126.

As noted above, the controller 112 may be activated in response to receipt of a signal generated by the user separation sensor arrangement 118 when the user separation sensor arrangement 118 determines that the wearable component 120 has become physically detached from the accessory, and/or exceeds a threshold separation distance from the user input sensor 122. Thereby, the threshold separation distance may be defined between the housing 102 and the wearable component 120. Thus, for example, the lanyard 124 may have a predetermined length that at least partially defines the threshold distance, and the lanyard may be configured to mechanically and/or electrically attach to the housing 102 and separate from the housing 102 when the distance between the wearable component 120 and the housing 102 exceeds the predetermined length of the lanyard 124. The user separation sensor arrangement 118 can include a user input sensor configured to determine whether the housing 102 and the lanyard are mechanically and/or electrically separated and provide an alarm signal in response.

As illustrated in FIG. 6, when a user's wrist to which the wearable component 120 is attached moves away from the housing 102 of the mobile accessory device 100 by a distance exceeding the length of the lanyard 124, the lanyard may pull out (e.g., separate, break away) the connector 126 from the housing 102 and out of engagement with the user input sensor 122, thereby activating the controller 112 (see, FIG. 7).

Further, in one embodiment the connector 126 may include a whistle. Thereby, once the connector 126 is removed from the housing 102, the user may blow on the whistle to bring attention to the user's circumstances, scare away an assailant, and/or summon help.

In an alternate embodiment, the connector extending from the wearable component may be configured to engage a power and/or data port of the mobile phone or a headphone jack thereon. In this embodiment, the mobile phone may itself (e.g., via a software application executing on the mobile phone) detect detachment or separation of the wearable component from the port or jack, thereby activating the alarm device.

As schematically illustrated in FIG. 7, the mobile accessory device 100 may also include a switch 128. The switch 128 may be provided in addition to, or as an alternate for, the user separation sensor arrangement 118. In a preferred embodiment, both the user separation sensor arrangement 118 and the switch 128 are provided.

An example embodiment of the switch 128 is illustrated in FIGS. 1 and 3-6. In some embodiments it may be desirable to provide the switch 128 with features configured to prevent accidental actuation thereof so as to avoid accidental activation of the controller 112 (see, FIG. 7). In this regard, in some embodiments actuation of the switch 128 may require movement of the switch along a non-linear path. For example, FIG. 8 illustrates an enlarged example embodiment of an embodiment of the switch 128A. As illustrated, the switch 128A may include a center button 130 and a slider 132. In order to activate the switch 128A, a user may slide the slider 132 in order to depress the center button 130. Thereby, issues with respect to accident actuation of the switch 128A may be mitigated. Various other switches requiring multi-stage actuation may be provided in other embodiments.

The controller 112 may be configured to be activated in response to a signal from the user separation sensor arrangement 118 and/or the switch 128. The particular response by the controller 112 may be set as desired. In some embodiments activation of the controller 112 by the switch 128 may result in the same response as activation of the alarm device by the user separation sensor arrangement 118. However, in other embodiments activation of the controller 112 by the switch 128 may result in a different response as compared to activation of the alarm device by the user separation sensor arrangement 118.

For example, the controller 112 may be configured to output an audible alarm configured to output sounds, predetermined spoken words, and/or noises (e.g., siren, buzzer, bell, speech) that are loud enough to attract attention from others in the vicinity of the mobile phone 200 when the user separation sensor arrangement 118 determines that the threshold separation distance is exceeded. In this regard, one or both of the audio output device 114 and the light output device 116 may be activated. However, in some configurations, the controller 112 may be silently activated when the switch 128 is actuated (e.g., the controller 112 or the mobile phone 200 may be configured to omit the emission of an attention-getting sound during activation). In some embodiments, a silent alarm can refer to any appropriate circuit and/or mechanism for taking a predetermined action in response to a trigger, and does not necessarily require (nor preclude) that the alarm device is itself incapable of generating an audible alarm.

In this regard, the controller 112 may be configured to direct the mobile phone 200 to send a communication (e.g., a telephone call, an SMS text message, an instant message, and email) to one or more predefined recipients in response to actuation of the switch 128. In some implementations, the communication can include one or more predetermined messages (e.g., pre-recorded voice message, pre-configured text or synthesized voice message). In some implementations, the communication can be sent to one or more predetermined recipients (e.g., emergency response center, 911, police, user contacts). The controller 112 may be configured to direct the mobile phone 200 to send a communication to one or more predefined recipients when the user separation sensor arrangement 118 determines that the threshold separation distance from the wearable component 120 is exceeded, and/or that the wearable component 120 has become detached from the mobile accessory device 100.

The controller 112 may be configured to direct the mobile phone 200 to activate a camera 207 (e.g., to capture still or motion video of the surroundings), a microphone 211 (e.g., to capture sounds in the surrounding environment), a position location detector system 154 (e.g., GPS or other location system to identify a local or global location of the phone), light output system to emit a visual indicator (e.g., blink an onboard LED, flash the phone's screen), and/or audio output system (e.g., built-in speaker of the phone, to emit an audible alarm or call for help) of the mobile phone 200, In some implementations, the communication can include one or more of a distress message, positioning coordinates of a determined position location (e.g., based on a GPS sensor in the mobile device), audio captured by mobile device, and video captured by the mobile device. The functionality of being able to send a communication in response to an alarm or other predetermined condition may be implemented by specialized software installed on and executed by the mobile device, for example, a downloadable software application (e.g., app) or other software component.

To transmit such notifications, as schematically illustrated in FIG. 7, the mobile accessory device 100 may further include a communication interface 134 (e.g., a communication circuit, communication circuitry). The communication interface 134 may be configured to communicate with a communication interface 206 (e.g., a communication circuit, communication circuitry) of the mobile phone 200 when directed by the controller 112. The communication interface 134 of the mobile accessory device 100 and the communication interface 206 of the mobile phone 200 may be any suitable arrangement, such as a device or circuitry embodied in either hardware, software, or a combination thereof that is configured to receive and/or transmit data. The communication interfaces 134, 206 may be configured to receive and/or transmit data via a wired communication connection or wireless communication connection. In this regard, the communication interfaces 134, 206 may include, for example, an antenna and supporting wireless transmitter, receiver, or transceiver hardware and/or hardwired components and/or software. For example, the communication interface 134 of the mobile accessory device 100 may include a wireless transmitter, receiver, or transceiver configured to communicate with the communication interface 206 of the mobile phone 200 via BLUETOOTH, photonic (e.g., infrared, IRDA), acoustic, ultrasonic, ZigBee, WiFi, or any other appropriate communication format. Further, the communication interface 206 of the mobile phone 200 may be configured to communicate with one or more cellular networks via any known communication standard.

Thereby, the communication interface 206 of the mobile phone 200 may send a communication to one or more designated contacts. The designated contacts may be selected by the user via a user-installable software application that may be loaded on the mobile phone 200. The type and/or content of the message may also be configured within the application.

In some embodiments, the communication may include a phone call with an audible message. For example, a prerecorded message may be played to convey a request for help. Alternatively or additionally, the mobile phone 200 may activate a microphone 211 thereof such that a recipient of the call may receive audio relating to the user of mobile accessory's circumstances (e.g., voice or other sounds corresponding to words or actions of the mobile phone user or anyone or anything else within the range of the mobile phone's microphone 208).

In some embodiments, the communication may include a video communication. For example, the mobile phone 200 may activate a camera 207 thereof such that a recipient of the call may receive video relating to the user of accessory's circumstances (e.g., video and audio within the range of the mobile device's camera 207 and microphone 208).

In some embodiments, the communication may include a text message, an email, or any other electronic communication. Thereby, the communication may include, for example, a message conveying a request for help and/or instructing the recipient to call police or other emergency services. The communication may also include location data regarding a position of the mobile phone 200. For example, the mobile phone 200 may further include a positioning system sensor 210 (e.g., GPS, GLONASS, indoor positioning), which may determine a location thereof, and such location information may be included in the communication transmitted by the communication interface 206 of the mobile phone. In another example, the mobile accessory device 100 may further include a position location detector system 154 (e.g., GPS, GLONASS, indoor positioning), which may determine a location thereof, and such location information may be included in the communication transmitted by the communication interface 134 of the mobile accessory. For example, the recipients of the communication may be provided with an image showing the position of the mobile phone 200 and/or a link to a map showing the position. Such a map may be updated with the positon of the mobile phone 200 such that the position thereof may be tracked in the event that movement occurs. Thereby, emergency service personnel may be directed to the location of the mobile phone 200.

In another embodiment, communications may additionally or alternatively be transmitted to other users of mobile accessory devices in local proximity to the mobile accessory device 100. For example, the communication interface 134 of the mobile accessory device 100 may directly communicate with the communication interface of other nearby mobile phone accessories to alert their users of a nearby user in need of assistance. In some embodiments the mobile accessory devices 100 may form a mesh network via the communication interfaces 134 to expand the reach of the local alerts.

FIG. 9 schematically illustrates control circuitry components of the controller 112 (e.g., an alarm device) according to an embodiment of the present disclosure. As illustrated, the control circuitry of the controller 112 may include or otherwise be in communication with a processor 136 and a memory device 138.

The processor 136 may be embodied in a number of different forms. For example, the processor 136 may be embodied as one or more of various processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), processing circuitry, or various other processing devices including integrated circuits such as, for example, a special-purpose computer chip, or other hardware processor. In an example embodiment, the processor 136 may be configured to execute instructions stored in the memory device 138 or otherwise accessible to the processor. Alternatively or additionally, the processor 136 may be configured to execute hard coded functionality. As such, the processor 136 may be capable of performing operations according to embodiments of the present disclosure while configured accordingly. Alternatively, when the processor 136 is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the operations described herein. The processor 136 may include a clock, an arithmetic logic unit (ALU), and logic gates configured to support operation of the processor, amongst other components.

The memory device 138 may include non-transitory and tangible memory that may be, for example, volatile and/or non-volatile memory. The memory device 138 may be configured to store information, data, files, applications, instructions, or the like. For example, the memory device 138 can be configured to buffer input data for processing by the processor 136. Additionally or alternatively, the memory device 138 can be configured to store instructions for execution by the processor 136.

The processor 136 may be configured to execute program code instructions stored on a non-transitory computer readable medium. In this regard, an embodiment of a non-transitory computer readable medium for storing computer instructions executed by a processor (e.g., processor 136) is provided, such as the memory device 138. The non-transitory computer readable medium may include program code instructions for performing the alarm operations described herein.

The various aspects, embodiments, implementations, or features of the described embodiments can be used separately or in any combination. Various aspects of the described embodiments can be implemented by software, hardware or a combination of hardware and software. The described embodiments can also be embodied as computer readable code on a computer readable medium for controlling the above-described operations. In particular, computer readable code may be configured to perform each of the operations of the methods described herein and embodied as computer readable code on a computer readable medium for controlling the above-described operations. In this regard, a computer readable storage medium, as used herein, refers to a non-transitory, physical storage medium (e.g., a volatile or non-volatile memory device, which can be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape, and optical data storage devices. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Although the present disclosure is generally described as relating to a mobile accessory, in another embodiment some or all of the components of the mobile accessory described above may be included in a standalone personal safety device (see, e.g., FIG. 23). In other words, a personal safety device may be configured for use without requiring a separate mobile phone. In this regard, the personal safety device may be configured to communicate with cellular networks and configured to determine a location of the personal safety device. Thus, for example, the communication interface may be configured to communicate with cellular or satellite networks in order to allow for transmission of electronic communications and the personal safety device may further include a GPS sensor configured to determine the location of the personal safety device.

As noted above, the form factor of the mobile accessory device 100 may vary. In this regard, FIG. 10 illustrates an embodiment of the mobile accessory device 100A including the switch 128 of FIG. 8. FIG. 11 illustrates an embodiment of the mobile accessory device 100B provided in the form of a case. FIG. 12 illustrates an embodiment of the mobile accessory device 100C wherein the mobile accessory is substantially rectangular with rounded corners. FIG. 13 illustrates an embodiment of the mobile accessory device 100D wherein the mobile accessory is round. FIG. 14 illustrates an embodiment of the mobile accessory device 100E wherein the user separation sensor arrangement includes a wireless wearable component 120D. FIGS. 15-18 illustrate an embodiment of the mobile accessory device 100F wherein the mobile accessory is ovular. FIG. 19 illustrates an embodiment of the mobile accessory device 100G wherein the wearable component of the user separation sensor arrangement is not attached for illustration purposes. FIG. 20 illustrates an embodiment of the mobile accessory device 100H wherein a mobile phone is not attached for illustration purposes. FIG. 21 illustrates an embodiment of the mobile accessory device 100I wherein the mobile accessory is attached to a case 208 for the mobile phone 200.

In examples such as the mobile accessory device 100E and the wearable component 120D of FIG. 14, the connection between the wearable component 120D and the mobile accessory device 100E may be wireless. For example, the connection may be a radio frequency connection (e.g., BLUETOOTH connection), a photonic connection (e.g., infrared beacon, IrDA), sonic (e.g., ultrasonic beacon), or magnetic (e.g., a Hall sensor in the mobile accessory device activated when a magnet in the wearable component or the mobile phone is moved too far away).

In some embodiments, the user separation sensor arrangement 118 can be configured to measure or otherwise detect a strength of a wireless signal provided by the wearable component. The strength of the signal can be proportional or otherwise representative of the distance between the wearable component and the user separation sensor arrangement 118 (e.g., the larger the separation distance, the weaker the received signal will be). The user separation sensor arrangement 118 can compare the strength of the received signal to a predetermined threshold signal strength value. If the received signal strength is determined to be less than the threshold signal strength value, the user separation sensor arrangement 118 can provide an activation signal to the controller 112. In some embodiments, the user separation sensor arrangement 118 may be configured to detect the presence and/or absence of a beacon signal, and the threshold signal strength value can be a timeout value. For example, the wearable component 120D can be configured to emit a beacon signal once every second, and the threshold signal strength value can be set to five seconds. In this example, the user separation sensor arrangement 118 can determine that no beacon signal has been received for at least five seconds, and respond by determining that the wearable component 120D is no longer in proximity (and/or physically attached) to the mobile accessory device 100E and provide an activation signal to the controller 112.

FIGS. 22A-F illustrate steps associated with usage of a wearable component 120I (e.g., a wrist strap) of the mobile accessory device 100I of FIG. 21. FIG. 22A shows a mobile phone 200 having an attached (e.g., adhesively, with tabs/slots, or hooks and loops) mobile accessory device 100I. The microphone of the mobile phone 200 is shown at 208. The mobile accessory device 100I includes a groove 209 defined in the surface of the mobile accessory device 100I, sized to accommodate storage of the wearable component 120I. FIGS. 22B-D show a user in the process of removing the wearable component 120I from the groove 209 so that he or she can engage the wearable component 120I into a worn position, such as shown in FIG. 22E (e.g., donned upon a wrist). FIG. 22F illustrates how the user might hold mobile phone 200 after he or she has removed wearable component 120I form the groove 209 and put it around his or her wrist. The user can later remove (e.g., doff) the wearable component 120I and stow it in the groove 209.

FIG. 23 illustrates an embodiment of a personal safety device 300 that does not require usage of a separate mobile phone, but rather is implemented as a standalone, dedicated personal safety device. Such a personal safety device 300 may have sufficient components and functionalities to perform the operation

Further, FIGS. 24-26 illustrate an embodiment of the mobile accessory device 100J according to an additional example embodiment of the present disclosure. The mobile accessory device 100J is illustrated as being attached to the mobile phone 200 as discussed above. The overall configuration and features of the mobile accessory device 100J may be substantially similar to that of the mobile accessory device 100 of FIG. 1. However, the mobile accessory device 100J of FIGS. 24-26 may vary in one or more respects.

For example, as illustrated, the position of the components of the mobile accessory device 100J relative to the housing 102J may vary. In this regard, the light output device 116J may be positioned at a top center of the outer surface 106J of the housing 102J. This configuration may allow the light output device 116J to be exposed and visible above the top of the user's hand in the event of activation while in the user's hand, such that it is more noticeable. The audio output device 114J may be positioned in a similar location as compared to the audio output device 114 of the mobile accessory device 100 of FIG. 1, but the housing 102J may include a pattern of round holes defined there through that allow sounds to exit the mobile accessory device 100J. Further, the switch 128J may be substantially similar to the switch 128A described above with respect to FIG. 8, but the ends thereof may be relatively more rounded for improved ergonomics and/or appearance. Additionally, the battery portion may be positioned at the attachment surface of the mobile accessory device 100J engaged with the mobile phone 200 in order to de-clutter the exposed outer surfaces thereof.

Further, the mobile accessory device 100J may include a nail slot 140J, which may be positioned between the connector 126J and the housing 102J. In this regard, in some embodiments the user separation sensor arrangement may be activated by engaging a fingernail in the nail slot 140J and releasing the connector 126 rather than requiring the user to release the wearable component 120J first. Thereby, activation of the user separation sensor arrangement may be conducted quickly (e.g., in an unexpected dangerous situation), if necessary.

Further, the particular configuration of the wearable component 120J may differ. In this regard, as illustrated in FIGS. 24-26, in an un-extended configuration, the lanyard 124J may wrap around a lower comer of the housing 102J and extend to and wrap around a top comer of the housing. The wearable component 120J may then extend downward from the lanyard 124J to the bottom edge of the housing 102J. A clip 142J may be positioned at the interface between the lanyard 124J and the wearable component 120J. In some embodiments, the clip 142J may be moveable such that the relative length of the wearable component 120J relative to the lanyard 124J is adjustable and thereby a user may tighten the wearable component around his or her wrist during use. The clip 142J may be configured to engage the housing 102J when in an un-extended configuration to retain the lanyard 124J in place.

Further, the wearable component 120J may include a pull tab 144J at an end thereof. The pull tab 144J may retain the wearable component 120J in the un-extended configuration until the user releases the pull tab from engagement with the housing 102J. Releasing the pull tab 144J from engagement with the housing 102J may activate one or more features. For example, in response to the pull tab 144J being released, the positioning system sensor 210 (see, FIG. 7) may be instructed to activate via the communication mechanisms described above. Accordingly, when a user extends the wearable component 120J and places it on his or her wrist, for example when confronted with a dangerous situation or location, the user's location may be determined and tracked at that time. Thereby, in the event that the user pulls out the connector 126J, the positioning system sensor 210 will have already been activated in order to substantially immediately provide the user's location as described above. Thereby, for example, any delays associated with determining the user's location may be avoided. Further, the user's location may be tracked during the time period during which the pull tab 144J is released and thereby the user's location information may optionally be shared with one or more persons, if desired.

The embodiment of the mobile accessory device 100K illustrated in FIGS. 27 and 28 is substantially similar to the mobile accessory of FIGS. 24-26 in most respects and hence the configuration thereof will not be repeated. However, the nail slot 140K is enlarged.

FIGS. 29-35 illustrate various views of another example mobile accessory device 100I according to an additional example embodiment of the present disclosure. The mobile accessory device 100L is configured to be attached to the mobile phone 200 as will be discussed further below. The overall configuration and features of the mobile accessory device 100L may be substantially similar to that of the mobile accessory device 100 of FIG. 1. However, the mobile accessory device 100L of FIGS. 29-35 may vary in one or more respects.

For example, as illustrated, the position of the components of the mobile accessory device 100L relative to the housing 102L may vary. The audio output device 114L may be positioned in a similar location as compared to the audio output device 114 of the mobile accessory device 100 of FIG. 1, but the housing 102L may include a round hole defined there through that allow sounds to exit the mobile accessory device 100L.

Further, the particular configuration of the wearable component 120L may differ. In this regard, as illustrated in FIGS. 29-35, in an un-extended configuration, wearable component 120L and the lanyard 124L may be stow-able in a groove 2909 formed about the periphery of the housing 102L. Further, the wearable component 120L may include a pull tab 144L at an end thereof. The pull tab 144L may retain the wearable component 120L in the stowed (e.g., un-extended) configuration until the user releases the pull tab 144L from engagement with the housing 102L. Releasing the pull tab 144L from engagement with the housing 102L may activate one or more features. For example, in response to the pull tab 144L being released, the positioning system sensor 210 (see, FIG. 7) may be instructed to activate via the communication mechanisms described above. Accordingly, when a user removes the wearable component 120L from the groove 2909 and places it on his or her wrist, for example when confronted with a dangerous situation or location, the user's location may be determined and tracked at that time. Thereby, in the event that the user pulls out the connector 126L, the positioning system sensor 210 will have already been activated in order to substantially immediately provide the user's location as described above. Thereby, for example, any delays associated with determining the user's location may be avoided. Further, the user's location may be tracked during the time period during which the pull tab 144L is released and thereby the user's location information may optionally be shared with one or more persons, if desired.

Further, the switch 128L may be a pressure sensitive or membrane switch defined as a fingertip-sized recess having a textured pattern (e.g., to ease identification and location of the switch 128L by either sight or touch). In use, the switch may be used to activate an alarm though a predetermined continuous press (e.g., three seconds) or through a predetermined series of presses (e.g., three presses within five seconds), for example, to reduce the occurrence of accidental activation. In some implementations, the switch 128L may activate a different type of alarm than may be triggered by separation of the lanyard. For example, the mobile accessory device 100L may respond to activation of the switch 128L by initiating a silent alarm to alert one or more predetermined recipients (e.g., discretely sending a message to a preselected contact), while the mobile accessory device 100L may respond to separation of the connector 126L by initiating an audible alarm and alerting one or more predetermined recipients (e.g., set off a siren and send a message or place a phone call to police).

Further, the mobile accessory device 100L may include a nail slot positioned between the connector 126L and the housing 102L. In this regard, in some embodiments the user separation sensor arrangement may be activated by engaging a fingernail in the nail slot and releasing the connector 126L rather than requiring the user to release the wearable component 120L first. Thereby, activation of the user separation sensor arrangement may be conducted quickly (e.g., in an unexpected dangerous situation), if necessary.

The mobile accessory device 100L also includes a visual indicator 2902 (e.g., a light, a display). The visual indicator 2902 is configured to provide a visible indication of one or more statuses of the mobile accessory device. For example, the visual indicator 2902 may blink at a first rate or pattern (e.g., or illuminate steadily), illuminate at a first brightness, and/or illuminate with a first color to display a first condition (e.g., to indicate that the mobile accessory device 100L is connected to or paired with the mobile phone 200 and/or an associated alarm software application running on the phone), and blink, illuminate, and/or colorize in different predetermined manners to display other conditions (e.g., to indicate that the mobile accessory device 100L is not paired or otherwise communicatively associated with mobile phone 200, to indicate that the mobile accessory device 100L is not able to communicate with the mobile phone 200 to which it was previously paired or otherwise communicatively associated). In some embodiments, the visual indicator 2902 may display differently shaped predetermined patterns to indicate different conditions of the mobile accessory device 100L. For example, the visual indicator 2902 may appear as a periodically blinking, blue BLUETOOTH symbol to indicate that the mobile accessory device 100L is ready for pairing, and may appear as a red “X” when the mobile accessory device 100L is not able to communicate with the paired mobile phone 200 or an associated software application installed thereupon and configured to respond to alarm signals from the mobile accessory device 100L.

Referring now to FIG. 35, a rear perspective view of the mobile accessory device 100L is shown. The rear side of the housing 102L includes an adhesive pad 3502. In use, the adhesive pad 3502 can be contacted against a surface of the mobile phone 200 (e.g., the rear surface 202).

FIG. 36 is a flow chart of an example process 3600 for using an example mobile accessory device. In some implementations, the process 3600 can be performed using one or more of the example mobile device accessories 100A-100L of FIGS. 1-23, and 25-35, and the personal safety device 300 of FIG. 23.

At 3610, an attachment surface of a housing of a mobile accessory device is engaged to a mobile device. For example, the attachment surface 104 of the housing 102 may be configured to engage the rear surface 202 of the mobile phone 200. In another example, the adhesive pad 3502 shown in FIG. 35 can be used to secure the mobile accessory device 100L to a mobile device, such as to the rear surface 202 of the mobile phone 200.

At 3620, a wearable component is donned upon a user of the mobile device. For example, the wearable component 120 of FIG. 5, the wireless wearable component 120D of FIG. 14, and/or the wearable component 120I of FIGS. 22A-F can be worn about a user's wrist. In other examples, the wearable component can donned upon or otherwise carried by a user (e.g., a pendant, a ring, an earring, an earpiece, bracelet, wristwatch, eyeglass frame, hair clip), the user's clothing (e.g., a remote unit carried in the user's pocket, a pin, a badge, clipped to a belt, a belt buckle, head band, hat), and/or the user's personal effects (e.g., a remote unit carried in purse or bag, a key fob, an identification card).

At 3630, a separation sensor detects that the wearable component has separated from the housing. For example, the user input sensor 122 can determine that the wearable component 120 has exceeded a threshold separation distance from the controller 112 and/or that the wearable component 120 has become physically detached from the mobile accessory device 100.

In some embodiments, the process 3600 can include detecting a mechanical separation of the housing and a lanyard affixed to the wearable component, the lanyard having a predetermined length and mechanically connecting the wearable component to the housing, the lanyard being mechanically separable from the housing when distance between the wearable component and the housing exceeds the predetermined length. For example, the user input sensor 122 can determine that the wearable component 120 has become detached, disengaged, or otherwise physically separated from the controller 112.

In some embodiments, detecting that the wearable component has separated from the housing can include determining a signal strength of a wireless tether signal transmitted by a wireless transmitter of the wearable component to a wireless receiver arranged within the housing and in communication with the separation sensor, the signal strength being representative of a distance between the wearable component and the housing, and determining that the signal strength is less than or equal to a predetermined signal strength defining a predetermined separation distance. For example, the user separation sensor arrangement 118 can determine that the wearable component 120D has exceeded a threshold separation distance from the controller 112, or that a periodic beacon transmitted by the wearable component 120D has not been received for a predetermined length of time.

At 3640, an alarm device is activated based on detecting that the wearable component has separated from the housing. For example, the controller 112 of FIG. 7 can be activated. In some embodiments, activating the alarm device can include transmitting an alarm signal; and wherein the process 3600 can also include receiving, by mobile device, the alarm signal, and sending, by the mobile device and in response to the receiving the alarm signal, a predetermined communication to one or more predefined recipients. For example, the controller 112 of FIG. 7 can activate the communication interface 134 to communicate with the mobile phone 200. The mobile phone 200 may have a software application installed and executing thereupon, and the software application can be configured to react to the communication from the mobile accessory device 100E to cause the mobile phone to communicate with one or more predetermined recipients. For example, the software application may be configured to initiate a call, send a text message, email, media file, media stream, location information (e.g., GPS data), captured audio and/or video, or any other appropriate information to one or more contacts previously identified by the user (e.g., family member, friend, neighbor, doctor, nurse, caregiver, welfare official, emergency services, 911)

In some embodiments, activating the alarm device can include activating an audio output component disposed within the housing and configured to emit an audible alert when activated. For example, the controller 112 includes the audio output device 114 that can emit a siren, noise, prerecorded or synthesized spoken words or other sounds, or any other appropriate sound that is sufficiently loud enough to attract the attention of other nearby persons and/or repel an attacker. In some embodiments, activating the alarm device can include activating a visual output configured to emit an audible alert when activated. For example, the controller 112 includes the light output device 116 that can emit a light or strobe to attract the attention of other nearby persons and/or repel an attacker.

In some embodiments, the process 3600 can include removing the wearable component from a cavity defined by the housing, wherein the cavity is sized to accommodate storage of the wearable component. For example, FIGS. 22A-22F show that the example wearable component 120I can be at least partly removed from the mobile accessory device 100I before being worn about the wrist of the user. In some embodiments, the process 3600 can also include doffing the wearable component from the user, and stowing the wearable component in a cavity defined by the housing, wherein the cavity is sized to accommodate storage of the wearable component. For example, the process illustrated by FIGS. 22A-22F can be reversed such that the user can take the wearable component 120I or 120L off his or her wrist, and placed back in the groove 209 or 2909 defined in the housing of the mobile accessory device 100I or 100L.

FIGS. 37a-45 illustrate various views of another example mobile accessory device 100M according to an additional example embodiment of the present disclosure. The mobile accessory device 100M is configured to be attached to the mobile phone 200, either directly or indirectly, as will be discussed further below. The overall configuration and features of the mobile accessory device 100M may be substantially similar to, or a subset of, that of the mobile accessory device 100 of FIG. 1. However, the mobile accessory device 100M of FIGS. 37a-45 may vary in one or more respects.

The mobile accessory device 100M includes a user input sensor having a movable component 144M (e.g., a pull tab), which serves as a user input mechanism, and is configured to activate when the movable component 144M is at least partially moved, and an alarm device (not shown) disposed in the housing 102M and configured to activate in response to activation of the user input sensor. Activation of the alarm device can cause an audible alarm, or cause a software application to be executed on the mobile phone 200, or both. The audible alarm can come either from an optional audio emitting device disposed in the mobile accessory device 100M or (e.g., in embodiments where the mobile accessory device 100M does not include an audio emitting device) from the mobile phone 200, e.g., using a speaker built into the mobile phone 200.

For example, as illustrated, the position of the components of the mobile accessory device 100M relative to a housing 102M may vary. A pull tab 144M is configured to remain in a stowed (e.g., un-extended) configuration until the user releases the pull tab 144M from engagement with the housing 102M or moves the pull tab 144M relative to the housing 102M. Releasing or moving the pull tab 144M may activate one or more features. For example, in response to the pull tab 144M being moved, removed (at least in part), shifted, or released, the positioning system sensor 210 (see, FIG. 7) may be instructed to activate via the communication mechanisms described above. Further, the user's location may be tracked, e.g., using GPS-like functionality built into the mobile phone 200, during the time period in which the pull tab 144M is released and thereby the user's location information may optionally be shared with one or more persons, if desired, e.g., using the communications capabilities of the mobile phone 200 (e.g., phone, email, SMS text).

Further, the mobile accessory device 100M may include a slot 126M or a feature providing equivalent functionality, positioned between the pull tab 144M and the housing 102M. In this regard, in some embodiments the user separation sensor arrangement may be activated, for example, by engaging a fingernail or equivalent in the slot 126M and moving the pull tab 144M. Thereby, based on user input, activation of the user separation sensor arrangement may be conducted quickly (e.g., in an unexpected dangerous situation), if necessary, for example, by moving (at least in part) the pull tab 144M.

In some embodiments, the slot 126M, which serves as a user input mechanism, may be supplemented or substituted with one or more other mechanical features configured to provide frictional, grippable, or graspable surface or element to ease releasing or moving the pull tab 144M. Examples of such mechanical features can include raised or recessed ribs, dimples, latches, loops, hooks, projections, textures (e.g., rough, soft, sticky), or combinations of these or other mechanical features that can promote manual operation (e.g., movement or removal) of the pull tab 144M.

Alternatively, or in addition, other use input mechanisms (e.g., switches or buttons) may be used as a user input mechanism to trigger actuation of the mobile accessory device 100M. In one such embodiment, a switch 128M (e.g., a button) is arranged on a lateral side 3710a of the housing 102M, substantially perpendicular to a major face surface 3712. Another switch 129M is arranged on a lateral side 3710b of the housing 102M, substantially perpendicular to the major face surface 3712 opposite the switch 129M. The switch 128M and/or the switch 129M may be a depressible button, pressure sensitive, or membrane switches defined as a fingertip-sized recess or protrusion having a textured pattern (e.g., to facilitate identification and location of the switch by either sight or touch). In use, the switch 128M and the switch 129M are pressed substantially simultaneously. For example, in the illustrated configuration, a user can squeeze the switch 128M and the switch 129M with two different fingers of one hand in order to activate an alarm, thereby reducing a likelihood of false alarms due to accidental actuation of a single button. The switches may be used to activate an alarm though a predetermined continuous press (e.g., three seconds), through a predetermined series of presses (e.g., three presses within five seconds), or through a particular sequence of presses (e.g., first pressing the switch 128M and then the switch 129M), for example, to reduce the occurrence of accidental activation.

In some implementations, the switches 128M and 129M may activate a different type of action than may be triggered by separation of the pull tab 144M. For example, the mobile accessory device 100M may respond to activation of the switches 128M and 129M by initiating a silent alarm to alert one or more predetermined recipients (e.g., causing the mobile phone 200 to discretely send a message to a preselected contact), while the mobile accessory device 100M may respond to movement or partial removal of the pull tab 144M by initiating an audible alarm and alerting one or more predetermined recipients (e.g., set off a siren and send a message or place a phone call to police). The audible alarm can come either from an optional audio emitting device disposed in the mobile accessory device 100M or (e.g., in embodiments where the mobile accessory device 100M does not include an audio emitting device) from the mobile phone 200, e.g., using a speaker built into the mobile phone 200.

In some embodiments, the movable component (e.g., pull tab 144M) can be configured to be at least partly moved relative to the housing 102M when subjected to a predetermined force. In some embodiments, the mobile accessory device 100M can include a wearable component having a lanyard (e.g., the example wearable component 120) configured to mechanically attach to the housing 102M and/or the pull tab 144M and provide at least the predetermined force to the movable component based on a pull of upon the lanyard and at least partly move the movable component relative to the housing 102M based on the pull.

FIG. 37b shows the mobile accessory device 100M adhered or affixed to a companion mobile accessory device 3701 (e.g., a wallet for holding identification cards, credit cards, cash, or the like) which in turn is adhered or affixed to the mobile phone 200. However, the mobile accessory device 100M can be adhered or affixed directly to the mobile phone 200 without the need for, or use of, the companion mobile accessory device 3701.

FIGS. 38-39 show the mobile accessory device 100M attached to the companion mobile accessory device 3701 without the mobile phone 200, whereas FIG. 40 shows the companion mobile accessory device 3701 alone.

FIGS. 41-43 show the mobile accessory device 100M separate from the companion mobile accessory device 3701. In some implementations, the mobile accessory device 100M can engage (e.g., adhere to) a portion of the mobile phone 200. In some implementations, the mobile accessory device 100M can engage a portion of a companion mobile accessory device 3701 (which will be discussed further in the description of FIGS. 44-45). In some embodiments, the mobile accessory device 100M and the companion mobile accessory device 3701 may be configured as two physically independent components that may be adhered or otherwise mechanically engaged to each other or may be used independently. In some embodiments, the mobile accessory device 100M and the companion mobile accessory device 3701 may be configured as a combined unit (e.g., formed as a monolithic, unitary assembly having a shared housing).

Referring now to FIG. 43, a rear perspective view of the mobile accessory device 100M is shown. A major face 4302 of the rear side of the housing 102M includes an adhesive pad 4301. In use, the adhesive pad 4301 can be contacted against (e.g., adhered to) a surface of the mobile phone 200 (e.g., the rear surface 202), or the surface 3702 of the companion mobile accessory device 3701, or any other appropriate surface.

Referring now to FIGS. 40 and 45, rear perspective views of the companion mobile accessory device 3701 is shown. A rear side 3703 of the companion mobile accessory device 3701 includes an adhesive pad 4001. In use, the adhesive pad 4001 can be contacted against a surface of the mobile phone 200 (e.g., the rear surface 202), or any other appropriate surface.

Referring now primarily to FIGS. 36-40, 44, and 45, the companion mobile accessory device 3701 is shown. The companion mobile accessory device 3701 has a housing that defines a cavity 4002. The cavity 4002 is configured to removably retain one or more wallet-sized cards 3704, such as credit cards, identification cards (e.g., driver's license), loyalty cards, security access cards, folded cash, or any other appropriately sized items.

FIG. 46 is a flow chart of an example process for using an example mobile accessory device. In some implementations, the process 4600 can be performed using one or more of the example mobile device accessories 100A-100L of FIGS. 1-23, and 25-35, the personal safety device 300 of FIG. 23, and the mobile accessory device 100M of FIGS. 37a-43.

At 4610, an attachment surface of a housing of a mobile accessory device is engaged to a mobile device. For example, the major face 4302 of the housing 102M may be configured to engage the rear surface 202 of the mobile phone 200. In another example, the adhesive pad 4301 shown in FIG. 43 can be used to secure (e.g., adhere) the mobile accessory device 100M to the companion mobile accessory device 3701.

At 4620, a user input is received. For example, one or a combination of the switches 128M, 129M may have been pressed by a user. In another example, the pull tab 144M may have been actuated or partly removed by a user.

At 4630, a separation sensor detects, based on the received user input, that the mobile accessory device 100M has been actuated. For example, the user input sensor 122 can determine that the pull tab 144M has been moved, removed (at least partially), released or shifted, or that the switch 128M and/or the button 129M has been pressed.

In some embodiments, the process 4600 can include detecting a mechanical separation of the housing and a lanyard affixed to a wearable component, the lanyard having a predetermined length and mechanically connecting the wearable component to the housing, the lanyard being mechanically separable from the housing when distance between the wearable component and the housing exceeds the predetermined length. For example, the pull tab 144M can be connected to the wearable component 120, and the user input sensor 122 can determine that the wearable component 120 has caused the pull tab 144M to move or at be at least partly removed from the housing 102M.

At 4640, an alarm device is activated based on detecting that the user input has been actuated. For example, the controller 112 of FIG. 7 can be activated. In some embodiments, activating the alarm device can include transmitting an alarm signal; and wherein the process 4600 can also include receiving, by mobile device, the alarm signal, and sending, by the mobile device and in response to the receiving the alarm signal, a predetermined communication to one or more predefined recipients. For example, the controller 112 of FIG. 7 can activate the communication interface 134 to communicate with the mobile phone 200. The mobile phone 200 may have a software application installed and executing thereupon, and the software application can be configured to react to the communication from the mobile accessory device 100M to cause the mobile phone to communicate with one or more predetermined recipients, and/or to emit an audible alarm or other sound. For example, the software application may be configured to initiate a call, send a text message, email, media file, media stream, location information (e.g., GPS data), captured audio and/or video, or any other appropriate information to one or more contacts previously identified by the user (e.g., family member, friend, neighbor, doctor, nurse, caregiver, welfare official, emergency services, 911). In some embodiments, the alarm device can be any appropriate circuit and/or mechanism that is configured for taking a predetermined action in response to a trigger, and does not necessarily require nor preclude that the alarm device is itself capable of generating an audible alarm.

In some embodiments, activating the alarm device can include activating an audio output component disposed within the housing and configured to emit an audible alert when activated. For example, the mobile accessory device 100M can include the audio output device 114 that can emit a siren, noise, prerecorded or synthesized spoken words or other sounds, or any other appropriate sound that is sufficiently loud enough to attract the attention of other nearby persons and/or repel an attacker. In some embodiments, activating the alarm device can include activating a visual output configured to emit an audible alert when activated. For example, the mobile accessory device 100M can include the light output device 116 that can emit a light or strobe to attract the attention of other nearby persons and/or repel an attacker.

In another configuration, the mobile accessory device need not be configured to be physically attachable to the mobile device, but rather may be implemented as a standalone unit that can be carried or worn by a user (e.g., as a wallet attachment or insert, key fob, bracelet, or the like), and which maintains a wireless communication connection between the accessory and the mobile device. In this configuration, other than the lack of physical attachment, the accessory can be designed and implemented to have any or all of the same features and/or functionality as the configuration in which the accessory is designed to be attached to the mobile device, as described above.

FIGS. 47-49B illustrate various views of a mobile accessory device 100N according to an additional example embodiment of the present disclosure. The mobile accessory device 100N is configured to be attached to the mobile phone 200, either directly or indirectly, as will be discussed further below. The overall configuration and features of the mobile accessory device 100N may be substantially similar to, or a subset of, that of the mobile accessory device 100 of FIG. 1. However, the mobile accessory device 100N of FIGS. 47-49B may vary in one or more respects.

The mobile accessory device 100N includes a housing 102N and a user input sensor having a movable component 4744 (e.g., a sliding switch, a pull tab, a trigger component), which serves as a user input mechanism, and is configured to activate when the movable component 4744 is at least partially moved relative to the housing 102N, and controller (e.g., the controller 112 of FIG. 7, not shown here) disposed in the housing 102N and configured to activate in response to activation of the user input sensor. Activation of the controller can cause an audible alarm, or cause a software application to be executed on the mobile phone 200, or both. The audible alarm can come either from an optional audio emitting device disposed in the mobile accessory device 100N or (e.g., in embodiments where the mobile accessory device 100N does not include an audio emitting device) from the mobile phone 200, e.g., using a speaker built into the mobile phone 200.

For example, as illustrated, the position of the components of the mobile accessory device 100N relative to a housing 102N may vary. The movable component 4744 is configured to remain in a stowed (e.g., un-extended) configuration until the user slide the movable component 4744 away from the stowed configuration relative to the housing 102N. Moving or releasing the movable component 4744 may activate one or more features. For example, in response to the movable component 4744 being moved, removed (at least in part), shifted, or released, the position location detector system 154 or 210 (see, FIG. 7) may be instructed to activate via the communication mechanisms described above. Further, the user's location may be tracked, e.g., using GPS-like functionality built into the mobile accessory device 100N or the mobile phone 200, during the time period in which the movable component 4744 is out of its default position and thereby the user's location information may optionally be shared with one or more persons, if desired, e.g., using the communications capabilities of the mobile phone 200 or the mobile accessory device 100N (e.g., phone, email, SMS text).

Further, the mobile accessory device 100N may include a slot 4726, a recess, a depression, a textured area, or a feature providing equivalent functionality to ease movement of the moveable component 4744, positioned between the movable component 4744 and the housing 102N. In this regard, in some embodiments the user input sensor arrangement may be activated, for example, by engaging a fingertip or fingernail or equivalent in the slot 4726 and moving the movable component 4744. Thereby, based on user input, activation of the user separation sensor arrangement may be conducted quickly (e.g., in an unexpected dangerous situation), if necessary, for example, by moving (at least in part) the movable component 4744.

In some embodiments, the movable component 4744, which serves as a user input mechanism, may be supplemented or substituted with one or more other mechanical features configured to provide frictional, grippable, or graspable surface or element to ease releasing or moving the movable component 4744. Examples of such mechanical features can include raised or recessed ribs, dimples, latches, loops, hooks, projections, textures (e.g., rough, soft, sticky), or combinations of these or other mechanical features that can promote manual operation (e.g., movement or removal) of the movable component 4744.

Alternatively, or in addition, other user input mechanisms (e.g., switches or buttons) may be used as a user input mechanism to trigger actuation of the mobile accessory device 100N. In one such embodiment, a switch 128N (e.g., a button) is arranged on a lateral side 4710a of the housing 102N, substantially perpendicular to a major face surface 4712. Another switch 129N is arranged on a lateral side 4710b of the housing 102N, substantially perpendicular to the major face surface 4712 opposite the switch 129N. The switch 128N and/or the switch 129N may be a depressible button, pressure sensitive, or membrane switches defined as a fingertip-sized recess or protrusion having a textured pattern (e.g., to facilitate identification and location of the switch by either sight or touch). In use, the switch 128N and the switch 129N are pressed substantially simultaneously. For example, in the illustrated configuration, a user can squeeze the switch 128N and the switch 129N with two different fingers of one hand in order to activate an alarm, thereby reducing a likelihood of false alarms due to accidental actuation of a single button. The switches may be used to activate an alarm or non-alarm function though a predetermined continuous press (e.g., three seconds), through a predetermined series of presses (e.g., three presses within five seconds), or through a particular sequence of presses (e.g., first pressing the switch 128N and then the switch 129N), for example, to reduce the occurrence of accidental activation. In some embodiments, the user input mechanism can be configured to differentiate between and respond to multiple different user inputs. For example, the user can use one predetermined combination of buttons and press patterns to activate one response, and can use another predetermined combination to active another response. In a more specific example, one press the switch 128N could be used to activate a texting application on the mobile phone, two presses could be used to activate a camera app on the mobile phone, and three presses could be used to activate one or more of the alarm functions.

Alternatively, or in addition, other user input mechanisms (e.g., microphones, audio sensors) may be used as a user input mechanism to trigger actuation of the mobile accessory device 100N. In one such embodiment, the mobile accessory device 100N can include a microphone and sound detector circuit (e.g., the sound detector arrangement 150 and the microphone 152). The sound detector circuit can be configured to respond to predetermined sounds or sound patterns as a user input (e.g., voice commands, shouts, alarms, horns, sirens, beeps, bells). In some implementations, the sound detector circuit can respond to sounds as user inputs by triggering its internal alarm functions, by triggering another device (e.g., activating an application on a mobile phone to send a message for help, causing a mobile phone to emit an audible or visual alarm), or by triggering an existing function of another device (e.g., activating a voice assistant or other voice-responsive feature of a mobile phone or other device in communication with the mobile accessory device 100N).

In some implementations, the switches 128N and 129N may activate a different type of action than may be triggered by separation of the movable component 4744. For example, the mobile accessory device 100N may respond to activation of the switches 128N and 129N by initiating a silent alarm to alert one or more predetermined recipients (e.g., causing the mobile phone 200 to discretely send a message to a preselected contact), while the mobile accessory device 100N may respond to movement or partial removal of the movable component 4744 by initiating an audible alarm and alerting one or more predetermined recipients (e.g., set off a siren and send a message or place a phone call to police). The audible alarm can come either from an optional audio emitting device disposed in the mobile accessory device 100N or (e.g., in embodiments where the mobile accessory device 100N does not include an audio emitting device) from the mobile phone 200, e.g., using a speaker built into the mobile phone 200.

In some embodiments, the movable component 4744 (e.g., pull tab) can be configured to be at least partly moved relative to the housing 102N when subjected to a predetermined force. In some embodiments, the mobile accessory device 100N can include a wearable component having a lanyard (e.g., the example wearable component 120) configured to mechanically attach to the housing 102N and/or the movable component 4744 and provide at least the predetermined force to the movable component based on a pull of upon the lanyard and at least partly move the movable component relative to the housing 102N based on the pull.

The mobile accessory device 100N has a rear surface 4702 substantially parallel to the major face surface 4712. In the illustrated example, an adhesive pad 4810 is affixed to the rear surface 4702. In use, the adhesive pad 4801 can be pressed against another surface (e.g., the rear of the mobile phone 200) to attach the mobile accessory device 100N to the other surface.

FIGS. 49A and 49B illustrate a sectional view of the example mobile accessory device 100N of FIG. 47. These views are provided to show the configuration and operation of the movable component 4744 relative to the housing 102N.

FIG. 49A shows the mobile accessory device 100N in a first configuration (e.g., a triggered configuration). The movable component 4744 is configured to move linearly along the slot 4726. FIG. 49B shows the mobile accessory device 100N in a second configuration (e.g., a default, un-triggered configuration). The movable component 4744 can be slid along the slot 4726 (e.g., inward, toward the center of the housing 102N) to change the movable component 4744 from the first configuration to the second configuration, and the movable component 4744 can be slid along the slot 4726 (e.g., outward, away from the center of the housing 102N) to change the movable component 4744 from the second configuration to the first configuration (e.g., to trigger an alarm function). As the movable component 4744 is actuated between the two configurations, the movable component 4744 activates and releases a switch 4901 (e.g., as part of the user input sensor 122).

FIG. 50 illustrates a perspective from view of the example mobile accessory device 100N of FIGS. 47 and 49B an example companion mobile accessory device 5000. FIG. 51 illustrates a perspective rear view of the example mobile accessory device 100N and companion mobile accessory device 5000. FIGS. 50 and 51 shows the mobile accessory device 100N adhered or affixed to the companion mobile accessory device 5000 (e.g., a wallet for holding identification cards, credit cards, cash, or the like). In some embodiments, the companion mobile accessory device 5000 can, in turn, be adhered, affixed, or otherwise coupled to the mobile phone 200.

Referring now to FIG. 51. A rear side 5002 of the companion mobile accessory device 5000 includes an adhesive pad 5001. In use, the adhesive pad 5001 can be contacted against a surface of the mobile phone 200 (e.g., the rear surface 202), or any other appropriate surface. The companion mobile accessory device 5000 defines a cavity 5003. The cavity 5003 is configured to removably retain one or more wallet-sized cards 5004, such as credit cards, identification cards (e.g., driver's license), loyalty cards, security access cards, folded cash, or any other appropriately sized items.

FIG. 52 illustrates a partially exploded perspective side view of the example mobile accessory device 100N and the companion mobile accessory device 5000. In the illustrated example, the companion mobile accessory device 5000 includes a collection of pins 5201 and tabs 5202, and the mobile accessory device 100N includes a corresponding collection of bores 5203 and slots 5204. The pins 5201 and the bores 5203, and the tabs 5202 and the slots 5204 are configured to matingly engage to mechanically affix the companion mobile accessory device 5000 to the mobile accessory device 100N.

FIGS. 53 and 54 illustrate an example mobile accessory device 5300 having magnetic features. In some embodiments, the mobile accessory device 5300 can be a modification of the example mobile accessory device 100N of FIGS. 47-49B, or the combination of the mobile accessory device 100N and the example companion mobile accessory device 5000 device of FIGS. 50-52.

The mobile accessory device 5300 includes a housing 5302, and the housing 5302 includes an attachment component 5310 that is configured to magnetically engage corresponding magnetic features provided on the rear surface 202 of the mobile phone 200. In some embodiments, the attachment component 5310 can be made of a magnet, a collection of magnets, a magnetic material, or combination of these and any other appropriate passively or actively magnetic components that can magnetically couple the mobile accessory device 5300 to the mobile phone 200.

In some embodiments, the mobile accessory device 5300 can include sensors that can determine whether or not the mobile accessory device 5300 is attached, coupled, or otherwise substantially abutted to the mobile phone 200. For example, the mobile accessory device 5300 can include a switch (e.g., a momentary pin switch that is kept depressed by contact between the mobile accessory device 5300 and the rear surface 202 and released when the two become separated), a photonic sensor (e.g., an illuminator and a photodetector that can detect the presence or absence of illumination reflected off the rear surface 202), or a magnetic sensor (e.g., a Hall sensor or reed switch in the mobile accessory device 5300 that is configured to be activated when mobile accessory device 5300 is moved too far away from the magnetic features provided on the rear surface 202). In some embodiments, the mobile accessory device 5300 can include a wearable component such as a tether or a lanyard (e.g., the example wearable component 120) configured to mechanically attach to the housing 5302 and provide at least a predetermined force to the housing 5302 based on a pull of upon the lanyard and at least partly separate the mobile accessory device 5300 from the mobile phone 200 based on the pull.

FIGS. 55A and 55B illustrate perspective and side views of an example of a mobile accessory device button 5500 according to an additional example embodiment of the present disclosure. The mobile accessory device button 5500 is configured to be attached to the mobile phone 200, either directly or indirectly, as will be discussed further below. The overall configuration and features of the mobile accessory device button 5500 may be substantially similar to, or a subset of, that of the mobile accessory device 100 of FIG. 1. However, the mobile accessory device button 5500 may vary in one or more respects.

The mobile accessory device button 5500 includes a housing 5502 and a button 5504 that serves as a user input mechanism, and is configured to activate when the button 5504 is at least partially moved relative to the housing 5502, and controller (e.g., the controller 112 of FIG. 7, not shown here) disposed in the housing 5502 and configured to activate in response to activation of the user input sensor. In the illustrated example, the housing 5502 and the button 5504 are configured with a generally convex (e.g., domed) shape.

Activation of the controller can cause an audible alarm, or cause a software application to be executed on the mobile phone 200, or both. The audible alarm can come either from an optional audio emitting device disposed in the mobile accessory device button 5500 or (e.g., in embodiments where the mobile accessory device button 5500 does not include an audio emitting device) from the mobile phone 200, e.g., using a speaker built into the mobile phone 200. Alternatively, or in addition, other user input mechanisms (e.g., microphones, audio sensors) may be used as a user input mechanism to trigger actuation of the mobile accessory device button 5500.

A rear side 5506 of the mobile accessory device button 5500 includes an adhesive pad 5508. In use, the adhesive pad 5001 can be contacted against a surface of the mobile phone 200 (e.g., the rear surface 202), or any other appropriate surface. For example, the mobile accessory device button 5500 can be affixed, engaged, adhered, or other otherwise coupled atop a one-handed phone holder that is attached to the mobile phone 200. In some embodiments, the mobile accessory device button 5500 can include magnetic, adhesive, and/or mechanical features to enable attachment, adherence, affixment, engagement, and/or coupling of the mobile accessory device button 5500, directly or indirectly, to the mobile phone 200.

FIGS. 56A and 56B illustrate perspective and side views of an example of a mobile accessory device button 5600 according to an additional example embodiment of the present disclosure. The mobile accessory device button 5600 is configured to be attached to the mobile phone 200, either directly or indirectly, as will be discussed further below. The overall configuration and features of the mobile accessory device button 5600 may be substantially similar to, or a subset of, that of the mobile accessory device 100 of FIG. 1. However, the mobile accessory device button 5600 may vary in one or more respects.

The mobile accessory device button 5600 includes a housing 5602 and a button 5604 that serves as a user input mechanism, and is configured to activate when the button 5604 is at least partially moved relative to the housing 5602, and controller (e.g., the controller 112 of FIG. 7, not shown here) disposed in the housing 5602 and configured to activate in response to activation of the user input sensor. In the illustrated example, the housing 5602 and the button 5604 are configured with a generally concave (e.g., scalloped, indented, recessed) shape.

Activation of the controller can cause an audible alarm, or cause a software application to be executed on the mobile phone 200, or both. The audible alarm can come either from an optional audio emitting device disposed in the mobile accessory device button 5600 or (e.g., in embodiments where the mobile accessory device button 5600 does not include an audio emitting device) from the mobile phone 200, e.g., using a speaker built into the mobile phone 200. Alternatively, or in addition, other user input mechanisms (e.g., microphones, audio sensors) may be used as a user input mechanism to trigger actuation of the mobile accessory device button 5600.

A rear side 5606 of the mobile accessory device button 5600 includes an adhesive pad 5608. In use, the adhesive pad 5001 can be contacted against a surface of the mobile phone 200 (e.g., the rear surface 202), or any other appropriate surface. For example, the mobile accessory device button 5600 can be affixed, engaged, adhered, or other otherwise coupled atop a one-handed phone holder that is attached to the mobile phone 200. In some embodiments, the mobile accessory device button 5600 can include magnetic, adhesive, and/or mechanical features to enable attachment, adherence, affixment, engagement, and/or coupling of the mobile accessory device button 5600, directly or indirectly, to the mobile phone 200.

FIG. 57 is a flow chart of an example process 5700 using an example mobile accessory device. In some implementations, the process 5700 can be performed using one or more of the example mobile device accessories 100A-100N and 5300-5600 of FIGS. 1-23, and 25-35, the personal safety device 300 of FIG. 23, the mobile accessory device 100M of FIGS. 37a-43, the mobile accessory device 100N of FIGS. 47-52, the mobile accessory device 5300 of FIGS. 53-54, and the mobile accessory device buttons 5500 and 5600 of FIGS. 55A-56B.

At an option step 5710, an attachment surface of a housing of a mobile accessory device is engaged to a mobile device. For example, the surface 4801 of the housing 102N may be configured to engage the rear surface 202 of the mobile phone 200. In another example, the attachment component 5310 shown in FIG. 53 can be used to secure (e.g., magnetically couple) the mobile accessory device 5300 to the mobile phone 200.

At 5720, a user input of the mobile accessory device is received. For example, one or a combination or a pattern of the switches 128N, 129N may have been pressed by a user. In another example, the movable component 4744 may have been actuated or partly moved by a user. In another example, the button 5504 may be pressed by a user.

At 5730, a user input sensor detects, based on the received user input, that the mobile accessory device has been actuated. For example, the user input sensor 122 can determine that the movable component 4744 has been moved, removed (at least partially), released, or shifted, or that the switch 128N and/or the button 129N has been pressed.

In some embodiments, the process 5700 can include detecting a mechanical separation of the housing and a lanyard affixed to a wearable component, the lanyard having a predetermined length and mechanically connecting the wearable component to the housing, the lanyard being mechanically separable from the housing when distance between the wearable component and the housing exceeds the predetermined length. For example, the movable component 4744 can be connected to the wearable component 120, and the user input sensor 122 can determine that the wearable component 120 has caused the movable component 4744 to move or at be at least partly removed from the housing 102N.

At 5740, a device function is activated based on detecting that the user input has been actuated. For example, the controller 112 of FIG. 7 can be activated. In some embodiments, activating the device function can include transmitting an alarm signal; and wherein the process 5700 can also include receiving, by mobile device, the alarm signal, and sending, by the mobile device and in response to the receiving the alarm signal, a predetermined communication to one or more predefined recipients. For example, the controller 112 of FIG. 7 can activate the communication interface 134 to communicate with the mobile phone 200. The mobile phone 200 may have a software application installed and executing thereupon, and the software application can be configured to react to the communication from the mobile accessory device 100M to cause the mobile phone to communicate with one or more predetermined recipients, and/or to emit an audible alarm or other sound. For example, the software application may be configured to initiate a call, send a text message, email, media file, media stream, location information (e.g., GPS data), captured audio and/or video, or any other appropriate information to one or more contacts previously identified by the user (e.g., family member, friend, neighbor, doctor, nurse, caregiver, welfare official, emergency services, 911). In some embodiments, the device function can be any appropriate circuit and/or mechanism that is configured for taking a predetermined action in response to a trigger, and does not necessarily require nor preclude that the alarm device is itself capable of generating an audible alarm.

In some embodiments, activating the device function can include activating an audio output component disposed within the housing and configured to emit an audible alert when activated. For example, the mobile accessory device 100N can include the audio output device 114 that can emit a siren, noise, prerecorded or synthesized spoken words or other sounds, or any other appropriate sound that is sufficiently loud enough to attract the attention of other nearby persons and/or repel an attacker. In some embodiments, activating the alarm device can include activating a visual output configured to emit an audible alert when activated. For example, the mobile accessory device 100N can include the light output device 116 that can emit a light or strobe to attract the attention of other nearby persons and/or repel an attacker.

In some embodiments, activating the device function can include activating a non-alarm function of the device. For example, the mobile accessory device 100N can be configured to respond to activation by communicating with the mobile phone 200. The mobile device can be configured (e.g., with an application executing on the mobile phone 200) to receive the communication and respond by activating a function of the mobile phone 200 (e.g., opening an app, taking a photo, triggering an alarm, activating a voice assistant into a standby or listening mode).

In another configuration, the mobile accessory device need not be configured to be physically attachable to the mobile device, but rather may be implemented as a standalone unit that can be carried or worn by a user (e.g., as a wallet attachment or insert, key fob, bracelet, or the like), and which maintains a wireless communication connection between the accessory and the mobile device. In this configuration, other than the lack of physical attachment, the accessory can be designed and implemented to have any or all of the same features and/or functionality as the configuration in which the accessory is designed to be attached to the mobile device, as described above.

FIGS. 58A and 58B illustrate perspective and side views, respectively, of an example mobile device 5800 and an example mobile accessory device 5900 in an expanded configuration. FIGS. 59A and 59B illustrate perspective and side views, respectively, of the example mobile device 5800 and the example mobile accessory device 5900 in a collapsed configuration. In general, the mobile accessory device 5900 includes some or all of the features and functions of the mobile accessory devices described above, integrated into an expandable and collapsible grip for a mobile device.

The mobile accessory device 5900 is configured to be attached to the mobile device 5800, either directly or indirectly, as will be discussed further below. In some embodiments, the mobile device can be the example mobile phone 200 of FIGS. 1-6. The overall configuration and features of the mobile accessory device 5900 may be substantially similar to, or a subset of, that of the example mobile accessory devices 100-100N and 5300 of FIGS. 1-22, 24-35, 37A-43, 47-54, and the example mobile accessory device buttons 5500 and 5600, of FIGS. 55A-56B. However, the mobile accessory device 5900 may vary in one or more respects.

The mobile accessory device 5900 includes a housing 5902, a button 5904, a switch 5906a, and a switch 5906b. The button 5904 and the switches 5906a and 5906b serve as user input mechanisms of a user input apparatus arranged at least partly within the housing 5902, and are configured to activate when the buttons 5904 and/or the switches 5906a and/or 5906b are at least partially moved relative to the housing 5502. Circuitry (e.g., the controller 112 of FIG. 7, not shown here) is disposed at least partly within the housing 5902 and is configured to activate in response to activation of the user input apparatus and trigger one or more predetermined functions including causing a mobile device to perform one or more predetermined mobile device functions.

In the illustrated example, the button 5904 is configured as a compliant (e.g., membrane type) momentary switch that provides a substantially smooth, flush surface that at least partly defines a major surface of the housing 5902. The button 5904 can be pressed upon to provide activation of the controller. In some embodiments, the button 5904 can be vertically moveable relative to the housing 5902 (e.g., like a traditional pushbutton), horizontally moveable (e.g., like a sliding switch), rotatable (e.g., like a rotary dial or switch), non-movable (e.g., a hall sensor, photo sensor, or any other appropriate form of proximity sensor) or can be configured as any appropriate form of switch mechanism or switchable sensing apparatus.

The switch 5906a is arranged on a lateral side 5908a of the housing 5902, substantially perpendicular to a major face surface 5910. Another switch 5906b is arranged on a lateral side 5908b of the housing 5902, substantially perpendicular to the major face surface 5910 opposite the switch 5906a. The switch 5906a and/or the switch 5906b may be depressible button, sliding, pressure sensitive, or membrane switches defined as a fingertip-sized recess or protrusion having a textured pattern (e.g., to facilitate identification and location of the switch by either sight or touch). In use, the switch 5906a and the switch 5906b are pressed substantially simultaneously. For example, in the illustrated configuration, a user can squeeze the switch 5906a and the switch 5906b with two different fingers of one hand in order to activate an alarm, thereby reducing a likelihood of false alarms due to accidental actuation of a single button.

The button 5904 and/or the switches 5906a and/or 5906b may be used to activate an alarm or non-alarm function though a predetermined continuous press (e.g., three seconds), through a predetermined series of presses (e.g., three presses within five seconds), or through a particular sequence of presses (e.g., first pressing the switch 5906a and then the switch 5906b), for example, to reduce the occurrence of accidental activation. In some embodiments, the user input mechanism can be configured to differentiate between and respond to multiple different user inputs. For example, the user can use one predetermined combination of buttons/switches and press patterns to activate one response, and can use another predetermined combination to active another response. In a more specific example, one press of the button 5904 could be used to activate a texting application on the mobile phone, two presses could be used to activate a camera app on the mobile phone, and three presses could be used to activate one or more of the alarm functions.

Activation of the controller can cause an audible alarm, or cause a software application to be executed on the mobile device 5800, or both. The audible alarm can come either from an optional audio emitting device disposed in the mobile accessory device 5900 or (e.g., in embodiments where the mobile accessory device 5900 does not include an audio emitting device) from the mobile device 5800, e.g., using a speaker built into the mobile device 5800.

Alternatively, or in addition, other user input mechanisms (e.g., microphones, audio sensors) may be used as a user input mechanism to trigger actuation of the mobile accessory device 5900. For example, the mobile accessory device 5900 can include a sound detection circuit configured to activate in response to one or more predetermined sounds (e.g., a predefined activation keyword or other utterances that can be recognized when spoken by the user, a shout, glass breakage, alarms or sirens, automobile crash sounds).

In some embodiments, the housing 5902 can include one or more light output devices that can be activated response to activation of the user input apparatus. For example, the housing 5902 can include a collection of lights or a light pipe to provide a halo or ring-like illumination about the periphery of the housing 5902. In another example, the button 5904 can be configured with a luminous layer (e.g., electroluminescent film) that can illuminate some or all of the major face surface 5910 when activated.

A rear side 5920 of the mobile accessory device 5900 defines an attachment surface that includes an adhesive pad (not shown). In use, the adhesive pad can be contacted against a surface of the mobile device 5800 (e.g., the rear surface 202 of the example mobile phone 200), or any other appropriate surface (e.g., a protective phone case). In some embodiments, the mobile accessory device 5900 can include magnetic (e.g., example attachment component 5310), adhesive, and/or mechanical features to enable attachment, adherence, affixment, engagement, and/or coupling of the mobile accessory device 5900, directly or indirectly, to the mobile device 5800.

The housing 5902 is configured as an expandable and collapsible, one-handed phone grip that is affixed or otherwise attached to the mobile device 5800. The housing 5902 a platform 5922 that defines an attachment surface that is attachable to a portable electronic device (e.g., such as the mobile device 5800), a case for a portable electronic device, or other desired component. The housing 5902 is movable between an expanded configuration, as shown in FIGS. 58A-58B, and a collapsed configuration, as shown in FIGS. 59A-59B. In some embodiments, a locking device can be disposed between the housing 5902 and the platform 5922 to rotatably and releasably couple the housing 5902 to the platform 5922. The locking device can be movable between an unlocked configuration, in which the housing 5902 can be removable from the platform 5922, and a locked configuration, in which the housing 5902 can be secured to the platform 5922. When the housing 5902 is in the expanded configuration, the mobile accessory device 5900 can rotate substantially freely about a longitudinal axis perpendicular to the platform 5922.

The housing 5902 has an accordion-like structure 5930 having a collapsible wall 5932. The housing 5902 is movable between the expanded configuration, as shown in FIGS. 58a-58b, and collapsed configuration, as shown in FIGS. 59a-59b. The collapsible wall 5932 can be made of a flexible material, such as polyester-based thermoplastic polyurethane elastomer, that may be formed by injection molding, thermoforming, or compression molding, or may be any equivalently functional material suitable for its intended purpose.

In some embodiments, the mobile accessory device 5900 can include sensors that can determine whether or not the mobile accessory device 5900 is attached, coupled, or otherwise substantially abutted to the mobile device 5800. For example, the mobile accessory device 5900 can include a switch (e.g., a momentary pin switch that is kept depressed by contact between the mobile accessory device 5900 and the mobile device 5800 and released when the two become separated), a photonic sensor (e.g., an illuminator and a photodetector that can detect the presence or absence of illumination reflected off the mobile device 5800), or a magnetic sensor (e.g., a Hall sensor or reed switch in the mobile accessory device 5900 that is configured to be activated when mobile accessory device 5900 is moved too far away from the magnetic features provided on the mobile device 5800). In some embodiments, the mobile accessory device 5900 can include a wearable component such as a tether or a lanyard (e.g., the example wearable component 120) configured to mechanically attach to the housing 5902 and provide at least a predetermined force to the housing 5902 based on a pull of upon the lanyard and at least partly separate the mobile accessory device 5900 from the mobile device 5800 based on the pull.

In some embodiments, the mobile accessory device 5900 can include sensors that can determine whether or not the mobile accessory device 5900 is in the expanded or collapsed configuration. For example, the mobile accessory device 5900 can include a switch (e.g., a momentary pin switch that is kept depressed when the housing 5902 is collapsed and released when the housing 5902 is expanded), a photonic sensor (e.g., an illuminator and a photodetector that can detect the expanded/collapsed configuration of the housing 5902), or a magnetic sensor (e.g., a Hall sensor or reed switch in the mobile accessory device 5900 that is configured to be activated when mobile accessory device 5900 is collapsed in proximity to magnetic features provided on the mobile device 5800). In some embodiments, the mobile accessory device 5900 can include a wearable component such as a tether or a lanyard (e.g., the example wearable component 120) configured to mechanically attach to the housing 5902 and provide at least a predetermined force to the housing 5902 based on a pull of upon the lanyard and at least partly expand the mobile accessory device 5900 from the collapsed configuration based on the pull.

While the housing 5902 has been described as being collapsible, the housing 5902 is not limited to such configurations. In some embodiments, the housing 5902 can be a rigid, semi-rigid, or compliant (e.g., substantially non-collapsible) housing configured to substantially maintain a single grippable configuration, such as the example expanded configuration of FIGS. 58A and 58B.

FIG. 60 is a flow chart of an example process 6000 using an example mobile accessory device. In some implementations, the process 6000 can be performed using the example mobile accessory device 5900 of FIGS. 58A-59B.

At 6010, a mobile device accessory is provided. The mobile device accessory includes a housing including a collapsible grip and defining an attachment surface that is configured to adhere to, attach to, or engage with another surface, a user input apparatus arranged at least partly within the housing and configured to activate in response to input by a user, and a controller arranged at least partly within the housing and configured to activate in response to activation of the user input apparatus and trigger one or more predetermined functions including causing a mobile device to perform one or more predetermined mobile device functions. For example, the mobile accessory device 5900 can be provided.

At 6020, the mobile accessory device is engaged to a surface of a mobile device. For example, the mobile accessory device 5900 can be attached, adhered, magnetically coupled, or otherwise affixed to the mobile device 5800.

In some implementations, engaging the mobile device accessory to a surface of a mobile device can include adhering the grip to the mobile device, mechanically engaging the grip to the mobile device, and/or magnetically attaching the grip to the mobile device. For example, the mobile accessory device 5900 can be adhered to the mobile device 5800 by an adhesive pad. In another example, the mobile accessory device 5900 can include structural features that can be mechanically engaged to mating features on the mobile device 5800. In another example, the mobile accessory device 5900 can include one or more magnets that can magnetically couple to one or more magnets or magnetic materials in the mobile device 5800.

The process 6000 can include, at 6030 and in response to input by the user, (i) causing an audible alarm to be emitted by an audio output device, or (ii) causing a software application to be executed on a mobile device, or (iii) both. For example, actuation of the button 5904 and/or one or both of the switches 5906a-5906b can cause the mobile accessory device 5900 to emit an alert or warning sound, and/or trigger activation of a function of a software application (e.g., an app) installed on the mobile device 5800, and/or a combination of these another any other appropriate form of alarm, notification, or action that can be triggered in response to user input.

The process 6000 can include, at 6040, expanding the grip, wherein the grip includes a body movable between an expanded configuration and a collapsed configuration. For example, the housing 5902 can be expanded to the example configuration shown in FIGS. 58A-58B.

The process 6000 can include, at 6050, collapsing the grip. For example, the housing 5902 can be collapsed to the example configuration shown in FIGS. 59A-59B.

In some implementations, the mobile accessory device can include one or more of (a) a first button at least partly defining a major surface of the housing (e.g., the button 5904), (b) at least one second button arranged on a lateral surface defined by the housing (e.g., the switches 5906a and 5906b), and (c) a sound detection circuit configured to activate in response to one or more predetermined sounds (e.g., a microphone connected to the controller in the mobile accessory device 5900).

In some implementations, the process 6000 can include receiving, by the sound detection circuit, a sound, identifying, by the sound detection circuit, the sound as corresponding to a predetermined sound, and activating the user input apparatus based on the identifying. For example, the mobile accessory device 5900 can include a sound detection circuit configured to activate in response to one or more predetermined sounds (e.g., a predefined activation keyword or other utterances that can be recognized when spoken by the user, a shout, glass breakage, alarms or sirens, automobile crash sounds).

In some implementations, the process 6000 can include detecting, by control circuitry of a mobile accessory device, user input based on activation of a user input apparatus, establishing a communications connection from the control circuitry to a communication circuit of the mobile device, and communicating with the communication circuit. For example, the mobile accessory device 5900 can include the example controller 112 of FIG. 7, which can activate the communication interface 134 to communicate with the mobile device 5800. The mobile device 5800 may have a software application installed and executing thereupon, and the software application can be configured to react to the communication from the mobile accessory device 5900 to cause the mobile device 5800 to communicate with one or more predetermined recipients, and/or to emit an audible alarm or other sound. For example, the software application may be configured to initiate a call, send a text message, email, media file, media stream, location information (e.g., GPS data), captured audio and/or video, or any other appropriate information to one or more contacts previously identified by the user (e.g., family member, friend, neighbor, doctor, nurse, caregiver, welfare official, emergency services, 911). In some embodiments, the device function can be any appropriate circuit and/or mechanism that is configured for taking a predetermined action in response to a trigger, and does not necessarily require nor preclude that the alarm device is itself capable of generating an audible alarm.

In some implementations, activation of the user input apparatus can include substantially simultaneous actuation of a first button arranged on a first lateral surface defined by the housing, and a second button arranged on a second lateral surface opposite the first button. For example, in the illustrated configuration, a user can squeeze the switch 5906a and the switch 5906b with two different fingers of one hand in order to activate an alarm. In another example, the switches 5906a and/or 5906b may be used to activate an alarm though a predetermined continuous press, through a predetermined series of presses, or through a particular sequence of presses.

In some implementations, the user input apparatus can include a button, and activation of the user input apparatus includes detecting a predetermined pattern of presses of the button. For example, the button 5904 can be used to activate an alarm though a predetermined continuous press, and/or through a predetermined series of presses.

In some implementations, the process 6000 can include activating, in response to input by the user, an alarm device having (i) an audio output device, (ii) a light output device, or (iii) both. For example, pressing the button 5904 and/or one or both of the switches 5906a-5906b can cause the example controller 112 to cause the example audio output device 114 to emit a sound. In another example, pressing the button 5904 and/or one or both of the switches 5906a-5906b can cause the example controller 112 to activate the example light output device 116.

FIG. 61 is a block diagram of computing devices 6100, 6150 that may be used to implement the systems and methods described in this document, either as a client or as a server or plurality of servers. Computing device 6100 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Computing device 6100 can also represent all or parts of various forms of computerized devices, such as embedded digital controllers, media bridges, modems, network routers, network access points, network repeaters, and network interface devices including mesh network communication interfaces. Computing device 6150 is intended to represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smartphones, and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed in this document.

Computing device 6100 includes a processor 6102, a memory 6104, a storage device 6106, a high-speed interface 6108 connecting to memory 6104 and high-speed expansion ports 6110, and a low speed interface 6112 connecting to a low speed bus 6114 and storage device 6106. Each of the components 6102, 6104, 6106, 6108, 6110, and 6112, are interconnected using various busses, and may be mounted on a common motherboard or in other manners as appropriate. The processor 6102 can process instructions for execution within the computing device 6100, including instructions stored in the memory 6104 or on the storage device 6106 to display graphical information for a GUI on an external input/output device, such as display 6116 coupled to high speed interface 6108. In other implementations, multiple processors and/or multiple buses may be used, as appropriate, along with multiple memories and types of memory. Also, multiple computing devices 6100 may be connected, with each device providing portions of the necessary operations (e.g., as a server bank, a group of blade servers, or a multi-processor system).

The memory 6104 stores information within the computing device 6100. In one implementation, the memory 6104 is a computer-readable medium. In one implementation, the memory 6104 is a volatile memory unit or units. In another implementation, the memory 6104 is a non-volatile memory unit or units.

The storage device 6106 is capable of providing mass storage for the computing device 6100. In one implementation, the storage device 6106 is a computer-readable medium. In various different implementations, the storage device 6106 may be a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory or other similar solid state memory device, or an array of devices, including devices in a storage area network or other configurations. In one implementation, a computer program product is tangibly embodied in an information carrier. The computer program product contains instructions that, when executed, perform one or more methods, such as those described above. The information carrier is a computer- or machine-readable medium, such as the memory 6104, the storage device 6106, or memory on processor 6102.

The high speed controller 6108 manages bandwidth-intensive operations for the computing device 6100, while the low speed controller 6112 manages lower bandwidth-intensive operations. Such allocation of duties is exemplary only. In one implementation, the high-speed controller 6108 is coupled to memory 6104, display 6116 (e.g., through a graphics processor or accelerator), and to high-speed expansion ports 6110, which may accept various expansion cards (not shown). In the implementation, low-speed controller 6112 is coupled to storage device 6106 and low-speed expansion port 6117 through the low-speed bus 6114. The low-speed expansion port, which may include various communication ports (e.g., Universal Serial Bus (USB), BLUETOOTH, BLUETOOTH Low Energy (BLE), Ethernet, wireless Ethernet (WiFi), High-Definition Multimedia Interface (HDMI), ZIGBEE, visible or infrared transceivers, Infrared Data Association (IrDA), fiber optic, laser, sonic, ultrasonic) may be coupled to one or more input/output devices, such as a keyboard, a pointing device, a scanner, a networking device such as a gateway, modem, switch, or router, e.g., through a network adapter 6113.

Peripheral devices can communicate with the high speed controller 6108 through one or more peripheral interfaces of the low speed controller 6112, including but not limited to a USB stack, an Ethernet stack, a WiFi radio, a BLUETOOTH Low Energy (BLE) radio, a ZIGBEE radio, a THREAD radio, an HDMI stack, and a BLUETOOTH radio, as is appropriate for the configuration of the particular sensor. For example, a sensor that outputs a reading over a USB cable can communicate through a USB stack.

The network adapter 6113 can communicate with a network 6115. Computer networks typically have one or more gateways, modems, routers, media interfaces, media bridges, repeaters, switches, hubs, Domain Name Servers (DNS), and Dynamic Host Configuration Protocol (DHCP) servers that allow communication between devices on the network and devices on other networks (e.g. the Internet). One such gateway can be a network gateway that routes network communication traffic among devices within the network and devices outside of the network. One common type of network communication traffic that is routed through a network gateway is a Domain Name Server (DNS) request, which is a request to the DNS to resolve a uniform resource locator (URL) or uniform resource indicated (URI) to an associated Internet Protocol (IP) address.

The network 6115 can include one or more networks. The network(s) may provide for communications under various modes or protocols, such as Global System for Mobile communication (GSM) voice calls, Short Message Service (SMS), Enhanced Messaging Service (EMS), or Multimedia Messaging Service (MMS) messaging, Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Personal Digital Cellular (PDC), Wideband Code Division Multiple Access (WCDMA), CDMA2000, General Packet Radio System (GPRS), or one or more television or cable networks, among others. For example, the communication may occur through a radio-frequency transceiver. In addition, short-range communication may occur, such as using a BLUETOOTH, BLE, ZIGBEE, WiFi, IrDA, or other such transceiver.

In some embodiments, the network 6115 can have a hub-and-spoke network configuration. A hub-and-spoke network configuration can allow for an extensible network that can accommodate components being added, removed, failing, and replaced. This can allow, for example, more, fewer, or different devices on the network 6115. For example, if a device fails or is deprecated by a newer version of the device, the network 6115 can be configured such that network adapter 6113 can to be updated about the replacement device.

In some embodiments, the network 6115 can have a mesh network configuration (e.g., ZIGBEE). Mesh configurations may be contrasted with conventional star/tree network configurations in which the networked devices are directly linked to only a small subset of other network devices (e.g., bridges/switches), and the links between these devices are hierarchical. A mesh network configuration can allow infrastructure nodes (e.g., bridges, switches and other infrastructure devices) to connect directly and non-hierarchically to other nodes. The connections can be dynamically self-organize and self-configure to route data. By not relying on a central coordinator, multiple nodes can participate in the relay of information. In the event of a failure of one or more of the nodes or the communication links between then, the mesh network can self-configure to dynamically redistribute workloads and provide fault-tolerance and network robustness.

The computing device 6100 may be implemented in a number of different forms, as shown in the figure. For example, it may be implemented as a standard server 6120, or multiple times in a group of such servers. It may also be implemented as part of a rack server system 6124. It may also be implemented as part of network device such a modem, gateway, router, access point, repeater, mesh node, switch, hub, or security device (e.g., camera server). In addition, it may be implemented in a personal computer such as a laptop computer 6122. Alternatively, components from computing device 6100 may be combined with other components in a mobile device (not shown), such as device 6150. In some embodiments, the device 6150 can be a mobile telephone (e.g., a smartphone), a handheld computer, a tablet computer, a network appliance, a camera, an enhanced general packet radio service (EGPRS) mobile phone, a media player, a navigation device, an email device, a game console, an interactive or so-called “smart” television, a media streaming device, or a combination of any two or more of these data processing devices or other data processing devices. In some implementations, the device 6150 can be included as part of a motor vehicle (e.g., an automobile, an emergency vehicle (e.g., fire truck, ambulance), a bus). Each of such devices may contain one or more of computing device 6100, 6150, and an entire system may be made up of multiple computing devices 6100, 6150 communicating with each other through a low speed bus or a wired or wireless network.

Computing device 6150 includes a processor 6152, memory 6164, an input/output device such as a display 6154, a communication interface 6166, and a transceiver 6168, among other components. The device 6150 may also be provided with a storage device, such as a microdrive or other device, to provide additional storage. Each of the components 6150, 6152, 6164, 6154, 6166, and 6168, are interconnected using various buses, and several of the components may be mounted on a common motherboard or in other manners as appropriate.

The processor 6152 can process instructions for execution within the computing device 6150, including instructions stored in the memory 6164. The processor may also include separate analog and digital processors. The processor may provide, for example, for coordination of the other components of the device 6150, such as control of user interfaces, applications run by device 6150, and wireless communication by device 6150. Suitable processors for the execution of a program of instructions include, by way of example, both general and special purpose microprocessors, and the sole processor or one of multiple processors of any kind of computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. The processor can be supplemented by, or incorporated in, ASICs (application-specific integrated circuits), FPGAs (field programmable gate arrays), PLDs (programmable logic devices)

Processor 6152 may communicate with a user through control interface 6158 and display interface 6156 coupled to a display 6154. The display 6154 may be, for example, a TFT LCD display or an OLED display, or other appropriate display technology. The display interface 6156 may include appropriate circuitry for driving the display 6154 to present graphical and other information to a user. The control interface 6158 may receive commands from a user and convert them for submission to the processor 6152. In addition, an external interface 6162 may be provide in communication with processor 6152, so as to enable near area communication of device 6150 with other devices. External interface 6162 may provide, for example, for wired communication (e.g., via a docking procedure) or for wireless communication (e.g., via Bluetooth or other such technologies).

The memory 6164 stores information within the computing device 6150. In one implementation, the memory 6164 is a computer-readable medium. In one implementation, the memory 6164 is a volatile memory unit or units. In another implementation, the memory 6164 is a non-volatile memory unit or units. Expansion memory 6174 may also be provided and connected to device 6150 through expansion interface 6172, which may include, for example, a SIMM card interface. Such expansion memory 6174 may provide extra storage space for device 6150, or may also store applications or other information for device 6150. Specifically, expansion memory 6174 may include instructions to carry out or supplement the processes described above, and may include secure information also. Thus, for example, expansion memory 6174 may be provide as a security module for device 6150, and may be programmed with instructions that permit secure use of device 6150. In addition, secure applications may be provided via the SIMM cards, along with additional information, such as placing identifying information on the SIMM card in a non-hackable manner.

The memory may include for example, flash memory and/or MRAM memory, as discussed below. In one implementation, a computer program product is tangibly embodied in an information carrier. The computer program product contains instructions that, when executed, perform one or more methods, such as those described above. The information carrier is a computer- or machine-readable medium, such as the memory 6164, expansion memory 6174, or memory on processor 6152.

Device 6150 may communicate wirelessly through communication interface 6166, which may include digital signal processing circuitry where necessary. Communication interface 6166 may provide for communications under various modes or protocols, such as GSM voice calls, Voice Over LTE (VOLTE) calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, GPRS, WiMAX, LTE, 4G, and/or 5G, among others. Such communication may occur, for example, through radio-frequency transceiver 6168. In addition, short-range communication may occur, such as using a Bluetooth, WiFi, or other such transceiver (not shown) configured to provide uplink and/or downlink portions of data communication. In addition, GPS receiver module 6170 may provide additional wireless data to device 6150, which may be used as appropriate by applications running on device 6150.

Device 6150 may also communication audibly using audio codec 6160, which may receive spoken information from a user and convert it to usable digital information. Audio codex 6160 may likewise generate audible sound for a user, such as through a speaker, e.g., in a handset of device 6150. Such sound may include sound from voice telephone calls, may include recorded sound (e.g., voice messages, music files, etc.) and may also include sound generated by applications operating on device 6150.

The computing device 6150 may be implemented in a number of different forms, as shown in the figure. For example, it may be implemented as a cellular telephone 6180. It may also be implemented as part of a smartphone 6182, personal digital assistant, or other similar mobile device.

Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

These computer programs (also known as programs, software, software applications or code) include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms “machine-readable medium” “computer-readable medium” refers to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), and the Internet.

Some communication networks can be configured to carry power as well as information on the same physical media. This allows a single cable to provide both data connection and electric power to devices. Examples of such shared media include power over network configurations in which power is provided over media that is primarily or previously used for communications. One specific embodiment of power over network is Power Over Ethernet (POE) which pass electric power along with data on twisted pair Ethernet cabling. Examples of such shared media also include network over power configurations in which communication is performed over media that is primarily or previously used for providing power. One specific embodiment of network over power is Power Line Communication (PLC) (also known as power-line carrier, power-line digital subscriber line (PDSL), mains communication, power-line telecommunications, or power-line networking (PLN), Ethernet-Over-Power (EOP)) in which data is carried on a conductor that is also used simultaneously for AC electric power transmission.

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

The computing system can include routers, gateways, modems, switches, hub, bridges, and repeaters. A router is a networking device that forwards data packets between computer networks and performs traffic directing functions. A network switch is a networking device that connects networked devices together by performing packet switching to receive, process, and forward data to destination devices. A gateway is a network device that allows data to flow from one discrete network to another. Some gateways can be distinct from routers or switches in that they can communicate using more than one protocol and can operate at one or more of the seven layers of the open systems interconnection model (OSI). A media bridge is a network device that converts data between transmission media so that it can be transmitted from computer to computer. A modem is a type of media bridge, typically used to connect a local area network to a wide area network such as a telecommunications network. A network repeater is a network device that receives a signal and retransmits it to extend transmissions and allow the signal can cover longer distances or overcome a communications obstruction.

As used herein, the terms “circuit”, “circuitry”, “controller” are used to mean any and every electronic or electrical device (including not only discrete hardware components, but also programmable devices such as a PLD, software executed by a general purpose or special purpose microprocessor, or the like. Nothing in this document, except where otherwise indicated, can be used to suggest that functionality described herein is necessarily implemented purely by hardware components.

Although a few implementations have been described in detail above, other modifications are possible. For example, the logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. In addition, other steps may be provided, or steps may be eliminated, from the described flows, and other components may be added to, or removed from, the described systems. Accordingly, other implementations are within the scope of the following claims.

Claims

1. A mobile accessory device comprising: a housing comprising a collapsible grip and defining an attachment surface that is configured to adhere to, attach to, or engage with another surface;a user input apparatus arranged at least partly within the housing and configured to activate in response to input by a user; anda controller arranged at least partly within the housing and configured to activate in response to activation of the user input apparatus and trigger one or more predetermined functions including causing a mobile device to perform one or more predetermined mobile device functions.

2. The mobile accessory device of claim 1, wherein the collapsible grip comprises a body movable between an expanded configuration and a collapsed configuration.

3. The mobile accessory device of claim 1, wherein the collapsible grip is configured to adhere to the mobile device.

4. The mobile accessory device of claim 1, wherein the collapsible grip is configured to mechanically engage the mobile device.

5. The mobile accessory device of claim 1, wherein the user input apparatus comprises one or more of: (a) a first button at least partly defining a major surface of the housing;(b) at least one second button arranged on a lateral surface defined by the housing; and(c) a sound detection circuit configured to activate in response to one or more predetermined sounds.

6. The mobile accessory device of claim 5, wherein the one or more predetermined sounds comprises one or more utterances that can be recognized when spoken by the user.

7. The mobile accessory device of claim 1, wherein the user input apparatus comprises a first button arranged on a first lateral surface defined by the housing, and a second button arranged on a second lateral surface opposite the first button.

8. The mobile accessory device of claim 1, further comprising an alarm device comprising (i) an audio output device, (ii) a light output device, or (iii) both, configured to activate in response to activation of the user input apparatus.

9. The mobile accessory device of claim 1, wherein activation of the controller causes a software application to be executed on the mobile device.

10. The mobile accessory device of claim 1, wherein the one or more predetermined mobile device functions comprises (i) causing an audible alarm to be emitted by the mobile device, or (ii) causing a software application to be executed on the mobile device, or (iii) both.

11. A method of using a mobile accessory device, comprising: providing a mobile accessory device comprising: a housing comprising a collapsible grip and defining an attachment surface that is configured to adhere to, attach to, or engage with another surface;a user input apparatus arranged at least partly within the housing and configured to activate in response to input by a user; anda controller arranged at least partly within the housing and configured to activate in response to activation of the user input apparatus and trigger one or more predetermined functions including causing a mobile device to perform one or more predetermined mobile device functions; andengaging the mobile accessory device to a surface of a mobile device.

12. The method of claim 11, further comprising, in response to input by the user, (i) causing an audible alarm to be emitted by an audio output device, or (ii) causing a software application to be executed on the mobile device, or (iii) both.

13. The method of claim 11, further comprising expanding or collapsing the collapsible grip, wherein the collapsible grip comprises a body movable between an expanded configuration and a collapsed configuration.

14. The method of claim 11, wherein engaging the mobile accessory device to a surface of a mobile device comprises: adhering the collapsible grip to the mobile device;mechanically engaging the collapsible grip to the mobile device; ormagnetically attaching the collapsible grip to the mobile device.

15. The method of claim 11, wherein the mobile accessory device further comprises one or more of: (a) a first button at least partly defining a major surface of the housing;(b) at least one second button arranged on a lateral surface defined by the housing; and(c) a sound detection circuit configured to activate in response to one or more predetermined sounds.

16. The method of claim 15, further comprising: receiving, by the sound detection circuit, a sound;identifying, by the sound detection circuit, the sound as corresponding to a predetermined sound; andactivating the user input apparatus based on the identifying.

17. The method of claim 11, further comprising: detecting, by the controller, user input based on activation of a user input apparatus;establishing a communications connection from the controller to a communication circuit of the mobile device; andcommunicating with the communication circuit.

18. The method of claim 17, wherein activation of the user input apparatus comprises substantially simultaneous actuation of a first button arranged on a first lateral surface defined by the housing, and a second button arranged on a second lateral surface opposite the first button.

19. The method of claim 17, wherein the user input apparatus comprises a button, and activation of the user input apparatus comprises detecting a predetermined pattern of presses of the button.

20. The method of claim 17, further comprising activating, in response to input by the user, an alarm device comprising (i) an audio output device, (ii) a light output device, or (iii) both.

21. The method of claim 11, further comprising performing one or more predetermined mobile device functions comprising: (i) causing an audible alarm to be emitted by the mobile device, or (ii) causing a software application to be executed on the mobile device, or (iii) both.