Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Jian Wu 0028

dblp:96/2744-28 · DBLP profile ↗
← Back
4ranked-venue papers
3as first author
0since 2021 · last 2007
—ORCID · conflict

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 2 · 1 first-authorComputer networks · 2 · 2 first-authorSecurity and privacy · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer networks
2 papers
Routing and switching · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Embedded and real-time systems · 54% Distributed systems · 23% Hardware reliability and fault tolerance · 23%

Topics — the 11 heaviest of 11, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Routing and switching
fault-tolerant routing
0.112007
Internet routing resilience to failures: analysis and implications · CoNEXT 2007
Routing and switching
inter-domain routing
0.112007
Internet routing resilience to failures: analysis and implications · CoNEXT 2007
Routing and switching › inter-domain routing
BGP
0.112005
Finding a Needle in a Haystack: Pinpointing Significant BGP Routing Changes in an IP Network · NSDI 2005
Routing and switching › routing dynamics
routing change detection
0.112005
Finding a Needle in a Haystack: Pinpointing Significant BGP Routing Changes in an IP Network · NSDI 2005
Routing and switching
routing dynamics
0.112005
Finding a Needle in a Haystack: Pinpointing Significant BGP Routing Changes in an IP Network · NSDI 2005
Distributed systems › fault tolerance › fault-tolerant real-time systems
fault-tolerant scheduling
0.012003
A Fault-Tolerant Scheduling Algorithm for Real-Time Periodic Tasks with Possible Software Faults · IEEE Trans. Computers 2003
Embedded and real-time systems › real-time scheduling
periodic task scheduling
0.012003
A Fault-Tolerant Scheduling Algorithm for Real-Time Periodic Tasks with Possible Software Faults · IEEE Trans. Computers 2003
Embedded and real-time systems
real-time scheduling
0.012003
A Fault-Tolerant Scheduling Algorithm for Real-Time Periodic Tasks with Possible Software Faults · IEEE Trans. Computers 2003
Hardware reliability and fault tolerance
software fault tolerance
0.012003
A Fault-Tolerant Scheduling Algorithm for Real-Time Periodic Tasks with Possible Software Faults · IEEE Trans. Computers 2003
Routing and switching › inter-domain routing
policy-based routing
0.012007
Internet routing resilience to failures: analysis and implications · CoNEXT 2007
Embedded and real-time systems › real-time scheduling › fixed-priority scheduling
fixed-priority preemptive scheduling
0.012003
A Fault-Tolerant Scheduling Algorithm for Real-Time Periodic Tasks with Possible Software Faults · IEEE Trans. Computers 2003

Methods — techniques the papers use, named apart from their topics

simulation · 0.1redundancy · 0.0deadline mechanism · 0.0
YearPublicationVenuePosition
2007 Internet routing resilience to failures: analysis and implications
abstract
Internet interdomain routing is policy-driven, and thus physical connectivity does not imply reachability. On average, routing on today's Internet works quite well, ensuring reachability for most networks and achieving reasonable performance across most paths. However, there is a serious lack of understanding of Internet routing resilience to significant but realistic failures such as those caused by the 911 event, the 2003 Northeast blackout, and the recent Taiwan earthquake in December 2006. In this paper, we systematically analyze how the current Internet routing system reacts to various types of failures by developing a realistic failure model, and then pinpoint reliability bottlenecks of the Internet. For validity of our simulation results, we generate topology graphs by addressing concerns over the incompleteness of topology and the inaccuracy of inferred AS relationships. By focusing on the impact of structural and policy properties, our analysis provides guidelines for future Internet design. The simulation tool we provide for analyzing routing resilience is also efficient to scale to Internet-size topologies.
Jian Wu 0028, Ying Zhang 0022, Z. Morley Mao, Kang G. Shin
CoNEXT1
2005 SMRP: Fast Restoration of Multicast Sessions from Persistent Failures
abstract
The growing reliance of networked applications on timely and reliable data transfer requires the underlying networking infrastructure to provide adequate services even in the presence of "persistent" failures (e.g., broken links/routers). It is much more difficult to meet this requirement for multicast sessions than for unicast communications because any on-tree component failure may often cause simultaneous service disruptions to multiple receivers. This paper presents a new multicast routing protocol, called the survivable multicast routing protocol (SMRP), which facilitates fast recovery of multicast sessions in face of persistent failures via local detour paths. Our evaluation results show that SMRP trades end-to-end delay and resource usage for short, and hence fast, recovery paths. For example, under a certain set of parameter values, SMRP shortens the recovery path by 20% with only a 5% increase of end-to-end delay and resource usage. Moreover, several design enhancements have made SMRP efficient, robust, flexible and scalable.
Jian Wu 0028, Kang G. Shin
DSN1
2005 Finding a Needle in a Haystack: Pinpointing Significant BGP Routing Changes in an IP Network
Jian Wu 0028, Z. Morley Mao, Jennifer Rexford, Jia Wang 0001
NSDI1
2003 A Fault-Tolerant Scheduling Algorithm for Real-Time Periodic Tasks with Possible Software Faults
abstract
A hard real-time system is usually subject to stringent reliability and timing constraints. One way to avoid missing deadlines is to trade the quality of computation results for timeliness, and software fault tolerance is often achieved with the use of redundant programs. A deadline mechanism which combines these two methods is proposed to provide software fault tolerance in hard real-time periodic task systems. We consider the problem of scheduling a set of real-time periodic tasks each of which has two versions: primary and alternate. The primary version contains more functions and produces good quality results, but its correctness is more difficult to verify. The alternate version contains only the minimum required functions and produces less precise results and its correctness is easy to verify. We propose a scheduling algorithm which 1) guarantees either the primary or alternate version of each critical task to be completed in time and 2) attempts to complete as many primaries as possible. Our basic algorithm uses a fixed priority-driven preemptive scheduling scheme to preallocate time intervals to the alternates and, at runtime, attempts to execute primaries first. An alternate will be executed only if necessary because of time or bugs.
Ching-Chih Han, Kang G. Shin, Jian Wu 0028
IEEE Trans. Computers3