• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 482 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL-CC1352P: BLE MESH BEACON STRUCTURE

Rushiraj Sheth
Prodigy 10 points
Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: CC1352P, CC2642R

Hello !

I am currently working on a project involving the study and implementation of BLE MESH network using TI development kit.

Can you please provide the detailed structure of BLE MESH PACKET / MESH BEACON STRUCTURE ?

Thanks and Regards,

Rushiraj Sheth.

  • 0
    TI__Guru** 101490 points

    Hi,

    Thank you for reaching out.

    If I may, I am not sure the Bluetooth Mesh examples are available for the CC1352P devices. I would rather suggest to start the evaluation using CC2642R.

    I have asked an expert to provide more in depth answer.

    Best regards,

  • 0 in reply to Clément
    Prodigy 10 points

    Thank you for replying.

    Actually, I already ran the simple mesh node example provided in the package. So, possibly, the mesh examples are supported but in order to understand what information is delivered during broadcasting, I need to understand mesh beacon structure (how the mesh beacon structure looks like).

    Here's the link to simple mesh node example: TI Bluetooth Mesh Fundamentals

    Hoping for a positive reply !

    Thanks and Regards,

    Rushiraj Sheth.

  • +1 in reply to Rushiraj Sheth
    TI__Mastermind 25810 points

    Hey Rushiraj,

    Great question! There are a few different factors to your question, and I'll try to address them. Please let me know if you have any follow up questions.

    • Bluetooth Mesh defines both Control messages and Access messages. Control messages are like network messages. Access messages are essentially application payloads. For this response, I will cover access message payloads.
    • Within access payloads, you can have a segmented or unsegmented payload.
    • Each payload must use an op code (1, 2 or 3 bytes long). If you are using Bluetooth SIG defined models, then you may have a 1 or 2 byte long op code depending on the model chosen. All vendor/custom models must use a 3 byte long op code.
    • There is additional overhead of 4 bytes to transmit the TransMIC, required for authenticating the payload.

    I would refer you to visit the Mesh Profile specification, Section 3.7.3 Access payload to see a summary of what I described above. Table 3.42 describes the maximum "useful" payload sizes. In short, an unsegmented payload can be up to 11 bytes long, and a segmented payload can be up to 8 bytes long per segment.

    I hope this helps. There are other types of payloads sent in a Mesh network, like Secure Network Beacons and other messages to maintain the network. These are handled by the Zephyr stack, so an application developer shouldn't worry too much on that.

    P.S.: To clarify on the thread: we do support the CC1352P device.

  • 0 in reply to Ammar N
    Prodigy 10 points

    This information is really helpful !

    Thanks a lot! As suggested by you, I will refer the Mesh Profile Specification and will let you know in case of any further questions.

    Thanks and Regards,

    Rushiraj Sheth.