You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Attributes

Description

Type

New

Industry Sector

IoT

Business driver

There is currently no global specification for broad IoT interoperability, independent of the physical radio.   Moving the buffer to the Edge will allow stable QoS under any condition.  DQ is a universal lower MAC, therefore synchronous and asynchronous can share the channel, hence a seamless migration path.

Business use cases

1. Automotive

2. Industrial IoT

3. Smart City

Business Cost - Initial Build Cost Target Objective

There is no additional cost for utilizing a Distributed Queue (DQ) collision detection scheme, as it is a direct replacement or swap with Aloha-based technologies, requiring no change at OSI layers 2.5 or above. 

Experimental Zigbee and LoRa base stations with RasPi and a radio hat have been achieved for $85.

Business Cost – Target Operational Objective

The target operational objective is to achieve >95% throughput at all times, or Near-Perfect packet efficiency in a star network.  Some efficiency will be lost in the hybrid DQ model to afford a commercial migration path for legacy devices which have no knowledge of the novel MAC but this will still shatter the Aloha-based 50% maximum.

Security need

Security is a function of packet efficiency.  DQ allows to encrypt the whole packet at the MAC/Data Link layer including the packet header.  

Regulations

N/A

Other restrictions

N/A

Additional details

The hexadecimal address list from the DQWA Appendix can be made available.  It was only left out to make the document more manageable.

Case Attributes

Description

Type

New

Blueprint Family - Proposed   Name

Buffer at the Edge

Use Case

IoT

Blueprint proposed Name

Buffer at the Edge Blueprint Family: Swapping out Aloha-based MACs

Initial POD Cost (capex)

N/A

Scale & Type

Theoretcally infinite

Applications

Massive IoT with stable QoS

Power Restrictions

N/A

Infrastructure orchestration

Host:

•Any network hardware

SDN

N/A

Workload Type

N/A

Additional Details

N/A

Committer

Committer

Company

 Committer Contact Info

Committer Bio

Committer Picture

Self Nominate for PTL (Y/N)

Jonathan Gael
M2M Belljonathan@m2mbell.comGael looks forward to contributing the fully drawn specification for any engineer to build an interoperable DQ system.
N
Houda ChihiTunisie Telecomhouda.chihi@supcom.tn








Attributes

Description

Type

New

Industry Sector

IoT

Business driver

There is currently no global specification for broad IoT interoperability, independent of the physical radio.   Moving the buffer to the Edge will allow stable QoS under any condition.  DQ is a universal lower MAC, therefore synchronous and asynchronous can share the channel, hence a seamless migration path.

Business use cases

1. Automotive

2. Industrial IoT

3. Smart City

Business Cost - Initial Build Cost Target Objective

There is no additional cost for utilizing a Distributed Queue (DQ) collision detection scheme, as it is a direct replacement or swap with Aloha-based technologies, requiring no change at OSI layers 2.5 or above. 

Experimental Zigbee and LoRa base stations with RasPi and a radio hat have been achieved for $85.

Business Cost – Target Operational Objective

The target operational objective is to achieve >95% throughput at all times, or Near-Perfect packet efficiency in a star network.  Some efficiency will be lost in the hybrid DQ model to afford a commercial migration path for legacy devices which have no knowledge of the novel MAC but this will still shatter the Aloha-based 50% maximum.

Security need

Security is a function of packet efficiency.  DQ allows to encrypt the whole packet at the MAC/Data Link layer including the packet header.  

Regulations

N/A

Other restrictions

N/A

Additional details

The hexadecimal address list from the DQWA Appendix can be made available.  It was only left out to make the document more manageable.

Case Attributes

Description

Type

New

Blueprint Family - Proposed   Name

Buffer at the Edge

Use Case

IoT

Blueprint proposed Name

Buffer at the Edge Blueprint Family: Swapping out Aloha-based MACs

Initial POD Cost (capex)

N/A

Scale & Type

Theoretically infinite

Applications

Massive IoT with stable QoS

Power Restrictions

N/A

Infrastructure orchestration

Host:

•Any network hardware

SDN

N/A

Workload Type

N/A

Additional Details

N/A

Committer

Committer

Company

 Committer Contact Info

Committer Bio

Committer Picture

Self Nominate for PTL (Y/N)

Jonathan Gael
M2M Bell
Gael looks forward to contributing the fully drawn specification for any engineer to build an interoperable DQ system.
N












  • No labels