EP1751999A1 - System und verfahren für zusammenarbeitsmeldungen zwischen monilkommunikationsendgeräten - Google Patents

System und verfahren für zusammenarbeitsmeldungen zwischen monilkommunikationsendgeräten

Info

Publication number
EP1751999A1
EP1751999A1 EP05764864A EP05764864A EP1751999A1 EP 1751999 A1 EP1751999 A1 EP 1751999A1 EP 05764864 A EP05764864 A EP 05764864A EP 05764864 A EP05764864 A EP 05764864A EP 1751999 A1 EP1751999 A1 EP 1751999A1
Authority
EP
European Patent Office
Prior art keywords
message
messaging
messaging service
server
recipient
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.)
Withdrawn
Application number
EP05764864A
Other languages
English (en)
French (fr)
Inventor
Sung-Mu Yangjimaeul hanyang Apt. 516-101 SON
Young-Ae Kim
Kang-Suk Toegye-Jugong Apt. 358-804 HUH
Te-Hyun Dongaecobil Apt. 102-1002 KIM
Hee-Joung Lee
Dong-Hee Shim
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.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
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
Priority claimed from KR1020040025959A external-priority patent/KR100548429B1/ko
Priority claimed from KR1020050007294A external-priority patent/KR100690874B1/ko
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of EP1751999A1 publication Critical patent/EP1751999A1/de
Withdrawn legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18Service support devices; Network management devices
    • H04W88/184Messaging devices, e.g. message centre
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/56Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58Message adaptation for wireless communication

Definitions

  • the present invention relates to a messaging service for a mobile communications terminal, and in particular, to a system and method for interworking messages of a mobile communications terminal that receives multimedia contents transmitted by using an instant messaging (IM) client.
  • IM instant messaging
  • Message services for mobile communication terminals can be broadly divided into instant message (IM) services, multimedia message services (MMS), and short message services (SMS).
  • IM instant message
  • MMS multimedia message services
  • SMS short message services
  • An instant message service generally provides the user of the terminal with highspeed conversation-type communication means, such as text-based messages.
  • the instant message client includes so-called 'presence services' that can notify the user about various operation information, such as the party that is connected with the user, the on-line status of the client, the possibility of replies, and the like.
  • the multimedia message service is a message service that transmits text messages together with videos, combined images, background music, and the like that are desired by the user. However, such transmissions are performed without considering the state (status) of the message recipient.
  • the related art message service system for a mobile communication terminal allows message services between mobile communication terminals having the same message client installed therein, but has the problem of not being able to provide message services between mobile communication terminals having different messages clients installed therein. Disclosure of Invention Technical Problem
  • the present invention provides a system and method that allows interworking (compatibility) among mobile communication terminals that support different types of messaging services, whereby multimedia contents transmitted by using an instant message client can be received by a multimedia message client at the receiving end (e.g., receiving terminal).
  • Technical Solution [8] In order to satisfy the continuing development of mobile and wireless communication technologies, the present invention provides compatibility between user terminals (mobile handsets, wireless access devices, etc.) that have different capabilities and support various types of messaging services such that a user of one type of messaging service may send messages to a user of another type of messaging service.
  • Figure 1 depicts an exemplary structure of a system for mobile communications terminal message service interworking according to the present invention.
  • Figure 2 depicts a block diagram of an exemplary structure of an instant message server according to the present invention.
  • Figure 3 depicts a block diagram of an exemplary structure of a multimedia message service center according to the present invention.
  • Figure 4 depicts a block diagram of an exemplary structure of a mobile core network according to the present invention.
  • Figures 5 and 6 depict flow charts of an exemplary method of interworking mobile communications terminal messages according to the present invention.
  • Figures 7 through 9 depict an exemplary embodiment for checking whether a multimedia message service client of a receiver terminal exists by using an instant message client of a transmitting terminal according to the present invention.
  • Figure 10 depicts a flow of signals of a system for interworking mobile communication terminal messages according to an embodiment of the present invention.
  • Figure 11 and 12 depict structures of the basic architecture of an interworking of messaging services according to embodiments of the present invention.
  • Figure 13 depicts a flow chart of a method for interworking of messaging services according to an embodiment of the present invention.
  • Figure 14 depicts a flow chart of a method for interworking of messaging services according to an embodiment of the present invention using a recipient messaging service field and an originating messaging service field.
  • Figure 15 depicts a signal flow for a method of interworking between respectively different messaging systems in a first embodiment of the present invention.
  • Figure 16 depicts a signal flow for a method of interworking between respectively different messaging systems in a second embodiment of the present invention.
  • Figure 17 depicts a signal flow for a method of interworking between respectively different messaging systems in a third embodiment of the present invention.
  • Figure 18 depicts a signal flow for a method of interworking between respectively different messaging systems in a fourth embodiment of the present invention.
  • Figure 19 depicts a signal flow for a method of interworking between respectively different messaging systems in a fifth embodiment of the present invention.
  • Figure 20 depicts a signal flow for a method of interworking between respectively different messaging systems in a sixth embodiment of the present invention.
  • Figure 21 depicts a format of a message having a recipient messaging service field and an originating messaging service field according to the present invention.
  • Figure 22 depicts an example of a SIP message header format according to the present invention.
  • Figure 23 depicts an example of a RTP message header format according to the present invention.
  • Figure 24 depicts an example of a RTCP message header format according to the present invention.
  • the present invention provides a system for interworking messages of a mobile communication terminal in which a transmitting terminal having a first message client installed therein for transmitting multimedia contents to a receiving terminal having a second message client installed therein, the system comprises, a first server that checks whether the multimedia contents can be transmitted to the receiving terminal; a second server that converts a format of the multimedia contents transmitted from the first server into a contents format supported by the receiving terminal; and a mobile core network that collects information related to the terminals, and provides information requested by the first server, the second server, and each terminal
  • a system for mobile communication terminal message interworking comprises, a transmitting terminal that transmits multimedia contents by using a first message client; a receiving terminal that receives the multimedia contents by using a second message client; a first server that checks the receiving address of the multimedia contents and checks a message client installed in the receiving terminal; a second server that converts a format of the multimedia contents transmitted from the first server into a format supported by the receiving terminal and that transmits the multimedia contents upon request from the receiving terminal; and a mobile core network that collects information related to the terminals, and provides information requested by the first server, the second server, and each terminal.
  • a method for mobile communication terminal message interworking according to the present invention comprises, determining a path for transmitting multimedia contents according to a service supported by a message client installed in a receiving terminal; and transmitting to the receiving terminal upon converting the multimedia contents into a format that is supported by the receiving terminal.
  • a method for mobile communication terminal message interworking comprises, transmitting multimedia contents to a first server upon activating a first message client installed in a transmitting terminal; checking an address of a receiving terminal and a second message client installed in the receiving terminal; informing from a second server, reception of the multimedia contents of the receiving terminal; converting a format of the multimedia contents into a contents format supported by the receiving terminal, upon transmission of a reception request from the receiving terminal; and transmitting the multimedia contents to the receiving terminal.
  • Figure 1 depicts an exemplary structure of a system for mobile communications terminal message service interworking according to the present invention, whereby the system is for interworking between an instant message service terminal and a multimedia message service terminal.
  • the system comprises a transmitting terminal (10) that stores and transmits multimedia contents formed by a user; an instant message server (20) that checks whether the multimedia contents transmitted from the transmitting terminal (10) can be transmitted to a receiving terminal (50); a multimedia message service (MMS) center (30) that checks a format and codec of the multimedia contents transmitted from the instant message server (20) and converts such into a contents format supported by the receiving terminal (50); a WAP gateway (40) that notifies the receiving terminal (50) when the multimedia contents are inputted to the multimedia message service center (30); a receiving terminal (50) that requests the notified multimedia contents from the multimedia message service center (30) through the WAP gateway (40), and receives the requested multimedia contents through the WAP gateway (40); and a mobile core network (60) that performs authentication and authorization, and performs periodic or non-periodic updating of information from the transmitting terminal (10) and the receiving terminal (50).
  • the instant message server (20) is a first server for processing instant messages
  • the multimedia message service center that checks a format and code
  • the transmitting terminal (10) is a mobile communication terminal having an instant message client installed therein
  • the receiving terminal (50) is a mobile communication terminal having a multimedia message service client (and not an instant message client) installed therein.
  • the instant message server (20) allows transmission of multimedia contents upon request from the transmitting terminal (10), and checks the information stored in the mobile core network (60) to determine whether the receiving terminal (50) to which the multimedia contents are to be transmitted has an instant message client or a multimedia message service client installed therein.
  • FIG. 2 depicts a block diagram of an exemplary structure of an instant message server according to the present invention, comprising a transceiving module (21) that receives multimedia contents and the like transmitted from the transmitting terminal (10) and transmitting such to a different server; a receiving terminal checking module (23) that performs addressing resolution for the destination of the multimedia contents to be transmitted and checks from the mobile core network (60) as to whether the receiving terminal (50) has a multimedia message server client installed therein; and a storage module (25) that temporarily stores the multimedia contents transmitted from the transmitting terminal (10).
  • a transceiving module (21) that receives multimedia contents and the like transmitted from the transmitting terminal (10) and transmitting such to a different server
  • a receiving terminal checking module that performs addressing resolution for the destination of the multimedia contents to be transmitted and checks from the mobile core network (60) as to whether the receiving terminal (50) has a multimedia message server client installed therein
  • a storage module (25) that temporarily stores the multimedia contents transmitted from the transmitting terminal (10).
  • the multimedia message service center (30) determines whether the format/codec of the multimedia contents received from the instant message server (20) is supported by the receiving terminal (50). If the format/codec of the multimedia contents is supported, the multimedia contents are not converted but transmitted directly to the receiving terminal (50), but if the format/codec of the multimedia contents is not supported, the multimedia contents are converted to a format/codec that is appropriate for the receiving terminal (50) and then transmitted.
  • FIG. 3 depicts a block diagram of an exemplary structure of a multimedia message service center according to the present invention comprising, a transceiving module (31) that receives multimedia contents from the instant message server (20) and transmits the multimedia contents that have been appropriately converted for the receiving terminal (50) to a different server or to the receiving terminal (50); a notification module (33) that notifies reception of the multimedia contents to the receiving terminal (50); a storage module (35) that temporarily stores the received multimedia contents; and a conversion module (37) that checks the format/codec of the received multimedia contents and converts the multimedia contents according to the capabilities of the receiving terminal (50).
  • a transceiving module (31) that receives multimedia contents from the instant message server (20) and transmits the multimedia contents that have been appropriately converted for the receiving terminal (50) to a different server or to the receiving terminal (50)
  • a notification module (33) that notifies reception of the multimedia contents to the receiving terminal (50)
  • a storage module (35) that temporarily stores the received multimedia contents
  • a conversion module (37) that checks
  • the mobile core network (60) is a generic user profile (GUP) server of the 3GPP TS 23.240, that employs a simple mail transfer protocol (SMTP) for exchanging information with the instant message server (20) and the multimedia message service center (30).
  • GUP generic user profile
  • SMTP simple mail transfer protocol
  • the mobile core network is defined in the wireless village interpersonal messaging system (IMPS) of the Open Mobile Alliance (OMA) standard.
  • FIG. 4 depicts a block diagram of an exemplary structure of a mobile core network according to the present invention, comprising a transceiving module (61) that receives information request signals from the instant message server (20) or the multimedia message service enter (30) or a terminal, or transmits certain information; an authentication module (63) that performs authentication and authorization for each comprising element of the system or for each subscriber; a database (65) that stores and periodically or non-periodically updates user terminal service subscription information, user profile information, presence information, access rights information, and the like; and a home location register (HLR) (67) that manages network information of the terminal.
  • a transceiving module (61) that receives information request signals from the instant message server (20) or the multimedia message service enter (30) or a terminal, or transmits certain information
  • an authentication module (63) that performs authentication and authorization for each comprising element of the system or for each subscriber
  • a database (65) that stores and periodically or non-periodically updates user terminal service subscription information, user profile information, presence information,
  • the instant message server (20) checks the address of the destination to which the multimedia contents are to be transmitted, and upon performing addressing resolution, checks whether the receiving terminal 950) has a multimedia message service client (and not an instant message client) installed therein, and then transmits the multimedia contents to the multimedia message service center (30).
  • the multimedia message service center (30) checks the format/codec of the transmitted multimedia contents, to determine whether the receiving terminal (50) supports that format/codec. If the format/codec of the multimedia contents are of the type that is supported by the receiving terminal (50), the multimedia contents are not converted but transmitted directly to the receiving terminal (50), and if not the type supported by the receiving terminal (50), the multimedia contents are converted to a type that is supported by the receiving terminal (50) and then transmitted.
  • the multimedia contents are transmitted to the receiving terminal (50) through the WAP gateway (40), and the recipient may check the contents of the transmitted multimedia contents by using the multimedia message service client installed in the receiving terminal (50).
  • the receiving terminal (50) can receive the multimedia contents transmitted by a transmitting terminal (10) that uses an instant message client.
  • the transmitting terminal (10) and the instant message server (20) receive from the mobile core network (60), information that the receiving terminal (50) does not have an instant message client installed therein, but only has a multimedia message service client installed therein.
  • Figures 5 and 6 depict flow charts of an exemplary method of interworking mobile communications terminal messages according to the present invention.
  • the sender activates the instant message client installed in the transmitting terminal (10) and checks the message client installed in the receiving terminal (50) (Sl l).
  • the transmitting terminal (10) has installed therein, the same instant message client as that in the receiving terminal (50) or has only a multimedia message service client (that is not an instant message client) installed therein, or has both an instant message client and a multimedia message client installed simultaneously therein.
  • the transmitting terminal (10) has an instant message client installed therein and the receiving terminal (50) has a multimedia message service client installed therein.
  • the multimedia contents are transmitted to the receiving terminal (50) (S12).
  • the transmitting terminal (10) can inform the sender that such contents cannot be sent. This is because the multimedia message service client installed in the receiving terminal (50) can only receive multimedia contents, and thus if the sender attempts to transmit other types of contents, the transmitting terminal (10) can generate an alarm to inform the sender.
  • the instant message server (20) that received the multimedia contents checks the address of the receiving terminal (50) (S13), receives the information of the receiving terminal (50) provided from the mobile core network (60), and then checks whether only a multimedia message service client is installed in the receiving terminal (50) (S14).
  • the instant message server (20) Upon determining whether an instant message client is installed in the receiving terminal (50) (S15), if an instant message client is not installed but only a multimedia message service client is installed, the instant message server (20) transmits the multimedia contents to the multimedia message service center (30) (S16). [56] If an instant message client is installed in the receiving terminal (50), the multimedia contents are transmitted to the receiving terminal (50) through the WAP gateway (40) (S17), and if both an instant message client and a multimedia message service client are installed in the receiving terminal (50), the multimedia contents are transmitted according to the user's selection or network settings (SI 8). Here, it is determined whether the multimedia contents are to be transmitted to the instant message client or to the multimedia message service client according to the user's selection or the network settings.
  • the multimedia message service center (30) temporarily stores the multimedia contents, and informs the receiving terminal (50) through the WAP gateway (40) by transmitting a short message to indicate that the multimedia contents were received (S19).
  • the request signal is transmitted to the multimedia message service center (30) via the WAP gateway (40) (S20).
  • the multimedia message service center (30) receiving the request signal checks whether the format/codec of the multimedia contents are supported by the receiving terminal (50) (S21).
  • the receiving terminal (50) If the format/codec of the multimedia contents are not supported by the receiving terminal (50), the contents are converted into a contents format that is supported by the receiving terminal (50) (S22), and if the format/codec are supported, then the format of the multimedia contents are not converted.
  • the multimedia message service center (30) transmits the multimedia contents that have or have not been converted to the receiving terminal (50) via the WAP gateway (40) (S23).
  • the receiving terminal (50) that receives the multimedia contents transmits to the transmitting terminal (10), a delivery report signal indicating that the contents have been received (S24).
  • FIGs 7 through 9 depict an exemplary embodiment for checking whether a multimedia message service client of a receiver terminal (50) exists by using an instant message client of a transmitting terminal (10) according to the present invention.
  • Special characters such as subscripts or superscripts, or colors may be used to distinguish users (receiver terminals).
  • each icon displayed on the instant message client refers to a recipient or receiving terminal (50).
  • Figure 7 depicts an example in which the on-line or off-line states of receiving terminals (50) that have an instant message client installed therein, and those receiving terminals (50) that do not have an instant messaging client installed therein can be indicated in different colors. Also, among the receiving terminals (50) that do not have an instant message client installed therein, those that have a multimedia message service client installed therein can be indicated with a letter 'm' to indicate that multimedia message service would be possible with that terminal.
  • Figure 8 depicts an example in which the on-line or off-line states of receiving terminals (50) that have an instant message client installed therein are indicated in different colors, and the receiving terminals (50) that do not have an instant message client installed therein are indicated in the same color as those receiving terminals (50) having an instant message client therein but that are in off-line state. Also, among the receiving terminals (50) that do not have an instant message client installed therein, those that can support a multimedia message service can be indicated with a letter 'm' to indicate that multimedia message service would be possible with that terminal.
  • Figure 9 depicts an example in which the instant message client employs special characters (such as subscripts) to distinguish various types of services supported by the receiving terminal (50), such as multimedia message services, instant message services, location services, and the like.
  • the n-line and off-line states for the instant service are distinguished by different colors, and the receiving terminals (50) the can support multimedia message service can have a subscript 'm' added thereto to indicate that multimedia message service is possible.
  • the subscript 'm' can be added to all receiving terminals that can support multimedia message services regardless of the online or off-line states of their instant message clients.
  • a method for checking whether or not a multimedia message client is installed in a receiving terminal in addition to the method of checking the colors or subscripts of the icons as described above, a method of checking the registration information of the corresponding icons in the receiving terminal may also be used. Namely, because the icons also contain registration information that includes information about the message client installed in the corresponding receiving terminal, the user can select a certain icon to check its registration information in order to check whether the receiving terminal has a multimedia message client installed therein.
  • Figure 10 depicts a flow of signals of a system for interworking mobile communication terminal messages according to the present invention.
  • the instant message server (20) that received the multimedia contents from the transmitting terminal (10) transmits a multimedia contents transmit signal (ForwardMessage.Req) to the multimedia message service center (30), and receives a response signal (ForwardMessage.Res) with respect to the transmit signal from the multimedia message service center (30) (A20).
  • the multimedia service center (30) that received the multimedia contents from the instant message server (20) transmits a notification signal (MessageNotification.Req) to the receiving terminal (50) to indicate that the multimedia contents have been received, and receives a response message (MessageNotification.Res) with respect to the notification signal (A30).
  • the receiving terminal (50) that received the notification signal transmits a multimedia contents request signal (GetMessage.Req) to the multimedia message service center (30), and receives a response signal (GetMessage.Res) that includes the multimedia contents (A40).
  • a multimedia contents request signal GetMessage.Req
  • a response signal GetMessage.Res
  • the receiving terminal (50) receiving the multimedia contents stored in the multimedia message service center (30) transmits a transmit complete signal (MessageDelivered) to the multimedia message service center (30) (A50), which then transmits a transmit report signal (Deli very Report. Req) to the instant message server (20).
  • a transmit complete signal MessageDelivered
  • A50 multimedia message service center
  • a transmit report signal Deli very Report. Req
  • the instant message server (20) the received the transmit report signal transmits a response signal (Deli very Report. Res) to the multimedia message service center (30) (A60), and transmits to the transmitting terminal (10) a transmit report signal (DeliveryReport.Req) that indicates the completion of the multimedia contents transmission (A70).
  • Figure 11 depicts a structure of a basic architecture of an interworking of messaging services according to the present invention.
  • a block diagram of the logical entities that may comprise the interworking of different messaging services is shown, and the details of each entity will be described.
  • the (inter-service) messaging relay is a logical entity responsible for the transfer of a message between two messaging services. Such responsibilities include, identifying the target messaging service based upon the address-resolution and recipient user-profile, conversion of the message format to he accepted format of the recipient messaging service, and producing the proper billing records for he transfer to the target messaging service.
  • the MR interfaces with the different messaging servers (and may be implemented as part of a messaging server) to transfer the message information (both content and 'envelope') between different services.
  • it interfaces to he basic enablers for address resolution, accessing the user-profile, and receiving and storing he message in persistent storage.
  • the MR is responsible for various functionalities, including the support of varied protocols such as (but not exclusively) MM4, MM7, SMTP, various SIP-based protocols, etc.; and accepting messages to be transferred to a different messaging server, wherein the message may either be supplied explicitly or be accessed through a link to network storage.
  • Other responsibilities include identifying the target messaging service, which may be supplied explicitly by the originating messaging service or ascertained from the recipient's user-profile; performing message conversion and adaptation to render in the target messaging service formats; maintaining the message in persistent storage until the message has been successfully delivered to the target messaging service; managing the forwarding of delivery and read reports that may be routed back from the recipient messaging service to the originator of the message upon request and where supported by both the originating and recipient messaging services; and maintaining the privacy and security of the messaging services.
  • the address resolution is a logical entity responsible for completion of the abbreviated address to be a fully qualified address according to the address format used by the destination messaging service.
  • the AdR is an interface between a messaging server or the messaging relay (MR) and the address book that allows the expansion of a given recipient address to the fully qualified address that identifies the recipient messaging service and destination server for the message delivery.
  • the interface should support the input of any address format, including shortened 'nicknames' and an indication of the desired format of fully qualified format, and return the fully qualified address or an indication that no such address is available for the supplied input.
  • the user profile is a logical entity that defines certain information that should be defined within the profile of users that subscribe to messaging services and should be accessible to the messaging servers and the messaging relay (MR).
  • the user profile provides both an interface between the messaging server (or MR) and the database of user information within the operator's domain as well as a specified set of user parameters that indicate a minimal set of attributes.
  • the attributes should include at least certain types of information, such as a list of messaging services that the user is subscribed to, a list of 'preferred' messaging services that the user would define to receive different media types, and basic messaging parameters.
  • the content & header transcoding is a logical entity that provides services of transcoding either the content of a message or a header formats between the formats of different messaging services.
  • the transcoding services provide services to the messaging server or the MR to perform adaptation of the content and message format. This may be supported by an extended version of the Standard Transcoding Interface (STI). Extensions should allow transformation of header information and not only the content information that is currently supported.
  • STI Standard Transcoding Interface
  • the message store is a logical entity that provides persistent storage of messages in the network that may be accessed by the messaging servers and the messaging relay (MR) to store and retrieve the message being sent.
  • the message storage provides persistent storage for messages that should be accessible across all messaging services provided by the operator.
  • the message storage should provide an interface that allows storage of messages in various formats (e.g., e-mail, multimedia messages (MM), short message service (SMS), etc.), generation of URI for the messages, retrieval and replacement of the message in the storage based on a URI, and management of the storage by the messaging servers or the MR.
  • Figure 12 depicts a structure of a basic architecture of an interworking of messaging services according to the present invention. Like in Figure 11, a block diagram of the logical entities that may comprise the interworking of different messaging services and the interfaces (reference points) therebetween are shown, but the details of the different features will be explained.
  • the sending side and the receiving side of Figure 12 and the originating side and the recipient side of Figure 11 respectively have equivalent logical entities.
  • the sending messaging service interworking server and the receiving messaging server in Figure 12 respectively correspond to the recipient originating service message server and the recipient 'preferred' service messaging server in Figure 11.
  • the originating messaging server and the sending messaging service interworking server may be part of the same logical entity. Namely, a single server may serve the functions of both servers, as indicated by the dotted lines in Figure 12.
  • the address resolution and message store in Figure 11 respectively correspond to the address converter and message storage in Figure 12.
  • the presence server in Figure 11 cooperates with the originating messaging server and the recipient originating service messaging server, while the presence server in Figure 12 cooperates with the originating client and the originating messaging server.
  • the message store is connected to the inter-service messaging relay and the recipient 'preferred' service messaging server, while in the receiving side of Figure 12, the message storage is connected with the sending messaging service interworking server, the messaging relay, and the receiving messaging server.
  • Figure 13 depicts a flow chart of a method for interworking of messaging services according to the present invention.
  • the present invention also provides a method of interworking between different messaging systems, the method comprising: sending by a terminal to an originating messaging server, a message including recipient preferred messaging service type; receiving the message by a recipient originating service messaging server; and sending a transcoded message to a recipient preferred service messaging server, by considering the received message including recipient preferred messaging service type, without checking any other network entity to get information about the recipient preferred messaging service type.
  • the transcoded message is sent to a recipient preferred service messaging server, without having to check other network entities such as a user profile to find the recipient preferred messaging service type, because only the received message including recipient preferred messaging service type needs to be considered.
  • the step of sending the message including recipient preferred messaging service type further comprises the steps of performing address resolution, checking a user profile, and storing the message prior to sending. Also, the step of sending the transcoded message further comprises a step of converting the received message having a first format into a second format to allow compatibility between different types of messaging services. Additionally, the originating messaging server receives from a presence server, state information and possible service applications related to a recipient terminal prior to sending the message including recipient preferred messaging service type.
  • the present invention provides a method of interworking between different messaging systems, the method comprising: receiving a message related to a messaging service; obtaining preferred messaging service type of a recipient; inserting in the received message, at least one parameter related to the obtained preferred messaging service type; and sending the received message having the parameter inserted therein to a recipient originating service messaging server.
  • This method can further comprise a step of finding a destination messaging system which the received message should be routed to, wherein the preferred messaging service type is obtained from a presence server or a user profile, wherein the at least one parameter is for sending or receiving a message of the preferred messaging service, and wherein the at least one parameter includes one parameter for sending a message of the preferred messaging service and another parameter for receiving a message of the preferred messaging service.
  • the present invention provides a method of interworking between different messaging systems, the method comprising: receiving a message having a parameter therein that indicates a preferred messaging service type; processing the message according to the parameter into a format supported by the preferred messaging service; and providing the message to a recipient of the preferred messaging service.
  • the message can be received by a recipient originating service messaging server in a format that is different from the format of the preferred messaging service; and the processing step can include a step of performing address resolution; and the messages can be processed via a messaging relay for checking of a user profile, performing content and header transcoding, and storing the messages; and the messages can be provided to the recipient via a recipient preferred service messaging server.
  • the present invention provides a messaging service method, comprising: sending a message from an originating client to an originating messaging server; storing the message in a message storage; obtaining user information through a presence server or a user profile, wherein the information contains at least a preferred messaging service type; finding a next server through address resolution; sending the message to the next server; transcoding an originating message format into a recipient message format; finding a recipient preferred service messaging server through address resolution; sending the transcoded message to the recipient preferred service messaging server; storing the transcoded message and sending a notification to the recipient client; requesting to receive the transcoded message to the recipient preferred service messaging server; and receiving the transcoded message.
  • the present invention provides a messaging service method comprising: receiving by a first messaging service server, a multimedia message sent by a first user client of a first messaging service; processing the multimedia message at the first messaging service server and at a second messaging service server; and providing by the second messaging service server, the processed multimedia message to a second user client of a second messaging service.
  • the processing can modify the contents or the format of the multimedia message to allow compatibility between the first and second messaging services, and wherein the first messaging service is an instant message service and the second messaging service is a multimedia message service.
  • the processing can check whether a messaging address is available for the second user client, and wherein the first messaging service is a multimedia message service and the second messaging service is an instant message service.
  • the first user client can have a functionality to indicate possible service applications and presence information to the user, and wherein the possible service applications and presence information can be indicated as a visual display provided to a user by employing different colors and text characters. !
  • Figures 14 through 24 depict more specific embodiments of the present invention that pertain to the interworking by using parameters (e.q., header fields) to indicate either the originating (sending) messaging service type or the recipient (receiving) messaging service type or both.
  • parameters e.q., header fields
  • parameters refer to using the reserve bits of the fields in the header portion of a message to specify the originating (sending) and/or the recipient (receiving) messaging service types. This 'adding' of a new field does not actually increase the overall size of the header, but one or more bits that were previously reserved in the related art are used as a new field to indicate the messaging service type.
  • the parameters can be added by the originating client, the originating messaging server, or the recipient originating service messaging server, to be described in more detail below.
  • Figure 14 depicts a flow chart of a method for interworking of messaging services according to an embodiment of the present invention using a recipient messaging service field and an originating messaging service field.
  • a field indicating the messaging service type is added and the message is transmitted (Sl l), the messaging relay receives this message (S13) and checks whether a type of messaging service field is included in the message.
  • a recipient messaging service field and/or an originating messaging service field may be included in the message.
  • such fields are included into the message by the originating client or the originating messaging server or the originating messaging service interworking server.
  • the messaging relay first checks whether the message contains a recipient messaging service field (S15). If not, the messaging relay checks the messaging service type desired to be received by the recipient client by referring to the user profile (S17).
  • the messaging relay converts (changes) the message via the transcoding unit into a message format that is supported at the recipient client (S19). Then, the messaging relay converts the address of the message via the address converter into an address format that is used by the recipient messaging server and also checks the address of the next destination (S21). The address converted message is then transmitted to the recipient messaging server, which transmits the me ssage to the recipient client (S23).
  • the recipient client checks to see whether an originating messaging service field exists (S25). If so, the recipient client can check the messaging service type of the originating client (S27), otherwise, the recipient client cannot perform such checking (S29). If checking can be performed, the recipient client may then transmit a reply message in response to the received message.
  • the originating (sending) side that receives such reply (response) can then convert the messaging service format without having to check the user profile by the messaging relay. However, if an originating messaging service field does not exist, the messaging service format needs to be converted after referring to the user profile that would contain information regarding the originating messaging service type.
  • Figure 15 depicts a signal flow for a method of interworking between respectively different messaging systems in a first embodiment of the present invention, in which the originating client inserts the recipient messaging service field.
  • the originating client checks from a presence server, the messaging service that is set at the recipient client for reception (S31), and a recipient messaging service field is included with the message (S33).
  • the recipient messaging service field is a field that indicates the type of messaging service that can currently be received by the recipient client. This can be achieved by setting one or more reserve bits in the header portion or body portion of the message, or using an indication in another portion of the message.
  • the message with the recipient messaging service field is then transmitted to the originating messaging server (OM1).
  • the originating messaging server stores the received message in a message store (storage) (IM5) and checks the user profile for the information necessary in transmitting the message (IM3), and then checks the address book to determine the address of the next destination to which the message is to be sent (IM2). Then, the originating messaging server retrieves the message from the message storage (IM5) and transmits it to the originating messaging service interworking server (IMCN).
  • IM5 message store
  • IM3 the user profile for the information necessary in transmitting the message
  • IM2 the address book to determine the address of the next destination to which the message is to be sent
  • the originating messaging server retrieves the message from the message storage (IM5) and transmits it to the originating messaging service interworking server (IMCN).
  • IMCN originating messaging service interworking server
  • the originating messaging server and the originating messaging service interworking server may be part of a single server or may be separate servers.
  • the originating messaging service interworking server cooperates twith the address converter to check the next destination address of the message (IM2) and sends the message to the messaging relay for performing message service interworking (IMl).
  • the address converter can perform the same functions as those of the address book in the originating side.
  • the messaging relay checks the type of messaging service at the recipient client by referring to the recipient messaging service field of the message and then converts the messaging service format to be appropriate for the recipient client via the transcoding unit (IM4) If necessary (as shown by the dotted arrow line), the messaging relay may check the user profile for additional information of the recipient client other than the messaging service type (IM3).
  • IM4 transcoding unit
  • the messaging relay cooperates with the address converter to convert the address of the recipient client included in the message into an address format that is used by the messaging service of the recipient client, and checks the address of the next destination to which the converted message should be transmitted to (IM2).
  • the messaging relay transmits the converted message to the recipient messaging server (IMl).
  • the messaging relay may temporarily store a copy of the message until the message is successfully transmitted to the recipient messaging server.
  • the copy of the message may be stored within the messaging relay itself or in a separate storage means.
  • the recipient messaging server stores the received message in a message storage of the recipient messaging server (IM5), and uses a notification message to notify the recipient client that a message has arrived (S35).
  • IM5 message storage of the recipient messaging server
  • S35 notification message
  • the message storage may be an internal part of the recipient messaging server or a separate entity.
  • the recipient client Upon checking the notification message, the recipient client requests reception of the message (S37), then the recipient messaging server requests the message from the message storage (IM5), the message storage allows the message to b sent to the recipient messaging server (IM5) which then transmits the message to the recipient client (RM1).
  • a message from the originating client that uses a certain type of messaging service can be properly transmitted to the desired recipient client that uses another type of messaging service, whereby one or more messaging service parameters (e.g., fields, flags, etc.) are used to improve the signal flow among various network entities.
  • one or more messaging service parameters e.g., fields, flags, etc.
  • the above procedures may be performed in a sequence that is slightly different than that as shown, if such would be necessary or more desirable. Examples of such are shown hereafter.
  • Figure 16 depicts a signal flow for a method of interworking between respectively different messaging systems in a second embodiment of the present invention, in which the originating messaging server inserts the recipient messaging service field.
  • the originating client does not perform steps S31 and S33 of Figure 15. Instead, the originating messaging server can check from a presence server, the messaging service that is set at the recipient client for reception (shown by the dotted arrow line before checking the address book to determine the address of the next destination to which the message is to be sent (IM2)), and the originating messaging server includes a recipient messaging service field with the message (S41). All other subsequent steps may be the same as those in Figure 15.
  • Figure 17 depicts a signal flow for a method of interworking between respectively different messaging systems in a third embodiment of the present invention, in which the originating messaging service interworking server inserts the recipient messaging service field.
  • the originating messaging server checks the user profile for the information necessary in transmitting the message (IM3), the originating messaging server first retrieves the message from the message storage (IM5), then checks the address book to determine the address of the next destination to which the message is to be sent (IM2), and then transmits the message to the originating messaging service interworking server (IMCN).
  • IM3 the message storage
  • IM2 the address book to determine the address of the next destination to which the message is to be sent
  • IMCN originating messaging service interworking server
  • the originating messaging service interworking server can store the message into a message storage in the recipient side (IM5), and the recipient client messaging service can be checked from the user profile (IM3). Then, the originating messaging service interworking server cooperates with the address converter to check the next destination address of the message (IM2), retrieve the message form the message storage (IM5), and add a recipient messaging service field to the message (S51). All other subsequent steps may be the same as those in Figures 15 or 16.
  • FIG. 18 depicts a signal flow for a method of interworking between respectively different messaging systems in a fourth embodiment of the present invention, in which the originating messaging server inserts the originating messaging service field.
  • All of the procedures can be the same as those in Figure 15, except that the originating client adds an originating messaging service field into the message (S61) prior to performing any other steps, and the recipient client can check the type of originating messaging service (S67) at the end of the procedures. Also, instead of obtaining messaging service information of the recipient client from the presence server (S31) and the optional step of referring to the user profile at the recipient side (IM3) of Figure 15, a presence server is not used and thus the messaging service information of the recipient client can be obtained by the messaging relay from the user profile at the recipient side (IM3).
  • Figure 19 depicts a signal flow for a method of interworking between respectively different messaging systems in a fifth embodiment of the present invention, in which the originating messaging server inserts the originating messaging service field.
  • the originating messaging server adds an originating messaging service field to the message (S71) after performing the five initial steps (OM1, IM5, IM3, IM2, IM5) but before the step of transmitting the message (having the originating messaging service field) to the originating messaging service interworking server (IMCN).
  • IMCN originating messaging service interworking server
  • Figure 20 depicts a signal flow for a method of interworking between respectively different messaging systems in a sixth embodiment of the present invention, in which the originating messaging service interworking server inserts the originating messaging service field.
  • the originating messaging service interworking server adds an originating messaging service field to the message (S81) after receiving the message from the originating messaging server (IMCN) and cooperating with the user profile (IM3) and the address converter (IM2). All subsequent steps may be the same as those in Figure 19.
  • Figure 21 depicts a format of a message having messaging service fields according to the present invention.
  • a recipient messaging service field and a originating messaging service field may be optionally included in the header portion of a message.
  • the recipient messaging service field and the originating messaging service field may be optionally included in other portions of a message, besides the header.
  • FIG. 22 depicts an example of a portion of a Session Initiation Protocol (SIP) message header format according to the present invention.
  • SIP Session Initiation Protocol
  • the SIP is used during a session configuration (set up) procedure for providing services of multimedia data in real-time.
  • an invitation message IV, INVITE
  • an option field OPT, Option Field
  • MESSAGE a header field of the message
  • FIG. 23 depicts an example of a format for a Real-Time Protocol (RTP) message header used in transmitting multimedia data in real-time according to the present invention.
  • RTP Real-Time Protocol
  • Figure 24 depicts an example of a format for a Real-time Transport Control Protocol (RTCP) message header used in controlling an RTP protocol according to the present invention.
  • RTCP Real-time Transport Control Protocol
  • length (size) of the originating messaging service field and the recipient messaging service field to be added to the RTP or RTCP may be variably adjusted accordingly.
  • the system and method of interworking mobile communication terminal messages according to the present invention has the effect of allowing compatibility between different messaging systems, such as an instant messaging client and a multimedia messaging service client, such that multimedia contents transmitted by using a transmitting terminal having an instant message client installed therein can be received by a receiving terminal having a multimedia message service client installed therein.
  • the system and method of interworking mobile communication terminal messages according to the present invention has the effect of allowing a sender to use the instant message client installed in his transmitting terminal to check whether certain recipients can receive multimedia message services. Furthermore, by adding an originating messaging service field and/or a recipient messaging service field to the message, the procedures needed for verifying the messaging service type can be advantageously minimized and the signal traffic between network entities can be advantageously reduced. Also, the recipient client can be aware of the messaging service type used at the originating client in order to perform interworking of different messaging services.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
EP05764864A 2004-04-14 2005-04-14 System und verfahren für zusammenarbeitsmeldungen zwischen monilkommunikationsendgeräten Withdrawn EP1751999A1 (de)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US56191804P 2004-04-14 2004-04-14
KR1020040025959A KR100548429B1 (ko) 2004-04-14 2004-04-14 이동통신 단말기 메시지의 호환을 위한 시스템 및 방법
US56460904P 2004-04-23 2004-04-23
KR1020050007294A KR100690874B1 (ko) 2004-04-23 2005-01-26 서로 다른 메시징 서비스의 상호연동 방법
PCT/KR2005/001085 WO2005117469A1 (en) 2004-04-14 2005-04-14 System and method of interworking messages between mobile communication terminals

Publications (1)

Publication Number Publication Date
EP1751999A1 true EP1751999A1 (de) 2007-02-14

Family

ID=35451287

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05764864A Withdrawn EP1751999A1 (de) 2004-04-14 2005-04-14 System und verfahren für zusammenarbeitsmeldungen zwischen monilkommunikationsendgeräten

Country Status (4)

Country Link
EP (1) EP1751999A1 (de)
JP (1) JP2007533245A (de)
MX (1) MXPA06011967A (de)
WO (1) WO2005117469A1 (de)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7257583B2 (en) * 2004-01-09 2007-08-14 Microsoft Corporation System and method for updating an on-device application catalog in a mobile device receiving a push message from a catalog server indicating availability of an application for download
JP4887779B2 (ja) 2005-12-28 2012-02-29 ソニー株式会社 情報処理装置および情報処理方法、プログラム、並びに、記録媒体
EP2087746B1 (de) 2006-11-13 2014-02-26 Samsung Electronics Co., Ltd. System und verfahren zur bereitstellung eines konvergierten nachrichtenübermittlungsdienstes
US8311046B2 (en) 2006-11-28 2012-11-13 Core Wireless Licensing S.A.R.L. Method for the delivery of messages in a communication system
WO2008067654A1 (en) * 2006-12-05 2008-06-12 Nortel Networks Limited Method and system for communicating between devices
CN101227418B (zh) * 2007-01-19 2012-04-04 华为技术有限公司 一种实现融合ip消息的方法、装置及系统
CN101291297A (zh) * 2007-04-19 2008-10-22 华为技术有限公司 网络、能力中心实体、互通功能实体及消息通知方法
WO2017045033A1 (en) * 2015-09-16 2017-03-23 Giftmobile Pty Ltd System and method for generating a personalised mms messsage having a redeemable component
CN112311654A (zh) * 2019-07-29 2021-02-02 腾讯科技(深圳)有限公司 即时通讯消息的处理方法、装置、介质及电子设备
KR102245250B1 (ko) * 2020-01-03 2021-04-27 주식회사 카카오 메시징 서버의 동작 방법 및 장치

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6263212B1 (en) * 1998-02-17 2001-07-17 Alcatel Usa Sourcing, L.P. Short message service center
AU3990000A (en) * 1999-03-17 2000-10-04 Telefonaktiebolaget Lm Ericsson (Publ) System and method for short message delivery between gsm and tdma networks
AT411312B (de) * 2000-10-20 2003-11-25 Universal Comm Platform Ag Verfahren zum übermitteln von kurznachrichten (sms) zwischen rechnern im internet
US7072359B2 (en) * 2002-07-09 2006-07-04 Qualcomm, Inc. Short message conversion between different formats for wireless communication systems
KR20040006174A (ko) * 2002-07-11 2004-01-24 와이더덴닷컴 주식회사 무선단말기 이용자에 대한 인스턴트 메시지 전달 방법

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2005117469A1 *

Also Published As

Publication number Publication date
MXPA06011967A (es) 2006-12-15
WO2005117469A1 (en) 2005-12-08
JP2007533245A (ja) 2007-11-15

Similar Documents

Publication Publication Date Title
US20050243978A1 (en) System and method of interworking messages between mobile communication terminals
WO2005117469A1 (en) System and method of interworking messages between mobile communication terminals
KR101506029B1 (ko) 통합 메시징 서비스를 제공하기 위한 시스템과 방법
US9634865B2 (en) Method of providing quick answer service in SIP message service system
US9088531B2 (en) Interworking method and system in converged IP messaging service
EP1599979B1 (de) Nachrichtenverwaltung
JP5006864B2 (ja) 移動無線ネットワークにおけるデータ伝送のための方法および移動通信装置
EP2063590B1 (de) Verfahren und system zur übermittlung von email und ein push mail server
US8767543B2 (en) Terminal and method for storing and retrieving messages in a converged IP messaging service
US20030193967A1 (en) Method, apparatus and system for processing multimedia messages
US8825772B2 (en) System and method for operating a server for real-time communication of time-based media
US8300628B2 (en) Method and system for transmitting supplementary data, and communication terminal
US9391930B2 (en) CPM service provisioning system and method for interworking with non-CPM service
KR100548429B1 (ko) 이동통신 단말기 메시지의 호환을 위한 시스템 및 방법
WO2008148339A1 (fr) Procédé, agent d'utilisateur servant à traiter un message d'un modèle de dispositif de messagerie
WO2008128469A1 (fr) Réseau, entité de centre de capacité, entité de fonction d'interopération et procédé de notification de message
KR20080034072A (ko) Sip기반의 전송 메시지를 이용한 이종 메시지의 전송방법 및 이를 위한 사용자 장치
WO2009045061A2 (en) Procedure for forwarding stored messages and/or media in a converged ip messaging service and terminal therefor
WO2006068572A1 (en) A method and arrangement for communicating multimedia content

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: 20061002

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 MC NL PL PT RO SE SI SK TR

RIN1 Information on inventor provided before grant (corrected)

Inventor name: SHIM, DONG-HEE

Inventor name: LEE, HEE-JOUNG

Inventor name: KIM, YOUNG-AE

Inventor name: SON, SUNG-MU,YANGJIMAEUL HANYANG APT. 516-101

Inventor name: HUH, KANG-SUK,TOEGYE-JUGONG APT. 358-804

Inventor name: KIM, TE-HYUN,

RIN1 Information on inventor provided before grant (corrected)

Inventor name: SON, SUNG-MU,YANGJIMAEUL HANYANG APT. 516-101

Inventor name: HUH, KANG-SUK,6

Inventor name: LEE, HEE-JOUNG

Inventor name: KIM, YOUNG-AE

Inventor name: SHIM, DONG-HEE

Inventor name: KIM, TE-HYUN,

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20090917