Where SCTE-35 is the in-band cue marking "an ad break happens here", SCTE-224 is the out-of-band schedule and policy layer telling the system what should happen at that break. A typical SCTE-224 document includes: scheduled events (a baseball game on this date from this time), audience restrictions (this game blacked out in this market because of broadcast rights), action policies (replace national ads with local ads in this region), and contingency events (if a game runs long, this break should be moved).
SCTE-224 is the workflow language between content providers, broadcasters and distributors. A regional sports network uses it to communicate blackout rules to its MVPDs; a national broadcaster uses it to schedule ad replacement against its affiliates; an OTT service uses it to drive geo-fenced content rules. The SSAI server typically consumes both SCTE-35 cues (in-stream signals) and SCTE-224 metadata (out-of-band schedule) to make per-viewer manifest decisions.
In production, SCTE-224 lives between ad-decisioning servers, content management systems and SSAI servers. Most operators consume it via REST or file-drop interfaces from upstream content providers. The 2023 revision improved support for FAST channels, virtual MVPD use cases and dynamic event handling. SCTE-224 is less commonly discussed than SCTE-35 but equally essential for any operation that touches broadcast-style rights management.
