EP3320431A1 - Computer-implemented method for processing data object variants - Google Patents
Computer-implemented method for processing data object variantsInfo
- Publication number
- EP3320431A1 EP3320431A1 EP16738099.7A EP16738099A EP3320431A1 EP 3320431 A1 EP3320431 A1 EP 3320431A1 EP 16738099 A EP16738099 A EP 16738099A EP 3320431 A1 EP3320431 A1 EP 3320431A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data object
- feature type
- variants
- matching
- computer
- 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
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4494—Execution paradigms, e.g. implementations of programming paradigms data driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM]
- G05B19/41885—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM] characterised by modeling, simulation of the manufacturing system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/4492—Inheritance
Definitions
- the invention relates to a computer-implemented method for processing data object variants of at least one software tool for the development of mechatronic systems, wherein the data object variants in particular at least parts of hardware variants and / or software variants of the mechatronic systems correspond and have at least one common feature type and one embodiment of the feature type ,
- the invention also relates to a computerized work environment for manipulating data object variants of at least one software tool.
- Methods for processing data object variants are known from various fields of technical development, primarily from those areas in which the developers involved have to solve programming tasks similar, but in part still varying engineering tasks. This typically occurs when the goal of the development are different product variants, ie products which, in addition to common, identical proportions, also have mutually differing components.
- the mechatronic systems to be developed may be mechanical or electrical systems or systems comprising both mechanical and electrical components. The development of these systems may involve only the development of software for these systems and not the development of the physical systems themselves.
- controllers are usually understood to be robust small computers prepared for industrial use, which usually have integrated I / O interfaces.
- the controllers which are often equipped with a real-time operating system, execute programs which, in the broadest sense, make contact with a technical process to be controlled via the I / O interface and act on this process in the desired manner.
- ECUs takes place in various steps, some of which are executed in different tools, which are usually implemented as software. These steps typically include the architectural design of the system being developed with a software architecture tool, the development of control algorithms, and routing models in graphical or text-based Modeling tools, generation of ready-to-run or near-series program code for one or more ECUs by means of a production code generator, testing of individual developed system components and finally testing of various system components for assembly, testing of the developed controller, whereby the different tests are performed by means of test setup, Test Automation and Test Management tools are created, executed, and supported.
- Model-in-the-Loop MIL
- Software-in-the-Loop SIL
- Processor-in-the-Loop PIL
- Hardware-in-the-Loop HIL
- controllers for engine variants partly have program-implemented functionalities that can be identical in the various control units and are identical, and that on the other hand certain functionalities are implemented differently from one another in order to cope with the different circumstances of the individual engine variants.
- the object of the present invention is to provide a computer-implemented method and a computer-aided working environment for processing data object variants of a software tool with which even during the processing of data object variants to changing correspondences between embodiments of feature types of different data object variants - and thus changing match groups - can be responded ,
- the above-indicated and derived object is achieved by detecting matching features of this feature type in different data object variants for at least one feature type and by storing information on match groups of data object variants for the feature type, ie Information about the data object variants with the matching configurations that form a match group.
- the method according to the invention thus ensures that, when processing data object variants, it is automatically checked whether there are matches between different embodiments of a feature type in different data object variants, wherein the data object variants, the matching embodiments, have been found for the feature type to which matching designs have been found , summarized into match groups and related information get saved.
- an overview is automatically obtained as to which data object variants match in which "equal shares", and consequently also which data object variants differ in which embodiments of feature types.
- the matching configurations of the respective feature type are recorded in the data object variants and for each feature type information on match groups of data object variants are stored, match groups - as before also formed by the data object variants having the matching features of the respective feature type.
- a further improvement of the computer-implemented method is achieved by rechecking at each machining operation of a data object variant, at least with regard to the processed feature type, whether a change of the match groups results.
- current information on match groups is stored by those data object variants with the matching features of the feature type.
- this embodiment of the method results in a continuous and uninterrupted control of the data object variants with regard to the existing and resulting matching groups of data object variants.
- the classification of a feature in matching groups of data object variants thus achieved is always up to date and completely observable.
- the information stored on the respective feature type information to match groups can be configured very different.
- the match group information stored on the feature type is simply stored as a list of identifiers of the data object variants having the matching features of the feature type according to an embodiment of the method.
- the information about matching groups stored for the feature has a link to the included data object variants, so that it is possible to look up the linked data object variant itself, in which the common configuration of Merkmaltyps exists.
- the data object variants include a link to the feature type with the stored information on match groups having the matching features of the feature type.
- the information on matching groups stored for the feature type has the matching features of the feature type itself, so that all information about the matching groups is stored at a central location, namely the feature types that come together in the matching groups and also the matching embodiments of these feature types.
- another data object variant-that is, an existing data object variant is selected as the starting point and the existing information on matching groups of data object variants is automatically supplemented with information about the further data object variant.
- the matching groups which comprise the existing data object variant serving as a starting point are supplemented with information in such a way that these match groups also comprise the further generated data object variants.
- this means that the added data object variant is initially oriented completely to the data object variant serving as the starting point. Deviations from the data object variant serving as a starting point are then defined in retrospect.
- the processing of an existing data object variant is preferably realized by first naming or selecting the data object variant, then automatically determining the matching groups that comprise the data object variant to be processed, and enabling the embodiments of feature types that are to be processed processing data object variant.
- This ensures that, although all embodiments of feature types that belong to the data object variant, are editable, but at the same time it is also ensured that a more extensive change of embodiments of feature types is not possible.
- several variants can be edited at the same time, if this at the beginning to be named the editing; the aforementioned release of embodiments of feature types then takes place for all affected data object variants.
- the invention further relates to a computer program product having a computer program comprising software means for performing the method explained above when the computer program is executed with a computer.
- the previously derived object is achieved in the aforementioned computer-assisted work environment characterized in that at least one feature type matching features of this Merkmaltyps are recorded in different data object variants and that are stored to the feature type information to match groups of data object variants with the matching features of the feature type.
- the computer-assisted work environment is designed in such a way that the previously explained computer-implemented method for processing data object variants can be carried out quite concretely.
- the work environment is implemented within the software tool, but in another advantageous embodiment the work environment is implemented independently of the software tool, wherein preferably the work environment can also access data object variants of several software tools. This is particularly important if in the working environment the data from different software tools - which nevertheless can refer to the same product or the same development object - are managed.
- the various software tools may be a mathematical modeling and simulation environment, code generators, various compilers, or test environments, for example.
- the working environment comprises at least one database, which is designed to store the types of features, the features of the feature type and / or the matching groups.
- the database can also be further configured to store development data of the mechatronic systems to be developed.
- 1 is a schematic representation for explaining data object variants and match groups
- Fig. 2 shows an inventive computer-implemented method for
- FIG. 3 shows the method according to FIG. 2 with embodiments of feature types which are stored together with the match groups for the feature types concerned, FIG.
- Fig. 4 shows the behavior of the method according to FIGS. 2 and 3 when changing the
- Fig. 5 shows the computer-implemented method according to FIGS. 2 to 4 with
- Fig. 6 shows the computer-implemented method according to FIGS. 2 to 5 for
- Fig. 7 shows the computer-implemented method according to FIGS. 2 to 6 for
- Fig. 8 shows the computer-implemented method according to FIGS. 2 to 7 for
- Fig. 1 shows a total of three data object variants VI, V2 and V3.
- Each of the data object variants VI, V2 and V3 contains certain characteristic types and concrete configurations of these feature types, which are not shown here in detail, however.
- the feature types contained in the data object variants VI, V2 and V3 may be unique in their design for a data object variant VI, V2 or V3, but it is also possible for the data object variants VI, V2 and V3 to have common configurations of one feature type or several feature types.
- Fig. 1 below the theoretically only possible coincidences between the three assumed data object variants VI, V2, V3 are illustrated, illustrated by the marked intersections.
- the data object variants VI, V2 and V3 can not have any matches in feature types or in embodiments of feature types, which is illustrated by the outer segments VI, V2 and V3.
- FIGS. 2 to 8 show a computer-implemented method for processing data object variants of at least one software tool and schematically a computer-assisted work environment for processing data object variants of at least one software tool that allow processing of data object variants resulting in a change of match groups, however automatically detected and tracked by changing matchgroups.
- the data object variants VI, V2 and V3 are shown, which have the common feature types A, B, C and D.
- Each of the data object variants VI, V2 and V3 can have special configurations a, b, c, d, the characteristic types A, B, C, D.
- the embodiments of the feature types A, B, C, D are for the data object variant VI as al, bl, cl and dl, for the data object variant V2 as a2, b2, c2 and d2 and for the data object variant V3 as a3, b3, c3 and d3 designated.
- the data object variants VI, V2 and V3 are completely identical in the embodiments for the feature types A and B, that is, that al is identical to a2 is identical to a3, and that bl is identical to b2 identical is with b3.
- the data object variants VI and V2 agree with regard to the feature type C, that is, that cl is identical to c2. With regard to the remaining embodiments of the feature types, there is accordingly no match.
- Characteristics types A, B, C and D in the context of ECU development are typically mathematical models, submodels, functions in symbolic or textual high-level languages, hardware descriptions, test scripts, parameter sets or even individual parameters.
- this feature type are detected in different data object variants VI, V2 and V3 and that the respective feature type A, B, C, D information on matching groups Gl, G2, G3 of data object variants VI, V2, V3 are stored.
- the matching groups G1, G2 and G3 thus contain in each case-in which specific information-technical representation whatsoever-the compilation of those data object variants which, with regard to the feature type A, B, C or D on which they are related, have matching configurations a, b, c , d have.
- the matching group Gl comprises z.
- the information consists only in a list of the data object variants VI, V2, V3 in which the configurations a, b, c, d of the respective feature type A, B, C and D match.
- the matching group Gl with respect to the feature type A, ie G1 (A), therefore comprises information for the matching group the naming of the data object variants VI, V2 and V3.
- the matching group G2 to the feature type C that is, G2 (C)
- G2 (C) includes only the data object variant V3
- the matching group Gl refers to the data object variants VI and V2 in terms of the feature type C, G1 (C), as information on the match group G1 (C) . From the information stored about the matching groups G1, G2 and G3, it is therefore always possible to see how the data object variants VI, V2 and V3 are segmented with respect to their characteristics.
- FIG. 3 shows an embodiment of the method and the working environment in which the information relating to the feature types A, B, C, D for the matching groups G1, G2 and G3 shows the matching configurations a, b, c, d of the feature type A , B, C, D themselves.
- the design c3 is stored for the data object variant V3.
- the embodiment makes - just as well as the embodiment of FIG. 2 - clear that a match group Gl, G2, G3 can consist only of the information to a single data object variant VI, V2, V3.
- FIG. 4 shows the processing of the existing data object variant VI and the result of the application of the method with regard to the adaptation of the matching groups G1 and G2.
- FIG. 4 starting from the data object variants VI, V2 and V3 already shown in FIGS. 2 and 3, the configuration al of the feature type A in the data object variant VI is changed, namely al in al '.
- the method now provides that after this processing operation of the data object variant VI, at least as regards the processed feature type A, it is again checked whether a change of the matching groups G1 and G2 results. In the event of a change to this feature type A current and updated information on the matching groups Gl and G2 of the data object variants are stored with the matching features of the feature type A.
- the change of the embodiment al to the design al 'of the feature type A in the data object variant VI results in a new match group G2 (A) to the feature type A, whereas the feature group G1 (A) is reduced in content regarding the feature type A. namely, the only information about the data object variant VI.
- the matching group G2 (A) contains information about the data object variants V2 and V3, since they have identical configurations a2 and a3 according to the assumption.
- the information in the matching groups G1, G2, G3 no longer consists of a list of identifiers of the data object variants VI, V2, V3, but the information respectively includes a link L to the data object variants VI, V2, V3, so that via the links L (V1), L (V2) and L (V3) from each match group G can be jumped directly to the relevant data object variants VI, V2, V3.
- FIG. 6 illustrates how a further, new data object variant V4 is added to the existing data object variants VI, V2, V3.
- the generation of the further data object variant V4 takes place in that an existing data object variant, here the data object variant VI, is selected as starting point and the existing information shown in FIG. 6 below for the matching groups G1, G2, G3 of data object variants, ie the existing data object variants VI, V2, V3, to supplement information about the further data object variant V4.
- the matching groups in this case all matching groups under G1, that is, G1 (A), G1 (B), G1 (C), and G1 (D), which comprise the existing data point variant VI serving as the starting point, thus containing information be supplemented that these match groups Gl also include the other generated data object variant V4.
- the matching groups have been supplemented under Gl with the identifier V4 of the further data object variant V4.
- the existing data object variant which is most similar to the future data object variant to be generated and therefore has the most matching features is generally used.
- FIG. 7 shows the processing of the existing data object variant V2.
- the data object variant V2 is initially named, which is symbolized in FIG. 2 by the border of the identifier "V2".
- the match groups comprising the data object variant to be processed are determined, in the present case the match groups G1 (A), G1 (B), G1 (C) and G2 (D) are.
- the embodiments of the feature types A, B, C, D are then released for processing, which belong to the data object variant V2 to be processed; In the case illustrated, these are the embodiments a1, b1, c1 and d2.
- Copies of all embodiments a, b, c, d are generated for editing, which are assigned to more than one data object variant V.
- Working with the above-described copies makes sense in general terms, in particular it makes sense if the matching group G belonging to this feature type A, B, C, D comprises more than the data object variant V2 to be processed.
- copies of the embodiments a1, b1, c1 are made, which are designated as copy (a1), copy (b1) and copy (c1). Since the embodiment d2 in the matching group G2 (D) does not contain multiple data object variants, it is not necessary to work with a copy of the design d2.
- FIG. 8 illustrates the procedure of the computer-implemented method and the computer-assisted working environment for the case in which the embodiment a, b, c, d of a feature type A, B, C, D of a first data object variant is transferred to a further data object variant.
- the design cl of the data object variant VI is to be transferred to the data object variant V3. This is done by selecting the embodiment cl to be transmitted of the feature type C of the first data object variant VI - indicated by the box around the design cl - and by selecting the further data object variant - in the exemplary embodiment indirectly by the outline of the design c3 of the data object variant V3 he follows.
- the matching group G1 (C), which comprises the first data object variant VI is supplemented by the further data object variant V3.
- the data object variant V3 in the match group G1 (C) is now additionally named.
- this further data object variant V3 is deleted so that the data object variant G2 (C) is resolved.
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/794,331 US9766882B2 (en) | 2015-07-08 | 2015-07-08 | Computer-implemented method for editing data object variants |
PCT/EP2016/065956 WO2017005783A1 (en) | 2015-07-08 | 2016-07-06 | Computer-implemented method for processing data object variants |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3320431A1 true EP3320431A1 (en) | 2018-05-16 |
Family
ID=56409068
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP16738099.7A Ceased EP3320431A1 (en) | 2015-07-08 | 2016-07-06 | Computer-implemented method for processing data object variants |
Country Status (5)
Country | Link |
---|---|
US (2) | US9766882B2 (en) |
EP (1) | EP3320431A1 (en) |
CN (1) | CN107710154A (en) |
DE (1) | DE112016003079A5 (en) |
WO (1) | WO2017005783A1 (en) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9766882B2 (en) * | 2015-07-08 | 2017-09-19 | Dspace Digital Signal Processing And Control Engineering Gmbh | Computer-implemented method for editing data object variants |
KR20200112386A (en) * | 2019-03-22 | 2020-10-05 | 삼성전자주식회사 | Electronic device and control method thereof |
US11243760B2 (en) * | 2019-07-24 | 2022-02-08 | Sap Se | Automated generation and consistency checking of software objects |
GB201917084D0 (en) * | 2019-11-22 | 2020-01-08 | Platinum Training Services Ltd | A checking system |
US11829689B1 (en) * | 2020-06-09 | 2023-11-28 | The Mathworks, Inc. | Systems and methods for creating variant regions in acausal simulation models |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7742903B2 (en) * | 2004-06-15 | 2010-06-22 | The Mathworks, Inc. | Variants in graphical modeling environments |
US10140387B2 (en) * | 2005-08-02 | 2018-11-27 | The Boeing Company | Model for managing variations in a product structure for a product |
DE102006044141A1 (en) * | 2006-09-15 | 2008-04-03 | Dspace Digital Signal Processing And Control Engineering Gmbh | Device and method for configuring a control system |
EP2330469B1 (en) * | 2009-12-03 | 2012-10-31 | dspace digital signal processing and control engineering GmbH | Method and development environment for generating an executable total control program |
DE102011082838A1 (en) | 2011-09-16 | 2013-03-21 | Siemens Aktiengesellschaft | Identification of reusable mechatronic components in factory automation |
DE102011054217A1 (en) * | 2011-10-06 | 2013-04-11 | Dspace Digital Signal Processing And Control Engineering Gmbh | Method for real-time testing of a control unit for an internal combustion engine with a simulator |
EP2706421B1 (en) * | 2012-09-11 | 2015-05-27 | dSPACE digital signal processing and control engineering GmbH | Method for the computer-controlled generation of at least a portion of an executable control program |
EP2759964A1 (en) | 2013-01-29 | 2014-07-30 | dSPACE digital signal processing and control engineering GmbH | Computer-implemented method for data management of product variants in the development of control devices |
US8924193B2 (en) | 2013-03-14 | 2014-12-30 | The Mathworks, Inc. | Generating variants from file differences |
CN103970547A (en) * | 2014-05-28 | 2014-08-06 | 北京经纬恒润科技有限公司 | Variable generating method and device as well as data processing method and device |
CN104317993B (en) * | 2014-10-16 | 2018-08-17 | 哈尔滨工程大学 | A kind of ship craft integrated electrical propulsion dummy emulation platform |
CN104537178B (en) * | 2014-12-31 | 2017-10-13 | 南京邮电大学 | A kind of power system associative simulation modeling method based on Matlab and Netlogo |
US9766882B2 (en) * | 2015-07-08 | 2017-09-19 | Dspace Digital Signal Processing And Control Engineering Gmbh | Computer-implemented method for editing data object variants |
-
2015
- 2015-07-08 US US14/794,331 patent/US9766882B2/en not_active Expired - Fee Related
-
2016
- 2016-07-06 CN CN201680039799.2A patent/CN107710154A/en active Pending
- 2016-07-06 WO PCT/EP2016/065956 patent/WO2017005783A1/en active Application Filing
- 2016-07-06 DE DE112016003079.7T patent/DE112016003079A5/en active Pending
- 2016-07-06 EP EP16738099.7A patent/EP3320431A1/en not_active Ceased
-
2017
- 2017-08-28 US US15/687,870 patent/US10452389B2/en active Active
Also Published As
Publication number | Publication date |
---|---|
DE112016003079A5 (en) | 2018-05-24 |
US9766882B2 (en) | 2017-09-19 |
US20170357503A1 (en) | 2017-12-14 |
US20170010887A1 (en) | 2017-01-12 |
WO2017005783A1 (en) | 2017-01-12 |
CN107710154A (en) | 2018-02-16 |
US10452389B2 (en) | 2019-10-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1330685B1 (en) | Testing method and testing device for starting up systems which are controlled by means of a program logic | |
EP2801872B1 (en) | Test device for testing a virtual control device | |
EP3320431A1 (en) | Computer-implemented method for processing data object variants | |
DE102005026040A1 (en) | Parameterization of a simulation working model | |
EP2009525A1 (en) | Test device and method for testing at least one electronic control system | |
EP2330469B1 (en) | Method and development environment for generating an executable total control program | |
EP2266066A1 (en) | Method and system for identification of grouping characteristics | |
DE102017120016A1 (en) | A method of configuring a test device set up to test an electronic controller and a configuration system | |
EP2706421A1 (en) | Method for the computer-controlled generation of at least a portion of an executable control program | |
EP1947568A1 (en) | Method for observing a control device | |
EP3629108B1 (en) | Planning of an automation system | |
EP3699704B1 (en) | System and method for validating system requirements of cyber-physical systems | |
EP1950635B1 (en) | Method for operating an automation system | |
WO2014154281A1 (en) | Object-based configuration of a process and/or production installation | |
DE102020119853B3 (en) | Method for controlling an automation system with visualization of program objects of a control program of the automation system and automation system | |
EP2191338B1 (en) | System for writing a simulation program | |
EP2990941B1 (en) | Computer-implemented method for generating a control device program codes and related report management environment | |
WO2008113305A1 (en) | Device for generating machining programs for a machine tool | |
EP2811352A1 (en) | Method for processing an automation project by a plurality of processing stations | |
EP2194457B1 (en) | Device for creating a marked reference data stream | |
AT522186B1 (en) | Computer-implemented method for the computer-aided generation of an executable control program for controlling and / or regulating a technical process | |
DE102013010783A1 (en) | Method and control device for testing an automation solution based on a PLC control | |
EP3803522B1 (en) | Method for producing or machining a product and control device for controlling a production system | |
DE102008004923B4 (en) | Method for updating a control sequence of a machine control system and device for carrying out the method | |
DE102021133935A1 (en) | Parameterization and/or configuration technique for a device based on a programmable logic controller |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
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: 20180208 |
|
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: 20190116 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
RAP3 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: DSPACE GMBH |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R003 |
|
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: 20220221 |