WO2003019884A1 - Systeme et procede de distribution d'informations a un utilisateur au moyen d'au moins deux technologies differentes - Google Patents
Systeme et procede de distribution d'informations a un utilisateur au moyen d'au moins deux technologies differentes Download PDFInfo
- Publication number
- WO2003019884A1 WO2003019884A1 PCT/FI2001/000738 FI0100738W WO03019884A1 WO 2003019884 A1 WO2003019884 A1 WO 2003019884A1 FI 0100738 W FI0100738 W FI 0100738W WO 03019884 A1 WO03019884 A1 WO 03019884A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- technology
- transferred information
- information
- transferred
- sms
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/184—Messaging devices, e.g. message centre
Definitions
- the invention relates in general to transmission of information in a world where multiple technologies are used to transmit information.
- it relates to a method to deliver quickly information using the best technology available.
- SMS Short Message Service
- GSM Global System for Mobile telecommunications
- UMTS Universal Mobile Telecommunication System
- SMS Short Message
- SGSN Serving GPRS Support Node
- MSC Mobile Switching Center
- the widely used Email system allows people to exchange information over the Internet. This system is fast and convenient but requires that both end users can use a computer having Internet access.
- the Internet access can be provided for example, by modem, ADSL, WLAN, or cellular systems (e.g. CDPD, GSM Circuit Switched Data, GPRS).
- Common Email product e.g. Microsoft Outlook
- unified messaging consists in converting a message from one technology into another.
- the unified messaging can convert a fax into an Email, an Email into a SMS, a SMS into a fax, an Email into a WAP (Wireless Application Protocol) message, a fax into a voice message and so on.
- WAP Wireless Application Protocol
- Multimedia Messaging defined in 3GPP (3 ld Generation Partnership Project) will also allow sending message containing text, picture, sound and/or video.
- the word technology is used to define a mean to transfer information between two end points supporting same protocol. Typically when information is exchanged between two terminals, both support the same technology.
- an intermediate element may adapt the transferred information from one technology to another (i.e. perform a protocol conversion). Examples of technologies are Email, SMS, WAP, Multimedia Messaging, fax, and paging.
- the object of the invention is to overcome the stated problem and make sure that the transferred information will be delivered to the receiver in a fast and practical way.
- the objects of the invention are achieved with a method and a system characterized in that the transferred information will be send from a device either simultaneously or with a certain delay at least two times through at least two technologies. It should be noted that sending through one technology could be direct or indirect. Therefore if the transferred information has been sent a first time using a first technology directly to a receiver device and a second time using same first technology to an intermediate server, and then sent using a second technology from the intermediate server to a receiver device, the transferred information has effectively been sent at least two times through at least two technologies.
- This method comprises the step of adapting the transferred information to the said technologies.
- the adaptation of the transferred information may consist in:
- the message carrying the same information sent through the other technology(s) will automatically be deleted.
- the objects of the invention are achieved with a mobile phone capable of sending an acknowledgement when an SMS has been read.
- the objects of the invention are achieved with a mobile phone capable of sending together with the transferred information, further configuration information indicating more than one technology and associated destination addresses where the transferred information should be sent.
- the objects of the invention are achieved with a WAP gateway comprising the functionality of
- the objects of the invention are achieved with an Email software comprising the functionality of
- an SMS-SC comprising the functionality of
- FIG. 1 illustrates the successful delivery of the information through SMS in the preferred embodiment.
- FIG. 2 illustrates the successful delivery of the information through Email in the preferred embodiment.
- FIG. 3 illustrates the architecture of the preferred embodiment, where only two technologies (Email and SMS) are used.
- Figure 4 illustrates the possible configuration of a user interface in alternative embodiments.
- Figure 5 illustrates the successful delivery of the information through SMS in the fifth embodiment.
- Figure 6 illustrates the architecture of one of the embodiment, where an intermediate server is used.
- a preferred embodiment of the invention is a method, and an inventive server characterized in that information is transferred using Email technology from the sender to an inventive server, and is sent by said inventive server to the receiver a first time using a normal Email sent and a second time using an SMS, both containing the same transferred information than the said first Email, or part of it.
- Figure 3 illustrates the architecture of the system according to the preferred embodiment, and depicts the sender computer 1 , the inventive server 2, the receiver Email Server 4, the SMS Service Center (SMS-SC) 3, and the receiver mobile phone 5.
- SMS-SC SMS Service Center
- the sender computer 1 is a normal computer capable of transferring information using Email technology.
- the inventive server 4 includes the inventive functionality which is characterized by the steps of
- the inventive server further has the capability to receive a message through Email.
- the SMS-SC 3 is, as defined in GSM and UMTS standards, a device capable of receiving an SMS, and storing the SMS until it has successfully transferred the SMS to the receiver mobile phone 5.
- the receiver mobile phone 5 is a normal mobile phone according to the GSM or UMTS standards.
- the mobile phone may be called MS (Mobile Station) or UE (User Equipment) in different specifications.
- the receiver Email server 4 is a normal Email server, storing the Email message until the receiver computer downloads it.
- FIGS 1 and 2 illustrate the signalling in accordance with the invention in a preferred embodiment.
- the first Email (message 1 in figures 1 and 2) is sent from a sender computer to a special address that is used to send urgent message to a receiver.
- This special address may for example be serge.haumont@urgent.mvcompany.com.
- This special address is handled by the inventive server.
- the inventive server duplicates the information contained in the said first Email and sends the said information simultaneously using the following technologies:
- SMS technology The message (message 2a in figure 1) is sent through SMS technology, using the mobile phone number of Serge Haumont. This number may be preconfigured (as explained in relation with figure 4) or may be read by an application from the internal company phone book.
- the message (message 2b in figure 1) is sent through Email technology to the normal Email address of the receiver (e.g., serge.haumont@mycompany.com).
- This Email message is sent using the option to request an acknowledgement when the Email is delivered and/or read.
- the receiver Email address may be easily deduced from said special address (e.g. taking "urgent" away) or may be preconfigured (as explained in relation with figure 4).
- the first case is described in relation with figure 1.
- the SMS is received by the mobile phone first, and an SMS acknowledgement is sent to the SMS-SC (current procedure).
- the SMS-SC indicates to the inventive server that the message was received by the mobile. This indication is sent through a new inventive interface. This interface may be internal if SMS-SC functionality is integrated in the inventive server.
- the Inventive server use the "Recall Message procedure" (message 4), well known and existing in many Email systems, to recall the Email.
- the Email is erased from the receiver Email server.
- the second case is described in relation with figure 2.
- the Email is delivered and/or read first (depending on the option set by the inventive server as explained in relation with figure 4).
- An acknowledgement is sent to the inventive server.
- the Inventive server then requests the SMS-SC to erase the SMS.
- This request is sent through a new inventive interface.
- This interface may be internal if SMS-SC functionality is integrated with the inventive server functionality.
- the SMS has not yet been received to the mobile phone so erasing the SMS when it is still stored in the SMS-SC is sufficient to prevent the receiver from receiving two times the transferred information. But the SMS may due to racing conditions or lost acknowledgement, have been received already by the MS.
- the SMS-SC may request the MS to erase the stored SMS. This may be implemented by adding such a request supporting such functionality in the SMS protocol, or by using another protocol such as Mexe (Mobile Execution Environment defined in GSM and UMTS standards).
- the message 2a and 2b are not sent simultaneously.
- the transferred information is first sent through a first technology (e.g. SMS in message 2a) and a timer is started.
- This timer should be configured so that the transferred information is likely to have been delivered through the first technology before the timer expires. For example, an SMS is likely to be delivered in less than 10 seconds, if the receiver mobile phone is switched on and under cellular coverage.
- the acknowledgement 3 is received before the timer expires, the transferred information is not sent through the second technology. If the acknowledgement 3 is not received before the timer expires, the transferred information is sent a second time through the second technology (e.g. Email in message 2b), and the method is after that similar to the first embodiment as shown on figures 1 and 2.
- a second technology e.g. Email in message 2b
- the sender of the information may be notified when the message has been successfully delivered (message 5 in figures 1 and 2).
- this acknowledgement may be sent using existing Email functionality to inform the sender when the message has been successfully delivered and/or read.
- the mobile phone is acknowledging the SMS when the SMS has been read (and not only delivered).
- an "SMS read acknowledgement" would have to be received by the SMS-SC, before the acknowledgement (message 3) can be sent to the inventive server by the SMS-SC.
- the capability of the mobile phone to send an acknowledgement when an SMS is read is a new feature. The sending of this acknowledgement can be triggered when the user presses the "read SMS" key on the mobile phone user interface. This acknowledgement could be implemented using the WAP technology, or an enhancement of the SMS standards.
- the sender of the information may be notified when the message has been read (and not only delivered) (message 5 in figures 1 and 2).
- this acknowledgement may be sent using existing Email functionality to inform the sender when the message has been successfully read.
- the SMS-SC may request the MS to erase the stored SMS. This may be implemented by adding such a request supporting such functionality in the SMS protocol, or by using another protocol such as Mexe (Mobile Execution Environment defined in GSM and UMTS standards).
- the transferred information cannot be completely sent through all the technologies that the inventive server can use.
- the said first Email sent in message 1 (figures 1 and 2) contains text (e.g. a question) and attachment (e.g. a word document containing background information for the question).
- the inventive server duplicates the transferred information contained in the said first Email and sends the said transferred information to the receiver using the following technologies:
- SMS technology Only part of the said transferred information (e.g. text part) is sent using an SMS message (message 2a in figure 1)
- Email technology All the said transferred information is sent using an Email message (message 2b in figure 1).
- the first case is described in relation with figure 5.
- the SMS is received by the mobile phone first, and an SMS acknowledgement is sent to the SMS-SC (current procedure).
- the SMS-SC indicates to the inventive server that the message was received by the mobile. This indication is sent through a new inventive interface. This interface may be internal if SMS-SC functionality is integrated with the inventive server functionality.
- the Inventive server does not recall the Email Message procedure as this message contains information which should be delivered to the receiver, and which was not in the SMS (e.g. a word attachment).
- the inventive server may optionally acknowledge the successful delivery of the message to the sender (message 4).
- the signalling also applies to the case where one of the technology do not support erasing the message. This may happen for example if an SMS-SC does not support the means to erase an SMS when requested by the sending entity, or if the Email software are not compatible.
- the second case is described in relation with figure 2.
- the Email is delivered and/or read first (depending on the option set by the inventive server).
- An acknowledgement is sent to the inventive server.
- the Inventive server then requests the SMS-SC to erase the SMS. This request is sent through a new inventive interface. This interface may be internal if SMS-SC functionality is integrated with the inventive server functionality.
- the figure 4 illustrates how the sending of transferred information through multiple technologies may be configured.
- the receiver address (e.g. serge.haumont@urgent.mycompany.com) may correspond a list of technologies. For each technology, the configuration indicates if this technology should be used to forward the transferred information, or not. On figure 4, this is illustrated by indicating yes or no in front of each technology. Then the inventive server will forward the transferred information sent to this receiver to all the technologies marked "yes". Moreover for every technology, the inventive server needs a destination address.
- the figure 4 illustrates the case where each destination address is manually configured. This configuration may be done by the receiver, by an administrator or by the sender. If the configuration is made by the sender, it implies that the technology used between the sender (1) and the inventive server (2) can support the transfer of this configuration or that the sender device and the inventive server are integrated in a single device.
- the configuration may contain also parameters adapted for various technologies. For example, it could request that messages sent through other technologies are erased when the message has been read or when it has been received (possible with Email technology, and SMS according to the fourth embodiment).
- acknowledgement can be sent when the transferred information has been delivered to the receiver and/or read by the receiver, this may as well be configured (as illustrated by the last line in figure 4).
- the inventive functionality is integrated in the Email software of the sender computer. It implies that the sender configures for every receiver typically stored in its address book a list of technologies with which the transferred information should be delivered. This could be done with an interface similar to the one depicted on figure 4. It also implies that the Email software is capable of sending message through multiple technologies. This may be done by supporting multiple technologies, or as explained in the eighth embodiment, by forwarding the transferred information to an intermediate server which will adapt it to another technology. In this embodiment, a separate address such as serge.haumont@urgent.mycompany.com is not needed. It is enough that the name of the receiver is linked, e.g. by the address book, to at least one address for every technology with which the transferred information will be sent.
- the inventive functionality is integrated in the Email software of the receiver Email server. It implies that the receiver or an administrator configures a list of technology with which the transferred information should be delivered. The address linked with every said technology may be configured manually, or by allowing the inventive functionality to retrieve it from an existing database. This could be done with an interface similar to the one depicted on figure 4. It also implies that the Email software is capable of sending message using multiple technologies. This may be done directly by supporting multiple technologies, or indirectly as further explained in relation to the eighth embodiment, by forwarding the transferred information to an intermediate server which will adapt it to another technology. In this embodiment, a separate address such as serge.haumont@urgent.mvcompany.com is not needed. It is enough that the Email address of the receiver is linked, e.g. by an address book, to at least one address for every other technology with which the transferred information will be sent.
- the inventive server uses an intermediate server to convert the message containing said information from one technology into another. Therefore, the inventive server may forward the transferred information at least two times using the same technology, but the receiver will receive the transferred information at least two times using at least two technologies. So the transferred information has effectively been sent at least two times using at least two technologies.
- the inventive server is integrated in the Email software of the sender computer (1).
- the inventive server functionality uses existing means to send an SMS using an Email software. These means consist in sending an Email using a special address (e.g. phone040123456@sms.mycompany.com) of an intermediate server (3) which converts the Email message into an SMS on the model of unified messaging.
- a special address e.g. phone040123456@sms.mycompany.com
- the sender device is a mobile phone and the inventive functionality is integrated within a WAP gateway.
- the transferred information is sent only once across the radio.
- An additional benefit is that the configuration parameter (as illustrated in figure 4) could easily be sent from the mobile phone to the inventive server functionality together with the transferred information using WAP technology.
- the WAP gateway may forward the transferred information, at least a first time using Email technology and a second time using SMS technology.
- this inventive functionality is integrated within an SMS Service Center. This avoids the need of a specific interface between the inventive server and an SMS-SC.
- the invention presented here bring multiple advantage to the user:
- the transmitted information will be seen only once by the receiver.
- the word "read” has been used in this invention to describe that the user gets to know the content of the transferred information. Therefore the word “read” should be understood in a broad sense in particular in the case of multimedia messages which may include video, picture and voices.
- multimedia messages which may include video, picture and voices.
- the application will read the video file and the video will be displayed to the user.
- Another example is a receiver checking its voice message using a normal phone call. In this case, the voice message is read by the voice mail server and sent through the PSTN (or ISDN or GSM) network to the receiver who listens it.
- the receiver may also receive the transferred information using a single device supporting many technologies, and/or using many devices supporting each one technology.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/FI2001/000738 WO2003019884A1 (fr) | 2001-08-22 | 2001-08-22 | Systeme et procede de distribution d'informations a un utilisateur au moyen d'au moins deux technologies differentes |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/FI2001/000738 WO2003019884A1 (fr) | 2001-08-22 | 2001-08-22 | Systeme et procede de distribution d'informations a un utilisateur au moyen d'au moins deux technologies differentes |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003019884A1 true WO2003019884A1 (fr) | 2003-03-06 |
Family
ID=8555919
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/FI2001/000738 WO2003019884A1 (fr) | 2001-08-22 | 2001-08-22 | Systeme et procede de distribution d'informations a un utilisateur au moyen d'au moins deux technologies differentes |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2003019884A1 (fr) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1299480C (zh) * | 2005-02-25 | 2007-02-07 | 钟志军 | 通过电子邮箱地址向移动电话发送短消息的装置和方法 |
US7245902B2 (en) | 2002-01-16 | 2007-07-17 | 2 Ergo Limited | Secure messaging via a mobile communications network |
EP1874066A1 (fr) * | 2006-06-30 | 2008-01-02 | Nortel Networks Limited | Livraison de SMS par un sous-système multimédia |
US7557738B2 (en) | 2006-07-14 | 2009-07-07 | Arc Innovations Limited | Text encoding system and method |
WO2011141319A1 (fr) * | 2010-05-12 | 2011-11-17 | Nokia Siemens Networks Oy | Diffusion améliorée de messages courts |
US8271024B1 (en) | 2003-11-26 | 2012-09-18 | Genband Us Llc | Messaging service interworking |
US9118574B1 (en) | 2003-11-26 | 2015-08-25 | RPX Clearinghouse, LLC | Presence reporting using wireless messaging |
EP4429196A1 (fr) * | 2023-03-10 | 2024-09-11 | T-Mobile Innovations LLC | Système de notification unifié |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1995012933A1 (fr) * | 1993-11-01 | 1995-05-11 | Telefonaktiebolaget Lm Ericsson | Systeme et procede de transmission de messages pour systeme de radiocommunications |
US5742905A (en) * | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Personal communications internetworking |
EP0854655A2 (fr) * | 1997-01-21 | 1998-07-22 | Motorola, Inc. | Client-serveur de communications multi-format et méthode |
WO2000041533A2 (fr) * | 1999-01-11 | 2000-07-20 | Infospace, Inc. | Client ameliore et procede de routage de messages permettant d'unifier les communications |
EP1022670A2 (fr) * | 1998-12-29 | 2000-07-26 | Pitney Bowes Limited | Système de messagerie électronique dynamique |
WO2000060837A1 (fr) * | 1999-04-07 | 2000-10-12 | Parable Telecommunications Group Plc | Systeme et procede de traitement de donnees de telecommunications |
EP1104964A1 (fr) * | 1999-12-02 | 2001-06-06 | Sony International (Europe) GmbH | Messagerie instantanée |
-
2001
- 2001-08-22 WO PCT/FI2001/000738 patent/WO2003019884A1/fr active Application Filing
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1995012933A1 (fr) * | 1993-11-01 | 1995-05-11 | Telefonaktiebolaget Lm Ericsson | Systeme et procede de transmission de messages pour systeme de radiocommunications |
US5742905A (en) * | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Personal communications internetworking |
EP0854655A2 (fr) * | 1997-01-21 | 1998-07-22 | Motorola, Inc. | Client-serveur de communications multi-format et méthode |
EP1022670A2 (fr) * | 1998-12-29 | 2000-07-26 | Pitney Bowes Limited | Système de messagerie électronique dynamique |
WO2000041533A2 (fr) * | 1999-01-11 | 2000-07-20 | Infospace, Inc. | Client ameliore et procede de routage de messages permettant d'unifier les communications |
WO2000060837A1 (fr) * | 1999-04-07 | 2000-10-12 | Parable Telecommunications Group Plc | Systeme et procede de traitement de donnees de telecommunications |
EP1104964A1 (fr) * | 1999-12-02 | 2001-06-06 | Sony International (Europe) GmbH | Messagerie instantanée |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7245902B2 (en) | 2002-01-16 | 2007-07-17 | 2 Ergo Limited | Secure messaging via a mobile communications network |
US8271024B1 (en) | 2003-11-26 | 2012-09-18 | Genband Us Llc | Messaging service interworking |
US9118574B1 (en) | 2003-11-26 | 2015-08-25 | RPX Clearinghouse, LLC | Presence reporting using wireless messaging |
CN1299480C (zh) * | 2005-02-25 | 2007-02-07 | 钟志军 | 通过电子邮箱地址向移动电话发送短消息的装置和方法 |
EP1874066A1 (fr) * | 2006-06-30 | 2008-01-02 | Nortel Networks Limited | Livraison de SMS par un sous-système multimédia |
US7557738B2 (en) | 2006-07-14 | 2009-07-07 | Arc Innovations Limited | Text encoding system and method |
AU2007273323B2 (en) * | 2006-07-14 | 2010-12-23 | Arc Innovations Limited | Text encoding system and method |
WO2011141319A1 (fr) * | 2010-05-12 | 2011-11-17 | Nokia Siemens Networks Oy | Diffusion améliorée de messages courts |
US8823767B2 (en) | 2010-05-12 | 2014-09-02 | Nokia Siemens Networks Oy | Delivery of short messages |
EP4429196A1 (fr) * | 2023-03-10 | 2024-09-11 | T-Mobile Innovations LLC | Système de notification unifié |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4255140B2 (ja) | 情報の無線検索方法 | |
JP4437124B2 (ja) | マルチメディアメッセージ通信サービス | |
EP2063590B1 (fr) | Procédé et système de transmission de courrier électronique et serveur de courrier électronique poussé | |
US7113767B2 (en) | Instant video- and voicemail messaging method and means | |
US7610043B2 (en) | Duplicate notification message processing method in terminal | |
JP4801649B2 (ja) | 無線lan上でマルチメディアメッセージサービスを確立するための無線通信方法およびシステム | |
TW200412103A (en) | Apparatus and method for transparent and integrated wireless messaging in a multi-mode environment | |
KR20030070914A (ko) | 멀티미디어 메시징 서비스 루팅 시스템 및 방법 | |
JP2011527467A (ja) | 拡張されたメッセージングプラットフォーム | |
US8909129B2 (en) | Method for transmitting data, particularly having multimedia contents, in a mobile communication network | |
CN101577867B (zh) | 多媒体消息业务中的推送消息发送方法、设备及系统 | |
EP1655915B1 (fr) | Procédé pour la gestion des notifications dupliquées dans un service de messagerie multimédia | |
JP4368885B2 (ja) | ショートメッセージ再送システム、ショートメッセージ再送方法 | |
WO2003019884A1 (fr) | Systeme et procede de distribution d'informations a un utilisateur au moyen d'au moins deux technologies differentes | |
JP2004532485A (ja) | マルチメディアレファレンスを有するメッセージのハンドリングのための方法 | |
CN1675903B (zh) | 阻塞不需要的消息的方法和系统 | |
US20040078439A1 (en) | Messaging method | |
JP2004532567A (ja) | マルチメディアメッセージサービス(mms)におけるメッセージング | |
CN100334892C (zh) | 一种多媒体消息转发方法 | |
JP2001077843A (ja) | メール配信システム | |
KR100783265B1 (ko) | 무선 통신망에서 통화 발신 정보를 멀티미디어 메시지로제공하는 시스템 | |
GB2425437A (en) | Sending MMS/SMS messages to e-mail addresses |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ PH PL PT RO SD SE SG SI SK SL TJ TM TR TT TZ UG US UZ VN YU ZA Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZW AM AZ BY KG KZ MD TJ TM AT BE CH CY DE DK ES FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW MR NE SN TD TG Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |