EP2549695B1 - Method and system for managing message threads in converged ip messaging service - Google Patents

Method and system for managing message threads in converged ip messaging service Download PDF

Info

Publication number
EP2549695B1
EP2549695B1 EP12189057.8A EP12189057A EP2549695B1 EP 2549695 B1 EP2549695 B1 EP 2549695B1 EP 12189057 A EP12189057 A EP 12189057A EP 2549695 B1 EP2549695 B1 EP 2549695B1
Authority
EP
European Patent Office
Prior art keywords
message
thread
client terminal
address
sms
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP12189057.8A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2549695A1 (en
Inventor
Kyung-Tak Lee
Sang-Kyung Sung
Wuk Kim
Jae-Kwon Oh
Seung-Yong Lee
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of EP2549695A1 publication Critical patent/EP2549695A1/en
Application granted granted Critical
Publication of EP2549695B1 publication Critical patent/EP2549695B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/06—Message adaptation to terminal or network requirements
    • H04L51/066—Format adaptation, e.g. format conversion or compression
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to a method and system for converged IP messaging service, and in particular, to a method and system for managing message threads in converged IP messaging service.
  • SMS Short Message Service
  • MMS Multimedia Messaging Service
  • IM Instant Messaging
  • CPM Converged IP Messaging
  • SIP Session Initiation Protocol
  • MMS Mobile Multimedia Subsystem
  • PoC Packet Control Protocol
  • FIG. 1 message transmission/reception in a CPM system is performed according to a process as shown in FIG. 1
  • message transmission/reception in an SMS system is performed according to a process as shown in FIG. 2 .
  • FIGs. 1 and 2 are based on an assumption that each system includes two users, although each system allows message transmission/reception between multiple users. It is also assumed here that users do not explicitly establish a session before exchanging the messages, i.e. the user who wants to start a conversation can send a message immediately without first requesting the creation of a session.
  • FIG. 1 illustrates a typical flow of a message sent from a first user and a second user, represented by a first CPM client 1 and a second CPM client 3 respectively, via a CPM server 2.
  • step 101 the first CPM client 1 sends a typical SIP MESSAGE having a configuration as shown in Table 1 to the CPM Server 2.
  • step 103 the CPM server 2 receives the SIP MESSAGE, identifies if the second CPM client 3 is registered in the CPM server 2, and forwards the SIP MESSAGE having a configuration as shown in Table 2 to the second client 3.
  • the second CPM client 3 receives the message in step 103, and sends back a "200 OK" message having a configuration as shown in Table 3 to the CPM server 2 in step 105.
  • the CPM server 2 Upon receiving the "200 OK" from the second CPM client in step 105, the CPM server 2 forwards a "200 OK" message having a configuration as shown in Table 4 to the CPM client 1 in step 107.
  • FIG. 2 illustrates a typical message processing flow when a first Mobile Station (MS) 4 sends a Short Message (SM) to a second MS 6 via a Short Message Service Center (SMSC) 5.
  • MS Mobile Station
  • SM Short Message
  • SMSC Short Message Service Center
  • step 201 the first MS 4 submits an SM to the SMSC 5 by using an SMS_SUBMIT Protocol Data Unit (PDU). At this time, the first MS 4 can also request an SMS status report (SMS_REPORT).
  • SMS_SUBMIT Protocol Data Unit PDU
  • SMS_REPORT SMS status report
  • the SMSC 5 Upon receiving the SMS_SUBMIT PDU, the SMSC 5 confirms the reception of the SMS_SUBMIT PDU by sending an SMS_SUBMIT_REPORT PDU back to the first MS 4 in step 203.
  • step 205 the SMSC 5 forwards the SM to the second MS 6 through an SMS_DELIVER PDU.
  • step 207 the second MS 6 acknowledges the reception of the SM by sending an SMS_DELIVER_REPORT PDU back to the SMSC 5.
  • the SMSC 5 Upon receiving the SMS_DELIVER_REPORT PDU, the SMSC 5 sends an SMS_STATUS_REPORT PDU to the first MS 4 to report that the SM was successfully delivered to the second MS 6 in step 209.
  • the SMS_SUBMIT PDU includes information elements (from [TS 23.040]) as shown in Table 5.
  • Table 5 Abbr. Reference P 1)
  • P 2) Description TP-MTI TP-Message-Type-Indic ator M 2b Parameter describing the message type.
  • TP-RD TP-Reject-Duplicates M b Parameter indicating whether or not the SC shall accept an SMS-SUBMIT for an SM still held in the SC which has the same TP-MR and the same TP-DA as a previously submitted SM from the same OA
  • TP-VPF TP-Validity-Period-For mat M 2b Parameter indicating whether or not the TP-VP field is present.
  • TP-RP TP-Reply-Path M b Parameter indicating the request for Reply Path.
  • TP-UD HI TP-User-Data-Header-In dicator O b Parameter indicating that the TP-UD field contains a Header.
  • TP-SR R TP-Status-Report-Reque st O b Parameter indicating if the MS is requesting a status report.
  • TP-MR TP-Message-Reference M I Parameter identifying the SMS-SUBMIT.
  • TP-DA TP-Destination-Address M 2-1 2o Address of the destination SME.
  • TP-DC S TP-Data-Coding-Schem e M o Parameter identifying the coding scheme within the TP-User-Data.
  • TP-VP TP-Validity-Period O o/7 o Parameter identifying the time from where the message is no longer valid.
  • TP-UD L TP-User-Data-Length M I Parameter indicating the length of the TP-User-Data field to follow.
  • the SMS_DELIVER PDU includes information elements (from [TS 23.040]) as shown in Table 6.
  • Table 6 Abbr.
  • Reference p 1) R 2) Description TP-MTI TP-Message-Type-Indic ator M 2b Parameter describing the message type.
  • TP-MMS TP-More-Messages-to-Send M b Parameter indicating whether or not there are more messages to send TP-RP TP-Reply-Path M b Parameter indicating that Reply Path exists.
  • TP-OA TP-Originating-Address M 2-12o Address of the originating SME.
  • TP-PID TP-Protocol-Identifier M o Parameter identifying the above layer protocol, if any.
  • TP-SCTS TP-Service-Centre-Time-Stamp M 7o Parameter identifying time when the SC received the message.
  • TP-UDL TP-User-Data-Length M I Parameter indicating the length of the TP-User-Data field to follow.
  • the TP-UD (User Data) contains the message to be sent.
  • the message can be preceded by a header inside the TP-UD.
  • the presence of the header is indicated by the TP-UDHI (User Data Header Indicator) information element, i.e., a TP-UDHI set to "1" indicates that TP-UD is a header.
  • TP-UDHI User Data Header Indicator
  • the header in the TP-UD may be structured as shown in Table 7 (from [TS 23.040]).
  • Table 7 Field Length Length of User Data Header 1 octet Information-Element-Identifier "A" 1 octet Length of Information-Element "A” 1 octet Information-Element “A” Data 0 to "n” octets Information-Element-Identifier "B” 1 octet Length of Information-Element "B” 1 octet Information-Element "B” Data 0 to "n” octets Information-Element-Identifier "X” 1 octet Length of Information-Element "X” 1 octet Information-Element "X” Data 0 to "n” octets
  • the "Information-Element-Identifiers" are predefined values; they all refer to a specific meaning.
  • the list of identifiers and their meaning (for SMS only) are shown in Table 8 (from [TS 23.040]): Table 8 VALUE (hex) MEANING Classification Repeatability 00 Concatenated short messages, 8-bit reference number SMS Control No 01 Special SMS Message Indication SMS Control Yes 02 Reserved N/A N/A 03 Value not used to avoid misinterpretation as ⁇ LF> character N/A N/A 04 Application port addressing scheme, 8 bit address SMS Control No 05 Application port addressing scheme, 16 bit address SMS Control No 06 SMSC Control Parameters SMS Control No 07 UDH Source Indicator SMS Control Yes 08 Concatenated short message, 16-bit reference number SMS Control No 09 Wireless Control Message Protocol SMS Control Note 3 ...
  • the message transmission according to the above-mentioned process may be performed either only once between two users or repeatedly multiple times between the same two users. That is, the users may exchange messages like a conversation through the SMS or CPM service. In this process, two users can handle a conversation by just exchanging a series of messages to each other without explicitly establishing a session beforehand. Therefore, messages that are transmitted to or received from the same counterpart are displayed on an individual window of a user.
  • the same concept is also applicable to the CPM service in which messages are transmitted/received after setup of a session. It is impossible to display a set of messages, which a CPM client has transmitted to or received from the same counterpart according to the CPM service, in a single window, for example, a conversational view. Further, it is also impossible to provide a conversational view including previously exchanged messages in the case of restarting the conversation later, because messages are not bound to any particular session, and thus are not linked to each other.
  • WO-2005/122604-A2 discloses a method for delivering a short message service (SMS) message to an interworking wireless local area network user equipment (UE) begins by registering the UE with an Internet Protocol short message gateway (IP-SM-GW).
  • IP-SM-GW Internet Protocol short message gateway
  • a capability report is sent from the UE to the IP-SM-GW, the capability report including the capabilities of the UE.
  • a SMS message is transmitted from a short message service center (SMSC) to the IP-SM-GW.
  • the capabilities of the UE are evaluated at the IP-SM-GW to determine whether the UE can receive the SMS message, and the SMS message is delivered to the UE via the IP-SM-GW if the UE has the capabilities to receive the SMS message.
  • SMS short message service
  • US-2004/015547-A1 discloses a system and method for providing chat group services to wireless mobile terminals.
  • the chat forum permits integrated voice and text messaging.
  • the system includes plural mobile terminals, each being capable of running a chat client application.
  • a server complex is connected to one or more wireless carrier networks by way of a packet-based network, such as the Internet.
  • the server complex includes server applications and components for supporting the chat group services and communicating with the chat clients on the mobile terminals.
  • the system also includes features that permit the integration of legacy mobile terminals, communication with machine interfaces using a chat metaphor, and robustness and reliability of operation across various wireless operators.
  • Certain embodiments of the present invention provide a method and system for simultaneously providing a single message group including messages transmitted/received between two Converged Internet Protocol Message (CPM) clients to the users.
  • CPM Converged Internet Protocol Message
  • Certain embodiments of the present invention also provide a method and system for simultaneously providing a single message group including messages transmitted/received between users of heterogeneous services, for example, between a CPM client of a CPM service requiring session setup and a Short Message Service (SMS) user of an SMS that does not require session setup, so that the CPM client can effectively transmit/receive a conversational message without determining if the counterpart of the conversational message is a user for whom the CPM service is supported.
  • SMS Short Message Service
  • a CPM system for managing multiple message threads and supporting a Session Initiation Protocol (SIP) based Converged Internet Protocol Messaging Service (CPMS), the CPM system comprising a CPM client for which the CPMS is supported; a non-IP Multimedia Subsystem (IMS) client that has not joined an IMS service; and an Inter-Working Function (IWF) for, when a recipient client of the CPM client is appointed as the non-IMS client by a CPM server and the IWF receives an SIP message for conversational message communication, converting a message format of the SIP message into a message format that can be received by the recipient client, inserting a thread identifier (ID) included in the SIP message into the converted message, and then transmitting the converted message to the recipient client via a server supporting the recipient client.
  • SIP Session Initiation Protocol
  • CPMS Converged Internet Protocol Messaging Service
  • IMS Inter-Working Function
  • the CPM system comprises a CPM client for which the CPMS is supported; a non-IMS client that has not joined an IMS service; and an IWF for, when a recipient client of the CPM client is appointed as the non-IMS client by a CPM server and the IWF receives an SIP message for conversational message communication, detecting and storing a thread ID from the SIP message, converting a message format of the SIP message into a message format that can be received by the recipient client, transmitting the converted message to the recipient client via a server supporting the recipient client, converting a message received from the recipient client within a predetermined valid reply period to an SIP message, inserting the stored thread ID into the converted SIP message, and transmitting the SIP message to the CPM client via the CPM server.
  • the IWF may delete the stored thread ID when there is no message received from the recipient client within the valid reply period.
  • the recipient client of the CPM client may be appointed as the non-IMS client by the CPM server and the IWF receives an SIP message for conversational message communication, the IWF detects the thread ID, a recipient address, and an originator address from the SIP message, checks if a thread ID, a recipient address, and an originator address corresponding to the detected thread ID, the recipient address, and the originator address are stored in a database, stores the detected thread ID, the recipient address, and the originator address and sets the valid reply period when the corresponding thread ID, the recipient address, and the originator address are not stored in the database, resets the valid reply period previously set in accordance with the detected thread ID when the corresponding thread ID, the recipient address, and the originator address are stored in the database, converts the message format of the SIP message into the message format that can be received by the recipient client, and transmits the converted message to the recipient client via the server supporting the recipient client.
  • the IWF may detect a recipient address and an originator address from the received message, checks if a recipient address and an originator address corresponding to the detected recipient address and the originator address are stored in a database, extracts a thread ID corresponding to the addresses, converts a message format of the received message into the message format of the SIP message, resets a valid reply period corresponding to the thread ID, inserts the thread ID into the message, and transmits the converted message to the CPM client.
  • the CPM system comprises a CPM client for which the CPMS is supported; a MS for which an SMS is supported; an IWF for, when a recipient client of the CPM client is appointed as the MS by a CPM server and the IWF receives an SIP message for conversational message communication, converting a message format of the SIP message into a message format of an SMS SUBMIT Protocol Data Unit (SMS_SUBMIT PDU), setting sub-address digits of a TP destination address of the SMS_SUBMIT PDU to a thread ID detected from the SIP message, and then transmitting the SMS_SUBMIT PDU to the SMSC; and the SMSC for receiving the SMS_SUBMIT PDU, converting the SMS_SUBMIT PDU to an SMS DELIVERY Protocol Data Unit (SMS_DELIVER PDU), setting sub-address digits of a TP originator address of the SMS_DELI
  • SMS_SUBMIT PDU SMS SUBMIT Protocol Data Unit
  • a method for managing a message thread including a series of messages transmitted to and received from a same counterpart by a CPM client supporting an SIP based CPMS comprises receiving a request for transmission of a message for conversational message communication from a recipient; when the message is a first message of a new message thread associated with the recipient, allocating a new thread ID to the new message thread, storing the new thread ID in relation to the recipient, inserting the new thread ID into the message, and then transmitting the message; when the message is a subsequent message in an existing message thread associated with the recipient, detecting a thread ID allocated in accordance with the existing message thread, inserting the allocated thread ID in the message, and then transmitting the message; receiving a message for conversational message communication; and when the received message includes a thread ID, providing a user with the received message with messages included in a message thread corresponding to the thread ID included in the received message.
  • a method for managing a message thread including a series of messages transmitted to and received from a same counterpart by a CPM client supporting an SIP based CPMS comprises transmitting, by a CPM client for conversational message communication, an SIP message that includes a thread ID allocated to a message thread associated with a recipient appointed as a non-IMS client that has not joined an IMS service; and when an IWF receives the SIP message through a CPM server, converting a message format of the SIP message into a message format that can be received by the recipient, inserting the thread ID in the converted message, and then transmitting the converted message to the recipient, by the IWF.
  • the method may further comprise converting the SIP message into an SMS SUBMIT Protocol Data Unit (SMS_SUBMIT PDU), inserting the thread ID into a control parameter of a TP user data header of the SMS_SUBMIT PDU, and transmitting the SMS_SUBMIT PDU to a Short Message Service Center (SMSC), by the IWF; and when the SMSC receives the SMS_SUBMIT PDU, the method may further comprise converting the SMS_SUBMIT PDU into an SMS DELIVERY Protocol Data Unit (SMS_DELIVER PDU), inserting the thread ID into a control parameter of a TP user data header of the SMS_DELIVER PDU, and transmitting the SMS_DELIVER PDU to the MS, by the SMSC.
  • SMS_SUBMIT PDU SMS SUBMIT Protocol Data Unit
  • SMS_DELIVER PDU SMS DELIVERY Protocol Data Unit
  • the method may further comprise converting the SIP message into an SMS_SUBMIT PDU, inserting the thread ID into a message thread information field of a TP user data header of the SMS_SUBMIT PDU, and transmitting the SMS_SUBMIT PDU to an SMSC, by the IWF; and when the SMSC receives the SMS_SUBMIT PDU, the method may further comprise converting the SMS_SUBMIT PDU into an SMS_DELIVER PDU, inserting the thread ID into a message thread information field of a TP user data header of the SMS _DELIVER PDU, and transmitting the SMS_DELIVER PDU to the MS, by the SMSC.
  • the method may further comprise converting the SIP message into an SMS_SUBMIT PDU, inserting the thread ID into a body of a TP user data header of the SMS_SUBMIT PDU, and transmitting the SMS_SUBMIT PDU to an SMSC, by the IWF; and when the SMSC receives the SMS_SUBMIT PDU, the method may further comprise converting the SMS_SUBMIT PDU into an SMS_DELIVER PDU, inserting the thread ID into a body of a TP user data header of the SMS_DELIVER PDU, and transmitting the SMS_DELIVER PDU to the MS, by the SMSC.
  • the method may further comprise converting the SIP message into an SMS_SUBMIT PDU, setting sub-address digits of a TP destination address of the SMS _SUBMIT PDU to the thread ID, and transmitting the SMS_SUBMIT PDU to an SMSC, by the IWF; and receiving the SMS_SUBMIT PDU, converting the SMS_SUBMIT PDU into an SMS_DELIVER PDU, setting sub-address digits of a TP originator address of the SMS _DELIVER PDU to the thread ID, and transmitting the SMS_DELIVER PDU to the MS, by the SMSC.
  • a method for managing a message thread including a series of messages transmitted to and received from a same counterpart in a CPM system supporting an SIP based CPMS comprises transmitting, by a CPM client for conversational message communication, an SIP message that includes a thread ID allocated to a message thread associated with a recipient appointed as a non-IMS client that has not joined an IMS service; and when an IWF receives the SIP message through a CPM server, storing the thread ID, an address of the CPM client, and a recipient address, setting a predetermined valid reply period corresponding to the thread ID, converting a message format of the SIP message into a message format that can be received by the recipient, and transmitting the converted SIP message to the recipient through a server supporting the recipient, by the IWF; and when the IWF receives a message from the recipient within the predetermined valid reply period, converting the message received from the recipient into an SIP message, inserting the stored thread ID into the SIP message, and then transmit
  • the method may further comprise deleting the stored thread ID by the IWF when there is no message received from the recipient client within the valid reply period.
  • Converting a message format of the SIP message into a message format that can be received by the recipient and transmitting the converted SIP message to the recipient through a server supporting the recipient by the IWF may comprise: searching a database for the thread ID, the address of the CPM client, and the recipient address; when the thread ID, the recipient address, and an originator address are not included in the database, storing the thread ID, the recipient address, and the originator address in the database and setting the valid reply period; when the thread ID, the recipient address, and the originator address are included in the database, resetting the valid reply period previously set in accordance with the thread ID; and converting a message format of the SIP message into a message format that can be received by the recipient client, and transmitting the converted message to the recipient via the server supporting the recipient client.
  • Converting the message received from the recipient into the SIP message, inserting the stored thread ID into the SIP message, and transmitting the SIP message to the CPM client via the CPM server by the IWF may comprise: when the IWF receives a message within the valid reply period from the recipient, detecting a recipient address and an originator address included in the received message; when the database includes a recipient address and an originator address corresponding to the detected addresses, extracting a thread ID corresponding to the addresses; and resetting the valid reply period corresponding to the thread ID, converting a message format of the message into a message format of the SIP message, inserting the converted message format into the thread ID, and transmitting the converted message to the CPM client.
  • a series of messages transmitted/received between a Converged Internet Protocol Message (CPM) client using the CPM service and the same counterpart is called a "messages thread.”
  • the present invention provides a more friendly user interface by grouping and displaying one or more messages included in a message thread on a single window when a CPM client provides the message thread to a user.
  • an identifier is assigned to a message thread corresponding to the particular counterpart and the message is then transmitted with the identifier.
  • the particular counterpart can be more than one.
  • a CPM client includes a Mobile Station (MS) that provides a user interface between a user and a CPM system in a communication network providing a CPM service (for example, the user interface directly provides a message to the user and receives an input from the user).
  • MS Mobile Station
  • the counterpart of the CPM client in the message communication either may be a CPM client or may not be a CPM client.
  • the counterpart may be either a mobile station of a messaging service transmitting/receiving messages without session setup or a client for which an IP Multimedia Service (IMS) is not supported.
  • IMS IP Multimedia Service
  • the present invention can be applied not only to a message service between CPM clients but also to another messaging system inter-working with the CPM system, which includes, for example, a messaging system that does not provide the IMS and a system providing a messaging service without session setup. Therefore, in the embodiments described below, a system in which a CPM system and an Short Message Service (SMS) system inter-work with each other is discussed to show an application of the present invention to a messaging service between a CPM system and another messaging system as well as a process of providing a message thread in a messaging service between CPM clients.
  • SMS Short Message Service
  • the CPM service is a Session Initiation Protocol (SIP)-based service which requires session setup for a messaging service, while the SMS service does not require session setup for message transmission/reception. Therefore, a CPM system and an SMS system inter-work through an Inter-working Function (IWF).
  • the IWF includes various functions, one representative example of which is the conversion of message formats of a short message and a CPM service message (hereinafter, a "CPM message").
  • CPM message CPM service message
  • FIG. 3 illustrates a process for processing a message in a system in which a CPM system and a short message system inter-work, wherein a CPM client 10 transmits a CPM message to a mobile station 60 for which SMS is supported.
  • a CPM client 10 transmits an SIP message through a CPM server 20 to the IWF 30 in steps 301 and 303.
  • the IWF 30 converts the message format from the CPM service to the SMS in step 305, and transmits the message to the Short Message Service Center (SMSC) 50 through the SMS SUBMIT Protocol Data Unit (SMS SUBMIT PDU) in step 307. Then, The Short Message Service Center (SMSC) 50 transmits the message to the MS 40 through the SMS DELIVERY Protocol Data Unit (SMS_DELIVER PDU) in step 311.
  • SMS Short Message Service Center
  • the MS 40 transmits an SMS_DELIVER_REPORT PDU to the SMSC 50 in step 313, and the SMSC 50 transmits an SMS_STATUS_REPORT PDU to the IWF 30 in step 315.
  • the IWF 30 Upon receiving the SMS_STATUS_REPORT PDU in step 315, the IWF 30 transmits "200 OK" through the CPM server 20 to the CPM client 10 in steps 317 and 319.
  • the CPM client 10 In the case of message transmission as described above, the CPM client 10 cannot differentiate a message thread related to the MS 40 from a message thread related to another communication object. Therefore, according to the present invention, the CPM client 10 inserts a thread ID in an SIP message before transmitting the SIP message.
  • a new eXtensible Markup Language (XML) document containing a ⁇ thread-id> tag is included in the SIP message. Table 9 shows an example of such an XML document. Table 9
  • Table 10 An XML schema corresponding to Table 9 is illustrated in Table 10.
  • the CPM client 10 when a CPM client 10 receives a request to send a message from the user in step 401, the CPM client 10 proceeds to step 403, in which the CPM client checks if the message is the first message of a new thread or a follow-up message of an existing thread.
  • the thread database stores an address corresponding to a particular subject and a thread ID allocated to message thread corresponding to the particular subject when the CPM client 10 exchanges messages with the particular subject for conversational messaging communication.
  • the CPM client 10 has the thread database. Further, the thread database may store messages relating to each thread ID in a manner corresponding to the corresponding thread ID or may store messages relating to each thread ID at a position corresponding to the corresponding thread ID.
  • the messages stored in this way are used for configuration of a conversational view. Therefore, referring to FIG. 4 again, when the CPM client 10 has exchanged a message with the message recipient, the message recipient has been allocated a thread ID, the allocated thread ID has been stored in the thread database, and the message corresponds to a follow-up message of an existing thread. Further, when the CPM client 10 has never received a message from the message recipient and the transmitted message is the first message, the message starts a new thread. Therefore, when an allocated thread ID exists in the address of the recipient of the message requested to be transmitted in step 401, the CPM client 10 detects the corresponding thread ID in step 405, and then proceeds to step 411.
  • the CPM client 10 when there is no thread ID allocated to the recipient, the CPM client 10 generates a new thread ID in step 407, stores the generated thread ID with a relation to the address of the recipient of the message in step 409, and then proceeds to step 411. In step 411, the CPM client 10 generates and transmits an SIP message including the detected thread ID or the generated thread ID.
  • the CPM client 10 may display a conversational view including the message, which corresponds to the recipient.
  • the CPM client 10 may load messages stored in the thread database in relation to the thread ID corresponding to the message or load messages by referring to the storage positions of the messages stored in the thread database in relation to the thread ID, thereby displaying the loaded messages with the message to be currently transmitted within one conversational view.
  • the message to be currently transmitted corresponds to a start of a new message thread, a conversational view including only the message to be currently transmitted will be displayed.
  • the CPM server 20 transmits the message to a corresponding CPM client according to the same process as the conventional process.
  • FIG. 5 illustrates an operation process of the CPM client 10 according to an embodiment of the present invention, when the CPM client 10 receives a CPM message including a thread ID.
  • the CPM client 10 receives and analyzes a new SIP message in step 501, and then proceeds to step 503.
  • the CPM client 10 checks if the SIP message includes a thread ID. When the SIP message does not include any thread ID, the CPM client 10 proceeds to step 505, in which the CPM client simply displays the message in a new conversational view, and ends the procedure.
  • the CPM client 10 proceeds to step 507, in which the CPM client 10 determines if the thread ID and a transmitter address (i.e. the associated originator user's address) included in the SIP message are stored in the thread database.
  • the CPM client 10 proceeds to step 509 when they are stored in the thread database, and proceeds to step 511 when they are not stored in the thread database.
  • the CPM client 10 loads the conversational view associated with the thread ID and the originator user in step 509, and then proceeds to step 513.
  • the message starts a new message thread.
  • the CPM client 10 stores the thread ID and originator's address received in the thread database, and creates a new conversational view associated to them.
  • the CPM client 10 proceeds to step 513.
  • the CPM client 10 adds the new message to the conversational view and displays it to the recipient user. This ends the procedure of the CPM client 10.
  • each message transmitted/received for conversational message communication between two CPM clients may include an identifier for discriminating the message from another message transmitted to or received from another CPM client other than the two CPM clients. Therefore, the two CPM clients can group the messages exchanged between them, so that the grouped messages can be provided to each user in a form of a conversational view.
  • Management and provision of such a message thread can be applied to transmission/reception of messages for conversational communication between a CPM client and an MS for which SMS is supported. Therefore, it is possible to make this inter-working as seamless as possible, and the CPM user does not need to be aware of what messaging service the recipient supports.
  • a thread ID is included in an SIP message transmitted by a sender CPM client and a short message transmitted to a recipient in response to the SIP message.
  • an IWF for inter-working a CPM system and an SMS system stores and manages a thread ID allocated to a CPM client of a transmitter side and an MS of a receiver side, and the IWF provides a service related to the thread ID only to the CPM client without providing the thread ID to the MS.
  • An embodiment according to the first method may extend the thread ID information to the SMS domain. This involves additional information elements in the SM sent to the SMS user, as well as adapted behavior from the MS that receives the SM and sends a reply to it.
  • FIG. 6 illustrates a message processing procedure of a short message system and a CPM system inter-working with each other.
  • the CPM client 10 transmits an SIP message including a message to be transmitted and a thread ID through the CPM server 20 to the IWF 30 in steps 601 and 603.
  • the process of configuring the SIP message by the CPM client 10 is similar to the process shown in FIG. 4 .
  • the IWF 30 receives the SIP message in step 605, it proceeds to step 607.
  • the IWF 30 converts the SIP message to an appropriate Short Message (SM).
  • SM Short Message
  • the SM may be, for example, an SMS_SUBMIT PDU.
  • step 609 the IWF 30 checks if the SIP message contains a thread ID. When a thread ID is present, the IWF 30 proceeds to step 611, and when a thread ID is not present, the IWF 30 proceeds to step 619.
  • step 611 the IWF 30 extracts the thread ID and incorporates the extracted thread ID in the SM. Then, the IWF 30 proceeds to step 613.
  • the IWF 30 sends the converted SM to the SMSC 50. Then, in step 615, the IWF 30 transmits the SMS_SUBMIT PDU to the SMSC 50. In step 617, the SMSC 50 transmits the message to the MS 40 through the SMS_SUBMIT PDU. In step 619, the MS 40 transmits SMS_DELI ⁇ /ER_REPORT PDU to the SMSC 50 and provides the message included in the SMS_DELIVER_REPORT PDU. In step 621, the SMSC 50 transmits the SMS_STATUS REPORT PDU to the IWF 30. Upon receiving the SMS_STATUS_REPORT PDU in step 621, the IWF 30 transmits "200 OK" through the CPM server 20 to the CPM client 10 in steps 623 and 625.
  • Steps 609 and 611 can also occur at any time during the conversion in step 607.
  • the IWF 30 includes the thread ID in the SM to be sent.
  • the thread ID may be either included in a header of the TP-UD (User Data) of the SM, or included in a body part of the TP-UD, or included in a TP-DA (Destination-Address).
  • TP-UD User Data
  • TP-DA TP-DA
  • the thread ID is included in a header of the TP-UD of the SM, a new SMS information element is added.
  • the thread ID is included in a body part of the TP-UD or in a TP-DA, it is possible to construct a system without addition of a new information element.
  • the present invention provides two embodiments, one of which is to include the thread ID in the SMSC control parameter included in the TP-UD, by referring to Table 8.
  • the SMSC control parameter contains information that can be used to control the SMSC, but can also be passed transparently to the recipient MS.
  • the SMSC control parameter contains "Selective Status Report" as octet 1, which controls the creation of status reports, depending on the error code of the particular message.
  • the present invention adds a second octet as shown in Table 11.
  • octet 1 Selective Status Report This facility is used to control the creation of Status Reports, depending on the error code of the particular message. It is also used by the sending entity to request inclusion of the original UDH into the Status Report. In this case the original UDH must be separated from the rest of the UDH using the Source Indicator. The TP-SRR must be set so that the Selective Status Report to be enabled. octet 2 Message thread ID This facility is used to identify the message thread this SM belongs to. The recipient MS must include this information in any reply to this message. The TP-RP (Reply Path) should be set when using this information.
  • the TP-RP (Reply Path) is included in both the SMS_SUBMIT and SMS_DELIVER PDUs to guarantee that the reply goes through the same SMSC that delivered the original message, which guarantees that the SMSC knows the originator MS and is able to forward the reply to the originator.
  • a new information element identifier may be added in the TP-UD header. That is, a new information element identifier named "Message Thread Information (MTI)" may be added in the TP-UD header.
  • MTI Message Thread Information
  • the message thread information can be classified as SMS control and set to have no repeatability.
  • FIG. 7 illustrates a process of transmitting a short message by an MS 40 in a case where a header of a TP-UD of a transmitted SM includes a thread ID.
  • the MS 40 receives a request for transmission of an SM in step 701
  • the MS 40 proceeds to step 703.
  • the MS 40 checks if the SM is a new message or the reply to a previously received message.
  • the MS 40 proceeds to step 705; when the SM is a new message, the message can be sent right away, so the MS 40 proceeds to step 709.
  • step 705 the MS 40 checks if the original message this SM is replying to contains a thread ID in the header of the TP-UD information element. When the original message this SM is replying to contains a thread ID in the header of the TP-UD information element, it proceeds to step 707. When the original message this SM is replying to does not contain a thread ID in the header of the TP-UD information element, it proceeds to step 709.
  • step 707 the MS 40 extracts the thread ID and includes the extracted thread ID in the header of the TP-UD of the SM to be sent. Then, in step 709, the MS 40 sends the SM to the SMSC 50.
  • the SMSC 50 transmits the received SM to the IWF 30, and the IWF 30 having received the SM operates according to the process as shown in FIG. 8 .
  • the IWF 30 when the IWF 30 receives an SM to be sent to the CPM client 10 in step 801, the IWF 30 converts the SM to an appropriate SIP message in step 803, and then proceeds to step 805.
  • step 805 the IWF 30 checks if the SM contains a thread ID information in the header of the TP-UD information element. When a thread ID is present, the IWF 30 proceeds to step 807, and when it is not, the IWF 30 proceeds to step 809, in which the IWF 30 transmits the SIP message converted in step 803.
  • step 807 the IWF 30 extracts the thread ID from the TP-UD of the SM and incorporates the extracted thread ID in the SIP message as an XML document format, as shown in Table 9, and then proceeds to step 809, in which the IWF 30 transmits the SIP message to the CPM server 20.
  • Steps 805 and 807 may be performed while the SM is converted to the SIP message in step 803.
  • the thread ID information may be appended in the existing SMS TP-DA (Destination Address) information element, using the existing sub-addressing and reply-path mechanisms.
  • SMS TP-DA Differentestination Address
  • An originating MS may send an SM with '*'s or '#'s included in the TP-DA field.
  • the first '#' encountered in the TP-DA indicates where the address for SMSC routing purposes is terminated. Additional '*'s or '#'s can be present in the following digits, and all these digits including the first '#' are subaddress digits.
  • the SMSC When the SMSC receives an SM to convey with such a subaddress information, the SMSC should deliver the SM to the destination MS with the same subaddress digits copied in the TP-OA field.
  • MS B having an address of 1234 will receive the SM with TP-OA of 987654321#56#789*.
  • the originating MS address is found in the TP-Originating-Address in the SMS-DELIVER PDU, and existence of the reply path is determined based on if the TP-RP has been set in SMS-DELIVER PDU.
  • the IWF 30 When the IWF 30 receives a SIP message that includes a thread ID and is targeting the MS 40, the IWF 30 converts the received SIP message to an SM and appends the thread ID in the TP-DA information element of the SMS_SUBMIT PDU that contains the SM, as if the thread ID were a sub-address, i.e. ⁇ dest_address># ⁇ thread_id>.
  • the IWF 30 needs to convert the thread ID to a unique digit sequence and keeps a mapping table between the original thread ID and the corresponding sequence in the TP-DA.
  • the IWF 30 also sets the TP-RP (Reply Path) bit to "1", requesting therefore that the replying MS submits any reply SM to the same SMSC from which it received the original SM.
  • TP-RP Reply Path
  • the IWF 30 sends an SMS_SUBMIT PDU to the SMSC 50.
  • the SMSC 50 converts the SMS_SUBMIT PDU to SMS_DELIVER PDU and transmits the converted PDU to the MS 40.
  • the MS 40 receives the SM from the SMSC 50 in an SMS_DELIVER PDU, that contains a TP-OA information element with the thread ID information as sub-address.
  • the MS 40 When the MS 40 sends a reply SM for the received SM, the MS 40 includes the entire content of the TP-OA of the SMS_DELIVER PDU of the received original SM, i.e. including the thread ID, in the TP-DA of the SMS_SUBMIT PDU of the reply SM, as per the reply path procedure.
  • the MS 40 sends the reply SM to the IWF 30 via the SMSC 50, which copies the thread ID in the TP-OA of the SMS_DELIVER PDU delivered to the IWF 30.
  • the IWF 30 When the IWF 30 receives the SMS_DELIVER PDU, the IWF 30 extracts the thread ID from the TP-OA information element and converts the SM to an appropriate SIP MESSAGE.
  • the thread ID is also included in the SIP MESSAGE using the XML format described above. At this time, the thread ID may need to be converted back to the original alphanumeric thread ID sequence using the mapping table described above.
  • the IWF 30 sends the SIP message to the CPM Server 20.
  • Another embodiment for inserting the thread ID in the SM includes a method of inserting the thread ID in the body part of the SM, which corresponds to usage SMS-Email inter-working functionality.
  • the IWF 30 when the IWF 30 receives a SIP message including a thread ID, the IWF 30 converts the SIP message to an SM and includes the thread ID as a subject in the body part of the TP-UD of the SMS_SUBMIT PDU: "## ⁇ thread ID># ⁇ message>".
  • the ⁇ to-address> could also be added by extracting the address (user@domain1.domain2) from the "To:" field of the SIP message.
  • the IWF 30 sends the SMS_SUBMIT PDU that contains the SM to the SMSC 50. Then, the MS 40 receives the SM from the SMSC 50 in an SMS_DELIVER PDU, that contains the thread ID information in the body part of the TP-UD. When the MS 40 sends a reply, it follows the same syntax, so includes the same subject (i.e. the thread ID) of the original message in the TP-UD. The MS 40 sends an SMS_SUBMIT PDU including the reply SM to the SMSC 50, and the SMSC 50 transmits the SMS_DELIVER PDU corresponding to the SMS_SUBMIT PDU to the IWF 30.
  • the IWF 30 When the IWF 30 receives the SMS_DELIVER PDU, the IWF 30 extracts the thread ID from the subject of the received SM, that is, the SMS_DELIVER PDU. Further, the IWF 30 converts the SM to an appropriate SIP message, includes the thread ID in the SIP message using the XML format described above, and then sends the SIP message to the CPM Server 20.
  • an IWF inter-working a CPM system and an SMS system stores and manages a thread ID allocated in accordance with an originator CPM client and a recipient MS, and does not provide the thread ID to the MS. This embodiment can be implemented without changing the conventional SMS system.
  • the IWF simulates the existence of a thread in the SMS domain by storing the "thread ID, originator's address, recipient's address" in the IWF during a certain amount of time.
  • FIG. 9 illustrates a message processing procedure by a CPM system and an SM system inter-working with each other.
  • the CPM client 10 sends an SIP message including a thread ID and a message to be transmitted via the CPM server 20 to the IWF 30.
  • the process of configuring the SIP message by the CPM client 10 is similar to the process shown in FIG. 4 .
  • the IWF 30 detects the thread ID, originator address, and recipient address, stores the detected information in the database, and then converts the SIP message to an appropriate SM. Thereafter, in step 907, the IWF 30 transmits an SMS_SUBMIT PDU including the converted SM to the SMSC 50. In step 909, the SMSC 50 transmits the message through the SMS_DELIVER PDU to the MS 40.
  • the MS 40 Upon receiving the SMS_DELIVER PDU, the MS 40 sends an SMS_DELIVER REPORT PDU to the SMSC 50 and provides the message included in the SMS_DELIVER PDU to the user, although not shown in the drawings. Further, the SMSC 50 transmits the SMS_STATUS_REPORT PDU to the IWF 30. Upon receiving the SMS_STATUS_REPORT PDU, the IWF 30 transmits "200 OK" to the CPM client 10 via the CPM server 20.
  • the MS 40 sends an SMS_SUBMIT PDU, which includes a reply message to the message received by the MS 40 in step 909, to the SMSC 50 in step 911.
  • the SMSC 50 sends a reply message through an SMS_DELIVER PDU to the IWF 30.
  • the IWF 30 detects the originator address and the recipient address included in the SMS_DELIVER PDU, and then obtains a thread ID corresponding to the originator address and the recipient address from the database.
  • the IWF 30 converts the reply message to an SIP message, inserts the obtained thread ID in the SIP message, and then transmits the SIP message to the CPM server 20.
  • the CPM server 20 sends the SIP message to the CPM client 10.
  • step 1000 the IWF 30 waits an event to occur.
  • the event implies either reception of an SIP message or an SM or expiration of a valid reply period.
  • the IWF 30 proceeds to step 1001.
  • the IWF 30 proceeds to step 1101. Further, when a valid reply period associated to a thread ID expires, the IWF 30 proceeds to step 1201.
  • the IWF 30 Upon receiving the SIP message, the IWF 30 checks if the SIP message contains a thread ID in step 1001. When the SIP message contains a thread ID in step 1001, the IWF 30 proceeds to step 1003, otherwise the IWF 30 proceeds to step 1011. In step 1003, the IWF 30 extracts the thread ID, originator's address, and recipient's address from the SIP message, and then proceeds to step 1005. In step 1005, the IWF 30 checks if the extracted three pieces of information is in its database. When there is no such information, the IWF 30 proceeds to step 1007. When there is the extracted three pieces of information, the IWF 30 proceeds to step 1009.
  • step 1007 the fact that there is no such information implies that the SIP message is the first message of a new message thread (or the thread existed, but expired).
  • the IWF 30 stores the thread ID, originator's address, and recipient's address in its database and starts a timer with a predefined valid reply period for this thread, and then proceeds to step 1011.
  • the timer and valid reply period give the lifetime of the thread management by the IWF 30. That is, when a message associated with a corresponding thread ID is not received within the valid reply period, the corresponding thread ID and associated address information are deleted. Further, when the thread ID, originator's address, and recipient's address are found, it implies that the SIP message is a follow-up message of an existing message thread.
  • step 1009 when the thread ID, originator's address, and recipient's address are found in the database, the IWF 30 recognizes that the thread is still active, and resets the timer associated with the thread to zero, to extend the lifetime management of the thread. Then, the IWF 30 proceeds to step 1011. In step 1011, the IWF 30 converts the SIP message to an appropriate SM and sends the SM to the SMSC 50 (note that no thread ID is included in the SM). Then, the IWF 30 returns back to step 1000 to wait for any new event.
  • step 1101 the IWF 30 converts the SM to an SIP message.
  • step 1103 the IWF 30 checks if the pair "originator's address - recipient's address" of the SIP message is in its database.
  • the IWF 30 proceeds to step 1105.
  • the IWF 30 When the pair "originator's address - recipient's address" of the SIP message is not in its database, the IWF 30 considers the SIP message is the first message of a new thread or is not associated with the thread, and then proceeds to step 1111.
  • the IWF 30 extracts the thread ID corresponding to the pair of addresses, and then proceeds to step 1107.
  • the IWF 30 includes the extracted thread ID in the SIP message, and then proceeds to step 1109.
  • the IWF 30 resets the timer associated with this thread ID to zero: since a message belonging to an existing thread has arrived, the lifetime of the thread ID is extended in the database so that it can continue to be managed. Then, the IWF 30 proceeds to step 1111, in which the IWF 30 sends the resulting SIP message to the CPM server 20. Then, the IWF 30 returns to step 1000 to wait for a new event.
  • the IWF 30 When an event of expiration of a valid reply period corresponding to a thread ID occurs, the IWF 30 removes the corresponding thread ID, originator's address and recipient's address from the database in step 1201. Then, the IWF 30 returns to Step 1000 to wait for a new event.
  • the present invention provides methods for managing multiple message threads for the CPM service and for the CPM-SMS inter-working.
  • the benefits of the present invention are:

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephone Function (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
EP12189057.8A 2006-11-13 2007-11-13 Method and system for managing message threads in converged ip messaging service Active EP2549695B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
KR20060111783 2006-11-13
PCT/KR2007/005690 WO2008060085A1 (en) 2006-11-13 2007-11-13 Method and system for managing message threads in converged ip messaging service
EP07833997.5A EP2082589B1 (en) 2006-11-13 2007-11-13 Method and system for managing message threads in converged ip messaging service

Related Parent Applications (3)

Application Number Title Priority Date Filing Date
EP07833997.5 Division 2007-11-13
EP07833997.5A Division EP2082589B1 (en) 2006-11-13 2007-11-13 Method and system for managing message threads in converged ip messaging service
EP07833997.5A Division-Into EP2082589B1 (en) 2006-11-13 2007-11-13 Method and system for managing message threads in converged ip messaging service

Publications (2)

Publication Number Publication Date
EP2549695A1 EP2549695A1 (en) 2013-01-23
EP2549695B1 true EP2549695B1 (en) 2018-10-31

Family

ID=39401855

Family Applications (2)

Application Number Title Priority Date Filing Date
EP07833997.5A Active EP2082589B1 (en) 2006-11-13 2007-11-13 Method and system for managing message threads in converged ip messaging service
EP12189057.8A Active EP2549695B1 (en) 2006-11-13 2007-11-13 Method and system for managing message threads in converged ip messaging service

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP07833997.5A Active EP2082589B1 (en) 2006-11-13 2007-11-13 Method and system for managing message threads in converged ip messaging service

Country Status (6)

Country Link
US (4) US20080123686A1 (ja)
EP (2) EP2082589B1 (ja)
JP (3) JP5090459B2 (ja)
KR (1) KR101424810B1 (ja)
CN (2) CN102395115B (ja)
WO (1) WO2008060085A1 (ja)

Families Citing this family (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8804758B2 (en) 2004-03-11 2014-08-12 Hipcricket, Inc. System and method of media over an internet protocol communication
US8831580B2 (en) 2008-08-15 2014-09-09 Hipcricket, Inc. Systems and methods of initiating a call
CN101394365A (zh) * 2007-09-17 2009-03-25 上海华为技术有限公司 一种消息关联方法及用户终端以及服务器
EP2213065A1 (en) * 2007-09-29 2010-08-04 Research In Motion Limited Schema indication system and method in a network environment including ims
US8407299B2 (en) 2007-10-27 2013-03-26 Research In Motion Limited Content disposition system and method for processing message content in a distributed environment
KR101414373B1 (ko) * 2008-02-13 2014-08-06 삼성전자주식회사 통합 메시징 서비스의 인터워킹 방법
WO2009104860A1 (en) 2008-02-22 2009-08-27 Lg Electronics Inc. Terminal and method for storing and retrieving messages in a converged ip messaging service
US8812711B2 (en) * 2008-02-27 2014-08-19 Red Hat, Inc. Three-way communication protocol
WO2009142473A1 (en) * 2008-05-23 2009-11-26 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for message routing in ims and circuit switched networks
US8055710B2 (en) * 2008-09-24 2011-11-08 International Business Machines Corporation System, method and computer program product for intelligent multi-person chat history injection
CN101729434B (zh) * 2008-10-10 2012-05-23 中兴通讯股份有限公司 消息交互的实现方法和融合业务系统
US8060604B1 (en) * 2008-10-10 2011-11-15 Sprint Spectrum L.P. Method and system enabling internet protocol multimedia subsystem access for non internet protocol multimedia subsystem applications
CN101729439B (zh) * 2008-10-23 2011-12-07 中兴通讯股份有限公司 消息处理方法/系统、融合业务系统
KR20100061295A (ko) * 2008-11-28 2010-06-07 삼성전자주식회사 통합 메시징 서비스에서 인터워킹을 위한 세션 제어 방법 및 시스템
WO2010082803A2 (en) * 2009-01-19 2010-07-22 Lg Electronics Inc. Method for delivering message based on cpm service and server thereof
KR101108776B1 (ko) * 2009-01-19 2012-02-24 엘지전자 주식회사 Ｃｐｍ 서비스 메시지의 전달 방법 및 그 서버
WO2010082801A2 (en) 2009-01-19 2010-07-22 Lg Electronics Inc. Method for delivering cpm message and server thereof
KR101055134B1 (ko) * 2009-01-19 2011-08-08 엘지전자 주식회사 메시지 전달 방법
KR101596955B1 (ko) * 2009-02-20 2016-02-23 삼성전자주식회사 통합 인터넷 프로토콜 메시징 시스템에서 세션 트랜스퍼 방법
CN102461095B (zh) * 2009-04-02 2016-03-23 诺基亚通信公司 消息通知
CN101854597B (zh) * 2009-04-03 2015-06-03 中兴通讯股份有限公司 大消息模式融合ip消息传输方法及系统
CN101925023B (zh) 2009-06-16 2014-09-10 中兴通讯股份有限公司 一种向群组传送大消息模式cpm消息媒体链路创建的方法
CN101925017A (zh) * 2009-06-17 2010-12-22 中兴通讯股份有限公司 一种大消息模式融合ip消息的传送方法
US20100325224A1 (en) * 2009-06-17 2010-12-23 Samsung Electronics Co., Ltd. Method and system for managing storing of messages in communication network
WO2011027466A1 (ja) * 2009-09-04 2011-03-10 富士通株式会社 電子機器、メール記録方法及びメール記録プログラム
WO2011040774A2 (en) * 2009-09-30 2011-04-07 Samsung Electronics Co., Ltd. System and method of handling read and delivery confirmations for messages
US8363599B2 (en) 2009-10-07 2013-01-29 Telefonaktiebolaget L M Ericsson (Publ) Method and internet protocol short message gateway (IP-SM-GW) for providing an interworking service between converged IP messaging (CPM) and short message service (SMS)
GB2475702A (en) * 2009-11-25 2011-06-01 Peter Tanner Collating responses sent in response to a message
KR101641542B1 (ko) * 2010-01-15 2016-07-22 삼성전자주식회사 메시지 전송 방법 및 시스템
JP5510056B2 (ja) * 2010-05-17 2014-06-04 富士ゼロックス株式会社 画像形成装置及びプログラム
US8385953B2 (en) 2010-06-23 2013-02-26 At&T Mobility Ii Llc Systems, methods, and computer program products for automatic mapping between parlay-X short messaging service message element XML encoding and native SMPP protocol data coding scheme
US8849322B2 (en) 2010-10-11 2014-09-30 Cox Communications, Inc. Systems and methods for sharing threaded conversations on mobile communications devices
KR20120089782A (ko) * 2010-12-15 2012-08-13 삼성전자주식회사 휴대용 단말의 메시지 관리를 위한 인터페이스 방법
US9819700B2 (en) 2011-05-30 2017-11-14 Telefonaktiebolaget Lm Ericsson (Publ) System and method for passive communication services
US9148397B2 (en) * 2011-12-19 2015-09-29 Facebook, Inc. Messaging object generation for synchronous conversation threads
US9641609B2 (en) * 2012-02-28 2017-05-02 Google Inc. Integrated messaging
US9161187B2 (en) * 2012-05-21 2015-10-13 Alcatel Lucent Caller ID for text messaging
US9232370B2 (en) 2013-02-01 2016-01-05 Mitel Mobility Inc. Enhanced converged IP message server system and method
US9485634B2 (en) * 2013-12-30 2016-11-01 Cellco Partnership Session managed messaging
JP5995220B2 (ja) 2014-07-11 2016-09-21 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ メッセージを処理する装置及び方法
CN105991416B (zh) * 2015-02-15 2019-05-31 无锡北邮感知技术产业研究院有限公司 一种消息传递方法及消息传递中间件
US10706069B2 (en) 2016-06-30 2020-07-07 Facebook, Inc. Techniques for replication of a client database to remote devices
US20180013714A1 (en) * 2016-07-06 2018-01-11 Facebook, Inc. Techniques for messaging using replication of a client database
KR102197881B1 (ko) * 2017-07-12 2021-01-04 주식회사 케이티 연결 메시지 서비스 시스템 및 방법
US11582175B2 (en) * 2017-09-21 2023-02-14 Motorola Solutions, Inc. System, device and method for secure message thread communication
GB201907461D0 (en) * 2019-05-27 2019-07-10 Canon Res Centre France Communication methods and devices in intelligent transport systems
JP7546742B1 (ja) 2023-09-27 2024-09-06 Kddi株式会社 情報処理装置、情報処理方法、及びプログラム

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5444860A (en) * 1992-02-14 1995-08-22 Unisys Corporation Translator system for message transfers between digital units operating on different message protocols and different clock rates
US6856618B2 (en) * 1997-10-21 2005-02-15 Intel Corporation Apparatus and method for computer telephone integration in packet switched telephone networks
JP3687884B2 (ja) 1998-12-04 2005-08-24 日立ソフトウエアエンジニアリング株式会社 メール分類方法およびシステム、記録媒体
KR20010098157A (ko) * 2000-04-28 2001-11-08 박종섭 Ｃｄｍａ 시스템에서의 교환기 및 ｉｗｆ간 ｅ1 채널할당장치 및 그 방법
US8086672B2 (en) * 2000-06-17 2011-12-27 Microsoft Corporation When-free messaging
SE516658C2 (sv) * 2000-07-21 2002-02-12 Ericsson Telefon Ab L M Förfarande och anordning för förbättrade kortmeddelandetjänster
JP2002108782A (ja) * 2000-10-04 2002-04-12 Mitsubishi Electric Corp 電子メール装置
JP2003018660A (ja) * 2001-07-05 2003-01-17 Hitachi Ltd 携帯電話メッセージ処理システム、方法及びこれに用いる装置
US7266591B1 (en) * 2001-12-17 2007-09-04 Verizon Business Global Llc Providing content delivery during a call hold condition
US20040103157A1 (en) 2002-04-17 2004-05-27 Nokia Corporation Store-and-forward server and method for storing and forwarding for instant messaging service implemented in IP multimedia core network subsystem (IMS)
US8150922B2 (en) * 2002-07-17 2012-04-03 Research In Motion Limited Voice and text group chat display management techniques for wireless mobile terminals
US7221739B1 (en) * 2002-11-14 2007-05-22 Bellsouth Intellectual Property Corporation Callback function for messaging platform in public telephone system
KR100899755B1 (ko) * 2003-02-15 2009-05-27 삼성전자주식회사 이동통신 네트워크를 통한 인스턴트 메시지 서비스 방법및 시스템
US7475110B2 (en) * 2004-01-07 2009-01-06 International Business Machines Corporation Method and interface for multi-threaded conversations in instant messaging
US8989737B2 (en) * 2004-03-10 2015-03-24 Nokia Corporation System and method for establishing a session initiation protocol communication session with a mobile terminal
KR100572464B1 (ko) * 2004-04-14 2006-04-18 주식회사 팬택앤큐리텔 통합 메시징 서비스 기능을 가지는 무선통신단말기 및 그방법
JP2005322142A (ja) 2004-05-11 2005-11-17 Takashi Koike 電子メール自動応答システム及びこれを用いたネットオークションシステム
US7715856B2 (en) 2004-06-02 2010-05-11 Interdigital Technology Corporation Reporting terminal capabilities for supporting short message service
US7218943B2 (en) * 2004-12-13 2007-05-15 Research In Motion Limited Text messaging conversation user interface functionality
KR100592882B1 (ko) * 2004-12-13 2006-06-26 한국전자통신연구원 세션 초기화 프로토콜(ｓｉｐ) 기능이 없는 이동 단말에인터넷 프로토콜 멀티미디어 서브시스템을 통한 세션초기화 프로토콜 기반 인스턴스 메시징 서비스 제공방법,시스템 및 이를 위한 인스턴스 메시징 프록시 서버
KR100655554B1 (ko) * 2004-12-21 2006-12-08 엘지전자 주식회사 유니버설 멀티미디어 액세스 시스템
KR100716817B1 (ko) * 2005-01-26 2007-05-09 주식회사 팬택 이동 통신 단말기 호 셋업 방법
US20060167849A1 (en) * 2005-01-26 2006-07-27 Echovox Sa Method and system for mobile instant messaging using multiple protocols
US8315190B2 (en) * 2005-01-28 2012-11-20 Qualcomm Incorporated Method and apparatus for interworking between push-to-talk over cellular (PoC) systems and instant messaging (IM) systems
CN1852267A (zh) * 2005-09-13 2006-10-25 华为技术有限公司 一种不同类型存在系统间的互连方法及互连服务器
US20070156909A1 (en) * 2005-12-29 2007-07-05 Osborn William R Proxy for extending IMS services to mobile terminals with SMS capabilities
US20070168537A1 (en) * 2006-01-18 2007-07-19 Archan Misra Method for intelligent and automated transmission of local context in converged signaling
US8001184B2 (en) * 2006-01-27 2011-08-16 International Business Machines Corporation System and method for managing an instant messaging conversation
US7567785B2 (en) * 2006-05-15 2009-07-28 Intel Corporation Methods and apparatus for a paging mechanism within wireless networks including multiple access points

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
KR101424810B1 (ko) 2014-08-04
EP2549695A1 (en) 2013-01-23
JP2010509835A (ja) 2010-03-25
JP5090459B2 (ja) 2012-12-05
CN102395115B (zh) 2016-05-18
JP2012256330A (ja) 2012-12-27
US20120185552A1 (en) 2012-07-19
US8010616B2 (en) 2011-08-30
US8176134B2 (en) 2012-05-08
JP5565977B2 (ja) 2014-08-06
US8312094B2 (en) 2012-11-13
EP2082589A1 (en) 2009-07-29
EP2082589A4 (en) 2012-04-18
US20110196937A1 (en) 2011-08-11
KR20080043264A (ko) 2008-05-16
US20110060805A1 (en) 2011-03-10
JP2012253783A (ja) 2012-12-20
JP5622802B2 (ja) 2014-11-12
EP2082589B1 (en) 2019-10-30
WO2008060085A1 (en) 2008-05-22
CN101536559A (zh) 2009-09-16
CN102395115A (zh) 2012-03-28
US20080123686A1 (en) 2008-05-29

Similar Documents

Publication Publication Date Title
EP2549695B1 (en) Method and system for managing message threads in converged ip messaging service
KR100824043B1 (ko) 이동 통신 단말의 인스턴트 메시지 전송 방법 및 시스템
EP1599979B1 (en) Message management
EP2082588B1 (en) Method and system for establishing session for message communication between converged ip messaging service client and short messaging service client
US8799373B2 (en) Method, system and apparatus for message interworking
US20100087215A1 (en) Method, system, and message service interworking module for implementing message service interworking
US20090131022A1 (en) Apparatuses and Methods for Anonymous Messaging
US20050193133A1 (en) Message header for messaging service
US20130097331A1 (en) Submit Report Handling In SMSIP
US20120178428A1 (en) Method, device and system for identifying a service
EP2136517B1 (en) Short message delivery
KR20080034072A (ko) Ｓｉｐ기반의 전송 메시지를 이용한 이종 메시지의 전송방법 및 이를 위한 사용자 장치
KR20080030906A (ko) 아이엠에스망에서의 레거시 서비스 메시지의 전송 방법 및이를 위한 사용자 장치
KR101630621B1 (ko) 통합 메시징 서비스 방법, 기계로 읽을 수 있는 저장 매체 및 장치

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20121018

AC Divisional application: reference to earlier application

Ref document number: 2082589

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20171025

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20180705

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AC Divisional application: reference to earlier application

Ref document number: 2082589

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1060724

Country of ref document: AT

Kind code of ref document: T

Effective date: 20181115

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602007056707

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1060724

Country of ref document: AT

Kind code of ref document: T

Effective date: 20181031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190131

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190228

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190301

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190201

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181113

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602007056707

Country of ref document: DE

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20181130

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20190131

26N No opposition filed

Effective date: 20190801

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181231

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181113

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190131

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181113

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181031

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20071113

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602007056707

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012580000

Ipc: H04L0051000000

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20231024

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20231023

Year of fee payment: 17