CROSS REFERENCE TO RELATED APPLICATIONS AND PRIORITY
[0001] The present application does not claim priority from any patent application.
TECHNICAL FIELD
[0002] The present disclosure in general relates to the field of mobile devices. More particularly, the present disclosure relates to a system and method for dismount of a mobile device holder.
BACKGROUND
[0003] Mobile devices, such as smart-phones, tablets, PDA devices, etc. have become a necessity for business as well as personal activities. These devices are used not only for communication with one another but also for other purposes such as preparing documents, sending emails, surfing websites, playing games, and the like. Further, these devices help a person in performing daily chores such as paying bills, banking, shopping, finding locations, and the like.
[0004] Generally, vehicle mounts or docks for mobile devices are mainly used for aiding the driver to use a mobile device for GPS functionalities. A driver, for example, may mount the mobile device using a holder mounted on the dashboard. In such a scenario, the holder may be extended towards the face of the driver in a protruding fashion in order to help the driver clearly view the mobile device screen. Though this may be useful for the driver in case of normal operation of the vehicle, however, in case of a crash, the protruding holder may cause facial injuries to the driver.
SUMMARY
[0005] This summary is provided to introduce aspects related to device and method for facilitating movement of a mobile device holder, further described below in the detailed description. This summary is not intended to identify essential features of the claimed disclosure nor is it intended for use in determining or limiting the scope of the claimed disclosure.
[0006] In another implementation, a mobile device holder is disclosed, in accordance with embodiments of the present disclosure. The mobile device may be mounted within a vehicle. The mobile device holder may include a memory and a processor. The processor may be configured to execute instructions stored in the memory to detect a crash condition for the vehicle. The processor may be further configured to execute instructions
3
stored in the memory to generate a signal based on the detected crash condition. Further, the processor may be configured to transmit the signal to a locking unit for disengaging the mobile device holder from a mounted position in the vehicle.
[0007] In yet another implementation, a method for disengaging a mobile device holder is disclosed, in accordance with an embodiment of the present disclosure. The method includes obtaining, by a processor, from a crash detector, information associated with a vehicle. The method further includes detecting, by the processor, a crash condition for the vehicle based on the obtained information. The method further includes generating, by the processor, a signal based on the detected crash condition. The method further includes transmitting, by the processor, the signal to a locking unit for disengaging the mobile device holder from a mounted position in the vehicle.
BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to refer like features and components.
[0009] Figure 1 illustrates network implementation of a mobile device holder, in accordance with an embodiment of the present disclosure.
[0010] Figure 2 illustrates an exemplary mobile device holder, in accordance with an embodiment of the present disclosure.
[0011] Figure 3 illustrates a method for disengaging a mobile device holder, in accordance with an embodiment of the present disclosure.
DETAILED DESCRIPTION
[0012] The present disclosure relates to a method and system for disengaging a mobile device holder from a mounted position within a vehicle. The mobile device holder may be moved based on context of one or more applications running on the mobile device. The various embodiments of the present disclosure are described with regards to the mobile device holder holding the mobile device and mounted within a vehicle. However, a person skilled in the art would appreciate that, other implementations for the movement of the mobile device holder may be possible, and those are covered within the scope of the present disclosure.
4
[0013] The present systems and methods will now be described more fully hereinafter with reference to the accompanying drawings in which exemplary embodiments of the invention are shown. However, the invention may be embodied in many different forms and should not be construed as limited to the representative embodiments set forth herein. The exemplary embodiments are provided so that this disclosure will be both thorough and complete, and will fully convey the scope of the invention and enable one of ordinary skill in the art to make, use and practice the invention. Like reference numbers refer to like elements throughout the various drawings.
[0014] Referring now to Figure 1, a network implementation 100 of a mobile device holder 102, in accordance with an embodiment of the present disclosure. The mobile device holder 102 may include a receptacle 104 for holding a mobile device such as a mobile phone, a tablet, a PDA device, a GPS device, and the like. The mobile device holder 102 may further include at least one processor 106. The at least one processor 106 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor 106 is configured to fetch and execute computer-readable instructions or modules stored in a memory (not shown).
[0015] As depicted, the mobile device holder 102 may further include a locking unit 108. In an implementation, the locking unit 108 may be used to secure the mobile device holder 102 to a mounting surface, for example, a dashboard of a vehicle. The locking unit 108, in one example, may include a clamp (not shown) to secure the mobile device holder 102 onto the mounting surface. In another example, a gas filled pouch (not shown) may be provided for creating a vacuum between the mobile device holder 102 and the mounting surface and thus securing the mobile device holder 102 onto the mounting surface. Further, the mobile device holder 102 may be mounted onto the mounting surface initially by manually locking the mobile device holder 102 on the mounting surface using the clamp or by sticking the mobile device holder 102 using the gas filled pouch (not shown). In an embodiment, the locking unit 108 may automatically disengage the mobile device holder 102 from the mounting surface based on signals received by the processor 106.
[0016] The mobile device holder 102 may further include a crash detector 110. In an implementation, the crash detector 110 may be configured to identify a crash or accident condition associated with the vehicle within which the mobile device holder 102 is
5
mounted. In an implementation, the crash detector 110 may detect the crash situation based on one or more parameters such as deceleration, vibrations, angular velocity, magnetic field etc. associated with the vehicle. The crash detector 110, in one implementation, may transmit the crash condition information to the processor 106. In an alternate implementation, the processor 106 may also receive the crash condition information from a crash detection system inbuilt in the vehicle.
[0017] The processor 106 may process the crash condition information and generate a signal based on the crash condition detected. Further, the processor 106 may transmit the signal to the locking unit 108 for disengaging the mobile device holder 102 from the mounting surface as soon as the crash condition is detected. In an exemplary implementation, the locking unit 108 may automatically disengage the mobile device holder 102 from the mounting surface based on signal received from the processor 106. As described in the foregoing, the mobile device holder 102 may be initially mounted onto the mounting surface either by a clamp or by using a gas filled pouch. In the implementation, for automatically disengaging the mobile device holder 102, the clamp may be unfastened by an actuator (not shown) included in the locking unit 108. In another implementation, the locking unit 108, based on the received signal, may activate a pin-like structure (not shown) to make a small orifice into the gas-filled pouch such that an air bubble may be generated within the gas-filled pouch. Due to the air-bubble, the vacuum between the mobile device holder 102 and the mounting surface may be eliminated, thus causing the mobile device holder 102 to free fall. Such a free fall of the mobile device holder 102 may ensure that a driver of the vehicle does not bump his/her face into the mobile device holder 102 and hence injury may be avoided.
[0018] Referring back to the fig, the mobile device holder 102 may also include a battery panel 112. In an implementation, the battery panel 112 may charge operational components of the mobile device holder 102.
[0019] In an implementation, the processor 106 may be configured to send a notification regarding the detected crash condition to at least one predefined user device 114. In the implementation, the notification may include information associated with location of crash, time of crash, list of hospitals in vicinity of the location of crash, and the like. In an implementation, the mobile holder 102 may transmit the notification to the predefined user device 114 over the network 116.
[0020] In one implementation, the network 116 may be a wireless network, a wired network or a combination thereof. The network 116 can be implemented as one of the
6
different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 116 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further the network 116 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.
[0021] In an embodiment, the processor 106 may also transmit the notification about the crash condition to a law enforcement agency (LEA) server 118. In an example, the LEA server 118 may belong to police department, traffic control department, and the like in vicinity of the location of crash. In an example, the processor 106 may detect the location of crash based on GPS information from a mobile device held in the receptacle 104. In another example, the mobile device holder 102 may be capable of detecting the current location of crash using techniques such as triangulation, and the like. Based on the location of crash, the LEA server 118 may be selected for sending the notification, accordingly. In an exemplary implementation, the mobile device holder 102 may tether to the mobile device held in the receptacle 104 for transmitting the notification to the LEA.
[0022] In another embodiment, the processor 106 may transmit an alert to the LEA server 118 in case it is detected that the mobile device holder 102 is remounted without authorized repair, after a crash situation. For example, a user using the mobile device holder 102 may be required to get the mobile device holder 102 repaired and quality checked before it could be mounted again. Further, after each repair activity, an operational status of the mobile device holder 102 may be updated within the LEA 118. This may ensure that the mobile device holder 102 is tested for safe usage each time.
[0023] Figure 2 illustrates various operational components of a mobile device holder 200, in accordance with an embodiment of the present disclosure. As described in the foregoing, the mobile device holder 200 may include a receptacle 202 for holding a mobile device 204. The mobile device holder 200 may further include a processor 206 and a battery panel 208. In an embodiment, the battery panel 208 may include one or more solar cells (not shown) for charging the battery panel 208. The battery panel 208 may thus be charged without the requirement of an external charging source, such as a car charger. The mobile device holder 200 may further include a connector element 210.
7
The connector element 210, in an example, may be responsible for communication between the processor 206 of the mobile device holder 200 and a processor (not shown) of the mobile device 204. In an example, the connector element 210 may be a Bluetooth® module. In another example, the connector element 210 may be a Wi-Fi router, a NFC device or an IR chip. The mobile device holder 200 may further include a locking unit 212 for clamping and unclamping the mobile device holder 200 from a mounting surface in a vehicle. In an alternate implementation, the mobile device holder 200 may be mounted on the mounting surface by a gas filled pouch 214. The gas filled pouch 214, in one example, may create a vacuum between the mobile device holder base (not shown) and a mounting surface. The mobile device holder 200 may also include an optional crash detector 216 for detecting a crash condition for the vehicle. In an alternate implementation, crash condition information may be received from a crash detection unit (not shown) of the vehicle.
[0024] In operation, information associated with the crash condition of the vehicle may be transmitted by the crash detector 216 to the processor 206. The processor 206, as soon as receiving the information, may generate a signal based on the detected crash condition. The processor 206 may then transmit the signal to the locking unit 212. In an implementation, the locking unit 212 may include an actuator (not shown), such that based on the received signal, the actuator may disengage a clamp (not shown). Disengaging the clamp would in turn result free fall of the mobile device holder 200 from the mounting surface. In an alternative implementation, in case the gas filled pouch 214 is used for sticking the mobile device holder 200 on the mounting surface, the locking unit 212 may activate a pin-like structure (not shown) for creating a small orifice within the gas filled pouch 214. This may disengage the mobile device holder 200 from the mounting surface by eliminating vacuum between the mobile device holder 200 and the mounting surface. Hence, the mobile device holder 200 may free fall from the mounting surface.
[0025] In an embodiment, the processor 206 may transmit a notification regarding the crash to one or more user devices and/or to a law enforcing agency server. Further, in case of remount of the mobile device holder 200 after a crash, the processor 206 may generate an alert to be sent to the law enforcing agency server if it is detected that the mobile device holder 200 is being used without authorized repair. This may ensure that the mobile device holder 200 is always operated in a safe mode.
8
[0026] In an exemplary implementation, the one or more predefined user devices may be registered for receiving notifications about the crash condition, using a webpage (not shown) associated with the mobile device holder 200. Further, other settings associated with the mobile device holder 200 may be configured through the webpage. In an example, the webpage may be accessed using a conventional mobile device or computer.
[0027] Figure 3 illustrates a method 300 for disengaging a mobile device holder from a mounting surface within a vehicle. The method may start at step 302 wherein information associated with a crash condition of the vehicle may be received from a crash detector. In an example, the information may include deceleration data, angular velocity data, and the like associated with the vehicle.
[0028] At step 304, a signal may be generated based on the obtained information. In an example, the signal may be generated by a processor integral to the mobile device holder.
[0029] Further, at step 308, the signal may be transmitted to a locking unit for disengaging the mobile device holder from the mounted surface in the vehicle.
[0030] Although implementations for methods and systems for identifying relevant test cases have been described in language specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations for changing orientation of a mobile device holder.

WE CLAIM:
1. A mobile device holder mounted within a vehicle, the mobile device holder comprising:
a crash detector; and
a processor;
wherein the crash detector is configured to:
detect a crash condition for the vehicle; and
wherein the processor configured to:
generate a signal based on the detected crash condition; and
transmit the signal to a locking unit for disengaging the mobile device holder from a mounting surface in the vehicle.
2. The mobile device holder of claim 1, wherein the processor is further configured to:
generate a notification for the detected crash condition, wherein the notification comprises at least a location of crash and a time of crash; and
transmit the notification to one or more predefined user devices.
3. The mobile device holder of claim 1, wherein the processor is further configured to:
obtain, from the locking unit, information associated with a remount operation of the mobile device holder;
compare the information associated with the remount operation to a predefined parameter; and
transmit a notification, at least to a central server, when the information associated with the remount operation does not correspond to the predefined parameter.
4. The mobile device holder of claim 1, wherein the processor is further configured to:
transmit the signal to the locking unit for disengaging the mobile device holder from the mounting surface, wherein disengaging of the mobile device holder comprises creating an orifice in a gas filled pouch, wherein the gas filled pouch securely fastens the mobile device holder to the mounting surface by means of a vacuum.
10
5. A method for disengaging a mobile device holder from a mounting surface in a vehicle, the method comprising:
obtaining, by a processor, from a crash detector, information associated with a crash condition of a vehicle;
generating, by the processor, a signal based on the information; and
transmitting, by the processor, the signal to a locking unit for disengaging the mobile device holder from the mounting surface in the vehicle.
6. The method of claim 5, further comprising:
generating, by the processor, a notification for the detected crash condition, wherein the notification comprises at least a location of crash and a time of crash; and
transmitting, by the processor, the notification to one or more predefined user devices.
7. The method of claim 5, further comprising:
obtaining, by the processor, from the locking unit, information associated with a remount operation of the mobile device holder;
analyzing, by the processor, the information associated with the remount operation against a predefined parameter; and
transmitting, by the processor, a notification at least to a central server, when the information associated with the remount operation does not correspond to the predefined parameter.
8. The method of claim 5, further comprising:
transmitting, by the processor, the signal to the locking unit, for disengaging the mobile device holder from the mounting surface, wherein disengaging of the mobile device holder comprises creating an orifice in a gas filled pouch, wherein the gas filled pouch securely fastens the mobile device holder to the mounting surface by means of a vacuum.