SCHC

SCHC
Name	SCHC
Full name	Static Context Header Compression
Developed by	IETF Internet Engineering Task Force
Initial release	2018
Status	Active
Related	6LoWPAN, IPv6, RPL (Routing Protocol for Low-Power and Lossy Networks), LoRaWAN, NB-IoT

SCHC Static Context Header Compression (SCHC) is a family of standards and mechanisms designed to enable efficient transmission of IPv6 and UDP/CoAP-based payloads over highly constrained wide-area and low-power networks such as LoRaWAN, NB-IoT, and other low-power wide-area network technologies. It reduces header overhead by using a shared, static context and supports fragmentation for payloads larger than link MTU. SCHC was specified in standards produced by the Internet Engineering Task Force and has been referenced in multiple profiles and implementations in the 3rd Generation Partnership Project, industrial consortia, and open-source projects.

Overview

SCHC provides a compression and fragmentation framework tailored for environments where endpoints and network technologies impose severe constraints on packet size, duty cycle, and energy consumption. It targets deployments involving devices from vendors like Semtech, STMicroelectronics, Nokia, and Huawei reaching back to core networks operated by carriers such as Orange (telecommunications), Vodafone, and Telefonica. SCHC leverages static, pre-provisioned contexts shared between endpoints (device and network) to encode common header fields of protocols including IPv6, UDP, CoAP, and application-layer identifiers into compact rule IDs. The approach complements other IETF work such as 6LoWPAN and routing stacks like RPL (Routing Protocol for Low-Power and Lossy Networks).

Technical Specification

The SCHC technical specification defines a rule-based compression model where each rule binds a sequence of header fields to an encoding action. Rules are identified by a Rule ID included in compressed packets; rule tables are provisioned out-of-band using management protocols or device provisioning workflows involving vendors like Cisco Systems, Ericsson, and AT&T. The specification describes field properties (directionality, matching operators), actions (not-sent, value-sent, mapping), and bit-level encoding formats. It also defines fragmentation headers, windowing, and retransmission behaviors. SCHC documents in the IETF Working Group detail profiles and examples using UDP, CoAP, 6LoWPAN, and link technologies such as LoRaWAN and NB-IoT.

Fragmentation and Compression Mechanisms

SCHC separates compression from fragmentation. Compression maps header fields to compact representations using the static context; fragmentation splits oversized datagrams into fragments compliant with link MTUs imposed by technologies like LoRaWAN and Sigfox. The fragmentation mechanism specifies modes such as No-ACK, ACK-on-Error, and ACK-Always, with tile, window, and CRC constructs for loss detection, inspired by techniques used in ARQ and selective-repeat protocols seen in broader networking standards. Fragment headers include a Rule ID and a Compression Residue Indicator; recovery procedures reference rule state maintained by endpoints and gateways implemented by vendors like Semtech and network operators including The Things Network.

Protocol Stack and Implementations

SCHC operates at the adaptation layer sitting between IPv6/transport protocols and link layers like LoRaWAN MAC or NB-IoT bearers. Implementations exist in embedded SDKs provided by companies such as STMicroelectronics and open-source stacks from projects like Contiki-NG and Zephyr Project. Commercial IoT platforms from AWS IoT and Azure IoT provide integration guides for SCHC-enabled devices through gateways that translate between constrained links and core IP networks. Gateway implementations often combine compression modules with radio drivers for chipsets from Semtech, Texas Instruments, and NXP Semiconductors.

Security and Privacy Considerations

Because SCHC relies on shared static contexts, secure provisioning and lifecycle management of rule tables are critical; compromised contexts can lead to misrouting or denial-of-service scenarios reminiscent of issues discussed in standards bodies like IETF security mailing lists. On links such as LoRaWAN where link-layer security exists (e.g., network and application session keys managed per LoRaWAN specification), SCHC compression must be applied either before encryption at the gateway or within end devices to preserve confidentiality and integrity. Threat models consider replay, tampering, and context desynchronization attacks; mitigations include authenticated provisioning processes used by vendors like NXP Semiconductors and operators such as Orange (telecommunications) and cryptographic protections standardized by IETF.

Use Cases and Deployments

Common SCHC use cases include smart metering, asset tracking, environmental monitoring, and industrial telemetry deployed by utilities such as Enel and logistics firms like DHL. Public deployments and pilots have been conducted by research organizations including CEA and universities participating in projects with EURECOM and T-Labs (Deutsche Telekom); industry pilots often involve integration with network providers like Vodafone and cloud platforms from Microsoft and Amazon. SCHC enables constrained devices to interact with IoT application servers using CoAP or constrained MQTT variants via gateways that perform protocol translation and compression.

Performance and Interoperability Studies

Empirical studies published in workshops and conferences (e.g., IEEE International Conference on Communications, ACM/IEEE IPSN) compare SCHC performance against header compression schemes like RFC 4944 adaptations and evaluate metrics such as compression ratio, energy consumption, latency, and packet loss under varying link conditions. Interoperability events and plugfests organized by consortia such as the LoRa Alliance and GSMA include SCHC test cases combining implementations from vendors including Semtech, STMicroelectronics, Nokia, and open-source projects like Contiki-NG. Results show substantial header-size reductions for common telemetry payloads and identify trade-offs in fragmentation retransmission modes on high-latency, duty-cycle-limited networks.

Category:Internet protocols