EP2652932B1 - Überwachung eines ziels mit mehreren identitäten bei legaler abhörung und datenspeicherung - Google Patents
Überwachung eines ziels mit mehreren identitäten bei legaler abhörung und datenspeicherung Download PDFInfo
- Publication number
- EP2652932B1 EP2652932B1 EP10805784.5A EP10805784A EP2652932B1 EP 2652932 B1 EP2652932 B1 EP 2652932B1 EP 10805784 A EP10805784 A EP 10805784A EP 2652932 B1 EP2652932 B1 EP 2652932B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- identities
- list
- data
- telecommunication
- telecommunication identities
- 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
- 230000014759 maintenance of location Effects 0.000 title claims description 47
- 238000012544 monitoring process Methods 0.000 title claims description 13
- 238000004891 communication Methods 0.000 claims description 23
- 238000000034 method Methods 0.000 claims description 21
- 230000000717 retained effect Effects 0.000 claims description 8
- 238000007726 management method Methods 0.000 claims description 5
- 238000004519 manufacturing process Methods 0.000 claims description 2
- 238000001914 filtration Methods 0.000 claims 2
- 238000004971 IR microspectroscopy Methods 0.000 description 23
- 238000012060 immune response imaging Methods 0.000 description 23
- 238000011835 investigation Methods 0.000 description 15
- AILFSZXBRNLVHY-UHFFFAOYSA-N 2,5-Dimethyl-4-ethoxy-3(2H)-furanone Chemical compound CCOC1=C(C)OC(C)C1=O AILFSZXBRNLVHY-UHFFFAOYSA-N 0.000 description 14
- 108010076504 Protein Sorting Signals Proteins 0.000 description 10
- 238000010586 diagram Methods 0.000 description 10
- 230000004913 activation Effects 0.000 description 5
- 238000001994 activation Methods 0.000 description 5
- 230000000875 corresponding effect Effects 0.000 description 5
- 230000001404 mediated effect Effects 0.000 description 5
- 230000008520 organization Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 230000032258 transport Effects 0.000 description 3
- WKVZMKDXJFCMMD-UVWUDEKDSA-L (5ar,8ar,9r)-5-[[(2r,4ar,6r,7r,8r,8as)-7,8-dihydroxy-2-methyl-4,4a,6,7,8,8a-hexahydropyrano[3,2-d][1,3]dioxin-6-yl]oxy]-9-(4-hydroxy-3,5-dimethoxyphenyl)-5a,6,8a,9-tetrahydro-5h-[2]benzofuro[6,5-f][1,3]benzodioxol-8-one;azanide;n,3-bis(2-chloroethyl)-2-ox Chemical compound [NH2-].[NH2-].Cl[Pt+2]Cl.ClCCNP1(=O)OCCCN1CCCl.COC1=C(O)C(OC)=CC([C@@H]2C3=CC=4OCOC=4C=C3C(O[C@H]3[C@@H]([C@@H](O)[C@@H]4O[C@H](C)OC[C@H]4O3)O)[C@@H]3[C@@H]2C(OC3)=O)=C1 WKVZMKDXJFCMMD-UVWUDEKDSA-L 0.000 description 2
- 238000013480 data collection Methods 0.000 description 2
- 230000002708 enhancing effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 101001036256 Homo sapiens Little elongation complex subunit 1 Proteins 0.000 description 1
- 101001036258 Homo sapiens Little elongation complex subunit 2 Proteins 0.000 description 1
- 102100039423 Little elongation complex subunit 1 Human genes 0.000 description 1
- 102100039420 Little elongation complex subunit 2 Human genes 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/30—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information
- H04L63/306—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information intercepting packet switched data communications, e.g. Web, Internet or IMS communications
Definitions
- the present invention generally relates to systems, software, methods, nodes and more particularly to mechanisms and techniques, to provide Law Enforcement Agencies with monitoring or retention data related to multiple telecommunication identities owned by single or multiple operators.
- Lawful Interception is used for legally monitoring voice and data communications between parties of interest to LEA.
- Data Retention is used to store data generated from e.g. public telecommunication and the Internet, which might be requested by Law Enforcement authorities in the course of investigations concerning said suspected criminals.
- Law Enforcement authorities In governments around the world, various law enforcement agencies may have the right to authorize this interception/retention in their respective jurisdictions.
- FIG. 1 is part of the prior art and discloses an Intercept Mediation and Delivery Unit IMDU, also called Intercept Unit.
- the IMDU is a solution for monitoring of Interception Related Information IRI and Content of Communication CC for the same target.
- the different parts used for interception are disclosed in current Lawful Interception standards (see 3GPP TS 33.107 and 3GPP TS 33.108 - Release 8).
- a Law Enforcement Monitoring Facility LEMF is connected to three Mediation Functions MF, MF2 and MF3 respectively for ADMF, DF2, DF3 i.e. an Administration Function ADMF and two Delivery Functions DF2 and DF3.
- the Administration Function and the Delivery Functions are each one connected to the LEMF via standardized handover interfaces HI1-HI3, and connected via interfaces X1-X3 to an Intercepting Control Element ICE in a telecommunication system.
- the ADMF is used to hide from ICEs that there might be multiple activations by different Law Enforcement Agencies.
- Messages REQ sent from LEMF to ADMF via HI1 and from the ADMF to the network via the X1_1 interface comprise identities of a target that is to be monitored.
- the HI1 interface is thus used to set the interception orders in the operator network.
- the Delivery Function DF2 receives Intercept Related Information IRI from the network via the X2 interface.
- the Delivery Function DF3 receives Content of Communication CC, i.e. speech and data, on X3 from the ICE. Requests are also sent from the ADMF to the Mediation Function MF2 in the DF2 on an interface X1_2 and to the Mediation Function MF3 in the DF3 on an interface X1_3. The requests sent on X1_3 are used for activation of Content of Communication, and to specify detailed handling options for intercepted CC.
- DF3 is responsible for call control signalling and bearer transport for an intercepted product.
- Intercept Related Information IRI received by DF2 is triggered by Events that in Circuit Switching domain are either call related or non-call related. In Packet Switching domain the events are session related or session unrelated.
- the message sent from the ADMF to the DF contains the target identity, which can be, for instance, one of the following: the IMSI, MSISDN or IMEI codes commonly associated to a mobile phone subscription.
- the message sent from the ADMF to the DF contains the address for delivery of IRI (i.e. the LEMF address), which subset of information shall be delivered, a DF2 activation identity, which uniquely identifies the activation for DF2 and is used for further interrogation or deactivation, respectively.
- the message sent from the ADMF to the DF also contains the warrant reference number, if required by national option.
- Intercept Related Information IRI events are generated at various moments, particularly when a call is initiated or ended, or for all supplementary services during a call and also for information which is not associated to a call. That is, there are call-related IRI events and non call-related IRI events.
- the Intercepting Control Element ICE in the network sends the relevant data to the DF2 for them to be delivered to the LEMF.
- Lawful Interception Identifier LIID Lawful Interception Identifier
- Communication Identifier CID Identifier CID
- CC Link Identifier CCLID Law enforcement can provide an alphanumeric string, the Case Identity to identify a particular surveillance.
- a case identity may be assigned to a Monitored Object through a command.
- FIG. 2 belongs to the prior art and shows the Handover Interfaces between a Data Retention System DRS (see ETSI TS 102 656 V.1.2.1 and ETSI TS 102 657 V.1.7.1) at a Communication Service Provider CSP, and an Authorized Organization AO.
- the figure shows an Administrative Function AdmF used to handle and forward requests from/to the AO.
- a Data Collection Function DCF collects data from network elements NEs.
- Storage S is used to collect and retain all possible data collected by the data collection function.
- the generic Handover Interface adopts a two port structure such that administrative request/response information and Retained Data Information are logically separated.
- the Handover Interface port 1 HI-A transports various kinds of administrative, request and response information from/to the Authorized Organization AO, and more particularly from/to an Issuing Authority IA thereof, and the organization at the CSP which is responsible for Retained Data matters.
- the HI-A interface may be crossing borders between countries. This possibility is subject to corresponding national law and/or international agreements.
- the Handover Interface port 2 HI-B transports the retained data information from the CSP, to the Authorized Organization AO, and more specifically to a Receiving Authority RA thereof. The individual retained data parameters have to be sent to the Requesting Authority at least once (if available).
- the HI-B interface may be crossing borders between countries. This possibility is subject to corresponding national law and/or international agreements.
- An investigation about subjects suspected of criminal activities does not only involve the monitoring of calls and retrieval of data items related to communications of a single target identity, for example a single MSISDN, IMSI, IMEI, IP address, etc. used by the suspected subjects. It is in fact often needed to extend the investigation to multiple identities, for example because the subjects suspected of criminal activities use more than one handset or because the investigation has to consider also other people in relationship with the suspected and whose conversations with each other and with the suspected are also under investigation. This scenario is even more complicated in case the target identities are owned by different operators or providers.
- the above-mentioned problem and others are solved by the invention which provides a new functionality for Lawful Intercept and Data Retention that allows combining multiple warrants/queries into one request.
- the invention provides a new functionality for Lawful Intercept and Data Retention that allows combining multiple warrants/queries into one request.
- an enhancement of the handover interfaces HI1/HI-A of Lawful Interception LI and Data Retention DR respectively, which allow to trigger a single warrant with multiple targets included in lists for Lawful Intercept, and performing multiple queries towards those lists in Data Retention, allowing LEA investigators to save time and effort.
- a number of telecommunication identities of one or more target users are grouped in at least one list of telecommunication identities which is identified by a corresponding identification element, or list identifier.
- This list identifier can be used as a correlation item in a further enhancement of handover interfaces HI2/HI-B of LI and DR, respectively. This can be useful for example to correlate data related to the same investigation.
- the information data retrieved from a telecommunications network which relate to the number of identities included in the list of target identities are tagged with a corresponding list identifier before they are delivered to the Authorities requesting the information data.
- the single warrant/query is repartitioned into a plurality of requests each directed to each of the network operators managing one or more of said identities.
- a Lawful Interception embodiment is disclosed.
- the invention works within the framework of a Data Retention application.
- Figure 3 discloses a signal sequence diagram representing an example of use of the invention in a Lawful Intercept environment where a list of identities is owned by a single operator.
- An enhancement of the handover interface HI1 of the Intercept Unit (see Figure 1 ) previously discussed is proposed, which allows to trigger a single warrant with multiple identities, belonging to one or more target users included in one or more lists.
- These lists can be any one of e.g. blacklists (i.e. lists containing identities belonging to known criminals), whitelists (i.e. lists of identities which are clearly not belonging to suspected subjects), and greylists (i.e. lists of identities belonging to suspected subjects).
- These lists are identified by a list identifier List_id which is also used as a correlation item, thus enhancing the interface HI2 of the Intercept Unit.
- the multiple identities of one or more subjects suspected of e.g. illegal, criminal or terrorist activities, whose traffic needs to be intercepted are all owned by a single operator.
- a LEA is interested in two investigations, the first one involving target identities x and y, and the other involving the target identities x' and y', plus the additional identity z.
- the Law Enforcement Management Function LEMF identifies for example two e.g. IMEI lists of handsets, list L containing identities x and y, and list K containing identities x', y' and z, and passes a request for Lawful Intercept "Request LI" to the Administration Function ADMF of the LI. Then, the Lawful Interception is activated in phase "Activate LI" by providing a single warrant for each list L, K in an Intercepting Control Element ICE (e.g., Gateway GPRS Support Node GGSN, Mobile Switching Centre MSC, etc.) by fetching an e.g. IMEI list of targets, linked to a respective list identifier List_id L and List_id K.
- Intercepting Control Element ICE e.g., Gateway GPRS Support Node GGSN, Mobile Switching Centre MSC, etc.
- the ICE intercepts and filters ("IMEI x", "IMEI y") and ("IMEI x'", “IMEI y'", “IMEI z"), and generally speaking "IMEI m” and "IMEI n" belonging to a generic list List_id, only relevant traffic coming from or going to the identities, listed in the lists identified by List_id L and List_id K (and generally speaking, any list identified by a List_id).
- the ICE forwards raw IRIs ("IRI x", “IRI y"), ("IRI x'", “IRI y'", “IRI z"), and generally speaking "IRI n", and optionally CC (in general, "CC m") to the Lawful Interception mediation system LEMF, when traffic data related to any of the IMEI in the target lists reaches the ICE. Data relate to the originator or recipient identities under monitoring.
- IMEIx is in communication with IMEIy, in a specified time window and they are in the same list, the intercepted communication will be reported only once on the Handover Interface.
- Lawful Interception Mediation System converts the intercepted traffic into the required standard format and sends it to a collection function running at the LEMFs.
- Figure 4 discloses a signal sequence diagram representing another example of use of the invention in a Lawful Intercept environment, where a list of identities is owned by multiple operators.
- the exemplary scenario is similar to the one discussed above, and relates to an enhancement of the handover interface HI1 of the Intercept Unit (see Figure 1 ) previously discussed which allows to trigger a single warrant with multiple targets included in one or more lists.
- These lists can be any one of e.g. blacklists, whitelists and greylists.
- These lists are identified by a list identifier List_id which is also used as a correlation item, thus enhancing the interface HI2 of the Intercept Unit.
- the multiple identities of one or more subjects suspected of e.g. illegal, criminal or terrorist activities, whose traffic needs to be intercepted are owned by different operators, for example a first operator Op1 and a second operator Op2.
- a LEA is interested in two investigations, the first one involving target identities x and y, and the other involving target identities z and w.
- Target identities x and w are for example owned by the first operator Op1, while target identities y and z are for example owned by the second operator Op2.
- the Law Enforcement Management Function LEMF identifies for example two e.g. IMEI lists of handsets, list L containing identities x and y, and list K containing identities z and w, which are not owned by a single operator.
- the LEMF passes a request for Lawful Intercept "Request” to the Administration Function ADMF of the LI.
- the lists are transferred from ADMF to a Multi-Operator Mediation Function "Multi-Op MF" (see "Activate Multi-Op LI").
- the triggered warrant shall use a special operator identifier associated to the Multi-Op MF.
- the Lawful Interception mediation system using the embedded Multi-Operator Mediation Function, provisions multiple warrants repartitioned among several ICEs, (ICE1, ICE2 in the example) each one owned by a specific operator, by fetching an e.g. IMEI list of targets, linked to a respective list identifier List_id L and List_id K.
- ICE1, ICE2 in the example
- each ICE intercepts and filters only relevant traffic coming from or going to the identities, listed in the lists identified by List_id L and List_id K (in the example ICE 1: “IMEI x" for List_id L and “IMEI w" for List_id K; ICE 2: “IMEI y” for List_id L and “IMEI z” for List_id K).
- the ICE forwards raw IRIs ("IRI x", “IRI y”, “IRI z", “IRI w"), and optionally CCs (not shown in figure 4 ) to the Lawful Interception mediation system LEMF, when traffic data related to any of the IMEI in the target lists reaches the ICE. Data relate to the originator or recipient identities under monitoring.
- IMEIx is in communication with IMEIy, in a specified time window and they are in the same list eg. identified by List_id L, the intercepted communication will be reported only once on the Handover Interface.
- Lawful Interception Mediation System converts the intercepted traffic into the required standard format and sends it to a collection function running at the LEMFs, further correlating the provided data by Operator Identifier.
- FIG. 5 shows a signal sequence diagram representing an example of Data Retention in a simplified environment involving only one operator.
- Data e.g traffic data records which includes end users identities such as IP addresses, coming from a Source (e.g. a MultiService Proxy, a Mobile Switching Centre MSC, a Multimedia Messaging Centre MMC, a Radius server, an Email server, a NAT server, etc.), are transferred to the Data Retention system DR Mediation Function/Delivery Function (MF/DF) at a predetermined time interval.
- the data records can contain IP addresses of the users, or IMSI, MSISDN, or any other specific identity indicator.
- the data are mediated and further transferred (“Mediated Data") from the Data Retention MF/DF and stored in a Data Retention system storage which can be e.g. a database.
- a LEA may submit a request to query the Data Retention system storage in order to retrieve traffic data information in a certain time window, about various identities, for example IP addresses, which can be grouped in lists. Each list is identified by a List_id, for example List_id L and List_id K.
- the request from LEA is received by the Data Retention Administrative Function ADMF through HI-A and it is passed on to the Data Retention MF/DF.
- the Data Retention storage is queried, and then the results are returned to the MF/DF.
- the MF/DF then delivers the results of the query to LEA, through HI-B.
- the delivered data includes traffic data information related to the identities, e.g. IP addresses, each one of them belonging to the respective list identified by e.g. List_id L and List_id K.
- FIG. 7 shows a signal sequence diagram representing an example of Data Retention in a more complex environment involving several operators. For reasons of clarity, only two operators are shown in Figure 7 , but naturally the same concepts apply and can be extended to cover the case of more than two operators.
- Data e.g traffic data records which includes end users identities coming from multiple sources ("Source 1", "Source 2"), are transferred to the Data Retention system DR Mediation Function/Delivery Function (MF/DF) at a predetermined time interval.
- MF/DF Data Retention system DR Mediation Function/Delivery Function
- the data records can contain IP addresses of the users, or IMSI, MSISDN, or any other specific identity indicator.
- Event Data Records provided from a specific operator are identified by an operator ID, for example a Communication Service Provider CSP ID, which can be agreed upon on a national basis and is unique for each operator within the same country. Then, the data from each operator (“Data 1", “Data 2”) are mediated and further transferred (“Mediated Data 1", “Mediated Data 2”) from the Data Retention MF/DF and stored in a Data Retention system storage which can be e.g. a database.
- CSP ID Communication Service Provider
- a LEA may submit a request to query the Data Retention system storage in order to retrieve traffic data information or multimedia messaging data information or any other specific information stored in the DR storage system in a certain time window, about various identities, for example IP addresses or IMSIs, which can be grouped in lists. Each list is identified by a List_id, for example List_id L and List_id K. The identities in the lists are associated to a respective CSP ID which identifies the corresponding operator.
- the request from LEA is received by the Data Retention Administrative Function ADMF through HI-A and it is passed on to a Multi-Operator Mediation Function, which is in charge to associate each identity, for example IP address or IMSI, to the specific CSP ID used for each operator, expanding the single request from LEA into several requests ("Multi Req.”), which are then sent to the Data Retention MF/DF.
- Multi Req. the Data Retention storage
- the results are returned to the MF/DF.
- the MF/DF then delivers the results of the query to LEA, through HI-B.
- the delivered data includes traffic data information related to the identities, e.g. IMSIs or IP addresses, each one of them belonging to the respective list identified by e.g. List_id L and List_id K, and preferably grouped by CSP IDs.
- the list identifier List-id can be used as a correlation item for the provided traffic query results.
- the method and systems which have been described above have several advantages, especially for the LEAs.
- the investigators can save a significant amount of time and efforts.
- the list identifiers - and more generally the process which has been described - gives the Lawful Enforcement Agencies the possibility to get correlated data, providing a more complete and manageable overview of data related to monitored targets for investigation purposes.
- the LEA can perform multi-target warrants/multiple list queries using subscribers' identities event when they are not owned by a single operator, therefore helping investigators to save time and effort.
Landscapes
- Engineering & Computer Science (AREA)
- Technology Law (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Claims (18)
- Verfahren zum Bereitstellen von Überwachungsdaten oder Daten aus Vorratsdatenspeicherung, die sich auf mehrere Telekommunikationsidentitäten im Telekommunikationsnetz beziehen, an Vollzugsbehörden in einem Telekommunikationsnetz, umfassend den Schritt des Gruppierens einer Anzahl der Telekommunikationsidentitäten in wenigstens einer Liste aus Telekommunikationsidentitäten, die durch wenigstens ein entsprechendes Listenidentifizierungselement identifiziert wird, umfassend den Schritt des Abrufens von überwachten Informationsdaten aus dem Telekommunikationsnetz mit Bezug auf die Anzahl von Telekommunikationsidentitäten in der wenigstens einen Liste aus Telekommunikationsidentitäten, den Schritt des Markierens der abgerufenen überwachten Informationsdaten mit einem entsprechenden Listenidentifizierungselement, und Liefern der mit dem entsprechenden Listenidentifizierungselement markierten abgerufenen überwachten Informationsdaten.
- Verfahren nach Anspruch 1, umfassend den Schritt des Einholens einer einzelnen Ermächtigung oder Anforderung von einer Vollzugsbehörde, um das Überwachen der mehreren Telekommunikationsidentitäten einzuleiten.
- Verfahren nach Anspruch 1, wobei der Schritt des Abrufens überwachter Informationsdaten das Abrufen von abfangbezogenen Informationen und von Kommunikationsinhalt in einem gesetzeskonformen Abfangsystem umfasst.
- Verfahren nach Anspruch 1, wobei der Schritt des Abrufens von überwachten Informationsdaten das Abrufen von bevorrateten Daten in einem Vorratsdatenspeicherungssystem umfasst.
- Verfahren nach einem der Ansprüche 1 bis 4, die folgenden Schritte umfassend:- Definieren einer oder mehrerer Listen aus Telekommunikationsidentitäten,- Zuordnen eines eindeutigen Listenidentifikators für jede der einen oder mehreren Listen von Telekommunikationsidentitäten,- Weiterleiten einer Anforderung für ein gesetzeskonformes Abfangen an eine Administrationsfunktion (ADMF) eines gesetzeskonformen Abfangsystems,- Bereitstellen einer Ermächtigung für ein Abfang-Steuerungselement eines einzelnen Betreibers durch Abrufen einer oder mehrerer Listen von Zielidentitäten,- Abfangen und Filtern von relevantem Datenverkehr von den und an die Identitäten in den Listen,- Weiterleiten von unverarbeiteten abfangsbezogenen Informationen an das Vermittlungssystem für gesetzeskonformes Abfangen, wenn Datenverkehrsdaten an eine der Identitäten in den Ziellisten das Abfangsteuerelement erreichen,- Liefern der Ergebnisse der Anforderung an die Vollzugsbehörden-Verwaltungsfunktion (LEMF), durch das Vermittlungssystem für gesetzeskonformes Abfangen über die Übergabeschnittstelle.
- Verfahren nach einem der Ansprüche 1 bis 4, die folgenden Schritte umfassend:- Definieren einer oder mehrerer Listen aus Telekommunikationsidentitäten,- Zuordnen eines eindeutigen Listenidentifikators für jede der einen oder mehreren Listen von Telekommunikationsidentitäten,- Weiterleiten einer Anforderung zum Abfragen eines Speichers eines Vorratsdatenspeicherungssystems an eine Administrationsfunktion (ADMF) eines Vorratsdatenspeicherungssystems,- Senden der Anforderung an die Vorratsdatenspeicher-Vermittlungs-/-Lieferfunktion (MF/DF),- Abfragen des Vorratsdatenspeichers, Erhalten wenigstens eines Satzes von Ergebnissen,- Zurücksenden der Ergebnisse an die Vermittlungs-/Lieferfunktion,- Liefern der Ergebnisse der Anfrage an die Vollzugsbehörde über die Übergabeschnittstelle HI-B.
- Verfahren nach einem der Ansprüche 1 bis 6, wobei die Telekommunikationsidentitäten von mehreren Netzbetreibern verwaltet werden, umfassend den Schritt des Aufteilens der einen Anforderung in mehrere Anforderungen, die jeweils an jeden der Netzbetreiber gerichtet sind, die eine oder mehrere der Telekommunikationsidentitäten verwalten.
- Verfahren nach Anspruch 7, die folgenden Schritte umfassend:- Definieren einer oder mehrerer Listen aus Telekommunikationsidentitäten,- Zuordnen eines eindeutigen Listenidentifikators für jede der einen oder mehreren Listen von Telekommunikationsidentitäten,- Weiterleiten einer Anforderung für ein gesetzeskonformes Abfangen an eine Administrationsfunktion (ADMF) eines gesetzeskonformen Abfangsystems,- Transferieren der einen oder mehreren Listen von der Administrationsfunktion (ADMF) an eine Mehrbetreiber-Vermittlungsfunktion,- Bereitstellen mehrerer Ermächtigungen, die zwischen mehreren Abfang-Steuerungselementen aufgeteilt worden sind, die jeweils zu einem spezifischen Betreiber gehören, durch Abrufen einer oder mehrerer Listen von Zielidentitäten,- Abfangen und Filtern von relevantem Datenverkehr von den und an die Identitäten in den Listen,- Weiterleiten von unverarbeiteten abfangsbezogenen Informationen an das Vermittlungssystem für gesetzeskonformes Abfangen, wenn Datenverkehrsdaten bezogen auf eine der Identitäten in den Ziellisten die Abfangsteuerelemente erreichen,- Liefern der Ergebnisse der Anforderung an die Vollzugsbehörden-Verwaltungsfunktion (LEMF) durch das Vermittlungssystem für gesetzeskonformes Abfangen über die Übergabeschnittstelle.
- Verfahren nach einem der Ansprüche 1 bis 6, wobei die Telekommunikationsidentitäten von mehreren Kommunikationsdienstleistern verwaltet werden, umfassend den Schritt des Aufteilens der einen Anforderung in mehrere Anforderungen, von denen jede sich auf Vorratsdaten bezieht, die für jeden Kommunikationsdienstleister spezifisch sind, der eine oder mehrere der Telekommunikationsidentitäten verwaltet.
- Verfahren nach Anspruch 9, die folgenden Schritte umfassend:- Definieren einer oder mehrerer Listen aus Telekommunikationsidentitäten,- Zuordnen eines eindeutigen Listenidentifikators für jede der einen oder mehreren Listen von Telekommunikationsidentitäten,- Weiterleiten einer Anforderung zum Abfragen eines Speichers eines Vorratsdatenspeicherungssystems an eine Administrationsfunktion (ADMF) eines Vorratsdatenspeicherungssystems,- Weiterleiten der Anforderung an eine Mehrbetreiber-Vermittlungsfunktion, die jede Identität mit einem Betreiberidentifikator verbindet,- Erweitern der Anforderung von der Vollzugsbehörde in mehrere Anforderungen,- Senden der mehreren Anforderungen an die Vorratsdatenspeicher-Vermittlungs-/-Lieferfunktion (MF/DF),- Abfragen des Vorratsdatenspeichers, Erhalten wenigstens eines Satzes von Ergebnissen,- Zurücksenden der Ergebnisse an die Vermittlungs-/Lieferfunktion,- Liefern der Ergebnisse der Anfrage an die Vollzugsbehörde über die Übergabeschnittstelle HI-B.
- Verfahren nach Anspruch 8 oder 10, wobei die möglichen Duplikate ausgefiltert werden, bevor die Daten an die Übergabeschnittstelle bereitgestellt werden.
- System zum Überwachen oder Vorratsspeichern von Daten, die sich auf mehrere Telekommunikationsidentitäten in einem Telekommunikationsnetz beziehen, wobei das System Markierungsmittel zum Markieren von überwachten Informationen oder vorratsgespeicherten Daten mit einem Listenidentifizierungselement umfasst, welches eine Liste aus diesen Telekommunikationsidentitäten identifiziert, ferner umfassend Mittel zum Abrufen von überwachten Informationsdaten von einem Telekommunikationsnetz, die sich auf die Anzahl von Telekommunikationsidentitäten in der Liste aus Telekommunikationsidentitäten beziehen, und Mittel zum Liefern der mit dem entsprechenden Listenidentifizierungselement markierten, überwachten Informationsdaten.
- System nach Anspruch 12, wobei es sich um ein gesetzeskonformes Abfangsystem handelt, das ferner eine Mehrbetreiber-Vermittlungsfunktion umfasst, um eine einzelne Ermächtigung in mehrere Ermächtigungen aufzuteilen, von denen jede an einen entsprechenden Netzbetreiber gerichtet ist, der eine oder mehrere der Telekommunikationsidentitäten verwaltet.
- System nach Anspruch 12, wobei es sich um ein Vorratsdatenspeicherungssystem handelt, das ferner eine Mehrbetreiber-Vermittlungsfunktion umfasst, um eine einzelne Anforderung in mehrere Anforderungen aufzuteilen, von denen jede sich auf Vorratsdaten bezieht, die für jeden Kommunikationsdienstleister spezifisch sind, der eine oder mehrere der Telekommunikationsidentitäten verwaltet.
- Telekommunikationsnetz mit einem System nach einem der Ansprüche 12 bis 14.
- Knoten zum Einsatz in einem gesetzeskonformen Abfangsystem zum Bereitstellen von Überwachung mehrerer Telekommunikationsidentitäten in einem Telekommunikationsnetz an Vollzugsbehörden, umfassend einen oder mehrere Kreise zum Gruppieren einer Anzahl der Telekommunikationsidentitäten in wenigstens einer Liste aus Telekommunikationsidentitäten, welche durch wenigstens ein entsprechendes Listenidentifikationselement identifiziert ist, ferner umfassend Mittel zum Abrufen von überwachten Informationsdaten von einem Telekommunikationsnetz, die sich auf die Anzahl von Telekommunikationsidentitäten in der Liste aus Telekommunikationsidentitäten beziehen, und Mittel zum Liefern der mit dem entsprechenden Listenidentifizierungselement markierten, abgerufenen überwachten Informationsdaten.
- Knoten zum Einsatz in einem Vorratsdatenspeicherungssystem zum Bereitstellen von Daten aus Vorratsdatenspeicherung mit Bezug auf mehrere Telekommunikationsidentitäten in einem Telekommunikationsnetz an Vollzugsbehörden, umfassend einen oder mehrere Kreise zum Gruppieren einer Anzahl der Telekommunikationsidentitäten in wenigstens einer Liste aus Telekommunikationsidentitäten, welche durch wenigstens ein entsprechendes Listenidentifikationselement identifiziert ist, ferner umfassend Mittel zum Abrufen von überwachten Informationsdaten von einem Telekommunikationsnetz, die sich auf die Anzahl von Telekommunikationsidentitäten in der Liste aus Telekommunikationsidentitäten beziehen, und Mittel zum Liefern der mit dem entsprechenden Listenidentifizierungselement markierten, abgerufenen überwachten Informationsdaten
- Produktionsartikel, umfassend einen Programmspeicher mit computerlesbarem Code zum Bereitstellen von Überwachung oder Daten aus Vorratsdatenspeicherung mit Bezug auf mehrere Telekommunikationsidentitäten mit einer oder mehreren Telekommunikationsidentitäten im Telekommunikationsnetz an Vollzugsbehörden in einem Telekommunikationsnetz, wobei der Programmcode computerlesbaren Programmcode umfasst, der in der Lage ist, eine Anzahl der Telekommunikationsidentitäten in wenigstens einer Liste aus Telekommunikationsidentitäten, welche durch wenigstens ein entsprechendes Listenidentifikationselement identifiziert ist, zu gruppieren, der ebenfalls in der Lage ist, von einem Telekommunikationsnetz überwachte Informationsdaten, die sich auf die Anzahl von Telekommunikationsidentitäten in der wenigstens einen Liste aus Telekommunikationsidentitäten beziehen, abzurufen, die abgerufenen überwachten Informationsdaten mit einem entsprechenden Listenidentifizierungselement zu markieren und die mit dem entsprechenden Listenidentifizierungselement markierten, abgerufenen Informationsdaten zu liefern.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2010/070162 WO2012079653A1 (en) | 2010-12-17 | 2010-12-17 | Monitoring target having multiple identities in lawful interception and data retention |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2652932A1 EP2652932A1 (de) | 2013-10-23 |
EP2652932B1 true EP2652932B1 (de) | 2015-07-29 |
Family
ID=44583537
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP10805784.5A Active EP2652932B1 (de) | 2010-12-17 | 2010-12-17 | Überwachung eines ziels mit mehreren identitäten bei legaler abhörung und datenspeicherung |
Country Status (3)
Country | Link |
---|---|
US (1) | US20130282878A1 (de) |
EP (1) | EP2652932B1 (de) |
WO (1) | WO2012079653A1 (de) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012106528A2 (en) * | 2011-02-02 | 2012-08-09 | Cellcrypt Group Limited | A method of providing lawful interception of data in a secure communication system |
EP3949305A1 (de) | 2019-03-25 | 2022-02-09 | Telefonaktiebolaget LM ERICSSON (PUBL) | Rechtmässiges abhören in einer mobilen verbindung |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE59803795D1 (de) * | 1997-02-13 | 2002-05-16 | Siemens Ag | Verfahren zur steuerung der gesetzmässigen überwachung des fernmeldeverkehrs |
US6577865B2 (en) * | 1998-11-05 | 2003-06-10 | Ulysses Holdings, Llc | System for intercept of wireless communications |
US8428056B2 (en) * | 2000-12-22 | 2013-04-23 | Avaya, Inc. | Generation of redundant scheduled network paths using a branch and merge technique |
US8131744B2 (en) * | 2004-12-17 | 2012-03-06 | International Business Machines Corporation | Well organized query result sets |
US20090234845A1 (en) * | 2006-02-22 | 2009-09-17 | Desantis Raffaele | Lawful access; stored data handover enhanced architecture |
US20100199189A1 (en) * | 2006-03-12 | 2010-08-05 | Nice Systems, Ltd. | Apparatus and method for target oriented law enforcement interception and analysis |
US7978620B2 (en) * | 2007-05-14 | 2011-07-12 | Cisco Technology, Inc. | Dynamically troubleshooting voice quality |
US8819080B2 (en) * | 2007-06-13 | 2014-08-26 | The Boeing Company | System and method for collection, retrieval, and distribution of data |
EP2266301B1 (de) * | 2008-04-04 | 2018-06-13 | Telefonaktiebolaget LM Ericsson (publ) | Aktivitätsmeldung für abfangzwecke |
EP2345222B1 (de) * | 2008-10-10 | 2016-08-24 | Telefonaktiebolaget LM Ericsson (publ) | Vollmachtverwaltung rechtlicher autoritäten |
US8806358B2 (en) * | 2009-03-27 | 2014-08-12 | Bank Of America Corporation | Positive identification and bulk addition of custodians to a case within an electronic discovery system |
US8498998B2 (en) * | 2010-10-11 | 2013-07-30 | International Business Machines Corporation | Grouping identity records to generate candidate lists to use in an entity and relationship resolution process |
-
2010
- 2010-12-17 US US13/993,234 patent/US20130282878A1/en not_active Abandoned
- 2010-12-17 EP EP10805784.5A patent/EP2652932B1/de active Active
- 2010-12-17 WO PCT/EP2010/070162 patent/WO2012079653A1/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
EP2652932A1 (de) | 2013-10-23 |
US20130282878A1 (en) | 2013-10-24 |
WO2012079653A1 (en) | 2012-06-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8478227B2 (en) | System and method for lawful interception of user information | |
EP2491705B1 (de) | Li-meldung für aktualisierte standortinformationen für eps | |
US9253273B2 (en) | User data automatic lookup in lawful interception | |
RU2479933C2 (ru) | Один отчет об активности для целей перехвата | |
US20230007052A1 (en) | Managing lawful interception information | |
EP2191636A1 (de) | Überwachung von instant-messaging- und präsenzdiensten | |
US8606190B2 (en) | User and traffic data retention in lawful interception | |
CN102037756B (zh) | 在号码可移植性的情况下的li/dr服务连续性 | |
US20110055910A1 (en) | User-centric interception | |
EP2792182B1 (de) | Klassifizierung von abgefangener internetnutzlast | |
EP2505006B1 (de) | Methode und system zur automatischen identifizierung von unbeknannten identitäten | |
EP2652932B1 (de) | Überwachung eines ziels mit mehreren identitäten bei legaler abhörung und datenspeicherung | |
EP2671359B1 (de) | Verfahren zur überwachung bösartiger angriffe | |
EP2371116B1 (de) | Rechtmässige identifikation unbekannter endgeräte | |
EP2272245A1 (de) | Verwendung von eindeutigen verweisen zur ermöglichung einer korrelation von datenretentions- oder rechtmässigen abfangdatensätzen | |
US20120016988A1 (en) | Supervision of li and dr query activities |
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: 20130702 |
|
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) | ||
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTG | Intention to grant announced |
Effective date: 20150416 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: TELEFONAKTIEBOLAGET L M ERICSSON (PUBL) |
|
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: 740029 Country of ref document: AT Kind code of ref document: T Effective date: 20150815 |
|
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: T3 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602010026316 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 740029 Country of ref document: AT Kind code of ref document: T Effective date: 20150729 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
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: 20150729 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: 20151030 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: 20150729 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: 20150729 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: 20151029 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20151129 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: 20150729 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: 20150729 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: 20151130 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: 20150729 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: 20150729 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: 20150729 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: 20150729 |
|
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: 20150729 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: 20150729 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: 20150729 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: 20150729 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: 20150729 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602010026316 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20150729 Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20151231 |
|
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: DE Ref legal event code: R119 Ref document number: 602010026316 Country of ref document: DE |
|
26N | No opposition filed |
Effective date: 20160502 |
|
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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20151217 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: 20150729 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: 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: 20150729 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20160831 |
|
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: 20151231 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20151217 Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160701 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20151231 |
|
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: 20151231 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20150729 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20150729 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: 20150729 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: 20101217 |
|
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: 20150729 |
|
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: 20150729 |
|
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: 20150729 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: 20150729 |
|
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: 20150729 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20231227 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20231226 Year of fee payment: 14 |