EP2732403A1 - Traitement de données générées par un dispositif - Google Patents

Traitement de données générées par un dispositif

Info

Publication number
EP2732403A1
EP2732403A1 EP11735638.6A EP11735638A EP2732403A1 EP 2732403 A1 EP2732403 A1 EP 2732403A1 EP 11735638 A EP11735638 A EP 11735638A EP 2732403 A1 EP2732403 A1 EP 2732403A1
Authority
EP
European Patent Office
Prior art keywords
generated data
request
server
identifier
device identifier
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.)
Ceased
Application number
EP11735638.6A
Other languages
German (de)
English (en)
Inventor
Robert Skog
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 EP2732403A1 publication Critical patent/EP2732403A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring

Definitions

  • the present application relates to a method of caching device generated data, a server arranged to cache device generated data, and a computer-readable medium.
  • Machine-to-machine broadly refers to technologies which allow devices to communicate with other devices via wired and wireless networks. M2M devices will, in many cases, produce data that an M2M application may access, interpret and act upon. For example: an M2M device may send information representing a temperature reading of 47°C. An M2M application may receive this information, interpret it and then initiate some action.
  • the data exchange between a device and an application can occur synchronously or asynchronously. This is particularly likely where the communications network connecting to the M2M device is wireless.
  • Synchronous data exchange requires a real-time connection, but in many cases the M2M device will produce data that can be consumed by the application at a later point in time.
  • the data supplied by an electricity meter to a billing application can be supplied at substantially any time, the primary requirement being that the information is accurate. This means that certain communications can be postponed until off-peak hours, which may help smooth peaks in network traffic.
  • a contrary example is that of data transmitted from a vehicle to an emergency services application in the event of an accident.
  • a mechanism for asynchronous M2M communication is provided. This allows for a request received from an M2M application, the request for data from an M2M device, to still be serviced in the absence of a viable communication link between the network and the M2M device.
  • the wireless communications network is provided with a mechanism for interim data storage. This allows a request for data from an M2M application to be answered using the stored data, which includes the data most recently received from the M2M device. This allows requests for data to be serviced in the absence of a viable communication link between the network and the M2M device. Further, even if there is a viable communication link between the network and the M2M device, the request may be more quickly serviced from storage than by communicating directly with the device.
  • each device in the wireless communications network has a unique identity used by the network to distinguish between different devices.
  • This unique identity comprises at least one of the IMEI (International Mobile Equipment Identity), the IMSI (International Mobile Subscriber Identity), and the MSISDN (Mobile Subscriber Integrated Services Digital Network Number).
  • the M2M data is stored using a unique identifier for the M2M device, the unique identifier being the same as that used in the wireless communications network as a primary key.
  • each M2M data record stored is uniquely associated with the correct M2M device. Later, the data from a particular device can be readily retrieved because the stored data can be reliably associated with the particular device. Further, such retrieval can be done without the need to map the request to a new additional device identifier.
  • the method comprises receiving device generated data from a device via a wireless communication network.
  • the method also comprises retrieving a device identifier used by components within the wireless communication network to identify the device.
  • the method further comprises storing the device generated data with the retrieved device identifier.
  • the communications network is used to label the stored device generated data, the stored data is uniquely attributable to the device that generated it, without the need for provisioning a new unique identification number to each device.
  • the method may further comprise storing the device generated data using the retrieved device identifier as a primary key. Where the device generated data is stored in a file system, the root directory of the file system may be named with the device identifier.
  • the device may be a sensor, and may include a wireless communication module.
  • the method may further comprise receiving a request for particular device generated data.
  • the method may further still comprise, in response to such a request, retrieving the particular device generated data; and returning the particular device generated data in reply to the request.
  • the request may identify the particular device by its device identifier.
  • the device generated data can be readily retrieved from storage, particularly if the request for device generated data includes the device identifier in the retrieve message. If the request does not include the device identifier, then the method may further comprise mapping the device identified in the request to a device identifier.
  • the device identifier may comprise at least one of the MSISDN, IMSI, and IMEI.
  • the server comprises a receiver, a processor, and a memory.
  • the receiver is arranged to receive device generated data from a device via a wireless network.
  • the processor is arranged to retrieve a device identifier used by components within the wireless network to identify the device.
  • the memory is arranged to store the device generated data with the device identifier.
  • the server may further comprise a session database for receiving session information in respect of the device.
  • the session information may comprise an IP-address of the device, plus the device identifier.
  • the device identifier used by the wireless communications network may be required to discover the device identifier used by the wireless communications network if the device does not include the
  • the memory may store the device generated data in a file system, wherein the root directory of the file system is named with the device identifier.
  • the receiver may be further arranged to receive a request for particular device generated data.
  • the processor may be further arranged to retrieving the particular device generated data, and return the particular device generated data in reply to the request.
  • Figure 1 illustrates the basic arrangement of a system incorporating the method disclosed herein;
  • Figure 2 illustrates a storage tree maintained by a storage server
  • Figure 3 shows a signaling diagram illustrating the registration of a device 100 with the storage server and the subsequent storing of device generated data in the storage server;
  • Figure 4 shows a signaling diagram illustrating the retrieval by an application of data stored in the storage server
  • Figure 5 is a flow diagram illustrating a method of caching device generated data
  • Figure 6 is a flow diagram illustrating a method of retrieving cached device generated data
  • FIG. 7 illustrates the general structure of the server described above. Detailed description
  • the M2M data is stored using, as a primary key, the same unique identifier for the M2M device that is used in the wireless communications network.
  • FIG. 1 illustrates the basic arrangement of a system incorporating the method disclosed herein.
  • a plurality of devices and sensors connect to a wireless communications network 150.
  • a device 100, a coffee machine 101 , and a gateway 1 10 include wireless communication modules allowing them to communicate with the wireless communications network 150.
  • the device 100, the coffee machine 101 , and the gateway 1 10 are illustrated including a SIM card (Subscriber Identity Module card).
  • SIM card Subscriber Identity Module card
  • Each SIM card carries a unique serial number, the Integrated Circuit Card Identifier (ICCID) and the ICCID.
  • ICCID Integrated Circuit Card Identifier
  • the device 100, the coffee machine 101 , and the gateway 1 10 may each have an equipment identifier such as the International Mobile Equipment Identity (IMEI) which may be used by the wireless communications network 150 to identify them.
  • the device 100 and the coffee machine 101 contain at least one sensor, information from which is accessible by an external application 180.
  • the gateway 1 10 communicates with sensors 105 by a local communication network.
  • the sensors 105 may connect to the gateway 1 10 by wire, or by a local wireless connection such as BluetoothTM or WiFiTM.
  • a storage server 170 is connected to the wireless communications network 150.
  • the storage server 170 is arranged to receive requests from and serve responses to the application 180.
  • the storage server 170 is a part of the wireless communications network 150.
  • the applications 180 may reside either within or outside of the wireless communications network 150.
  • device 100 In the following explanation reference will be made to device 100. However the following may equally apply to the coffee machine 101 or the combination of the gateway 1 10 with at least one sensor 105.
  • a device 100 sends a store request to the storage server 170 via the wireless communications network 150.
  • the store request may be sent using HTTP POST and a unique ID, for example "devicelD".
  • Such a store request may be arranged as: http://www.m2mse.com/devicelD/temp/14july201 1/highest_temp
  • the store request comprises a host URL part, which in the above example is "www.m2mse.com”. This points to the storage server 170, which in this example has the host name "m2mse”.
  • the store request further comprises a path part, which is 7devicelD/temp/14july201 1/highest_temp" in the above example. This path part is used to direct where to store the body of the store request, which in this example is stored as "temp.xml".
  • the first section of the path part of the store request in this case the device identifier "devicelD" must be provisioned (either manually or automatically) by the device 100 before it sends the store request.
  • the device identifier must be unique such that the storage server 170 can distinguish between different devices.
  • the storage server 170 makes use of the SIM card that uniquely identifies a wireless communications device such as device 100, gateway 1 10 or coffee machine 101 .
  • the unique identity carried by the SIM card uniquely identifies the SIM card to the wireless communications network 150.
  • This unique identity that is used by the wireless communications network 150 is also used by the storage server 170 to create a storage tree or directory structure for storage of the resource received from the device 100.
  • the storage path (which points to a resource) is thus preserved from the original request. What is added is the identity used by the wireless communications network 150 as the root of each different storage path.
  • the wireless communications network 150 includes a home location register which maps the IMSI on the SIM card to the MSISDN.
  • the MSISDN corresponding to an IMSI is readily identified by both the wireless
  • the MSISDN is used as a unique identifier attributable to device 100.
  • Figure 2 illustrates a storage tree maintained by a storage server 170.
  • the storage server 170 is the "m2mse” storage server referenced above and it has received a store request as follows: http://www.m2mse.com/MSISDN1/temp/14july201 1/highest_temp
  • the root of "m2mse” comprises three directories each for a different device 100 that the storage server 170 has received store requests from.
  • the storage server has stored the resource "temp.xml” in the directory called “highest_temp”, which in turn is stored in a directory for today's temp called "14 July 201 1", which in turn is stored in a directory called “temp”, which in turn is stored in a directory called "MSISDN1".
  • Data from days preceding the 14 July 201 1 is stored in directories alternative to the "14 July 201 1 ".
  • pressure data is stored in a directory alternative to the "temp" directory.
  • FIG. 3 shows a signaling diagram illustrating the registration of a device 100 with the storage server 170 and the subsequent storing of a resource in the storage server 170.
  • Storage server 170 comprises a session database 171 , a web server 172, and a storage 173.
  • the device 100 sends a PDP context activation to the Gateway GPRS Support Node of a wireless communications network 150.
  • the PDP context is a data structure which contains the identity of the device 100 as used by the wireless
  • session information from the PDP context is sent from the wireless communications network 150 to a session database 171 in the storage server 170.
  • the session information includes the device IP address, the device MSISDN, and the device IMSI.
  • the session information is stored in the session database 171 .
  • a store request is sent from the device 100 to the web server 172 of the storage server 170.
  • the store request takes the form: http://www.m2mse.com/temp/14july201 1/highest_temp where the address of the web server 172 is "www.m2mse.com".
  • This store request does not indicate the device identifier, so at 305, the web server 172 retrieves the MSISDN of the device 100 that sent the store request from the session database 171 .
  • the web server 172 uses the IP-address of the device 100, which it received with the store request, to identify the device 100 to the session database 171 .
  • the web server 172 has the MS ISDN of the device 100, at 306 it uses this to store the data (here xml data "temp.xml” describing today's highest temperature) using the same path as received in the store request
  • FIG. 4 shows a signaling diagram illustrating the retrieval of data stored in the storage server 170 by an application 180.
  • an application 180 issues an HTTP GET request to the storage server 170.
  • the HTTP GET message is received by the web server 172, which in this example has the host name "M2MSE". Since the path (pointing to a resource) from the original store request (sent from the device 100 to storage server 170) is preserved in the storage 173, the application 180 can use the same path in its HTTP GET request.
  • the HTTP GET request comprises: http://www.m2mse.com/MSISDN1/temp/14july201 1/highest_temp
  • the application 180 provides the MSISDN number for the particular device 100. This allows for expedient processing of the get request at 402, whereby the web server 172 accesses the storage 173 at the tree path indicated by the received identity "MSISDN1 " and retrieves the resource indicated by the path indicated in the get request. At 403 the retrieved resource is sent by the web server 172 to the application 180.
  • the above described method and apparatus allows a device 100 to store data in the storage server 170 re-using a device identifier that is used in the wireless communications network 150. This means that the data is stored without the need for provisioning a new unique key for that purpose. Further, this solution offers a secure way for a device to either write or read its own data. There is minimal risk of a device writing to or an application reading from the wrong data area because the area is identified by the unique ID used by the wireless communications network.
  • the application 180 may not include the MSISDN of the particular device 100 in its HTTP GET request at 401 . In that case, the storage server 170 accesses a database to map the identity given in the HTTP GET request, such as an external ID, to the appropriate MSISDN.
  • the database may be part of the wireless communications network 150, such as a Home Location Register. Such a mapping step would always be required if a new unique identifier was used for the storage of data. Using the same identifier for data storage that is used in the wireless communications network to identify the device still provides the above described advantages in the storage of data even if the application 180 does not use this identifier for data retrieval.
  • Figure 5 is a flow diagram illustrating the method of caching device generated data.
  • device generated data is received from a device via a wireless communications network.
  • a device identifier is retrieved, the device identifier being that used by components within the wireless communications network to identify the device.
  • the device generated data is stored with the device identifier, that is, the device generated data is stored in association with the device identifier. The device generated data may then be located in and retrieved from storage using the device identifier.
  • Figure 6 is a flow diagram illustrating the method of retrieving cached device generated data.
  • a request for particular device generated data is received.
  • the request includes a device identifier, the device identifier being that used by components within the wireless communications network to identify the device.
  • the particular device generated data is retrieved from a data store, using the received device identifier.
  • a reply to the request is sent, the reply comprising the particular device generated data.
  • FIG. 7 illustrates the general structure of the server described above.
  • the server 700 comprises a receiver 710, a processor 720, and a memory 730.
  • the receiver 710 comprises a communications module for receiving and sending messages.
  • the receiver 710 is arranged to communicate via a wireless communications network, and can receive device generated data from a plurality of devices via the wireless communications network.
  • the receiver 710 is further connected to a wired network and can receive a request for device generated data from an application either via the wired network or via the wireless communications network.
  • the server 700 further comprises a processor 720, which is arranged to perform the method disclosed herein.
  • the processor 720 controls
  • the memory 730 may store the device generated data.
  • the device generated data is stored on a storage device external to the server but connected thereto via a communications network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de mise en cache de données générées par un dispositif. Le procédé consiste à recevoir des données générées par un dispositif à partir d'un dispositif par l'intermédiaire d'un réseau de communication sans fil. Le procédé consiste en outre à extraire un identificateur de dispositif utilisé par des composants à l'intérieur du réseau de communication sans fil pour identifier le dispositif; et à stocker les données générées par le dispositif avec l'identificateur de dispositif.
EP11735638.6A 2011-07-14 2011-07-14 Traitement de données générées par un dispositif Ceased EP2732403A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2011/062100 WO2013007314A1 (fr) 2011-07-14 2011-07-14 Traitement de données générées par un dispositif

Publications (1)

Publication Number Publication Date
EP2732403A1 true EP2732403A1 (fr) 2014-05-21

Family

ID=44509258

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11735638.6A Ceased EP2732403A1 (fr) 2011-07-14 2011-07-14 Traitement de données générées par un dispositif

Country Status (4)

Country Link
US (1) US10045175B2 (fr)
EP (1) EP2732403A1 (fr)
CN (1) CN103703474B (fr)
WO (1) WO2013007314A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2803208B1 (fr) * 2012-01-13 2018-09-05 Iot Holdings, Inc. Procédé et appareil permettant la réalisation de communications de machine à machine
EP3024256B1 (fr) 2012-02-03 2019-11-06 Iot Holdings, Inc. Procédé et appareil pour supporter des services à base de contexte et contenu m2m
US20160092886A1 (en) * 2014-09-30 2016-03-31 Nalpeiron Inc. Methods of authorizing a computer license
EP3202171A4 (fr) * 2014-10-03 2018-04-04 IMC Holdings, Inc. Procédés et systèmes pour le contrôle des stocks
JPWO2017056194A1 (ja) * 2015-09-29 2017-10-05 株式会社東芝 情報機器または情報通信端末および、情報処理方法
US11418947B2 (en) 2016-08-30 2022-08-16 Radcom Ltd. Mobile network user monitoring system
CN110169037A (zh) * 2017-01-03 2019-08-23 德国电信股份有限公司 用于使用移动通信网络来在一方面应用服务器与另一方面至少一个物联网通信设备之间进行数据传输的方法、移动通信网络、系统、物联网通信设备、程序和计算机程序产品

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19844631A1 (de) * 1998-09-29 2000-04-06 Gantner Electronic Gmbh Schrun System zur Überwachung, Steuerung, Verfolgung und Handling von Objekten
WO2000078001A2 (fr) * 1999-06-11 2000-12-21 Microsoft Corporation Modele de commande de dispositif distant guide par donnees, avec adaptateur general de messagerie entre interface de programmation et reseau
EP1083768A1 (fr) * 1999-09-08 2001-03-14 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Procédé pour faciliter de la transmission de données
US20030005177A1 (en) * 2001-06-30 2003-01-02 Duran Louis A. Loading files for a hardware device
US20040133453A1 (en) * 2002-11-27 2004-07-08 Jean-Philippe Jomini Method and system for providing at home health care service
US7148803B2 (en) 2003-10-24 2006-12-12 Symbol Technologies, Inc. Radio frequency identification (RFID) based sensor networks
ATE461428T1 (de) 2004-06-16 2010-04-15 Swisscom Ag Elektronische baueinheit mit einem messsensor und einer drahtlosen schnittstelle
US7130773B1 (en) * 2004-11-30 2006-10-31 Sun Microsystems, Inc. Method and apparatus for processing data using objects
PL1829317T3 (pl) * 2004-12-22 2008-08-29 Ericsson Telefon Ab L M Sposoby i układy do zapisywania w pamięci podręcznej informacji statycznych dla aplikacji danych pakietowych w bezprzewodowych systemach telekomunikacyjnych
US8325614B2 (en) * 2010-01-05 2012-12-04 Jasper Wireless, Inc. System and method for connecting, configuring and testing new wireless devices and applications
US8849908B2 (en) * 2005-10-13 2014-09-30 Kaydon A. Stanzione Internet based data, voice and video alert notification communications system
ZA200903090B (en) * 2006-11-06 2010-07-28 Ericsson Telefon Ab L M Method and apparatuses for allowing session control of IMS services via a CS access by USSD messages
CN101222419B (zh) 2007-01-10 2011-07-20 华为技术有限公司 数据通信方法及系统、数据发送/接收装置
US8311042B2 (en) * 2007-06-15 2012-11-13 Mformation System and method for automatic detection and reporting of the mapping between device identity and network address in wireless networks
WO2009071735A1 (fr) * 2007-12-05 2009-06-11 Erace Security Solutions Oy Ltd Gestion de station mobile
US8407769B2 (en) * 2008-02-22 2013-03-26 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for wireless device registration
US20090253409A1 (en) * 2008-04-07 2009-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Method of Authenticating Home Operator for Over-the-Air Provisioning of a Wireless Device
US20100100876A1 (en) * 2008-10-21 2010-04-22 Enfora, Inc. Wireless device provisioning hardware tool
US9456007B2 (en) * 2008-11-15 2016-09-27 Adobe Systems Incorporated Session aware notifications
BR112012022204B1 (pt) * 2010-03-01 2022-04-19 IOT Holdings, Inc Gateway entre máquinas
US9135031B1 (en) * 2010-04-28 2015-09-15 Netapp, Inc. System and method for determining storage resources of a virtual machine in a virtual server environment
WO2011163561A1 (fr) * 2010-06-25 2011-12-29 Interdigital Patend Holdings, Inc. Interface d'un serveur m2m avec la dorsale 3gpp
US9310345B2 (en) * 2010-09-30 2016-04-12 Hitachi, Ltd. Sensor system, computer, and machine
US8713365B2 (en) * 2011-01-28 2014-04-29 Microsoft Corporation Re-establishing push notification channels via user identifiers
US20120246305A1 (en) * 2011-03-23 2012-09-27 Hughes Network Systems, Llc System and method for management of cots devices in managed networks based on device auto-detection
EP2721849A4 (fr) * 2011-06-15 2015-03-04 Ericsson Telefon Ab L M Mise à disposition de données de service de connectivité dans un réseau de télécommunication

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None *
See also references of WO2013007314A1 *

Also Published As

Publication number Publication date
WO2013007314A1 (fr) 2013-01-17
CN103703474A (zh) 2014-04-02
US10045175B2 (en) 2018-08-07
CN103703474B (zh) 2018-01-19
US20140143383A1 (en) 2014-05-22

Similar Documents

Publication Publication Date Title
US10848526B2 (en) Device triggering
US10045175B2 (en) Handling device generated data
EP3669561B1 (fr) Procédé d'obtention de données d'abonnement concernant un abonné dans un réseau de télécommunication
JP2019537356A (ja) ユーザ端末の位置エリアの更新方法、アクセスネットワークエンティティ、ユーザ端末およびコアネットワークエンティティ
EP3413537B1 (fr) Procédé de transmission d'informations et appareil d'accès à un réseau central
CN103491527B (zh) 一种检索终端外部标识的方法及系统
EP2469766A1 (fr) Procédé, système et appareil de transmission de données
US9451429B2 (en) Message processing method with respect to terminal having multiple external identifiers
CN110621051B (zh) 路由方法及装置
US10863555B2 (en) Access method, apparatus, device, and system
CN117812577A (zh) 一种通信方法及装置
CN1926892B (zh) 通过寻址硬件部分将消息发送到移动台的方法与设备
CN102215560A (zh) 一种对m2m终端实现管理的方法及系统
WO2012065492A1 (fr) Procédé et terminal d'envoi d'imsi
CN102158828B (zh) 短消息处理方法和设备
US20140357264A1 (en) Method and Arrangement For Connectivity in a Communication Network
CN102546846A (zh) 业务服务器地址的获取方法、系统及装置
EP3046312A1 (fr) Procédé et dispositif de traitement d'informations d'identification
GB2594930A (en) Authentication of devices to third party services
US20250227512A1 (en) Communication method and apparatus
CN117440332A (zh) 信息发送方法、物联网短信息中心、终端设备及存储介质
CN102811431A (zh) 建立imsi和msisdn映射关系的方法及装置
WO2016106598A1 (fr) Procédé et appareil de sélection de réseau d'accès
CN104243567A (zh) 一种用于在云计算传送信息的方法

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

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

APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

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

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20230516