EP1916794B1 - Détecteur d'erreur et procédé de détection d'erreur - Google Patents

Détecteur d'erreur et procédé de détection d'erreur Download PDF

Info

Publication number
EP1916794B1
EP1916794B1 EP07119334.6A EP07119334A EP1916794B1 EP 1916794 B1 EP1916794 B1 EP 1916794B1 EP 07119334 A EP07119334 A EP 07119334A EP 1916794 B1 EP1916794 B1 EP 1916794B1
Authority
EP
European Patent Office
Prior art keywords
data
unit
error detection
error
diagnostic
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.)
Expired - Fee Related
Application number
EP07119334.6A
Other languages
German (de)
English (en)
Other versions
EP1916794A2 (fr
EP1916794A3 (fr
Inventor
Kaoru Noumi
Susumu Nishihashi
Tomoyuki Katou
Yukio Ishikawa
Yasuyuki Umezaki
Hidetaka Ebeshu
Shigeo Koide
Yukio Fujisawa
Hiroaki Shimauchi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Denso Ten Ltd
Fujitsu Semiconductor Ltd
Renesas Electronics Corp
Original Assignee
Denso Ten Ltd
Fujitsu Semiconductor Ltd
Renesas Electronics Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Denso Ten Ltd, Fujitsu Semiconductor Ltd, Renesas Electronics Corp filed Critical Denso Ten Ltd
Publication of EP1916794A2 publication Critical patent/EP1916794A2/fr
Publication of EP1916794A3 publication Critical patent/EP1916794A3/fr
Application granted granted Critical
Publication of EP1916794B1 publication Critical patent/EP1916794B1/fr
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0045—Arrangements at the receiver end
    • 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/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
    • G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0061—Error detection codes
    • H04L1/0063—Single parity check
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/24—Testing correct operation
    • H04L1/242—Testing correct operation by comparing a transmitted test signal with a locally generated replica
    • H04L1/243—Testing correct operation by comparing a transmitted test signal with a locally generated replica at the transmitter, using a loop-back
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/24—Testing correct operation
    • H04L1/242—Testing correct operation by comparing a transmitted test signal with a locally generated replica
    • H04L1/244—Testing correct operation by comparing a transmitted test signal with a locally generated replica test sequence generators

Definitions

  • the present invention relates to an error detector that detects data errors. More particularly, the present invention relates to an error detector suitable for installation on an in-vehicle gateway apparatus which relays data among a plurality of communication networks.
  • a plurality of ECUs such as an engine ECU, a door controlling ECU, an air-bag ECU, an audio ECU and a navigation ECU have been installed in a vehicle, as shown in FIG. 24 .
  • a gateway apparatus which serves as an interface is required.
  • JP-A-2003-244187 and JP-A-2003-264571 disclose technologies of routing function of the gateway apparatus realized in software.
  • the gateway apparatus relays data sent and received among a plurality of different networks and realizes gateway functions such as communication protocol conversions and packet filtering. Consequently, a communication is made between nodes that are connected to different networks.As a plurality of devices is connected via networks and data is sent and received by communication, data errors in communication may occur. The data stored in a memory may have errors caused by garbled bits and such. While installation of a device with a data check function has been designed to increase the reliability of data, unless otherwise a device to verify that the check function itself is functioning normally is provided, the reliability of data lowers.
  • a parity bit generated by a parity generator is inverted by an error generator and error data is stored in a memory for parity.
  • a parity checker is configured to output an error signal.
  • the present invention addresses the problems described above and aims to provide an error detector and an error detection method capable of performing a thorough failure diagnosis of an error detection function.
  • An error detector according to the invention is defined in claim 1.
  • An error detector includes an error detection data generating unit that generates error detection data for a data string sent from a first apparatus to a second apparatus, an error detecting unit that detects, based on the error detection data generated by the error detection data generating unit, an error in a data string output from the second apparatus, a data switching unit that switchingly outputs data from the error detection data generating unit as error detection data for the data string and data sent from a diagnostic data sending unit that sends diagnostic data, and a failure diagnosing unit that diagnoses a failure in an error detection function including at least one of the error detection data generating unit and the error detecting unit based on the error detection data output from the data switching unit while the data switching unit is switched to output data sent from the diagnostic data sending unit.
  • the error detector may also include a determining unit that determines the data switching unit operates normally in response to a coincidence between diagnostic data written in the second apparatus and diagnostic data read from the second apparatus while the data switching unit is switched to output the diagnostic data sent from the diagnostic data sending unit and further to a non-coincidence between the diagnostic data output from the diagnostic data sending unit and the data read from the second apparatus while the data switching unit is switched to output error detection data from the error detection data generating unit.
  • the determining unit determines that the data switching unit operates normally and the data switching unit outputs the diagnostic data sent from the diagnostic data sending unit, the determining unit determines the error detecting unit operates abnormally in response to a non-coincidence between the diagnostic data and a detection result made by the error detecting unit for the data string output from the second apparatus.
  • the operation of the error detection function is verified after the operation of the data switching unit is verified, making the operation verification of the error detection function highly accurate.
  • the error detection data generated by the error detection data generating unit is data to be used for a parity check of the data string, and the error detecting unit performs a parity check of the data string output from the second apparatus.
  • the first apparatus is at least one of a controlling unit of a gateway apparatus that controls transfer of frame data between a plurality of communication channels and a search engine unit that controls transfer of the frame data
  • the second apparatus is a memory unit that stores data.
  • the data string includes at least one of post-routing frame data that is output from at least one of the controlling unit and the search engine unit and routing data to be used for controlling transfer of the frame data.
  • An error detection method includes: adding, to a data string sent from a first apparatus to a second apparatus, either error detection data generated by an error detection data generating unit or diagnostic data sent from a diagnostic data sending unit; detecting an error in a data string output from the second apparatus by an error detecting unit based on the error detection data, when the error detection data is added to the data string; and diagnosing a failure of an error detection function including at least one of the error detection data generating unit and the error detecting unit based on the diagnostic data, when the diagnostic data is added to the data string.
  • the present invention provides a thorough failure diagnosis of an error detection function to be performed.
  • Bus lines that connect between a CPU I/F 1100 and a memory 1200 are connected with a parity bit summing unit 1300 which includes a parity bit generator 1301 (corresponds to an error detection data generator of the present invention) and a selector circuit 1302 (corresponds to a data switcher of the present invention).
  • a parity bit summing unit 1300 which includes a parity bit generator 1301 (corresponds to an error detection data generator of the present invention) and a selector circuit 1302 (corresponds to a data switcher of the present invention).
  • the parity bit generator 1301 performs a parity operation on a data string which a CPU (corresponds to a diagnostic data transmitter and a failure diagnostic tool of the present invention) writes to the memory 1200, and appends a parity bit of the operation result to the data string. For example, when 32 bit data is written to the memory 1200, a parity operation on a data string composed of 31 bits is performed and a parity bit of the operation result is appended to the most significant bit (32nd bit) of the data string.
  • the selector circuit 1302 is a circuit to select the parity bit to be appended to a data string to be either an operation result of the parity bit generator 1301 or a parity bit output from the CPU.
  • the selector circuit 1302 is fed with a force generation enable signal which the CPU outputs.
  • the CPU generates diagnostic data (1 bit) which makes the result of a parity operation normal or abnormal and is appended to a data string for testing.
  • the CPU stores the address of the data string written and errata information of the diagnostic data appended to the data string linked together.
  • the bus lines which connect between the CPU I/F 1100 and the memory 1200 are provided with a checker 1400 which includes a parity checker 1401.
  • the parity checker 1401 (corresponds to an error detector of the present invention) performs a parity check on a data string read out from the memory 1200 and outputs the result of the parity check to the CPU.
  • the CPU When the data string for testing is written to the memory 1200 for a predefined number of times, the CPU reads out the data string written for testing from the memory 1200. In the checker 1400, the parity checker 1401 performs a check on the data string read out from the memory 1200. The result of the check is notified to the CPU.
  • the CPU verifies the operation of the parity checker 1401, based on the errata information of the parity bit appended and the result of the parity check by the parity checker 1401.
  • step T1 When starting a diagnosis of the parity checker 1401 (step T1), the CPU sets the force generation enable signal to on (step T2).
  • the CPU When the force generation enable signal is set to on, the CPU appends diagnostic data (1 bit) which makes the result of the parity check normal or abnormal to the most significant bit (the parity bit) of a data string for testing and stores the data string to the memory 1200 (step T3).
  • the CPU stores the address of the data string written to the memory 1200 and the errata information of the diagnostic data appended to the data string (step T4).
  • step T5 When the number of writing data for testing is reached to a predefined number of times (step T5; YES), the CPU reads out the data string for testing from the memory 1200. In this case, the parity checker 1401 performs a parity check on the read out data for testing (step T6). When the result of the parity check on the data for testing is obtained, the CPU judges whether the parity checker 1401 is operating properly or not, based on the result of the parity check and the errata information of the diagnostic data stored.
  • An abnormality may be developed in the result of a parity check caused by an abnormal fixation of the selector circuit 1302.
  • the force generation enable signal is set to on for the selector circuit 1302 to output a signal from the CPU. Then, as diagnostic data, 0 and 1 are switched around and stored in the memory 1200. In this case, by comparing the diagnostic data read out from the memory 1200 with the diagnostic data output from the CPU, whether the both data match or not is judged. When the both data match, the force generation enable signal is set to off. Then, the CPU outputs diagnostic data by switching around 0 and 1.
  • a CPU bus 16 is connected with a CPU 2, a flash read only memory (ROM) 3, a universal asynchronous receiver transmitter (UART) 4, an interrupt control unit 6, a DMA controller 7, a CAN interface unit 8, a plurality of CANs 9 (while four CAN of CAN_0, CAN_1, CAN_2 and CAN_3 are shown in a second embodiment, the number of CANs is not limited to this), a bus interface unit 10, and the like.
  • the bus interface unit 10 is connected with a search engine unit 11, a map memory 13, a sending buffer 14 and a receiving control unit 15.
  • the search engine unit 11, the sending buffer 14 and the receiving control unit 15 are connected by data lines which input and output data from and to the CPU bus 16 via the bus interface unit 10. Between the search engine unit 11 and the sending buffer 14 and between the search engine unit 11 and the receiving control unit 15 are also connected by data lines.
  • the receiving control unit 15 is connected with the CAN interface unit 8 by data lines as to input data directly from the CAN interface unit 8. In FIG. 3 , other than data lines, control lines which send and receive control signals are shown.
  • the CPU 2 outputs signals for controlling the abovementioned function sections to the control lines.
  • the control lines are also wired between the DMA controller 7 and the search engine unit 11, and the DMA controller 7, without the control by the CPU 2, reads out data from the search engine unit 11 and transfers the data to forwarding destinations.
  • the configuration having the search engine unit 11, the map memory 13, the sending buffer 14, the receiving control unit 15, the bus interface unit 10 and the CAN interface unit 8 is called a gateway hardware macro section 17.
  • the gateway hardware macro section 17 is mainly provided with the following functions: first, to take out frame data from a message box of the CAN 9 by using, as a trigger, an interrupt signal generated by the CAN 9 when the frame data is received; second, to route the frame data received; and third, to detect routing errors and other errors. Besides the above, a transmit function of routed data and such may be provided.
  • the flash ROM 3 stores data or programs used when the CPU 2 runs various processes including a data transmission process.
  • the CPU 2 controls the whole in-vehicle gateway apparatus 1 shown in FIG. 3 and processes the transmission of the frame data routed by the search engine unit 11 by program-control.
  • the CPU 2 performs routing to sort forwarding destinations of the frame data received, based on the programs stored in the flash ROM 3.
  • the UART 4 is connected with external devices and converts parallel signals sent from the external devices to serial signals, and conversely, converts serial signals sent from serial devices to parallel signals.
  • the interrupt control unit 6 controls outputs of interrupt signals output from the search engine unit 11 to the CPU 2.
  • a sending FIFO a first storage
  • the search engine unit 11 outputs an interrupt signal to the CPU 2.
  • the DMA controller 7 DMA transfers frame data stored in the sending FIFO 21 routed by the search engine unit 11 without involving the CPU 2.
  • a plurality of CANs 9 (i.e. CAN_0, CAN_1, CAN_2 and CAN_3) is provided for each communication channel and stores the frame data received from a CAN bus (not shown) and the frame data routed by the search engine unit 11 and by the CPU 2.
  • the routed frame data is read out from the message box and is output to the CAN bus.
  • the search engine unit 11 takes out frame data from the message box of the CAN 9, with the interrupt signal output from the CAN 9 as a trigger, and stores the data to the receiving control unit 15 via the CAN interface unit 8. Thereafter, the search engine unit 11 takes out the frame data from the receiving control unit 15 by a predefined timing clock and performs processes such as routing and searching information of relay destinations of data.
  • the search engine unit 11 is also provided with a function to detect an error occurred in the routing process. The details of a routing map stored in the map memory 13 are described later.
  • the sending buffer 14 stores the frame data routed by the search engine unit 11.
  • the receiving control unit 15 stores the frame data read out from the message box of the CAN 9.
  • the routing of frame data is performed in parallel by a software controlling unit 50 of the CPU 2 and by the gateway hardware macro section 17 provided as hardware.
  • the gateway hardware macro section 17 has, as shown in FIG. 4 , distributing units 51 and registers 56 provided for each communication channel, a selector unit 52, a time stamp unit 61, a search engine unit 11, a map memory 13 and a sending FIFO 21.
  • the abovementioned parity bit summing unit 1300 and checker 1400 are provided between the search engine unit 11 and the map memory 13. Their details are described later.
  • the distributing unit 51 which may be called routing unit, is provided for each communication channel, takes out frame data from a message box 9 of the CAN 9 and performs a sorting process of output destination of the frame data.
  • the distributing unit 51 in reference with destination information set in the frame data, sets the forwarding destination of the frame data to any one of the software controlling unit 50, the selector unit 52 or both the software controlling unit 50 and the selector unit 52.
  • the software controlling unit 50 is a functional section which is enabled by the program-controlled operation of the CPU 2.
  • sorting output destinations of data by the unit of channels and of selected frames allows processes by the software controlling unit 50 and by the hardware in the search engine unit 11 to be preformed in parallel.
  • the start time of the process in the software controlling unit 50 can be expedited.
  • the register 56 stores setting information set by the software controlling unit 50.
  • the setting information at least contains operational setting information of an in-vehicle gateway apparatus and setting information for sorting.
  • the distributing unit 51 sorts out frame data according to the setting information stored in the register 56. While only the distributing unit 51 operates referencing with the setting information, the selector unit 52, the search engine unit 11 and the sending FIFO 21 provided at later stages never stop operating and such by the setting information. Consequently, even if the settings of the gateway, communication channels and such are dynamically changed, the problems in that frame data being lost and such in the gateway hardware macro section 17 do not occur.
  • the selectingor unit 52 is provided at the prior stage to the search engine unit 11.
  • the selector unit 52 is fed with frame data from a plurality of communication channels and selects the frame data to output to the search engine unit 11.
  • the selector unit 52 controls the timing of outputting the selected frame data to the search engine unit 11. Even when frame data is output from a plurality of communication channels simultaneously, the selector unit 52 selects the frame data by the order of priority and by the order of arrival, and controls the timing of output to the search engine unit 11. Consequently, the search engine unit 11 can be shared by a plurality of communication channels.
  • the distributing unit 51 has a first destination distributing unit 59 and a second destination distributing unit 60.
  • Frame data is sorted by a message distributing unit 58 of the CAN 9 according to an ID of the data and is registered to the message boxes (0, 1, 2, 3, and so on).
  • the first destination distributing unit 59 sets the destination of frame data in the locations sorted by the message distributing unit 58 (i.e. the message boxes 0, 1, 2, 3, and so on) for the software controlling unit 50 or for the search engine unit 11, or sets a multi-destination transmission which sets destinations for both the software controlling unit 50 and the search engine unit 11. Some frame data is discarded here.
  • the second destination distributing unit 60 according to the processing status of the search engine unit 11, forcibly changes the frame data which has been destined for the search engine unit 11 to the software controlling unit 50 or sets frame data to be discarded.
  • time stamp unit 61 In reference with FIG. 6 , a configuration of the time stamp unit 61 is described.
  • the time stamp unit 61 appends time stamps to the frame data input to the selector unit 52.
  • the time stamp unit 61 as shown in FIG. 6 , is provided with a frequency divider 611 and a free running counter 612.
  • the frequency divider 611 is fed with a function enabling signal and a divider ratio setting signal output from the CPU 2, and a clock signal.
  • the frequency divider 611 When the function enabling signal is enabled, the frequency divider 611, outputs a counter enabling signal which is produced based on the frequency divided clock signal according to the setting of the divider ratio setting signal to the free running counter 612.
  • the free running counter 612 is fed with the clock signal, the counter enabling signal output from the frequency divider 611 and the function enabling signal from the CPU 2.
  • the free running counter 612 when the function enabling signal is enabled, outputs a time stamp by counting the counter enabling signal output from the frequency divider 611.
  • the clock frequency is at 16 MHz and the free running counter is a 16-bit counter
  • the frequency dividing setting of 1/128
  • the minimum measurable time becomes 8 ⁇ s and the maximum measurable time becomes 0.524 seconds.
  • the frequency dividing setting is 1/16384
  • the minimum measurable time becomes 1.024 ms and the maximum measurable time becomes 67.1 seconds.
  • the CPU 2 sets, for the time stamp unit, the divider ratio according to the range to be measured and resolution (step S1), and thereafter, sets the function enabling signal enable and activates the time stamp unit 61 (step S2).
  • the selector unit 52 has registers 521, 522, 523 and 524 provided for each communication channel, and a select logic unit 525 and a selector 526.
  • the registers 521, 522, 523 and 524 are fed with frame data from each channel, timing notifying signals to notify the input timing of frame data to respective registers 521, 522, 523 and 524, and a time stamp issued by the time stamp unit 61.
  • the time stamp issued by the time stamp unit 61 is appended to the frame data in the registers 521, 522, 523 and 524.
  • the registers 521, 522, 523 and 524 output, to the select logic unit 525, a status signal which indicates whether the valid frame data is held in the registers 521, 522, 523 and 524 or not.
  • the registers 521, 522, 523 and 524 output the frame data, to which the time stamp is appended, to the selector 526 at a predefined timing.
  • the select logic unit 525 outputs, to the selector 526, a select instruction signal that selects the frame data to be output, based on the status signals from the registers 521, 522, 523 and 524.
  • the selector 526 selects the frame data according to the select instruction signal from the select logic unit 525, and thereafter, outputs the frame data to the search engine unit 11 in a subsequent stage.
  • the search engine unit 11 is provided with a status controlling unit 70, an entry identifying unit 71, a number summing unit 72, a number subtractor 73, a minimum selector 74, an maximum selector 75, an summing unit 76, a dividing and holding unit 77, a table 78 configured in memory, a matching and comparing unit 79 and an entry checking unit 80.
  • the status controlling unit 70 is fed with a frame output signal from the selector unit 52 and controls all functional sections shown in FIG. 9 .
  • the status controlling unit 70 controls to search the table 78 for the predetermined number of times according to a number of times to search which is input from the entry identifying unit 71.
  • the entry identifying unit 71 has a first conversion table 92 and a second conversion table 93.
  • a set value of a number of valid entries entered to the first conversion table 92 represents the number of entries registered in a routing map which is referenced in destination search.
  • the first conversion table 92 calculates a value of number of search which sets the number of times to search the memory 78 from the set value of a number of valid entries. For example, when the number of entry for a channel is 256 entries (nodes), as 256 is the eighth power of 2, the number of times to search becomes 9 times by adding a value of +1.
  • the second conversion table 93 is fed with the set value of a number of valid entries and outputs a maximum entry number and a minimum entry number.
  • the minimum entry number is the least number of ID numbers of the nodes registered (0), and similarly, the maximum entry number represents the greatest number of the ID numbers of the nodes registered (the set value of a number of valid entries).
  • the minimum entry number is output to the minimum selector 74 and the maximum entry number is output to the maximum selector 75.
  • the value of number of search is output to the status controlling unit 70.
  • the minimum selector 74 is fed with the minimum entry number from the entry identifying unit 71.
  • the minimum selector 74 selects and outputs any one of the aforementioned minimum entry number, the previous entry number, or the entry number derived from the output of the dividing and holding unit 77 with an added value of +1, according to the control of the status controlling unit 70.
  • the maximum selector 75 is fed with the maximum entry number from the entry identifying unit 71.
  • the maximum selector 75 selects and outputs any one of the aforementioned maximum entry number, the previous entry number, or the entry number derived from the output of the dividing and holding unit 77 with an added value of -1, according to the control of the status controlling unit 70.
  • the summing unit 76 adds the entry number of the minimum selector 74 and the entry number of the maximum selector 75.
  • the dividing and holding unit 77 divides the added value of the summing unit 76 by 2 and holds the result of the division.
  • FIG. 11 illustrates the concept of a method of the binary tree search.
  • a minimum set value of a memory which the channel subject to search uses is set as N and that of a maximum set value is set as M.
  • the set value of a number of valid entries is set as the maximum set value and the minimum set value is set as the value of 0.
  • the entry checking unit 80 judges whether the entry data read out from the table 78 is normal data or not. The judged result is output to the status controlling unit 70.
  • the matching and comparing unit 79 compares an entry data read out from the table 78 with an ID of received data.
  • FIG. 12 a configuration of the matching and comparing unit 79 is shown.
  • the matching and comparing unit 79 is provided with a logical operating unit 95 and a match comparison operator 96.
  • the logical operating unit 95 refines search ranges by superposing a mask over an ID of received data as shown in FIG. 13 .
  • the matching and comparing unit 79 compares the mask superposed ID number with the entry data read out and judges whether the both match or not.
  • the status controlling unit 70 When search is started, the status controlling unit 70 first sets the search time to a value of 0 (step S11). In synchronous with this process, the entry identifying unit 71 sets the value of number of search according to the number of entries (step S12). The value of number of search is notified from the entry identifying unit 71 to the status controlling unit 70.
  • the status controlling unit 70 compares the number of search times with the value of number of search notified from the entry identifying unit 71 (step S13), and when the number of search times is less than the value of number of search (step S13; YES), based on an initial value or the information of a previous large-or-small comparison, a pointer address of a memory is generated (step S14).
  • the minimum selector 74 is fed with a minimum entry number from the entry identifying unit 71.
  • the maximum selector 75 is fed with an maximum entry number from the entry identifying unit 71.
  • the summing unit 76 adds the minimum entry number and the maximum entry number.
  • the dividing and holding unit 77 divides the added value by 2 and holds the result. The result value becomes an address of the pointer.
  • step S15 When an address of the pointer is generated, the entry data represented by the pointer address is read out from the memory 78 (step S15). The read out entry data is fed to the entry checking unit 80 and is judged whether the data is normal or not (step S16). When the value is not normal (step 516; NO), it is processed as a system error. When the entry data is normal (step S16; YES), whether the ID of the received data matches with the entry data or not is judged by the matching and comparing unit 79 (step S17).
  • step S17; NO the number of search times is incremented and the result of the large-or-small comparison in the matching and comparing unit 79 is output to the status controlling unit 70 (step S18), and steps in and following the step S13 are repeated.
  • the status controlling unit 70 controls the minimum selector 74 and the maximum selector 75, and the pointer address corresponding to the result of the previous comparison is generated.
  • step S19 the destination information of the matched entry data is checked (step S19), and when normal, is written to the sending FIFO 21 (step S20).
  • step S19; NO In case the destination information is not normal (step S19; NO), either it is processed as a system error (step S21) or the frame data is discarded (step S22). Further, the status controlling unit 70, when the number of search times becomes greater than the value of number of search (step S13; YES), discards the frame data received (step S22).
  • the status controlling unit 70 while being in an idle state not receiving any frame data, may conduct a normality confirmation operation for map information. This process is described in reference with flowcharts shown in FIGS. 16A and 16B .
  • the status controlling unit 70 while being in the idle state not receiving any frame data (step S31), conducts a self-check (step S44).
  • the status controlling unit 70 generates a pointer address (step S45) first, and searches the entry data stored in the corresponding address and takes out the data (step S46). Thereafter, the normality of entry data taken out is judged (step S47). When the searched entry data is judged as normal (step S47; YES), the process is finished. When an error is detected (step S47; NO), it is processed as a system error (step S48).
  • FIG. 17 shows a configuration of the sending FIFO 21 and that of discarding frame data according to a delay time in the process of frame data.
  • the sending FIFO 21 is provided with a time stamp FIFO 210 which stores a time stamp and a data FIFO 211 which stores frame data.
  • a data discarder 300 that discards data according to a delay time in process is provided with a comparing unit 301 and a valid unit 302.
  • the time stamp added frame data output from the search engine unit 11 is separated to a time stamp and an area other than the time stamp by a separating unit 220, and are respectively held in the time stamp FIFO 210 (hereinafter abbreviated also as TS FIFO) and the data FIFO 211.
  • the separating unit 220 takes out the time stamp inserted at a predefined location of frame data and outputs to the TS FIFO 210.
  • the valid unit 302 stores validation data, where a value of 1 is stored for the valid data, which represents the data held in the time stamp FIFO 210 and in the data FIFO 211 valid.
  • the comparing unit 301 is fed with a time stamp and timeout setting information.
  • the time stamp is the information representing the current time issued by the time stamp unit 61.
  • the timeout setting information is the information set by the CPU 2 and is the setting of a permissible delay time to take for frame data entered in the gateway hardware macro section 17 to be output from the gateway hardware macro section 17.
  • the valid unit 302, the time stamp FIFO 210 and the data FIFO 211 are respectively configured with a FIFO of the same configuration.
  • the time stamp information of the frame data written to the data FIFO 211 is written to the same area of the time stamp FIFO 210.
  • the validation data that represents whether the frame data being valid data or invalid data is written to the same area of the valid unit 302.
  • the comparing unit 301 reads out the time stamp in the area where the data representing being valid is stored in the valid unit 302 from the TS FIFO 210, and compares that with the time stamp information representing the current time output from the time stamp unit 61. When the difference between the time in the time stamp stored in the TS FIFO 210 and the current time exceeds the timeout setting information notified from the CPU 2, the comparing unit 301 changes validation data in the valid unit 302 to that of invalid data, i.e. stores a value of 0. When the validation data is changed to that of invalid data, the value in a message counter 303 is subtracted by a value of 1.
  • the CPU 2 reads out the value of the message counter 303 at a predefined timing.
  • the CPU 2 reads out the frame data from the data FIFO 211. In this case, the frame data for which the data representing being invalid is stored in the valid unit 302 is discarded without being read out.
  • the comparing unit 301 may be configured to output an interrupt signal to the CPU 2. This configuration is shown in FIG. 18 .
  • the CPU 2 is fed with the interrupt signal, it reads out the frame data stored in the data FIFO 211 in priority.
  • FIGS. 17 and 18 the configurations of discarding the frame data whose dwell time in the gateway hardware macro section 17 exceeded the timeout time by hardware are shown. However, other than those, by the software control of the CPU 2, the frame data whose dwell time exceeded the timeout time may be discarded by software.
  • the CPU 2 references with the message counter 303 at a predefined time interval and judges whether processing data is stored in the sending FIFO 21 (step S51).
  • processing data is stored in the sending FIFO 21 (step S51: YES)
  • the CPU 2 reads out the processing data from the sending FIFO 21 (step S52) and reads out the time stamp information representing the current time from the time stamp unit 61 (step S53).
  • the CPU 2 compares the time stamp information appended to the frame data read out from the sending FIFO 21 with the current time information read out from the time stamp unit 61 (step S54).
  • step S55 When the difference between the time in the time stamp and the current time is greater than a first criterion value ⁇ (step S55; YES), the frame data is discarded (step S56).
  • step S57; YES When the difference between the time in the time stamp and the current time is smaller than the first criterion value ⁇ and is greater than a second criterion value ⁇ (step S57; YES), the CPU 2 judges that the process of the frame data is delayed and processes the frame data in priority (step S58).
  • the first criterion value ⁇ is set as a greater value than that of the second criterion value ⁇ .
  • step S57 When the difference between the time in the time stamp and the current time is smaller than the second criterion value ⁇ (step S57; NO), the CPU 2 judges that the process of the frame data is not delayed and processes normally (step S59).
  • FIGS. 20A through 20D configurations of the frame data transferred in the gateway hardware macro section 17 are shown.
  • FIG. 20A shows the configuration of the frame data input to the selector unit 52.
  • FIG. 20B shows the configuration of the frame data with a time stamp appended output from the selector unit 52 to the search engine unit 11.
  • FIG. 20C shows the configuration of the frame data with the time stamp appended written to the sending FIFO 21.
  • FIG. 20D shows the configuration of the frame data which the CPU 2 reads out from the sending FIFO 21.
  • the asterisk mark shown in FIGS. 20B through 20D represents being composed of a plurality of bits.
  • the time stamp information appended to frame data may be appended only to the data judged as valid frame data by the search engine unit 11.
  • FIG. 21 shows the configuration in that case. In view of measuring a dwell time in the gateway hardware macro section 17, while the configuration in FIG. 4 measures the strict dwell time, the configuration shown in FIG. 21 allows the scale of hardware to be small.
  • a parity bit summing unit 1300 and a checker 1400 in the aforementioned first embodiment are provided between the software controlling unit 50 and the map memory 13.
  • appending parity bit to the data written to the map memory 13 from the software controlling unit 50 for example, data for a routing map
  • the parity bit summing unit 1300 and the parity check of the data which the software controlling unit 50 read out from the map memory 13 is performed by a parity checker 1401.
  • the error judgment of a selector circuit 1302 and the parity checker 1401 is performed in the same procedure as described in the first embodiment mentioned above.
  • the frame data read out from the map memory 13 and the check result of the parity checker 1401 are output to the search engine unit 11 as well.
  • the parity bit summing unit 1300 and the checker 1400 may be provided between the search engine unit 11 and the sending FIFO 21.
  • the parity check of the frame data written to the sending FIFO 21 from the search engine unit 11 is performed by the parity checker 1401.
  • the frame data read out from the parity checker 1401 and from the sending FIFO 21 are output to the software controlling unit 50.
  • the search engine unit 11 may be configured to check the parity.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Small-Scale Networks (AREA)
  • Detection And Correction Of Errors (AREA)
  • Techniques For Improving Reliability Of Storages (AREA)
  • Test And Diagnosis Of Digital Computers (AREA)
  • For Increasing The Reliability Of Semiconductor Memories (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Claims (4)

  1. Détecteur d'erreur comprenant :
    une unité de génération de données de détection d'erreur (1301) qui engendre des données de détection d'erreur à partir d'une chaîne de données envoyée par un premier appareil (1100, 50, 11), les données de détection d'erreur étant ajoutées à la chaîne de données à stocker dans un deuxième appareil (1200, 13, 21),
    une unité de détection d'erreur (1401) qui effectue un contrôle de parité sur la chaîne de données lue du deuxième appareil, lue ensemble avec les données de détection d'erreur y ajoutées, pour détecter une erreur dans la chaîne de données lue du deuxième appareil,
    une unité de commutation de données (1302) qui envoie, selon la commutation, en tant que données de détection d'erreur à ajouter à la chaîne de données, soit les données de détection d'erreur envoyées par l'unité de génération de données de détection d'erreur (1301), soit des données de diagnostic, pour une utilisation comme données de détection d'erreur pendant des essais, envoyées par une unité d'envoi de données de diagnostic (1100), sur la base d'un état d'entrée d'un signal d'activation de génération de force reçu par l'unité de commutation de données,
    une unité de diagnose d'erreur qui détermine si l'unité de détection d'erreur fonctionne anormalement, sur la base de la question de savoir si un résultat d'un contrôle de parité, par l'unité de détection d'erreur, de la chaîne de données à laquelle les données de diagnostic ont été ajoutées, lu du deuxième appareil, correspond à une information d'erreur qui indique si les données de diagnose envoyées par l'unité d'envoi de données de diagnose (1100) rend un résultat d'une opération de parité effectuée sur la chaîne de données, normal ou anormal, et
    une unité de détermination qui détermine que l'unité de commutation de données (1302) fonctionne normalement lorsque les données de diagnose envoyées par l'unité d'envoi de données de diagnose (1100) et les données de détection d'erreur lues du deuxième appareil (1200) vont ensemble pendant que le signal de génération de force est activé et l'unité de commutation de données (1302) est commutée pour sortir les données de diagnose envoyées par l'unité d'envoi de données de diagnose comme les données de détection d'erreur à ajouter à la chaîne de données pour stockage dans le deuxième appareil, et, en outre, lorsque les données de diagnose envoyées par l'unité d'envoi de données de diagnose et les données de détection d'erreur lues du deuxièmes appareil ne vont pas ensemble, pendant que le signal de génération de force est désactivé et l'unité de commutation de données est commutée pour sortir les données de détection d'erreur envoyées par l'unité de génération de données de détection d'erreur (1301) comme les données de détection d'erreur à ajouter à la chaîne de données pour stockage dans le deuxième appareil,
    caractérisé en ce que l'unité de détermination détermine que l'unité de détection d'erreur (1401) fonctionne anormalement lorsque l'unité de détermination détermine que l'unité de commutation de données (1402) fonctionne normalement et l'unité de diagnose d'erreur détermine que la fonction de détection d'erreur fonctionne anormalement.
  2. Détecteur d'erreur selon la revendication 1, caractérisé en ce que
    le premier appareil (1100) est au moins un parmi une unité de commande d'un appareil de passerelle qui commande le transfert de données de trame entre une pluralité de canaux de communication et une unité de moteur de recherche qui commande le transfert des données de trame, et
    le deuxième appareil (1200) est une unité de mémoire qui stocke des données.
  3. Détecteur d'erreur selon la revendication 2, caractérisé en ce que la chaîne de données comprend au moins les unes parmi des données de trame d'après routage qui sont sorties par au moins une parmi l'unité de commande et l'unité de moteur de recherche, et des données de routage à utiliser pour commander le transfert des données de trame.
  4. Procédé de détection d'erreur comprenant :
    une étape de génération de données de détection d'erreur pour engendrer des données de détection d'erreur à partir d'une chaîne de données envoyée par un premier appareil (1100, 50, 11), les données de détection d'erreur étant à ajouter à la chaîne de données et à stocker ensemble avec la chaîne de données dans un deuxième appareil (1200, 13, 21),
    une étape de détection d'erreur pour effectuer un contrôle de parité sur la chaîne de données lue du deuxième appareil, lue ensemble avec les données de détection d'erreur y ajoutées, pour détecter une erreur dans la chaîne de données lue du deuxième appareil,
    une étape de commutation de données pour envoyer, selon la commutation, en tant que données de détection d'erreur à ajouter à la chaîne de données, soit les données de détection d'erreur engendrées à l'étape de génération de données de détection d'erreur, soit des données de diagnostic, pour une utilisation comme données de détection d'erreur pendant des essais, envoyées par une unité d'envoi de données de diagnostic (1100), sur la base d'un état d'entrée d'un signal d'activation de génération de force,
    une étape de diagnose d'erreur pour effectuer la diagnose si la détection d'erreur à l'étape de détection d'erreur fonctionne anormalement, sur la base de la question de savoir si un résultat d'un contrôle de parité à l'étape de détection d'erreur de la chaîne de données à laquelle les données de diagnostic ont été ajoutées, correspond à une information d'erreur qui indique si les données de diagnose envoyées par l'unité d'envoi de données de diagnose (1100) rend un résultat d'une opération de parité effectuée sur la chaîne de données, normal ou anormal, et
    une étape de détermination pour déterminer que l'étape de commutation de données fonctionne normalement en réponse à une coïncidence entre la sortie des données de diagnose de l'unité d'envoi de données de diagnose (1100) et les données de détection d'erreur lues du deuxième appareil (1200) pendant que le signal de génération de force est activé et l'étape de commutation de données est commutée pour sortir les données de diagnose envoyées par l'unité d'envoi de données de diagnose comme les données de détection d'erreur à ajouter à la chaîne de données pour stockage dans le deuxième appareil, et, en outre, à une non-coïncidence entre la sortie des données de diagnose de l'unité d'envoi de données de diagnose et les données de détection d'erreur lues du deuxième appareil pendant que le signal de génération de force est désactivé et l'unité de commutation de données est commutée pour sortir les données de détection d'erreur engendrées à l'étape de génération de données de détection d'erreur comme les données de détection d'erreur à ajouter à la chaîne de données pour stockage dans le deuxième appareil,
    caractérisé en ce que l'étape de détermination détermine que l'étape de détection d'erreur fonctionne anormalement lorsque l'étape de détermination détermine que l'étape de commutation de données fonctionne normalement et l'étape de diagnose d'erreur détermine que la fonction de détection d'erreur fonctionne anormalement.
EP07119334.6A 2006-10-27 2007-10-25 Détecteur d'erreur et procédé de détection d'erreur Expired - Fee Related EP1916794B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2006293371A JP4652308B2 (ja) 2006-10-27 2006-10-27 エラー検出システム及びエラー検出方法

Publications (3)

Publication Number Publication Date
EP1916794A2 EP1916794A2 (fr) 2008-04-30
EP1916794A3 EP1916794A3 (fr) 2013-03-06
EP1916794B1 true EP1916794B1 (fr) 2015-12-23

Family

ID=39032226

Family Applications (1)

Application Number Title Priority Date Filing Date
EP07119334.6A Expired - Fee Related EP1916794B1 (fr) 2006-10-27 2007-10-25 Détecteur d'erreur et procédé de détection d'erreur

Country Status (3)

Country Link
US (1) US8122316B2 (fr)
EP (1) EP1916794B1 (fr)
JP (1) JP4652308B2 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102007028766A1 (de) * 2007-06-22 2008-12-24 Continental Teves Ag & Co. Ohg Prüfverfahren und elektronische Schaltung zur sicheren seriellen Übertragung von Daten
CN101938371B (zh) * 2009-06-30 2012-09-26 比亚迪股份有限公司 一种汽车报文配置处理系统及工作方法
WO2011021906A2 (fr) 2009-08-21 2011-02-24 Samsung Electronics Co., Ltd. Procédé et dispositif pour demander des données et procédé et dispositif pour obtenir des données
US9720950B2 (en) 2015-06-15 2017-08-01 International Business Machines Corporation Verification of record based systems
US9524205B1 (en) 2016-01-04 2016-12-20 International Business Machines Corporation Code fingerprint-based processor malfunction detection
JP2019168749A (ja) 2018-03-22 2019-10-03 ソニーセミコンダクタソリューションズ株式会社 記憶制御回路、記憶装置、撮像装置、および、記憶制御方法
CN111736878B (zh) * 2020-08-10 2020-12-08 广州汽车集团股份有限公司 一种对cpu连接ddr芯片的数据线异常进行定位的方法及系统

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4740971A (en) * 1986-02-28 1988-04-26 Advanced Micro Devices, Inc. Tag buffer with testing capability
US4794597A (en) * 1986-03-28 1988-12-27 Mitsubishi Denki Kabushiki Kaisha Memory device equipped with a RAS circuit
JPH02123631U (fr) * 1989-03-16 1990-10-11
US5515383A (en) * 1991-05-28 1996-05-07 The Boeing Company Built-in self-test system and method for self test of an integrated circuit
JPH0583847A (ja) 1991-09-20 1993-04-02 Fujitsu Ltd 電源ユニツトのアラーム検出装置
JP3158215B2 (ja) * 1991-10-04 2001-04-23 富士通株式会社 パリティ反転試験方式
JPH1078891A (ja) 1996-09-05 1998-03-24 Nec Corp ソフトウェアプログラム評価装置
US6397357B1 (en) * 1996-10-08 2002-05-28 Dell Usa, L.P. Method of testing detection and correction capabilities of ECC memory controller
US5908471A (en) * 1997-01-31 1999-06-01 Sun Microsystems, Inc Diagnostic arrangement for digital computer system
JPH10228389A (ja) * 1997-02-17 1998-08-25 Hitachi Ltd 故障検出診断装置
JP3039455B2 (ja) * 1997-06-30 2000-05-08 日本電気株式会社 半導体メモリ装置テスト方法及び半導体メモリ装置
US7155568B2 (en) * 2001-09-29 2006-12-26 Hewlett-Packard Development Company, L.P. Transaction generator for initialization, rebuild, and verify of memory
US7032142B2 (en) * 2001-11-22 2006-04-18 Fujitsu Limited Memory circuit having parity cell array
JP2003244187A (ja) 2002-02-19 2003-08-29 Denso Corp 車載ゲートウェイ装置およびコンピュータプログラム
JP3969129B2 (ja) 2002-03-08 2007-09-05 株式会社デンソー ゲートウェイおよび通信データの中継方法
JP3986898B2 (ja) 2002-06-20 2007-10-03 富士通株式会社 メモリ擬似故障注入装置
US6988237B1 (en) * 2004-01-06 2006-01-17 Marvell Semiconductor Israel Ltd. Error-correction memory architecture for testing production errors
JP2005215590A (ja) 2004-02-02 2005-08-11 Matsushita Electric Ind Co Ltd 液晶表示装置の駆動方法
DE102004021267B4 (de) * 2004-04-30 2008-04-17 Infineon Technologies Ag Verfahren zum Testen eines Speicherbausteins und Prüfanordnung
TWI289851B (en) * 2005-05-04 2007-11-11 Univ Tsinghua Semiconductor memory and method of correcting errors for the same
JP4768374B2 (ja) * 2005-09-16 2011-09-07 株式会社東芝 半導体記憶装置

Also Published As

Publication number Publication date
EP1916794A2 (fr) 2008-04-30
US8122316B2 (en) 2012-02-21
JP2008112224A (ja) 2008-05-15
EP1916794A3 (fr) 2013-03-06
JP4652308B2 (ja) 2011-03-16
US20080141074A1 (en) 2008-06-12

Similar Documents

Publication Publication Date Title
EP1916794B1 (fr) Détecteur d'erreur et procédé de détection d'erreur
US8027352B2 (en) Gateway apparatus and data managing method
EP1916813B1 (fr) Appareil d'accès et procédé de contrôle de transfert de données
US5727018A (en) Process for obtaining a signal indicating a synchronization error between a pseudo-random signal sequence from a transmitter and a reference pseudo-random signal sequence from a receiver
EP1718008A2 (fr) La passerelle et le procédé de routage.
EP1760939B1 (fr) Détection de faute dans une table de données d'un noeud de réseau
US20170134358A1 (en) Communication system, communication control device, and fraudulent information-transmission preventing method
JP5034703B2 (ja) Ｃａｎのエラー発生方法およびｃａｎ通信装置
US20110022936A1 (en) Sending device, receiving device, communication control device, communication system, and communication control method
JPH08163151A (ja) シリアル通信装置
CN112398672B (zh) 一种报文检测方法及装置
JP2009253464A (ja) ゲートウェイ装置及びゲートウェイ方法
US7802150B2 (en) Ensuring maximum reaction times in complex or distributed safe and/or nonsafe systems
JP5322433B2 (ja) 処理システムにおけるデータ処理中のエラー検知方法および制御システム
US7542412B2 (en) Self-routing, star-coupler-based communication network
JP2008072328A (ja) ゲートウェイｅｃｕの評価装置
US11558219B2 (en) Relay device
US20230412284A1 (en) Method for communicating information, receiver device, sensor device, and system
US20230231739A1 (en) Inspection apparatus and inspection method
JP3172120B2 (ja) 車両用電子制御装置試験システム
JP4219314B2 (ja) 通信装置
JP2914858B2 (ja) 交換スイッチの障害検出システム
JP2023104670A (ja) 検査装置及び検査方法
CN117997723A (zh) 故障定位方法、装置、车辆、服务器以及存储介质
JP2001211185A (ja) 非同期交換系統におけるデータセルの転送をチェックする方法、およびそのような方法に用いる基本交換装置およびネットワーク

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

AK Designated contracting states

Kind code of ref document: A2

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 MT NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: FUJITSU MICROELECTRONICS LIMITED

Owner name: FUJITSU TEN LIMITED

Owner name: RENESAS TECHNOLOGY CORP.

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: RENESAS TECHNOLOGY CORP.

Owner name: FUJITSU SEMICONDUCTOR LIMITED

Owner name: FUJITSU TEN LIMITED

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: FUJITSU TEN LIMITED

Owner name: RENESAS ELECTRONICS CORPORATION

Owner name: FUJITSU SEMICONDUCTOR LIMITED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 1/00 20060101AFI20121011BHEP

Ipc: G06F 11/22 20060101ALI20121011BHEP

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

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 MT NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 1/00 20060101AFI20130128BHEP

Ipc: G06F 11/22 20060101ALI20130128BHEP

17P Request for examination filed

Effective date: 20130902

RBV Designated contracting states (corrected)

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 MT NL PL PT RO SE SI SK TR

AKX Designation fees paid

Designated state(s): DE FR GB

17Q First examination report despatched

Effective date: 20131115

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602007044264

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0001000000

Ipc: H04L0001240000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 11/22 20060101ALI20150528BHEP

Ipc: H04L 1/00 20060101ALI20150528BHEP

Ipc: G06F 11/10 20060101AFI20150528BHEP

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 1/00 20060101ALI20150608BHEP

Ipc: G06F 11/10 20060101ALI20150608BHEP

Ipc: G06F 11/22 20060101ALI20150608BHEP

Ipc: H04L 1/24 20060101AFI20150608BHEP

INTG Intention to grant announced

Effective date: 20150623

RIN1 Information on inventor provided before grant (corrected)

Inventor name: FUJISAWA, YUKIO

Inventor name: EBESHU, HIDETAKA

Inventor name: NOUMI, KAORU

Inventor name: NISHIHASHI, SUSUMU

Inventor name: UMEZAKI, YASUYUKI

Inventor name: SHIMAUCHI, HIROAKI

Inventor name: KOIDE, SHIGEO

Inventor name: ISHIKAWA, YUKIO

Inventor name: KATOU, TOMOYUKI

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): DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602007044264

Country of ref document: DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602007044264

Country of ref document: DE

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

26N No opposition filed

Effective date: 20160926

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 602007044264

Country of ref document: DE

Owner name: DENSO TEN LIMITED, KOBE-SHI, JP

Free format text: FORMER OWNERS: FUJITSU SEMICONDUCTOR LIMITED, YOKOHAMA-SHI, KANAGAWA, JP; FUJITSU TEN LIMITED, KOBE-SHI, HYOGO, JP; RENESAS ELECTRONICS CORPORATION, KAWASAKI-SHI, KANAGAWA, JP

Ref country code: DE

Ref legal event code: R082

Ref document number: 602007044264

Country of ref document: DE

Representative=s name: HASELTINE LAKE KEMPNER LLP, DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 602007044264

Country of ref document: DE

Representative=s name: HL KEMPNER PATENTANWALT, RECHTSANWALT, SOLICIT, DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 602007044264

Country of ref document: DE

Representative=s name: HASELTINE LAKE LLP, DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 602007044264

Country of ref document: DE

Owner name: FUJITSU TEN LIMITED, KOBE-SHI, JP

Free format text: FORMER OWNERS: FUJITSU SEMICONDUCTOR LIMITED, YOKOHAMA-SHI, KANAGAWA, JP; FUJITSU TEN LIMITED, KOBE-SHI, HYOGO, JP; RENESAS ELECTRONICS CORPORATION, KAWASAKI-SHI, KANAGAWA, JP

Ref country code: DE

Ref legal event code: R081

Ref document number: 602007044264

Country of ref document: DE

Owner name: FUJITSU SEMICONDUCTOR LIMITED, YOKOHAMA-SHI, JP

Free format text: FORMER OWNERS: FUJITSU SEMICONDUCTOR LIMITED, YOKOHAMA-SHI, KANAGAWA, JP; FUJITSU TEN LIMITED, KOBE-SHI, HYOGO, JP; RENESAS ELECTRONICS CORPORATION, KAWASAKI-SHI, KANAGAWA, JP

Ref country code: DE

Ref legal event code: R081

Ref document number: 602007044264

Country of ref document: DE

Owner name: RENESAS ELECTRONICS CORPORATION, JP

Free format text: FORMER OWNERS: FUJITSU SEMICONDUCTOR LIMITED, YOKOHAMA-SHI, KANAGAWA, JP; FUJITSU TEN LIMITED, KOBE-SHI, HYOGO, JP; RENESAS ELECTRONICS CORPORATION, KAWASAKI-SHI, KANAGAWA, JP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602007044264

Country of ref document: DE

Representative=s name: HASELTINE LAKE LLP, DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 602007044264

Country of ref document: DE

Owner name: RENESAS ELECTRONICS CORPORATION, JP

Free format text: FORMER OWNERS: FUJITSU SEMICONDUCTOR LIMITED, YOKOHAMA-SHI, KANAGAWA, JP; FUJITSU TEN LIMITED, KOBE-SHI, HYOGO, JP; RENESAS ELECTRONICS CORPORATION, TOKIO/TOKYO, JP

Ref country code: DE

Ref legal event code: R081

Ref document number: 602007044264

Country of ref document: DE

Owner name: DENSO TEN LIMITED, KOBE-SHI, JP

Free format text: FORMER OWNERS: FUJITSU SEMICONDUCTOR LIMITED, YOKOHAMA-SHI, KANAGAWA, JP; FUJITSU TEN LIMITED, KOBE-SHI, HYOGO, JP; RENESAS ELECTRONICS CORPORATION, TOKIO/TOKYO, JP

Ref country code: DE

Ref legal event code: R082

Ref document number: 602007044264

Country of ref document: DE

Representative=s name: HASELTINE LAKE KEMPNER LLP, DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 602007044264

Country of ref document: DE

Representative=s name: HL KEMPNER PATENTANWALT, RECHTSANWALT, SOLICIT, DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602007044264

Country of ref document: DE

Representative=s name: HL KEMPNER PATENTANWALT, RECHTSANWALT, SOLICIT, DE

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20201022

Year of fee payment: 14

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602007044264

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