Title of Invention | METHOD FOR CONTROLLING A REMOTE MOBILE DEVICE FROM A CLIENT MOBILE DEVICE |
---|---|
Abstract | This invention explains a method to control a remote mobile from another client mobile using message-triggers comprising the steps of: generating a message-trigger for the remote mobile from the client mobile; setting a different Teleservice ID by the client mobile, in order for the said message-trigger to be differentiated from a normal SMS at the remote mobile side; differentiating between a normal incoming SMS and an incoming Message-trigger by checking the Teleservice ID field of the incoming SMS at the remote mobile; decoding the encoded password and authorizing the sender of the trigger once the remote mobile has received a message-trigger; and processing the command accordingly after authorizing the sender of the trigger. |
Full Text | FIELD OF THE INVENTION This invention relates, in general, to mobile communication and Mobile Handset Functionality. Further, this invention relates to remote controlling of mobile communication devices from other mobile communication devices. More particularly, this invention relates to a method to control a remote mobile from another client mobile using message-triggers. DESCRIPTION OF RELATED ART Currently available handsets, do not allow the user to operate the mobile device remotely to any extent. For example, consider a scenario where the user has left his mobile device at his residence. Currently, there would be no way by which the user can set the call forward feature in his mobile device to some other number. Consider a situation in which the user is away from his mobile device and wants to set a call forward feature or to grant any profile based access permission to a third user. Presently, the user cannot remotely operate his mobile device if he does not have physical access to his mobile device. The problems involved in the given scenario are mentioned below: a) The user has no way to operate his mobile device from some other mobile device. b) While there are many features which can be equally effective or even more useful in the circumstances when the user does not has physical access to his mobile device, there are no means today to exploit those features. SUMMARY OF THE INVENTION The invention involves using Mobile-to-Mobile messaging in a different manner and for a different purpose i.e. to trigger certain operations upon reception by the targeted mobile device! The idea is to make remote operation of mobile device possible. This invention provides the mobile device with some effective ways with which an authorized user can operate them remotely up to a limited extent. Examples are given below • A data session can be started with the mobile to exchange any information; • A two-party game can be played; • Location information or any other information what the remote mobile can sense, like temperature, humidity, etc. can be obtained; • Non interactive web browsing can be done; • Wallpaper download from the Service-provider server can be done; • Command to lock the mobile device can be sent; • Command to set the call forward feature can be sent; • Command to grant the access permission to different users in case when Profile based access mechanism is implemented on the remote mobile device can be sent, etc. The proposed invention encompassed a few effective ways for the user to operate his mobile remotely to a particular extent. The invention uses special SMS/EMS/MMS to trigger certain events on the remote mobile device. Accordingly, this invention explains a method to control a remote mobile from another client mobile using message-triggers comprising the steps of: (a) generating a message-trigger for the remote mobile from the client mobile; (b) setting a different Teleservice Id by the client mobile, in order for the said message-trigger to be differentiated from a normal SMS at the remote mobile side; (c) differentiating between a normal incoming SMS and an incoming Message-trigger by checking the Teleservice Id field of the incoming SMS at the remote mobile; (d) decoding the encoded password and authorizing the sender of the trigger once the remote mobile has received a message-trigger; and (e) processing the command accordingly after authorizing the sender of the trigger. The message-trigger contains a predefined string which acts as a command on the remote mobile to perform specific operations. The message-trigger carries the authorization password in secure manner along with the said commands. The said message trigger would typically contain the remote mobile device's phone number. The message-trigger contains a coded password which authorizes the user to let him trigger the features remotely. A message is sent as an acknowledgement of the successful operation back to the user based on the choice of implementation. The user of the remote mobile in his phonebook initially stores the list of trusted numbers from which he can receive Message-triggers without any other authorization. The user of the remote mobile sets a password in the mobile device which gets always compared with the password in the message-trigger once the mobile device receives a trigger. The said method is adapted to operate in a manner such that a choice is given to the user to decide a time duration for which only the first Message-trigger needs to be authorized and others following it from the same client mobile within the predefined time interval need not to carry the encoded password along with them. An incoming message found to be a normal SMS after getting scrutinized for it being a potential message-trigger, is forwarded to the SMS layer else if it is a message-trigger then it is parsed for its contents. The Teleservice ID tells the SMS layer of the remote mobile device that whether the incoming message is a normal SMS or a Message Trigger. The client mobile device provides a user interface for the user to generate a Message-trigger and the said user-interface gives the choice to the user to enable or disable the said feature. To create a message-trigger, user has to enter remote mobile number, the command, and the password as an input to the client mobile. The password is encoded properly with any standard cryptographic technique and sent along with the message and after sending the Message-trigger, the said password is destroyed from the memory. These and other objects, features and advantages of the present invention will become more readily apparent from the detailed description taken in conjunction with the drawings and the claims. BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS Figure 1 illustrates the algorithm for the remote mobile side. Figure 2 illustrates the Message-Trigger and SMS structure. Figure 3 illustrates the Architecture at Remote Mobile Side. DETAILED DESCRIPTION OF THE INVENTION The preferred embodiments of the present invention will now be explained with reference to the accompanying drawings. It should be understood however that the disclosed embodiments are merely exemplary of the invention, which may be embodied in various forms. The following description and drawings are not to be construed as limiting the invention and numerous specific details are described to provide a thorough understanding of the present invention, as the basis for the claims and as a basis for teaching one skilled in the art how to make and/or use the invention. However in certain instances, well-known or conventional details are not r described in order not to unnecessarily obscure the present invention in detail. The proposed invention provides a simple solution to operate a mobile device remotely from another mobile device. The detailed description of how the invention is carried out is mentioned in the sections below: The present invention introduces the usage of Mobile-to-Mobile message-triggers which will operate the mobile device remotely in a safe manner. The client mobile device has a module running on it which will enable the user to generate a message-trigger for the remote mobile device. The message-trigger will also carry the authorization password in secured way along with the commands. A Message-trigger will contain a "predefined string" which will act as a command on the remote mobile to perform certain operation. The typical structure of the message would be like " Figure Two explains the protocol and this structure in a pictorial form. After being processed successfully at the remote mobile side, this command will set the Call Forward feature to the The Message-trigger may itself contain a coded password which will authorize the user to let him trigger the features remotely E.g. send SMS with text body as "SET_CALL_FORWARD The client module will set a different Teleservice Id, in order or this SMS-trigger to be differentiated from a normal SMS at the remote mobile side. Remote Side The remote mobile device has a module running on it which will differentiate between a normal incoming SMS and an incoming Message-trigger by checking the Teleservice ID field of the incoming SMS. Once it has received a Message-trigger, it will decode the encoded password and will authorize the sender of the trigger. After authorization of the sender, it will process the command accordingly. A message as an acknowledgement of the successful operation could be sent back to the user depending upon the choice of implementation. There could be any or both of the options available depending upon the choice of implementation to ensure the security of the information • The user in his phonebook can make a separate category in which he can store the list of trusted numbers from which he can receive Message-triggers without any other authorization • The user can set a password in his mobile device which will be always compared with the password in the Message-trigger once the mobile device receives one. • A choice could be given to the user to decide a time duration for which only the first Message-trigger needs to be authorized and others following it from the same client mobile within the predefined time interval need not to carry the encoded password along with them Operation of the Invention The algorithim suggested in Figure 1 explains the working of the module at the remote mobile side. Any incoming message is first differentiated for it being a potential Message-trigger, if it is normal SMS then it is being forwarded to the SMS layer else if it is a Message-Trigger then it is given to be parsed for its contents. Which typically contains Command to be processed, Remote Mobile Phone no. and the Authorization Password, as shown in Figure 2. Once authorized successfully the remote mobile executes the command accordingly and after execution it informs to the sender mobile about the result of the execution being successful or not, depending upon the choice of implementation. Figure 2 shows the standard SMS Transport layer and Teleservice Layer structure, and Message- Trigger structure as an Application layer on the top of it. Refer standard IS 637 (Short Message Service for Spread Spectrum Systems) for the explanation of standard layers of SMS. Application layer information for Message-Trigger is packed into the CHARi field of the User-Data of an incoming SMS which can be retrieved once an incoming SMS can be identified as a Message-Trigger, based on its Teleservice-ID. The architecture shown in figure 3 explains how the incoming trigger will get processed from the physical layer to the application layer on the remote mobile side. First, whenever a mobile device receives an SMS data burst from the lower layer, it'll check its Teleservice ID. The Teleservice ID will tell the SMS layer that whether it's a normal SMS or a Message Trigger. If it is a normal SMS, then it'll pass it to the SMS application to be informed to the user that a new SMS has arrived and else if it is a Message Trigger then it'll be passed to Message Trigger application layer inorder to be parsed to retrieve the required data as shown in Figure 2 and then to be authenticated and for further command execution. Figure 1 (Processing of Message-Triggers at remote mobile side) presents a flowchart of various steps involved when an incoming SMS alert arrives. The specialized modules is running on both, client and remote mobile in order to support this feature. The module on client side will provide a user interface for the user to generate a Message-trigger. The user-interface will give the choice to the user to enable or disable this feature. To create a message-trigger, user has to enter remote mobile device no., the command, and the password as an input to the client mobile device. The password will be encoded properly with any standard cryptographic technique in order to maintain security and sent along with the message. After sending of the Message-trigger, the password will be destroyed from the memory. On the remote mobile side an incoming SMS alert is checked first for its being a Message-trigger by seeing its Teleservice ID, if it is a Message-trigger then the message has been parsed for the commands and the encoded password. The password is decoded and compared to authorize the sender. If the sender is authorized, the command would be executed accordingly; else, the client mobile will be informed regarding the failure of authorization through a SMS. If the command gets executed successfully, the client mobile will be informed regarding the successful execution, else it'll be informed regarding the failure of the command execution. The figure one depicts the process of the invention's functionality at the remote mobile side. The figure two explains the structure of the Message Trigger to be carried by the SMS having a different Teleservice ID from Client mobile to Remote mobile. The figure three explains the architecture of the module at the Remote mobile side. The handset uses smart approach in those conditions where a user is away from his mobile because of any reason, and wants to use it somehow. The advantages of this scheme include: • Registers the idea of operating a mobile remotely with the help of messages. • Extra level of intelligence in the Mobile, to tackle certain critical situations like forgetting the mobile device at some place or loss of mobile. • There have been no changes on the Service Provider side as it is an ordinary SMS delivery for the service provider. The foregoing description of illustrated embodiments of the present invention, including what is described in the Abstract, is not intended to be exhaustive or to limit the invention to the precise forms disclosed herein. While specific embodiments of, and examples for, the invention are described herein for illustrative purposes only, various equivalent modifications are possible within the spirit and scope of the present invention, as those skilled in the relevant art will recognize and appreciate. As indicated, these modifications may be made to the present invention in light of the foregoing description of illustrated embodiments of the present invention and are to be included within the spirit and scope of the present invention. Thus, while the present invention has been described herein with reference to particular embodiments thereof, a latitude of modification, various changes and substitutions are intended in the foregoing disclosures, and it will be appreciated that in some instances some features of embodiments of the invention will be employed without a corresponding use of other features without departing from the scope and spirit of the invention as set forth. Therefore, many modifications may be made to adapt a particular situation or material to the essential scope and spirit of the present invention. It is intended that the invention not be limited to the particular terms used in following claims and/or to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include any and all embodiments and equivalents falling within the scope of the appended claims. GLOSSARY OF TERMS AND DEFINITIONS THEREOF • Message-Trigger: A normal SMS/EMS/MMS having a different Class e.g. Class 0 in case of SMS, or a different Teleservice Id, depending upon the choice of implementation, which will carry the command to be executed on the remote mobile along with the authorization password. WE CLAIM 1. A method to control a remote mobile from another client mobile using message-triggers comprising the steps of: (a) generating a message-trigger for the remote mobile from the client mobile; (b) setting a different Teleservice Id by the client mobile, in order for the said message-trigger to be differentiated from a normal SMS at the remote mobile side; (c) differentiating between a normal incoming SMS and an incoming Message-trigger by checking the Teleservice Id field of the incoming SMS at the remote mobile; (d) decoding the encoded password and authorizing the sender of the trigger once the remote mobile has received a message-trigger; and (e) processing the command accordingly after authorizing the sender of the trigger. 2. A method as claimed in claim 1 wherein the message-trigger contains a predefined string which acts as a command on the remote mobile to perform specific operations. 3. A method as claimed in claim 1 wherein the message-trigger carries the authorization password in a secure manner along with the said commands. 4. A method as claimed in claim 1 wherein the said message trigger typically contains the remote mobile phone number. 5. A method .as claimed in claim 1 wherein the message-trigger contains a coded password which authorizes the user to let him trigger the features remotely. * 6. A method as claimed in claim 1 wherein a message is sent as an acknowledgement of the successful operation back to the user depending upon the choice of implementation. 7. A method as claimed in claim 1 wherein the user of the remote mobile in his phonebook initially stores the list of trusted numbers from which he can receive Message-triggers without any other authorization. 8. A method as claimed in claim 1 wherein the user of the remote mobile sets a password in the mobile which gets always compared with the password in the message-trigger once the mobile device receives a trigger. 9. A method as claimed in claim 1 wherein the said method is adapted to operate in a way such that a choice is given to the user to decide a time duration for which only the first Message-trigger needs to be authorized and others following it from the same client mobile within the predefined time interval need not to carry the encoded password along with them. 10. A method as claimed in claim 1 wherein an incoming message found to be a normal SMS after getting scrutinized for it being a potential message-trigger, is forwarded to the SMS layer; else, if it is a message-trigger then it is parsed for its contents. 11. A method as claimed in claim 1 wherein the Teleservice ID tells the SMS layer of the remote mobile that whether the incoming message is a normal SMS or a Message Trigger. 12. A method as claimed in claim 1 wherein the client mobile provides a user interface for the user to generate a Message-trigger and the said user-interface gives the choice to the user to enable or disable the said feature. 13. A method as claimed in claim 1 wherein to create a message-trigger, user has to enter remote mobile number, the command, and the password as an input to the client mobile. 14. A method as claimed in claim 1 wherein the password is encoded properly with any standard cryptographic technique and sent along with the message and after sending the Message-trigger, the said password is destroyed from the memory. 15. A method to control a remote mobile from another client mobile using message-triggers substantially described particularly with reference to the accompanying drawings. |
---|
Patent Number | 278000 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Indian Patent Application Number | 1428/CHE/2005 | ||||||||
PG Journal Number | 51/2016 | ||||||||
Publication Date | 09-Dec-2016 | ||||||||
Grant Date | 08-Dec-2016 | ||||||||
Date of Filing | 06-Oct-2005 | ||||||||
Name of Patentee | Samsung R&D Institute India-Bangalore Pvt Ltd., | ||||||||
Applicant Address | # 2870, ORION Building, Bagmane Constellation Business Park, Outer Ring Road, Doddanakundi Circle, Marathahalli Post, Bangalore -560037, Karnataka, India, | ||||||||
Inventors:
|
|||||||||
PCT International Classification Number | H04M 3/42 | ||||||||
PCT International Application Number | N/A | ||||||||
PCT International Filing date | |||||||||
PCT Conventions:
|