WO2008022990A1 - Passerelle et procédé pour router des messages - Google Patents

Passerelle et procédé pour router des messages Download PDF

Info

Publication number
WO2008022990A1
WO2008022990A1 PCT/EP2007/058630 EP2007058630W WO2008022990A1 WO 2008022990 A1 WO2008022990 A1 WO 2008022990A1 EP 2007058630 W EP2007058630 W EP 2007058630W WO 2008022990 A1 WO2008022990 A1 WO 2008022990A1
Authority
WO
WIPO (PCT)
Prior art keywords
messaging
message
service
messaging service
gateway node
Prior art date
Application number
PCT/EP2007/058630
Other languages
English (en)
Inventor
Céline ROUVIERE
Matthias RÖBKE
Original Assignee
France Telecom
T-Mobile International Ag
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by France Telecom, T-Mobile International Ag filed Critical France Telecom
Publication of WO2008022990A1 publication Critical patent/WO2008022990A1/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/58—Message adaptation for wireless communication

Definitions

  • the invention relates to messaging systems.
  • Messaging systems provide messaging services over different kinds of communication networks.
  • Presently known messaging systems only permit an exchange of messages between messaging services based on short message service (“SMS") technology and messaging services based on IM-SIMPLE technology.
  • SMS technology is provided over circuit- switched and packet- switched networks.
  • Messaging services based on IM-SIMPLE technology are provided over a session initiation protocol (“SIP") technology over Internet Protocol (“IP”) multimedia networks.
  • SIP session initiation protocol
  • IP Internet Protocol
  • IM-SIMPLE stands for Instant Messaging - SIP for Instant Messaging and Presence Leveraging Extensions.
  • a "single service” messaging systems is a unique system which provides a unique messaging type.
  • a "multi service” messaging systems is a unique system which provides multiple messaging types.
  • single service messaging systems will also be called “conventional messaging systems”, the (messaging) services they provide “conventional (messaging) services”, and a terminal suitable for use of a single service messaging system will also be called a “conventional terminal” or “legacy terminal”.
  • Multi service messaging systems will also be called “converged IP messaging systems”, the (messaging) services they provide “convergent (messaging) services” and a terminal suitable for use of a converged IP messaging system will also be called a “convergent terminal”.
  • Examples of converged IP messaging systems are messaging systems based on SIP technology over IP technology. Put differently, today the single messaging services are hosted in “silos" where every service exists independent from each other. There is a discussion for a convergent messaging service, where the border between the individual (single) services will no longer exist. In such a convergent messaging service, the individual messaging functionality shall be a function of the user interface rather than the underlying technology.
  • the invention therefore proposes a method for transmitting messages between different messaging services of different communication networks, wherein in a first communication network a first messaging service is supported and in a second communication network a second messaging service is supported, wherein a border gateway node is employed which converts a message protocol used in the first messaging service to a second message protocol used in the second messaging service and routes the message from the first to the second messaging service and vice- versa.
  • this technical implementation bridges the gap between conventional messaging systems like MMS, SMS and IM on the one hand and an IP based, converged messaging service on the other.
  • the method as described above is characterized in that the border gateway node is capable of converting messages from and to the following message services: Short Message Service, Multimedia Messaging Service, Enhanced Message Service, Instant Messaging Service, IP Messaging Service.
  • the method as described above is characterized in that the border gateway node is connected to and communicates with a convergent messaging application server and is also connected to and communicates with service nodes of messaging services via the corresponding protocols defined for each messaging service.
  • the method as described above is characterized in that the border gateway node performs a protocol mapping of several elements of supported messaging protocols, comprising: messages, delivery & read reports, error codes responses, presence attributes in case of interworking with legacy IM, sessions (creation, modification, maintenance) in case of interworking with legacy IM.
  • the method as described above is characterized in that the border gateway node analyzes the structure and the substance of a message originating from the first messaging service and will route the message toward the second messaging service which can best handle and deliver the content to the user according to converting rules defined for each of the supported messaging service.
  • the method as described above is characterized in that the border gateway node questions a database which stores a capability list for each supported messaging service with which the gateway node interworks.
  • the method as described above is characterized in that the capability list comprises the following parameters: Size of Message, Integrated Content (text, audio, image, video, etc.), Nature of Message (session-based, immediate, deferred).
  • the method as described above is characterized in that the border gateway node stores the message context to be able to handle requests or responses within the same messaging communication such as delivery reports, read reports, or on-going session messaging.
  • the invention also relates to a system for transmitting messages between different messaging services of different communication networks, comprising: a first communication network supporting a first messaging service, a second communica- tion network supporting a second messaging service, a border gateway node connected to the communication networks and providing message transmission between the communication networks, the border gateway node comprising means for converting a first message protocol used in the first messaging service to a second message protocol used in the second messaging service and vice- versa.
  • the system as described above is characterized in that the border gateway node comprises a database which stores a capability list for each supported messaging service with which the gateway node interworks.
  • the system as described above is characterized in that the capability list comprises the following parameters: Size of Message, Integrated Content (text, audio, image, video, etc.), Nature of Message (session-based, immediate, deferred).
  • the invention also relates to data processing software program comprising a program code which performs a method as described above when it is executed on a suitable data processing system.
  • the invention also relates data processing program product comprising a program code which is executable on data processing system to performing a method as described above.
  • the invention also relates to a gateway comprising
  • the gateway according to the invention advantageously ensures interoperability between existing conventional messaging systems and new converged IP messaging systems.
  • the gateway provides interworking so that even if few users have new Instant messaging system ("IMS") devices for use with new converged IP messaging systems, these users can use these devices with any recipients (conventional or not).
  • IMS Instant messaging system
  • the gateway permits thus a coexistence of the existing conventional messaging systems and the new converged IP messaging systems.
  • the gateway provides a seamless service to the users of messaging systems and provides a bridge functionality to per- mit interoperability between the existing and the new messaging "worlds".
  • the gateway as described above is characterized in that it comprises
  • Figure 1 shows a border gateway node according to the invention connected to a SIP/IP Multimedia network and to a 2/2.5/3G network,
  • Figure 2 show a border gateway node according to the Invention connected to a SIP/IP Multimedia network and to messaging system SMS, MMS, and IM of a 2/2.5/3G network
  • Figure 3 shows a first implementation of the invention
  • Figure 4 shows a second implementation of the invention
  • Figure 5 is a schematic representation of two messaging systems networks capable of exchanging messages according to technologies known in the state of the art
  • Figure 6 is a schematic representation of two messaging systems interconnected via a gateway according to the invention
  • Figure 7 is a more detailed representation of the gateway according to the invention
  • Figure 8 is a flowchart representing the routing of a message sent by a first type of legacy terminal to a convergent terminal and
  • Figure 9 is a flowchart representing the routing of a message sent by a convergent terminal to a first type of legacy terminal.
  • the present invention proposes the implementation of an "intelligent" gateway function which serves as an interconnection between the individual messaging systems and their underlying communication networks.
  • the gateway function is realized as a border gateway node or gateway for short which comprises a function to route a message, originating from a convergent SIP/IP net- work to a target messaging system i.e. an MMS System, an SMS System etc, and vice versa.
  • a target messaging system i.e. an MMS System, an SMS System etc, and vice versa.
  • the border gateway node is connected to and communicates with a convergent messaging application server and is also connected to and communicates with the service nodes of legacy messaging systems via the corresponding protocols defined for each legacy service e.g. SMS, MMS, IMPS.
  • a convergent messaging application server is also connected to and communicates with the service nodes of legacy messaging systems via the corresponding protocols defined for each legacy service e.g. SMS, MMS, IMPS.
  • the main purpose of the border gateway node is to perform a protocol adoption or conversion between messaging services of existing communication networks of the 2 nd and 3 rd Generation and upcoming SIP/IP communication networks.
  • the border gateway node is responsible for the protocol mapping of several elements such as: - messages
  • border gateway Another purpose of the border gateway is a functionality to route messages from an SIP/IP multimedia network to a legacy messaging system e.g. MMS, SMS, IM etc.
  • a legacy messaging system e.g. MMS, SMS, IM etc.
  • the border gateway takes into account that every messaging system has its own capabilities.
  • the routing function of the border gateway node will analyze the structure and the substance of the message originating from the SIP/IP Multimedia Network and will route the message toward the messaging system which can best handle and deliver the content to the user according to converting rules defined for each of the supported legacy messaging systems.
  • the border gateway When applying this method the border gateway also considers timing options within the messages like immediate or deferred delivery options.
  • the border gateway node comprises a database which stores a capability list for each supported messaging system with which the gateway interworks.
  • This capability list will be composed by the following parameters (list not exhaustive):
  • the gateway shall also keep the message context to be able to handle requests/responses within the same messaging communication such as delivery/read reports, on-going session messaging. It shall store the required information that defines the message context like (list non exhaustive): Message ID: uniquely identifies the message
  • Transaction ID uniquely identify a couple of request/response regarding a message Messaging type: immediate session based or non session based, or deferred Legacy service used: SMS, MMS or IM
  • Session Context used in case of interworking with the IM legacy system. It may include the IMPS sessionID and the SIP session context (calllD, local & remote tags).
  • the border gateway node is preferable implemented as an application server (AS) connected to a SIP/IP Multimedia network 1 and to several messaging systems SMS 4, MMS 5 and IM 6 of a 2/2.5/3G network 2.
  • AS application server
  • SIP/IP Multimedia network 1 a SIP/IP Multimedia network 1
  • SMS 4 MMS 5 and IM 6 of a 2/2.5/3G network 2
  • SIP/IP multimedia network 1 and a 2/2.5/3G network 2
  • a Serving - Call/Session Control Function 3 is implemented in the SIP/IP network 1 which controls message forwarding form a sender 10 (Fig.
  • a border gateway node 7 (application server) is provided which is connected to related network elements of both the SIP/IP network 1 and the 2/2.5/3G network 2.
  • the border gateway node 7 is preferably situated in either one of the communication networks 1, 2 and is connected to an SMS service centre, an MMS service centre as well as to the S-CSCF 3 via a convergent messaging application server 8.
  • the convergent messaging application server 8 When a message is sent form a sender, located in the SIP/IP network 1, to a recipient located in the 2/2.5/3G network 2, the convergent messaging application server 8 receives the message form the S-CSCF 3 and is responsible for resolving the recipient address out of the message. If the recipient address is assigned to a user who has a communication terminal supporting only legacy messaging services, the message will be forwarded to the border gateway node 7.
  • the border gateway node 7 comprises a database which stores a capability list for each supported messaging system with which the gateway node interworks.
  • the message received from the convergent messaging application server 8 is analyzed and will be routed to the messaging system 4, 5 or 6 which capabilities fit best to the characteristics of the message and which is supported by the recipient's legacy terminal.
  • the border gateway node 7 also stores the messaging context to be able to handle requests or responses within the same messaging communication such as delivery reports, read report, or on-going session messaging.
  • an SIP/IP multimedia network 1 and a 2/2.5/3G network 2
  • GSM/UMTS mobile communication network for example a GSM/UMTS mobile communication network.
  • a Serving - Call/Session Control Function 3 is implemented in the SIP/IP network 1 which controls message forwarding form a sender to a recipient 110.
  • the 2/2.5/3G network 2 supports several legacy messaging services for example SMS 4, MMS 5 and IM services 6.
  • a border gateway node 7 (application server) is provided which is connected to related network elements of both the SIP/IP network 1 and the 2/2.5/3G network 2.
  • the border gateway node 7 is preferably situated in either one of the communication networks 1, 2 and is connected to an SMS service centre, an MMS service centre as well as to the S-CSCF 3 via a border gateway control function 9.
  • the S-CSCF When a message is sent form a sender, located in the SIP/IP network 1, to a recipient located in the 2/2.5/3G network 2, the S-CSCF is responsible for resolving the recipient address out of the message. If the recipient address is assigned to a user who has a communication terminal supporting only legacy messaging services, the message will be forwarded to the border gateway control function 9 which, based on specific rules, will address the message to the border gateway node 7.
  • the border gateway node 7 comprises a database which stores a capability list for each supported messaging system with which the gateway node interworks.
  • the message received from the convergent messaging application server 8 is analyzed and will be routed to the messaging system 4, 5 or 6 which capabilities fit best to the characteristics of the message and which is supported by the recipient's legacy terminal.
  • the border gateway node 7 also stores the messaging context to be able to handle requests or responses within the same messaging communication such as delivery reports, read report, or on-going session messaging.
  • the protocols used between the border gateway node 7 and the legacy systems 4, 5 and 6 can be two technical implementations regarding the protocols used between the border gateway node 7 and the legacy systems 4, 5 and 6:
  • MM4 interfaces and assigned protocols are implemented for a communication between partner systems. For example to communicate between MMS Systems 5 a MM4 interface with a dedicated MM4 protocol was developed. Similar interfaces, like UCP, SMPP and CIMD2 as well as HTTP and SSP, exists for the communication between SMS and Instant Messaging Systems 6. It is assumed that similar interfaces will exist for the communication between SIP/IP multimedia Systems. In this case, the border gateway should be connected to legacy systems via MM4-like protocol, e.g. MM4 interface to MMS, SSP for IMPS,
  • FIG. 5 shows a first messaging system 110.
  • a first terminal 19 can access the messaging system 110.
  • a second messaging system 13 as well as a second terminal 15 and a third terminal 17.
  • the systems 110 and 13 messages can be exchanged.
  • the systems will make use of different telecommunication networks (e.g. circuit- switched and packet-switched mobile networks).
  • telecommunication networks are also known to the person skilled in the art as underlying telecommunication networks and will not be discussed further here.
  • These telecommunication networks can be managed by different telecommunications operators.
  • a user of the terminal 15 it is possible for a user of the terminal 15 to exchange messages with the user of terminal 17. In this case only the messaging system 13 is used.
  • a user of terminal 15 it is also possible for a user of terminal 15 to send a message to the user of terminal 19.
  • the message may have different formats and may be of the type SMS, MMS or IMPS.
  • a computer program also called an SMS client
  • MMS client a computer program, also called an MMS client
  • the terminals 15, 17 and 19 may also represent convergent terminals that exchange messages via converged IP messaging systems. In this case, these systems will make use of underlying telecommunication networks such as one or more IP Multimedia Subsystem networks.
  • terminal 15 is a legacy terminal and terminal 19 is a convergent terminal.
  • Figure 6 shows a conventional messaging system 23 and a converged IP messaging system 21.
  • a legacy terminal 211 and a legacy terminal 29 are also shown.
  • the terminals 211 and 29 are capable of exchanging messages via the system 23.
  • Also shown in figure 6 are a convergent terminal 27 and a convergent terminal 213.
  • the terminals 27 and 213 are capable of exchanging messages via the converged IP messaging system 21.
  • a gateway 25 according to the invention is shown referenced with reference numeral 25.
  • the gateway 25 communicates with a convergent messaging Application Server ("AS") on the one hand and on the other hand with the conven- tional system 23 by means of the applicable protocol used within the conventional system, for instance MMS, SMS, IMPS, depending of the specific type of system 23.
  • the AS provides messaging functionalities like for example store and forward functionality, content adaptation and messaging session management.
  • a "messaging session” is an exchange of messages where the senders and recipients join together for a period of time. The session is established at some moment in time, continues for a finite duration and then is dissolved. Messages exchanged are associated together in the context of this session.
  • the gateway 25 is capable to do a protocol adoption between the conventional system 23 and the converged IP messaging system 21.
  • the gateway 25, or in fact in each case an element of the gateway 25, see below, is responsible for the protocol mapping of several elements such as: - messages,
  • gateway 25 is also responsible for
  • FIG. 7 shows the gateway 25 in more detail whereas the routing of a message via the gateway 25 from the network 23 over to the network 21 and vice versa will be explained in connection with the figures 8 and 9.
  • the gateway 25 shown in figure 7 comprises a routing engine 31.
  • the routing engine 31 The routing engine
  • Routing rules help the gateway 25 to find the route based on several criteria such as message type and terminal capabilities see below.
  • the gateway 25 also comprises a module 33 in which information is stored on each conventional network a message may potentially be routed to.
  • the module 33 will thus store the following information:
  • SMS Service name: SMS
  • Messaging type deferred, immediate non session based.
  • Message size limit for example 600 Kbytes
  • Message size limit in case of IMPS the message size limit is implementation specific: each operator may define a limit.
  • the gateway 25 also comprises a module 34 for protocol mapping.
  • This module 34 converts messages coming from the converged IP messaging system 21 into the corresponding protocol of the conventional system 23 and vice versa.
  • the module 34 is responsible for mapping of: - messages,
  • the module 34 is also able to communicate with the conventional system 23. Depending on the implementation chosen, the module may communicate via the following protocols:
  • system 23 is an SMS system
  • system 23 is an MMS system.
  • the gateway 25 gets the terminal capabilities from an external database, it could be provided with the user's profile that is stored in a Home Subscriber Server (“HSS").
  • HSS Home Subscriber Server
  • routing rules may be supplied in the form of an algorithm.
  • An example of such an algorithm is:
  • the gateway 25 comprises in addition a message context module 35.
  • the function of the module 35 is to route messages within the same messaging session between two messaging systems.
  • the module 35 also routes delivery and/or read reports related to a previous message exchanged between two messaging systems.
  • This module 35 contains all the information required to define the context of the messages. This information is necessary for the gateway 25 to route requests and/or responses within the same messaging communication.
  • the information in the module 35 will comprise a message identifier (ID) which identifies the message in a unique way, a transaction ID which identifies a couple of request/response regarding a message in a unique way, the messaging type information element which identifies the kind of messaging type i.e. deferred, immediate session- based or immediate non session-based and a service information element, which identifies the conventional network messaging service used, i.e. a messaging service based on SMS-, MMS- or IMPS -technology.
  • ID message identifier
  • a transaction ID which identifie
  • the information in the module 35 may also include for the converged IP messaging network a session ID and the session context i.e. call ID, local and remote tags. Call ID, and local and remote tags are all used to remember the context of the SIP session The call ID is defined in SIP.
  • the gateway 25 is used to route messages within a messaging session (e.g. IM kind of services) between a network over which conventional messaging services are provided and a network over which converged IP messaging services are provided
  • the module 33 is also responsible for mapping of - presence attributes and - sessions (creation, modification, maintenance)
  • FIGS. 8 and 9 will be used to explain the routing of a message via the gateway 25 from the system 23 to the system 21 and vice versa.
  • Figure 8 describes the different steps in the routing of an SMS message from a conventional messaging system to a converged IP messaging system.
  • a user composes during a step 41 an SMS message on his legacy terminal 29.
  • the user sends during a step 43 the message to a recipient.
  • SMS Centre an SMS Centre
  • the SMSC queries during a step 47 a Home Location Register (“HLR”) or an HSS to get routing information, like for example address resolution to know from which operator the recipient is.
  • HLR Home Location Register
  • HSS Home Location Register
  • the SMSC delivers during a step 49 the message to the recipient's terminal. 6. Otherwise, the SMSC forwards 411 the message to the gateway 25.
  • the gateway 25 analyses during a step 412 the message content for example, the message size, media type, checks during a step 413 the recipient's profile in the HSS, and checks during a step 415 the routing rules. It also checks during a step 417 the message context if existing. 8.
  • the gateway 25 converts during a step 419 the SMS message into the appropriate format to forward it to the converged IP messaging system.
  • the SMS message in the appropriate format will be called "convergent message" in the following description relating to figure 8.
  • the gateway 25 forwards during a step 421 the convergent message to the converged
  • BGCF Border Gateway Control Function
  • the BGCF forwards during a step 425 the message to a Serving - Call/Session Control Function ("S-
  • the CSCF which then forwards during the step 421 the convergent message to the converged IP messaging system.
  • the CSCF is used to process SIP signaling packets and the term CSCF is used to collectively designate several SIP servers or proxies. 12.
  • the converged IP messaging system processes during a step 427 the convergent message.
  • the converged IP messaging system sends during a step 429 the message to the S- CSCF which then forwards during a step 430 the message to the recipient's termi- nal.
  • Figure 9 describes the different steps in the routing of a message from a convergent messaging system to a conventional messaging system, in this case a messaging system providing messaging services based on SMS technology.
  • a user composes a text message (this message will be called a convergent message in the following explanation relating to figure 9) on his convergent terminal during a step 51.
  • the user sends the message to a recipient during a step 53.
  • the converged messaging system requests the HSS for the recipient's profile during a step 57.
  • the converged IP messaging system forwards the message to the gateway 25 during a step 59.
  • the converged IP messaging system forwards during a step 511 the message to the recipient.
  • a BGCF is connected to the gateway 25 a.
  • the message may be forwarded to the converged IP messaging system through the S-CSCF for some processing during a step 513. If so, once the message has been processed by the converged IP messaging system, the message is sent back to the S-CSCF during a step 515. b. Then the S-CSCF checks the user's profile when receiving the message during a step 517. c. The recipient appears to have a legacy terminal; the S-CSCF forwards the message to the BGCF during a step 519. d. The BGCF then forwards the message to the gateway 25 during a step 521. 5.
  • the gateway 25 analyses during a step 523 the message content (message size, type of media%), checks during a step 525 the recipient's profile in the HSS, checks during a step 527 the capabilities of the conventional messaging systems and checks during a step 529 the routing rules. It also checks during a step 531 the message context if existing.
  • the capabilities of the terminal comprise for instance screen size, supported codecs, and supported services like SMS, MMS.
  • the capabilities of the conventional messaging system comprise for instance maximum message size, type of messaging experience: elements to help the gateway to route the message. 6.
  • the gateway 25 chooses during a step 533 the appropriate conventional messaging system based on the above information.
  • the gateway 25 then converts during a step 535 the convergent message into an SMS message to forward it to the chosen conventional messaging system based on SMS technology. 8. The gateway 25 forwards during a step 537 the message to an SMS-Center.
  • the SMS-Center then transmits during a step 539 the message to the recipient's terminal.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé pour transmettre des messages entre différents services de messagerie de différents réseaux de communication. Dans un premier réseau de communication, un premier service de messagerie est pris en charge et, dans un second réseau de communication, un second service de messagerie est pris en charge. Un nœud de passerelle de frontière est employé pour convertir un protocole de message utilisé dans le premier service de messagerie à un second protocole de message utilisé dans le service de messagerie et route le message du premier au second service de messagerie et vice versa.
PCT/EP2007/058630 2006-08-22 2007-08-20 Passerelle et procédé pour router des messages WO2008022990A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP06291342.1 2006-08-22
EP06291342 2006-08-22

Publications (1)

Publication Number Publication Date
WO2008022990A1 true WO2008022990A1 (fr) 2008-02-28

Family

ID=38695473

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/058630 WO2008022990A1 (fr) 2006-08-22 2007-08-20 Passerelle et procédé pour router des messages

Country Status (1)

Country Link
WO (1) WO2008022990A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2109270A1 (fr) * 2008-04-07 2009-10-14 Nokia Siemens Networks Oy Procédé et dispositif de sélection d'une technologie de communication
WO2009127873A1 (fr) 2008-04-17 2009-10-22 Vodafone Group Plc Télécommunications basées sur des sessions
WO2012003668A1 (fr) * 2010-07-09 2012-01-12 中兴通讯股份有限公司 Procédé, système et serveur d'interfonctionnement pour transmettre un message

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1265408A1 (fr) * 2001-06-05 2002-12-11 Abb Research Ltd. Système et procédé pour la distribution de messages
US20030023691A1 (en) * 2001-07-27 2003-01-30 Knauerhase Robert C. Routing messages using presence information
GB2398969A (en) * 2003-02-27 2004-09-01 Ericsson Telefon Ab L M Message management between communication units with differing capabilities

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1265408A1 (fr) * 2001-06-05 2002-12-11 Abb Research Ltd. Système et procédé pour la distribution de messages
US20030023691A1 (en) * 2001-07-27 2003-01-30 Knauerhase Robert C. Routing messages using presence information
GB2398969A (en) * 2003-02-27 2004-09-01 Ericsson Telefon Ab L M Message management between communication units with differing capabilities

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2109270A1 (fr) * 2008-04-07 2009-10-14 Nokia Siemens Networks Oy Procédé et dispositif de sélection d'une technologie de communication
WO2009127873A1 (fr) 2008-04-17 2009-10-22 Vodafone Group Plc Télécommunications basées sur des sessions
WO2012003668A1 (fr) * 2010-07-09 2012-01-12 中兴通讯股份有限公司 Procédé, système et serveur d'interfonctionnement pour transmettre un message

Similar Documents

Publication Publication Date Title
KR101506029B1 (ko) 통합 메시징 서비스를 제공하기 위한 시스템과 방법
US7702342B2 (en) Method and system for implementing a message service based on IP multimedia subsystem
US8799373B2 (en) Method, system and apparatus for message interworking
US8788599B2 (en) Message delivery mechanism
JP5199461B2 (ja) Ｉｍｓおよび回路交換ネットワークにおけるメッセージルーティングの方法およびシステム
EP2028815A1 (fr) Procédé et système de délivrance de données de services de messagerie
US8244905B2 (en) Routing mechanisms for messaging applications using an enhanced gateway control function
US9246706B2 (en) Interworking between messaging services
US20090075684A1 (en) Apparatus and method for routing message service
CN101322381B (zh) 一种基于ip的消息路由方法、系统和设备
US20100087215A1 (en) Method, system, and message service interworking module for implementing message service interworking
US20090221310A1 (en) Message interworking method, system, entity and message delivery report processing method, system, the entity, terminal for message interworking
JP2016026450A (ja) ショートメッセージサービスをサポートする、ターミナルのケーパビリティのレポーティング
EP2058991A1 (fr) Procédé, système et appareil destinés à mettre en uvre l'interfonctionnement de messages
JP2007533245A (ja) 移動通信端末間のメッセージ連動システム及びその方法
EP2130388B1 (fr) Compatibilité de messagerie instantanée dans un système de communication
CN100589454C (zh) 一种基于ip传输的消息路由方法和系统
CN101115224A (zh) 用于ims网络的短信分叉方法及系统
US20100325192A1 (en) Cpm service provisioning system and method for interworking with non-cpm service
CN101370172B (zh) 不同类型的消息业务通信的处理方法、系统和设备
WO2008022990A1 (fr) Passerelle et procédé pour router des messages
CN100466760C (zh) 一种基于ip网络域消息业务的实现方法
KR101043696B1 (ko) 인스턴트 메시지 서비스 시스템 및 이동통신 단말기, 및 그 서비스방법
EP2136517B1 (fr) Livraison de messages courts
WO2009054614A1 (fr) Procédé d'interfonctionnement service cpm/service non cpm

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07802729

Country of ref document: EP

Kind code of ref document: A1