2008
DOI: 10.1109/tns.2008.2001742
|View full text |Cite
|
Sign up to set email alerts
|

Specification and Verification of Soft Error Performance in Reliable Internet Core Routers

Abstract: This paper presents a methodology for developing a specification for soft error performance of an integrated hardware/ software system that must achieve highly reliable operation. The methodology enables tradeoffs between reliability and cost to be made during the early silicon design and SW architecture phase. An accelerated measurement technique using neutron beam irradiation is also described that ties the final system performance to the reliability model and specification. The methodology is illustrated fo… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2008
2008
2019
2019

Publication Types

Select...
7

Relationship

0
7

Authors

Journals

citations
Cited by 13 publications
(3 citation statements)
references
References 14 publications
0
3
0
Order By: Relevance
“…To better understand the impact of soft errors and the effects of different chip level and system level mitigation strategies, we classify the SEU impact for networking system into five user-experienced outage time zones. They are: No-outage, Low Impact (Low), Medium Impact (Medium), High Impact (High) and Unrecoverable zones [2].…”
Section: System Level Mitigation Methodsmentioning
confidence: 99%
“…To better understand the impact of soft errors and the effects of different chip level and system level mitigation strategies, we classify the SEU impact for networking system into five user-experienced outage time zones. They are: No-outage, Low Impact (Low), Medium Impact (Medium), High Impact (High) and Unrecoverable zones [2].…”
Section: System Level Mitigation Methodsmentioning
confidence: 99%
“…Many critical bits that are used by a design will not cause functional failure if upset. The effect of some CRAM upsets may be masked by the timing, logic, and the current state of the design [24]. A soft error occurring too late in a clock cycle to be latched into memory, or an upset in a register whose value will be over written before it is used are examples of temporal masking.…”
Section: Architectural Vulnerability Factormentioning
confidence: 99%
“…The software layer (i.e., firmware, system and application software) is a key element of a complex digital system and plays a key role from the reliability standpoint [14]. While raw errors are generated at the technology level due to undesired effects such as ageing, environmental stress, variability etc., many detectable errors can be gracefully managed by correct software handling and a significant portion of the undetectable errors may be masked, depending on the application.…”
Section: Software Components Characterizationmentioning
confidence: 99%