Coexistence of Thread/Matter (SSED) and BLE (PAwR) on nRF54L15

[Gilbert_J]

I am developing a proof-of-concept for remote controlled super-low-power devices using PAwR.
I started with nRF52840 (for boths, clients and remote) and now migrated my code the newer
nRF54L15 Platform (using holyiot24005 Modules).
All worked fine and i am impressed how energy saving a client can be designed.

The "cherry on the cake" - feature would have been to integrate my remote into Matter/Thread based home automation.

I have to admit i am definitely no matter expert and the topic seems to be quite complex, but my upfront research showed that a "Synchronous Sleepy End Device" that uses the same interval timing as my PAwR Train should be the right architecture to design a power efficient bridge between the two standards. Also from what i read the nRF54L15 should be capable to handle both timeslotted in "parallel".

Unfortunately i am now already struggeling with commissioning to my Matter Server. (currently with "DestinationAddressFiltered", but i don´t want to go too much into details now)

My questions are:

Is my assumption correct that the Chip should be able to handle this?
Is probably any special Multiprotocol configuration required?

Has anybody already tried to create a multi-protocol project running Matter/Thread and BLE/PAwR in parallel?

Is anybody aware of existing examples?

Would it make sense to migrate to the newest SDK?  (from the changelogs i´d say no...)

My Setup:

• Hardware: Holyiot-24005 module (nRF54L15)
• SDK: nRF Connect SDK v3.1.1
• Matter SDK: Integrated via NCS
• Border Router: Home Assistant with OpenThread Border Router (OTBR)
• Commissioning Method: CHIPoBLE (via Android Companion App)

Thanks for your help!

Best regards,
  Gilbert

[SwRa]

Hi Gilbert,

Your assumptions are more or less correct.. nRF54L15 can run Matter over Thread and BLE concurrently on a single SoC using the multiprotocol (System‑on‑Chip) design. Refer: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/matter/overview/integration.html#matter_platform_designs_system-on-chip_multiprotocol The radio time‑sharing is handled by the Multiprotocol Service Layer (MPSL). There have been discussions regarding this on Devzone, like this one:  Is it possible that running Matter_light and BLE peripheral_uart at the same time?  I am not sure about  PAwR‑specific coexistence though.. I will have to check this internally and get back to you. 

Regards,

Swathy

[Gilbert_J]

Thanks so far - would be great if you could get any additional information.

Regards,
  Gilbert

[SwRa]

Hi Gilbert,

Just confirmed with the team.. It should work. BLE always has priority and occupies the radio when there is some BLE event, and Thread/15.4 takes whatever is left. So it is advised to make sure not to spend too much time on the radio on BLE.

Could you provide some information on the radio pattern on BLE (like how long the packets are, how frequent etc.)?

Regards,

Swathy