RFID seeking: Finding a lost tag rather than only detecting its missing

Chen Zhang, Qiang Wang, Jian Xu, Lei Xie
2014
Journal paper

Abstract

This paper proposes a novel type of RFID application, i.e., RFID seeking. Several existing types of RFID applications such as monitoring, searching, locating/navigating, are similar with RFID seeking. However, they are either inapplicable or vulnerable for RFID seeking scenarios, in which a user is to find a lost tagged item in a blind spot, or to find a wanted item among a mass of similar ones. In this paper, detailed requirements for RFID seeking are suggested. The first secure RFID seeking protocol is proposed, meeting all the given requirements. Its security is formally verified by using the AVISPA tool. The proposed protocol is server-less, lightweight, privacy-friendly to both RFID readers and tags, and is secure against common attacks such as eavesdropping, manipulating, replaying, tracing, Denial of Service (DoS), etc.

Official source

https://infoscience.epfl.ch/record/201368?ln=en

About this result

This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.

Ontological neighbourhood

Systems science and engineering

Systems thinking: Systems engineering

Related concepts (25)

In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder.

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success or failure of a systems or software project.cite book |editor1= Alain Abran |editor2=James W.

In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours. They are contrasted with functional requirements that define specific behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture, because they are usually architecturally significant requirements.

Related publications (94)

RFID seeking: Finding a lost tag rather than only detecting its missing

Dynamical simulation via quantum machine learning with provable generalization

Lessons Learned from Data-Driven Building Control Experiments: Contrasting Gaussian Process-based MPC, Bilevel DeePC, and Deep Reinforcement Learning

A Reuse-Ready Timber Slab-and-Column System for Modular Building Structures

Dynamical simulation via quantum machine learning with provable generalization

Lessons Learned from Data-Driven Building Control Experiments: Contrasting Gaussian Process-based MPC, Bilevel DeePC, and Deep Reinforcement Learning

A Reuse-Ready Timber Slab-and-Column System for Modular Building Structures