2019
DOI: 10.1007/978-3-030-23425-6_2
|View full text |Cite
|
Sign up to set email alerts
|

An Instruction Set Architecture for Secure, Low-Power, Dynamic IoT Communication

Abstract: This chapter presents an instruction set architecture (ISA) dedicated to the rapid and efficient implementation of single-channel IoT communication interfaces. The architecture is meant to provide a programming interface for the implementation of signaling protocols based on the recently introduced pulsed-index schemes. In addition to the traditional aspects of ISA design such as addressing modes, instruction types, instruction formats, registers, interrupts, and external I/O, the ISA includes special-purpose … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
2

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 7 publications
0
1
0
Order By: Relevance
“…Currently there is no unified IoT firmware architecture [ 129 ] and, although there are commercial reasons behind their inherent variability, having a unified architecture would make security analysis significantly easier. Unification also requires translation, interpretation, and mapping to associate any abstract (IoT-specific) commands to multiple underlying architectures allowing greater automation [ 145 ]. Firmware vendors must also agree to a unified machine-independent stack for firmware development in order to have greater standardization.…”
Section: Contemporary Research and Open Challengesmentioning
confidence: 99%
“…Currently there is no unified IoT firmware architecture [ 129 ] and, although there are commercial reasons behind their inherent variability, having a unified architecture would make security analysis significantly easier. Unification also requires translation, interpretation, and mapping to associate any abstract (IoT-specific) commands to multiple underlying architectures allowing greater automation [ 145 ]. Firmware vendors must also agree to a unified machine-independent stack for firmware development in order to have greater standardization.…”
Section: Contemporary Research and Open Challengesmentioning
confidence: 99%