The accompanying drawings, which are included to provide a further understanding of the invention and constitute a part of this specification, illustrate embodiments of the invention and together with the description help to explain the principles of the invention. In the drawings:
a is a block diagram illustrating a system according to one embodiment of the invention,
b is a block diagram illustrating a system according to another embodiment of the invention,
a is a diagram illustrating a method according to one embodiment of the invention, and
b is a diagram illustrating a method according to another embodiment of the invention.
Reference will now be made in detail to the embodiments of the invention, examples of which are illustrated in the accompanying drawings.
a illustrates a system according to one embodiment of the invention. The system of the embodiment of the invention illustrated in
The system of the embodiment of the invention illustrated in
Furthermore, the remote controller 110 may be configured to operate the mobile device to send a message to a recipient indicated by the received messaging request via a mobile communication network. Furthermore, the remote controller 110 may be configured to operate the mobile device to store a message received in the received messaging request in the mobile device.
In an embodiment, the remote controller 110 is implemented as software. For example, the remote controller 110 may comprise a mobile web server module (not illustrated) comprising e.g. a mobile Apache (mApache) web server which is able to create wireless Internet connections and to listen out for incoming messaging requests, and which therefore can be reached by a web server 108 via the gateway 104. In addition to the mobile web server module, the remote controller 110 may comprise a command module (not illustrated) able to operate the mobile device 100 as disclosed above. Alternatively, the mobile web server module may be configured to operate the mobile device 100 directly. In another embodiment, the remote controller 110 is implemented as hardware.
For example, if the remote controller 110 comprises the mobile web server module, the mobile web server module may be configured to maintain a first web page which, when called by the web server 108 with the messaging request, causes a program (e.g. a program comprised in the command module) to be run on the mobile device 100 for operating the mobile device 100 to send a message to a recipient indicated by the received messaging request. Correspondingly, the mobile web server module may be configured to maintain a second web page which, when called by the web server 130 causes a program (which may be the same program as above or it may another program) to be run on the mobile device 100 for operating the mobile device 100 to store a message received in the received messaging request in the mobile device 100.
Alternatively, the mobile web server module may be configured to maintain a single web page that can be called with different parameters resulting in different actions taken. For example, when called by the web server 108 with messaging request comprising a first set of parameters (identifying the recipient of a message), the single web page causes a program to be run on the mobile device 100 for initiating a message sending operation to the identified recipient. The recipient may be identified with a telephone number, an email address or an IP address. Correspondingly, when called by the web server 108 with the messaging request comprising a second set of parameters (that instruct to store a message in the mobile device 100), the single web page causes a program to be run on the mobile device 100 for storing the message received in the messaging request in the mobile device 100.
The system of the embodiment of the invention illustrated in
The gateway 104 is further configured to receive from the web server 108 a messaging request addressed to an assigned connection identifier. The gateway 104 is further configured to forward the messaging request to a mobile device indicated by the assigned connection identifier, i.e. the mobile device 100 in the example illustrated in
The gateway 104 and the mobile device 100 are connected to each other over a wireless Internet network 102 which in the example illustrated in
The system of the embodiment of the invention illustrated in
The system of the embodiment of the invention illustrated in
The web server 108 is further configured to check from the gateway 104, whether the second mobile device has an active connection with the gateway, to send to the gateway 104 a messaging request addressed to a connection identifier assigned by the gateway to the second mobile device, when the second mobile device has an active connection with the gateway 104, and to send to the gateway 104 a messaging request addressed to a connection identifier assigned by the gateway 104 to the first mobile device, when the second mobile device does not has an active connection with the gateway 104.
The computing device 112 and the web server 108 are connected to each other over Internet 106 in the example illustrated in
Although not disclosed in
b illustrates a system according to another embodiment of the invention. In the embodiment disclosed in
a illustrates a method according to one embodiment of the invention. First, the remote controller 110 establishes a wireless Internet connection from the mobile device 100a to the gateway 104, step 200. Then, in response, the gateway 104 assigns a connection identifier indicating the mobile device 100a, step 201. At step 202, the remote controller 110 begins to monitor the established wireless Internet connection by listening out for incoming requests. As a result, the messaging service provided by the invention is now activated.
Some time later, the user of the mobile device 100a decides to send a message, e.g. a short message (SMS), a multimedia message (MMS) or an email message, with the computing device 112 to at least one intended recipient. However, the user is engrossed with a task involving the computing device 112 and does not wish to pick up the mobile device 100a and start typing the message with it. Therefore, at steps 203 and 204, the user accesses a web site at the web server 108 with the web browser 114 included in the computing device 112 and starts generating a message. The web site may display contact information specific to the user of the mobile device 100a. In an embodiment, the user is authenticated e.g. via a log-on procedure (involving e.g. a user name and password) before allowed to access the web site. The contact information may be stored e.g. on the data base arranged in connection with the web server 108. Obviously, there may be several pieces of contact information stored in the data base, each being specific to a mobile device of a different user. In such a case, the log-on procedure may be utilized in determining which set of contact information to display to each user on the web site.
The contact information specific to the mobile device 100a of the user may be obtained to the web server 108 and data base e.g. from the mobile device 100a while the user utilizes the messaging remote control service provided by the invention for the first time, that is, while the mobile device 100a of the user and the web server 108 communicate for the first time. In other words, the contact information may be transferred to the web server 108 from the mobile device 100a. As is known, people often maintain a phonebook type of list of repeatedly used telephone numbers or email addresses in their mobile telephones. Later on, the contact information may be updated e.g. by the web server 108 polling the mobile device 110a via the gateway 104.
The web site may display a set of contact information for example as rows where each row comprises a name of a contact and a telephone number/email address associated with that contact. Furthermore, each row may comprise e.g. a control button, the pressing of which selects the corresponding contact and telephone number/email address for messaging procedure of the invention.
At step 205 the web server 108 checks whether the intended recipient (a second mobile device 100b) has an active connection with the gateway 104. In the example of
In one embodiment of
b illustrates a method according to another embodiment of the invention. First, the remote controller 110 establishes a wireless Internet connection from the mobile devices 100a and 100b to the gateway 104, step 300. Then, in response, the gateway 104 assigns a unique connection identifier indicating each mobile device 100a and 100b, step 301. At step 302, the remote controller 110 begins to monitor the established wireless Internet connection by listening out for incoming requests. As a result, the messaging service provided by the invention is now activated. It is apparent that the establishment of the wireless Internet connection from the mobile devices 100a and 100b to the gateway 104 does not in practice happen simultaneously.
Some time later, the user of the mobile device 100a decides to send a message, e.g. a short message (SMS), a multimedia message (MMS) or an email message, with the computing device 112 to at least one intended recipient. However, the user is engrossed with a task involving the computing device 112 and does not wish to pick up the mobile device 100a and start typing the message with it. Therefore, at steps 303 and 304, the user accesses a web site at the web server 108 with the web browser 114 included in the computing device 112 and starts generating a message. The web site may display contact information specific to the user of the mobile device 100a. In an embodiment, the user is authenticated e.g. via a log-on procedure (involving e.g. a user name and password) before allowed to access the web site. The contact information may be stored e.g. on the data base arranged in connection with the web server 108. Obviously, there may be several pieces of contact information stored in the data base, each being specific to a mobile device of a different user. In such a case, the log-on procedure may be utilized in determining which set of contact information to display to each user on the web site.
The contact information specific to the mobile device 100a may be obtained to the web server 108 and data base e.g. from the mobile device 100a while the user utilizes the messaging remote control service provided by the invention for the first time, that is, while the mobile device 100a of the user and the web server 108 communicate for the first time. In other words, the contact information may be transferred to the web server 108 from the mobile device 100a. As is known, people often maintain a phonebook type of list of repeatedly used telephone numbers or email addresses in their mobile telephones. Later on, the contact information may be updated e.g. by the web server 108 polling the mobile device 100a via the gateway 104.
The website may display a set of contact information for example as rows where each row comprises a name of a contact and a telephone number/email address associated with that contact. Furthermore, each row may comprise e.g. a control button, the pressing of which selects the corresponding contact and telephone number/email address for messaging procedure of the invention.
At step 305 the web server 108 checks whether the intended recipient (a second mobile device 100b) has an active connection with the gateway 104. In the example of
The messaging request from the web server 108 at step 306 may also instruct the gateway to send a copy of the message also to the mobile device 100a. Therefore, at step 308 the gateway sends a copy of the message to the mobile device 100a. In response to the received messaging request, the remote controller 110 operates the mobile device 100a to place the message in the native messaging application's “Sent” folder.
The invention may be implemented with software in various system elements, e.g. in a mobile device and a network server comprising at least one of the gateway and the web server. The mobile device and the network server may then comprise at least one memory. The memory may refer to a single memory or memory area or to a plurality memories or memory areas that may include e.g. random access memories (RAM), read-only memories (ROM) etc. The memory may also include other applications or software components that are not described in more detail and also may include the computer program (or portion thereof), which when executed on a central processing unit performs at least some of the method characteristics disclosed in the invention. The central processing unit may also include memory or a memory may be associated therewith which may include the computer program (or portion thereof) which when executed on the central processing unit performs at least some of the method characteristics disclosed in the invention.
It is obvious to a person skilled in the art that with the advancement of technology, the basic idea of the invention may be implemented in various ways. The invention and its embodiments are thus not limited to the examples described above, instead they may vary within the scope of the claims.