EP2724514A1 - Mmtel network call logging - Google Patents

Mmtel network call logging

Info

Publication number
EP2724514A1
EP2724514A1 EP11726827.6A EP11726827A EP2724514A1 EP 2724514 A1 EP2724514 A1 EP 2724514A1 EP 11726827 A EP11726827 A EP 11726827A EP 2724514 A1 EP2724514 A1 EP 2724514A1
Authority
EP
European Patent Office
Prior art keywords
call
information
data handling
handling unit
call event
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
EP11726827.6A
Other languages
German (de)
French (fr)
Other versions
EP2724514B1 (en
Inventor
Mattias Wildeman
Jan GJÄRDMAN
Jan Lidin
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP2724514A1 publication Critical patent/EP2724514A1/en
Application granted granted Critical
Publication of EP2724514B1 publication Critical patent/EP2724514B1/en
Not-in-force 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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/56—Arrangements for indicating or recording the called number at the calling subscriber's set
    • 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/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • Embodiments herein relate generally to logging of call events in a MMTel communication network, and in particular to logging of call events in a storage server.
  • MMTel Multimedia Telephony Service
  • Some existing solutions are client centric, i.e. the mobile phone or IP Multimedia Subsystem (IMS) client is responsible for storing the data and then presenting a consolidated view to a user of the phone.
  • Some existing solutions are network centric but not consolidated, for example Short Message Service (SMS), Multimedia Messaging Service (MMS), Session Initiation Protocol (SIP)
  • SMS Short Message Service
  • MMS Multimedia Messaging Service
  • SIP Session Initiation Protocol
  • SIP MESSAGE message are stored in one network log and call data is stored in a different network log.
  • SIP Message it is intended a SIP MESSAGE message, i.e. a SIP message called MESSAGE.
  • the client centric solutions have several drawbacks, for example, when a phone is not connected to the network because it is turned off or is out of range, call events that occur from other devices trying to reach the not connected phone will not be logged in the phone, e.g. missed calls. If multiple clients are connected to the same identity, e.g. phone number or SIP Uniform Resource Identifier (URI), mediation issues occur. For example, if a message is deleted on one device, the same message may still be present on other devices, communication initiated on one device is not visible at other devices and calls answered on one device may be registered as missed calls on other devices. Further, if the phone is lost, then the log information is also lost, and the log information may further potentially be read by an outside party.
  • URI Uniform Resource Identifier
  • a method in a data handling unit for handling information regarding call events in a Multimedia Telephony Service, MMTel, network for enabling call logging.
  • the method comprises receiving information on at least one call event, generating a SIP Message comprising call log information referring to the call event, and sending the generated SIP Message towards a storage server.
  • the storage server is enabled to store call log information regarding the call event.
  • a data handling in a Multimedia Telephony Service, MMTel, network adapted for handling information regarding calls is provided.
  • the data handling unit is configured to receive information on at least one call event, to generate a SIP Message comprising call log information referring to the call event, and to send the generated SIP Message towards a storage server.
  • the storage server is enabled to store call log information regarding the call event.
  • the data handling unit and the method therein have several advantages.
  • a user may access his/her call log information and obtain information regarding different call events, e.g. missed calls, the reason why they were missed, to which device or terminal the call was placed and so on.
  • call events which occur when a phone is not connected to a network will be logged.
  • the logging of call events regarding the telephone number will be logged.
  • any deletion of local call information on a specific device will not incur deletion on the storage server so that the information is not lost.
  • the call event log information is not lost.
  • Yet an advantage is that the stored call information is easily accessible from the storage server at any later stage.
  • Figure 1 is a flowchart of an exemplifying embodiment of a method in a data handling unit.
  • Figure 2a is a block diagram schematically illustrating an exemplifying embodiment of a data handling unit.
  • Figure 2b is a block diagram of an exemplifying embodiment of an MMTel network.
  • Figure 2c is a block diagram of yet an exemplifying embodiment of an MMTel network
  • Figure 2d is a schematic signalling diagram of an exemplifying embodiment of a method in a data handling unit.
  • Figure 2e is a schematic signalling diagram of yet an exemplifying embodiment of a method in a data handling unit.
  • a data handling unit and a method therein are provided for handling information regarding call events in a Multimedia Telephony Service, MMTel, network for enabling call logging.
  • the logging of call events are performed in such a way that a SIP Message is generated for a call event and sent to a storage server.
  • a call event is any of a missed call, a placed call, a received call, a diverted call, a barred call, and so on.
  • Figure 1 illustrates the method comprising receiving 1 10 information on at least one call event, generating 130 a SIP Message comprising call log information referring to the call event, and sending 140 the generated SIP
  • the storage server is enabled to store call log information regarding the call event.
  • a terminal e.g. a phone
  • the actions taken by user A generates call event information, both with regards to user A and user B.
  • the generated call information comprises e.g. successful placed call, call duration, identity of called user, and so on.
  • the generated call information comprises e.g. successful received call, call duration, identity of calling user, and so on.
  • the generated call information comprises e.g. un-successful placed call, identity of called user and so on.
  • the generated call information comprises e.g. missed call, missed call while busy on phone, missed call while out-of-coverage or missed call while phone turned off.
  • the call information is generated with regards to a user identity, meaning that two separate pieces of call information are generated, one call information for user A and one call information for user B.
  • the generated call information is received 1 10 in the data handling unit. Then a SIP Message comprising call log information referring to the call event is generated 130 and sent 140 to a storage server. In this way, call log information is generated and then stored in the storage server.
  • the stored call log information for a specific user may be accessed by the user, using one of his communication devices to obtain the call log information relating to him/her.
  • the generated call log information in this example for user A and B may be generated separately or together.
  • the received call log information comprises call event information regarding both users.
  • two separate call event information are received, one call event information for user A and one call event information for user B.
  • the exemplified embodiment has several advantages.
  • a user may access his/her call log information and obtain information regarding different call events, e.g. missed calls, the reason why they were missed, to which device or terminal the call was placed and so on.
  • call events which occur when a phone is not connected to a network will be logged.
  • the logging of call events regarding the telephone number will be logged.
  • any deletion of local call information on a specific device will not incur deletion on the storage server so that the information is not lost.
  • the call event log information is not lost.
  • Yet an advantage is that the stored call information is easily accessible from the storage server at any later stage.
  • the method further comprises matching 120 a caller or called party to settings in a user profile for the caller or called party, using the received information before generating the SIP Message and generating the SIP Message comprising call log information referring to the call event, only if settings in the user profile for the caller or called party indicates that call event information is to be saved.
  • the data handling unit receives 1 10 information on a call event comprising e.g. call event type and the identity of the user for who the call event is related. For example, if a user A tries to place a call to a user B and the call attempt is un-successful, then the received 1 10 call event information for user B may comprise e.g. missed call from user A while busy on phone.
  • User B has a user profile which in an example is stored in an MMTel Application Server, and the user profile indicates whether or not call event information is to be saved. Alternatively, the user profile is stored in a Home Subscriber Server (HSS) and is then fetched by the MMTel Application Server when a call event is executed.
  • HSS Home Subscriber Server
  • the data handling unit may simply discard the received 1 10 information on at least one call event.
  • the method comprises generating 130 a SIP Message comprising call log information referring to the call event, and sending 140 the generated SIP Message towards a storage server as described above.
  • this functionality of matching 120 a caller or called party to settings in a user profile for the caller or called party is performed by the MMTel Application Server.
  • the data handling unit will generate 130 a SIP Message comprising call log information referring to the call event and send 140 the generated SIP Message towards the storage server. This means that if call event information is received 1 10, it has already been
  • the information on at least one call event is received 1 10 from an MMTel Application Server.
  • the information on at least one call event is received 1 10 from a Mobile Switching Centre, MSC.
  • call event information for all users involved in the call event.
  • call event information for the users involved in the conference call, i.e. the call event...
  • the call log information is at least one of a time stamp, payload, originating party, destination party, history, Session
  • body of the SIP Message comprises information on the nature of the call event in plaintext.
  • the SIP Message comprises plaintext such as for example "Missed call”, “Received call - duration 1 :43”, "Missed call dd/mm/yy/time while phone off'.
  • the plaintext is the text which will be shown to a user when he/she accesses the stored call log information on the storage server.
  • a user's MMTel Application Server profile comprises information defining a plaintext language to be used.
  • the MMTel Application Server profile comprises, in this embodiment, information defining the language to be used with regards to the user.
  • the user may at some point in time have been given the option to indicate which language he/she prefers, for example English, and then the use of English is defined in the MMTel Application Server profile of the user.
  • the user profile, from which either the MMTel Application Server or the data handling unit determines whether call event information, is to be saved or not is in an example dynamic such that a user may at any time activate or de-activate the service of having call event information stored. In yet an example, this is performed via supplementary service codes, a Ut interface or a web Interface.
  • the Ut interface is defined in 3GPP TS 24.623 "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
  • a user may use a client, which may be an application on a phone, a web browser or the like, to access the storage server and retrieve call event
  • the call event information may be retrieved together with all incoming messages, voicemails etc. of the user.
  • the storage server supports in an example sorting functions such that the user may retrieve only voicemails, only messages from a certain caller and so on. In an example, the storage server delegates the sorting to the client of the user and simply returns all messages relating to the account of the user.
  • the client of the user uses, in an example, any supported protocol, e.g. Internet Message Access Protocol (IMAP), XML Configuration Access Protocol (XCAP) or Structured Query Language (SQL).
  • IMAP Internet Message Access Protocol
  • XCAP XML Configuration Access Protocol
  • SQL Structured Query Language
  • Embodiments herein also relate to a data handling unit in a Multimedia Telephony Service ,MMTel, network for handling information regarding calls.
  • MMTel Multimedia Telephony Service
  • the data handling unit has the same objects and advantages as the method therein. Consequently, the data handling unit will be described in brief to avoid unnecessary repetition.
  • the data handling unit 200 in a Multimedia Telephony Service, MMTel, network adapted for handling information regarding calls is configured to receive information on at least one call event, to generate a SIP Message comprising call log information referring to the call event, and to send the generated SIP Message towards a storage server 270.
  • the storage server 270 is enabled to store call log information regarding the call event.
  • the data handling unit 200 is further adapted to match a caller or called party to settings in a user profile for the caller or called party using the received information before generating the SIP Message.
  • the data handling unit is also adapted to generate the SIP Message comprising call log infornnation referring to the call event, only if settings in the user profile for the caller or called party indicate that call event infornnation is to be saved.
  • the information on at least one call event is received from an MMTel Application Server 260.
  • the information on at least one call event is received from a Mobile Switching Centre, MSC.
  • MSC Mobile Switching Centre
  • the call log information is at least one of a time stamp, payload, originating party, destination party, history, Session Description Protocol, SDP, and the like.
  • a body of the SIP Message comprises information on the nature of the call event in plaintext.
  • a user's MMTel Application Server profile comprises information defining a plaintext language to be used.
  • the data handling unit is comprised in an MMTel Application Server 260.
  • the data handling unit 200 is a part of the MMTel Application Server 260. This means that the data handling unit 200 is an
  • the data handling unit 200 is connected to an MMTel Application Server 260. See figure 2c.
  • Figure 2b is a block diagram of an exemplifying embodiment of an MMTel network.
  • the exemplifying embodiment illustrated in figure 2b shows the data handling unit 200 being incorporated within a MMTel Application Server 260.
  • the MMTel Application Server 260 also comprises a Call Service Logic Unit 265, which is configured to send, to the data handling unit 200, information on at least one call event. This corresponds to step 1 10 in figure 1 .
  • the data handling unit 200 sends a generated SIP Message towards a storage server 270.
  • Figure 2b further illustrates a user B accessing the storage server 270 by using an IMAP client 295 as has been described above. It shall be noted that other clients may be used by a user to access the storage server 270.
  • the Call Service Logic Unit 265 is configured to match a caller or called party to settings in a user profile for the caller or called party, and to send the information on at least one call event to the data handling unit 200, only if settings in a user profile for the caller or called party indicates that call event information is to be saved.
  • this functionality is implemented into the data handling unit 200 as has been described above with regards to step 120 in figure 1 .
  • Figure 2c is a block diagram of yet an exemplifying embodiment of an MMTel network.
  • FIG. 2c shows the data handling unit 200 being a separate unit connected to the MMTel Application Server 260.
  • the functionalities of the units in figure 2c are the same as in figure 2b.
  • Figure 2c also illustrates a Mobile Switching Centre, MSC, 300 being configured to send, to the data handling unit 200, information on at least one call event. This corresponds to step 1 10 in figure 1 .
  • Figure 2d is a schematic signalling diagram of an exemplifying
  • the data handling unit is incorporated into the MMTel Application Server 260 as illustrated in figure 2b.
  • the signalling diagram illustrates the storing of call event information regarding user B.
  • a user A makes use of his/her phone 290 to place a call of some kind to a phone 297 of user B. This is illustrated in figure 2d by the user A phone 290 sending a 2:1 SIP invite message to IMS 280.
  • the different procedures taking place in IMS 280 is not described in detail since they are known in the art. However, the different procedures result in determining that the user B phone 297 is not available.
  • the data handling unit within the MMTel Application Server 260 then generates a SIP Message comprising call log information referring to the call event, corresponding to step 130 of figure 1 , and sends 2:3 the SIP Message with information about a missed call from user A to the storage server 270.
  • IMS 280 informs user A that user B was not available by sending 2:6 a message to user A.
  • the user B may later use a device 295 comprising a client for accessing the storage server 270 to retrieve or fetch call log information. This is illustrated in figure 2d by the user B IMAP client 295 fetching 2:4 messages from the storage server 270 and receiving 2:5 information about the missed call from user A.
  • Figure 2e is a schematic signalling diagram of yet an exemplifying embodiment of a method in a data handling unit.
  • the data handling unit is a separate unit 200 connected to the MMTel Application Server 260 as illustrated in figure 2c.
  • the signalling illustrated in figure 2e differs from the signalling illustrated in figure 2d in that the MMTel Application Server 260 sends 2:2 an information message to the data handling unit 200, the information message comprising information about a missed call from user A. This is illustrated as a separate signalling step since the data handling unit 200 is a "standalone" unit which is connected to the MMTel Application Server 260. Then the data handling unit 200 generates and sends a SIP Message comprising call event information as having been described above.
  • figure 2a merely illustrates various functional units and modules in the data handling unit in a logical sense.
  • the functions in practice may be implemented using any suitable software and hardware means/circuits etc..
  • the embodiments are generally not limited to the shown structures of the data handling unit and the functional units and modules.
  • the previously described exemplary embodiments may be realised in many ways.
  • one embodiment includes a computer-readable medium having instructions stored thereon that are executable by the data handling unit, e.g. the processing unit 210 therein, for executing the method.
  • the instructions executable by the computing system and stored on the computer-readable medium perform the method steps of the present invention as set forth in the claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Multimedia (AREA)

Abstract

A data handling unit and a method therein for handling information regarding call events in a Multimedia Telephony Service, MMTel, network are provided for enabling call logging, wherein a SIP Message comprising call log information referring to a call event is generated for the call event and sent to a storage server. The method comprises receiving information on at least one call event, generating a SIP Message comprising call log information referring to the call event,and sending the generated SIP Message towards a storage server.

Description

MMTEL NETWORK CALL LOGGING
Technical field
[0001 ] Embodiments herein relate generally to logging of call events in a MMTel communication network, and in particular to logging of call events in a storage server.
Background
[0002] There is a demand for a call log in Multimedia Telephony Service (MMTel) communication networks which is accessible from user devices independent of the device used for communication, and which also comprise information about call activities when no device was registered in the network.
[0003] Some existing solutions are client centric, i.e. the mobile phone or IP Multimedia Subsystem (IMS) client is responsible for storing the data and then presenting a consolidated view to a user of the phone. Some existing solutions are network centric but not consolidated, for example Short Message Service (SMS), Multimedia Messaging Service (MMS), Session Initiation Protocol (SIP)
MESSAGE message are stored in one network log and call data is stored in a different network log. Hereinafter, when the term "SIP Message" is used, it is intended a SIP MESSAGE message, i.e. a SIP message called MESSAGE.
[0004] The client centric solutions have several drawbacks, for example, when a phone is not connected to the network because it is turned off or is out of range, call events that occur from other devices trying to reach the not connected phone will not be logged in the phone, e.g. missed calls. If multiple clients are connected to the same identity, e.g. phone number or SIP Uniform Resource Identifier (URI), mediation issues occur. For example, if a message is deleted on one device, the same message may still be present on other devices, communication initiated on one device is not visible at other devices and calls answered on one device may be registered as missed calls on other devices. Further, if the phone is lost, then the log information is also lost, and the log information may further potentially be read by an outside party. Summary
[0005] It is an object of the exemplifying embodiments to address at least some of the problems outlined above. In particular, it is an object of the exemplifying embodiments to provide a data handling unit and a method therein for handling information regarding call events in a Multimedia Telephony Service, MMTel, network for enabling call logging, wherein a SIP Message comprising call log information referring to a call event is generated for the call event and sent to a storage server. These objects and others may be obtained by providing a data handling unit and a method in a data handling unit according to the independent claims attached below.
[0006] According to an aspect a method in a data handling unit is provided for handling information regarding call events in a Multimedia Telephony Service, MMTel, network for enabling call logging. The method comprises receiving information on at least one call event, generating a SIP Message comprising call log information referring to the call event, and sending the generated SIP Message towards a storage server. In this way, the storage server is enabled to store call log information regarding the call event.
[0007] According to an aspect, a data handling in a Multimedia Telephony Service, MMTel, network adapted for handling information regarding calls is provided. The data handling unit is configured to receive information on at least one call event, to generate a SIP Message comprising call log information referring to the call event, and to send the generated SIP Message towards a storage server. In this way, the storage server is enabled to store call log information regarding the call event.
[0008] The data handling unit and the method therein have several advantages. By storing call log information for call events on the storage server, a user may access his/her call log information and obtain information regarding different call events, e.g. missed calls, the reason why they were missed, to which device or terminal the call was placed and so on. Further, call events which occur when a phone is not connected to a network will be logged. In case one telephone number is valid for multiple devices, the logging of call events regarding the telephone number will be logged. Hence, any deletion of local call information on a specific device will not incur deletion on the storage server so that the information is not lost. Still further, should a phone be lost, the call event log information is not lost. Yet an advantage is that the stored call information is easily accessible from the storage server at any later stage.
Brief description of drawings
[0009] Embodiments will now be described in more detail in relation to the accompanying drawings, in which:
[00010] Figure 1 is a flowchart of an exemplifying embodiment of a method in a data handling unit.
[0001 1 ] Figure 2a is a block diagram schematically illustrating an exemplifying embodiment of a data handling unit.
[00012] Figure 2b is a block diagram of an exemplifying embodiment of an MMTel network.
[00013] Figure 2c is a block diagram of yet an exemplifying embodiment of an MMTel network
[00014] Figure 2d is a schematic signalling diagram of an exemplifying embodiment of a method in a data handling unit.
[00015] Figure 2e is a schematic signalling diagram of yet an exemplifying embodiment of a method in a data handling unit.
Detailed description
[00016] Briefly described, exemplifying embodiments of a data handling unit and a method therein are provided for handling information regarding call events in a Multimedia Telephony Service, MMTel, network for enabling call logging. The logging of call events are performed in such a way that a SIP Message is generated for a call event and sent to a storage server. In this description, a call event is any of a missed call, a placed call, a received call, a diverted call, a barred call, and so on.
[00017] An exemplifying embodiment of such a method in a data handling unit for handling information regarding call events in a Multimedia Telephony Service, MMTel, network for enabling call logging will now be described with reference to the flowchart in figure 1 .
[00018] Figure 1 illustrates the method comprising receiving 1 10 information on at least one call event, generating 130 a SIP Message comprising call log information referring to the call event, and sending 140 the generated SIP
Message towards a storage server. In this way, the storage server is enabled to store call log information regarding the call event.
[00019] When a first user A makes use of a terminal, e.g. a phone, to place a call to a second user B, the actions taken by user A generates call event information, both with regards to user A and user B. In case the call is successful, for user A, the generated call information comprises e.g. successful placed call, call duration, identity of called user, and so on. For user B, in case the call is successful, the generated call information comprises e.g. successful received call, call duration, identity of calling user, and so on. In case the call is not successful, for user A, the generated call information comprises e.g. un-successful placed call, identity of called user and so on. For user B, in case the call is un-successful, the generated call information comprises e.g. missed call, missed call while busy on phone, missed call while out-of-coverage or missed call while phone turned off. Of course other call information may be generated and the examples above are merely examples. It shall be noted that the call information is generated with regards to a user identity, meaning that two separate pieces of call information are generated, one call information for user A and one call information for user B.
[00020] The generated call information is received 1 10 in the data handling unit. Then a SIP Message comprising call log information referring to the call event is generated 130 and sent 140 to a storage server. In this way, call log information is generated and then stored in the storage server. The stored call log information for a specific user may be accessed by the user, using one of his communication devices to obtain the call log information relating to him/her.
[00021 ] The generated call log information in this example for user A and B may be generated separately or together. In one example, the received call log information comprises call event information regarding both users. In another example, two separate call event information are received, one call event information for user A and one call event information for user B.
[00022] The exemplified embodiment has several advantages. By storing call log information for call events on the storage server, a user may access his/her call log information and obtain information regarding different call events, e.g. missed calls, the reason why they were missed, to which device or terminal the call was placed and so on. Further, call events which occur when a phone is not connected to a network will be logged. In case one telephone number is valid for multiple devices, the logging of call events regarding the telephone number will be logged. Hence, any deletion of local call information on a specific device will not incur deletion on the storage server so that the information is not lost. Still further, should a phone be lost, the call event log information is not lost. Yet an advantage is that the stored call information is easily accessible from the storage server at any later stage.
[00023] According to an embodiment, the method further comprises matching 120 a caller or called party to settings in a user profile for the caller or called party, using the received information before generating the SIP Message and generating the SIP Message comprising call log information referring to the call event, only if settings in the user profile for the caller or called party indicates that call event information is to be saved.
[00024] In this embodiment, the data handling unit receives 1 10 information on a call event comprising e.g. call event type and the identity of the user for who the call event is related. For example, if a user A tries to place a call to a user B and the call attempt is un-successful, then the received 1 10 call event information for user B may comprise e.g. missed call from user A while busy on phone. User B has a user profile which in an example is stored in an MMTel Application Server, and the user profile indicates whether or not call event information is to be saved. Alternatively, the user profile is stored in a Home Subscriber Server (HSS) and is then fetched by the MMTel Application Server when a call event is executed. If the user profile indicates that call event information is not to be saved, then the data handling unit may simply discard the received 1 10 information on at least one call event. On the other hand, if the user profile indicates that call event information is to be saved, the method comprises generating 130 a SIP Message comprising call log information referring to the call event, and sending 140 the generated SIP Message towards a storage server as described above.
[00025] In an alternative embodiment, this functionality of matching 120 a caller or called party to settings in a user profile for the caller or called party is performed by the MMTel Application Server. This means, that the data handling unit will generate 130 a SIP Message comprising call log information referring to the call event and send 140 the generated SIP Message towards the storage server. This means that if call event information is received 1 10, it has already been
ascertained, by the MMTel Application Server, that a SIP Message is to be generated and sent to the storage server. This is illustrated in figure 1 by the step 120 being in a dotted rectangle as this functionality may be implemented in the data handling unit by the method performed therein, or in e.g. the MMTel
Application Server.
[00026] According to yet an embodiment, the information on at least one call event is received 1 10 from an MMTel Application Server.
[00027] According to still an embodiment, the information on at least one call event is received 1 10 from a Mobile Switching Centre, MSC.
[00028] According to the two embodiments above, it is the entity (MMTel
Application Server or the MSC) which either receives the call attempt request from user A, i.e. originating side, and/or the entity (MMTel Application Server or the MSC) to which user B, i.e. terminating side, is connected or associated that generates call event information. In other words, there is always an MMTel AS or a MSC handling originating and terminating call events for each user involved in the call event, and this is normally the entity which generates the call event
information for all users involved in the call event. For some special services like conferencing there may be a specific AS taking care of this service and it would then also be able to generate call event information for the users involved in the conference call, i.e. the call event...
[00029] According to an embodiment, the call log information is at least one of a time stamp, payload, originating party, destination party, history, Session
Description Protocol, SDP, and the like.
[00030] According to still an embodiment, body of the SIP Message comprises information on the nature of the call event in plaintext.
[00031 ] This means that the SIP Message comprises plaintext such as for example "Missed call", "Received call - duration 1 :43", "Missed call dd/mm/yy/time while phone off'. The plaintext is the text which will be shown to a user when he/she accesses the stored call log information on the storage server.
[00032] According to an embodiment, a user's MMTel Application Server profile comprises information defining a plaintext language to be used.
[00033] The MMTel Application Server profile comprises, in this embodiment, information defining the language to be used with regards to the user. The user may at some point in time have been given the option to indicate which language he/she prefers, for example English, and then the use of English is defined in the MMTel Application Server profile of the user.
[00034] The user profile, from which either the MMTel Application Server or the data handling unit determines whether call event information, is to be saved or not is in an example dynamic such that a user may at any time activate or de-activate the service of having call event information stored. In yet an example, this is performed via supplementary service codes, a Ut interface or a web Interface. The Ut interface is defined in 3GPP TS 24.623 "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
[00035] A user may use a client, which may be an application on a phone, a web browser or the like, to access the storage server and retrieve call event
information. The call event information may be retrieved together with all incoming messages, voicemails etc. of the user. The storage server supports in an example sorting functions such that the user may retrieve only voicemails, only messages from a certain caller and so on. In an example, the storage server delegates the sorting to the client of the user and simply returns all messages relating to the account of the user. During the retrieval, the client of the user uses, in an example, any supported protocol, e.g. Internet Message Access Protocol (IMAP), XML Configuration Access Protocol (XCAP) or Structured Query Language (SQL).
[00036] Embodiments herein also relate to a data handling unit in a Multimedia Telephony Service ,MMTel, network for handling information regarding calls. Such a data handling unit will now be described with reference to the block diagram in figure 2a.
[00037] The data handling unit has the same objects and advantages as the method therein. Consequently, the data handling unit will be described in brief to avoid unnecessary repetition.
[00038] The data handling unit 200 in a Multimedia Telephony Service, MMTel, network adapted for handling information regarding calls is configured to receive information on at least one call event, to generate a SIP Message comprising call log information referring to the call event, and to send the generated SIP Message towards a storage server 270. In this way, the storage server 270 is enabled to store call log information regarding the call event.
[00039] According to an embodiment, the data handling unit 200 is further adapted to match a caller or called party to settings in a user profile for the caller or called party using the received information before generating the SIP Message. The data handling unit is also adapted to generate the SIP Message comprising call log infornnation referring to the call event, only if settings in the user profile for the caller or called party indicate that call event infornnation is to be saved.
[00040] According to still an embodiment, the information on at least one call event is received from an MMTel Application Server 260.
[00041 ] According to yet an embodiment, the information on at least one call event is received from a Mobile Switching Centre, MSC.
[00042] According to a further embodiment, the call log information is at least one of a time stamp, payload, originating party, destination party, history, Session Description Protocol, SDP, and the like.
[00043] According to still an embodiment, a body of the SIP Message comprises information on the nature of the call event in plaintext.
[00044] According to yet an embodiment, a user's MMTel Application Server profile comprises information defining a plaintext language to be used.
[00045] In a further embodiment, the data handling unit is comprised in an MMTel Application Server 260.
[00046] In this embodiment, the data handling unit 200 is a part of the MMTel Application Server 260. This means that the data handling unit 200 is an
integrated part of the MMTel Application Server 260. See figure 2b.
[00047] According to an embodiment, the data handling unit 200 is connected to an MMTel Application Server 260. See figure 2c.
[00048] Figure 2b is a block diagram of an exemplifying embodiment of an MMTel network.
[00049] The exemplifying embodiment illustrated in figure 2b, shows the data handling unit 200 being incorporated within a MMTel Application Server 260. The MMTel Application Server 260 also comprises a Call Service Logic Unit 265, which is configured to send, to the data handling unit 200, information on at least one call event. This corresponds to step 1 10 in figure 1 . Further illustrated in figure 2b is that the data handling unit 200 sends a generated SIP Message towards a storage server 270. This corresponds to step 140 in figure 1 . Figure 2b further illustrates a user B accessing the storage server 270 by using an IMAP client 295 as has been described above. It shall be noted that other clients may be used by a user to access the storage server 270. In an example of this illustrated embodiment, the Call Service Logic Unit 265 is configured to match a caller or called party to settings in a user profile for the caller or called party, and to send the information on at least one call event to the data handling unit 200, only if settings in a user profile for the caller or called party indicates that call event information is to be saved. In another example, this functionality is implemented into the data handling unit 200 as has been described above with regards to step 120 in figure 1 .
[00050] Figure 2c is a block diagram of yet an exemplifying embodiment of an MMTel network.
[00051 ] The exemplifying embodiment illustrated in figure 2c, shows the data handling unit 200 being a separate unit connected to the MMTel Application Server 260. The functionalities of the units in figure 2c are the same as in figure 2b. Figure 2c also illustrates a Mobile Switching Centre, MSC, 300 being configured to send, to the data handling unit 200, information on at least one call event. This corresponds to step 1 10 in figure 1 .
[00052] Figure 2d is a schematic signalling diagram of an exemplifying
embodiment of a method in a data handling unit. In this embodiment, the data handling unit is incorporated into the MMTel Application Server 260 as illustrated in figure 2b. The signalling diagram illustrates the storing of call event information regarding user B.
[00053] In figure 2d, a user A makes use of his/her phone 290 to place a call of some kind to a phone 297 of user B. This is illustrated in figure 2d by the user A phone 290 sending a 2:1 SIP invite message to IMS 280. The different procedures taking place in IMS 280 is not described in detail since they are known in the art. However, the different procedures result in determining that the user B phone 297 is not available. The data handling unit within the MMTel Application Server 260 then generates a SIP Message comprising call log information referring to the call event, corresponding to step 130 of figure 1 , and sends 2:3 the SIP Message with information about a missed call from user A to the storage server 270. Also IMS 280 informs user A that user B was not available by sending 2:6 a message to user A. The user B may later use a device 295 comprising a client for accessing the storage server 270 to retrieve or fetch call log information. This is illustrated in figure 2d by the user B IMAP client 295 fetching 2:4 messages from the storage server 270 and receiving 2:5 information about the missed call from user A.
[00054] Figure 2e is a schematic signalling diagram of yet an exemplifying embodiment of a method in a data handling unit. In this embodiment, the data handling unit is a separate unit 200 connected to the MMTel Application Server 260 as illustrated in figure 2c.
[00055] The signalling illustrated in figure 2e differs from the signalling illustrated in figure 2d in that the MMTel Application Server 260 sends 2:2 an information message to the data handling unit 200, the information message comprising information about a missed call from user A. This is illustrated as a separate signalling step since the data handling unit 200 is a "standalone" unit which is connected to the MMTel Application Server 260. Then the data handling unit 200 generates and sends a SIP Message comprising call event information as having been described above.
[00056] It should be noted that figure 2a merely illustrates various functional units and modules in the data handling unit in a logical sense. The functions in practice may be implemented using any suitable software and hardware means/circuits etc.. Thus, the embodiments are generally not limited to the shown structures of the data handling unit and the functional units and modules. Hence, the previously described exemplary embodiments may be realised in many ways. For example, one embodiment includes a computer-readable medium having instructions stored thereon that are executable by the data handling unit, e.g. the processing unit 210 therein, for executing the method. The instructions executable by the computing system and stored on the computer-readable medium perform the method steps of the present invention as set forth in the claims.
[00057] While the embodiments have been described in terms of several embodiments, it is contemplated that alternatives, modifications, permutations and equivalents thereof will become apparent upon reading of the specifications and study of the drawings. It is therefore intended that the following appended claims include such alternatives, modifications, permutations and equivalents as fall within the scope of the embodiments and defined by the pending claims.

Claims

1 . A method (100) in a data handling unit for handling information regarding call events in a Multimedia Telephony Service ,MMTel, network for enabling call logging, the method comprising:
- receiving (1 10) information on at least one call event,
- generating (130) a SIP Message comprising call log information referring to said call event, and
- sending (140) said generated SIP Message towards a storage server, thereby enabling said storage server to store call log information regarding said call event.
2. A method (100) according to claim 1 , further comprising matching (120) a caller or called party to settings in a user profile for said caller or called party, using said received information before generating said SIP Message and generating said SIP Message comprising call log information referring to said call event, only if settings in the user profile for said caller or called party indicates that call event information is to be saved.
3. A method (100) according to claim 1 or 2, wherein said information on at least one call event is received (1 10) from a MMTel Application Server.
4. A method (100) according to claim 1 or 2, wherein said information on at least one call event is received (1 10) from a Mobile Switching Centre, MSC.
5. A method (100) according to any of claims 1 -4, wherein call log information is at least one of a time stamp, payload, originating party, destination party, history, Session Description Protocol, SDP, and the like.
6. A method (100) according to any of claims 1 -5, wherein a body of said SIP Message comprises information on the nature of the call event in plaintext.
7. A method (100) according to claim 6, wherein a user's MMTel
Application Server profile comprises information defining a plaintext language to be used.
8. A data handling unit (200) in a Multimedia Telephony Service , MMTel, network for handling information regarding calls, the data handling unit being adapted to:
- receive information on at least one call event,
- generate a SIP Message comprising call log information referring to said call event, and to
- send said generated SIP Message towards a storage server,
thereby enabling said storage server to store call log information regarding said call event.
9. A data handling unit (200) according to claim 8, further being adapted to match a caller or called party to settings in a user profile for said caller or called party using said received information before generating said SIP Message, and adapted to generate said SIP Message comprising call log information referring to said call event, only if settings in the user profile for said caller or called party indicates that call event information is to be saved.
10. A data handling unit (200) according to claim 8 or 9, wherein said information on at least one call event is received from a MMTel Application Server.
1 1 . A data handling unit (200) according to claim 8 or 9, wherein said information on at least one call event is received from a Mobile Switching Centre, MSC.
12. A data handling unit (200) according to any of claim 8-1 1 , wherein call log information is at least one of a time stamp, payload, originating party, destination party, history, Session Description Protocol, SDP, and the like.
13. A data handling unit (200) according to any of claims 8-12, wherein a body of said SIP Message comprises information on the nature of the call event in plaintext.
14. A data handling unit (200) according to claim 13, wherein a user's MMTel Application Server profile comprises information defining a plaintext language to be used.
15. A data handling unit (200) according to any of claims 8-14, wherein said data handling unit (200) is comprised in a MMTel Application Server (260).
16. A data handling unit (200) according to any of claims 8-14, wherein said data handling unit (200) is connected to a MMTel Application Server (260).
17. A MMTel Application Server (260) comprising a data handling unit according to any of claims 8-14.
EP11726827.6A 2011-06-22 2011-06-22 Mmtel network call logging Not-in-force EP2724514B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2011/060499 WO2012175131A1 (en) 2011-06-22 2011-06-22 Mmtel network call logging

Publications (2)

Publication Number Publication Date
EP2724514A1 true EP2724514A1 (en) 2014-04-30
EP2724514B1 EP2724514B1 (en) 2020-08-05

Family

ID=44627375

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11726827.6A Not-in-force EP2724514B1 (en) 2011-06-22 2011-06-22 Mmtel network call logging

Country Status (3)

Country Link
US (1) US9509819B2 (en)
EP (1) EP2724514B1 (en)
WO (1) WO2012175131A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6161825B2 (en) * 2014-03-19 2017-07-12 エルジー エレクトロニクス インコーポレイティド Service request procedure execution method and user device
US10694040B1 (en) 2018-02-26 2020-06-23 Wells Fargo Bank, N.A. Centralized event log generation and analysis for contact centers
US10313511B1 (en) 2018-06-05 2019-06-04 Wells Fargo Bank, N.A. Customer self-help control system for contact centers
US11228676B1 (en) 2020-11-04 2022-01-18 The Fifth Lab Inc. System and method for providing telephone event data

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8965980B2 (en) * 2003-03-27 2015-02-24 Siebel Systems, Inc. Universal support for multiple external messaging systems
AU2003260819A1 (en) * 2003-09-12 2005-04-06 Nokia Corporation Method and device for handling missed calls in a mobile communications environment
US20060105766A1 (en) * 2004-10-26 2006-05-18 Azada Maria R Method for delivering a call to a dual-mode mobile unit using a single number
HRP20110446T1 (en) * 2005-08-04 2011-07-31 T-Mobile International Ag Method for collecting user behavior during run-time in a mobile 3gpp ip-based multimedia subsystem (ims)
US7873032B2 (en) * 2006-03-02 2011-01-18 Tango Networks, Inc. Call flow system and method use in VoIP telecommunication system
CN100596084C (en) * 2006-04-20 2010-03-24 华为技术有限公司 System for mobile circuit domain user to access IMS network and registration method for access
JP4829347B2 (en) * 2006-08-01 2011-12-07 テレフオンアクチーボラゲット エル エム エリクソン（パブル） Method and apparatus for collecting user activity in a communication system
CN101772155B (en) * 2009-01-05 2016-06-29 中兴通讯股份有限公司 The cancellation method of IP Multimedia System centralized traffic
EP2449755A1 (en) * 2009-06-30 2012-05-09 Markport Limited Anonymous party voice call processing

Also Published As

Publication number Publication date
WO2012175131A1 (en) 2012-12-27
EP2724514B1 (en) 2020-08-05
US20140105073A1 (en) 2014-04-17
US9509819B2 (en) 2016-11-29

Similar Documents

Publication Publication Date Title
US10484436B2 (en) User device selection
US9247418B2 (en) Communication-session termination when subscriber server is unavailable
US8867723B2 (en) Method of retrieving service information
CN103155606B (en) Dynamic call routing for real-time handling of inbound voice calls on mobile phones
US10348781B2 (en) Method and apparatus for enabling registration of aggregate end point devices through provisioning
EP2104305A1 (en) Call service handling in an IMS-based system
US20150117439A1 (en) Systems and methods for controlling telephony communications
US20100142695A1 (en) Methods, systems and crbt center for playing crbt and crt
US11165910B2 (en) Automated unavailability response for call handling
US8027445B2 (en) Method and system to provision emergency contact services in a communication network
EP2724514B1 (en) Mmtel network call logging
EP1914971B1 (en) System and method for providing multimedia contents in a communication system
US10212193B2 (en) Service support for suspended and inactive subscribers
US9426188B2 (en) Apparatus and method for conferencing
US20080159489A1 (en) System and method for providing an announcement indicating the status of a called party
CN104853047B (en) A kind of automatic back calling method and equipment
EP1879369A1 (en) Method and system of processing presence information in a communications system
US11082556B2 (en) System and method for determining spoofing of at least one identifier
WO2013079115A1 (en) Enhanced user options for rule-based services in ip multimedia subsystem
US20250159461A1 (en) Method and apparatus for processing duplicate call of dual sim user equipment
CN101060704B (en) An Emergency Registration Method for Internet Protocol Multimedia Subsystem Domain
WO2007104225A1 (en) A method, device and system for optimizing call back service in communication network
CN101291445A (en) Method, device and system for business data operation through session initiation protocol
Camarillo et al. Multimedia Telephony Services: PSTN/ISDN Simulation Services
US20140140246A1 (en) Monitoring of call forwarding destination

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

AK Designated contracting states

Kind code of ref document: A1

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

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170703

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 29/08 20060101AFI20200414BHEP

Ipc: H04W 24/08 20090101ALN20200414BHEP

Ipc: H04W 4/00 20180101ALI20200414BHEP

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

INTG Intention to grant announced

Effective date: 20200428

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

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM 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: 1300332

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200815

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011068061

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

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200805

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1300332

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200805

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

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

Ref country code: NO

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

Effective date: 20201105

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

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

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

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

Ref country code: HR

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

Effective date: 20200805

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

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

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

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

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

Ref country code: RS

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

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

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

Ref country code: SM

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011068061

Country of ref document: DE

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

Ref country code: AL

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

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

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

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

Ref country code: 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: 20200805

26N No opposition filed

Effective date: 20210507

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

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

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

Ref country code: SI

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

Effective date: 20200805

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

Ref country code: GB

Payment date: 20210628

Year of fee payment: 11

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602011068061

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029080000

Ipc: H04L0065000000

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602011068061

Country of ref document: DE

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210630

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

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

Ref country code: IE

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

Effective date: 20210622

Ref country code: DE

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

Effective date: 20220101

Ref country code: CH

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

Effective date: 20210630

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

Ref country code: FR

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

Effective date: 20210630

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

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

Effective date: 20220622

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

Ref country code: GB

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

Effective date: 20220622

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

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

Ref country code: MK

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

Effective date: 20200805

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

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

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