WO2009082097A1

WO2009082097A1 - Method and system for providing a message including a list of recipient user devices to each recipient user device

Info

Publication number: WO2009082097A1
Application number: PCT/KR2008/007178
Authority: WO
Inventors: Romain Masson
Original assignee: Lg Electronics Inc.
Priority date: 2007-12-26
Filing date: 2008-12-04
Publication date: 2009-07-02

Abstract

A method and system for controlling a message in a multi-device system including a plurality of user devices registered to a server for a user, are discussed. According to an embodiment, the method includes receiving, by the server, a SIP-based message associated with the user; acquiring, by the server, a list of the registered user devices for the user; inserting, by the server, a list of recipient user devices based on at least the list of registered user devices in the SIP-based message; and transmitting, by the server, the SIP-based message including the list of recipient user devices to each of the recipient user devices.

Description

METHOD AND SYSTEM FOR PROVIDING A MESSAGE INCLUDING A LIST OF RECIPIENT USER DEVICES TO EACH

RECIPIENT USER DEVICE

Technical Field

[1] The present invention relates to a method and system for providing information regarding recipient user devices that are receiving a message in the same message to each of the recipient user devices.

Background Art

[2] An IP multimedia subsystem (IMS) is spotlighted as essential information and communication technology for providing a new multimedia service in a next generation internet protocol (IP) based communication environment. The IMS combines an IP network with the mobile communication environment. Accordingly, in the IMS, since a terminal and an IP network easily interact with each other, it is possible to provide multimedia services such as IP-based voice, audio, video, and data by using a mobile communication terminal.

[3] One of the available signaling protocols of the IMS network is a session initiation protocol (SIP). The SIP is a call control protocol in an application layer for generating, modifying, and terminating an IP-based multimedia service session between user terminals or between a user terminal and an entity with an IP address by searching for a location of a target to be communicated with.

[4] Among the various services provided through the IMS network, a converged IP messaging (CPM) service is technology for combining existing multimedia communication services such as a short messaging service (SMS), a multi-media messaging service (MMS), an E-mail service, a voice over IP (VoIP) service, a push-to (PT) service, and the like with one another and providing the combined service under an IP- based infrastructure. Unlike existing individual multimedia communication services provided through limited networks and terminals, in the CPM, it is possible to provide a converged service regardless of kinds of terminals, types of media, kinds of access networks, and types of services.

[5] In a CPM service system, a user can register the user's multiple devices at a network server so that the user can receive a message (e.g., CPM message) or content to each of the user's registered devices. For example, in a CPM service system, assume a user R registers his home PC and his mobile phone at a network server. When a sender X sends a message addressed to the user R, then the server (or another server communicating with that server) can send the message to each of the user R's registered devices depending on the configurations. As a result, the user R can access the message at those recipient user devices.

[6] In the related art, however, a recipient at any of the recipient user devices that are receiving a message does not and cannot know which other user devices are also receiving the same message. This can create problems since such a message may be viewed by undesirable persons without the intended recipient realizing that such undesirable viewing is occurring or occurred. Disclosure of Invention Technical Solution

[7] A technical goal of the present invention is to provide a method and system for providing information identifying all recipient user devices that are receiving a particular message to each of the recipient user devices.

[8] Another technical goal of the present invention is to provide an enhanced CPM service method and system which address the limitations and disadvantages associated with the related art.

[9] Another technical goal of the present invention is to provide a method, server and user device for registering user device information associated with a user, inserting a list of recipient user devices in a message, and providing the message including the list of recipient user devices to each of the recipient user devices.

[10] According to an aspect of the present invention, there is provided a method for controlling a message in a multi-device system, the multi-device system including a plurality of user devices registered to a server for a user, the method comprising: receiving, by the server, a SIP-based message associated with the user; acquiring, by the server, a list of the registered user devices for the user; inserting, by the server, a list of recipient user devices based on at least the list of registered user devices in the SIP-based message; and transmitting, by the server, the SIP-based message including the list of recipient user devices to each of the recipient user devices.

[11] According to another aspect of the present invention, there is provided a method for controlling a message in a multi-device system, the multi-device system including a plurality of user devices registered to a server for a user, the method comprising: receiving, by one of the registered user devices, a SIP-based message associated with the user, the SIP-based message including recipient user device information identifying all recipient user devices to which the SIP-based message is to be sent, the identified recipient user devices including the one of the registered user devices and being all the registered user devices or a subset of the registered user devices; processing, by the one of the registered user devices, the SIP-based message including the recipient user device information; and displaying, on a display of the one of the registered user devices, at least a part of the recipient user device information.

[12] According to another aspect of the present invention, there is provided, in a multi- device system including a plurality of user devices registered to a server for a user, one of the registered user devices comprising: a receiving unit configured to receive a SIP- based message associated with the user, the SIP-based message including recipient user device information identifying all recipient user devices to which the SIP-based message is to be sent, the identified recipient user devices including the one of the registered user devices, and being all the registered user devices or a subset of the registered user devices; a controller configured to process the SIP-based message including the recipient user device information; and a display unit configured to display at least a part of the recipient user device information under control of the controller.

Advantageous Effects

[13] In multi-user device systems, the present invention allows the registration of multiple user devices in association with a user along with possible message receipt preference information, the insertion of recipient user device information into a message based on the registered information, and the transmission of the message including the recipient user device information to each of the recipient user devices. As a result, any user in each of the recipient user devices can readily know which devices are receiving the same message. Further, such information can be used to control the distribution and accessing of the message among the multiple user devices as well as to manage the user devices and information stored in each of those devices. Brief Description of the Drawings

[14] FIG. 1 is a block diagram of a system for registering multiple user devices in association with a user according to an embodiment of the present invention.

[15] FIG. 2 is an example of user device address information and user device name information stored in association with user information according to the present invention.

[16] FIG. 3 is a block diagram of a system for delivering a message including recipient user device information to each of the recipient user devices according to an embodiment of the present invention.

[17] FIG. 4 is an example of a screen display illustrating a message including recipient user device information according to an embodiment of the present invention.

[18] FIG. 5 is a block diagram of a user device according to an embodiment of the present invention.

[19] FIG. 6 is a flowchart illustrating a method for delivering a message including recipient user device information to each of the recipient user devices according to an embodiment of the present invention.

[20] FIG. 7 is an example of a SIP INVITE message including recipient user device information according to an embodiment of the present invention.

[21] FIG. 8 is an example of a SIP MESSAGE message including recipient user device information in its header according to an embodiment of the present invention.

[22] FIG. 9 is an example of a SIP MESSAGE message including recipient user device information in its body according to an embodiment of the present invention. Mode for the Invention

[23] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The following embodiments should be considered in descriptive sense only and not for purpose of limitation.

[24] The present invention preferably applies to a CPM message/system, but is clearly not limited thereto and is equally applicable to and encompasses an OMA system, an IETF system, any multi-device system or a SIP based message/system such as PoC or instance message where multiple devices are used. In fact, the present invention is applicable to any service that supports multiple devices per user.

[25] Further, the present invention encompasses a transmission and reception of a message by a user device, where the message can be in any form and can be a content, data, signal, request, information, etc. For example, the present invention is applicable to any message type that the service supports to provide the message to multi-user devices, e.g., voice mail, text message, text message within a gaming application or any other application, voice/video conferences, etc.

[26] FIG. 1 is a block diagram of a system for registering multiple user devices in association with a user according to an embodiment of the present invention.

[27] Referring to FIG. 1, the system includes one or more user devices 2OA (device A),

2OB (device B), ... associated with a user (e.g., Lambda), and an application server (AS) 30 configured to communicate with each of the user devices 2OA, 2OB,... through a network such as a SIP/IP core using known communication methods. All components of the system are operatively coupled and configured.

[28] The application server 30 is preferably a network server for providing interfaces and services to clients (e.g.., user devices 2OA, 2OB,...). Some examples of such application server can be messaging servers such as SIMPLE IM Server, presence server, gaming server, etc. In the IMS/CPM environment, the application server 30 can be a SIP Application Server (SIP AS) for interfacing with the S-CSCF using SIP so as to host and execute the IP multimedia services. Each user device can be any device capable of communicating with the application server 30 and/or receiving a message from the application server 30 or another server communicating with the application server 30.

[29] If the system of FIG. 1 is a CPM system, each user device 2OA, 2OB,... can include a

CPM client which allows a user to use CPM-based services by interacting with other CPM functional components such as a CPM conversation server in the system. The application server 30 can be or can include such a CPM conversation server functioning as the network-side server for coordinating various communications and interactions among multiple CPM clients. Other known components (e.g., message and media storage server, etc.) in CPM systems may also be present in the present system.

[30] As shown in FIG. 1, the user Lambda can register all of his user devices 2OA, 2OB,... to the application server 30 through a network. For example, at each of the user devices 2OA, 2OB,..., the user can register that user device by inputting his credential and/or user identification information (e.g., login and/or password) into the user device. Then the user device sends a registration message (e.g., a SIP Register, etc.) to the application server 30 through a known communication channel. The registration message includes preferably the address of the user device and the user identity information, but can additionally include the name of the user device (optional), network address information, user's message receipt preference information, etc.

[31] Once or as the application server 30 receives the user device address information from each of the user devices for a particular user (in this example, Lambda), the application server 30 compiles all the user device address information for the user Lambda by linking the user device address information to the user information (e.g., user ID, etc.).

[32] In addition, the user can set a specific desired device name for a user device, which then can be sent to the application server 30 along with the device address information of the user device. For example, at a particular user device, the user device can be configured to request the user if the user would like to name the device according to the user's preference. Once the user names the device (e.g., "My Laptop" for the user device 20A), the device name is registered with the device address information both in association with the user in the application server 30.

[33] All information (e.g., user device address information, user device name information, etc.) registered in association with the user as discussed above is also referred to herein as user device registration information.

[34] FIG. 2 shows an example of a table showing user device address information (e.g.,

Device Address 1, Device Address 2, etc.) and user device name information (Device Name 1, Device Name 2, etc.) for the user Lambda's various user devices, which are stored in association with the user Lambda (user information). This table or the information stored therein is stored in the application server 30 or in a storage unit accessible by the application server 30. [35] Furthermore, each user can define his or her preferences related to how and/or when the user receives his messages, so that each message may be selectively received only by certain user device(s) according to such preference information as desired or needed. Such preference information is referred to herein as message receipt preference information, which can be stored in the application server in association with the user and/or device address information and/or device name information. For example, if the user prefers to receive all his large-sized messages only at his PC at home, but not at his PDA or notebook due to memory constraints, then the user can enter this message receipt preference information to the application server 30, so that a message routing server (e.g., terminating AS) processes the user's messages according to the message receipt preference information.

[36] FIG. 3 is a block diagram of a system for delivering a message including a list of recipient user devices to each of the recipient user devices according to an embodiment of the present invention. The system of FIG. 3 can be a CPM system, a SIP-based message system, any multi-device system, etc. as discussed above.

[37] In the system of FIG. 3, the user Lambda has registered his user devices 2OA, 2OB,... to a terminating application server 50 (or to another application server communicating with the terminating application server 50) according to the registration methods discussed above in connection with FIG. 1 and/or FIG. 2.

[38] When a sender of a message such as a user Gamma sends a message (e.g., a CPM message or any type of SIP-based message such as a SIP INVITE, a SIP MESSAGE, a SIP NOTIFY, etc.) directed to the user Lambda through the user Gamma's device 10, the message is sent to an application server servicing the user Gamma's device, namely, an originating application serve (AS) 40 through a SIP/IP core 100.

[39] The originating AS 40 then sends the message to the terminating AS 50 (AS servicing the user Lambda's devices) through the SIP/IP core 100. Here, if the user Lambda's devices and the user Gamma's devices are serviced by one same AS, then the originating AS and the terminating AS would be the same.

[40] Once the terminating AS 50 receives the message directed to the user Lambda, the terminating AS 50 checks its database and determines which of the user Lambda's registered device(s) should be receiving the message. For example, the terminating AS 50 can determine all devices registered in association with the user Lambda using the user device registration information. Then the terminating AS 50 can further check the stored message receipt preference information of the user Lambda and determines which (all or subset) of those registered devices should be receiving the message based on the message receipt preference information (if stored or applicable). As a default setup, the terminating AS 50 can determine to send the message to all registered user devices of the user Lambda. [41] As a variation, in addition to the user device registration information and/or message receipt preference information, the terminating AS 50 can further check operator policy information, network load information, or any other information to decide which user device associated with the user Lambda will receive the message. Operator policy information can be a policy (e.g., default settings) set by an operator (e.g., service provider). In one example, the system can be set so that the operator policy information overrides the message receipt preference information.

[42] Once the terminating AS 50 determines which of the user Lambda's devices will receive the message, the terminating AS 50 inserts such recipient user device information into the message. The recipient user device information indicates a list of those user devices that are to receive the message. For instance, in the example of FIG. 3, if the devices A and B (2OA and 20B) are to receive the message, the device address information and/or the device name information of the devices A and B are inserted into the message to be sent to each of the devices A and B. The recipient user device information is preferably inserted into a header or body of the message in a CPM service system or other SIP based system. Further, the recipient user device information may be inserted by any SIP server in the path of the message delivery in the home network of a recipient of the message.

[43] The terminating AS 50 sends the message including the recipient user device information to each of the recipient user devices of the user Lambda through the SIP/IP core 100. At each of the recipient user devices, the message including the recipient user device information can be output on an output unit (e.g., audio output unit and/or display unit) of the user device. For instance, as shown in FIG. 4 illustrating an example of a screen display of a user device, the message including a message content 60 and a list of recipient user devices (recipient user device information) 60 can be displayed on the display unit of each of the recipient user devices. In this example, since the devices A and B are receiving this message, the devices A and B are identified (60), e.g., by the device name or by some other identification information. Accordingly, the same message including the recipient user device information is displayed in all recipient user devices, which can occur simultaneously or in some designated order.

[44] FIG. 5 is a block diagram of an example of a user device (e.g., user device 10, 2OA,

2OB,...) according to an embodiment of the present invention.

[45] As shown in FIG. 5, each of the user devices 10, 2OA, 2OB,... can include a CPM client 71 for providing communications associated with CPM based services, a transmitter 72 for transmitting signals including messages, etc., a receiver 73 for receiving signals including messages, etc., an input unit 74 (e.g., a keyboard, keypad, etc.) for receiving a user's input such as registration information, user preference in- formation, etc., a display or output unit 75 for visually outputting signals including messages and other contents, an audio output unit 76 (e.g., speakers), a memory 77 for storing data, and a controller 70 for controlling these components and/or operations of the user device. Each user device can include other components, and all components of the user devices are operatively coupled and configured.

[46] Examples of the user devices 10, 2OA, 2OB, ... include, but are not limited to, a computer notebook, a PC, a mobile terminal, a user equipment, a handset, a smart phone device, a pager, a PDA, a GPS device, a Bluetooth device, etc.

[47] FIG. 6 is a flowchart illustrating a method for delivering a message including recipient user device information to each of the recipient user devices according to an embodiment of the present invention. The method of FIG. 6 is implemented in the system of FIG. 3, but can be implemented in other suitable systems.

[48] Referring to FIG. 6, at step Sl, a user (e.g., Gamma) using his user device 10 generates and sends a message directed to a recipient user (e.g., Lambda). This message can be any SIP based message to be sent towards another user device, such as a SIP INVITE, a SIP MESSAGE, a SIP NOTIFY, etc. A SIP INVITE, a SIP MESSAGE and a SIP NOTIFY are known SIP messages. Generally, a SIP INVITE request is sent by a SIP client device when a user is willing to initiate a session, e.g., a chat session, during which messages can be exchanged. A SIP MESSAGE is generally used as a stand alone message or a pager mode message. A SIP NOTIFY is generally used to keep track of certain status information. Accordingly, the present invention is applicable to any type of SIP based messages including all types of SIP messages, SIP requests, etc.

[49] Through the SIP/IP core 100, the message from the user Gamma device 10 is received by the originating AS 40 which in turn forwards the message to the terminating AS 50 at step S2. The originating AS 40 and the terminating AS 50 can be the same server or different servers/entities located within the same network or different networks.

[50] At step S3, the terminating AS 50 checks its stored information associated with the recipient user (Lambda), determines which of the registered user devices of the user Lambda should be receiving the message, and inserts such recipient user device information into the message, e.g., into a header or body of the message. For instance, the terminating AS 50 determines which registered user device(s) of the user Lambda should be receiving the message based on one or more of the following information: user device registration information of the user Lambda, message receipt preference information (if applicable) of the user Lambda, operator policy information (if applicable), etc. In some cases, all registered user devices may receive the message, whereas in other cases, only a subset of the registered devices may receive the message.

[51] Once the recipient user devices are determined, the terminating AS 50 generates recipient user device information identifying a list of the recipient user devices based on the determination results, and inserts the recipient user device information into the message. In this example, the recipient user device information indicates that the device A (20A) and device B (20B) will receive the message.

[52] At steps S4 and S5, the message including the recipient user device information is sent to each of the recipient user devices, namely in this example, the devices A and B (2OA and 20B). The message can be sent to the devices A and B simultaneously or in some order (if designated). At each of the recipient devices A and B, the message including the recipient user device information is output via the display unit and/or audio output unit, e.g., as shown in FIG. 4.

[53] Accordingly, the recipient at one device can know exactly which of the recipient's other devices have also received the same message. Such information can also assist the recipient with organizing, updating and managing his multiple devices and information stored therein.

[54] As discussed above at step S3, the terminating As 50 inserts the recipient user device information into the header or body of the message, which will be now discussed in more detail referring to various examples shown in FIGs. 7-9.

[55] For example, as shown in FIG. 7, if the message involved is a SIP INVITE request message 84 which includes a header area (H) and a body area (B), the recipient user device information can be inserted into the SIP header area (H) of the message 84. As a variation, the recipient user device information can be inserted into the body area (B) (SDP - Session Description Protocol) of the message 84. The recipient user device information includes a list of recipient user devices identified by the device names 80A and 81A (e.g., My Laptop and My PDA) and the corresponding device addresses 80B and 8 IB. In one example, when the recipient user device information is displayed at each user device, the device names without the devices addresses may be displayed.

[56] In another example, as shown in FIG. 8, if the message involved is a SIP MESSAGE message 86 which includes a header area (H) and a body area (B), the recipient user device information can be inserted into the header area (H) of the message 86. As a variation, the recipient user device information can be inserted into the body area (B) of the message 86. The recipient user device information includes a list of recipient user devices identified by the device names 80A and 81A and the corresponding device addresses 80B and 8 IB.

[57] In still another example, as shown in FIG. 9, if the message involved is a SIP

MESSAGE message 88 which includes a header area (H) and a body area (B), the recipient user device information can be inserted into the body area (B) of the message 88. As a variation, the recipient user device information can be inserted into the header area (H) of the message 88. Here, the recipient user device information is inserted in the body as a MIME (Multipurpose Internal Mail Extensions) attachment, and includes a list of recipient user devices identified by the device names 80A and 81A and the corresponding device addresses 80B and 8 IB. A MIME is generally an internet standard extending the email data format for allowing support of different text codings, non-text contents, and multiple contents. A MIME attachment is a part of contents inside the MIME message. Content types defined in the MIME are often used in known communication protocols such as HTTP or SIP.

[58] Accordingly, the present invention allows a recipient of a message to know exactly which of the recipient's devices are receiving the same message, which in turn results in enhanced management of the message and user devices in multi-user device systems.

[59] While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the appended claims. Industrial Applicability

[60] The present invention may be applicable to a user device and a network server for providing enhanced message related information in CPM systems, SIP-based systems and other multi-device systems.

Claims

[1] method for controlling a message in a multi-device system, the multi-device system including a plurality of user devices registered to a server for a user, the method comprising: receiving, by the server, a SIP-based message associated with the user; acquiring, by the server, a list of the registered user devices for the user; inserting, by the server, a list of recipient user devices based on at least the list of registered user devices in the SIP-based message; and transmitting, by the server, the SIP-based message including the list of recipient user devices to each of the recipient user devices.

[2] The method of claim 1, wherein in the inserting step, the list of recipient user devices is inserted into a header or body of the SIP-based message.

[3] The method of claim 1, wherein the inserting step includes: determining, by the server, the list of recipient user devices based on the list of registered user devices and at least one of user preference information and operator policy information.

[4] The method of claim 3, wherein in the determining step, the operator policy information overrides the user preference information.

[5] The method of claim 1 , wherein the SIP-based message is a SIP INVITE, a SIP

MESSAGE, or a SIP NOTIFY.

[6] The method of claim 1, wherein the list of recipient user devices includes device name information of each of the recipient user devices and device address information of each of the recipient user devices.

[7] A method for controlling a message in a multi-device system, the multi-device system including a plurality of user devices registered to a server for a user, the method comprising: receiving, by one of the registered user devices, a SIP-based message associated with the user, the SIP-based message including recipient user device information identifying all recipient user devices to which the SIP-based message is to be sent, the identified recipient user devices including the one of the registered user devices and being all the registered user devices or a subset of the registered user devices; processing, by the one of the registered user devices, the SIP-based message including the recipient user device information; and displaying, on a display of the one of the registered user devices, at least a part of the recipient user device information.

[8] The method of claim 7, wherein in the receiving step, the recipient user device information inserted into a header or body of the SIP-based message is received.

[9] The method of claim 7, wherein the SIP-based message is a SIP INVITE, a SIP

MESSAGE, or a SIP NOTIFY.

[10] The method of claim 7, wherein the displayed recipient user device information includes at least one of device name information of each recipient user device and device address information of each recipient user device.

[11] In a multi-device system including a plurality of user devices registered to a server for a user, one of the registered user devices comprising: a receiving unit configured to receive a SIP-based message associated with the user, the SIP-based message including recipient user device information identifying all recipient user devices to which the SIP-based message is to be sent, the identified recipient user devices including the one of the registered user devices, and being all the registered user devices or a subset of the registered user devices; a controller configured to process the SIP-based message including the recipient user device information; and a display unit configured to display at least a part of the recipient user device information under control of the controller.

[12] The one of the registered user devices of claim 11, wherein the receiving unit receives the recipient user device information inserted into a header or body of the SIP-based message.

[13] The one of the registered user devices of claim 11, wherein the SIP-based message is a SIP INVITE, a SIP MESSAGE, or a SIP NOTIFY.

[14] The one of the registered user devices of claim 11, wherein the recipient user device information identifies all recipient user devices, and includes at least one of device name information and device address information for each recipient user device.