Miri Systems provides machine to machine authentication technology that can be tailored for specific industries. Authentication occurs either on demand or continuously between machines and can be one-way or two-way, with communication encrypted. Activation data is pushed directly from an institution's cloud to devices like drones and control stations. Each account acts as its own encoder/decoder.
1. Machine to Machine Authentication
Miri Systems machine to machine authentication technology can be tailored to
specific industries.
Authentication occurs on demand and/or continuously between machines.
Authentication can be one way or two way, both the controlling device
and the receiving device authenticate each other.
Communication can also be encrypted.
2. Example Drone Diagram – Activation data is pushed to devices
VIA
User Control Station Drone
Cell Phone Computer Tablet Controller
The activation data can be pushed directly from the Institutions
cloud to the Drone and Control Station. Every account created on a
device acts as it own encoder/decoder.
Seed Data Seed Data
3. Example Drone Diagram – One Way Mission Control Authentication
VIA
User Control Station encoder Drone decoder
Control Station generates MiriID
Cell Phone Computer Tablet Controller
Control MiriID submitted
Control station transmits MiriID to validate and
authenticate mission instructions. Process can
occur continuously or at specified intervals.
Default to pre-determined protocol
No Yes
Mission continues
4. Example Drone Diagram – One Way Drone Authentication
VIA
User Control Station decoder Drone encoder
Drone generates MiriID
Cell Phone Computer Tablet Controller
Drone submits MiriID
MiriID is validating and verifying the data stream from the Drone and maintains the
chain of custody for the data.
Default to pre-determined protocol
Yes
Mission continues
No
5. Point A request connection to
point C and identifies and
authenticates itself through
MiriID. Point C makes a web
service call to the Command
Center for validation.
MiriID can validate millions of
transactions. Each transaction
verification is completed in 2 – 4
milliseconds.
Successful authentication and
authorization level for point A is
communicated to point C and
two way communication
between A and C is established.
Authentication
Command Center
Data
Point A
Data
Point B
Data
Point C
Data
Point D
Data
Point E
Encoder
Encoder
Encoder Encoder
Encoder
Decoder
*Each Data Point represents a machine device.
**Networks can include thousands of data points.
Two Way Device Authentication
6. Two Way Device Authentication
Point A request connection to
point C and attempts to identify
and authenticate itself through
MiriID. Point C makes a web
service call to the Command
Center for validation. Validation
is not granted.
Authentication
Command Center
Data
Point A
Data
Point B
Data
Point C
Data
Point D
Data
Point E
Encoder
Encoder
Encoder Encoder
Encoder
Decoder
*Each Data Point represents a machine device.
**Networks can include thousands of data points.