commit | 201b7b1a3d337bd1afaa97880f32c3cca77cf283 | [log] [tgz] |
---|---|---|
author | Jintao Lin <jintaolin@google.com> | Thu Jun 04 13:09:16 2020 +0800 |
committer | GitHub <noreply@github.com> | Wed Jun 03 22:09:16 2020 -0700 |
tree | 2c132ef445046ab5e2092c403b9472ca2448f5d0 | |
parent | 72c369ced30b9059f22155f37fbcb2b1deba0620 [diff] |
[mac] move auxiliary frame counter from Mac to SubMac (#4976) In Thread 1.2, it is possible to receive an IEEE 802.15.4-2015 packet. Per specification, receiver should acknowledge this packet with an IEEE 802.15.4-2015 ACK(Enh-ACK). This Enh-ACK can include header IE with it and requires security enabled bit in FCF be set to true. It is impractical for the host to generate the Enh-ACK and send to RCP for transmission within AIFS time(192us). So RCP should prepare the Enh-ACK by itself, which requires it to fill in the frame counter and do the encryption/authentication. This commit tries to address the need of filling auxiliary frame counter in RCP by including the following changes: - Move frame counter related functions from MAC layer to SubMac layer, which is mirrored in RCP. - Set mMacFrameCounter to RCP using newly added spinel properties. - RCP reports last used frame counter to host in TxDone and RxDone. - Add a simulation test for reset verification.
OpenThread released by Google is...
...an open-source implementation of the Thread networking protocol. Google Nest has released OpenThread to make the technology used in Nest products more broadly available to developers to accelerate the development of products for the connected home.
...OS and platform agnostic, with a narrow platform abstraction layer and a small memory footprint, making it highly portable. It supports both system-on-chip (SoC) and network co-processor (NCP) designs.
...a Thread Certified Component, implementing all features defined in the Thread 1.1.1 specification, including all Thread networking layers (IPv6, 6LoWPAN, IEEE 802.15.4 with MAC security, Mesh Link Establishment, Mesh Routing) and device roles, as well as Border Router support.
More information about Thread can be found at threadgroup.org. Thread is a registered trademark of the Thread Group, Inc.
All end-user documentation and guides are located at openthread.io. If you're looking to do things like...
...then openthread.io is the place for you.
Note: For users in China, end-user documentation is available at openthread.google.cn.
If you're interested in contributing to OpenThread, read on.
We would love for you to contribute to OpenThread and help make it even better than it is today! See our Contributing Guidelines for more information.
Contributors are required to abide by our Code of Conduct and Coding Conventions and Style Guide.
OpenThread follows the Semantic Versioning guidelines for release cycle transparency and to maintain backwards compatibility. OpenThread's versioning is independent of the Thread protocol specification version but will clearly indicate which version of the specification it currently supports.
OpenThread is released under the BSD 3-Clause license. See the LICENSE
file for more information.
Please only use the OpenThread name and marks when accurately referencing this software distribution. Do not use the marks in a way that suggests you are endorsed by or otherwise affiliated with Nest, Google, or The Thread Group.
There are numerous avenues for OpenThread support:
openthread
tagThe openthread-users Google Group is the recommended place for users to discuss OpenThread and interact directly with the OpenThread team.