EP3811203A1 - Verfahren zum aktualisieren von software auf einem zielgerät - Google Patents
Verfahren zum aktualisieren von software auf einem zielgerätInfo
- Publication number
- EP3811203A1 EP3811203A1 EP19726990.5A EP19726990A EP3811203A1 EP 3811203 A1 EP3811203 A1 EP 3811203A1 EP 19726990 A EP19726990 A EP 19726990A EP 3811203 A1 EP3811203 A1 EP 3811203A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- update
- software
- target device
- data packet
- information
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/658—Incremental updates; Differential updates
Definitions
- the invention is based on a method or a device according to the type of the independent claims.
- the present invention also relates to a computer program.
- So-called delta processes can be used to update the software of components. Differences between two software versions are calculated and transferred to the respective components.
- Update device a corresponding update device, a method for processing a data packet and / or
- Update device deposited copy of the current software to create a data packet representing the new software
- the target device and / or the update device can be used and / or arranged, for example, in a vehicle or in an industrial system or a machine or in various other devices that are connected and connected to one another.
- a target device or target unit can be understood to mean an electrical device, for example a control device that processes sensor signals and outputs control and / or data signals as a function thereof.
- the target device can have an interface that can be designed in terms of hardware and / or software.
- the target device controls the
- the target device can, for example, access sensor signals such as acceleration, pressure, steering angle or environment sensor signals.
- the control can take place via corresponding actuators such as brake or steering actuators.
- a device for example installed in the vehicle, can be used for storing backups and controlling
- Update processes can be understood in a delta process.
- the first interface can be a radio interface for wireless communication, for example with the vehicle.
- communication can take place via the first interface in a wired manner.
- the second interface can be a radio interface for wireless communication, for example with the vehicle.
- An external data processing device can be understood to mean, for example, a server or a mobile terminal. Under one
- Differentiation information can be understood, for example, a so-called delta file.
- a delta file also referred to as a delta update file
- the differentiation information can represent a significantly smaller amount of data compared to a full version of the new software.
- the data package can be a compressed or uncompressed update package for installing the full version of the new software.
- the issuing step can be dependent on whether that
- Target device only a software updater or additionally one
- Update unit for example with a delta installer, for performing a delta method.
- the data packet can be output in the first case, while in the second case it is sufficient to output only the differentiation information.
- the approach presented here relates to devices that have software updates or consist of several components, each of which supports a software update, but has its own memory and is connected to one another. Individual components can be restricted due to their resource situation.
- the approach presented here is based on the knowledge that to update the software of individual components, for example a vehicle, to a new version, a so-called delta file, which contains the differences between a currently installed version and the new version, and a copy of the, for example, stored in the vehicle currently installed version can be used, for example, to calculate and check the new version in the vehicle itself, before the new version is loaded onto the relevant component.
- a so-called delta file which contains the differences between a currently installed version and the new version
- a copy of the, for example, stored in the vehicle currently installed version can be used, for example, to calculate and check the new version in the vehicle itself, before the new version is loaded onto the relevant component.
- security For example, errors affecting the vehicle when updating are kept to a minimum. It also has one
- Update procedure has the advantage that, instead of a full version of the software, only the delta file assigned to the relevant component
- Update This enables the update to be carried out particularly quickly and efficiently, in particular if the update is imported, for example, via a radio interface.
- both the old and the new software are stored in the vehicle as a centrally stored backup, it is possible, for example, in the event of an error, to perform a full update or rollback as required
- the approach presented here encompasses a system-wide delta update procedure that calculates, saves and verifies new versions from a delta file in an update device, such as a central delta installer with an integrated backup server, in order to use the new software in a second Step to distribute to the appropriate target units in the overall system.
- an update device such as a central delta installer with an integrated backup server
- Only one delta update version should ever be transmitted, be it wireless or in the internal system, for example via a vehicle bus.
- Delta update files can only be transferred if the target unit also has a delta update.
- Backup software for the individual target units must be available in the update device or at least be able to be loaded.
- the update device can be created, for example, with one or more central installation units with one or more delta installers with corresponding storage resources, although it is rather common only to have a central point that supports several Delta Installers if necessary.
- These central installation units with delta installer can have one or more delta update procedures and must also have the current software of the target unit as a backup or at least have access to it. It does not matter whether the target units use an update unit with or without a delta installer. The security of the update process is therefore not solely due to the individual components, but primarily centrally through the
- Update units with delta installers of the individual components require minimal additional resources and less memory access than with a full update.
- a major advantage of the approach presented here is that a resource-related expansion of the target units, such as RAM or flash memory, can be omitted and a secure update including rollback can still be supported. This means that even small target systems can use delta update procedures.
- Another advantage is that wireless data transmission to the overall system, for example, can be minimized by the delta update process. This also applies to individual components that do not themselves support delta updates, and also in the event that a full update is to take place via the internal bus.
- the bus load in the target system can be minimized if the target units themselves have an update unit with a delta installer.
- the target units can carry out a delta update process very quickly, since no additional memory accesses are required.
- the installation unit of the target units with delta installer does not require any rollback functionality for each component, since this can be implemented centrally in the update device.
- the protection of the delta installer against each component is also advantageous.
- the update device runs autonomously with the central delta installer and can check the received software without influencing the target unit and save it in a new version as a backup, it can be checked whether the software is correct before the user is even affected by a software update can be.
- defects in target units can be avoided since the software is pre-checked or a backup of a full version of old and new software is available in the update device with a central delta installer.
- Such a method can easily be integrated into existing central units, such as a central gateway.
- such a method can be applied to any number of components, provided there is enough storage space.
- the method can include a step of
- the step of outputting the data packet and / or the differentiation information can be outputted depending on a result of the checking.
- the integrity of the data packet can be determined using a
- Checksum are checked to detect bit errors in the data packet. This allows errors in the data packet to be recognized early or corrected. This prevents incorrect software updates on the target device. Alternatively, bit errors can already be handled by the software update process. According to a further embodiment, the
- Discrimination information is suppressed when it is found during the check that the data packet is faulty. This can prevent incorrect update data from being transferred to the target device. Functional failures of the target device as a result of an incorrect update can thus be avoided.
- Data packets received by the update device are forwarded directly to the target device without prior calculation.
- the target device and the update device calculate the new software in parallel or in succession.
- the new software can be labeled as the current software if the result information from the target device indicates that the update was successful. Additionally or alternatively, the step of issuing can be carried out again by the update device in order to obtain the copy and / or reset information
- the target device Return the target device to an earlier version of the software to the interface to the target device if the result information of the target device indicates that the update was unsuccessful. As a result, the risk of functional failures of the target device as a result of an update can be reduced to a minimum.
- the target device is reset to an earlier version of the software
- Update device with a central delta installer calculate a delta version between the new and old version in order to switch from the new software back to the old one. To do this, the installation units with the central delta installer also require a delta generator.
- the approach presented here creates an update device with units that are designed to execute and / or to control the method according to one of the above embodiments.
- the approach presented here also creates a process for
- the approach presented here also relates to a target device with units which are designed to carry out and / or to control the processing method according to the above embodiment.
- Target device or an update device can be implemented.
- a computer program product or computer program with program code which can be stored on a machine-readable carrier or storage medium such as a semiconductor memory, a hard disk memory or an optical memory and for carrying out, implementing and / or controlling the steps of a method according to one of the
- Fig. 1 is a schematic representation of a data flow in the
- FIG. 2 shows a schematic illustration of the creation of a data packet from FIG. 1;
- FIG. 3 shows a schematic illustration of an update device from FIG. 1 at three successive points in time
- Fig. 4 is a schematic representation of a data flow in the
- FIG. 5 shows a flowchart of a method for updating software according to an exemplary embodiment
- Fig. 6 is a flowchart of a method for processing a
- Fig. 7 is a schematic representation of a vehicle according to a
- Fig. 1 shows a schematic representation of a data flow in the
- Updating software on three target devices 100, 102, 104 here only by way of example control devices of a machine, here only by way of example of a vehicle, in a method according to an exemplary embodiment.
- An exemplary sequence of an over-the-air update process is shown with an update device 106, which comprises an installation unit 120 with a central delta installer for target devices 100, 102 with and for a target device 104 without a delta update.
- the three target devices 100, 102, 104 are each coupled to a central update device 106, for example of the vehicle.
- the update device 106 comprises a receiving unit 108 for
- Interface 116 here a radio interface as an example, to an external data processing device 118, which can also be a cable connection or a USB medium, among other things.
- Differentiation information 110, 112, 114 is, for example, each a delta update file for software update in a so-called delta method.
- the differentiation information in each case represents differences between current software installed on the respective target device 100, 102, 104 and new software to be installed on the respective target device 100, 102, 104.
- Receiving unit 108 received differentiation information 110, 112, 114 each with a suitable storage unit 122, such as one
- Flash memory combined copy of the current software installed on the respective target devices 100, 102, 104 to combine to form a data packet.
- the three data packets each represent a full version of the new software to be installed on the respective target devices 100, 102, 104.
- the installation unit 120 checks the data packets for their respective integrity, for example by means of checksums or other suitable check values. Only if a data packet is error-free and the calculation of the full version of the new software was also successful, does the installation unit 120 trigger one
- Update process for updating the relevant target device 100, 102, 104 is updated.
- the installation unit 120 provides the first differentiation information 110 after it has been more successful Checking the data packet assigned to the first target device 100, the second differentiation information 112 after successful checking of the data packet assigned to the second target device 102 and a data packet 124 assigned to the third target device 104 after its successful checking, each to a second interface 126, here, for example, to a CAN Bus of the vehicle.
- the target devices 100, 102, 104 each include one
- Target device receiving unit 128 for reading in data via the second
- the update units 130 each include a suitable software updater.
- the first target device 100 and the second target device 102 each comprise an update unit with a delta installer for carrying out a delta update using the first differentiation information 110 in the case of the first target device 100 or using the second differentiation information 112 in the case of the second
- the update unit 130 of the third target device 104 is designed to carry out the update exclusively as a full update by means of the third data packet 124.
- a delta installer is a software component as an extension to a software updater.
- a software updater is a software component in a target device that is responsible for its own software update.
- FIG. 2 shows a schematic representation of the creation of a data packet from FIG. 1.
- the receiving unit 108 and the installation unit 120 are shown.
- the update device 106 first receives the corresponding delta file from the receiving unit 108, here, for example, the first
- Discrimination information 110 searches in a step 200 in the
- Storage unit after the corresponding copy of the current software, creates the data packet in a subsequent step 202 by calculating the full version of the new software using the
- FIG. 3 shows a schematic illustration of an update device 106 from FIG. 1 at three successive times one
- version 1.0 is to be updated to version 1.1.
- the storage unit 122 After receiving the discrimination information 110, the storage unit 122 has the first in addition to the copy 300
- Distinction information 110 which represents a delta between version 1.0 and a new version 1.1 of the software, as shown in the middle image.
- the right picture shows the content of the storage unit 122 after the calculation of the full version 1.1.
- Fig. 4 shows a schematic representation of a data flow in the
- the update device 106 contains the copy 300, the first differentiation information 110 and the data packet 302.
- the target device 100 is updated in three ways.
- the update device 106 merely provides the target device 100 with the differentiation information 110.
- the target device 100 then updates the current software using the delta installer and finally stores the version of the new software in a target device storage unit 400, for example a flash memory.
- the update device 106 provides the target device 100 with the data package 302 with the full version 1.1 for updating the current software, for example if the update using the delta installer fails.
- the update device 106 provides the target device 100 with the copy 300 of version 1.0, for example.
- 5 shows a flowchart of a method 500 for updating software according to an exemplary embodiment.
- the method 500 can be carried out, for example, using an update device, as described above with reference to FIGS. 1 to 4.
- the differentiation information or, depending on the number of target devices to be updated, a plurality of differentiation information assigned to one target device is received via the first interface to the data processing device external to the vehicle, for example.
- the differentiation information is combined with a copy of a current software version stored on the respective target devices stored in the update device.
- resulting data packets represent, for example, a full version of the new software to be installed for each target device.
- Distinguishing information about the second interface to the target devices If the target device to be updated has, for example, a suitable delta installer, the update to the new software version can take place in a particularly resource-saving manner solely by means of the differentiation information transmitted to the target device and the current version on the target device.
- FIG. 6 shows a flowchart of a method 600 for processing a data packet and / or a differentiation information according to one
- the method 600 can be carried out, for example, using one of the target devices, as described above with reference to FIGS. 1 to 5.
- the corresponding data packet or the corresponding differentiation information is received via the second interface, for example a CAN bus. This takes place in a second step 620
- Update of the current software available on the target device in question using the data packet for example a
- each target unit in the vehicle in FIG. 1 the three target devices 100, 102, 104 in this example, each has a software updater 128 with full update functionality and possibly a delta installer 130.
- software updaters with delta Installers receive software updaters without a delta installer, not a delta file, but a full version for software updates.
- the vehicle has a central delta installer.
- This central delta installer previously called installation unit 120, is either part of an already existing component, for example a central gateway or an over-the-air master, or is implemented as an independent unit. If an existing central component is expanded, the installation unit 120 or the central component is the update master, for example.
- the installation unit 120 has direct access via the storage unit 122 to backups of all software in the system which are to be updated by this method.
- versions of the currently used software of all components should be available as full versions and be stored in a correspondingly large persistent storage unit 122.
- These software backups for example, are flashed once during production or even pre-flashed.
- the installation unit 120 accepts the delta update file of each individual target unit, searches for the corresponding backup in the storage unit 122 and uses this combination by means of a delta installer in the storage unit 122, as is shown schematically in FIG. 2.
- the installation unit 120 now checks the calculated new software for correctness and saves it locally as the new backup version 302.
- the update device 106 thus has the full version of the current software of each target unit, the full version of the new software of each target unit and the respective delta update file of each target unit. This can be seen from FIGS. 3 and 4.
- the entire or subsystem is put into update mode.
- the individual software updates of the target units are offered the previously received delta update file or the full version of the new software as an update package.
- Target units now also use the delta update method, for example, and confirm the respective result to installation unit 120.
- the installation unit 120 sends the previously self-calculated new full version in the form of the data packet 302 as a full update, compressed or uncompressed, to the relevant target unit, as shown in FIG. 4.
- the old backup version for example, is transmitted in the form of a copy 300 as a full update.
- the new version 302 of the software is noted in the installation unit 120 as the currently valid version, so that it can be used as a reference for further updates.
- a condition for the update using the delta method is also that the delta installer in the installation unit 120 and the delta installer in the target unit to be updated are compatible.
- a direct update for example via the vehicle bus, the
- Installation unit 120 can also be updated so that the versions remain identical. Otherwise, a later over-the-air update in the field would only be possible with a full update.
- the copy 300 of the current software is not permanently available in the storage unit 122, but is only loaded by the relevant target unit when required. Thus, an initial flashing of the memory unit 122 can be omitted.
- the installation unit 120 additionally comprises a delta generator, for example in order to also be able to transmit a rollback file, which is calculated by the packages 302 and 300, as a delta file.
- the vehicle 700 for example a road vehicle for the transportation of people, has a target device 100.
- the target device 100 is, for example, an engine control device or an airbag control device with a functionality as implemented in known control devices.
- the target device 100 has a rewritable memory for storing software for operating the target device 100. To the software too
- an update device 106 is integrated in the vehicle 700, which is designed to transmit a data packet 302 and additionally or alternatively a signal comprising differentiation information 110 to the target device 100.
- the data packet comprises
- Embodiment an updated version of the software for storage in the memory of the target device 100.
- the distinction information 110 comprises data which is a difference between the software stored in the target device 100 and the updated Define software version.
- Differentiation information 110 is transmitted in the form of electrical signals according to one exemplary embodiment.
- the update device 106 is designed to receive a signal, which includes the differentiation information 110, from a data processing device 118 arranged outside the vehicle and to use it to generate the data packet 302.
- the data processing device 118 has a combining device which is designed to combine the differentiation information 110 with a copy 300 of the software currently stored in the target device 100, which is stored in a memory of the update device 106.
- the data processing device 118 has a combining device which is designed to combine the differentiation information 110 with a copy 300 of the software currently stored in the target device 100, which is stored in a memory of the update device 106.
- Data processing device 118 has a checking device which is designed to check the data packet 302 for errors.
- the update device 106 is designed to, depending on a result of the check carried out in the checking device, either the data packet 302 or the
- an exemplary embodiment comprises a “and / or” link between a first feature and a second feature, this is to be read in such a way that the embodiment according to one embodiment has both the first feature and the second feature and according to a further embodiment either only that has the first feature or only the second feature.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102018209972.3A DE102018209972A1 (de) | 2018-06-20 | 2018-06-20 | Verfahren zum Aktualisieren von Software auf einem Zielgerät mittels einer Aktualisierungseinrichtung und Verfahren zum Verarbeiten eines Datenpakets und/oder einer Unterscheidungsinformation mittels eines Zielgeräts |
PCT/EP2019/063602 WO2019242996A1 (de) | 2018-06-20 | 2019-05-27 | Verfahren zum aktualisieren von software auf einem zielgerät |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3811203A1 true EP3811203A1 (de) | 2021-04-28 |
Family
ID=66668936
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19726990.5A Pending EP3811203A1 (de) | 2018-06-20 | 2019-05-27 | Verfahren zum aktualisieren von software auf einem zielgerät |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP3811203A1 (de) |
CN (1) | CN112567339A (de) |
DE (1) | DE102018209972A1 (de) |
WO (1) | WO2019242996A1 (de) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113505363B (zh) * | 2021-08-04 | 2022-11-29 | 上海瓶钵信息科技有限公司 | 通过软件方式实现存储空间防重放的方法和系统 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103699408A (zh) * | 2013-12-12 | 2014-04-02 | 乐视网信息技术(北京)股份有限公司 | 一种软件升级的方法和设备 |
JP6216730B2 (ja) * | 2015-03-16 | 2017-10-18 | 日立オートモティブシステムズ株式会社 | ソフト更新装置、ソフト更新方法 |
US10101992B2 (en) * | 2015-06-15 | 2018-10-16 | Lear Corporation | Telematics control unit comprising a differential update package |
US10437680B2 (en) * | 2015-11-13 | 2019-10-08 | Kabushiki Kaisha Toshiba | Relay apparatus, relay method, and computer program product |
JP6755158B2 (ja) * | 2016-09-30 | 2020-09-16 | 株式会社日立製作所 | 計算機システム、計算機システムによるソフトウェアの更新方法、及び、そのためのプログラム |
-
2018
- 2018-06-20 DE DE102018209972.3A patent/DE102018209972A1/de active Pending
-
2019
- 2019-05-27 EP EP19726990.5A patent/EP3811203A1/de active Pending
- 2019-05-27 CN CN201980053946.5A patent/CN112567339A/zh active Pending
- 2019-05-27 WO PCT/EP2019/063602 patent/WO2019242996A1/de unknown
Also Published As
Publication number | Publication date |
---|---|
CN112567339A (zh) | 2021-03-26 |
WO2019242996A1 (de) | 2019-12-26 |
DE102018209972A1 (de) | 2019-12-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE102019109672A1 (de) | Rückgängigmachung nach einem teilausfall in mehreren elektronischen steuergeräten mittels over-the-air-updates | |
EP3218804A1 (de) | Update einer firmware | |
DE19839680A1 (de) | Verfahren und Vorrichtung zur Veränderung des Speicherinhalts von Steuergeräten | |
WO2019096840A1 (de) | Verfahren und system zum aktualisieren einer fahrzeugsoftware | |
WO2019137773A1 (de) | Absicherung eines softwareupdates eines steuergerätes eines fortbewegungsmittels | |
EP3811203A1 (de) | Verfahren zum aktualisieren von software auf einem zielgerät | |
DE102021211908A1 (de) | Verfahren zum Verarbeiten von Daten | |
EP3353650A1 (de) | System und verfahren zur verteilung und/oder aktualisierung von software in vernetzten steuereinrichtungen eines fahrzeugs | |
DE102015207795A1 (de) | Verfahren und Vorrichtung zum Aktualisieren von Software in einem Transportmittel | |
WO2017178211A1 (de) | Verfahren zum betreiben eines steuergeräts für ein fahrzeug, steuergerät, betriebssystem, kraftfahrzeug | |
DE102013021231A1 (de) | Verfahren zum Betrieb eines Assistenzsystems eines Fahrzeugs und Fahrzeugsteuergerät | |
EP3384411B1 (de) | Verfahren zum übertragen eines funktionsbefehls zwischen einem kraftfahrzeug und einer fahrzeugexternen einrichtung sowie schnittstellenvorrichtung und system | |
EP3724758B1 (de) | Verfahren zum durchführen eines updates einer softwareapplikation in einem gerät, das sich im betrieb befindet, sowie gerät und kraftfahrzeug | |
EP2962162B1 (de) | Verfahren zur einrichtung oder aktualisierung einer programmierung eines steuergerätes eines verkehrsmittels | |
DE102019000493A1 (de) | Verfahren zur Aktualisierung einer jeweiligen Software mehrerer Steuergeräte eines Fahrzeugs | |
WO2020099023A2 (de) | Steuergerät für eine fahrzeugkomponente, kit umfassend ein steuergerät und eine testereinrichtung, fahrzeug, verfahren zum aktualisieren eines steuergeräts und computerlesbares speichermedium | |
DE102020216481A1 (de) | Verfahren zum Betreiben eines Steuergeräts und Steuergerät | |
DE102012217312B4 (de) | Verfahren und System zur Aktualisierung von Code in Verarbeitungssystemen | |
DE102012218665B4 (de) | Applikationssystem für Steuergeräte | |
WO2009103728A1 (de) | Verfahren und vorrichtung zum speichern von informationsdaten | |
DE202014010619U1 (de) | Update einer Firmware | |
DE102017222267A1 (de) | System und Verfahren zum Aktualisieren von Softwaremodulen mindestens eines Schienenfahrzeugs | |
WO2023006531A1 (de) | Verfahren zur überprüfung digitaler signaturen, fahrzeug-recheneinheit und fahrzeug | |
DE102020216071A1 (de) | Verfahren zum Betreiben einer Vorrichtung, ein Steuergerät eines Kraftfahrzeugs, und Vorrichtung | |
WO2023020807A1 (de) | Automatisches erkennen und korrigieren von speicherfehlern in einem sicheren mehrkanaligen rechner |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
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 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20210120 |
|
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 |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAV | Request for validation of the european patent (deleted) | ||
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: 20230213 |