[mac] make `Frame::ParseInfo` public and unify frame field access (#13543)

This commit refactors MAC frame parsing and field inspection across
the OpenThread stack by making `Frame::ParseInfo`, `RxFrame::ParseInfo`,
and `TxFrame::ParseInfo` public and deprecating/removing individual
getter methods directly on `Frame`.

Previously, `Frame` provided dozens of separate getter methods
(`GetDstAddr()`, `GetSrcAddr()`, `GetDstPanId()`, `GetSrcPanId()`,
`GetSecurityLevel()`, `GetKeyIdMode()`, `GetFrameCounter()`,
`GetCommandId()`, `GetPayload()`, `Find<IeType>()`, etc.). Calling
these methods repeatedly on the same frame resulted in multiple
parsing passes over the PSDU buffer. Furthermore, callback handlers
across `SubMac`, `Mac`, `MeshForwarder`, and various schedulers had to
re-query individual fields or maintain partial state independently.

This commit unifies frame parsing into a single-pass model:
- `ParseInfo` extracts and caches all relevant frame header fields,
  addresses, PAN IDs, security attributes, Header IEs, and payload/header
  boundaries during a single parse pass.
- Frame parsing and validation can be done incrementally using
  `ParseMode` (`kParseAddrFields`, `kParseSecurityHeader`, or
  `kParseFully`).
- Passing `ParseInfo` across layer boundaries eliminates redundant
  parsing operations and simplifies code across the codebase.
38 files changed
tree: 013009edecd61f1f12f022a1f309fa3b5ce382ad
  1. .gemini/
  2. .github/
  3. doc/
  4. etc/
  5. examples/
  6. include/
  7. script/
  8. src/
  9. tests/
  10. third_party/
  11. tools/
  12. zephyr/
  13. .clang-format
  14. .clang-tidy
  15. .codecov.yml
  16. .default-version
  17. .gitattributes
  18. .gitignore
  19. .gitmodules
  20. .gn
  21. .prettierrc
  22. AGENTS.md
  23. AUTHORS
  24. BUILD.gn
  25. CMakeLists.txt
  26. CMakePresets.json
  27. CODE_OF_CONDUCT.md
  28. CONTRIBUTING.md
  29. LICENSE
  30. NOTICE
  31. README.md
  32. SECURITY.md
  33. STYLE_GUIDE.md
README.md

OpenThread Ask DeepWiki


What is OpenThread?

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.4.0 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.

Who supports OpenThread?

Getting started

All end-user documentation and guides are located at openthread.io. If you're looking to do things like...

  • Learn more about OpenThread features and enhancements
  • Use OpenThread in your products
  • Learn how to build and configure a Thread network
  • Port OpenThread to a new platform
  • Build an application on top of OpenThread
  • Certify a product using OpenThread

...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.

Contributing

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.

License

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.

Need help?

OpenThread support is available on GitHub: