EP1810145A1 - Verfahren und vorrichtung zur synchronisierung in einem mehrprozessorsystem - Google Patents
Verfahren und vorrichtung zur synchronisierung in einem mehrprozessorsystemInfo
- Publication number
- EP1810145A1 EP1810145A1 EP05797084A EP05797084A EP1810145A1 EP 1810145 A1 EP1810145 A1 EP 1810145A1 EP 05797084 A EP05797084 A EP 05797084A EP 05797084 A EP05797084 A EP 05797084A EP 1810145 A1 EP1810145 A1 EP 1810145A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- processor
- synchronization
- signal
- mode
- processors
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 230000001960 triggered effect Effects 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 3
- 238000001514 detection method Methods 0.000 description 14
- 230000001360 synchronised effect Effects 0.000 description 8
- 238000013500 data storage Methods 0.000 description 6
- 230000003111 delayed effect Effects 0.000 description 4
- 102100040844 Dual specificity protein kinase CLK2 Human genes 0.000 description 2
- 101000749291 Homo sapiens Dual specificity protein kinase CLK2 Proteins 0.000 description 2
- 230000001934 delay Effects 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000000630 rising effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000000926 separation method Methods 0.000 description 2
- 241000761456 Nops Species 0.000 description 1
- 230000001427 coherent effect Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 238000012913 prioritisation Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
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/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/30181—Instruction operation extension or modification
-
- 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/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/30181—Instruction operation extension or modification
- G06F9/30189—Instruction operation extension or modification according to execution mode, e.g. mode flag
-
- 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/46—Multiprogramming arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/1629—Error detection by comparing the output of redundant processing systems
- G06F11/1641—Error detection by comparing the output of redundant processing systems where the comparison is not performed by the redundant processing components
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/1695—Error detection or correction of the data by redundancy in hardware which are operating with time diversity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/16—Protection against loss of memory contents
-
- 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/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/38—Concurrent instruction execution, e.g. pipeline or look ahead
- G06F9/3836—Instruction issuing, e.g. dynamic instruction scheduling or out of order instruction execution
- G06F9/3851—Instruction issuing, e.g. dynamic instruction scheduling or out of order instruction execution from multiple instruction streams, e.g. multistreaming
-
- 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/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/38—Concurrent instruction execution, e.g. pipeline or look ahead
- G06F9/3885—Concurrent instruction execution, e.g. pipeline or look ahead using a plurality of independent parallel functional units
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/845—Systems in which the redundancy can be transformed in increased performance
Definitions
- dual-computer systems or dual-processor systems are today's computer systems for safety-critical applications, in particular in vehicles such as antilock braking systems, electronic stability program (ESP), X-by-wire systems such as drive-by-wire or steer-by-wire as well as break-by-wire, etc. or other networked systems.
- ESP electronic stability program
- X-by-wire systems such as drive-by-wire or steer-by-wire as well as break-by-wire, etc. or other networked systems.
- powerful error mechanisms and error handling mechanisms are required, in particular to counteract transient errors that arise, for example, in miniaturization of the semiconductor structures of the computer systems. It is relatively difficult to protect the core itself, so the processor.
- One solution to this is, as mentioned, the use of a dual-computer system or dual core system for fault detection.
- Such processor units with at least two integrated execution units are thus known as dual-core or multi-core architectures.
- dual-core or multi-core architectures are proposed according to the current state of the art mainly for two reasons: On the one hand, an increase in performance, ie a performance increase, can be achieved by considering and treating the two execution units or cores as two arithmetic units on a semiconductor component. In this configuration, the two execution units or cores process different programs or tasks. As a result, an increase in performance can be achieved, which is why this configuration is referred to as a power mode or performance mode.
- the second reason to implement a dual-core or multi-core architecture is an increase in security by the redundancy of the two execution units
- Execute program The results of the two execution units or CPUs, ie cores, are compared and an error can be recognized in the comparison for consistency.
- this configuration is referred to as safety mode or safety mode or error detection mode.
- the object of the invention is now to present a unit and a method which supplies the instructions / data to the at least two processors or cores redundantly or differently depending on the mode and in particular divides the memory access rights in the performance mode, the synchronization and / or desynchronization of the two processors or enable cores during a mode change.
- Such a unit is not yet known. It enables the effective operation of a two-processor system so that the two modes of safety and performance can be switched during operation.
- processors will be discussed below, which also includes cores or computing units conceptually.
- the synchronization can be clock-accurate and clock-synchronized by the presented method, but there may also be applications in which such an exact synchronization is not required. Then this method can also be used to achieve a "loose" synchronization: a loose synchronization is a synchronization in which the two
- processors process the same, but the time interval of the processing can vary in a given by the comparator frame.
- a dual-processor system there are 2 processors that can handle the same or different tasks. These two processors of the dual-computer system can execute these tasks isochrone- or off-clock.
- the invention also shows a method and a device in which the switchover is triggered by a signal.
- This can be generated, for example, by observing the command bus (see if the switch request is executed) or a control signal of the decoder (eg triggering an interrupt, writing to a register, ... in the other processor) and thereby the processor to the default Program address jumps.
- the two processors may suitably jump to different program locations due to an identifier, ie ID, which is unique for each processor in the multiprocessor system and thus desychronized (important: processor identification by a processorID bit, conditional jump, readout of processorld bit from a memory area separate for each processor but with the same address, processor-bit stored in internal processor register).
- ID an identifier
- the invention discloses a method and a device for synchronization in a multiprocessor system having at least two processors, wherein switching means are provided by which can be switched between at least two operating modes, wherein the device is configured such that a synchronization is performed by a stop signal, which Pre-processor stops to synchronize with the at least second processor.
- the synchronization can be accomplished by notifying a switch request of at least one processor (e.g., triggering an interrupt, writing to a register, ... the other processor) and thereby causing the processor to jump to a predetermined program address.
- processor e.g., triggering an interrupt, writing to a register, ... the other processor
- the invention also shows a data distribution unit of at least one
- switching means ModeSwitch
- the unit is configured such that the data distribution and / or the data source (in particular Instr.Speicher, data memory , Cache) is dependent on the mode of operation.
- the first operating mode corresponds to a safety mode, in which the two arithmetic units execute the same programs and / or data and comparison means are provided, which are the ones resulting from the processing of the same programs
- the erf ⁇ ndungswashe unit or the inventive method allows the implementation of the two modes in a two-processor system. If the two processors operate in error detection mode (F mode), the two processors receive the same data / instructions and operate in performance mode (P mode), so each processor can access the memory. Then this unit manages the accesses to the only simply existing memory or peripherals.
- F mode error detection mode
- P mode performance mode
- the unit takes over the data / addresses of a processor (called master here) and forwards them to the components such as memory, bus, etc.
- the second processor here slave
- the data distribution unit accepts this at a second port, but does not forward the request to the others
- the data distribution unit gives the slave the same data as the master and compares the data of the two processors. If these are different, this indicates the data distribution unit (here DVE) by an error signal.
- DVE data distribution unit
- the two processors work on different parts of the program.
- the memory accesses are thus also different.
- the DVE thus accepts the request from the processors and returns the results / requested data to the processor that requested them.
- one processor is placed in a wait state until the other has been serviced.
- the switching between the two modes and thus the different operation of the data distribution unit is effected by a control signal. This can either be generated by one of the two processors or externally.
- the DVE unit delays the data for the slave accordingly or stores the output data of the master until it matches the output data of the master
- Slave can be compared for error detection.
- FIG. 1 shows a dual-computer system with a first computer 100, in particular one
- the Whole system is operated with a predetermined clock or in predetermined clock cycles (clock cycle) CLK.
- CLK clock cycles
- the clock is supplied to this.
- a special feature for error detection is also included by way of example, in which namely the first computer 100 and the second
- Calculator 101 with a time offset in particular a predetermined time offset or a predetermined clock offset work.
- any time can be predetermined for a time offset and also any desired clock with respect to an offset of the clock cycles. This can be an integer offset of the clock cycle, but just as shown in this example, for example, an offset of 1.5
- this system is just designed, for example, to operate in a predetermined time offset or clock cycle offset, in particular here 1.5 clock cycles, ie during the one computer, z. B.
- computer 100 directly the components, in particular the external components 103 and 104 responds, the second computer 101 operates with a delay of exactly 1.5 clock cycles to do so.
- computer 101 is fed with the inverted clock, that is to say the inverted clock at the clock input CLK2.
- Address bus 117A is connected to computer 100 via a command address connection IA1 (instruction address 1) and to computer 101 via an instruction address connection IA2 (instruction address 2).
- the instructions themselves are transmitted via the sub-command bus 117B, which is connected to computer 100 via a command terminal II (Instruction 1) and to computer 101 via a command terminal 12 (Instruction 2).
- IA1 instruction address 1
- IA2 instruction address 2
- the instructions themselves are transmitted via the sub-command bus 117B, which is connected to computer 100 via a command terminal II (Instruction 1) and to computer 101 via a command terminal 12 (Instruction 2).
- Command bus 117 consisting of 117A and 117B is a component 103, e.g. B. an instruction memory, in particular a secure instruction memory or the like interposed. This component, in particular as a command memory is operated in this example with the clock CLK.
- a data bus is shown at 116, which is a data address bus or a data address line 116A and a
- Data bus or a data line 116B contains.
- 116A that is to say the data address line, is connected to the computer 100 via a data address connection DA1 (data address 1) and to the computer 101 via a data address connection DA2 (data address 2).
- DA1 data address 1
- DA2 data address 2
- DO1 Data Out 1
- DO2 Data Out 2
- the data bus 116C which is connected to computer 100 or computer 101 via a data connection Dil (Data In 1) and a data connection DI2 (Data In 2), also belongs to data bus 116.
- a component 104 is interposed, for example a data memory, in particular a secure data memory o. ⁇ . This component 104 is also supplied with the clock CLK in this example.
- the components 103 and 104 are representative of any components which are connected via a data bus and / or command bus to the computers of the dual-computer system and corresponding to the accesses via data and / or commands of the dual-processor system with respect to write operations and / or read operations erroneous data and / or commands receive or give away.
- error detection generators 105, 106 and 107 are provided for error prevention which error detection generate such as a parity bit or other error code such as an error correction code, so ECC, o. ⁇ ..
- ECC error correction code
- Also provided for this purpose are the corresponding Starbucksungsprüf healthyen or check devices 108 and 109 for checking the respective misdetection so for example, the parity bit or other error code such as ECC.
- a delay unit 102 is now connected as shown in the lines of the data bus and / or in the command bus. Because of
- Clarity is shown only the involvement in the data bus. Of course, this is just as possible and imaginable with regard to the command bus.
- This delay unit 102 or the delay unit delays the accesses, here in particular the memory accesses, in such a way that a possible time or clock offset is compensated, in particular in the event of an error detection, for example via the comparators 110 and
- the error signal is generated in the dual-computer system, that is, the error detection is performed in the dual-computer system.
- Different variants can be implemented: Delay the write and read operations, delay only the write operations, or, although not preferred, delay the read operations. It can be converted by a change signal, in particular the error signal, a delayed write operation in a read operation to prevent erroneous writing.
- DVE data distribution unit
- IllOpDetect Switching between the two modes is detected by the "Switch-Detect" units located between the cache and the processor on the instruction bus and looking to load the IUOp command into the processor. so this event is communicated to the Modeswitch unit.
- the Switch-Detect unit is unique to each processor, and the Switch-Detect unit does not need to be fault-tolerant because it is duplicated and redundant. On the other hand, it is conceivable to perform this unit fault-tolerant and thus singular, but preferred is the redundant design.
- ModeSwitch Switching between the two modes is triggered by the "Switch-Detect" unit.If switching from Lock to Split mode, both "Switch-Detect” units will detect switching as both processors are the same Execute program code in Lock mode. The "Switch-Detect” unit of the processor 1 detects this 1.5 clocks before the "Switch-Detect” unit of the processor 2.
- the "Modeswitch” unit holds the processor 1 by 2 with the help of the wait signal
- the processor 2 is also stopped 1.5 clocks later, but only half a clock so that it is synchronized to the system clock, then the status signal is switched to split for the other components and the two processors continue to work If the two processors now perform different tasks, they must diverge in program code, by having read access to the processor ID immediately after switching to split mode This read processor ID is different for each of the two processors compared to a desired processor ID, then with a Conditional Jump command the appropriate processor to a other program site be brought. When switching from split mode to lock mode, a processor will notice this, or one of them first. This processor will execute program code containing the switchover command. This is now registered by the "Switch-Detect" unit and communicates this to the Modeswitch unit, which stops the corresponding processor and shares the second one
- Desired synchronization by an interrupt with The second processor receives an interrupt and can now execute a software routine to complete its task. Now he also jumps to the program location where the changeover command is located. His "Switch-Detect" unit now also signals the desire to change mode to the Modeswitch unit. The Wait signal for the processor 1 is now deactivated for the next rising system clock edge and 1.5 clocks later for the processor 2. Both now work again synchronous with a clock offset of 1.5 clocks.
- Mode this can be detected by an external watchdog.
- the watchdog Upon a trigger signal for each processor, the watchdog notices that the waiting processor is no longer reporting. If there is only one watchdog signal for the processor system, then the triggering of the watchdog must only take place in lock mode. Thus, the watchdog would recognize that the mode switch did not occur.
- the mode signal is available as a dual-rail signal. Where "UO" is the lock mode and " ⁇ 01" is the split mode. Errors have occurred with "W and" ⁇ 11 "'.
- IramControl Access to the instruction memory of the two processors is via the
- IRAM Control Controlled by IRAM Control. This must be designed securely because it is a single point of failure. It consists of two state machines for each processor, ie one isochronous iramlclkreset and one asynchronous readiraml. In safety-critical mode, the state machines of the two processors monitor each other and in performance mode, they work separately. The reloading of the two caches of the processors are controlled by 2 state machines. A synchronous state machine iramclkreset and an asynchronous readiram. These two state car offices also distribute the memory accesses in split mode. Here processor 1 has the higher priority. After a access to the main memory by processor 1 gets now - if both processors want to access the main memory again ⁇ processor2 assigned the memory access permission. These two state machines are implemented for each processor. In lock mode, the output signals of the machines are compared to detect any errors.
- the data for updating the cache 2 in lock mode are delayed by 1.5 cycles in the IRAM control unit.
- This register is mirrored in the memory area with the address 65528.
- the program counter of the processor 1 is delayed by 1.5 clocks to be compared in lock mode with the program counter of the processor 2 can.
- the caches of the two processors can be reloaded differently.
- the two caches are not coherent.
- the two processors can diverge and the comparators thus signal an error.
- a flag table is set up in the IRAM Control. In this is noted whether a cache line in
- Lock or split mode was written.
- lock mode the cache line entry value is set to 0 on a cache line reload, and in split mode, even if the cache line is cached from a single cache, to 1. If the processor now executes a memory access in lock mode, then becomes checks if this cache line has been updated in lock mode, ie is the same in both caches. in the
- DramControl In this component, the parity is formed for each of the address, data, and memory control signals from each processor.
- Processor 1 coordinates the memory accesses.
- the state in split mode is again subdivided into 7 states, which are the
- processor 1 has locked the data store. If processor 2 wants to access the memory in this state, it is stopped by a wait signal until processor 1 releases the data memory again.
- ⁇ - Core2 ⁇ _Lock Is the same state as the previous one except that now processor 2 has locked the data memory and processor 1 is stopped during data storage operations.
- processor 2 gets the memory pre-reserved. In the case of normal memory access without locks, processor 2 can access processor 1 before processor 1 if processor 1 was in front of it.
- Memory access of processor 1 The memory is not locked in this case. Processor 1 is allowed to access the data store. If he wants to lock him, he can do so in this condition.
- the DVE consists of the detection of the changeover request (IUOPDetect) of the ModeSwitch unit and the Iram and DramControl.
- the switching of the two processors is triggered here by way of example by the command IHOp in the program.
- each processor can be uniquely identified.
- a number is assigned to each processor.
- one core is 1 and the other is 0. This is encoded in the processor status register.
- the two processors are stopped here for synchronization by the wait command.
- the clock for the processor to be paused may be stopped (by, for example, an OR with o to pause and 1 to continue clocking).
- Switching between the two modes is detected by the units “Switch-Detect” which is located between the cache and the Processor on the instruction bus and see if the command IHOp is loaded into the processor. If the command is detected, this event is communicated to the Modeswitch unit. This detection is signaled by the "Core 1 signal” or “Core 2 signal” (see Figure 2) of the "Mode-Switch” unit.
- the “Switch-Detect” unit is available for each processor individually. Detect “does not have to be fault-tolerant since it is duplicated and therefore redundant.
- Mode-Switch Switching between the two modes is triggered by the "Switch-Detect” unit If switching from the Lock to the Split mode, both "Switch-Detect” units detect the changeover as both
- Processors execute the same program code in lock mode.
- the "Switch-Detect” unit of the processor 1 detects this 1.5 clocks before the "Switch-Detect” unit of the processor 2.
- the "Modeswitch” unit stops the processor 1 by 2 clocks with the help of the wait signal.
- the processor 2 is also stopped 1.5 clocks later, but only by half a clock to be synchronized to the system clock.
- the status signal is switched to split for the other components and the two processors continue to work.
- the two processors In order for the two processors to perform different tasks, they must diverge in the program code. This is done by reading the processor ID directly after switching to split mode. This read processor ID is for each of the two processors.
- the address of the status register in which the processor ID is stored is first written in rl LDL r 1,248 LDH r 1,255, followed by separation of the two processors by IUOp command error
- Test bit at 5th digit of the status register If it is 0, then it is processor 1 and 1 is processor 2 BTEST r2,5 by a conditional jump is now brought processor 2 to another program point JMPI CT 10
- both "Switch-Detect" units must tell the Modeswitch unit that they want to be in Split mode. If the changeover request is made by only one unit, the error is recognized by the comparison units, since these continue to receive data from one of the two processors and these do not match the stopped processor.
- the two processors are in split mode and one does not switch back to lock mode, this can be detected by an external watchdog.
- the watchdog Upon a trigger signal for each processor, the watchdog notices that the waiting processor is no longer reporting. If there is only one watchdog signal for the processor system, then the triggering of the watchdog must only take place in lock mode.
- Watchdog detect that the mode switch was not made.
- the mode signal is available as a dual-rail signal (in Figure 2 it is called status). Where “10” stands for lock mode and "01" for split mode. Errors have occurred with “00" and "11". Since the switch command is detected at the beginning of the pipeline of the processor, there must be no jumps in the pipeline stages after detection. The easiest way to prevent this is to introduce two NOps before the IHOp command.
- the core of the invention is, as stated above, the general mode of operation of the mode
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Multimedia (AREA)
- Hardware Redundancy (AREA)
- Multi Processors (AREA)
- Synchronisation In Digital Transmission Systems (AREA)
- Debugging And Monitoring (AREA)
- Techniques For Improving Reliability Of Storages (AREA)
Abstract
Description
Claims
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE200410051950 DE102004051950A1 (de) | 2004-10-25 | 2004-10-25 | Verfahren und Vorrichtung zur Taktumschaltung bei einem Mehrprozessorsystem |
DE200410051952 DE102004051952A1 (de) | 2004-10-25 | 2004-10-25 | Verfahren zur Datenverteilung und Datenverteilungseinheit in einem Mehrprozessorsystem |
DE200410051992 DE102004051992A1 (de) | 2004-10-25 | 2004-10-25 | Verfahren und Vorrichtung zur Verzögerung von Zugriffen auf Daten und/oder Befehle eines Mehrprozessorsystems |
DE200410051937 DE102004051937A1 (de) | 2004-10-25 | 2004-10-25 | Verfahren und Vorrichtung zur Synchronisierung in einem Mehrprozessorsystem |
DE200410051964 DE102004051964A1 (de) | 2004-10-25 | 2004-10-25 | Verfahren und Vorrichtung zur Überwachung einer Speichereinheit in einem Mehrprozessorsystem |
PCT/EP2005/055537 WO2006045800A1 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur synchronisierung in einem mehrprozessorsystem |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1810145A1 true EP1810145A1 (de) | 2007-07-25 |
EP1810145B1 EP1810145B1 (de) | 2008-09-03 |
Family
ID=35677569
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP05801268A Ceased EP1807761A1 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur datenverteilung aus wenigstens einer datenquelle in einem mehrprozessorsystem |
EP05811107A Withdrawn EP1820102A2 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur taktumschaltung bei einem mehrprozessorsystem |
EP05811008A Ceased EP1812861A1 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur verzögerung von zugriffen auf daten und/oder befehle eines mehrprozessorsystems |
EP05801543A Not-in-force EP1807763B1 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur überwachung einer speichereinheit in einem mehrprozessorsystem |
EP05797084A Active EP1810145B1 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur synchronisierung in einem mehrprozessorsystem |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP05801268A Ceased EP1807761A1 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur datenverteilung aus wenigstens einer datenquelle in einem mehrprozessorsystem |
EP05811107A Withdrawn EP1820102A2 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur taktumschaltung bei einem mehrprozessorsystem |
EP05811008A Ceased EP1812861A1 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur verzögerung von zugriffen auf daten und/oder befehle eines mehrprozessorsystems |
EP05801543A Not-in-force EP1807763B1 (de) | 2004-10-25 | 2005-10-25 | Verfahren und vorrichtung zur überwachung einer speichereinheit in einem mehrprozessorsystem |
Country Status (8)
Country | Link |
---|---|
US (4) | US20080126718A1 (de) |
EP (5) | EP1807761A1 (de) |
JP (5) | JP2008518312A (de) |
KR (4) | KR20070067168A (de) |
AT (2) | ATE407398T1 (de) |
DE (2) | DE502005005284D1 (de) |
RU (1) | RU2007119316A (de) |
WO (5) | WO2006045798A1 (de) |
Families Citing this family (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7882379B2 (en) * | 2006-09-22 | 2011-02-01 | Sony Computer Entertainment Inc. | Power consumption reduction in a multiprocessor system |
US20080244305A1 (en) * | 2007-03-30 | 2008-10-02 | Texas Instruments Deutschland, Gmbh | Delayed lock-step cpu compare |
DE102007063291A1 (de) * | 2007-12-27 | 2009-07-02 | Robert Bosch Gmbh | Sicherheitssteuerung |
JP4633134B2 (ja) * | 2008-03-27 | 2011-02-16 | ルネサスエレクトロニクス株式会社 | マイクロコントローラ、制御システム及びマイクロコントローラの設計方法 |
US7941698B1 (en) * | 2008-04-30 | 2011-05-10 | Hewlett-Packard Development Company, L.P. | Selective availability in processor systems |
JP2010198131A (ja) * | 2009-02-23 | 2010-09-09 | Renesas Electronics Corp | プロセッサシステム、及びプロセッサシステムの動作モード切り替え方法 |
US8275977B2 (en) * | 2009-04-08 | 2012-09-25 | Freescale Semiconductor, Inc. | Debug signaling in a multiple processor data processing system |
US8295287B2 (en) * | 2010-01-27 | 2012-10-23 | National Instruments Corporation | Network traffic shaping for reducing bus jitter on a real time controller |
US8954714B2 (en) * | 2010-02-01 | 2015-02-10 | Altera Corporation | Processor with cycle offsets and delay lines to allow scheduling of instructions through time |
US9052887B2 (en) | 2010-02-16 | 2015-06-09 | Freescale Semiconductor, Inc. | Fault tolerance of data processing steps operating in either a parallel operation mode or a non-synchronous redundant operation mode |
KR101664108B1 (ko) | 2010-04-13 | 2016-10-11 | 삼성전자주식회사 | 멀티 코어의 동기화를 효율적으로 처리하기 위한 하드웨어 가속 장치 및 방법 |
JP5718600B2 (ja) * | 2010-09-10 | 2015-05-13 | 日本電気通信システム株式会社 | 情報処理システム、および、情報処理方法 |
US8683251B2 (en) | 2010-10-15 | 2014-03-25 | International Business Machines Corporation | Determining redundancy of power feeds connecting a server to a power supply |
JP5796311B2 (ja) * | 2011-03-15 | 2015-10-21 | オムロン株式会社 | 制御装置およびシステムプログラム |
JP5679047B2 (ja) | 2011-04-18 | 2015-03-04 | 富士通株式会社 | スレッド処理方法、およびスレッド処理システム |
US9086977B2 (en) * | 2011-04-19 | 2015-07-21 | Freescale Semiconductor, Inc. | Cache memory with dynamic lockstep support |
WO2014080245A1 (en) | 2012-11-22 | 2014-05-30 | Freescale Semiconductor, Inc. | Data processing device, method of execution error detection and integrated circuit |
US9429981B2 (en) * | 2013-03-05 | 2016-08-30 | St-Ericsson Sa | CPU current ripple and OCV effect mitigation |
US9823983B2 (en) | 2014-09-25 | 2017-11-21 | Nxp Usa, Inc. | Electronic fault detection unit |
WO2016087175A1 (de) * | 2014-12-01 | 2016-06-09 | Continental Teves Ag & Co. Ohg | Rechensystem für ein kraftfahrzeugsystem |
JP6516097B2 (ja) * | 2015-06-11 | 2019-05-22 | 大日本印刷株式会社 | 演算装置、icカード、演算方法、及び演算処理プログラム |
JP2019061392A (ja) | 2017-09-26 | 2019-04-18 | ルネサスエレクトロニクス株式会社 | マイクロコントローラ及びマイクロコントローラの制御方法 |
US10642826B1 (en) | 2018-08-30 | 2020-05-05 | Gravic, Inc. | Mixed-mode method for combining active/active and validation architectures utilizing a check integrity module |
US11269799B2 (en) * | 2019-05-03 | 2022-03-08 | Arm Limited | Cluster of processing elements having split mode and lock mode |
US11899547B2 (en) * | 2021-11-30 | 2024-02-13 | Mellanox Technologies, Ltd. | Transaction based fault tolerant computing system |
US12032460B2 (en) * | 2022-02-11 | 2024-07-09 | Stmicroelectronics S.R.L. | Systems and methods to test an asynchronous finite machine |
Family Cites Families (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE1269827B (de) * | 1965-09-09 | 1968-06-06 | Siemens Ag | Verfahren und Zusatzeinrichtung zur Synchronisierung von parallel arbeitenden Datenverarbeitungsanlagen |
US3783250A (en) * | 1972-02-25 | 1974-01-01 | Nasa | Adaptive voting computer system |
US4823256A (en) * | 1984-06-22 | 1989-04-18 | American Telephone And Telegraph Company, At&T Bell Laboratories | Reconfigurable dual processor system |
AU616213B2 (en) * | 1987-11-09 | 1991-10-24 | Tandem Computers Incorporated | Method and apparatus for synchronizing a plurality of processors |
US6038584A (en) * | 1989-11-17 | 2000-03-14 | Texas Instruments Incorporated | Synchronized MIMD multi-processing system and method of operation |
US5226152A (en) * | 1990-12-07 | 1993-07-06 | Motorola, Inc. | Functional lockstep arrangement for redundant processors |
DE4104114C2 (de) * | 1991-02-11 | 2000-06-08 | Siemens Ag | Redundantes Datenverarbeitungssystem |
JPH05128080A (ja) * | 1991-10-14 | 1993-05-25 | Mitsubishi Electric Corp | 情報処理装置 |
US5751932A (en) * | 1992-12-17 | 1998-05-12 | Tandem Computers Incorporated | Fail-fast, fail-functional, fault-tolerant multiprocessor system |
JPH07121483A (ja) * | 1993-10-28 | 1995-05-12 | Nec Eng Ltd | 共有メモリアクセス制御回路 |
US5758132A (en) | 1995-03-29 | 1998-05-26 | Telefonaktiebolaget Lm Ericsson | Clock control system and method using circuitry operating at lower clock frequency for selecting and synchronizing the switching of higher frequency clock signals |
CA2178440A1 (en) * | 1995-06-07 | 1996-12-08 | Robert W. Horst | Fail-fast, fail-functional, fault-tolerant multiprocessor system |
JPH096733A (ja) * | 1995-06-14 | 1997-01-10 | Toshiba Corp | 並列信号処理装置 |
JPH0973436A (ja) * | 1995-09-05 | 1997-03-18 | Mitsubishi Electric Corp | 多重化計算機における動作モード切替方式 |
US5732209A (en) * | 1995-11-29 | 1998-03-24 | Exponential Technology, Inc. | Self-testing multi-processor die with internal compare points |
US5809522A (en) * | 1995-12-18 | 1998-09-15 | Advanced Micro Devices, Inc. | Microprocessor system with process identification tag entries to reduce cache flushing after a context switch |
FR2748136B1 (fr) * | 1996-04-30 | 1998-07-31 | Sextant Avionique | Module electronique avec architecture redondante pour controle d'integrite du fonctionnement |
GB2317032A (en) * | 1996-09-07 | 1998-03-11 | Motorola Gmbh | Microprocessor fail-safe system |
GB9704542D0 (en) * | 1997-03-05 | 1997-04-23 | Sgs Thomson Microelectronics | A cache coherency mechanism |
EP0978784A1 (de) * | 1998-08-04 | 2000-02-09 | Motorola, Inc. | Verfahren zur Rechnerprogrammkodierung und Verfahren zur Fehlerbeseitigung kodierter Rechnerprogramme |
GB2340627B (en) * | 1998-08-13 | 2000-10-04 | Plessey Telecomm | Data processing system |
JP2000200255A (ja) * | 1999-01-07 | 2000-07-18 | Hitachi Ltd | プロセッサ間の同期化方法及び同期回路 |
WO2000079405A1 (fr) * | 1999-06-21 | 2000-12-28 | Hitachi, Ltd. | Processeur de donnees |
US6640313B1 (en) * | 1999-12-21 | 2003-10-28 | Intel Corporation | Microprocessor with high-reliability operating mode |
US6615366B1 (en) * | 1999-12-21 | 2003-09-02 | Intel Corporation | Microprocessor with dual execution core operable in high reliability mode |
US6772368B2 (en) * | 2000-12-11 | 2004-08-03 | International Business Machines Corporation | Multiprocessor with pair-wise high reliability mode, and method therefore |
DE10136335B4 (de) | 2001-07-26 | 2007-03-22 | Infineon Technologies Ag | Prozessor mit mehreren Rechenwerken |
US6947047B1 (en) * | 2001-09-20 | 2005-09-20 | Nvidia Corporation | Method and system for programmable pipelined graphics processing with branching instructions |
US20040076189A1 (en) * | 2002-10-17 | 2004-04-22 | International Business Machines Corporation | Multiphase clocking method and apparatus |
US7055060B2 (en) * | 2002-12-19 | 2006-05-30 | Intel Corporation | On-die mechanism for high-reliability processor |
JP2004234144A (ja) * | 2003-01-29 | 2004-08-19 | Hitachi Ltd | プロセッサの動作比較装置および動作比較方法 |
BRPI0411824A (pt) * | 2003-06-24 | 2006-08-08 | Bosch Gmbh Robert | processo para a comutação entre, pelo menos, dois modos de operação de uma unidade de processamento, bem como, unidade de processamento correspondente |
US7134031B2 (en) * | 2003-08-04 | 2006-11-07 | Arm Limited | Performance control within a multi-processor system |
DE10349581A1 (de) * | 2003-10-24 | 2005-05-25 | Robert Bosch Gmbh | Verfahren und Vorrichtung zur Umschaltung zwischen wenigstens zwei Betriebsmodi einer Prozessoreinheit |
-
2005
- 2005-10-25 EP EP05801268A patent/EP1807761A1/de not_active Ceased
- 2005-10-25 KR KR1020077009252A patent/KR20070067168A/ko not_active Application Discontinuation
- 2005-10-25 WO PCT/EP2005/055532 patent/WO2006045798A1/de active Application Filing
- 2005-10-25 US US11/666,407 patent/US20080126718A1/en not_active Abandoned
- 2005-10-25 KR KR1020077009250A patent/KR20070083771A/ko not_active Application Discontinuation
- 2005-10-25 KR KR1020077009253A patent/KR20070083772A/ko active IP Right Grant
- 2005-10-25 WO PCT/EP2005/055539 patent/WO2006045802A2/de active Application Filing
- 2005-10-25 DE DE502005005284T patent/DE502005005284D1/de active Active
- 2005-10-25 DE DE502005005490T patent/DE502005005490D1/de active Active
- 2005-10-25 JP JP2007537305A patent/JP2008518312A/ja active Pending
- 2005-10-25 US US11/666,405 patent/US7853819B2/en active Active
- 2005-10-25 EP EP05811107A patent/EP1820102A2/de not_active Withdrawn
- 2005-10-25 JP JP2007537304A patent/JP2008518311A/ja active Pending
- 2005-10-25 US US11/666,406 patent/US20080163035A1/en not_active Abandoned
- 2005-10-25 JP JP2007537301A patent/JP2008518308A/ja active Pending
- 2005-10-25 JP JP2007537303A patent/JP2008518310A/ja active Pending
- 2005-10-25 EP EP05811008A patent/EP1812861A1/de not_active Ceased
- 2005-10-25 WO PCT/EP2005/055538 patent/WO2006045801A2/de active IP Right Grant
- 2005-10-25 EP EP05801543A patent/EP1807763B1/de not_active Not-in-force
- 2005-10-25 RU RU2007119316/09A patent/RU2007119316A/ru not_active Application Discontinuation
- 2005-10-25 AT AT05797084T patent/ATE407398T1/de not_active IP Right Cessation
- 2005-10-25 KR KR1020077009251A patent/KR20070062579A/ko not_active Application Discontinuation
- 2005-10-25 US US11/666,413 patent/US20090164826A1/en not_active Abandoned
- 2005-10-25 EP EP05797084A patent/EP1810145B1/de active Active
- 2005-10-25 WO PCT/EP2005/055542 patent/WO2006045804A1/de active Application Filing
- 2005-10-25 WO PCT/EP2005/055537 patent/WO2006045800A1/de active Application Filing
- 2005-10-25 AT AT05801543T patent/ATE409327T1/de not_active IP Right Cessation
- 2005-10-25 JP JP2007537302A patent/JP4532561B2/ja not_active Expired - Fee Related
Non-Patent Citations (1)
Title |
---|
See references of WO2006045800A1 * |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1810145B1 (de) | Verfahren und vorrichtung zur synchronisierung in einem mehrprozessorsystem | |
EP1917592B1 (de) | Rechnersystems mit wenigstens zwei ausführungseinheiten und einer vergleichseinheit sowie verfahren zu dessen steuerung | |
DE102005055067A1 (de) | Vorrichtung und Verfahren zum Beheben von Fehlern bei einem wenigstens zwei Ausführungseinheiten mit Registern aufweisenden System | |
DE10349581A1 (de) | Verfahren und Vorrichtung zur Umschaltung zwischen wenigstens zwei Betriebsmodi einer Prozessoreinheit | |
EP2513796A1 (de) | Verfahren zum betreiben einer recheneinheit | |
DE102008004205A1 (de) | Schaltungsanordnung und Verfahren zur Fehlerbehandlung in Echtzeitsystemen | |
EP1776637A2 (de) | Verfahren zur verzögerung von zugriffen auf daten und/oder befehle eines zweirechnersystems sowie entsprechende verzögerungseinheit | |
WO2007057270A1 (de) | Programmgesteuerte einheit und verfahren zum betreiben derselbigen | |
EP1398700A1 (de) | Verfahren und Schaltungsanordnung zur Synchronisation redundanter Verarbeitungseinheiten | |
WO2005045665A1 (de) | Verfahren und vorrichtung zur operandenverarbeitung in einer prozessoreinheit | |
EP1552394A1 (de) | Verfahren zur ereignissynchronisation, insbesondere für prozessoren fehlertoleranter systeme | |
EP1618476A2 (de) | Programmgesteuerte einheit und verfahren | |
DE102004051952A1 (de) | Verfahren zur Datenverteilung und Datenverteilungseinheit in einem Mehrprozessorsystem | |
EP1776636A2 (de) | Verfahren zum registrieren von fehlern und entsprechendes register | |
EP2228723B1 (de) | Verfahren zur Fehlerbehandlung eines Rechnersystems | |
DE102004051937A1 (de) | Verfahren und Vorrichtung zur Synchronisierung in einem Mehrprozessorsystem | |
DE102004051964A1 (de) | Verfahren und Vorrichtung zur Überwachung einer Speichereinheit in einem Mehrprozessorsystem | |
DE102005037226A1 (de) | Verfahren und Vorrichtung zur Festlegung eines Startzustandes bei einem Rechnersystem mit wenigstens zwei Ausführungseinheiten durch markieren von Registern | |
EP1398699A1 (de) | Verfahren zur Ereignissynchronisation, insbesondere für Prozessoren fehlertoleranter Systeme | |
DE102004051992A1 (de) | Verfahren und Vorrichtung zur Verzögerung von Zugriffen auf Daten und/oder Befehle eines Mehrprozessorsystems | |
DE102004051950A1 (de) | Verfahren und Vorrichtung zur Taktumschaltung bei einem Mehrprozessorsystem | |
WO2007017372A1 (de) | Verfahren und vorrichtung zur steuerung eines rechnersystems mit wenigstens zwei ausführungseinheiten | |
DE102010031017A1 (de) | Verfahren zur Überwachung des Programmablaufs eines Prozessors | |
DE102005037259A1 (de) | Verfahren und Vorrichtung zur Festlegung eines Startzustandes bei einem Rechnersystem mit wenigstens zwei Ausführungseinheiten durch Umschalten von Registersätzen | |
DE102005037258A1 (de) | Verfahren und Vorrichtung zur Festlegung eines Startzustandes bei einem Rechnersystem mit wenigstens zwei Ausführungseinheiten durch Übernehmen des Startzustandes |
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: 20070525 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR MK YU |
|
17Q | First examination report despatched |
Effective date: 20070827 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR MK YU |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: LANGUAGE OF EP DOCUMENT: GERMAN |
|
REF | Corresponds to: |
Ref document number: 502005005284 Country of ref document: DE Date of ref document: 20081016 Kind code of ref document: P |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081214 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 |
|
NLV1 | Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act | ||
BERE | Be: lapsed |
Owner name: ROBERT BOSCH G.M.B.H. Effective date: 20081031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081203 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090103 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20081031 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 |
|
26N | No opposition filed |
Effective date: 20090604 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20081031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20081025 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081203 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20081025 Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090304 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20091031 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20091031 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081204 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20101021 Year of fee payment: 6 Ref country code: IT Payment date: 20101028 Year of fee payment: 6 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080903 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IE Payment date: 20111020 Year of fee payment: 7 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20121025 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20121025 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20121025 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20121025 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20131018 Year of fee payment: 9 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20150630 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20141031 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20161213 Year of fee payment: 12 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 502005005284 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180501 |