Abstract: The present subject matter relates to methods and systems for changing orientation of a mobile device holder holding a mobile device. Context of one or more applications running on the mobile device is monitored. Based on the determined context, an application from the applications being monitored is displayed onto a display of the mobile device. Further, based on the application being displayed, a signal from the mobile device is transmitted to the mobile device holder for changing an orientation of the mobile device holder.
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 changing orientation 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. However, in other applications, the mount may also hold the mobile device in a position such that the driver or a passenger in the vehicle may watch videos, listen to songs, activate/deactivate a call, and the like in a hands-free fashion. However, sometimes such applications may cause distraction to the driver while the vehicle is in motion. For example, the driver may lose his/her concentration while driving in case a video is being played on the mobile device. Such a distraction in turn may lead to accidents resulting in loss of life and property.
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 one implementation, a mobile device is disclosed, in accordance with embodiments of the present disclosure. The system may include an input/output modality, a memory and a processor coupled to the memory. The processor may execute instructions stored in the memory for monitoring one or more applications running on the input/output modality and in a background. The processor may further execute instructions for determining a context of the one or more applications and displaying, on the input/output modality, an application from the one or more applications being monitored based on the context or a user input. The processor may further execute instructions for generating a signal based upon the application being displayed on the input/output modality. The processor may further execute instructions for transmitting the signal to a mobile device holder for changing an orientation of the mobile device holder.
[0007] In another implementation, a mobile device holder is disclosed, in accordance with embodiments of the present disclosure. The mobile device holder may include a receptacle, a processor and a motor. The receptacle may be configured to hold a phone. The processor may be configured to receive a signal from the phone. The signal may be received upon occurrence of an event, wherein the event is determined based upon an application being displayed on the phone. Further, the motor may be configured to change an orientation of the receptacle based upon the signal received by the processor.
[0008] In yet another implementation, a method for changing an orientation of a mobile device holder is disclosed, in accordance with an embodiment of the present disclosure. The method may include monitoring, by a processor, one or more applications running on an input/output modality and in a background. The method may further include determining, by the processor, a context of the one or more applications. The method may further include displaying, by the processor, on the input/output modality, an application from the one or more applications being monitored based on the context or a user input. The method may further include generating, by the processor, a signal based upon the application being displayed on the input/output modality. The method may further comprise transmitting, by the processor, the signal to the mobile device holder for changing an orientation of the mobile device holder.
[0009] In yet another implementation, a method for changing an orientation of a mobile device held in a receptacle is disclosed, in accordance with an embodiment of the present disclosure. The method may include holding, by a receptacle, a phone. The method may further include receiving, by a processor, a signal from the phone, wherein the signal is received upon occurrence of an event. The event may be determined based upon an application being displayed on the phone. The method may further include changing, by a motor, an orientation of the receptacle based upon the signal received by the processor.
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] 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.
[0011] Figure 1(a) illustrates network implementation of a mobile device holder and a system for changing an orientation of the mobile device holder, in accordance with an embodiment of the present disclosure.
[0012] Figure 1(b) illustrates an exemplary mobile device holder, in accordance with an embodiment of the present disclosure.
[0013] Figure 2 illustrates a method for changing an orientation of a mobile device holder, in accordance with an embodiment of the present disclosure.
[0014] Figure 3 illustrates a method for changing an orientation of a mobile device held in a receptacle in accordance with an embodiment of the present disclosure.
DETAILED DESCRIPTION
[0015] The present disclosure relates to a method and system for changing an orientation of a mobile device holder holding a mobile device. 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.
[0016] 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.
[0017] Referring now to Figure 1(a), a network implementation 100 of a mobile device 102 and a mobile device holder 104, in accordance with an embodiment of the present disclosure. The mobile device 102, in an implementation, may have a bi-directional communication with the mobile device holder 104, via the network 106. As depicted, the mobile device 102 may include at least one processor 108, an input/output (I/O) modality 110, and a memory 112. The at least one processor 108 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 108 is configured to fetch and execute computer-readable instructions or modules stored in the memory 112.
[0018] The I/O modality 110 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O modality 110 may enable the mobile device 102 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O modality 110 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O modality 110 may include one or more ports for connecting a number of devices to one another or to another server.
[0019] The memory 112 may include any computer-readable medium or computer program product known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or nonvolatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, a compact disks (CDs), digital versatile disc or digital video disc (DVDs) and magnetic tapes. The memory 112 may include modules 114 and data 116.
[0020] The modules 114 include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. In one implementation, the modules 114 may include a context module 118, a display module 120, a signaling module 122 and other modules 124. The other modules 124 may include programs or coded instructions that supplement applications and functions of the mobile device 102.
[0021] The data 116, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 114. The data 116 may also include application data 126 and other data 128. Each of the aforementioned modules is explained in detail in subsequent paragraphs of the specification.
[0022] In one implementation, the network 106 may be a wireless network, a wired network or a combination thereof. The network 106 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 110 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 106 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like. In another implementation, the network 106 may also be a module facilitating a Bluetooth®, an NFC or an IR communication.
[0023] In an embodiment, the mobile device 102 may be a mobile device such as a smart phone, a tablet device, PDA device, a GPS device, and the like. In the embodiment, the mobile device holder 104 may hold the mobile device 102 in a receptacle 130. The mobile device holder 104 may further include at least one processor 132 for communicating with the mobile device 102. The mobile device holder 104 may further include at least one motor 134 and a battery panel 136. The motor 134 may be configured to rotate the receptacle 130 in a desired direction. Further, the battery panel 136 may be used to charge different components of the mobile device holder 104.
[0024] In operation, one or more applications may be running within the mobile device 102. In an implementation, the applications may be executed in an active mode or a background mode. Applications running in the active mode, in one example, may be executed on the I/O modality 110. Further, applications running in the background mode may be executed by the processor 108 such that these applications may be passively executed without being displayed on the I/O modality 110.
[0025] In an embodiment, the context module 118 may monitor the applications executed both in the active mode as well as in the background mode. Further, the context module 118 may determine context of the applications. In an example, context of the applications may be media, location, gaming, social networking, email and the like. Based on the determined context of the applications, the display module 120 may display one of the applications being monitored, on the I/O modality 110. In one implementation, the application may be displayed on the I/O modality 110 by replacing an application already displayed on the I/O modality 110.
[0026] Further, based on the application displayed on the I/O modality 110, the signaling module 122 may transmit a signal to the mobile device holder 104. In an embodiment, the signaling module 122 may transmit the signal in order to change an orientation of the receptacle 130 of the mobile device holder 104. The signal transmitted by the signal module 122 may be received by the processor 132 of the mobile device holder 104. In one example, the processor 132 may be a microcontroller. The processor 132, based on the signal received by the mobile device 102, may detect a direction in which the receptacle 130 is to be moved. In order to change the orientation of the receptacle 130, the processor 132 may then send the signal to the motor 134. The motor 134, in an example, may be a stepper motor. The motor 134, at receiving the signal from the processor 132, may change the direction of the receptacle as directed by the signal.
[0027] Taking an example, the mobile device 102 may be held in the receptacle 130 of the mobile device holder 104 that may be mounted on a dashboard of the vehicle. The context module 118 of the mobile device may determine context of applications running actively on and in a background of the mobile device. Assuming that there are three applications running simultaneously on the mobile device, these applications may be monitored and context for each of the three applications may be determined. In an instance, for example, one of the three applications may be determined as a location application while the other two applications may be determined as a media application and a gaming application respectively. Based on the context, the display module 120 may display one of the three applications on the I/O modality 110 of the mobile device 102. For example, the media application may be currently displayed on the I/O modality 110. Further, the mobile device 102 may be currently facing towards a passenger of the vehicle. Furthermore, it may be determined that a sharp turn would be encountered by the vehicle 100 meters ahead from a current location. That is, it may be imperative to display the location application so that the driver may be aware of the sharp turn. This may be detected by the context module 118 such that the context module 118 enables the display module 120 to display the location application on the I/O modality 110. As the location application is displayed on the I/O modality 110, the signaling module 122 may send the signal to the mobile device holder 104, for changing the orientation of the mobile holder 104. Based on the received signal, the processor 132 of the mobile device holder 104 may enable the motor 134 to automatically rotate the receptacle 130 holding the mobile device 102, away from the passenger to the driver’s side. Thus, movement of the mobile device 102 based on the context of the applications may ensure safe driving of the vehicle.
[0028] In another embodiment, the signaling module 122 may also send the signal to the mobile device holder 104 based on changes in context of an application being currently displayed onto the I/O modality 110. In the embodiment, the context module 118 may monitor the application being displayed. Based on detected changes in the context of the application, the context module 118 may enable the signaling module 122 to transmit a signal to the mobile device holder 104 to change the orientation of the mobile device holder 104. Taking an example, a restaurant search application may be displayed onto the I/O modality 110 of the mobile device 102. Further, the mobile device 102 may be facing away from the driver towards the passenger side. The passenger may browse the application to find a restaurant of choice and click on a “Show Directions” option within the application to get directions to the restaurant. As the passenger clicks on the option, a map may be displayed within the application and this may be detected by the context module 118. Based on the detection, the signaling module 122 to send a signal to the mobile device holder 104 for rotating the receptacle 130, containing the mobile device 102, towards the driver side. Thus, this may aid the driver to get correct directions to the selected restaurant. In an implementation, the priority ranks for the applications may be stored in the application data 126.
[0029] In yet another embodiment, the orientation of the mobile device holder 104 may be changed based on a priority rank of an application. In the embodiment, priority ranks for one or more applications may be set by a passenger/driver based on the context of the applications. For example, in an instance where the vehicle is not in motion, a gaming application may have a highest priority rank. In such instance, whenever the driver halts the vehicle, the gaming application may be displayed on the I/O modality 110 and the mobile device holder 104, containing the mobile device 102, may rotate towards the passenger. Further, as soon as the vehicle is in motion, the gaming application may be switched to the background mode and a location application may be displayed on the I/O modality 110. Based on the change in application, the mobile device holder 104 may be moved towards the driver of the vehicle.
[0030] Referring back to the fig., in an embodiment, the signaling module 122 may also transmit the signal to the mobile device holder 104 based on a user input. In an example, the user input may be a voice input or a tactile input. For example, if a location application is currently displayed on the I/O modality 110 and a media application is running in the background mode, the mobile device 102 may be facing towards the driver side. If a passenger wishes to signal the mobile device holder 104 to move the mobile device 102 in his/her direction, the passenger may give a voice input through a microphone unit (not shown) of the mobile device 102 or a tactile input on the I/O modality 110. Based on the received input, the signaling module 122 may transmit the signal to the mobile device holder 104. The signal may be received by the processor 132 that may then enable the motor 134 to rotate the receptacle 130, holding the mobile device 102, towards the passenger.
[0031] Figure 1(b) illustrates various components of the mobile device holder 104, in accordance with an embodiment of the present disclosure. As described in the foregoing, the mobile device holder 104 may include the receptacle 130 for holding the mobile device 102. The mobile device holder 104 may further include the processor 132 and the battery panel 136. In an embodiment, the battery panel 136 may include one or more solar cells 138 for charging the battery panel 136. The battery panel 136 may thus be charged without the requirement of an external charging source, such as a car charger. The mobile device holder 104 may further include a connector element 140. The connector element 140 may be responsible for communication between the processor 132 of the mobile device holder 104 and the processor 108 of the mobile device 102. In an example, the connector element 102 may be a Bluetooth® module. In another example, the connector element 102 may be a Wi-Fi router, a NFC device or an IR chip. The mobile device holder 104 may further include a rotary member 142. The rotary member 142 may include the motor 134. The rotary member may be configured to move the mobile device holder 104, and thus the mobile device 102, based on signals received from the processor 132.
[0032] In an implementation, various settings for the mobile device holder 104 may be configured by a user through a dedicated interface on any mobile device, such as the mobile device 102, to be used with the mobile device holder 104. In the implementation, a web server (not shown) may be embedded within the mobile device holder 104 such that user settings from the interface may be received by the web server. The user, in an example, may customize, type of applications to be used, priority ranks of the applications, applications to be excluded, and the like using the interface.
[0033] Figure 2 illustrates a method 200 for changing an orientation of a mobile device holder, in accordance with an embodiment of the present disclosure. The method 200 starts at 202 wherein one or more applications running on an I/O modality and a background may be monitored. In an implementation, the one or more applications may be running on the I/O modality and background of a mobile device.
[0034] At step 204, a context of the one or more applications may be determined. In an example, the context of the application may be based on a type of the application. For example, the context of the application may be gaming, email, location, etc.
[0035] At step 206, an application from the one or more applications being monitored may be displayed on the I/O modality. The application may be displayed based on the context or a user input. In one example, the user input may be a voice input or a tactile input.
[0036] At step 208, a signal may be generated based on the application being displayed on the I/O modality. The signal, in an implementation, may be generated by the mobile device.
[0037] At step 210, the signal may be transmitted to a mobile device holder for changing the orientation of the mobile device holder. In an example, the signal may be received by a processor of the mobile device holder. The processor may send the signal to a motor such that the motor may rotate a receptacle of the mobile device holder holding the mobile device.
[0038] Figure 3 illustrates a method 300 for …, in accordance with an embodiment of the present disclosure. The method 300 starts at step 302, wherein a receptacle may hold a mobile device.
[0039] At step 304, a signal from the mobile device may be received by a processor. The signal may be received based upon occurrence of an event. Further, the event may be determined based upon an application being displayed on the mobile device. In an example, the event may be displaying of an application on a display of the mobile device. In another example, the event may be a user input.
[0040] At step 306, the orientation of the receptacle may be changed based on the signal received by the processor.
[0041] 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.
Claims:WE CLAIM:
1. A mobile device comprising:
an input/output modality;
a memory; and
a processor coupled to the memory, wherein the processor executes instructions stored in the memory for:
monitoring one or more applications running on the input/output modality and in a background;
determining a context of the one or more applications;
displaying, on the input/output modality, an application from the one or more applications being monitored, based upon one of the context or a user input;
generating a signal based upon the application being displayed on the input/output modality; and
transmitting the signal to a mobile device holder for changing an orientation of the mobile device holder.
2. The mobile device of claim 1, wherein the one or more applications comprise a media application, a gaming application, a social networking application, an email application, and a location application.
3. The mobile device of claim 1, wherein the user input is one of a voice input and a tactile input.
4. The mobile device of claim 1, wherein the processor executes instructions stored in the memory for:
identifying a priority rank of the application, wherein priority ranks of the one or more applications are based on the context of the one or more applications; and
displaying the application on the input/output modality based at least in part upon the priority rank of the application,.
5. A mobile device holder comprising:
a receptacle for holding a mobile device;
a processor for receiving a signal from the mobile device, wherein the signal is received upon occurrence of an event, wherein the event is determined based upon an application being displayed on the mobile device; and
a motor for changing an orientation of the receptacle based upon the signal received by the processor.
6. The mobile device holder of claim 5, wherein the one or more applications comprise a media application, a gaming application, a social networking application, an email application, and a location application.
7. The mobile device holder of claim 5, further comprising a battery and a set of solar cells for charging the battery, wherein the battery is connected to the receptacle, the processor and the motor.
8. A method for changing an orientation of a mobile device holder, the method comprising:
monitoring, by a processor, one or more applications running on an input/output modality and in a background of a mobile device;
determining, by the processor, a context of the one or more applications;
displaying, by the processor, on the input/output modality, an application from the one or more applications being monitored based upon one of the context or a user input;
generating, by the processor, a signal based upon the application being displayed on the input/output modality; and
transmitting, by the processor, the signal to the mobile device holder for changing an orientation of the mobile device holder.
9. The method of claim 8, further comprising:
identifying, by the processor, a priority rank of the application, wherein priority ranks of the one or more applications are based on the context of the one or more applications; and
displaying, by the processor, the application on the input/output modality based at least in part upon the priority rank of the application.
10. The method of claim 8, wherein the one or more applications comprise a media application, a gaming application, a social networking application, an email application, and a location application.
11. A method changing an orientation of a mobile device held by a receptacle, the method comprising:
receiving, by a processor, a signal from the mobile device, wherein the signal is received upon occurrence of an event, wherein the event is determined based upon an application being displayed on the mobile device; and
changing, by a motor, an orientation of the receptacle based upon the signal received by the processor.
12. The method of claim 11, wherein the one or more applications comprise a media application, a gaming application, a social networking application, an email application, and a location application. , Description:FORM 2
| Section | Controller | Decision Date |
|---|---|---|
| # | Name | Date |
|---|---|---|
| 1 | 201611007375-IntimationOfGrant25-10-2023.pdf | 2023-10-25 |
| 1 | Form 9 [02-03-2016(online)].pdf | 2016-03-02 |
| 2 | 201611007375-PatentCertificate25-10-2023.pdf | 2023-10-25 |
| 2 | Form 3 [02-03-2016(online)].pdf | 2016-03-02 |
| 3 | 201611007375-Annexure [23-05-2023(online)].pdf | 2023-05-23 |
| 4 | Form 18 [02-03-2016(online)].pdf | 2016-03-02 |
| 4 | 201611007375-Written submissions and relevant documents [23-05-2023(online)].pdf | 2023-05-23 |
| 5 | Drawing [02-03-2016(online)].pdf | 2016-03-02 |
| 5 | 201611007375-Correspondence to notify the Controller [18-04-2023(online)].pdf | 2023-04-18 |
| 6 | Description(Complete) [02-03-2016(online)].pdf | 2016-03-02 |
| 6 | 201611007375-US(14)-HearingNotice-(HearingDate-15-05-2023).pdf | 2023-04-17 |
| 7 | Form 26 [06-07-2016(online)].pdf | 2016-07-06 |
| 7 | 201611007375-Proof of Right [22-10-2021(online)].pdf | 2021-10-22 |
| 8 | 201611007375-GPA-(11-07-2016).pdf | 2016-07-11 |
| 8 | 201611007375-FORM 13 [09-07-2021(online)].pdf | 2021-07-09 |
| 9 | 201611007375-Form-1-(11-07-2016).pdf | 2016-07-11 |
| 9 | 201611007375-POA [09-07-2021(online)].pdf | 2021-07-09 |
| 10 | 201611007375-CLAIMS [30-06-2020(online)].pdf | 2020-06-30 |
| 10 | 201611007375-Correspondence Others-(11-07-2016).pdf | 2016-07-11 |
| 11 | 201611007375-COMPLETE SPECIFICATION [30-06-2020(online)].pdf | 2020-06-30 |
| 11 | abstract.jpg | 2016-07-14 |
| 12 | 201611007375-FER.pdf | 2019-12-30 |
| 12 | 201611007375-FER_SER_REPLY [30-06-2020(online)].pdf | 2020-06-30 |
| 13 | 201611007375-OTHERS [30-06-2020(online)].pdf | 2020-06-30 |
| 14 | 201611007375-FER.pdf | 2019-12-30 |
| 14 | 201611007375-FER_SER_REPLY [30-06-2020(online)].pdf | 2020-06-30 |
| 15 | 201611007375-COMPLETE SPECIFICATION [30-06-2020(online)].pdf | 2020-06-30 |
| 15 | abstract.jpg | 2016-07-14 |
| 16 | 201611007375-CLAIMS [30-06-2020(online)].pdf | 2020-06-30 |
| 16 | 201611007375-Correspondence Others-(11-07-2016).pdf | 2016-07-11 |
| 17 | 201611007375-POA [09-07-2021(online)].pdf | 2021-07-09 |
| 17 | 201611007375-Form-1-(11-07-2016).pdf | 2016-07-11 |
| 18 | 201611007375-GPA-(11-07-2016).pdf | 2016-07-11 |
| 18 | 201611007375-FORM 13 [09-07-2021(online)].pdf | 2021-07-09 |
| 19 | Form 26 [06-07-2016(online)].pdf | 2016-07-06 |
| 19 | 201611007375-Proof of Right [22-10-2021(online)].pdf | 2021-10-22 |
| 20 | Description(Complete) [02-03-2016(online)].pdf | 2016-03-02 |
| 20 | 201611007375-US(14)-HearingNotice-(HearingDate-15-05-2023).pdf | 2023-04-17 |
| 21 | Drawing [02-03-2016(online)].pdf | 2016-03-02 |
| 21 | 201611007375-Correspondence to notify the Controller [18-04-2023(online)].pdf | 2023-04-18 |
| 22 | Form 18 [02-03-2016(online)].pdf | 2016-03-02 |
| 22 | 201611007375-Written submissions and relevant documents [23-05-2023(online)].pdf | 2023-05-23 |
| 23 | 201611007375-Annexure [23-05-2023(online)].pdf | 2023-05-23 |
| 24 | Form 3 [02-03-2016(online)].pdf | 2016-03-02 |
| 24 | 201611007375-PatentCertificate25-10-2023.pdf | 2023-10-25 |
| 25 | 201611007375-IntimationOfGrant25-10-2023.pdf | 2023-10-25 |
| 25 | Form 9 [02-03-2016(online)].pdf | 2016-03-02 |