EP1929730A2 - Verfahren und vorrichtung für instantmessaging - Google Patents

Verfahren und vorrichtung für instantmessaging

Info

Publication number
EP1929730A2
EP1929730A2 EP06795523A EP06795523A EP1929730A2 EP 1929730 A2 EP1929730 A2 EP 1929730A2 EP 06795523 A EP06795523 A EP 06795523A EP 06795523 A EP06795523 A EP 06795523A EP 1929730 A2 EP1929730 A2 EP 1929730A2
Authority
EP
European Patent Office
Prior art keywords
message
msrp
sip
encapsulated
session
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
EP06795523A
Other languages
English (en)
French (fr)
Other versions
EP1929730A4 (de
EP1929730B1 (de
Inventor
Miguel-Angel Garcia-Martin
Adamu Haruna
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.)
Nokia Technologies Oy
Original Assignee
Nokia Oyj
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 Nokia Oyj filed Critical Nokia Oyj
Publication of EP1929730A2 publication Critical patent/EP1929730A2/de
Publication of EP1929730A4 publication Critical patent/EP1929730A4/de
Application granted granted Critical
Publication of EP1929730B1 publication Critical patent/EP1929730B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • 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]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00—Encapsulation of packets

Definitions

  • This invention is related to instant messaging using protocols such as SIP (Session Initiation Protocol) and MSRP (Message Session Relay).
  • SIP Session Initiation Protocol
  • MSRP Message Session Relay
  • SIP instant messages can be sent to users, whether or not the user is online.
  • a SIP MESSAGE request can be used to carry the instant message. This is sometimes called page mode, because each instant message is not related to other instant messages.
  • SIP can be used to establish a session and MSRP is used to carry the actual instant messages within that session. This can be useful for users who are trying to follow the flow of a conversation, because the relation between instant messages can identify them as corresponding to a given conversation.
  • An embodiment of the present invention provides, for example, a method for stored message delivery including receiving a SIP or MSRP message, encapsulating the received SIP or MSRP message in another
  • MSRP message and transmitting the encapsulated SIP or MSRP messages to an intended recipient.
  • Another embodiment of the present invention provides, for example, an apparatus for use as a store message application server.
  • the apparatus can include a reception module configured to receive a SIP message, an encapsulation module configured to encapsulate the received SIP message in an MSRP message, and a transmission module configured to transmit the encapsulated SIP message to an intended recipient.
  • Yet another embodiment of the present invention provides, for example, an apparatus for use as a store message application server including means for receiving a SIP message.
  • the apparatus can also include means for encapsulating the received SIP message in an MSRP message and means for transmitting the encapsulated SIP message to an intended recipient.
  • An additional embodiment of the present invention provides, for example, a computer program embodied on a computer readable medium for providing stored messages, comprising a computer program controlling a computer to receive a SIP message, encapsulate the received SIP message in an MSRP message, and transmit the encapsulated SIP message to an intended recipient.
  • Figure 1 shows a diagram flow that exemplifies the sequence of messages.
  • Figure 2 shows various levels of encapsulation of the different messages, when the user retrieves his unread instant messages from the store message application server.
  • Figure 3 is a depiction of an example method according to the present invention.
  • FIG. 4 is a depiction of a sample apparatus according to the present invention. DESCRIPTION OF THE PREFERRED EMBODIMENT(S):
  • Certain embodiments of the present invention can provide a SIP mechanism to retrieve instant messages that were previously deposited in an application server, which was acting as a message store application server.
  • the invention can help to achieve these and other goals by maintaining the relevant headers of the SIP message by encapsulating it as a message/sip, for example, as defined in RFC 3261 Section 27.5, or as a message/sipfrag, as defined in RFC 3420, and then sending it as the payload of an MSRP SEND request.
  • a message store application server can then add a header to the MSRP SEND message and to the encapsulated SIP message containing the time and date when the message was received.
  • the invention may be configured to insert a date/time header in every stored SIP and MSRP message.
  • the invention can use novel semantics for the encapsulation of the stored instant messages, and the message/sip and message/sipfrag may be used in MSRP, outside of its original context.
  • the invention can provide a novel and unobvious method of delivering encapsulated SIP messages, including the header information, as the payload of an MSRP message.
  • the invention can also provide novel semantics for encapsulating MSRP messages as message/msrp.
  • the invention therefore, can relate to an area of instant messaging based upon SIP/SIMPLE technology.
  • SIP/SIMPLE develops services, mainly instant messaging and presence, based on the application of SIP and specifications developed within the IETF IMPP working group.
  • SIP/SIMPLE IM in Open Mobile Alliance (OMA) which is mainly driven by operator service and business requirements, is also based on SIP/SIMPLE technology.
  • the invention can also provide a method and apparatus whereby a user can contact his mail server and retrieve existing instant messages already deposited in the store message application server.
  • the instant messages can be deposited in the store message application server using SIP MESSAGE requests (as per IETF RPC 3428) or MSRP messages (e.g., MSRP SEND requests) that are part of a SIP session.
  • MSRP messages e.g., MSRP SEND requests
  • the metadata and/or header information can enable the user to determine the source of the message, the time at which message was left, and so forth.
  • the phone can send a subscription to a message-summary event package, and receive a notification with the pending message; according to RFC 3842 "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)."
  • SIP Session Initiation Protocol
  • the Notifier (which may be an SIP User Agent acting on behalf of the user's messaging system) can send a message summary of the stored messages in the body of a SIP NOTIFY request, e.g. "there are 4 old messages and 3 new messages waiting for you.”
  • message headers such as To, From, Date, Subject, and Message-ID (In SIP this may map to Call-ID) may be appended to each message.
  • the User Equipment can send an INVITE request to the message store application server including the type of desired media to retrieve (for the purpose of this invention, the INVITE request includes a Session Description Protocol (SDP) description of messaging with MSRP, but may also include other media types different than messaging).
  • SDP Session Description Protocol
  • all stored messages may be transferred from the server to the UE. Each stored message may be sent in a separate MSRP SEND request (which may occur before chunking of MSRP SEND requests takes place), and each one may be identified by its own original Message-ID.
  • the user can retrieve all the messages at one time, but still may be able to classify all the messages by Message-ID.
  • the original sender identification (user information) is necessarily lost because the MSRP headers do not contain any relation to the SIP URI that deposits the message. Therefore, the association of senders to their particular messages already available in messaging application inboxes such as e-mail, instant messaging, Multimedia Messaging Service (MMS), and the like, can be lost. This also applies to SIP MESSAGE requests, in that they can be sent but the recipient will not be able to identify the sender, because the messages are sent to the store message application server.
  • MMS Multimedia Messaging Service
  • the invention provides a mechanism whereby the user, when he wants to retrieve his stored instant messages, establishes an MSRP session with his store message application server.
  • the store message Application Server may encapsulate each received session or standalone MESSAGE in an MSRP SEND request.
  • each MSRP SEND request may represent a SIP session or MESSAGE that contains a payload (e.g. one or more MSRP SEND requests, or some other type in the case of message).
  • Another user can create a SIP session by sending an INVITE request 3 to Charlie.
  • the INVITE request can contain a session description that includes an MSRP descriptor for the purpose of sending session-based instant messages.
  • the store message AS can intercept the INVITE request and establish the session.
  • the store message AS can acknowledge the SIP INVITE request 3 with a SIP 200 (OK) response 4.
  • Charlie can deposit two messages in Charlie's messaging account, using MSRP SEND requests 5, 7, including Text #2 and Text #3, respectively, which can be acknowledged by MSRP 200 (OK) responses 6 and 8 respectively.
  • Bob may conclude his session with a SIP BYE request 9 that may be acknowledged by a SIP 200 (OK) response 10.
  • Charlie comes online, and then may be notified that there are some messages in his inbox (RFC 3842 may provide some examples ways of notifying Charlie). Charlie may decide to retrieve his pending instant messages. Charlie then may establish a SIP session to his store message AS (SIP INVITE request 11). The store message AS may acknowledge with a SIP 200 (OK) response 12. The reverse is also possible: the store message AS may contact Charlie when it discerns that he is online.
  • the store message AS may take the stored MESSAGE that was sent as SIP MESSAGE request 1 , keep the relevant header fields of the SIP MESSAGE request 1 (e.g., From, To, Call-ID, P-Asserted-Identity, etc.), encapsulate it as either a message/sip (Section 27.5 of RFC 3261) or message/sipfrag (RFC 3420), and send it as the payload of a MSRP SEND request 13.
  • Charlie may acknowledge by sending an MSRP 200 (OK) response 14 to the store message AS.
  • the session may be concluded by the store message AS sending a SIP BYE request 17 to Charlie, and Charlie responding with a SIP 200 (OK) response 18 to the store message AS.
  • Other encapsulation techniques are also possible and permitted.
  • the message may be encapsulated before or after being stored.
  • the store message AS may take the stored SIP INVITE request 3, the stored MSRP SEND requests 5, 7, and the store SIP BYE request 9, and encapsulates them in another MSRP SEND request 15.
  • the message type for the encapsulating MSRP SEND 15 may be set to message/sip or message/sipfrag.
  • the store message AS may add a header that contains the time and date the message was received, for every SIP and MSRP encapsulated message.
  • the Call-ID (in SIP) and Message- ID in MSRP may be kept intact, thereby providing correlation with notifications.
  • every standalone message e.g., SIP MESSAGE requests
  • complete session e.g., from SIP INVITE until SIP BYE requests, including all the MSRP messages
  • MSRP SEND message 13 Each MSRP SEND message may contain a content type of message/sip or message/sipfrag.
  • all the relevant SIP headers may be encapsulated, along with the inner MSRP SEND messages that carry the stored instant messages. This may allow Charlie to determine the origin, time and date, of a message that was left.
  • one MSRP SEND message can be associated with one stored session of instant messages, including the SIP INVITE and BYE requests and all the MSRP SEND requests containing instant messages.
  • the one MSRP SEND message can be associated with one stored standalone SIP MESSAGE request containing an instant message.
  • the store message AS can insert a date/time header in stored SIP and MSRP messages.
  • the store message AS can keep the existing call-ID/message-ID to allow correlation with RFC 3842.
  • the present invention also provides general semantics for the encapsulation of stored instant messages, as well as a method and apparatus that enable recipients to gather information about senders, time/date of delivery, separate different sessions, and keep sessions of instant messages together.
  • the present invention also provides for a new use of message/sip and message/sipfrag in MSRP, outside its original context.
  • certain embodiments of the present invention are also applicable to offline message "push" delivery mechanisms.
  • the store messaging application server may know when an offline user gets back online, e.g. either by SIP SUBSCRIBE/NOTIFY and/or any other mechanism. The offline user can get back online, and the stored message application server can immediately establish an MSRP session with the user and deliver the stored messages to the user.
  • the present invention is described in terms of a situation in which the original SIP message is sent to an off-line user, the invention is of broader scope.
  • the invention also includes, for example, the situation in which a SIP message is simultaneously transmitted to a user and stored or archived for later reference.
  • An embodiment in which the message is archived simultaneously with user reception may be useful for a variety of purposes.
  • a user of a mobile terminal may prefer to store messages separate from the mobile terminal for information security or reliability reasons.
  • Other reasons for simultaneously archiving the stored messages may include the ability to access the stored messages from a plurality of terminals.
  • a user may wish to be able to access stored messages through a wired connection.
  • a user wishing to obtain a stored message can establish a session with a store message application server. The user can then request stored messages. The store message application server can deliver the stored messages encapsulated in one or more MSRP messages.
  • the original header information including the identity of the sender, the date and time the message was sent, and the like can be preserved for the user's reference.
  • delivery of the message there is no requirement that the system ensures delivery, or confirms delivery.
  • the system can, in certain embodiments, transmit the encapsulated message and assume that delivery occurs.
  • a message in accordance with the present invention is not limited to text messages, but may include, for example, image, audio, video components, or a combination of any of them.
  • Figure 3 depicts a method according to certain embodiments of the present invention.
  • a SIP or MSRP message 31 can be received in step 33.
  • the message 31 can be a SIP message, either a single SIP message or part of a SIP session, or it can be an MSRP message which is part of a SIP session.
  • the SIP message 31 can contain header information including identity of sender, time sent, date sent, and so forth.
  • the SIP or MSRP message 31 After the SIP or MSRP message 31 is received, it may be encapsulated within an MSRP message in the encapsulate step 35.
  • the encapsulation can be done immediately on receipt, or there may be some delay between receipt and encapsulation.
  • the encapsulation can encapsulate a single SIP message in a single MSRP message or can encapsulate an entire SIP session, including the exchanged MSRP messages in that session, in a single MSRP message.
  • the SIP or MSRP message 31 After the SIP or MSRP message 31 has been encapsulated, it may be transmitted to its intended destination in transmit step 37.
  • the intended destination can be a target user.
  • the term "user" can refer to equipment operated by, assigned to, or belonging to the user. Accordingly, the transmission may be to a user's mobile device, such as a personal digital assistant, mobile computer, wireless networked media device, or cell phone.
  • Transmit step 37 may occur immediately after encapsulation, but may be delayed. In certain embodiments, transmission occurs when it is determined that a target user who was previously off-line is now on-line. The target user may request the messages, or the messages may be sent automatically to the user.
  • FIG 4 depicts an apparatus according to certain embodiments of the present invention.
  • a SIP or MSRP message 41 can be received in a reception module 43.
  • the message 41 can be either a single SIP message or part of a SIP session, or it can be an MSRP message which is part of a SIP session.
  • the SIP message 41 can contain header information including identity of sender, time sent, date sent, and so forth.
  • the reception module can be located in a store message application server.
  • the store message application server may be connected to one or more networks.
  • the store message application server can be equipped with a transceiver for communicating with the one or more networks.
  • the reception module can also include a general purpose computer (not shown) for carrying out storing, notifying, receiving, encapsulating, and transmitting steps.
  • the general purpose computer can include memory.
  • the memory can include RAM and ROM.
  • the memory can be a digital memory embodied on optical or magnetic media.
  • the computer can communicate using a network interface card, or other device for connecting to a network.
  • the general purpose computer may employ any suitable hardware to accomplish the various functions it performs.
  • the SIP or MRSP message 41 After the SIP or MRSP message 41 is received by the reception module 43, it may be encapsulated within an MSRP message in the encapsulation module 45. The encapsulation can be done immediately on receipt, or there may be some delay between receipt and encapsulation.
  • the encapsulation can encapsulate a single SIP message in a single MSRP message or can encapsulate an entire SIP session, including all the SIP and MSRP messages exchanged as part of the session, in a single MS
  • the SIP or MSRP message 41 After the SIP or MSRP message 41 has been encapsulated, it may be transmitted to its intended destination by the transmission module 47.
  • the intended destination can be a target user.
  • the term "user" can refer to equipment operated by, assigned to, or belonging to the user. Accordingly, the transmission may be to a user's mobile device, such as a personal digital assistant, mobile computer, wireless networked media device, or cell phone.
  • the transmission module 47 may transmit immediately after encapsulation occurs, but may delay transmission. In certain embodiments, transmission occurs when it is determined that a target user who was previously off-line is now on-line. The target user may request the messages, or the messages may be sent automatically to the user.
  • the transmission module 47 may be configured to transmit a notification from notification module (not shown).
  • the notification module can inform a user that stored messages are waiting, and invite the user to retrieve the messages.
  • the notification module can also, or alternatively automatically include a portion of the SIP message in the notification.
  • the notification module may send a notification to a first user that a stored message from a particular second user is waiting.
  • the notification module may include an indication of the age of the stored message.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Multimedia (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Communication Control (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
EP06795523.7A 2005-09-30 2006-08-21 Verfahren und vorrichtung für instantmessaging Active EP1929730B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US72205405P 2005-09-30 2005-09-30
US11/319,268 US7561595B2 (en) 2005-09-30 2005-12-29 Method and apparatus for instant messaging
PCT/IB2006/002587 WO2007036777A2 (en) 2005-09-30 2006-08-18 Method and apparatus for instant messaging

Publications (3)

Publication Number Publication Date
EP1929730A2 true EP1929730A2 (de) 2008-06-11
EP1929730A4 EP1929730A4 (de) 2011-02-16
EP1929730B1 EP1929730B1 (de) 2017-07-26

Family

ID=37900120

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06795523.7A Active EP1929730B1 (de) 2005-09-30 2006-08-21 Verfahren und vorrichtung für instantmessaging

Country Status (9)

Country Link
US (2) US7561595B2 (de)
EP (1) EP1929730B1 (de)
JP (1) JP5249034B2 (de)
KR (1) KR100936189B1 (de)
CN (1) CN101300797B (de)
AU (1) AU2006296335B2 (de)
ES (1) ES2638588T3 (de)
TW (1) TWI459791B (de)
WO (1) WO2007036777A2 (de)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100824043B1 (ko) * 2005-04-08 2008-04-21 삼성전자주식회사 이동 통신 단말의 인스턴트 메시지 전송 방법 및 시스템
CN100488139C (zh) * 2005-08-10 2009-05-13 华为技术有限公司 建立聊天室数据传输通道实现聊天消息传送的方法
US7561595B2 (en) * 2005-09-30 2009-07-14 Nokia Corporation Method and apparatus for instant messaging
CN100542172C (zh) * 2005-10-11 2009-09-16 华为技术有限公司 一种离线消息发送和接收方法
CN100514968C (zh) * 2005-10-11 2009-07-15 华为技术有限公司 离线消息的处理方法和即时消息服务器
US20070115926A1 (en) * 2005-10-27 2007-05-24 3Com Corporation System and method for receiving a user message at a packet-network telephone
US7734704B2 (en) * 2006-07-28 2010-06-08 International Business Machines Corporation Method and system for identifying and automatically redisplaying unread instant messages
EP2210400B1 (de) * 2007-11-16 2016-06-01 Telefonaktiebolaget LM Ericsson (publ) Verfahren zur ereignispaket-abwicklung
KR101397633B1 (ko) 2007-12-05 2014-05-22 주식회사 케이티 아이엠에스 기반 인스턴트 메시지 서비스 제공 시스템 및방법
TW201015940A (en) * 2008-10-01 2010-04-16 Avermedia Tech Inc Network authorization method and application thereof
CN101998573A (zh) * 2009-08-14 2011-03-30 中兴通讯股份有限公司 一种融合ip消息的路由系统及方法
KR101396767B1 (ko) * 2009-12-24 2014-05-16 에릭슨엘지엔터프라이즈 주식회사 Ｓｉｐ 기반 통신 서비스 제공 시스템 및 그 방법
CN102195787B (zh) * 2010-03-17 2013-09-11 华为技术有限公司 消息处理方法和消息会话传输协议服务器
US8621213B2 (en) 2010-06-08 2013-12-31 Merge Healthcare, Inc. Remote control of medical devices using instant messaging infrastructure
CN102130846B (zh) * 2010-08-30 2012-11-14 华为技术有限公司 一种即时消息发送、接收方法、装置和系统
CN102006288A (zh) * 2010-11-12 2011-04-06 中兴通讯股份有限公司 多页彩信的传输系统和方法、sip终端以及彩信代理服务器
US9143632B2 (en) * 2011-04-18 2015-09-22 Arris Technology, Inc. Method for signaling a facsimile pass through mode over a VOIP voice service
US8861509B2 (en) * 2011-06-27 2014-10-14 Intel Mobile Communications GmbH Communication devices and methods for generating a message
CN103546437A (zh) * 2012-07-16 2014-01-29 中兴通讯股份有限公司 一种ims中实现离线消息收发的方法、ue及as
CN103475567B (zh) * 2013-07-31 2016-09-14 华为软件技术有限公司 数据传输方法、装置、设备及系统
CN104243288B (zh) * 2014-09-30 2015-12-02 小米科技有限责任公司 消息传输方法及装置、电子设备
CN105471841B (zh) * 2015-11-12 2018-09-28 中国电子科技集团公司第三十研究所 一种基于msrp协议的多业务数据的传输方法及装置
CN112243012B (zh) * 2019-07-16 2023-06-30 中国移动通信有限公司研究院 一种离线消息传输方法、装置、服务器及终端
US10491582B1 (en) * 2019-07-19 2019-11-26 Capital One Services, Llc Message authenticated communication sessions

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005029809A1 (en) * 2003-09-19 2005-03-31 Telefonaktiebolaget Lm Ericsson (Publ) Exchange protocol for combinational multimedia services
US20050213537A1 (en) * 2004-02-27 2005-09-29 Ingimundarson Jon I Interworking gateway and method

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7058036B1 (en) * 2000-02-25 2006-06-06 Sprint Spectrum L.P. Method and system for wireless instant messaging
DE60218906T2 (de) * 2001-12-07 2007-11-29 Telefonaktiebolaget Lm Ericsson (Publ) Dienstzugang und Fernsprechkonferenzsystem und -verfahren in einem Telekommunikationsnetzwerk
JP4127106B2 (ja) * 2003-04-10 2008-07-30 日本電気株式会社 移動通信システム及び方法、移動通信端末
JP4060764B2 (ja) * 2003-07-11 2008-03-12 日本電信電話株式会社 通信装置
CN100493074C (zh) * 2003-10-24 2009-05-27 中国科学院计算技术研究所 一种终端应用协议中自适应的多媒体分布播放方法
JP3980562B2 (ja) * 2004-01-09 2007-09-26 日本電信電話株式会社 Ｓｉｐ通信制御装置
CN1642148B (zh) * 2004-01-17 2012-06-20 腾讯科技（深圳）有限公司 一种即时通讯处理方法
US7672255B2 (en) * 2004-04-05 2010-03-02 Oomble, Inc. Mobile instant messaging conferencing method and system
US20060083305A1 (en) * 2004-10-15 2006-04-20 James Dougherty Distributed motion detection event processing
US20060168037A1 (en) 2004-12-21 2006-07-27 Alcatel Systems and methods for handling presence messages
US20080147806A1 (en) * 2005-02-08 2008-06-19 Ling Robbie Method and Arrangements in a Mobile Communication Network
US7532890B2 (en) * 2005-04-01 2009-05-12 Rockliffe Systems Content-based notification and user-transparent pull operation for simulated push transmission of wireless email
US20060230154A1 (en) * 2005-04-11 2006-10-12 Nokia Corporation Method and entities for performing a push session in a communication system
US7561595B2 (en) * 2005-09-30 2009-07-14 Nokia Corporation Method and apparatus for instant messaging
US9258259B2 (en) * 2005-09-30 2016-02-09 Nokia Technologies Oy Retrieval of offline instant messages
CN100514968C (zh) * 2005-10-11 2009-07-15 华为技术有限公司 离线消息的处理方法和即时消息服务器
US20080240117A1 (en) * 2007-03-30 2008-10-02 Telefonaktiebolaget Lm Ericsson (Publ) System, Method, and Interworking Function for Interfacing MMS and IMS Messaging Systems
KR101264805B1 (ko) * 2008-11-20 2013-05-15 삼성전자주식회사 프레즌스 서비스 제공방법 및 시스템

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005029809A1 (en) * 2003-09-19 2005-03-31 Telefonaktiebolaget Lm Ericsson (Publ) Exchange protocol for combinational multimedia services
US20050213537A1 (en) * 2004-02-27 2005-09-29 Ingimundarson Jon I Interworking gateway and method

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CAMPBELL B ET AL: "The Message Session Relay Protocol; draft-ietf-simple-message-session s-09.txt", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, vol. simple, no. 9, 24 October 2004 (2004-10-24), XP015027599, ISSN: 0000-0004 *
See also references of WO2007036777A2 *
SINGH K ET AL: "Peer-to-Peer Internet Telephony using SIP", INTERNET CITATION, 31 October 2004 (2004-10-31), XP002336408, Retrieved from the Internet: URL:http://www1.cs.columbia.edu/ library/TR-repository/reports/reports-20 04/cucs-044-04.pdf [retrieved on 2005-07-18] *

Also Published As

Publication number Publication date
WO2007036777A8 (en) 2008-04-17
WO2007036777A2 (en) 2007-04-05
CN101300797B (zh) 2012-09-05
US8204932B2 (en) 2012-06-19
JP5249034B2 (ja) 2013-07-31
KR20080053945A (ko) 2008-06-16
US20090282118A1 (en) 2009-11-12
ES2638588T3 (es) 2017-10-23
US7561595B2 (en) 2009-07-14
TW200719685A (en) 2007-05-16
TWI459791B (zh) 2014-11-01
CN101300797A (zh) 2008-11-05
JP2009510873A (ja) 2009-03-12
EP1929730A4 (de) 2011-02-16
US20070076751A1 (en) 2007-04-05
AU2006296335A1 (en) 2007-04-05
AU2006296335B2 (en) 2010-09-02
KR100936189B1 (ko) 2010-01-11
WO2007036777A3 (en) 2007-07-12
EP1929730B1 (de) 2017-07-26

Similar Documents

Publication Publication Date Title
US7561595B2 (en) Method and apparatus for instant messaging
KR100966959B1 (ko) 단말기 디바이스, 네트워크 디바이스, 메시지 검색 방법 및 컴퓨터 프로그램 저장 제품
EP1861970B1 (de) Verfahren und anordnung in einem kommunikationssystem zum abliefern von nachrichten an einen empfänger
EP2146511B1 (de) Verfahren und system zur bereitstellung eines benachrichtigungsdienstes und benachrichtigungsanwendungssever
US9491003B2 (en) Method and apparatus for keeping orders among messages of discrete media type in CPM session
WO2013043365A1 (en) Archive control for text messages
JP5753316B2 (ja) テキスト・メッセージングのための、ＲＥＳＴｆｕｌウェブ・サービスとパケット交換ネットワークとの間におけるインターフェース
US9462131B2 (en) Voice messaging method and system, and converged messaging server and client
KR20080034072A (ko) Ｓｉｐ기반의 전송 메시지를 이용한 이종 메시지의 전송방법 및 이를 위한 사용자 장치
WO2008148339A1 (fr) Procédé, agent d'utilisateur servant à traiter un message d'un modèle de dispositif de messagerie
WO2008044829A1 (en) Method for transmitting different type messages using a sip-based transport message and user equipment therefor
US20150120843A1 (en) Method and Device to Store and Forward a File Thumbnail to an Initially Unavailable Client
CN101292480A (zh) 脱机即时消息的取回
KR20080090250A (ko) 이종 메시지의 상호 연동을 통한 메시지 전송 방법

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

AK Designated contracting states

Kind code of ref document: A2

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

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

A4 Supplementary search report drawn up and despatched

Effective date: 20110119

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA CORPORATION

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA TECHNOLOGIES OY

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20170410

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 HU IE IS IT LI LT LU LV MC NL 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: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 913226

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170815

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602006053145

Country of ref document: DE

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2638588

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20171023

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20170726

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

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170726

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

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

Ref country code: MC

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

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

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

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

Ref country code: CH

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

Effective date: 20170831

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602006053145

Country of ref document: DE

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

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

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

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20170831

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

Ref country code: LU

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

Effective date: 20170821

26N No opposition filed

Effective date: 20180430

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

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

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 NON-PAYMENT OF DUE FEES

Effective date: 20170831

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

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

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

Ref country code: CY

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

Effective date: 20170726

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602006053145

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012580000

Ipc: H04L0051000000

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230527

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

Ref country code: TR

Payment date: 20230818

Year of fee payment: 18

Ref country code: IT

Payment date: 20230711

Year of fee payment: 18

Ref country code: GB

Payment date: 20230629

Year of fee payment: 18

Ref country code: ES

Payment date: 20230908

Year of fee payment: 18

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

Ref country code: FR

Payment date: 20230703

Year of fee payment: 18

Ref country code: DE

Payment date: 20230703

Year of fee payment: 18