EP2297645A1 - Plateforme de messagerie étendue - Google Patents

Plateforme de messagerie étendue

Info

Publication number
EP2297645A1
EP2297645A1 EP09773867A EP09773867A EP2297645A1 EP 2297645 A1 EP2297645 A1 EP 2297645A1 EP 09773867 A EP09773867 A EP 09773867A EP 09773867 A EP09773867 A EP 09773867A EP 2297645 A1 EP2297645 A1 EP 2297645A1
Authority
EP
European Patent Office
Prior art keywords
message
server
delivery channel
delivery
channel
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP09773867A
Other languages
German (de)
English (en)
Other versions
EP2297645A4 (fr
EP2297645B1 (fr
Inventor
John Anthony Underwood
Christopher Edward Keys
Markku Kero
Rainer Leinonen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
3rd Brand Pte Ltd
Original Assignee
3rd Brand Pte Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 3rd Brand Pte Ltd filed Critical 3rd Brand Pte Ltd
Publication of EP2297645A1 publication Critical patent/EP2297645A1/fr
Publication of EP2297645A4 publication Critical patent/EP2297645A4/fr
Application granted granted Critical
Publication of EP2297645B1 publication Critical patent/EP2297645B1/fr
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/23—Reliability checks, e.g. acknowledgments or fault reporting
    • 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/14—Multichannel or multilink protocols
    • 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/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • 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 present application relates to systems and methods for providing extended messaging services.
  • the present invention relates to providing extended messaging and/or file sharing services within a mobile communications network.
  • SMS Short Message Service
  • SMSC Short Message Service Centre
  • MAP Mobile Application Part
  • Short messages can be encoded using a variety of alphabets: the default GSM 7-bit alphabet (shown below), the 8-bit data alphabet, and the 16-bit UTF-16/UCS-2 alphabet.
  • SMSC Short Message sizes of 160 7-bit characters, 140 8-bit characters, or 70 16-bit characters (including spaces).
  • Support of the GSM 7- bit alphabet is mandatory for GSM handsets and network elements,[15] but characters in languages such as Arabic, Chinese, Korean, Japanese or Cyrillic alphabet languages (e.g. Russian) must be encoded using the 16-bit UCS-2 character encoding (Unicode). Routing data and other metadata is additional to the payload size. If a recipient is not reachable, the SMSC queues the message for later retry. Some SMSCs also provide a "forward and forget" option where transmission is tried only once. Accordingly message delivery is best effort, so there are no guarantees that a message will actually be delivered to its recipient and delay or complete loss of a message is not uncommon, particularly when sending between networks.
  • IM Instant Messaging
  • MIM Mobile Instant Messaging
  • IM Instant Messaging
  • SMS Short Message Service
  • a local PC backup/archive may be required to provide any sort of message backup capability and then the process is manual in nature.
  • a user wishing to save messages must perform this manual process prior to deleting messages on their mobile device to free up space for new messages.
  • an extended message system said system including: at least one server configured to receive a message from a originating device for delivery to at least one recipient device via a first delivery channel; and wherein the at least one server is further configured to select an alternate delivery channel in the event that delivery of the message via the first delivery channel cannot be effected;
  • the originating device may be configured to select an alternate delivery channel in the event that the delivery of the message via the first delivery channel cannot be effected.
  • the messaging network may be considered to comprise an Originating Device, at least one server and one or more recipients (these may be mobile devices or Email or other recipient types).
  • a message may be considered to be a textual message or may be some other type of data message or file such as, but not limited to, a picture, music file or document.
  • the originating device may include one or more predefined rules sets, for governing how the message is transmitted.
  • the rule set may include information relating to the period of time the originating device waits before resending the message on the first delivery channel, how often and for how long the retries continue on the first delivery channel before switching to an alternate delivery channel.
  • the message may include a retry counter which is incremented on each attempt of the originating device to deliver the message to the at least one server.
  • the system may enable the user to reconfigure the rule set in accordance with their preferences.
  • the originating device may display an indicator to the user providing information on the delivery status of the message.
  • the first delivery channel may be an Internet Protocol (IP) based messaging channel and the message may be an instant message or chat message.
  • IP Internet Protocol
  • the alternate delivery channel is an SMTP, MIME, POP, IMAP or similar messaging channel.
  • the alternate delivery channel may be an SS7 or similar messaging channel.
  • the originating device or the at least one server may reformat the message to comply with the alternate delivery channel's messaging standard.
  • the originating device is adapted to receive an acknowledgement message from said at least one server on receipt of the message via the first messaging channel.
  • the originating device applies the business rules and user settings of the sender to determine the action to take. Typically this may include a defined number of retry attempts and subsequently a switch to the alternate delivery channel on which delivery is to be affected. It may also require the intervention of the user to determine what action to take. Further it may include a delivery by the primary delivery channel to the server with instructions included in the message header to direct the server to switch to the secondary delivery channel.
  • the at least one server will first attempt to deliver the message using the delivery channel specified by the user of the originating device.
  • the server may include one or more predefined rules sets, for governing how the message is transmitted.
  • the rule set may include information relating to the period of time the at least one server waits before resending the message on the first delivery channel, how often and for how long the retries continue on the first delivery channel before switching to an alternate delivery channel.
  • the message may include a retry counter which is incremented on each attempt of the server to deliver the message to the at least one recipient device.
  • the system may enable the user to reconfigure the rule set in accordance with their preferences.
  • the server may divest the responsibility to manage retries to the originating device.
  • the at least one server is adapted to receive an acknowledgement message from said at least one recipient device on receipt of the message via the first messaging channel.
  • the system may also be configured such that the at least one server notifies the originating device of the receipt of the message by the least one recipient device. This end to end notification is only required to provide assured delivery when the originating device is managing the retry process. Where this is not the case and the at least one server remains in control of the process and maintains the assuredness of delivery it is not mandatory for the receipt acknowledgement to be returned to the originating device.
  • the acknowledgement message may be any suitable format, provided that it contains at a minimum, sufficient information to associate the acknowledgement with the message.
  • the acknowledgement may for example include a serial number, a timestamp, a unique ID or the like. The unique ID may be generated from the serial number and time stamp associated with the receipt of the message.
  • the server may simply pass through the acknowledgement of receipt to the originating device.
  • the originating device takes more responsibility for driving the assurance of delivery to the recipient device.
  • the server applies the business rules and user settings of the sender and recipient to determine the action to take. Typically this may include a defined number of retry attempts and subsequently a switch to the alternate delivery channel on which delivery is to be affected.
  • the at least one server may be coupled to a database.
  • the server maybe configured to periodically write a log of each attempt to deliver a message, along with network specific information to the database.
  • the database may also be used as a message repository for all messages passing through the delivery server.
  • the system may provide the user with a suitable interface to access all messages sent from and received by the user.
  • a method for routing messages including the steps of: receiving at a server a message from an originating device for delivery to the at least one recipient; forwarding the message to the at least one recipient device via a first delivery channel awaiting receipt of acknowledgement message from said least one recipient device, and in the event that no acknowledgment is received message the server resend the message to said at least one recipient device via an alternate delivery channel.
  • the method may include the step of re-sending the message via the first delivery channel a predetermined number of times before resending the message via the alternate delivery channel.
  • the step of resending the message via the first delivery channel includes the step of incrementing a retry counter associated with the message.
  • the method may optionally include the step of initiating at the originating device transfer of the message via an alternate delivery channel in the event of failure to affect delivery via the first delivery channel prior (i.e. originating device has ability of to override retry of first delivery channel).
  • the step of forwarding the message via the alternate delivery channel further includes the step of reformatting the message to comply with the channel's messaging standard.
  • the method may also incorporate processing on the receiving device to identify duplicate messages.
  • messages may be sent on several occasions before the sending at least one server or originating device gets a response back to indicate successful receipt. Where this is due to the receipt failing to be transmitted, rather than the message itself, the result can be duplicate messages arriving on the receiving device. This is addressed by utilising the unique identifier contained in messages as described above. The receiving device looks at the unique identifier in previously received messages and does not re-display a message previously received and displayed.
  • an indicator may be displayed to the user indicating the delivery status of a message.
  • message retries are controlled by the originating device, there is preferably a warning to a user attempting to exit from the sending application that a message has not yet been confirmed as being delivered and that retries are still outstanding.
  • FIG. 1 is a schematic block diagram of an extended message system according to one embodiment of the present invention.
  • FIG. 2 is a flow chart depicting the signalling between various points in the messaging system according to one embodiment of the invention
  • a message may be considered to be a textual message or may be some other type of data message or file such as, but not limited to, a picture, music file, or document.
  • an originating device 101 e.g. mobile hand set, PDA, portable computer or the like
  • the messaging application is a mobile IM application.
  • the user selects one or more recipients 107 from their contact or Buddy List 103.
  • the recipients 107 may be members of the same network 104 or members of a different network 106.
  • the device's messaging application 102 then forwards the message via the network 104 to the delivery server 105 complete with information regarding the intended recipients and the preferred delivery channel to be employed for message to the recipient device(s) 107.
  • the preferred delivery channels can be data (Internet Protocol/IP) based messaging (e.g.
  • the originating device 101 Once the originating device 101 has forwarded the message to the delivery server 105 it expects to receive an acknowledgment message/packet from the delivery server 105 confirming the receipt of the message.
  • the specific format of the acknowledgment is not critical provided it can be readily associated with the original sent message.
  • the originating device 101 fails to receive an acknowledgment it waits for a predetermined time, based on a predefined rule set, before attempting to resend the message.
  • the predefined rule set not only defines the period of time the device waits before resending the message but they also define how often and for how long the retries will continue.
  • the rule set may be configured to allow the sending device 101 a maximum of 10 retries, each retry being at 5 minute intervals after the original attempt to send the message. After exhausting the maximum number of reties the sending device 101 is still unable to complete message delivery, it may then after a predetermined period attempt to affect delivery via an alternate method to route the message to the delivery server 105.
  • the originating device client application will inform user as to the delivery status of the message and provide alternate delivery options prior to completing the log off or exit.
  • the delivery sever 105 in this case is coupled to at least one email server 108 and/or at least one messaging centre (SMSC 1 MMSC) 109 to provide a plurality of redundant delivery channels.
  • SMSC 1 MMSC messaging centre
  • the delivery server will switch to the next preferred delivery format.
  • the delivery server 105 may switch from IM to SMS to effect delivery of the message.
  • the originating device 101 may prompt the user to select an alternative delivery channel in the event the message cannot be delivered via the primary deliver channel selected by the user.
  • a user may select a delivery channel that the server knows is not available for example the user may select IP based messaging but the server knows the receiving device is unavailable to receive this type of message.
  • the delivery server 105 converts the message to an alternate message format (SMS, email etc) for delivery via an alternate delivery channel (e.g. email gateway 108, SMSC109).
  • SMS alternate message format
  • the primary delivery channel may include a set of instructions included in the message header to direct the server to switch to the secondary delivery channel.
  • a message is sent (and resent) by the delivery server 105, it carries a retry counter, which is counted from 0 (initial delivery) upwards. For each retry, the counter is then incremented to indicate retrials. Based on the rule set configured on the delivery server, the delivery server can then choose to attempt alternative delivery methods for a message based on the retrial count. This allows for converting the message to an SMS, MMS or email after a specified number of retries. In the original iteration, a message will be attempted for delivery via SMS starting from the third retrial.
  • a log of each attempt to deliver the message along with network information including cell site etc is stored by the server in database 110.
  • the delivery server 105 may be coupled to the HLR (Home Location Register) of the network 104.
  • HLR Home Location Register
  • a log record is written to the database 110.
  • the log not only includes information on the unsuccessful delivery it also includes the HLR information relating to the receiving mobile device.
  • Subsequent analysis of the data thus provided using standard data analysis tools can reveal specific network areas that require maintenance and or upgrades. Such logging can identify specific carrier coverage issues or other network inadequacies.
  • the database 110 can be used as a storage facility for user messages which is discussed in greater detail below.
  • Fig 2 depicts the signalling employed by the messaging system 100 according to one embodiment of the present invention.
  • the delivery server 105 needs to firstly identify the intended recipient(s) 107 and the users preferred delivery channel.
  • Each client device (originating or receiving 101 , 107) in the network communicates with the server using a time-based heartbeat transaction 213, this allows the server to track the presence of all devices in the network.
  • each client device sends a heartbeat to the server every 10 minutes. If the server does not receive a heartbeat when it is expected, it marks that client device as offline.
  • the heartbeat transaction is not only utilised to show the presence of the client device but the level of services currently available to the client device.
  • the server checks to confirm the recipient 107 is connected to the server and is available to receive messages via the information provided through recipient device's heartbeat.
  • the receiving device 107 may not be ready or able to receive an IM message
  • the delivery server 105 attempts to send the message to each recipient using the applicable alternate delivery channel such as an SMS 209, Email 207 or other suitable messaging format.
  • a confirmation/acknowledgment message is expected from the recipient (or delivery agent, as the case may be in the case of SMS and Email) as the message has been delivered. This will then be passed on to the original sender of the message.
  • the specific format of the confirmation message is not critical provided it allows the system to associate the confirmation with the originally sent message.
  • originating device 101 forwards the IM message 201 to the delivery server 105 for delivery to the recipient device 107 via the primary deliver channel 202.
  • the delivery server 105 sends an acknowledgement message back to the originating device 101.
  • the delivery server on-sends the IM message to the recipient device 107.
  • the recipient device 107 then sends back an acknowledgement message 203 to the delivery server 105, the delivery server 105 then optionally advises the sending device 101 of successful end-to-end delivery of the message 204.
  • the primary delivery 202 channel is unavailable delivery server 105 then attempts to route the message via an alternate delivery channel such as email 205 via email gateway 108, or SMS 206 via SMSC 109.
  • the delivery server 105 converts the message from its native format to the appropriate email format before forwarding the message 205 to the email gateway. Email gateway 108 then forwards the message 207 to the recipient device 107, the recipient device then sends back an acknowledgement message 208.
  • SMS or MMS is selected as the alternate delivery channel the delivery server 105 converts the message form its native format to an appropriately sized SMS packet before forwarding the message the SMSC 109. Message truncation may optionally be performed in this instance however in the current embodiment of the invention as many SMS message packets are sent as are required to deliver the message in its entirety to the recipient device(s) 107.
  • the SMSC 109 then forwards the message 209 to the recipient device 107, the recipient device then the sends back an acknowledgement message 210.
  • the server does not look for a confirmation for messages 211, 212 (shown in dashed outline) sent via email or SMS via email servers and/or SMSC/SMS gateway since both of these formats are considered acceptably reliable.
  • a confirmation for messages 211, 212 shown in dashed outline
  • SMSC/SMS gateway since both of these formats are considered acceptably reliable.
  • the routing of messages from the delivery server 105 to the recipient device 107 may be done via a set of predetermined rules implemented on the delivery server 105.
  • the rule set governs the number of retry attempts; the alternate delivery channels to be employed and their order; the time for which retries will be continued; the frequency of retry attempts.
  • the following table shows one example of a rule set which is applied for routing messages with a textual messaging system according to one embodiment of the present invention:
  • Table 1 exemplary rule set for message routing
  • the alternate delivery channel may be configured as MMS or some other file transfer protocol.
  • the user may configure the rule set to suit their preferences e.g. via an online interface or the like.
  • the change in rule status is then communicated to the delivery server which modifies the operation of the rule set for the particular user.
  • the user can define how a message is routed to them based on their status setting, their offline settings and their current network presence.
  • the heartbeat transaction informs the delivery server of the user's presence.
  • the availability of the user to receive messages is determined based on a combination of the user defined Status setting, their Offline Settings" and whether they are connected (logged in):
  • Email routing which routes messages to email when the user is not logged on to a client device
  • the system may also present the user with the ability to assign various characteristics to a message, for example Message importance.
  • Message importance can be set to Normal or High by the sender.
  • the message importance is held as data in the message header and is used throughout the network to determine message processing. If the user selects High importance, message delivery rules through the network, server infrastructure and receiving device, treat the message differently. Typically High Importance messages are charged by the carrier at a premium rate.
  • the database 110 may be used as a remote storage facility.
  • This "StorelT” functionality provides a full message archive facility of all messages sent to and from the delivery server 105. Access to messages is provided via a website. A user can log in and then use extensive search facilities and tagging to access their messages. Sufficient storage is provided such that the user need never delete a message.
  • the delivery server writes each message sent and received in an asynchronous process to a data storage facility 110. Messages are typically written separately for each sender/recipient. Storage requirements can be reduced by writing a single copy of a message and using links to associate that message with multiple send/receivers. Tradeoffs would be accepted in this approach with slow search performance.
  • Tagging of message can be performed automatically if for example the message contains certain characteristics: • Contain a web link
  • the "StorelT” user interface also provides the ability via a PC version of the messaging client, to forward and reply to messages.
  • the web interface may include the following:
  • the management of retries may be performed by the originating device 101 instead of the delivery server 105.
  • the acknowledgement of receipt may by-pass the delivery server 105.
  • the originating device 101 is configured to provide the assurance of delivery to the recipient device 107.
  • the originating device 101 may be configured to display an indicator to the user providing information on the delivery status of the message.
  • the originating device 101 may be configured to select an alternate delivery channel in the event that the delivery of the message via the first delivery channel cannot be effected.
  • the originating device or the at least one server may reformat the message to comply with the alternate delivery channel's messaging standard.
  • the primary delivery channel may be further configured to send a message to the delivery server 105; the delivery server 105 including instructions in the message header to direct the server to switch to the secondary delivery channel.
  • An indicator may be displayed to the user to indicate the delivery status of a message.
  • message retries are controlled by the originating device, there is a warning to a user attempting to exit from the sending application that a message has not yet been confirmed as being delivered and that retries are still outstanding.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Seeds, Soups, And Other Foods (AREA)
  • Coloring Foods And Improving Nutritive Qualities (AREA)

Abstract

L'invention porte sur un système de messagerie, comprenant au moins un serveur configuré pour recevoir un message, provenant d'un dispositif d'origine, devant être distribué à au moins un dispositif destinataire par l'intermédiaire d'un premier canal de distribution ; le ou les serveurs étant en outre configurés pour sélectionner un canal de distribution de remplacement dans le cas où la distribution du message par l'intermédiaire du premier canal de distribution ne peut pas être effectuée. L'invention décrit en outre un procédé pour router des messages consistant à recevoir au niveau d'un serveur un message provenant d'un dispositif d'origine devant être distribué à au moins un destinataire ; à transférer le message au ou aux dispositifs destinataires par l'intermédiaire d'un premier canal de distribution ; à attendre la réception d'un message d'accusé de réception provenant dudit ou desdits dispositifs destinataires et, dans le cas où aucun message d'accusé de réception n'est reçu, le ou les serveurs envoient de nouveau le message audit ou auxdits dispositifs destinataires par l'intermédiaire d'un canal de distribution de remplacement.
EP09773867.8A 2008-07-04 2009-06-30 Plateforme de messagerie étendue Not-in-force EP2297645B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SG200805072-6A SG157991A1 (en) 2008-07-04 2008-07-04 Extended messaging platform
PCT/SG2009/000238 WO2010002354A1 (fr) 2008-07-04 2009-06-30 Plateforme de messagerie étendue

Publications (3)

Publication Number Publication Date
EP2297645A1 true EP2297645A1 (fr) 2011-03-23
EP2297645A4 EP2297645A4 (fr) 2014-12-24
EP2297645B1 EP2297645B1 (fr) 2016-03-02

Family

ID=41466220

Family Applications (1)

Application Number Title Priority Date Filing Date
EP09773867.8A Not-in-force EP2297645B1 (fr) 2008-07-04 2009-06-30 Plateforme de messagerie étendue

Country Status (18)

Country Link
US (1) US9237428B2 (fr)
EP (1) EP2297645B1 (fr)
JP (1) JP5246332B2 (fr)
KR (1) KR101291324B1 (fr)
CN (1) CN102027461B (fr)
AU (1) AU2009266360C1 (fr)
BR (1) BRPI0905730A2 (fr)
CA (1) CA2707467C (fr)
CO (1) CO6300817A2 (fr)
EG (1) EG26026A (fr)
ES (1) ES2574637T3 (fr)
MX (1) MX2010005978A (fr)
MY (1) MY154291A (fr)
RU (1) RU2459240C2 (fr)
SG (1) SG157991A1 (fr)
TW (1) TWI455530B (fr)
UA (1) UA100722C2 (fr)
WO (1) WO2010002354A1 (fr)

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100004146A (ko) * 2008-07-03 2010-01-13 삼성전자주식회사 이동통신 시스템에서 음영 지역의 단말의 통신을 위한 장치및 방법
CN101977396B (zh) * 2010-10-22 2014-11-05 中兴通讯股份有限公司 多媒体消息业务中实现网元业务切换的系统及方法
US9014343B1 (en) 2011-02-24 2015-04-21 Sprint Communications Company L.P. Recalling user-generated messages
US9137191B2 (en) * 2011-03-17 2015-09-15 Microsoft Technology Licensing, Llc Messaging for notification-based clients
US8924495B2 (en) * 2011-03-31 2014-12-30 Loment, Inc. Delivery control for HTTP communications among multiple end user communication devices
US8799385B2 (en) * 2011-03-31 2014-08-05 Loment, Inc. Delivery control for email communicated among multiple end user communication devices
US8799386B2 (en) * 2011-03-31 2014-08-05 Loment, Inc. Delivery control for email communicated among multiple end user communication devices
JP5604354B2 (ja) * 2011-04-05 2014-10-08 株式会社日立製作所 加入者終端装置による接続性監視方法とその制御方法
US8625753B1 (en) * 2011-06-03 2014-01-07 Sprint Communications Company L.P. Delivering recallable messages via internet or telephony communicaiton paths
US20130007142A1 (en) * 2011-06-30 2013-01-03 Jonathan Rosenberg Processing A Message
CN108848471B (zh) 2011-09-30 2022-12-30 华为终端(深圳)有限公司 一种实现短消息重发的方法和装置
US8391136B1 (en) * 2012-01-27 2013-03-05 Google Inc. Fallback messaging
US9641609B2 (en) * 2012-02-28 2017-05-02 Google Inc. Integrated messaging
US20140012929A1 (en) * 2012-06-15 2014-01-09 Life of Two Delivering messages over multiple communication paths
US9451539B2 (en) * 2012-06-27 2016-09-20 At&T Intellectual Property I, L.P. Method and apparatus for generating recommended changes to communication behaviors
FR2997776B1 (fr) * 2012-11-05 2015-12-18 Xooloo Gestion perfectionnee d'une base de messages
CN103472995B (zh) * 2013-09-10 2016-06-08 小米科技有限责任公司 一种消息展示的方法、装置及终端设备
US10320730B2 (en) 2013-09-10 2019-06-11 Xiaomi Inc. Method and device for displaying message
JP6163094B2 (ja) * 2013-12-03 2017-07-12 日本電信電話株式会社 メッセージ配信システム、メッセージ配信方法およびメッセージ配信プログラム
US20150310060A1 (en) * 2014-04-23 2015-10-29 Lawrence F. Glaser Memtag(s), Automated Creation of a Timeline Archive For Improving Personal, Business and Government Productivity and Communications
CN105099841B (zh) * 2015-08-31 2018-10-26 小米科技有限责任公司 消息的发送方法、装置、终端及路由器
CN106656729B (zh) * 2015-10-30 2019-11-22 阿里巴巴集团控股有限公司 一种发送信息的方法及装置
EP3273644B1 (fr) * 2016-07-18 2021-02-17 Vestel Elektronik Sanayi ve Ticaret A.S. Procédé, système et produit de programme informatique pour adaptation sélective et transmission des données de messagerie
US11101027B2 (en) * 2016-12-28 2021-08-24 Cerner Innovation, Inc. Messaging protocol
RU2658157C1 (ru) * 2017-04-26 2018-06-19 Закрытое акционерное общество "Восточный Ветер" Способ построения временных каналов передачи данных между клиентами служб обмена мгновенными сообщениями, использующими различные коммуникационные протоколы
CN108462987B (zh) 2017-08-07 2021-08-27 杭州青奇科技有限公司 一种共享自行车的车锁通信系统及车锁通信方法
DE102018207659A1 (de) * 2018-05-16 2019-11-21 Bayerische Motoren Werke Aktiengesellschaft Master-Slave-System
JP6590356B1 (ja) * 2019-05-16 2019-10-16 株式会社アクリート メッセージ通信装置及びメッセージ通信プログラム
JP6823740B2 (ja) * 2019-05-17 2021-02-03 ソフトバンク株式会社 メッセージ管理サーバ、メッセージ管理方法、メッセージ管理プログラムおよびメッセージ管理システム
JP6736102B1 (ja) * 2019-07-29 2020-08-05 株式会社アクリート メッセージ通信装置及びメッセージ通信プログラム
EP4078477A1 (fr) * 2019-12-16 2022-10-26 Liveperson, Inc. Systèmes et procédés pour une conversation bidirectionnelle proactive
JP7213385B1 (ja) 2021-11-12 2023-01-26 Kddi株式会社 メッセージの中継装置及びプログラム
EP4476897A4 (fr) * 2022-02-11 2026-03-04 GupShup Inc Système et procédé de messagerie commerciale riche à portée étendue
CN115277618B (zh) * 2022-07-25 2024-01-30 每日互动股份有限公司 一种消息发送的数据处理系统
US12395568B2 (en) * 2022-08-15 2025-08-19 Capital One Services, Llc Systems and methods to determine the loss of ability to notify customer through mobile app and prompt re-download

Family Cites Families (52)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH02311048A (ja) 1989-05-26 1990-12-26 Canon Inc 電子メールシステム
US5025252A (en) * 1989-11-03 1991-06-18 Motorola, Inc. Paging receiver with over-the-air characterization of call signal processing
US5742905A (en) * 1994-09-19 1998-04-21 Bell Communications Research, Inc. Personal communications internetworking
US5710976A (en) * 1996-01-18 1998-01-20 Motorola, Inc. Method and apparatus for reducing noise interference to improve outbound message reliability in a two-way messaging system
US6023779A (en) * 1996-01-18 2000-02-08 Pocketscience, Inc. Electronic, acoustical tone generating communications system and method
US6014429A (en) * 1996-08-12 2000-01-11 Lucent Technologies, Inc. Two-way wireless messaging system with transaction server
US5878352A (en) * 1996-12-20 1999-03-02 Motorola, Inc. Apparatus and method for selecting a transmitter for directed message delivery
US5966663A (en) * 1997-01-14 1999-10-12 Ericsson Messaging Systems Inc. Data communications protocol for facilitating communications between a message entry device and a messaging center
US6263212B1 (en) * 1998-02-17 2001-07-17 Alcatel Usa Sourcing, L.P. Short message service center
US6219694B1 (en) * 1998-05-29 2001-04-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device having a shared electronic address
US6766162B1 (en) * 1999-04-23 2004-07-20 Skyworks Solutions, Inc. Message notification system for wireless communication system
AU1026000A (en) * 1999-11-17 2001-05-30 Swisscom Mobile Ag Method and system for preparing and transmitting sms messages in a mobile radio network
JP3475883B2 (ja) * 1999-12-08 2003-12-10 日本電気株式会社 在席離席状態を確認可能な計算機端末および在席離席状態確認システム
US6807423B1 (en) * 1999-12-14 2004-10-19 Nortel Networks Limited Communication and presence spanning multiple access networks
JP2001237873A (ja) * 2000-02-22 2001-08-31 Canon Inc 電子メールシステムおよび電子メール通信方法
US6714793B1 (en) 2000-03-06 2004-03-30 America Online, Inc. Method and system for instant messaging across cellular networks and a public data network
US20020120697A1 (en) * 2000-08-14 2002-08-29 Curtis Generous Multi-channel messaging system and method
US7245928B2 (en) * 2000-10-27 2007-07-17 Cellemetry, Llc Method and system for improved short message services
US20020198946A1 (en) 2001-01-16 2002-12-26 Yi-Min Wang Personal centralized alert delivery systems and methds of use
US7190956B2 (en) * 2001-05-15 2007-03-13 Motorola Inc. Instant message proxy for circuit switched mobile environment
JP2003087408A (ja) * 2001-09-13 2003-03-20 Nec Corp ショートメッセージ配信システム
US7317699B2 (en) * 2001-10-26 2008-01-08 Research In Motion Limited System and method for controlling configuration settings for mobile communication devices and services
US20030110224A1 (en) * 2001-12-12 2003-06-12 Cazier Robert Paul Message auto-routing for electronic mail
US20040019695A1 (en) * 2002-07-25 2004-01-29 International Business Machines Corporation Messaging system and method using alternative message delivery paths
AU2002950435A0 (en) * 2002-07-29 2002-09-12 Trade Wind Communications Ltd A Bulk Communications Process Using Multiple Delivery Media
ATE370620T1 (de) * 2002-09-19 2007-09-15 Research In Motion Ltd Vorrichtung und verfahren zur sofortigen drahtlosen nachrichtenübermittlung
US7225226B2 (en) 2002-09-27 2007-05-29 International Business Machines Corporation Chat messaging channel redirection
US7853652B2 (en) * 2003-01-18 2010-12-14 International Business Machines Corporation Instant messaging system with privacy codes
JP2004326318A (ja) * 2003-04-23 2004-11-18 Murata Mach Ltd 通信装置
KR100887179B1 (ko) * 2003-05-27 2009-03-10 인터내셔널 비지네스 머신즈 코포레이션 채널 라우팅 방법 및 채널 라우팅 방법을 구현하는 시스템
JP4718767B2 (ja) 2003-06-24 2011-07-06 Ｎｅｃインフロンティア株式会社 コミュニケーション交換機
RU2253949C1 (ru) 2003-10-28 2005-06-10 Смоловик Сергей Николаевич Способ записи, сохранения и обмена информацией в сети сотовой связи
CN100375424C (zh) 2004-03-22 2008-03-12 国际商业机器公司 多媒体消息收发方法、系统、网关和客户设备
WO2005107283A1 (fr) * 2004-05-03 2005-11-10 Research In Motion Limited Systeme et procede destines a l'interruption de commandes sur un dispositif portable
US7962623B2 (en) * 2004-06-30 2011-06-14 Microsoft Corporation Sustaining session connections
US7305069B1 (en) * 2004-07-20 2007-12-04 Cisco Technology, Inc. Multi-copy, multi-media, non-redundant messaging
US7660873B2 (en) * 2004-08-16 2010-02-09 General Electric Company Systems and methods for communicating messages
CN1589048A (zh) * 2004-09-13 2005-03-02 于耕 多体制多信道无线通信设备及使用该设备的无线通信方法
US7583958B2 (en) * 2004-11-05 2009-09-01 Research In Motion Limited Integrated message delivery over a plurality of transport mediums
US8176086B2 (en) * 2004-11-30 2012-05-08 Avaya Inc. Methods and apparatus for determining a presence of a user
US20060190608A1 (en) * 2005-02-18 2006-08-24 Nokia Corporation Method for the obtaining of deployment components to electronic devices
JP2006243985A (ja) * 2005-03-02 2006-09-14 Nec Corp メッセージ通知システム及びその方法並びにそれに用いるサーバ
JP2007081811A (ja) * 2005-09-14 2007-03-29 Mitsubishi Electric Corp ネットワークの構成管理方法および通信端末
US7840207B2 (en) * 2005-11-30 2010-11-23 Research In Motion Limited Display of secure messages on a mobile communication device
US7831707B2 (en) * 2006-08-02 2010-11-09 Scenera Technologies, Llc Methods, systems, and computer program products for managing electronic subscriptions
US8675831B2 (en) 2006-10-24 2014-03-18 Alcatel Lucent Storage of data messages for later retrieval by the recipient
EP2226996B1 (fr) * 2007-02-27 2014-11-12 BlackBerry Limited Procédé, appareil et système destinés au lancement d'événements d'un calendrier
US8463649B2 (en) * 2007-03-02 2013-06-11 Cfph, Llc Bidding for a request to reserve a service
CN101068224B (zh) * 2007-06-18 2010-07-28 北京亿企通信息技术有限公司 一种即时通信系统中信息监视的方法
US7970381B2 (en) * 2007-08-13 2011-06-28 General Motors Llc Method of authenticating a short message service (sms) message
US8539361B2 (en) * 2007-12-03 2013-09-17 Blackberry Limited Multiple display regions in a unified message inbox
US8655714B2 (en) * 2007-12-28 2014-02-18 International Business Machines Corporation Automatic time-zone sensitive scheduling

Also Published As

Publication number Publication date
MX2010005978A (es) 2010-09-03
AU2009266360C1 (en) 2012-12-13
CA2707467C (fr) 2016-11-15
EG26026A (en) 2012-12-10
WO2010002354A1 (fr) 2010-01-07
KR101291324B1 (ko) 2013-07-30
JP5246332B2 (ja) 2013-07-24
AU2009266360A1 (en) 2010-01-07
ES2574637T3 (es) 2016-06-21
CN102027461B (zh) 2015-06-17
JP2011527467A (ja) 2011-10-27
US20100325470A1 (en) 2010-12-23
EP2297645A4 (fr) 2014-12-24
CA2707467A1 (fr) 2010-01-07
EP2297645B1 (fr) 2016-03-02
RU2010140041A (ru) 2012-08-10
TW201010348A (en) 2010-03-01
UA100722C2 (uk) 2013-01-25
CN102027461A (zh) 2011-04-20
US9237428B2 (en) 2016-01-12
RU2459240C2 (ru) 2012-08-20
SG157991A1 (en) 2010-01-29
CO6300817A2 (es) 2011-07-21
MY154291A (en) 2015-05-29
HK1155237A1 (en) 2012-05-11
KR20110020223A (ko) 2011-03-02
TWI455530B (zh) 2014-10-01
AU2009266360B2 (en) 2011-09-15
BRPI0905730A2 (pt) 2015-07-14

Similar Documents

Publication Publication Date Title
AU2009266360B2 (en) Extended messaging platform
US7076241B1 (en) System and method for selectively transmitting electronic messages
US6965917B1 (en) System and method for notification of an event
US8046014B2 (en) Management of messages included in a message thread displayed by a handheld device
US9614791B2 (en) Adding a contact to a contact list on a mobile device
US8150385B1 (en) Automated reply messages among end user communication devices
EP1783971B1 (fr) Procédé de traitement dans un terminal d'un message de notification en double
US20040019695A1 (en) Messaging system and method using alternative message delivery paths
US7076528B2 (en) System and method for communicating messages between a host computer and a designated device
CN101573928B (zh) 用于在通信系统中递送消息的方法
US20140143202A1 (en) Regulated Texting Solution for Mobile Devices
US7030730B1 (en) System and method for formatting an electronic message
US20040266441A1 (en) System and method for managing data items
CN101156384B (zh) 限制多媒体消息中心对多媒体消息转发次数的方法和系统
US8249560B2 (en) Sending method, receiving method, and system for email transfer by short message
HK1155237B (en) Extended messaging platform
CN101296415A (zh) 一种用于网站故障报警的系统及方法
KR20080049289A (ko) 인스턴트 메시징 서버와 메일 서버간 상호연동하는 실시간통합 메시징 시스템 및 그 서비스 방법
KR20040070557A (ko) 이동통신 시스템에서 메시지 전송 방법 및 장치
WO2021088768A1 (fr) Système et procédé de retransmission de sms à échec d'envoi
JP2005070851A (ja) 通信システム

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20100818

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: AL BA RS

RIN1 Information on inventor provided before grant (corrected)

Inventor name: KEYS, CHRISTOPHER EDWARD

Inventor name: KERO, MARKKU

Inventor name: LEINONEN, RAINER

Inventor name: UNDERWOOD, JOHN ANTHONY

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20141121

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 4/14 20090101ALI20141117BHEP

Ipc: G06F 15/173 20060101ALI20141117BHEP

Ipc: H04L 12/58 20060101ALI20141117BHEP

Ipc: H04L 29/14 20060101ALI20141117BHEP

Ipc: G06F 15/16 20060101AFI20141117BHEP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602009036592

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0015160000

Ipc: H04L0029140000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 15/173 20060101ALI20150710BHEP

Ipc: H04L 12/58 20060101ALI20150710BHEP

Ipc: H04L 29/14 20060101AFI20150710BHEP

Ipc: H04W 4/14 20090101ALI20150710BHEP

Ipc: G06F 15/16 20060101ALI20150710BHEP

Ipc: H04L 29/06 20060101ALI20150710BHEP

INTG Intention to grant announced

Effective date: 20150805

RIN1 Information on inventor provided before grant (corrected)

Inventor name: UNDERWOOD, JOHN ANTHONY

Inventor name: LEINONEN, RAINER

Inventor name: KERO, MARKKU

Inventor name: KEYS, CHRISTOPHER EDWARD

INTG Intention to grant announced

Effective date: 20150819

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 778677

Country of ref document: AT

Kind code of ref document: T

Effective date: 20160315

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602009036592

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 8

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2574637

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20160621

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20160302

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 778677

Country of ref document: AT

Kind code of ref document: T

Effective date: 20160302

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

Ref country code: NO

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

Effective date: 20160602

Ref country code: FI

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

Effective date: 20160302

Ref country code: HR

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

Effective date: 20160302

Ref country code: GR

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

Effective date: 20160603

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

Ref country code: LT

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

Effective date: 20160302

Ref country code: PL

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

Effective date: 20160302

Ref country code: AT

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

Effective date: 20160302

Ref country code: SE

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

Effective date: 20160302

Ref country code: LV

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

Effective date: 20160302

Ref country code: NL

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

Effective date: 20160302

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

Ref country code: EE

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

Effective date: 20160302

Ref country code: IS

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

Effective date: 20160702

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

Ref country code: PT

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

Effective date: 20160704

Ref country code: SK

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

Effective date: 20160302

Ref country code: CZ

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

Effective date: 20160302

Ref country code: RO

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

Effective date: 20160302

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602009036592

Country of ref document: DE

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

Ref country code: BE

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

Effective date: 20160302

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

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

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

Ref country code: DK

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

Effective date: 20160302

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

26N No opposition filed

Effective date: 20161205

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

Ref country code: SI

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

Effective date: 20160302

Ref country code: BG

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

Effective date: 20160602

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

Ref country code: LI

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

Effective date: 20160630

Ref country code: CH

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

Effective date: 20160630

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

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

Ref country code: LU

Payment date: 20170630

Year of fee payment: 9

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

Ref country code: TR

Payment date: 20170629

Year of fee payment: 9

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

Ref country code: IT

Payment date: 20170721

Year of fee payment: 9

Ref country code: MC

Payment date: 20170704

Year of fee payment: 9

Ref country code: ES

Payment date: 20170703

Year of fee payment: 9

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

Ref country code: HU

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

Effective date: 20090630

Ref country code: CY

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

Effective date: 20160302

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 10

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

Ref country code: MK

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

Effective date: 20160302

Ref country code: MT

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

Effective date: 20160630

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

Ref country code: DE

Payment date: 20180625

Year of fee payment: 10

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602009036592

Country of ref document: DE

Representative=s name: BARDEHLE PAGENBERG PARTNERSCHAFT MBB PATENTANW, DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 602009036592

Country of ref document: DE

Owner name: PHENIX INVESTMENT MANAGEMENT LTD., ROAD TOWN, VG

Free format text: FORMER OWNER: 3RD BRAND PTE. LTD., SINGAPORE, SG

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

Ref country code: FR

Payment date: 20180620

Year of fee payment: 10

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20180809 AND 20180815

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: PHENIX INVESTMENT MANAGEMENT LTD., VG

Effective date: 20180828

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

Ref country code: GB

Payment date: 20180620

Year of fee payment: 10

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

Ref country code: MC

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

Effective date: 20180702

Ref country code: LU

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

Effective date: 20180630

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

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

Ref country code: IE

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

Effective date: 20180630

Ref country code: IT

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

Effective date: 20180630

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20190916

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

Ref country code: ES

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

Effective date: 20180701

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602009036592

Country of ref document: DE

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

Effective date: 20190630

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

Ref country code: GB

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

Effective date: 20190630

Ref country code: DE

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

Effective date: 20200101

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

Ref country code: FR

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

Effective date: 20190630

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

Ref country code: TR

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

Effective date: 20180630