Expand description
SCCP/SPCP message identifiers and direction metadata for the message domain.
The numeric values are protocol facts. The catalog intentionally includes messages which this crate can only preserve opaquely today: knowing the ID is still useful for bounded forwarding and future typed implementations.
Start with MessageId when inspecting an unknown frame. Its
MessageId::contract links the numeric identifier to routing, payload
bounds, codec coverage, response selection, and field fidelity. Use
implemented_message_contracts to enumerate the typed subset.
Structs§
- Message
Contract - Machine-readable support record for one known message identifier.
- Payload
Size Bounds - Inclusive payload-size bounds, excluding the 12-byte frame header.
Enums§
- Codec
Support - How completely the public message model implements a catalog entry.
- Contract
Scope - Whether an identifier belongs to the base station-control inventory or an independently supported extension family.
- Contract
Verification - Verification depth for a wire contract.
- Emission
Support - Whether application code can construct a message without supplying raw wire bytes.
- Field
Fidelity - Whether all semantic wire fields survive typed decoding and re-encoding.
- Message
Direction - Legacy station-oriented view of the two handset message directions.
- Message
Id - A Skinny message identifier.
- Message
Route - The protocol roles between which a message is normally sent.
- Payload
Layout - The rule used to choose and bound a message payload layout.
- Response
Expectation - SCCP-level response expected for a request or media transaction.
- Runtime
Use - Present production/runtime role of a known message.
- Session
Response Selector - Session rule used to select a dynamic response identifier.
Functions§
- implemented_
message_ contracts - Iterates the complete typed implementation inventory in wire-ID order.