MESSAGING SERVICE EXPORT

Abstract

Method of exporting a message intended for a user and received by a providing device, from a providing device (6) to a rendering device (8) said method comprising:—receiving by a message pool manager (4) said message from the providing device (6);—storing said message in a message pool (9);—transmitting said message from the message pool manager (4) to the rendering device (8) further to a request from the rendering device (8).

Claims

1. A method of exporting a message intended for a user and received by a providing device, via a communication network, from said providing device to a rendering device, said method comprising: receiving by a message pool manager said message from the providing device; storing said message in a message pool managed by said pool manager; transmitting said message from the message pool manager to the rendering device further to a request from the rendering device.

2. The method of claim 1, wherein the reception of the message by the message pool manager and the transmission of said message to the rendering device are performed in an asynchronous manner

3. The method of claim 1, comprising rendering the message on a user interface of said rendering device.

4. The method of claim 3, wherein the message is rendered at a time determined by said rendering device.

5. The method of claim 3, wherein the message is rendered by the rendering device according to a display format determined by said rendering device.

6. The method of claim 1, wherein the method comprises removing the message from the message pool after its transmission to the rendering device or after its rendering.

7. The method of claim 1, comprising detecting, by the rendering device, that said rendering device is located in the perception range of the user.

8. The method of claim 7, wherein the rendering device is detected as being located in the perception range of the user if the user is using said rendering device.

9. The method of claim 7 or 8, wherein the detection is performed by the rendering device using at least one sensor.

10. The method of claim 1, wherein the providing device is a mobile phone and the rendering device is a set-top box or a connected television.

11. A message pool manager operable to export a message intended for a user and received by a providing device, via a communication network, from said providing device to a rendering device, said message pool manager comprising: a reception module operable to receive said message from the providing device; a storage module operable to store said message in a message pool; a transmission module operable to transmit said message from the message pool manager to the rendering device further to a request from the rendering device.

12. The message pool manager of claim 11, wherein said message pool manager is centralized in one device.

13. The message pool manager of claim 11, wherein said message pool manager is distributed over a plurality of devices.

14. A device operable to receive via a communication network a message intended for a user, wherein said device comprises a transmitter configured to transmit said message, upon its reception, to a message pool manager in order for said message to be stored in a message pool.

15. A computer-readable program comprising computer-executable instructions to enable a computer to perform the method of claim 1.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0057] The present invention is illustrated by way of examples, and not by way of limitation, in the figures of the accompanying drawings, in which like reference numerals refer to similar elements and in which:

[0058] FIG. 1 is a schematic view of a system in which the method of the present invention is advantageously implemented, according to a first embodiment of the invention;

[0059] FIG. 2 is a schematic view of a system in which the method of the present invention is advantageously implemented, according to a second embodiment of the invention;

[0060] FIG. 3 is a schematic view of the structure of a message pool manager according to an embodiment of the invention;

[0061] FIG. 4 shows an example of a message pool;

[0062] FIG. 5 is a schematic view of the structure of a rendering device according to an embodiment of the invention; and

[0063] FIG. 6 is a flowchart showing the steps of the message exporting method according to an embodiment of the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

[0064] Referring to FIG. 1, there is shown therein a schematic view of a centralized system 2 implementing a first embodiment of the present invention.

[0065] According to the first embodiment, the exporting service is managed in a centralized manner by a message pool manager 4 which can be a dedicated device for this service or a permanently connected device in the system 2.

[0066] The system 2 comprises for example a home network comprising a home router or an internet gateway to which are connected a plurality of devices.

[0067] According to the first embodiment of the invention, this home router or internet gateway plays the role of the message pool manager 4 and is operable to export a message intended for a first device 6, called here the providing device, to a second device 8, called here the rendering device.

[0068] The message pool manager 4 is operable to make available a message, which may be any kind of notification or SMS or email, received by the providing device 6, in order to be delivered or rendered by the rendering device 8 to the user. This is particularly advantageous when the providing device 6 is not in the range of perception of the user whereas the rendering device 8 is within this range of perception. By being in the range of perception of a device, it is meant that the user can physically perceive a notification issued by the device.

[0069] As shown in FIG. 1, the system 2 may comprise a plurality of providing devices 6 and a plurality of rendering devices 8. Thus, a message received by one of the providing devices 6 may be stored by the message pool manager 4 in a message pool 9 in order to be “picked” by one of the rendering devices 8 in the range of perception of the user, for instance the nearest rendering device 8 to the user.

[0070] For instance, the providing device 6 is a mobile phone or a tablet or a PC or a laptop, or any connected device able to receive a message intended for a user, such as a TV or a wearable device, whereas the rendering device 8 is a connected TV or a set-top box or a laptop or an alarm clock or any connected device operable to render the message, such as a smart watch or a connected fridge.

[0071] Obviously, according to the circumstances, a providing device 6 may also have the role of a rendering device 8 and vice versa, mainly in function of the proximity of each of these devices to the user.

[0072] The providing device 6 and the rendering device 8 are connected to the message pool manager 4 through a wired network such as Ethernet or PLC (Power Line Carrier) and/or a wireless network such as Wifi or Bluetooth.

[0073] Referring now to FIG. 2, there is shown therein a schematic view of a system 10 implementing a second embodiment of the present invention.

[0074] According to the second embodiment, the exporting service is managed in a distributed manner by the devices of the system 10.

[0075] The system 10 comprises for example a home network 12 to which are connected several devices 14, 16. By analogy with the first embodiment, the devices 14 are providing devices and the devices 16 are rendering devices.

[0076] The message pool manager 18 is then distributed over all these devices 14, 16, each of them hosting a part of a message pool 20.

[0077] According to this second embodiment, each device 14, 16 is able to subscribe to the message pool 20, read content and send/receive events. This can be achieved with well-known distributed computing techniques, such as UPnP, DDS, QeO, etc.

[0078] According to the second embodiment, a message, which may be any kind of notification or SMS or email, received by a providing device 14 is made available, preferably within said providing device 14 or in another connected device 14, 16 in order to be delivered or rendered by a rendering device 16 to the user. This is particularly advantageous when the providing device 14 is not in the range of perception of the user whereas the rendering device 16 is within this range of perception.

[0079] As shown in FIG. 2, the system 10 may comprise a plurality of providing devices 14 and a plurality of rendering devices 16. Thus, a message received by one of the providing devices 14 may be “picked” by one of the rendering devices 16 in the range of perception of the user, for instance the nearest rendering device 16 to the user.

[0080] For instance, the providing device 14 is a mobile phone or a tablet or a PC or a laptop, or any connected device operable to receive a message intended for a user whereas the rendering device 16 is a connected TV or a set-top box or a laptop or an alarm clock or any connected device operable to render the message.

[0081] Obviously, according to the circumstances, a providing device 14 may also have the role of a rendering device 16 and vice versa, mainly in function of the proximity of each of these devices to the user.

[0082] The providing device 14 and the rendering device 16 are connected to the home network 12 through a wired link such as Ethernet or PLC (Power Line Carrier) and/or a wireless link such as Wifi or Bluetooth.

[0083] FIG. 3 is a schematic view representing the structure of the message pool manager 4, 18 according to an embodiment of the present invention.

[0084] The message pool manager 4, 18 comprises a reception module 22 operable to receive a message from a providing device 6,14.

[0085] It also comprises a storage module 24 operable to store said message in the message pool 9, 20.

[0086] FIG. 4 shows an example of a message pool 9, 20 wherein each message comprises the following fields: [0087] the identity “SPI” (Service Provider Identifier) of the providing device 6,14. This identity can be of any kind of format, such as numeric, hexadecimal, ASCII. For instance, such identity may be “jane_mobile” or “bob_iphone”; [0088] the message date “Date”, for instance in the format dd/mm/yy followed by the exact time of sending the message; [0089] the sender “From” which may be for instance a phone number or an email address; [0090] the addressee “To”, for instance designated by his/her name “jane” or “bob” and his/her phone number or email address; [0091] the content of the message “Message”.

[0092] Optionally, other fields could favorably be added, such as the message type and/or the message priority and/or any other field which will bring some useful information about the message context to the user.

[0093] Furthermore, a message may be protected by a key in order to prevent non authorized rendering devices 8, 16 or users to access said message.

[0094] Returning to FIG. 3, the message pool manager 4, 18 further comprises a transmission module 26 operable to transmit said message from the message pool manager 4, 18 to a rendering device 8, 16 further to a request from said rendering device 8, 16 when said rendering device 8, 16 is in a perception range of the user.

[0095] In the case of the first embodiment of FIG. 1, the modules 22, 24, 26 of the message pool manager 4, are within one device which plays the role of the centralized message pool manager 4. All the messages of the message pool 9 are stored within a memory embedded or attached to said device.

[0096] In the case of the second embodiment of FIG. 2, the modules 22, 24, 26 and the message pool 20 are distributed in the devices 14, 16. For instance, when a message is intended for a providing device 14 out of range of the user's perception, said message is advantageously received by the reception module 22 and stored by the storage module 24 in a message pool 20 within said providing device 14. Then, the transmission module 26 transmits said message to a rendering device 16 after a request received from said rendering device 16 located in the range of perception of the user.

[0097] Alternatively, this transmission could occur before if the rendering device 16 wants to cache the message before the user comes in the range of perception of said rendering device 16.

[0098] FIG. 5 is a schematic view representing the structure of the rendering device 8, 16 according to an embodiment of the present invention.

[0099] The rendering device 8, 16 comprises a detection module 30 operable to detect that said rendering device 8, 16 is in the perception range of the user to whom the message is intended.

[0100] In order to detect if a user is in this range, the detection module 30 may consider if the user is using said rendering device 8, 16.

[0101] Advantageously, the detection module 30 comprises or is connected to at least one sensor operable to detect the user presence, such as a camera or a smart remote controller.

[0102] The detection module 30 may also use a proximity detector such as a near field sensor, for example NFC, Bluetooth LE, iBeacon, etc.

[0103] The rendering device 8, 16 also comprises a requesting module 32 operable to request a message stored in the message pool 9, 20 from the message pool manager 4, 18.

[0104] The rendering device 8, 16 further comprises a reception module 34 operable to receive said message from the message pool manager 4, 18.

[0105] The rendering device 8, 16 also comprises a rendering module 36 operable to render the message.

[0106] The manner of rendering the message depends on the rendering module 36 capabilities. For instance, if the rendering module 36 comprises a screen, it displays the message on the screen. If the rendering module 36 has an audio player, the message will be presented as an audio message.

[0107] Furthermore, the rendering module 36 is operable to determine the best time suitable for the rendering of the message to the user.

[0108] For example, if the rendering device 8, 16 is a connected TV or a set-top box, it may chose to render the message during a TV program break.

[0109] The rendering module 36 is also operable to determine a suitable display format for delivering the message to the user.

[0110] For instance, the message may be displayed in the form of a popup or of a panel or of an icon, etc.

[0111] The rendering device 8, 16 further comprises an input module 38, for instance a keyboard or a remote control or a touch screen enabling the user to answer to the message.

[0112] The rendering device 8, 16 also comprises a removing module 40 operable to remove the message from the message pool further to its rendering in order to prevent the rendering of the message from other rendering devices.

[0113] According to an embodiment, the providing device 6, 14 is notified about the message rendering completion and may decide to remove the message from its internal messaging service, such as for instance, the SMS notification bar.

[0114] Now, the details of an embodiment of the method of exporting messages will be described with reference to the flowchart of FIG. 6.

[0115] Let's consider for an illustrative purpose the case of a centralized pool manager, i.e. the embodiment of FIG. 1. The described steps below are of course identical in the case of a distributed pool manager.

[0116] As an example, the system 2 comprises two providing devices 6, for instance two mobile phones of two users Jane and Bob in the home: “Jane phone” and “Bob phone”, and two rendering devices 8: a TV and a laptop which may be used by both users Jane and Bob. The message pool manager 4 is for instance implemented in a home gateway.

[0117] Initially, the message pool 9 is empty and Bob is watching the TV 8. The detection module 30 of the TV 8 detects that Bob is using the TV 8 and thus that the TV 8 is in the range of perception of Bob.

[0118] At a first step 50, Bob's phone receives a message, for example an SMS.

[0119] As Bob is watching the TV 8 and does not want to be disturbed by the phone 6, the message is transmitted at step 52 from Bob's phone to the message pool manager 4 that stores it in the message pool 9.

[0120] At step 54, the message pool manager 4 notifies both rendering devices 8 about the arrival of a new message for the user Bob in the message pool 9.

[0121] The TV 8 which is in the range of perception of Bob requests the message from the message pool manager 4.

[0122] At step 56, after having received the message, the TV 8 displays the message, either immediately or during the next break of the TV program, for example. Bob reads the message and the removing module 40 of the TV 8 removes said message from the message pool 9.

[0123] At step 58, Bob answers the message using the input module 38, for example the remote control of the TV 8, and the TV 8 sends the answer to the message pool manager 4 which stores it in the message pool 9 as a message response. This message response comprises the field of the identifier of the providing device, which is “bob_phone” here. Optionally, it could also include an identifier of the original message.

[0124] At step 60, the message pool manager 4 transmits the message response to Bob's phone 6. Then, Bob's phone sends the message response through the mobile network in a conventional manner and removes the message response from the message pool 9.

[0125] While in the represented embodiment, the message type is a SMS, it could also be an email or an instant message, or even a simple notification such as an incoming call, where, if it has audio input/output capabilities, the rendering device 8 could pick up the call and connect the caller and the recipient.

[0126] While there has been illustrated and described what are presently considered to be the preferred embodiments of the present invention, it will be understood by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from the true scope of the present invention. Additionally, many modifications may be made to adapt a particular situation to the teachings of the present invention without departing from the central inventive concept described herein. Furthermore, an embodiment of the present invention may not include all of the features described above. Therefore, it is intended that the present invention is not limited to the particular embodiments disclosed, but that the invention includes all embodiments falling within the scope of the appended claims.

[0127] Expressions such as “comprise”, “include”, “incorporate”, “contain”, “is” and “have” are to be construed in a non-exclusive manner when interpreting the description and its associated claims, namely construed to allow for other items or components which are not explicitly defined also to be present. Reference to the singular is also to be construed to be a reference to the plural and vice versa.

[0128] A person skilled in the art will readily appreciate that various parameters disclosed in the description may be modified and that various embodiments disclosed and/or claimed may be combined without departing from the scope of the invention.

[0129] For instance, the invention may be advantageously implemented outside the home network in an external network such as Internet.