Module provider_server 

The OTA provider server (M9-F3): a dedicated task that advertises our operational service, accepts an inbound CASE session as the responder, and dispatches one server-side InvokeRequest. Productionizes the responder accept-flow proven in the actor’s loopback tests; hosts it in matter-controller so it can reuse the persisted operational identity (crate::credentials::operational_credentials) and the existing session / transport / discovery machinery without a new crate boundary.

Structs

ProviderServer

A multi-session OTA provider server: accepts inbound CASE sessions as the responder (one per pooled credential), then dispatches server-side InvokeRequests. Generic over the datagram transport so it runs over TokioUdpTransport in production and InMemoryDatagram in tests.

Functions

build_operational_service

Build the operational _matter._tcp mDNS record to advertise so a requestor can resolve us. Instance name is <compressed-fabric-id>-<node-id> in uppercase hex (Matter Core §4.3.1), matching what the controller’s initiator resolves against via operational_instance_name.