EP2008425B1 - Deleting mechanism in sip multimedia services - Google Patents
Deleting mechanism in sip multimedia services Download PDFInfo
- Publication number
- EP2008425B1 EP2008425B1 EP07713248.8A EP07713248A EP2008425B1 EP 2008425 B1 EP2008425 B1 EP 2008425B1 EP 07713248 A EP07713248 A EP 07713248A EP 2008425 B1 EP2008425 B1 EP 2008425B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- request
- sip
- user
- user account
- 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.)
- Active
Links
- 230000007246 mechanism Effects 0.000 title description 17
- 238000000034 method Methods 0.000 claims description 21
- 238000012546 transfer Methods 0.000 claims description 6
- 230000000977 initiatory effect Effects 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims 13
- 239000003795 chemical substances by application Substances 0.000 description 44
- 238000004891 communication Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 11
- 230000005540 biological transmission Effects 0.000 description 7
- 101100396152 Arabidopsis thaliana IAA19 gene Proteins 0.000 description 6
- 101100274486 Mus musculus Cited2 gene Proteins 0.000 description 6
- 101150096622 Smr2 gene Proteins 0.000 description 6
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 102100039292 Cbp/p300-interacting transactivator 1 Human genes 0.000 description 1
- 101000888413 Homo sapiens Cbp/p300-interacting transactivator 1 Proteins 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- 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
- H04L65/4061—Push-to services, e.g. push-to-talk or push-to-video
-
- 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]
- H04L51/046—Interoperability with other network applications or services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/147—Signalling methods or messages providing extensions to protocols defined by standardisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
Definitions
- the present invention relates generally to session initiation protocol (SIP) services and SIP for instant messaging and presence leveraging extensions (SIMPLE) services. More particularly, the present invention relates to SIP/SIMPLE based services such as instant messaging (IM) and push-to-talk (PoC) services.
- SIP session initiation protocol
- SIMPLE instant messaging and presence leveraging extensions
- IM instant messaging
- PoC push-to-talk
- the Open Mobile Alliance is a standards body which collectively develops open standards for use in the mobile industry.
- the OMA helps to create interoperable services enablers to work across countries, operators and mobile terminals and is driven by market requirements.
- companies supporting the Open Mobile Alliance work to aid in the rapid and wide development and deployment of a variety of new, enhanced mobile information, communication and entertainment services.
- the OMA is currently developing IM services based on SIP, Message Session Relay Protocol (MSRP) and Extensible Markup Language (XML) Configuration Access Protocol (XCAP) protocols developed by the International Engineering Task Force (IETF) SIMPLE working group.
- IM services based on SIP, Message Session Relay Protocol (MSRP) and Extensible Markup Language (XML) Configuration Access Protocol (XCAP) protocols developed by the International Engineering Task Force (IETF) SIMPLE working group.
- IETF International Engineering Task Force
- United States patent application publication number US 2002/083064 A1 discloses a server-side recycle bin system for retaining computer files and information.
- SPARKS DYNAMICSOFT R "The SIP Refer Method draft-sparks-sip-refer-3265disc-00; draft-sparks-sip-refer-3265disc-00.txt" is an internet draft that defines the REFER method. This SIP extension requests that the recipient REFER to a resource provided in the request. It provides a mechanism allowing the party sending the REFER to be notified of the outcome of the referenced request.
- the present invention comprises a novel deleting mechanism for use in SIP multimedia services.
- the present invention involves the use of various SIP multimedia service environment features for this purpose.
- a "recycle bin" is defined in the network and is associated with a SIP uniform resource identifier. Messages that are stored within the network are assigned a unique identifier. If a user desires to delete the message, he or she requests that a SIP/MSRP function be set up between the message and the network-defined recycle bin. When processed, the message is transferred to the recycle bin, leaving the user's account in the user's mail storage server.
- the system and method of the present invention is simple and easy to adopt, as already-existing defined tools such as the SIP REFER method, Virtual User Agent and SIP URI are used.
- the present invention comprises a novel deleting mechanism for use in SIP multimedia services.
- the present invention involves the use of various SIP multimedia service environment features for this purpose.
- a "recycle bin" or similar location for deleted items is defined in the network and is associated with a SIP uniform resource identifier. Messages that are stored within the network are assigned a unique identifier. If a user desires to delete the message, he or she requests that a SIP/MSRP session function be set up between the message and the network-defined recycle bin. When processed, the message is transferred to the recycle bin, leaving the user's account in the user's mail storage server.
- Figure 1 is a flow chart showing the operation of a deleting mechanism for SIP multimedia services in accordance with one embodiment of the present invention.
- Figure 1 shows the interaction among a user/client device 100, a user's account in mail storage 110 and a recycle bin 120 as defined herein. Both the user's account 110 and the recycle bin 120 are located remote from the user/client device.
- the SIP URI for the uscr/clicnt device is "[email protected].”
- the SIP URI for the user's account is "[email protected].”
- the SIP URI for the recycle bin is "[email protected].”
- messages in the network can be assigned unique message identifiers.
- Three such messages are shown at 130 in Figure 1 with identifiers of "[email protected]” (MSG 1) "[email protected]” (MSG 2) and "[email protected]” (MSG 3).
- messages can be stored as files.
- each message can be given a file name, a file type, and a hash value.
- a user decides he or she wants to delete MSG 2.
- the user/client device 100 sends an SIP REFER with INVITE request 150 to the message identifier [email protected], which serves as a virtual user agent 155, at the user's account 110.
- the SIP REFER request has the network-based recycle bin address ([email protected]) in the Refer-to header.
- the SIP REFER with INVITE request 150 serves to request that a SIP Session be set up with the network-based recycle bin 120 ([email protected]).
- the virtual user agent 155 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" message at 160.
- the virtual user agent 155 also sends an INVITE request to set up a SIP session with the recycle bin 120 at 170.
- the recycle bin 120 accepts this session at 180.
- MSRP message session relay protocol
- SDP session description protocol
- the virtual user agent 155 proceeds to notify the user/client 100 of the SIP session at 200, and the user/client device 100 acknowledges this notification at 210.
- MSG 2 is sent from the user's account 110 to the network-based recycle bin 120, causing MSG 2 to disappear from the user's account 110.
- the SIP session between the virtual user agent 155 and the recycle bin 120 is torn down.
- the end result, depicted at 220, is the presence of only MSG 1 and MSG 3 in the user's account 110 in the user's mail storage server.
- the functions of the user's account 110 and the recycle bin 120 are collocated. In this situation, the sending of an INVITE request to set up a SIP session 170, the acknowledgement of this request 180, and the setting up of the SIP session with MSRP 190 is not necessary.
- the mechanism to retrieve the stored or selected messages to the recycle bin can be based on the file transfer draft attached as Exhibit B, which is incorporated into this application.
- the REFER request can include the SDP descriptions of the file(s) to be deleted.
- a user decides he or she wants to delete MSG 2 (File 2).
- the user/client device 100 sends an SIP REFER with INVITE request 150 to the mail storage server, which serves as a virtual user agent 155, at the user's account 110.
- the SIP REFER request has the network-based recycle bin address ([email protected]) in the Refer-to header.
- the SIP REFER with INVITE request 150 serves to request that a SIP Session be set up with the network-based recycle bin 120 ([email protected]).
- the virtual user agent 155 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" message at 160.
- the virtual user agent 155 also sends an INVITE request to set up a SIP session with the recycle bin 120 at 170.
- the recycle bin 120 accepts this session at 180.
- MSRP message session relay protocol
- SDP session description protocol
- the virtual user agent 155 proceeds to notify the user/client 100 of the SIP session at 200, and the user/client device 100 acknowledges this notification at 210.
- File 2 is sent from the user's account 110 to the network-based recycle bin 120, causing MSG 2 to disappear from the user's account 110.
- the SIP session between the virtual user agent 155 and the recycle bin 120 is torn down.
- the end result, depicted at 220, is the presence of only MSG 1 (File 1) and MSG 3 (File 3) in the user's account 110 in the user's mail storage server.
- the functions of the user's account 110 and the recycle bin 120 are collocated. In this situation, the sending of an INVITE request to set up a SIP session 170, the acknowledgement of this request 180, and the setting up of the SIP session with MSRP 190 is not necessary.
- FIG. 3 An alternative embodiment of the invention is illustrated in Figure 3 .
- the SIP REFER with INVITE request is sent directly to the network-based recycle bin bypassing the virtual user agent.
- a user decides he or she wants to delete MSG 2.
- the user/client device 100 sends an SIP REFER with INVITE request 350 to the recycle bin 120 ([email protected]).
- the SIP REFER with INVITE request 350 serves to request that a SIP Session be set up between the network-based recycle bin 120 ( [email protected] ) and the user's account 110 or the virtual user agent 155 if one is used.
- the recycle bin 120 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" message at 360.
- the recycle bin 120 also sends an INVITE request to set up a SIP session with virtual user agent 155 at 370.
- the virtual user agent 155 accepts this session at 380.
- MSRP message session relay protocol
- SDP session description protocol
- the recycle bin 120 proceeds to notify the user/client 100 of the SIP session at 400, and the user/client device 100 acknowledges this notification at 410.
- MSG 2 is sent from the user's account 110 to the network-based recycle bin 120, causing MSG 2 to disappear from the user's account 110.
- the SIP session between the virtual user agent 155 and the recycle bin 120 is torn down.
- the end result, depicted at 420, is the presence of only MSG 1 and MSG 3 in the user's account 110 in the user's mail storage server.
- the functions of the user's account 110 and the recycle bin 120 are collocated. In this situation, the sending of an INVITE request to set up a SIP session 370, the acknowledgement of this request 380, and the setting up of the SIP session with MSRP 390 is not necessary.
- the embodiment of the invention illustrated in Figure 4 is an alternative to the embodiment of Figure 3 . Similar to Figure 3 , in this embodiment the SIP REFER with INVITE request is sent directly to the network-based recycle bin bypassing the virtual user agent. However, in the embodiment in Figure 4 , the mechanism to retrieve the stored or selected messages to the recycle bin is based on the file transfer draft attached as Exhibit B. In this embodiment, the REFER request includes the SDP descriptions of the file(s) to be deleted.
- a user decides he or she wants to delete MSG 2 (File 2).
- the user/client device 100 sends an SIP REFER with INVITE request 350 to the recycle bin 120 ([email protected]).
- the SIP REFER with INVITE request 350 serves to request that a SIP Session be set up with the network-based recycle bin 120 ([email protected]).
- the recycle bin 120 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" message at 360.
- the recycle bin 120 also sends an INVITE request to set up a SIP session with virtual user agent 155 at 370.
- the virtual user agent 155 accepts this session at 380.
- MSRP message session relay protocol
- SDP session description protocol
- the recycle bin 120 proceeds to notify the user/client 100 of the SIP session at 400, and the user/client device 100 acknowledges this notification at 410.
- File 2 (MSG 2) is sent from the user's account 110 to the network-based recycle bin 120, causing File 2 (MSG 2) to disappear from the user's account 110.
- File 2 MSG2
- the end result, depicted at 420, is the presence of only File 1 (MSG 1) and File 3 (MSG 3) in the user's account 110 in the user's mail storage server.
- the functions of the user's account 110 and the recycle bin 120 are collocated. In this situation, the sending of an INVITE request to set up a SIP session 370, the acknowledgement of this request 380, and the setting up of the SIP session with MSRP 390 is not necessary.
- multiple stored messages can be selected and deleted by the user.
- a Multiple-REFER request can be sent to the recycle bin 120 to delete multiple selected messages.
- Exhibit A which is incorporated into this application, illustrates one embodiment or implementation of the Multiple-REFER request.
- the SIP Multiple-REFER with INVITE request is sent directly to the network-based recycle bin bypassing the virtual user agent.
- the SIP Multiple-REFER with INVITE request can be sent to the virtual user agent as described with respect to the embodiment illustrated in Figure 1 .
- a user decides he or she wants to delete MSG 2 and MSG 3.
- the user/client device 100 sends an SIP Multiple-REFER with INVITE request 550 to the recycle bin 120 ( [email protected] ) including a URI list containing the URIs of the stored messages to be deleted (in this case MSG 2 and MSG3).
- the SIP Multiple-REFER with INVITE request 550 serves to request that SIP Sessions be set up with the network-based recycle bin 120 ([email protected]).
- the recycle bin 120 sends INVITE requests to set up SIP sessions with virtual user agents 155 and 156 at 570 and 571, respectively, one for each message being deleted.
- INVITE request 570 corresponds to MSG2 and INVITE request 571 corresponds to MSG3.
- the virtual user agents 155 and 156 accept these sessions at 580 and 581, respectively.
- MSRP message session relay protocol
- SDP session description protocol
- MSG 2 and MSG3 are sent from the user's account 110 to the network-based recycle bin 120, causing MSG 2 and MSG3 to disappear from the user's account 110.
- the SIP session between the virtual user agents 155 and 156 and the recycle bin 120 are torn down.
- the end result, depicted at 620, is the presence of only MSG 1 in the user's account 110 in the user's mail storage server.
- the functions of the user's account 110 and the recycle bin 120 can also be collocated. In this situation, the sending of the INVITE requests to set up a SIP session 570 and 571, the acknowledgements of these requests 580 and 581, and the setting up of the SIP sessions with MSRP 590 and 591 are not necessary.
- the embodiment shown in Figure 6 illustrates deleting multiple messages when the mechanism to retrieve the stored or selected messages to the recycle bin is based on the file transfer draft attached as Exhibit B.
- the REFER request again includes the SDP descriptions of the files to be deleted.
- a user decides he or she wants to delete MSG 2 (File 2) and MSG 3 (File 3).
- the user/client device 100 sends an SIP REFER with INVITE request 550 to the recycle bin 120 ( [email protected] ) using the syntax described in Exhibit B for the stored messages (files) to be deleted (in this case MSG 2 and MSG3).
- the SIP REFER with INVITE request 550 serves to request that SIP Sessions be set up between the network-based recycle bin 120 ( [email protected] ) and the user's account 110 or the virtual user agent 155 if one is used.
- the recycle bin 120 sends INVITE requests to set up SIP sessions with virtual user agent 155 at 570.
- the virtual user agent 155 accepts a session for each file to be deleted at 580 and 581, respectively.
- MSRP message session relay protocol
- SDP session description protocol
- a SIP session is set up with virtual user agent 156.
- File 2 (MSG 2) and File 3 (MSG3) are sent from the user's account 110 to the network-based recycle bin 120, causing MSG 2 (File 2) and MSG3 (File 3) to disappear from the user's account 110.
- MSG 2 File 2
- MSG3 Fe 3
- the SIP sessions between the virtual user agent 155 and the recycle bin 120 are torn down.
- the end result, depicted at 620 is the presence of only File 1 (MSG 1) in the user's account 110 in the user's mail storage server.
- the functions of the user's account 110 and the recycle bin 120 can also be collocated. In this situation, the sending of the INVITE requests to set up a SIP session 570 and 571, the acknowledgements of these requests 580 and 581, and the setting up of the SIP sessions with MSRP 590 and 591 are not necessary.
- all stored messages can be selected and deleted by the user.
- a REFER request can be sent to the recycle bin 120 to delete all messages by referring the SIP URI for the user's mail storage account instead of an individual message or URI list of messages.
- the SIP REFER with INVITE request is sent directly to the network-based recycle bin bypassing the virtual user agent.
- the SIP REFER with INVITE request can be sent to the virtual user agent as described with respect to the embodiment illustrated in Figure 1 .
- a user decides he or she wants to delete all of the messages in his or her mail storage account.
- the user/client device 100 sends an SIP REFER with INVITE request 750 to the recycle bin 120 ( [email protected] ) including the SIP URI for the user's mail storage account (in this case [email protected]).
- the SIP REFER with INVITE request 750 serves to request that a SIP Session be set up between the network-based recycle bin 120 ( [email protected] ) and the user's account 110 or the virtual user agent 155 if one is used.
- the recycle bin 120 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" messages at 760.
- the recycle bin 120 also sends an INVITE request to set up a SIP session with virtual user agent 155 at 770.
- the virtual user agent 155 accepts this session at 780.
- MSRP message session relay protocol
- SDP session description protocol
- the recycle bin 120 proceeds to notify the user/client 100 of the SIP session at 800, and the user/client device 100 acknowledges this notification at 810.
- the functions of the user's account 110 and the recycle bin 120 can also be collocated. In this situation, the sending of the INVITE requests to set up a SIP session 770, the acknowledgements of the request 780, and the setting up of the SIP session with MSRP 790 is not necessary.
- Figure 8 shows a system 10 in which the present invention can be utilized, comprising multiple communication devices that can communicate through a network.
- the system 10 may comprise any combination of wired or wireless networks including, but not limited to, a mobile telephone network, a wireless Local Area Network (LAN), a Bluetooth personal area network, an Ethernet LAN, a token ring LAN, a wide area network, the Internet, etc.
- the system 10 may include both wired and wireless communication devices.
- the system 10 shown in Figure 8 includes a mobile telephone network 11 and the Internet 28.
- Connectivity to the Internet 28 may include, but is not limited to, long range wireless connections, short range wireless connections, and various wired connections including, but not limited to, telephone lines, cable lines, power lines, and the like.
- the exemplary communication devices of the system 10 may include, but are not limited to, a mobile telephone 12, a combination PDA and mobile telephone 14, a PDA 16, an integrated messaging device (IMD) 18, a desktop computer 20, and a notebook computer 22.
- the communication devices may be stationary or mobile as when carried by an individual who is moving.
- the communication devices may also be located in a mode of transportation including, but not limited to, an automobile, a truck, a taxi, a bus, a boat, an airplane, a bicycle, a motorcycle, etc.
- Some or all of the communication devices may send and receive calls and messages and communicate with service providers through a wireless connection 25 to a base station 24.
- the base station 24 may be connected to a network server 26 that allows communication between the mobile telephone network 11 and the Internet 28.
- the system 10 may include additional communication devices and communication devices of different types.
- Figures 9 and 10 show one representative mobile telephone 12 within which the present invention may be implemented. It should be understood, however, that the present invention is not intended to be limited to one particular type of mobile telephone 12 or other electronic device.
- Other types of electronic devices that may be used include, but are not limited to, a PDA 16, a combination PDA and mobile telephone 14, an IMD 18, a desktop computer 20, and a notebook computer 22.
- the communication devices may be stationary or mobile as when carried by an individual who is moving.
- the communication devices may also be located in a mode of transportation including, but not limited to, an automobile, a truck, a taxi, a bus, a boat, an airplane, a bicycle, a motorcycle, etc.
- the mobile telephone 12 of Figures 9 and 10 includes a housing 30, a display 32 in the form of a liquid crystal display, a keypad 34, a microphone 36, an ear-piece 38, a battery 40, an infrared port 42, an antenna 44, a smart card 46 in the form of a UICC according to one embodiment of the invention, a card reader 48, radio interface circuitry 52, codec circuitry 54, a controller 56 and a memory 58.
- Individual circuits and elements are all of a type well known in the art, for example in the Nokia range of mobile telephones.
- the system 10 shown in FIG. 8 includes a mobile telephone network 11 and the Internet 28. Connectivity to the Internet 28 may include, but is not limited to, long range wireless connections, short range wireless connections, and various wired connections including, but not limited to, telephone lines, cable lines, power lines, and the like.
- the present invention is described in the general context of method steps, which may be implemented in one embodiment by a program product including computer-executable instructions, such as program code, executed by computers in networked environments.
- program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
- Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein.
- the particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Telephonic Communication Services (AREA)
- Computer And Data Communications (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
- The present invention relates generally to session initiation protocol (SIP) services and SIP for instant messaging and presence leveraging extensions (SIMPLE) services. More particularly, the present invention relates to SIP/SIMPLE based services such as instant messaging (IM) and push-to-talk (PoC) services.
- This section is intended to provide a background or context to the invention that is recited in the claims. The description herein may include concepts that could be pursued, but are not necessarily ones that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, what is described in this section is not prior art to the description and claims in this application and is not admitted to be prior art by inclusion in this section.
- The Open Mobile Alliance (OMA) is a standards body which collectively develops open standards for use in the mobile industry. The OMA helps to create interoperable services enablers to work across countries, operators and mobile terminals and is driven by market requirements. To expand the mobile market, companies supporting the Open Mobile Alliance work to aid in the rapid and wide development and deployment of a variety of new, enhanced mobile information, communication and entertainment services.
- The OMA is currently developing IM services based on SIP, Message Session Relay Protocol (MSRP) and Extensible Markup Language (XML) Configuration Access Protocol (XCAP) protocols developed by the International Engineering Task Force (IETF) SIMPLE working group. Instant Messaging service are already deployed using several proprietary technologies and Wireless Village specifications.
- United States patent application publication number
US 2002/083064 A1 discloses a server-side recycle bin system for retaining computer files and information. - SPARKS DYNAMICSOFT R: "The SIP Refer Method draft-sparks-sip-refer-3265disc-00; draft-sparks-sip-refer-3265disc-00.txt" is an internet draft that defines the REFER method. This SIP extension requests that the recipient REFER to a resource provided in the request. It provides a mechanism allowing the party sending the REFER to be notified of the outcome of the referenced request.
- There is currently a need for a deleting Mechanism in the SIP multimedia service environment. In an http environment, if a document needs to be deleted, an "http delete" command is simply issued. However, there is currently no corresponding deleting feature or function defined for the SIP environment. In fact, even SIP extensions for services have not defined such a feature. In current multimedia services, particularly OMA SIP/SIMPLE IM, there are several requirements about storing and retrieving messages. Although there is a need for deleting and selectively deleting stored messages, such a mechanism has yet to be defined.
- The present invention comprises a novel deleting mechanism for use in SIP multimedia services. The present invention involves the use of various SIP multimedia service environment features for this purpose. In one embodiment, a "recycle bin" is defined in the network and is associated with a SIP uniform resource identifier. Messages that are stored within the network are assigned a unique identifier. If a user desires to delete the message, he or she requests that a SIP/MSRP function be set up between the message and the network-defined recycle bin. When processed, the message is transferred to the recycle bin, leaving the user's account in the user's mail storage server.
- The system and method of the present invention is simple and easy to adopt, as already-existing defined tools such as the SIP REFER method, Virtual User Agent and SIP URI are used.
- These and other advantages and features of the invention, together with the organization and manner of operation thereof, will become apparent from the following detailed description when taken in conjunction with the accompanying drawings, wherein like elements have like numerals throughout the several drawings described below.
-
-
Figure 1 is a flow chart showing the operation of a deleting mechanism for SIP multimedia services in accordance with one embodiment of the present invention; -
Figure 2 is a flow chart showing the operation of a deleting mechanism for SIP multimedia services for deleting a selected message in accordance with another embodiment of the present invention; -
Figure 3 is a flow chart showing the operation of a deleting mechanism for SIP multimedia services for deleting a selected message in accordance with still another embodiment of the present invention; -
Figure 4 is a flow chart showing the operation of a deleting mechanism for SIP multimedia services for deleting multiple selected messages in accordance with an embodiment of the present invention; -
Figure 5 is a flow chart showing the operation of a deleting mechanism for SIP multimedia services for deleting multiple selected messages in accordance with an embodiment of the present invention; -
Figure 6 is a flow chart showing the operation of a deleting mechanism for SIP multimedia services for deleting multiple selected messages in accordance with an embodiment of the present invention; -
Figure 7 is a flow chart showing the operation of a deleting mechanism for SIP multimedia services for deleting all messages in a user's mail storage account in accordance with an embodiment of the present invention; -
Figure 8 is an overview diagram of a system within which the present invention may be implemented; -
Figure 9 is a perspective view of a mobile telephone that can be used in the implementation of the present invention; -
Figure 10 is a schematic representation of the telephone circuitry of the mobile telephone ofFigure 9 ; - The present invention comprises a novel deleting mechanism for use in SIP multimedia services. The present invention involves the use of various SIP multimedia service environment features for this purpose. In one embodiment, a "recycle bin" or similar location for deleted items is defined in the network and is associated with a SIP uniform resource identifier. Messages that are stored within the network are assigned a unique identifier. If a user desires to delete the message, he or she requests that a SIP/MSRP session function be set up between the message and the network-defined recycle bin. When processed, the message is transferred to the recycle bin, leaving the user's account in the user's mail storage server.
-
Figure 1 is a flow chart showing the operation of a deleting mechanism for SIP multimedia services in accordance with one embodiment of the present invention. In particular,Figure 1 shows the interaction among a user/client device 100, a user's account inmail storage 110 and arecycle bin 120 as defined herein. Both the user'saccount 110 and therecycle bin 120 are located remote from the user/client device. In the embodiment shown inFigure 1 , the SIP URI for the uscr/clicnt device is "[email protected]." The SIP URI for the user's account is "[email protected]." The SIP URI for the recycle bin is "[email protected]." - As discussed above, stored messages in the network can be assigned unique message identifiers. Three such messages are shown at 130 in
Figure 1 with identifiers of "[email protected]" (MSG 1)
"[email protected]" (MSG 2) and
"[email protected]" (MSG 3). Alternatively, messages can be stored as files. In one embodiment, each message can be given a file name, a file type, and a hash value. Three such messages are shown inFigure 2 with identifiers of "File 1 = (filename, filetype, unique hash value)", "File 2 = (filename, filetype, unique hash value)", and "File 3 = (filename, filetype, unique hash value)". - At 140 in
Figure 1 , a user decides he or she wants to delete MSG 2. At this point, the user/client device 100 sends an SIP REFER withINVITE request 150 to the message identifier [email protected], which serves as avirtual user agent 155, at the user'saccount 110. The SIP REFER request has the network-based recycle bin address ([email protected]) in the Refer-to header. The SIP REFER withINVITE request 150 serves to request that a SIP Session be set up with the network-based recycle bin 120 ([email protected]). Thevirtual user agent 155 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" message at 160. Thevirtual user agent 155 also sends an INVITE request to set up a SIP session with therecycle bin 120 at 170. Therecycle bin 120 accepts this session at 180. At 190, an SIP session is officially set up with thevirtual user agent 155 in the form of a message session relay protocol (MSRP), with the session description protocol (SDP) media attribute set to a=SendOnly. Thevirtual user agent 155 proceeds to notify the user/client 100 of the SIP session at 200, and the user/client device 100 acknowledges this notification at 210. In the SIP/MSRP session,MSG 2 is sent from the user'saccount 110 to the network-basedrecycle bin 120, causingMSG 2 to disappear from the user'saccount 110. After successful transmission of the message MSG2, the SIP session between thevirtual user agent 155 and therecycle bin 120 is torn down. The end result, depicted at 220, is the presence ofonly MSG 1 andMSG 3 in the user'saccount 110 in the user's mail storage server. - In an alternative embodiment of the present invention, the functions of the user's
account 110 and therecycle bin 120 are collocated. In this situation, the sending of an INVITE request to set up aSIP session 170, the acknowledgement of thisrequest 180, and the setting up of the SIP session withMSRP 190 is not necessary. - An alternative embodiment in which the messages are stored as files is illustrated in
Figure 2 . In this embodiment the mechanism to retrieve the stored or selected messages to the recycle bin can be based on the file transfer draft attached as Exhibit B, which is incorporated into this application. In this embodiment, the REFER request can include the SDP descriptions of the file(s) to be deleted. - At 140 in
Figure 2 , a user decides he or she wants to delete MSG 2 (File 2). At this point, the user/client device 100 sends an SIP REFER withINVITE request 150 to the mail storage server, which serves as avirtual user agent 155, at the user'saccount 110. The SIP REFER request has the network-based recycle bin address ([email protected]) in the Refer-to header. The SIP REFER withINVITE request 150 serves to request that a SIP Session be set up with the network-based recycle bin 120 ([email protected]). Thevirtual user agent 155 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" message at 160. Thevirtual user agent 155 also sends an INVITE request to set up a SIP session with therecycle bin 120 at 170. Therecycle bin 120 accepts this session at 180. At 190, an SIP session is officially set up with thevirtual user agent 155 in the form of a message session relay protocol (MSRP), with the session description protocol (SDP) media attribute set to a=SendOnly. Thevirtual user agent 155 proceeds to notify the user/client 100 of the SIP session at 200, and the user/client device 100 acknowledges this notification at 210. In the SIP/MSRP session,File 2 is sent from the user'saccount 110 to the network-basedrecycle bin 120, causingMSG 2 to disappear from the user'saccount 110. After successful transmission of the file File 2 (MSG2), the SIP session between thevirtual user agent 155 and therecycle bin 120 is torn down. The end result, depicted at 220, is the presence of only MSG 1 (File 1) and MSG 3 (File 3) in the user'saccount 110 in the user's mail storage server. - In an alternative embodiment of the present invention, the functions of the user's
account 110 and therecycle bin 120 are collocated. In this situation, the sending of an INVITE request to set up aSIP session 170, the acknowledgement of thisrequest 180, and the setting up of the SIP session withMSRP 190 is not necessary. - An alternative embodiment of the invention is illustrated in
Figure 3 . In this embodiment the SIP REFER with INVITE request is sent directly to the network-based recycle bin bypassing the virtual user agent. For example, at 340 inFigure 3 , a user decides he or she wants to deleteMSG 2. At this point, the user/client device 100 sends an SIP REFER withINVITE request 350 to the recycle bin 120 ([email protected]). The SIP REFER withINVITE request 350 serves to request that a SIP Session be set up between the network-based recycle bin 120 ([email protected]) and the user'saccount 110 or thevirtual user agent 155 if one is used. Therecycle bin 120 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" message at 360. Therecycle bin 120 also sends an INVITE request to set up a SIP session withvirtual user agent 155 at 370. Thevirtual user agent 155 accepts this session at 380. At 390, an SIP session is officially set up with thevirtual user agent 155 in the form of a message session relay protocol (MSRP), with the session description protocol (SDP) media attribute set to a=RecvOnly. Therecycle bin 120 proceeds to notify the user/client 100 of the SIP session at 400, and the user/client device 100 acknowledges this notification at 410. In the SIP/MSRP session,MSG 2 is sent from the user'saccount 110 to the network-basedrecycle bin 120, causingMSG 2 to disappear from the user'saccount 110. After successful transmission of the message MSG2, the SIP session between thevirtual user agent 155 and therecycle bin 120 is torn down. The end result, depicted at 420, is the presence ofonly MSG 1 andMSG 3 in the user'saccount 110 in the user's mail storage server. - Similar to the earlier embodiment, alternatively the functions of the user's
account 110 and therecycle bin 120 are collocated. In this situation, the sending of an INVITE request to set up aSIP session 370, the acknowledgement of thisrequest 380, and the setting up of the SIP session withMSRP 390 is not necessary. - The embodiment of the invention illustrated in
Figure 4 is an alternative to the embodiment ofFigure 3 . Similar toFigure 3 , in this embodiment the SIP REFER with INVITE request is sent directly to the network-based recycle bin bypassing the virtual user agent. However, in the embodiment inFigure 4 , the mechanism to retrieve the stored or selected messages to the recycle bin is based on the file transfer draft attached as Exhibit B. In this embodiment, the REFER request includes the SDP descriptions of the file(s) to be deleted. - At 340 in
Figure 4 , a user decides he or she wants to delete MSG 2 (File 2). At this point, the user/client device 100 sends an SIP REFER withINVITE request 350 to the recycle bin 120 ([email protected]). The SIP REFER withINVITE request 350 serves to request that a SIP Session be set up with the network-based recycle bin 120 ([email protected]). Therecycle bin 120 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" message at 360. Therecycle bin 120 also sends an INVITE request to set up a SIP session withvirtual user agent 155 at 370. Thevirtual user agent 155 accepts this session at 380. At 390, an SIP session is officially set up with thevirtual user agent 155 in the form of a message session relay protocol (MSRP), with the session description protocol (SDP) media attribute set to a=RecOnly. Therecycle bin 120 proceeds to notify the user/client 100 of the SIP session at 400, and the user/client device 100 acknowledges this notification at 410. In the SIP/MSRP session, File 2 (MSG 2) is sent from the user'saccount 110 to the network-basedrecycle bin 120, causing File 2 (MSG 2) to disappear from the user'saccount 110. After successful transmission of File 2 (MSG2), the SIP session between thevirtual user agent 155 and therecycle bin 120 is torn down. The end result, depicted at 420, is the presence of only File 1 (MSG 1) and File 3 (MSG 3) in the user'saccount 110 in the user's mail storage server. - Similar to the earlier embodiment, alternatively the functions of the user's
account 110 and therecycle bin 120 are collocated. In this situation, the sending of an INVITE request to set up aSIP session 370, the acknowledgement of thisrequest 380, and the setting up of the SIP session withMSRP 390 is not necessary. - In another embodiment, multiple stored messages can be selected and deleted by the user. In this embodiment, illustrated in
Figure 5 a Multiple-REFER request can be sent to therecycle bin 120 to delete multiple selected messages.. Exhibit A, which is incorporated into this application, illustrates one embodiment or implementation of the Multiple-REFER request. In the embodiment shown inFigure 5 , the SIP Multiple-REFER with INVITE request is sent directly to the network-based recycle bin bypassing the virtual user agent. Alternatively, the SIP Multiple-REFER with INVITE request can be sent to the virtual user agent as described with respect to the embodiment illustrated inFigure 1 . - At 540 in
Figure 5 , a user decides he or she wants to deleteMSG 2 andMSG 3. At this point, the user/client device 100 sends an SIP Multiple-REFER withINVITE request 550 to the recycle bin 120 ([email protected]) including a URI list containing the URIs of the stored messages to be deleted (in thiscase MSG 2 and MSG3). The SIP Multiple-REFER withINVITE request 550 serves to request that SIP Sessions be set up with the network-based recycle bin 120 ([email protected]). Therecycle bin 120 sends INVITE requests to set up SIP sessions withvirtual user agents INVITE request 570 corresponds to MSG2 andINVITE request 571 corresponds to MSG3. Thevirtual user agents virtual user agent 155 in the form of a message session relay protocol (MSRP), with the session description protocol (SDP) media attribute set to a=RecvOnly and at 591 a SIP session is set up withvirtual user agent 156. In the SIP/MSRP sessions,MSG 2 and MSG3 are sent from the user'saccount 110 to the network-basedrecycle bin 120, causingMSG 2 and MSG3 to disappear from the user'saccount 110. After successful transmission of the messages MSG2 and MSG3, the SIP session between thevirtual user agents recycle bin 120 are torn down. The end result, depicted at 620, is the presence ofonly MSG 1 in the user'saccount 110 in the user's mail storage server. - Similar to the earlier embodiments, the functions of the user's
account 110 and therecycle bin 120 can also be collocated. In this situation, the sending of the INVITE requests to set up aSIP session requests MSRP - The embodiment shown in
Figure 6 illustrates deleting multiple messages when the mechanism to retrieve the stored or selected messages to the recycle bin is based on the file transfer draft attached as Exhibit B. In this embodiment, the REFER request again includes the SDP descriptions of the files to be deleted. At 540 inFigure 6 , a user decides he or she wants to delete MSG 2 (File 2) and MSG 3 (File 3). At this point, the user/client device 100 sends an SIP REFER withINVITE request 550 to the recycle bin 120 ([email protected]) using the syntax described in Exhibit B for the stored messages (files) to be deleted (in thiscase MSG 2 and MSG3). In this case, the SDP parameters for each file (message) that is to be deleted needs to be sent in a separate media line "m =". The SIP REFER withINVITE request 550 serves to request that SIP Sessions be set up between the network-based recycle bin 120 ([email protected]) and the user'saccount 110 or thevirtual user agent 155 if one is used. Therecycle bin 120 sends INVITE requests to set up SIP sessions withvirtual user agent 155 at 570. Thevirtual user agent 155 accepts a session for each file to be deleted at 580 and 581, respectively. At 590, a SIP session is officially set up with thevirtual user agent 155 in the form of a message session relay protocol (MSRP), with the session description protocol (SDP) media attribute set to a=RecvOnly and at 591 a SIP session is set up withvirtual user agent 156. In the SIP/MSRP sessions, File 2 (MSG 2) and File 3 (MSG3) are sent from the user'saccount 110 to the network-basedrecycle bin 120, causing MSG 2 (File 2) and MSG3 (File 3) to disappear from the user'saccount 110. After successful transmission of the files File 2 (MSG 2) and File 3 (MSG3), the SIP sessions between thevirtual user agent 155 and therecycle bin 120 are torn down. The end result, depicted at 620, is the presence of only File 1 (MSG 1) in the user'saccount 110 in the user's mail storage server. - Similar to the earlier embodiments, the functions of the user's
account 110 and therecycle bin 120 can also be collocated. In this situation, the sending of the INVITE requests to set up aSIP session requests MSRP - In still another embodiment, all stored messages can be selected and deleted by the user. In this embodiment, illustrated in
Figure 7 a REFER request can be sent to therecycle bin 120 to delete all messages by referring the SIP URI for the user's mail storage account instead of an individual message or URI list of messages. Again in the embodiment shown inFigure 7 , the SIP REFER with INVITE request is sent directly to the network-based recycle bin bypassing the virtual user agent. Alternatively, the SIP REFER with INVITE request can be sent to the virtual user agent as described with respect to the embodiment illustrated inFigure 1 . - At 740 in
Figure 7 , a user decides he or she wants to delete all of the messages in his or her mail storage account. At this point, the user/client device 100 sends an SIP REFER withINVITE request 750 to the recycle bin 120 ([email protected]) including the SIP URI for the user's mail storage account (in this case [email protected]). The SIP REFER withINVITE request 750 serves to request that a SIP Session be set up between the network-based recycle bin 120 ([email protected]) and the user'saccount 110 or thevirtual user agent 155 if one is used. Therecycle bin 120 responds by accepting the SIP REFER request from the user/client device 100 with a "202 ACCEPT" messages at 760. Therecycle bin 120 also sends an INVITE request to set up a SIP session withvirtual user agent 155 at 770. Thevirtual user agent 155 accepts this session at 780. At 790, a SIP session is officially set up with thevirtual user agent 155 in the form of a message session relay protocol (MSRP), with the session description protocol (SDP) media attribute set to a=RecvOnly. Therecycle bin 120 proceeds to notify the user/client 100 of the SIP session at 800, and the user/client device 100 acknowledges this notification at 810. In the SIP/MSRP sessions, all messages in the user's mail storage account (MSG1,MSG 2 and MSG3 in this case) are sent from the user'saccount 110 to the network-basedrecycle bin 120, causing all messages to disappear from the user'saccount 110. After successful transmission of the all of the messages from the user's mail storage account, the SIP session between thevirtual user agent 155 and therecycle bin 120 is torn down. The end result, depicted at 820, is the no messages left in the user'saccount 110 in the user's mail storage server. - Similar to the earlier embodiments, the functions of the user's
account 110 and therecycle bin 120 can also be collocated. In this situation, the sending of the INVITE requests to set up aSIP session 770, the acknowledgements of therequest 780, and the setting up of the SIP session withMSRP 790 is not necessary. -
Figure 8 shows asystem 10 in which the present invention can be utilized, comprising multiple communication devices that can communicate through a network. Thesystem 10 may comprise any combination of wired or wireless networks including, but not limited to, a mobile telephone network, a wireless Local Area Network (LAN), a Bluetooth personal area network, an Ethernet LAN, a token ring LAN, a wide area network, the Internet, etc. Thesystem 10 may include both wired and wireless communication devices. - For exemplification, the
system 10 shown inFigure 8 includes amobile telephone network 11 and theInternet 28. Connectivity to theInternet 28 may include, but is not limited to, long range wireless connections, short range wireless connections, and various wired connections including, but not limited to, telephone lines, cable lines, power lines, and the like. - The exemplary communication devices of the
system 10 may include, but are not limited to, amobile telephone 12, a combination PDA andmobile telephone 14, aPDA 16, an integrated messaging device (IMD) 18, adesktop computer 20, and anotebook computer 22. The communication devices may be stationary or mobile as when carried by an individual who is moving. The communication devices may also be located in a mode of transportation including, but not limited to, an automobile, a truck, a taxi, a bus, a boat, an airplane, a bicycle, a motorcycle, etc. Some or all of the communication devices may send and receive calls and messages and communicate with service providers through awireless connection 25 to abase station 24. Thebase station 24 may be connected to anetwork server 26 that allows communication between themobile telephone network 11 and theInternet 28. Thesystem 10 may include additional communication devices and communication devices of different types. -
Figures 9 and10 show one representativemobile telephone 12 within which the present invention may be implemented. It should be understood, however, that the present invention is not intended to be limited to one particular type ofmobile telephone 12 or other electronic device. Other types of electronic devices that may be used include, but are not limited to, aPDA 16, a combination PDA andmobile telephone 14, anIMD 18, adesktop computer 20, and anotebook computer 22. The communication devices may be stationary or mobile as when carried by an individual who is moving. The communication devices may also be located in a mode of transportation including, but not limited to, an automobile, a truck, a taxi, a bus, a boat, an airplane, a bicycle, a motorcycle, etc. - The
mobile telephone 12 ofFigures 9 and10 includes ahousing 30, adisplay 32 in the form of a liquid crystal display, akeypad 34, amicrophone 36, an ear-piece 38, abattery 40, aninfrared port 42, anantenna 44, asmart card 46 in the form of a UICC according to one embodiment of the invention, acard reader 48,radio interface circuitry 52,codec circuitry 54, acontroller 56 and amemory 58. Individual circuits and elements are all of a type well known in the art, for example in the Nokia range of mobile telephones. For exemplification, thesystem 10 shown inFIG. 8 includes amobile telephone network 11 and theInternet 28. Connectivity to theInternet 28 may include, but is not limited to, long range wireless connections, short range wireless connections, and various wired connections including, but not limited to, telephone lines, cable lines, power lines, and the like. - The present invention is described in the general context of method steps, which may be implemented in one embodiment by a program product including computer-executable instructions, such as program code, executed by computers in networked environments. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.
- Software and web implementations of the present invention could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps. It should also be noted that the words "component" and "module," as used herein and in the claims, is intended to encompass implementations using one or more lines of software code, and/or hardware implementations, and/or equipment for receiving manual inputs.
- The foregoing description of embodiments of the present invention have been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the present invention to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the present invention as defined by the present claims. The embodiments were chosen and described in order to explain the principles of the present invention and its practical application to enable one skilled in the art to utilize the present invention in various embodiments and with various modifications as are suited to the particular use contemplated.
-
-
Claims (39)
- A method of deleting an item from a user's user account (110) in a server in a session initiation protocol, SIP, multimedia environment, comprising:receiving (150) a request from a user device (100) of the user to delete the item from the user account (110), wherein the request comprises a SIP REFER request;in response to receiving the request, establishing (170, 180) a SIP session between a network-based deleted items location (120) and the user account (110); andafter establishing the SIP session, transferring (190) the item from the user account (110) to the network-based deleted items location (120) using the SIP session, thereby causing (220) the item to be deleted from the user account (110).
- The method of claim 1, wherein said establishing is between the network-based deleted items location and a mail storage server at the user account.
- The method of claim 2, wherein the SIP REFER request includes an address for the network-based deleted items location (120) in its Refer-to header.
- The method of claim 1, wherein the request comprises a SIP Multiple-REFER request.
- The method of claim 1, further comprising, in response to receiving the request, transmitting an acknowledgment of the request to the user device (100).
- The method of claim 1, wherein the SIP session is established with a session description protocol, SDP, directional attribute set to a=SendOnly.
- The method of claim 1, wherein the SIP session is established with a session description protocol, SDP, directional attribute set to a=RecvOnly
- The method of claim 1, wherein the item includes a unique message identifier, and wherein the unique message identifier is included in the request from the user device (100).
- The method of claim 1, wherein the request is to delete multiple items from the user account (110) and wherein a uniform resource identifier, URI, URI-list of the multiple items is included in the request from the user device (100).
- The method of claim 1, wherein the request is to delete all items from the user account (110) and wherein a SIP uniform resource identifier, URI, for the user account (110) is included in the request from the user device (100).
- The method of claim 1, wherein the item is stored as a file having session description protocol, SDP, descriptions and wherein the file SDP descriptions are included in the request from the user device (100).
- The method of claim 11 wherein the request is to delete multiple items from the user account (110) and wherein file SDP descriptions for each of the multiple items is included in the request from the user device (100), the file SDP descriptions for each file being included in a separate media line in the request.
- The method of claim 1, wherein the user device (100), the user account and the network-based deleted items location (120) each possess a unique uniform resource identifier.
- The method of claim 1, wherein message session relay protocol, MSRP, is used to transfer the item from the user account (110) to the network-based deleted items location (120).
- A computer program product, embodied in a computer-readable medium, which computer code, when executed by a computing device to delete an item from a user's user account (110) in a server in a session initiation protocol, SIP, multimedia environment, comprising:computer code for receiving (150) a request from a user device (100) of the user to delete the item from the user account (110), wherein the request comprises a SIP REFER request;computer code for establishing (170, 180), in response to the request, a SIP session between a network-based deleted items location (120) and the user account (110); andcomputer code for, after establishing the SIP session, transferring (190) the item from the user account (110) to the network-based deleted items location (120), thereby causing (220) the item to be deleted from the user account (110).
- The computer program product of claim 15, wherein said establishing is between the network-based deleted items location and a mail storage server at the user account.
- The computer program product of claim 16, wherein the SIP REFER request includes an address for the network-based deleted items location (120) in its Refer-to header.
- The computer program product of claim 15, wherein the request comprises a SIP Multiple-REFER request.
- The computer program product of claim 15, wherein the SIP session is established with a session description protocol, SDP, directional attribute set to a=SendOnly.
- The computer program product of claim 15, wherein the SIP session is established with a session description protocol, SDP, directional attribute set to a=RecvOnly.
- The computer program product of claim 15, wherein the item includes a unique message identifier, and wherein the unique message identifier is included in the request from the user device (100).
- The computer program product of claim 15, wherein the request is to delete multiple items from the user account (110) and wherein a uniform resource identifier, URI, URI-list of the multiple items is included in the request from the user device (100).
- The computer program product of claim 15, wherein the request is to delete all items from the user account (110) and wherein a SIP uniform resource identifier, URI, for the user account (110) is included in the request from the user device (100).
- The computer program product of claim 15, wherein the item is stored as a file having session description protocol, SDP, descriptions and wherein the SDP descriptions are included in the request from the user device (100).
- The computer program product of claim 24, wherein the request is to delete multiple items from the user account (110) and wherein file SDP descriptions for each of the multiple items is included in the request from the user device (100) the file SDP descriptions for each file being included in a separate media line in the request.
- The computer program product of claim 15, wherein the user device (100), the user account and the network-based deleted items location each possess a unique uniform resource identifier.
- The computer program product of claim 15, wherein message session relay protocol, MSRP, is used to transfer the item from the user account (110) to the network-based deleted items location (120).
- An electronic device, comprising:a processor; anda memory unit communicatively connected to the processor and including:computer code for receiving (150) a session initiation protocol, SIP, request from a user device (100) of a user to delete an item from a user account (110) of the user in a server, wherein the request comprises a SIP REFER request;computer code for establishing (170, 180), in response to receiving the request, a SIP session between a network-based deleted items location (120) and the user account (110); andcomputer code for, after establishing the SIP session, transferring (190) the item from the user account (110) to the network-based deleted items location (120), thereby causing (220) the item to be deleted from the user account (110).
- The electronic device of claim 28, wherein said establishing is between the network-based deleted items location and a mail storage server at the user account.
- The electronic device of claim 29, wherein the SIP REFER request includes an address for the network-based deleted items location (120) in its Refer-to header.
- The electronic device of claim 28 wherein the request comprises a SIP Multiple-REFER request.
- The electronic device of claim 28, wherein the SIP session is established with a session description protocol, SDP, directional attribute set to a=SendOnly.
- The electronic device of claim 28, wherein the SIP session is established with a session description protocol, SDP, directional attribute set to a=RecvOnly.
- The electronic device of claim 28, wherein the item includes a unique message identifier, and wherein the unique message identifier is included in the request from the user device (100).
- The electronic device of claim 28, wherein the request is to delete multiple items from the user account (110) and wherein a uniform resource identifier, URI, URI-list of the multiple items is included in the request from the user device (100).
- The electronic device of claim 28, wherein the request is to delete all items from the user account (110) and wherein a SIP uniform resource identifier, URI, for the user account (110) is included in the request from the user device (100).
- The electronic device of claim 28, wherein the item is stored as a file having session description protocol, SDP, descriptions and wherein the file SDP descriptions are included in the request from the user device (100).
- The electronic device of claim 37, wherein the request is to delete multiple items from the user account (110) and wherein file SDP descriptions for each of the multiple items is included in the request from the user device (100), the file SDP descriptions for each file being included in a separate media line in the request.
- The electronic device of claim 28, wherein message session relay protocol, MSRP, is used to transfer the item from the user account (110) to the network-based deleted items location (120).
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US78864706P | 2006-04-03 | 2006-04-03 | |
PCT/IB2007/051193 WO2007113770A2 (en) | 2006-04-03 | 2007-04-03 | Deleting mechanism in sip multimedia services |
Publications (3)
Publication Number | Publication Date |
---|---|
EP2008425A2 EP2008425A2 (en) | 2008-12-31 |
EP2008425A4 EP2008425A4 (en) | 2014-07-30 |
EP2008425B1 true EP2008425B1 (en) | 2019-01-09 |
Family
ID=38564053
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP07713248.8A Active EP2008425B1 (en) | 2006-04-03 | 2007-04-03 | Deleting mechanism in sip multimedia services |
Country Status (12)
Country | Link |
---|---|
US (1) | US7805490B2 (en) |
EP (1) | EP2008425B1 (en) |
JP (1) | JP4775490B2 (en) |
KR (1) | KR100977188B1 (en) |
CN (1) | CN101455050B (en) |
AU (1) | AU2007232195B2 (en) |
BR (1) | BRPI0710719B1 (en) |
CA (1) | CA2661954C (en) |
MX (1) | MX2008012811A (en) |
RU (1) | RU2404549C2 (en) |
WO (1) | WO2007113770A2 (en) |
ZA (1) | ZA200809301B (en) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100077057A1 (en) * | 2008-09-23 | 2010-03-25 | Telefonaktiebolaget Lm Ericsson (Publ) | File Transfer in Conference Services |
JP2011035671A (en) * | 2009-07-31 | 2011-02-17 | Fujitsu Ltd | Server device, and anonymous calling method |
US9934895B2 (en) | 2012-06-29 | 2018-04-03 | Intel Corporation | Spiral near field communication (NFC) coil for consistent coupling with different tags and devices |
CN104158720A (en) * | 2013-05-14 | 2014-11-19 | 腾讯科技(深圳)有限公司 | Chatting record clearing method and system, and mobile terminal |
CN105208071A (en) * | 2014-11-26 | 2015-12-30 | 维沃移动通信有限公司 | Mobile terminal data deletion method and mobile terminal |
KR101538310B1 (en) * | 2014-12-17 | 2015-07-22 | 한국인터넷진흥원 | APPARATUS, SYSTEM AND METHOD FOR DETECTING ABNORMAL MESSAGE FOR OBTAINING LOCATION INFORMATION BASED ON VoLTE SERVICE IN 4G MOBILE NETWORKS |
CN105490919B (en) * | 2015-11-24 | 2019-11-08 | 小米科技有限责任公司 | Message cancelling method and device |
US11716363B2 (en) | 2017-11-02 | 2023-08-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Messaging resource function |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000250864A (en) | 1999-03-02 | 2000-09-14 | Fuji Xerox Co Ltd | Cooperative work support system |
US6871215B2 (en) | 2000-04-11 | 2005-03-22 | Telecommunication Systems Inc. | Universal mail wireless e-mail reader |
US7133923B2 (en) * | 2000-12-11 | 2006-11-07 | Acme Packet, Inc. | System and method for assisting in controlling real-time transport protocol flow through multiple networks via screening |
US6611836B2 (en) * | 2000-12-26 | 2003-08-26 | Simdesk Technologies, Inc. | Server-side recycle bin system |
US20020138654A1 (en) * | 2001-03-21 | 2002-09-26 | Zhigang Liu | Apparatus, and associated method, for facilitating deletion of dictionary content pursuant to communication of signaling protocol messages |
JP2002366410A (en) * | 2001-06-06 | 2002-12-20 | Fujitsu Ltd | Trash box server and trash box processing program |
US7461378B2 (en) * | 2002-06-11 | 2008-12-02 | Siemens Communications, Inc. | Methods and apparatus for processing an instant message |
WO2004036366A2 (en) * | 2002-10-16 | 2004-04-29 | Synthetic Networks, Inc. | Load testing methods and systems with transaction variability andconsistency |
US7653693B2 (en) * | 2003-09-05 | 2010-01-26 | Aol Llc | Method and system for capturing instant messages |
US20050050170A1 (en) * | 2003-08-29 | 2005-03-03 | International Business Machines Corporation | Method and apparatus for securely conducting digital property trade |
US7752271B2 (en) * | 2004-06-01 | 2010-07-06 | International Business Machines Corporation | Method of retracting an instant message |
US20060036689A1 (en) | 2004-06-04 | 2006-02-16 | John Buford | Personal messaging proxy |
US7840681B2 (en) | 2004-07-30 | 2010-11-23 | International Business Machines Corporation | Method and apparatus for integrating wearable devices within a SIP infrastructure |
KR100690793B1 (en) * | 2005-01-19 | 2007-03-09 | 엘지전자 주식회사 | Method for transmitting data in multimedia system |
US9258259B2 (en) * | 2005-09-30 | 2016-02-09 | Nokia Technologies Oy | Retrieval of offline instant messages |
WO2007105074A2 (en) * | 2006-03-13 | 2007-09-20 | Nokia Corporation | Deleting mechanism in sip multimedia services |
-
2007
- 2007-04-03 AU AU2007232195A patent/AU2007232195B2/en active Active
- 2007-04-03 WO PCT/IB2007/051193 patent/WO2007113770A2/en active Application Filing
- 2007-04-03 BR BRPI0710719-6A patent/BRPI0710719B1/en active IP Right Grant
- 2007-04-03 CN CN2007800183922A patent/CN101455050B/en active Active
- 2007-04-03 JP JP2009503713A patent/JP4775490B2/en active Active
- 2007-04-03 CA CA2661954A patent/CA2661954C/en active Active
- 2007-04-03 US US11/696,074 patent/US7805490B2/en active Active
- 2007-04-03 KR KR1020087026800A patent/KR100977188B1/en active IP Right Grant
- 2007-04-03 MX MX2008012811A patent/MX2008012811A/en active IP Right Grant
- 2007-04-03 EP EP07713248.8A patent/EP2008425B1/en active Active
- 2007-04-03 RU RU2008140278/09A patent/RU2404549C2/en active
-
2008
- 2008-10-30 ZA ZA200809301A patent/ZA200809301B/en unknown
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Publication number | Publication date |
---|---|
KR100977188B1 (en) | 2010-08-20 |
US20070233682A1 (en) | 2007-10-04 |
KR20090006154A (en) | 2009-01-14 |
WO2007113770A2 (en) | 2007-10-11 |
MX2008012811A (en) | 2008-10-15 |
RU2008140278A (en) | 2010-05-10 |
JP4775490B2 (en) | 2011-09-21 |
EP2008425A2 (en) | 2008-12-31 |
US7805490B2 (en) | 2010-09-28 |
CN101455050B (en) | 2012-11-14 |
RU2404549C2 (en) | 2010-11-20 |
ZA200809301B (en) | 2009-11-25 |
BRPI0710719A2 (en) | 2012-02-28 |
WO2007113770A3 (en) | 2008-02-14 |
EP2008425A4 (en) | 2014-07-30 |
AU2007232195A1 (en) | 2007-10-11 |
CA2661954A1 (en) | 2007-10-11 |
AU2007232195B2 (en) | 2011-01-27 |
CA2661954C (en) | 2012-08-14 |
BRPI0710719B1 (en) | 2020-03-03 |
JP2009532795A (en) | 2009-09-10 |
CN101455050A (en) | 2009-06-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2008425B1 (en) | Deleting mechanism in sip multimedia services | |
US7478146B2 (en) | System, apparatus, and method for communicating capabilities of a mobile device | |
KR100895028B1 (en) | System, method and computer program product for providing content to a terminal and directing the rendering of such content at the terminal | |
EP2345267B1 (en) | Method and apparatus for address book contact management | |
EP1427238A1 (en) | Method and system for creating content-shared calls | |
KR19990083633A (en) | Centralized Service Management System for Two-Way Interactive Communication Devices in Data Networks | |
KR20070038094A (en) | System, method and computer program product for providing content to a terminal | |
US8250168B2 (en) | Methods for accessing published contents from a mobile device | |
US20080294729A1 (en) | Email object for open mobile alliance data synchronization usage | |
EP1779691A1 (en) | System and method for application distribution | |
KR100733603B1 (en) | Mobile multimedia instant messenger service method and mobile multimedia messenger serive method using the same system | |
US7917590B2 (en) | Deleting mechanism in SIP multimedia services | |
JP4889813B1 (en) | Data brokerage system | |
US7203505B1 (en) | Message transfer from a source device via a mobile terminal device to a third device | |
KR101973531B1 (en) | Method and apparatus for automatically sharing applications between multiple clients | |
CN102160052A (en) | Method and apparatus for address book contact management | |
JP4774275B2 (en) | Communication control system and control device | |
CN101400020B (en) | Method, system and server for customer passively entering group to obtain group lists | |
Lakay et al. | SIP-based content development for wireless mobile devices | |
JP2005149447A (en) | E-mail conversion reply system | |
MXPA01010800A (en) | Radio terminal with browser | |
MXPA01010799A (en) | Radio terminal with browser |
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: 20081103 |
|
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 MT NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR MK RS |
|
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 INC. Owner name: NOKIA CORPORATION |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20140630 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 29/08 20060101ALI20140624BHEP Ipc: H04L 29/06 20060101AFI20140624BHEP |
|
17Q | First examination report despatched |
Effective date: 20150904 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20180130 |
|
GRAJ | Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted |
Free format text: ORIGINAL CODE: EPIDOSDIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTC | Intention to grant announced (deleted) | ||
INTG | Intention to grant announced |
Effective date: 20180625 |
|
GRAJ | Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted |
Free format text: ORIGINAL CODE: EPIDOSDIGR1 |
|
GRAL | Information related to payment of fee for publishing/printing deleted |
Free format text: ORIGINAL CODE: EPIDOSDIGR3 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
GRAR | Information related to intention to grant a patent recorded |
Free format text: ORIGINAL CODE: EPIDOSNIGR71 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTC | Intention to grant announced (deleted) | ||
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
INTG | Intention to grant announced |
Effective date: 20181129 |
|
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 MT 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 Ref country code: AT Ref legal event code: REF Ref document number: 1088722 Country of ref document: AT Kind code of ref document: T Effective date: 20190115 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602007057365 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
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: 1088722 Country of ref document: AT Kind code of ref document: T Effective date: 20190109 |
|
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: 20190109 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: 20190509 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: 20190109 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: 20190109 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: 20190109 Ref country code: ES 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: 20190109 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20190109 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: 20190509 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: 20190410 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: 20190409 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602007057365 Country of ref document: DE |
|
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: 20190109 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: 20190109 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: 20190109 Ref country code: IT 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: 20190109 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: 20190109 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: 20190109 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: 20190109 |
|
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: CH Ref legal event code: PL |
|
26N | No opposition filed |
Effective date: 20191010 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20190430 |
|
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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190109 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190403 |
|
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: 20190430 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190430 |
|
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: 20190430 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: 20190109 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190430 |
|
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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190109 |
|
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: 20190403 |
|
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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190109 |
|
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: 20070403 Ref country code: MT 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: 20190109 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602007057365 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0029060000 Ipc: H04L0065000000 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20240315 Year of fee payment: 18 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20240229 Year of fee payment: 18 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240306 Year of fee payment: 18 |