The latest development version of this page may be more current than this released 3.7.0 version.

Solicitation PDU RPL Configuration Server

The Solicitation PDU RPL Configuration Server model is a foundation model defined by the Bluetooth mesh specification. The model is enabled if the node has the On-Demand Private Proxy Server enabled.

The Solicitation PDU RPL Configuration Server model was introduced in the Bluetooth Mesh Protocol Specification version 1.1, and manages the Solicitation Replay Protection List (SRPL) saved on the device. The SRPL is used to reject Solicitation PDUs that are already processed by a node. When a valid Solicitation PDU message is successfully processed by a node, the SSRC field and SSEQ field of the message are stored in the node’s SRPL.

The Solicitation PDU RPL Configuration Server does not have an API of its own, and relies on a Solicitation PDU RPL Configuration Client to control it. The model only accepts messages encrypted with an application key as configured by the Configuration Client.

If present, the Solicitation PDU RPL Configuration Server model must only be instantiated on the primary element.

Configurations

For the Solicitation PDU RPL Configuration Server model, the CONFIG_BT_MESH_PROXY_SRPL_SIZE option can be configured to set the size of the SRPL.

API reference

group bt_mesh_sol_pdu_rpl_srv

Defines

BT_MESH_MODEL_SOL_PDU_RPL_SRV

Solicitation PDU RPL Server model composition data entry.