WO2008044829A1 - Procédé de transmission de différents types de messages au moyen d'un message de transport à base sip et équipement utilisateur correspondant - Google Patents

Procédé de transmission de différents types de messages au moyen d'un message de transport à base sip et équipement utilisateur correspondant Download PDF

Info

Publication number
WO2008044829A1
WO2008044829A1 PCT/KR2007/004429 KR2007004429W WO2008044829A1 WO 2008044829 A1 WO2008044829 A1 WO 2008044829A1 KR 2007004429 W KR2007004429 W KR 2007004429W WO 2008044829 A1 WO2008044829 A1 WO 2008044829A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
service
sip
integrated
transport
Prior art date
Application number
PCT/KR2007/004429
Other languages
English (en)
Inventor
Tae Soon Choi
Sung Mu Son
Woo Jun Ye
Narasmha Murthy Prakash
Masson Romain
Kang Suk Huh
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 KR1020070002866A external-priority patent/KR20080034072A/ko
Application filed by Lg Electronics Inc. filed Critical Lg Electronics Inc.
Publication of WO2008044829A1 publication Critical patent/WO2008044829A1/fr

Links

Classifications

    • 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/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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/2895—Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • 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/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • 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 message transmission method, and more particularly, to a method of transmitting different types of messages using an SIP-based transport message and a user equipment therefor.
  • IMS internet protocol multimedia subsystem
  • IP Internet Protocol
  • the IMS is a set of nodes which provide various multimedia services in a mobile communication network and which perform a call control operation and unifies the IP network and the mobile communication network. Accordingly, the IMS facilitates a mutual operation between a user equipment and the IP network and thus can provide an IP based multimedia service using the user equipment.
  • the IP based multimedia services can be roughly classified into a text message service, a voice service, and a video service, depending on the types of transport objects.
  • the text message service is further classified into a unidirectional text service and a bidirectional text service.
  • the unidirectional text service includes a short message service (SMS), a multimedia message service (MMS), and an E-mail service.
  • Each of the IP based multimedia services including the unidirectional text service has it's own protocol silo for transmitting messages. That is, in such services, the messages created using transport protocols specific to the respective services are transmitted and processed in accordance with the transport protocols.
  • the transport protocols used in the unidirectional text service are listed in Table 1.
  • IMAP Internet Messaging Access Protocol
  • SMTP Simple Mail Transfer Protocol
  • Messaging clients which are modules taking charge of the respective services should be provided to a user equipment so as to enjoy various services. That is, the messaging clients taking charge of the services should be all fitted to the user equipment to transmit and receive the corresponding service messages with the user equipment. If a specific messaging client is not provided, it is not possible to transmit and receive the corresponding service message. Accordingly, the user equipment should include various messaging clients for the SMS, the MMS, and the E-mail service having similar characteristics, whereby the complexity in configuration, for example, software, of the user equipment is made to increase. Disclosure of Invention Technical Problem
  • a technical goal of the invention is to provide a method for transmitting different types of messages by the use of an SIP based transport message in which various service messages can be transmitted in a merged manner so as to unify various existing services having used particular transport protocols and to provide a merged service, and a user equipment therefor.
  • Another technical goal of the invention is to provide a method for transmitting different types of messages by the use of an SIP based transport message in which even a user equipment not having various existing messaging clients can be made to enjoy various existing message services, and a user equipment therefor.
  • a method for transmitting different types of messages by the use of an SIP based transport message comprising the steps of: receiving from a first user equipment a first transport message including a first integrated message created from an input message; and processing the input message by interworking with a legacy service server (LSS) corresponding to service type information of the input message and transmitting to a second user equipment a second transport message including a second integrated message created from the processed input message.
  • LSS legacy service server
  • header units of the first and second integrated messages may each include a common header field containing information common to various types of service messages and a specific header field containing information specific to the various types of service messages.
  • a method for transmitting different types of messages by the use of an SIP based transport message comprising the steps of: receiving, by a first client control function (CCF) of a first user equipment (UE), a signal for requesting for a type of service determined from an input message; creating, by the first CCF, a first integrated message from the input message on the basis of the service type information of the signal; creating, by the first CCF, a first transport message including the first integrated message and transmitting the created first transport message to a server system; extracting, by a server control function (SCF) of the server system, the first integrated message included in the received first transport message; creating, by the SCF, a legacy service message corresponding to the service type information from the extracted first integrated message; and processing, by the SCF, the legacy service message through interworking a legacy service server (LSS) corresponding to the service type information.
  • CCF client control function
  • UE user equipment
  • LSS legacy service server
  • a method of transmitting different types of messages by the use of an SIP based transport message including the steps of: determining a service type from an input message and creating an integrated message from the input message on the basis of the determined service type; and creating and transmitting a transport message including the integrated message.
  • a user equipment for supporting a message service using an SIP based transport message including a processor that determines a service type from an input message, creates an integrated message from the input message on the basis of the determined service type, and transmits a transport message including the integrated message.
  • FIG. 1 is a block diagram illustrating a system for transmitting different types of messages by the use of an SIP based transport message according to an embodiment of the invention.
  • FIG. 2 is a flowchart illustrating an algorithm of determining a service type from an input message.
  • FIG. 3 is a diagram illustrating a format of an integrated message according to an embodiment of the invention.
  • FIGs. 4 to 7 are diagrams illustrating examples of the format shown in Fig. 3.
  • FIGs. 8 and 9 are diagrams illustrating examples of the format shown in Fig. 3, where a format is selected and used from two types of formats of an integrated message.
  • FIG. 10 is a block diagram illustrating a system used to explain a method of transmitting different types of messages by the use of an SIP based transport message between two user equipments in an IMS network according to an embodiment of the invention.
  • FIG. 11 is a diagram illustrating a message flow of transmitting different types of messages from a first user equipment and a second user equipment by the use of an SIP message in the system shown in Fig. 10 according to an embodiment of the invention.
  • Fig. 12 is a diagram illustrating a message flow of transmitting different types of messages from a first user equipment and a second user equipment by the use of an SIP message in the system shown in Fig. 10 according to another embodiment of the invention.
  • FIG. 13 is a block diagram illustrating a system used to explain a method of transmitting different types of messages by the use of the SIP based transport message according to another embodiment of the invention. Best Mode for Carrying Out the Invention
  • a session initiation protocol is known as one of the signaling protocols which can be used in an IP based multimedia service over an IMS network.
  • the SIP is a call control protocol of an application layer for searching for a position of a communication opposite and generating, correcting, and ending an IP based multimedia service session between user equipments or between a user equipment and an entity having an IP address.
  • the SIP message or an SIP based protocol message is used to provide an integrated message service in the IMS network.
  • the SIP based protocol is a transport protocol used to transmit different types of messages through an established SIP session and an example thereof is a message session relay protocol (MSRP).
  • MSRP message session relay protocol
  • an MSRP message which is simpler than the SIP message, is transmitted through the established SIP session, and is under the congestion control of a transport control protocol (TCP). Accordingly, by using the MSRP message, it is possible to transmit a message having a larger size in comparison with a case using the SIP message.
  • TCP transport control protocol
  • the SIP and the MSRP are exemplary protocols for embodiments of the invention and the message transmission method according to the invention is not limited to the message transmission method using the SIP and/or the MSRP.
  • FIG. 1 is a block diagram illustrating a configuration of a system for transmitting an
  • the SIP based transport message includes an SIP message and an SIP based protocol message.
  • Basic configurations of entities for transmitting different types of messages between a user equipment (UE) 10 and a server system 20 through an IMS core (SIP/IMS core) using an SIP as a signaling protocol are shown in Fig. 1.
  • the UE 10 includes a user interface (UI) 12 and a client control function (CCF) 14.
  • the UE 10 can support a converged IP messaging (CPM) service in which various services are merged through the IMS network.
  • CCM converged IP messaging
  • the UE 10 may be a fixed device or a mobile device and the kind and name thereof is not particularly limited.
  • the UE 10 may be a mobile station (MS), a laptop computer or a PDA (Personal Digital Assistant) having a CPM client function built therein.
  • the UE 10 may be called a user terminal (UT), a mobile station (MS), a subscriber station, or a wireless device.
  • the UE 10 accesses the IMS network by communicating with a server system 20 through an IMS core or directly through the established SIP session and supports various services such as the CPM service to be provided through the accessed IMS network. For example, when it is intended to transmit an SMS message using the CPM service, the UE 10 first accesses the IMS network and transmits a registration request message such as an SIP REGISTER message to the server system 20 through the IMS core to register in the server system 20.
  • a registration request message such as an SIP REGISTER message
  • the UE 10 includes a user interface (UI) 12 such as a control button, a voice command, a display, and/or an acoustic device.
  • UI user interface
  • the UI 12 enables a user to conveniently input a desired service type of message or a query associated therewith and notifies the user of the processing result of the query associated with a service process, the received message, and the like.
  • the UI 12 interworks with the CCF 14. For example, the UI 12 transmits a message input by a user to the CCF 14 to request for a predetermined message service, or receives a message from the CCF 14 to notify the user of the received message.
  • the UI 12 may perform a function of determining a service type from the message input by the user. For the purpose of this function, the UI 12 may include a module having an algorithm for classifying a service type from the input message. For example, when the user inputs a predetermined message, the UI 12 determines to which service the message is directed among various services (an SMS, an MMS, and an E-mail service). The UI 12 may deliver information on the service type of the input message, which is the determination result, to the CCF 14.
  • Fig. 2 is a flowchart illustrating an example of such an algorithm performed by the UI 12.
  • a user first inputs a message to be transmitted (Sl).
  • the user need not additionally input information on the service type to be used.
  • the UI 12 determines the service type using only the input message.
  • the message input by the user may include only a text, may include a multimedia file created in a synchronized multimedia integration language (SMIL) along with a text, or may include a file having a different form.
  • SMIL synchronized multimedia integration language
  • the size of 160 Bytes is arbitrary and the message size used as a determination reference in this step may vary depending on a transport protocol used in the message transmission method according to this embodiment of the invention.
  • the size of the message is 160 bytes as in this embodiment or may be properly determined within the range of values smaller than 160 Bytes.
  • the maximum size of a message which can be inserted into the body unit of the SIP MESSAGE is a value other than 160 Bytes or when a message other than the SIP MEASSAGE is used in the message transmission method to be described later, the size of the message may vary.
  • step S3 When it is determined in step S3 that the size of the input message is equal to or less than 160 Bytes, the service type of the message requested by the user is an SMS. When it is determined that the size of the input message is greater than 160 Bytes, the process of step S4 is performed.
  • the input message is a message including an SMIL file (S4).
  • S4 SMIL file
  • the service type requested by the user is an MMS.
  • the service type requested by the user is an E-mail service.
  • the function of determining the service type may be performed independently by the UI 12 or may be performed in cooperation with the UI 12 and the CCF 14. In some examples, the function is not performed by the UI 12 but may be performed by the CCF 14.
  • the UE 10 includes the CCF 14 for controlling a module taking charge of the CPM service and the CCF 14 performs the following various functions.
  • the CCF 14 may be a module itself taking charge of the CPM service or may be a functional entity included in the module or separated from the module.
  • the CCF 14 may perform the function of determining the service type from the input message.
  • the function of determining the service type may be performed independently by the CCF 14 or may be performed by interlocking with the UI 12. Or if the function is performed independently by the UI 12, the CCF 14 may not perform this function.
  • the CCF 14 performs a transcoding process of creating an integrated message from the input message or creating an output message from the integrated message.
  • the integrated message is a new type of message for replacing various types of service messages such as an SMS message, an MMS message, and an E-mail message with a single format message.
  • Fig. 3 is a diagram illustrating a format of an integrated message according to an embodiment of the invention.
  • the integrated message similarly to other existing message formats, the integrated message has a header unit and a body unit.
  • the content that is, the input message, is inserted into the body unit.
  • a message input through the UI 12 as the input message is inserted into the body unit or the input message may be encoded and then inserted into the body unit.
  • the header unit of the integrated message according to this embodiment is different from that of the message formats of various existing services, in that the header unit has a common header field and a specific header field.
  • Information common to various existing services that is, information contained in common in the header units of various existing service messages, are disposed in the common header field.
  • receiver information (To) receiver information
  • transmitter information (From) transmitter information
  • Message-ID message identification information
  • transaction ID transaction ID
  • available period information Expiry
  • service type information of input message Message Service Type
  • Information specific to the header units of various existing service messages is contained in the specific header field. That is, information which is not contained in the header unit of a different service but which is contained in only the header unit of a specific service message is disposed in the specific header field.
  • information other than the information contained in the common header field can be contained in the specific header field.
  • the other information may include service certre time stamp, protocol identifier, more message to send, priority, message waiting, alert SC, reply path, and status report capability.
  • the other information may include Date, X-ms-Status, X-Mms -Read- Status, X-Mms-MMS-Version, X- Mms-Message Size, X-Mms-Message-Class, X-Mms-Content-Location, and X- Mms-Response-Status.
  • the specific header field may include only one area as a whole, or may include two or more specific header subfields.
  • Fig. 4 shows the former in which the specific header field is not divided into subfields.
  • information specific to the header unit of the SMS message, the MMS message, or the E-mail message may be contained in the specific header field thereof. What service message the contained information indicates can be checked from Message Service Type contained in the common header field.
  • Figs. 5 to 7 show examples in which the specific header field is divided into two or more specific header subfields.
  • Fig. 5 shows an example in which the specific header field is divided into three subfields.
  • information specific to the SMS message may be contained in the SMS header subfield and the other subfields may contain no information or information indicating that there is no information.
  • information specific to the corresponding message is contained in the MMS header subfield or the E-mail header subfield. In this case, it can be checked to what service message the integrated message relates, on the basis that the information is contained in what subfield.
  • Figs. 6 and 7 show examples in which the specific header field is divided into two subfields.
  • the specific header field is divided into an SMS and MMS header subfield and an E-mail header subfield.
  • the SMS message or the MMS message information specific to the header unit of the corresponding message is contained in the SMS and MMS header subfield.
  • the E-mail message information specific to the header unit of the E- mail message is contained in the E-mail header subfield.
  • the specific header field is divided into an SMS and E-mail header subfield and an MMS header subfield.
  • the CCF 14 may select one of two types of message formats depending on the service type of the input message and may create an integrated message.
  • Figs. 8 and 9 are diagrams illustrating two types of integrated message formats.
  • the two types of integrated message formats include a case where the input message corresponds to the SMS and MMS service and a case where the input message corresponds to the E-mail service. More specifically, when the input message corresponds to the SMS service or the MMS service, the CCF 14 creates the integrated message by the use of the left message format. When the input message corresponds to the E-mail service, the CCF 14 creates the integrated message by the use of the right message format.
  • the two types of integrated message formats include a case where the input message corresponds to the SMS and E-mail service and a case where the input message corresponds to the MMS service. More specifically, when the input message corresponds to the SMS service or the E-mail service, the CCF 14 creates an integrated message by the use of the left message format. When the input message corresponds to the MMS service, the CCF 14 creates the integrated message by the use of the right message format.
  • the CCF 14 transmits and receives the integrated message to and from the SCF 22 by communicating with the SCF 22 in accordance with a predetermined transport protocol such as an SIP or an SIP based protocol.
  • a predetermined transport protocol such as an SIP or an SIP based protocol.
  • the CCF 14 transmits and receives information on the service type to and from the SCF 22 along with the integrated message or independently of the integrated message. More specifically, when the input message is a unidirectional short message such as the SMS message, the CCF 14 can transmit and receive the service type information and the integrated message by the use of one of the SIP messages such as an "SIP MESSAGE" message.
  • the CCF 14 can transmit and receive the integrated message by the use of one of the SIP based protocol messages such as an MSRP SEND message.
  • the service type information can be transmitted in a state where it is contained in the MSRP SEND message or may be transmitted and received by the use of an SIP invite message which is a session initiation request message.
  • the CCF 14 manages and controls a session for communication with the SCF 22.
  • the CCF 14 has an SIP session initiation function and can perform functions of generating, correcting, and ending a unidirectional or bidirectional SIP session.
  • the CCF 14 provides capability information of the UE 10 associated with the CPM service to the server system 20, for example the SCF 22. For example, when it is intended to register the UE 10 in the server system 20 taking charge of a merged service, the CCF 14 can provide information on the types of the message services supported by the UE 10 to the SCF 22 by the use of an SIP REGISTER message.
  • the server system 20 includes a server control function (SCF) 22 and plural legacy service servers (LSS) 24.
  • SCF server control function
  • LSS legacy service servers
  • the plural LSSs 24 are provided in the server system 20.
  • the LSSs 24 serve to create a service message or process a received service message and to perform a function of transmitting the corresponding service message to the LSS of another system, and thus are similar to the conventional LSS in function.
  • the LSS-I 24a creates an SMS message or processes a received SMS message and transmits the SMS message to an SMS server of another system or another user equipment having an SMS client
  • the function of the LSS 24 according to the invention is different from that of the conventional LSS in that all or a part of the above-mentioned functions can be performed by interworking with the SCF 22. That is, the LSS 24 according to the invention creates a service message in response to a request from the SCF 22.
  • the LSS 24 processes (performs processes such as confirmation of integrity of the message, charge for the message, and/or authentication for the message) the legacy service message transmitted from the SCF 22 and requests the SCF 22 to transmit the processed legacy service message. In this case, the LSS 24 may transmit the processed legacy service message to the SCF 22 along with the request.
  • the LSS 24 include plural LSSs of an LSS- 1 24a, an LSS-2 24b, and an LSS-3 24c.
  • the LSS-I 24a, the LSS-2 24b, and the LSS-3 24c are servers managing the services, respectively.
  • the LSS-I 24a may be an SMS service server
  • the LSS-2 24b may be an MMS service server
  • the LSS-3 24c may be an SIMPLE- IM service server.
  • the server system 20 has an SCF 22 for controlling a server managing the CPM service.
  • the SCF 22 may be a server itself managing the CPM service or a functional entity included therein.
  • the SCF 22 performs the following various functions.
  • the SCF 22 knows various service types and can know the service type of the transport message from information contained in the header (for example, "subject" header) of the message received from the CCF 14, for example, the "SIP MESSAGE” message or the SIP INVITE message.
  • the information on the service type of the transport message and known to the SCF 22 can be used to select a corresponding LSS managing the transport message among the plural LSSs.
  • Another function of the SCF 22 is performed by interworking with the LSS 24.
  • the SCF 22 may interwork with a separated LSS 24 or may include a integrated LSS 24. That is, the LSS 24 may be embedded and physically integrated in the SCF 22 or the SCF 22 and the LSS 24 may be physically separated from each other to form independent modules.
  • the SCF 22 processes the message received from the CCF 14 or creates a message to be transmitted to the CCF 14 by interworking with the LSS 24.
  • the SCF 22 extracts the integrated message from the received transport message (for example, SIP MESSAGE or MSRP SEND) and then performs a transcoding process of creating a service message from the integrated message. Then, the SCF 22 delivers the service message created in the transcoding process to the corresponding LSS 24.
  • the received transport message for example, SIP MESSAGE or MSRP SEND
  • LSS 24 performs a transcoding process of creating an integrated message by the use of the service message delivered from the LSS 24. Then, the SCF 22 creates a message to be transmitted to the CCF 14, for example, an SIP MESSAGE or MSRP SEND message, and inserts the integrated message created in the transcoding process into the created SIP MESSAGE or MSRP SEND message.
  • SCF 22 creates a message to be transmitted to the CCF 14, for example, an SIP MESSAGE or MSRP SEND message, and inserts the integrated message created in the transcoding process into the created SIP MESSAGE or MSRP SEND message.
  • the SCF 22 communicates with the CCF 14 in accordance with the SIP or the SIP based protocol (for example, MSRP).
  • the SCF 24 manages and controls a session for communication with the CCF 14. Specifically, the SCF 24 has the SIP session initiation function and can also perform functions of generating, correcting, and ending a unidirectional or bidirectional SIP session.
  • the SCF 24 manages capability information of the UE 10 associated with the CPM service.
  • Fig. 10 is a block diagram illustrating a system configuration used to explain a method of transmitting different types of messages between two UEs by the use of an SIP based transport message according to an embodiment of the invention.
  • the system includes a first UE 30, a server system 40, and a second UE 50.
  • the first UE 30 is a device for transmitting a service message to the second UE 50 and includes a first UI 32 and a first CCF 34.
  • the server system 40 is a system for managing a message transmission service between the first UE 30 and the second UE 50 and includes an SCF 42 and an LSS 44.
  • the second UE 50 is a device for receiving the service message from the first UE 30 and includes a second UI 52 and a second CCF 54.
  • the first and second UIs 32 and 52 and the first and second CCFs 34 and 54 are examples of the UI 12 and the CCF 14 described with reference to Fig. 1, respectively, and the SCF 42 and the LSS 44 are examples of the SCF 22 and the LSS 24 described with reference to Fig. 1. Accordingly, detailed de- scription of functions of the elements is omitted.
  • Fig. 11 is a flowchart illustrating a message flow of transmitting an integrated message from the first UE 30 to the second UE 50 by the use of the SIP message as a transport message in the system shown in Fig. 10.
  • the integrated message is the SMS message
  • all the service messages having the same characteristic as the SMS message can be transmitted using a method equal to or equivalent to the message transmitting procedure according to this embodiment.
  • the first UI 32 determines the service type from the input message and sends a signal for requesting for the determined type of service, for example, the SMS, to the first CCF 34 (SlOl). More specifically, when a predetermined message is input by the user, the first UI 32 performs a process of determining the type of the service requested by the user from the input message. It can be known from the process that the service requested by the user is the SMS. In the process of determining the type of the service requested by the user, for example, the algorithm described with reference to Fig. 2 can be used.
  • the first CCF 34 having received the SMS request creates a transport message to be transmitted to the SCF 42 from the message input by the user (S 102).
  • the process of creating the transport message can be divided into two steps. The first step is a process of creating an integrated message from the input message and the second step is a process of creating the transport message by the use of the created integrated message.
  • the first CCF 34 creates the integrated message to create the transport message.
  • the integrated message may be a message having any one of integrated message formats shown in Figs. 4 to 7, for example, the format shown in Fig. 5.
  • receiver information (To), transmitter information (From), and message identification information (Message-ID) are contained in the common header field thereof.
  • transaction identification information (transaction ID), available period information (Expiry), and service type information (Message Service Type) of the message input by the user may be contained in the common header field.
  • information for example, service certre time stamp, protocol identifier, more message to send, priority, message waiting, alert SC, reply path, and status report capability
  • the message input by the user is contained in the body unit of the integrated message.
  • the first CCF 34 having created the integrated message creates the transport message by the use of the integrated message. More specifically, the first CCF 34 can create the transport message by creating a message using the SIP, for example, a "FIRST SIP MESSAGE" message, inserting the information indicating the SMS message into a header unit (for example, "subject" header) of the "FIRST SIP MESSAGE” message, and inserting the created integrated message into a body unit of the "SIP MESSAGE” message without correction.
  • SIP for example, a "FIRST SIP MESSAGE” message
  • a header unit for example, "subject" header
  • the first CCF 34 transmits the transport message containing the integrated message, for example, the "FIRST SIP MESSAGE" message, to the SCF 42 (S 103).
  • the service type information can be transmitted in the state where it is contained in the header unit of the transport message.
  • the SCF 42 processes the received "FIRST SIP MESSAGE" message (S 104). More specifically, the SCF 42 extracts the service type information from the header unit (for example, "subject" header)and the integrated message from the body unit of the received transport message (first SIP MESSAGE). The service type information indicates the service type (SMS in this embodiment) of the extracted integrated message. The SCF 42 transcodes the extracted integrated message into an SMS message format.
  • the SCF 42 may further perform a necessary process on the received message in step S 104.
  • the SCF 42 can perform a process of confirmation of authorization and/or authentication by interworking with a integrated security enabler module or communicating with a separated security enabler module. Accordingly, the SCF 42 can transmit authorization and/or authentication information to the security enabler module.
  • the process of confirmation of authorization and/or authentication may be performed by the corresponding LSS 44, for example, the LSS-I 44a which is an SMS server, instead of the SCF 42.
  • the SCF 42 delivers the SMS message created in the transcoding process to the LS
  • S-I 44a which is the corresponding LSS 44 (S 105).
  • the LSS-I 44a performs a predetermined process on the delivered SMS message (S 106).
  • the process performed by the LSS-I 44a includes, for example, confirmation of integrity of the received SMS message and the process of confirmation of authorization and/or authentication by interworking with the security enabler module.
  • the LSS-I 44a may perform a charging process by interworking with a charging module.
  • the charging process may be performed by the SCF 42, instead of the LSS-I 44a.
  • the LSS- 1 44a requests the SCF 42 to transmit an SMS message to the second UE
  • the LSS-I 44a can deliver the SMS message to be transmitted to the SCF 42 along with the request.
  • the SCF 42 creates the transport message to be transmitted to the second UE 50, more specifically, the second CCF 54, in response to the request.
  • the process of creating the transport message can be roughly divided into two steps, similarly to step S 102.
  • the first step is a process of creating an integrated message from the delivered SMS message and the second step is a process of creating the transport message by the use of the created integrated message.
  • the SCF 42 creates the integrated message to create the transport message.
  • the integrated message may be a message having any one of integrated message formats shown in Figs. 4 to 7, for example, the format shown in Fig. 5.
  • the SCF 42 having created the integrated message subsequently creates a "SECOND SIP MESSAGE" message as the transport message by the use of the integrated message.
  • the information indicating the SMS message is contained in the header unit (for example, "subject" header) of the "SECOND SIP MESSAGE" message and the created integrated is inserted into the body unit of the second SIP MESSAGE without correction.
  • the SCF 44 transmits the "SECOND SIP MESSAGE" message to the second CCF
  • the second CCF 54 processes the received "SECOND SIP MESSAGE" message (SI lO). More specifically, the second CCF 54 extracts the service type information from the header unit (for example, "subject" header)and the integrated message from the body unit of the received "SECOND SIP MESSAGE” message. The service type information indicates the service type (SMS in this embodiment) of the extracted integrated message.
  • the second CCF 54 having processed the received "SECOND SIP MESSAGE" message transmits a message indicating the processing result to the SCF 42 in accordance with a usual message transmission procedure.
  • the SCF 42 or the LSS-I 44a having received the processing result may transmit charging data to the charging module in accordance with a usual procedure.
  • the second CCF 54 delivers a signal indicating that the SMS message is received, for example, an SMS notification message, to the second UI 52 (Sl 11).
  • the transmitting UE 30 creates the integrated message from the SMS message which is the input message and transmits the created integrated message to the server system 40 in a state where it is included in a kind of an SIP message.
  • the server system 40 transmits a message to the receiving UE 50 in the same manner.
  • the service type information of the input message is transmitted in a state where it is included in the SIP message, which is used as the transport message.
  • Fig. 12 is a flowchart illustrating a message flow of transmitting the integrated message from the first UE 30 to the second UE 50 by using the SIP based protocol message (for example, MSRP message) as the transport message.
  • SIP based protocol message for example, MSRP message
  • MSRP message the SIP based protocol message
  • the invention is described in detail below under the assumption that the integrated message is the MMS message, all the service messages having the same characteristic as the MMS message (for example, E-mail message) can be transmitted using a method equal to or equivalent to the message transmitting procedure according to this embodiment to be described later.
  • the first UI 32 determines the service type from the input message and sends a signal for requesting for the determined type of service, for example, the MMS, to the first CCF 34 (S201). More specifically, when a predetermined message is input by the user, the first UI 32 performs a process of determining the type of the service requested by the user from the input message. It can be known from the determination process that the service requested by the user is the MMS. In the process of determining the type of the service requested by the user, for example, the algorithm described with reference to Fig. 2 can be used.
  • the first CCF 34 having received the MMS request starts a process of establishing an SIP session with the SCF 42 of the server system 40 (steps S202 to S204).
  • the first CCF 34 first creates a session initiation request message, for example, SIP invite message (S202).
  • SIP invite message S202
  • the service type information of the input message is contained in the header unit (for example, "subject" header) of the SIP invite message and an SDP (Session Description Protocol) offer may be contained in the body unit of the SIP invite message.
  • SDP Session Description Protocol
  • the first CCF 34 transmits the created SIP invite message to the SCF 42 (S203).
  • the SIP session is established between the first CCF 34 and the SCF 42 (S204) by performing between the first CCF 34 and the SCF 42 a usual message transmission procedure including a process of allowing the SCF 42 to transmit a response message(for example, 200 OK) to the first CCF 34.
  • the first CCF 34 having received the MMS request creates a transport message to be transmitted to the SCF 42 from the message input by the user (S205).
  • the process of creating the transport message can be divided into two steps. The first step is a process of creating an integrated message from the input message and the second step is a process of creating the transport message by the use of the created integrated message.
  • the first CCF 34 creates the integrated message to create the transport message.
  • the integrated message may be a message having any one of integrated message formats shown in Figs. 4 to 7, for example, the format shown in Fig. 5.
  • receiver information (To), transmitter information (From), and message identification information (Message-ID) are contained in the common header field thereof.
  • message identification information transaction ID
  • available period information Expiry
  • service type information Message Service Type
  • information contained in the header unit of the MMS message information (for example, Date, X-ms-Status, X- Mms-Read-Status, X-Mms-MMS- Version, X-Mms-Message Size, X- Mms-Message-Class, X-Mms-Content-Location, and X-Mms-Response-Status) not contained in the common header field can be contained in the MMS header subfield.
  • the message input by the user is contained in the body unit thereof.
  • the first CCF 34 having created the integrated message creates the transport message by the use of the integrated message. More specifically, the first CCF 34 can create the transport message by creating a SIP based message, for example, MSRP SEND message and inserting the created integrated message into a body unit of the MSRP SEND message without correction. In some embodiments, when the service type information is not contained in the header unit of the SIP invite message, the information may be contained in the header unit of the MSRP SEND message.
  • the first CCF 34 transmits the created MSRP SEND message to the SCF 42 through the established SIP session (S206).
  • the SCF 42 creates the MMS message by processing the received MSRP SEND message (S207). More specifically, the SCF 42 extracts the integrated message from the body unit of the MSRP SEND message. Then, the SCF 42 transcodes the extracted integrated message into the MMS message format on the basis of the service type obtained from the receive SIP invite message or the MSRP SEND message.
  • the SCF 42 may perform a process of confirmation of authorization and/or authentication by in- terworking with a integrated security enabler module or a separate security enabler module.
  • the SCF 42 transmits the created MMS message to the LSS-2 44b which is the corresponding LSS 44 (S208).
  • the LSS-2 44b performs a necessary process on the received MMS message (S209) and notifies the first SCF 22 of the processing result.
  • the LSS-2 44b starts a procedure of transmitting the processed MMS message to another UE.
  • the LSS-2 44b first delivers a signal for requesting for transmitting an MMS notification message to the SCF 42 (S210).
  • the LSS-2 44b can transmit the MMS notification message to the SCF 42 along with the request signal.
  • the SCF 42 creates the transport message to be transmitted to the second UE 50, more specifically, the second CCF 54, in response to the request (S211).
  • the process of creating the transport message can be roughly divided into two steps, similarly to step S205.
  • the first step is a process of creating an integrated message from the delivered MMS message or the created MMS notification message and the second step is a process of creating the transport message by the use of the created integrated message.
  • the SCF 42 first creates the integrated message in order to create the transport message.
  • the integrated message may be a message having any one of integrated message formats shown in Figs. 4 to 7, for example, the format shown in Fig. 5.
  • the MMS notification message is inserted into the body unit of the integrated message.
  • the SCF 42 having created the integrated message subsequently creates an "SIP MESSAGE" message as the transport message by the use of the integrated message.
  • the information indicating the MMS message is contained in the header unit (for example, "subject" header) of the "SIP MESSAGE” message and the created integrated is inserted into the body unit of the SIP MESSAGE without correction.
  • the SCF 44 transmits the created "SIP MESSAGE" message to the second CCF 54
  • the second CCF 54 processes the received "SIP MESSAGE” message (S213). More specifically, the second CCF 54 extracts the service type information and the integrated message from the header unit (for example, "subject" header) and the body unit of the received "SIP MESSAGE” message.
  • the service type information indicates the service type (SMS in this embodiment) of the extracted integrated message.
  • the second CCF 54 having processed the received "SIP MESSAGE” message transmits a message indicating the processing result to the SCF 42 in accordance with a usual message transmission procedure.
  • the SCF 42 or the LSS-2 44b having received the processing result may transmit charging data to the charging module in accordance with a usual procedure.
  • the second CCF 54 delivers a signal indicating that the MMS message is received, for example, an MMS notification message, to the second UI 52 (S214).
  • the transmitting UE 30 determines the service type from the message input by the user and then requests for the determined type of service.
  • the UE 30 sets up an SIP session with the server system 40, creates the integrated message from the input message, for example, the MMS message, and transmits the created integrated message to the server system 40 through the established SIP session in a state where it is inserted into the MSRP message which is a kind of SIP based protocol message.
  • the service type information of the input message is also transmitted to the server system 40 together.
  • the server system 40 creates the integrated message from the MMS notification message which is the received notification message and transmits the created integrated message to the receiving UE 50 in the state where it is inserted into the SIP message.
  • the same method as transmitting a message from the transmitting UE 30 to the server system 40 may be used to transmit a message from the server system 40 to the receiving UE 50. That is, when a message is transmitted from the server system 40 to the receiving UE 50, a method of first es- tablishing an SIP session between the server system 40 and the receiving UE 50 and then transmitting the SIP based protocol message including the integrated message through the established SIP session may be used.
  • Fig. 13 is a block diagram illustrating a system configuration used to explain a message transmission method in an IMS network according to another embodiment of the invention.
  • the system includes a first UE 60, a first server system 70, a second E-mail service server (LSS-3 1 ) 82, and an E-mail service client (LSC-3) 84.
  • LSS-3 1 second E-mail service server
  • LSC-3 3 E-mail service client
  • the first UE 60 is an example of the UE 10 described with reference to Fig. 1 and includes a first UI 62 and a first CCF 64.
  • the first server system 70 is also an example of the server system 20 described with reference to Fig. 1 and includes a first SCF 72 and a first LSS 74.
  • the first LSS 74 includes plural legacy service servers.
  • a first LSS-I 74a may be an SMS server
  • a first LSS-2 74b may be an MMS server
  • a first LSS-3 74c may be an E-mail service server.
  • the configurations and functions of the entities constituting the first UE 60 and the first server system 70 are equal to those of the UE 10 and the server system 20 described above and thus detailed description thereof will be omitted.
  • the LSS-3' 82 as the second E-mail service server is an E-mail service server of a server system different from the first server system 70.
  • the LSS-3' 82 may be an entity equal to the LSS-3 74c as the first E-mail service server of the first server system 70.
  • the LSS-3' 82 manages an E-mail communication with the LSC-3 84, which is an E-mail service client of another user equipment.
  • the message transmission method in the IMS network according to the above-mentioned embodiment of the invention and the message transmission method according to the related art are used together. More specifically, the communication between the first UE 60 and the first server system 70 is performed using the message transmission method according to the embodiment of the invention.
  • the communication between the first LSS-3 74c which is a server managing the E-mail service in the first server system 70 and the LSS-3' 82 which is a server managing the E-mail service in another server system is performed using the IETF Lemonade IMAP or the OMA DS which is the message transmission method according to the related art.
  • the communication between the LSS-3' 82 and the LSC-3 84 is performed using the message transmission method according to the related art.
  • the invention is advantageously used in the field of a message transmission service using an IMS network and a system and a user equipment for supporting the service.

Abstract

L'invention concerne un procédé de transmission de différent types de messages au moyen d'un message de transport à base SIP dans lequel des services de messages variés, tels qu'un service de messages courts (SMS), un service de messages multimédias (MMS) et un service de courrier électronique peuvent être fournis de manière combinée; et un équipement utilisateur. Ledit procédé consiste : à déterminer un type de service à partir d'un message d'entrée et à créer un message intégré à partir dudit message d'entrée en fonction du type de service déterminé; et à créer un message de transport comprenant le message intégré. Une unité d'en-tête de message intégré comprend un champ d'en-tête commun contenant des informations communes de types de message de services variés et un champ d'en-tête spécifique contenant des informations spécifiques aux types de messages de services variés. Un message de transport contenant le message intégré créé est créé et transmis. Les procédés de création du message intégré et de transmission du message de transport peuvent être exécutés au moyen d'une fonction de commande client (CCF) qui est un processeur intégré à un équipement utilisateur.
PCT/KR2007/004429 2006-10-13 2007-09-13 Procédé de transmission de différents types de messages au moyen d'un message de transport à base sip et équipement utilisateur correspondant WO2008044829A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US85130806P 2006-10-13 2006-10-13
US60/851,308 2006-10-13
KR10-2007-0002866 2007-01-10
KR1020070002866A KR20080034072A (ko) 2006-10-13 2007-01-10 Ｓｉｐ기반의 전송 메시지를 이용한 이종 메시지의 전송방법 및 이를 위한 사용자 장치

Publications (1)

Publication Number Publication Date
WO2008044829A1 true WO2008044829A1 (fr) 2008-04-17

Family

ID=39283003

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2007/004429 WO2008044829A1 (fr) 2006-10-13 2007-09-13 Procédé de transmission de différents types de messages au moyen d'un message de transport à base sip et équipement utilisateur correspondant

Country Status (1)

Country Link
WO (1) WO2008044829A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108512863A (zh) * 2018-06-06 2018-09-07 中国人民解放军陆军工程大学 一种多类型sip设备语音通信控制系统
CN111211962A (zh) * 2018-11-22 2020-05-29 奥兰治 管理共享和共享消息的方法、不同类型的消息传递装置
US20220060513A1 (en) * 2020-08-21 2022-02-24 Oracle Intenational Corporation Centralized request processing and security zone policy enforcement in a cloud infrastructure system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050193133A1 (en) * 2002-04-08 2005-09-01 Nokia Corporation Message header for messaging service
US20060209791A1 (en) * 2005-03-21 2006-09-21 Tekelec Methods, systems, and computer program products for providing telecommunications services between a session initiation protocol (SIP) network and a signaling system 7 (SS7) network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050193133A1 (en) * 2002-04-08 2005-09-01 Nokia Corporation Message header for messaging service
US20060209791A1 (en) * 2005-03-21 2006-09-21 Tekelec Methods, systems, and computer program products for providing telecommunications services between a session initiation protocol (SIP) network and a signaling system 7 (SS7) network

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108512863A (zh) * 2018-06-06 2018-09-07 中国人民解放军陆军工程大学 一种多类型sip设备语音通信控制系统
CN111211962A (zh) * 2018-11-22 2020-05-29 奥兰治 管理共享和共享消息的方法、不同类型的消息传递装置
CN111211962B (zh) * 2018-11-22 2023-09-15 奥兰治 管理共享和共享消息的方法、不同类型的消息传递装置
US20220060513A1 (en) * 2020-08-21 2022-02-24 Oracle Intenational Corporation Centralized request processing and security zone policy enforcement in a cloud infrastructure system

Similar Documents

Publication Publication Date Title
US8204932B2 (en) Method and apparatus for instant messaging
EP2290911B1 (fr) Procede, dispositif et systeme de transmission de messages multimedia a des terminaux incompatibles
EP1632066B1 (fr) Traitement de message
EP1352499B1 (fr) Systeme et procede d'acheminement de service de messagerie multimedia
JP5090459B2 (ja) 統合ｉｐメッセージングサービスにおけるメッセージスレッドを管理する方法及びシステム
US20060230154A1 (en) Method and entities for performing a push session in a communication system
US8291022B2 (en) Method and device for messaging
US20100087215A1 (en) Method, system, and message service interworking module for implementing message service interworking
EP2146511B1 (fr) Procédé et système de réalisation de service de messagerie, et serveur d'application de messagerie
KR101490266B1 (ko) 통합 ｉｐ 메시징 서비스의 메시지를 저장 및 검색하는 단말 및 방법
EP2253108B1 (fr) Interfonctionnement entre domaines de service de messagerie
US20080240117A1 (en) System, Method, and Interworking Function for Interfacing MMS and IMS Messaging Systems
US20080261591A1 (en) Method for Transmitting Application-Specific Registration or De-Registration Data and System, Server and Communication Terminal Therefor
CN107580306A (zh) 一种转发多媒体消息的方法和系统
US8300628B2 (en) Method and system for transmitting supplementary data, and communication terminal
US20050193133A1 (en) Message header for messaging service
WO2009082097A1 (fr) Procédé et système pour fournir un message comportant une liste de dispositifs utilisateur récepteurs à chaque dispositif utilisateur récepteur
WO2008044829A1 (fr) Procédé de transmission de différents types de messages au moyen d'un message de transport à base sip et équipement utilisateur correspondant
KR20080034072A (ko) Ｓｉｐ기반의 전송 메시지를 이용한 이종 메시지의 전송방법 및 이를 위한 사용자 장치
WO2008148339A1 (fr) Procédé, agent d'utilisateur servant à traiter un message d'un modèle de dispositif de messagerie
CN100452778C (zh) 基于即时通讯的多媒体内容互动系统及其实现方法
GB2397723A (en) Data transmission
KR101008429B1 (ko) 메시지 포맷 변환 방법 및 그 장치
WO2009065362A1 (fr) Procédé, système et dispositif pour le routage d'un message selon un protocole sip dans un réseau traditionnel
Lin et al. Implementation and performance evaluation for a ubiquitous and unified multimedia messaging platform

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07808220

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07808220

Country of ref document: EP

Kind code of ref document: A1