UWB (IEEE802.15.4) Radio Mac Layer

[velag...@pathpartnertech.com]

Hi,

Please correct me if I am wrong. OpenThread is developed in compatible with IEEE802.15.4-2006 standard that means it can't support IEEE802.15.4-2011 standard networks like UWB. My object is to write a communication centric MAC layer between openthread and a UWB radio PHY in RIOT-OS. Can anybody guide me on this.


Regards,
jayaram.

[Jonathan Hui]

The Thread protocol is only specified for use on IEEE 802.15.4-2006.  That said, I do believe OpenThread could be used on top of alternative IEEE 802.15.4 PHYs.  However, those adaptations would not be Thread-compliant.

If you want to experiment, I would suggest looking at OpenThread's radio interface.  If you can provide project the UWB PHY capabilities through OpenThread's radio interface, then you would have a very good chance of reaching your goal.

Hope that helps.

--

Jonathan Hui

This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/bca118c8-4e15-437d-aa0f-fdff12e357eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[velag...@pathpartnertech.com]

thank you Jonathan Hui. So, I can assume that there is a provision to develop a MAC layer for new phy device which is compliant with IEEE802.15.4. Correct me If I am wrong.

And Jonathan need a help to start with openthread. I am planning to work on SAMR21 board. Do operating system is necessary to work on openthread? Does it uses OS services? Is it possible to implement on bare metal??

Regards,
jayaram

On Friday, February 3, 2017 at 11:31:53 AM UTC+5:30, Jonathan Hui wrote:

The Thread protocol is only specified for use on IEEE 802.15.4-2006.  That said, I do believe OpenThread could be used on top of alternative IEEE 802.15.4 PHYs.  However, those adaptations would not be Thread-compliant.

If you want to experiment, I would suggest looking at OpenThread's radio interface.  If you can provide project the UWB PHY capabilities through OpenThread's radio interface, then you would have a very good chance of reaching your goal.

Hope that helps.

--

Jonathan Hui

On Thu, Feb 2, 2017 at 9:32 PM, <velag...@pathpartnertech.com> wrote:

Hi,

Please correct me if I am wrong. OpenThread is developed in compatible with IEEE802.15.4-2006 standard that means it can't support IEEE802.15.4-2011 standard networks like UWB. My object is to write a communication centric MAC layer between openthread and a UWB radio PHY in RIOT-OS. Can anybody guide me on this.


Regards,
jayaram.

This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.

[Jonathan Hui]

I believe IEEE 802.15.4-2011 shares the same MAC layer across both O-QPSK and UWB PHYs, so I don't see a need to implement a new MAC layer.

All of the OpenThread examples run on bare metal.  However, OpenThread does not preclude use of an operating system.  In fact, I'm aware of OpenThread being used in FreeRTOS, RIOT-OS, Linux, and Windows.

--

Jonathan Hui

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/cc3b39a3-8c9d-4278-a73f-1fc32a840f58%40googlegroups.com.

[velag...@pathpartnertech.com]

Ok. Can I get any description or tutorial about how openthread is communicating with the PHY.

Regards,
jayaram

Jonathan Hui

[Jonathan Hui]

As mentioned below, please see the OpenThread radio interface and OpenThread example platforms that provide example implementations of that interface for different IEEE 802.15.4 platforms.

--

Jonathan Hui

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/16ac9efa-49a8-439a-8a95-3632378961f2%40googlegroups.com.

[velag...@pathpartnertech.com]

Thank you jonathan, I will go through them and will get back to you if I need any further clarifications.

Jonathan Hui

[Vinoth Kumar]

Hi Jayaram,

The platform abstraction of open thread is very clean and it is to the point. Have a look at files pointed by Jonathan and compare between cc2538 and posix, you will get more idea.

[velag...@pathpartnertech.com]

Hi Jonathan Hui,

Apart from Radio interface, will there be any changes required in "openthread-master/src/core/mac" as I observed this mac is developed for IEEE802.15.4-2006.

Thanks & Regards,
jayaram

[Jonathan Hui]

Hi Jayaram,

The MAC layer between IEEE 802.15.4-2006 and -2011 should be very similar, if not identical, especially considering the small subset that Thread actually uses.

Are there diffs in the -2011 MAC that you have in mind?

--

Jonathan Hui

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/d91175d0-99e9-4a42-b278-8618e702c2d2%40googlegroups.com.

[velag...@pathpartnertech.com]

I am going through the standard docs http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf
and http://standards.ieee.org/getieee802/download/802.15.4-2006.pdf

In MAC services currently I didn't see any differences between them. So, I hope touching the MAC core implementation in openthread is not necessary. Still I will dig more and let you know. Currently I will go with Radio Layer implementation for the PHY.

Thanks & Regards,

 (jayaram)

Jonathan Hui

[velag...@pathpartnertech.com]

Thank you vinodh.

I need help from you. To evaluate openthread functionality what I need. Which boards are fully functional as per Openthread standard? I need to purchase one of TI,Nordic and DIalog boards. I need suggestion to select the board which is fully functional.

Regards,
jayaram

[velag...@pathpartnertech.com]

Hi Jonathan Hui,

May I know which platform is better to test full functionality of OpenThread? Either CC2538 or nrF52840. Could you suggest one of them?

Thanks & Regards,

jayaram 

[Jonathan Hui]

Hi Jayaram,

The CC2538 is what we used to achieve the initial Thread 1.1 Certification announced here.

At the same time, the nRF52840 is very capable and should have no issue getting certified.  I'm confident the Nordic team will help if you run into any issues.

--

Jonathan Hui

This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/5c88643e-73a9-48f4-bbb6-19c751d2704e%40googlegroups.com.

[velag...@pathpartnertech.com]

Thank you Jonathan.

On Friday, February 10, 2017 at 10:43:33 PM UTC+5:30, Jonathan Hui wrote:

Hi Jayaram,

The CC2538 is what we used to achieve the initial Thread 1.1 Certification announced here.

At the same time, the nRF52840 is very capable and should have no issue getting certified.  I'm confident the Nordic team will help if you run into any issues.

--

Jonathan Hui

On Thu, Feb 9, 2017 at 4:31 AM, <velag...@pathpartnertech.com> wrote:

Hi Jonathan Hui,

May I know which platform is better to test full functionality of OpenThread? Either CC2538 or nrF52840. Could you suggest one of them?

Thanks & Regards,

jayaram 

On Friday, February 3, 2017 at 11:02:44 AM UTC+5:30, velag...@pathpartnertech.com wrote:

Hi,

Please correct me if I am wrong. OpenThread is developed in compatible with IEEE802.15.4-2006 standard that means it can't support IEEE802.15.4-2011 standard networks like UWB. My object is to write a communication centric MAC layer between openthread and a UWB radio PHY in RIOT-OS. Can anybody guide me on this.


Regards,
jayaram.

This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.

[velag...@pathpartnertech.com]

Hi Jonathan Hui,

I am almost near to complete adding uwb radio to openthread environment. Facing few issues with ping. Please check the following link for the topic in the group.

https://groups.google.com/d/topic/openthread-users/TLW-Dn6s77I/discussion

I need your valuable inputs for the issue mentioned in the discussion.

Thankyou.

Regards,
Jayaram.

[velag...@pathpartnertech.com]

Hi Jonathan,

 

   I have successfully integrated UWB radio (IEEE802.15.4-2011) with openthread on Nordic Platform (nRF52840) and tested all the CLI and NCP commands. 
   

   Now, my plan is to add ranging primitives(as per standard) as a mac sub layer. In current openthread implementation there are no mac primitives, no MLME ofcourse. What will be    the effect on above layers if we add mac primitives as per IEEE802.15.4 standard?

   And does thread specification point about MAC full compliance with IEEE802.15.4 standard?

    

Regards,
jayaram.

[Jonathan Hui]

On Fri, Jun 2, 2017 at 1:19 AM <velag...@pathpartnertech.com> wrote:

Hi Jonathan,

 

   I have successfully integrated UWB radio (IEEE802.15.4-2011) with openthread on Nordic Platform (nRF52840) and tested all the CLI and NCP commands. 

Great to hear!

   Now, my plan is to add ranging primitives(as per standard) as a mac sub layer. In current openthread implementation there are no mac primitives, no MLME ofcourse. What will be    the effect on above layers if we add mac primitives as per IEEE802.15.4 standard?

I would treat ranging as a feature outside the scope of Thread.  With that in mind, can the ranging hooks be provided via a platform-specific API?  In other words, the UWB radio driver would effectively have two clients (OpenThread and ranging).

   And does thread specification point about MAC full compliance with IEEE802.15.4 standard?

Thread 1.1 Chapter 3 specifies the IEEE 802.15.4 PHY/MAC requirements.  Note that Thread uses a small subset of IEEE 802.15.4-2006 MAC and does not require a device to provide a full IEEE 802.15.4-2006 MAC implementation.

--
Jonathan Hui

[velag...@pathpartnertech.com]

Thank you Jonathan,

Is it permitted to add ranging as a capability of the radio? such that after reading about the radio capability, MAC layer will enable the ranging related primitives (if we include). Also it will let openthread MAC supporting IEEE802.15.4-2011 standard.

[velag...@pathpartnertech.com]

Thank you Jonathan,

Is it permitted to add ranging as a capability of the radio? such that after reading about the radio capability, MAC layer will enable the ranging related primitives (if we include). Also it will let openthread MAC supporting IEEE802.15.4-2011 standard.

On Saturday, June 3, 2017 at 3:40:07 AM UTC+5:30, Jonathan Hui wrote:

[Jonathan Hui]

Hi Jayaram,

Ranging is currently a feature that is outside the scope of Thread.  From what I understand, the IEEE 802.15.4 ranging feature is primarily a PHY function and collection of timestamp reports.

What I had proposed previously is to add a shim between the radio driver and OpenThread that allows the ranging feature to be added on the side.  Is that a workable solution for you?

--

Jonathan Hui

This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/a9b856c8-62f8-4e93-a651-63644f39532e%40googlegroups.com.

[velag...@pathpartnertech.com]

May I know what is "shim" which you have mentioned in previous comment. And yes, I will try considering thread and ranging as two clients for UWB.

Thanks & Regards,
Jayaram.

[velag...@pathpartnertech.com]

Hi Jonathan,

Now we are interested to do upstream UWB related code to OpenThread. I need your suggestions here. The current UWB radio which I am working doesn't have MCU (microncontroller unit) inbuilt. So, I am using an existing platform in OpenThread and interfacing UWB radio with SPI lines. Added all UWB related driver code in thirdparty, created a separate radio.c and also created a seperate makefile.

I have gone through contributing.md. In my case I have only radio but not platform. So, how can I proceed further? Could you please guide me.

Regards,

Jayaram.

On Saturday, June 3, 2017 at 3:40:07 AM UTC+5:30, Jonathan Hui wrote: