computer science

Static Context Header Compression

Static Context Header Compression is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Static Context Header Compression rather than just read about it. In short: Static Context Header Compression (SCHC) is a standard compression and fragmentation mechanism defined in the IPv6 over LPWAN working group at the IETF. It offers compression and fragmentation of IPv6/UDP/CoAP packets to allow their transmission over the Low-Power Wide-Area Networks (LPWAN).

Key takeaways

Static Context Header Compression belongs to computer science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect Static Context Header Compression to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of Static Context Header Compression from memory before moving on to harder problems.

Reference excerpt

Static Context Header Compression (SCHC) is a standard compression and fragmentation mechanism defined in the IPv6 over LPWAN working group at the IETF. It offers compression and fragmentation of IPv6/UDP/CoAP packets to allow their transmission over the Low-Power Wide-Area Networks (LPWAN).

Compression scheme tailored to LPWAN

About LPWAN Low-Power Wide-Area Network (LPWAN) gathers the connectivity technologies tailored for Internet of Things (IoT), allowing for:

long-range communication (up to 40 km), very low energy consumption (on the device side), and energy efficiency (for networks). The trade-off for achieving these features includes severe limitation in terms of throughput and packet size supported. Also, LPWAN come with limitations on transmission modalities since, in order to save battery, devices are dormant most of the time and wake up only episodically to transmit and receive data for a short time window. As a result, the LPWAN use their specific protocols, each adapted to their own specificities. Most importantly, they cannot carry IPv6, which was designed to allocate addresses to the billions of IoT connected devices.

IETF compression standards In the early 2000s, the IETF produced the first wave of mature standards for compression and fragmentation:

RoHC (Robust Header Compression) in 2001, and 6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks) in 2007. Yet, these compression schemes cannot fit the LPWAN specificities. SCHC associates the benefits of the RoHC context, which provides high flexibility in the fields processing, and of the 6LoWPAN operations to avoid transiting fields that are known by the other side.

SCHC compression SCHC takes advantage of the LPWAN characteristics (no routing, highly predictable traffic format and content of messages) to reduce the overhead to a few bytes and save network traffic. The SCHC compression is based on the notion of context. A context is a set of rules that describes the communication context, meaning the header fields. It is shared and pre-provisioned in both the end-devices and the core network. The "static context" assumes that the rule description does not change during transmission. Thanks to this mechanism, IPv6/UDP headers are in most cases reduced to a small identifier.

SCHC fragmentation When compression is not enough, SCHC provides a fragmentation mechanism that works in 3 different ways:

No-Ack In this mode the SCHC packet is separated in multiple fragments that are blindly sent to the receiver, if the receiver missed any one packet then it won't be able to re build the sent packet.

Ack-On-Error In this mode the concept of "windows" is used, windows have a predefined size, allowing the receiver to keep a count of which windows or windows parts have been received, at the moment the receiver gets the last fragment from the sender it will calculate which parts of the packets it has missed and send a message describing that to the sender. The sender will then initialize the retransmission of the missing packet parts.

Ack-Always In Ack-Always mode the same retransmission mechanism as for Ack-On-Error is used except that it is not done at the end of the transmission but for each window.

Standardization efforts The Generic Framework for Static Context Header Compression and Fragmentation, RFC 8724 has been published in April 2020. It describes the generic framework that can be used on all LPWAN technologies, and more generally on all Internet networks. Additional work is dedicated to the definition of standard parameter settings and modes of operation to optimize SCHC's performance according to the implemented protocols and the underlying LPWAN technologies:

RFC 9011: SCHC over LoRaWAN RFC 8824: SCHC for CoAP RFC 9363: YANG Data Model for SCHC RFC 9391: SCHC over NB-IoT SCHC over Sigfox SCHC over IEEE 802.15.4 networks OAM for LPWAN using SCHC On May 17, 2022, The LoRa Alliance (global association of companies backing the open LoRaWAN® standard for the internet of things low-power wide-area networks) announced that LoRaWAN now seamlessly supports Internet Protocol version 6 (IPv6) from end-to-end. By expanding the breadth of device-to-application solutions with IPv6, LoRaWAN's addressable IoT market is also broadened to include internet based standards required in smart electricity metering and new applications in smart buildings, industries, logistics, and homes. The Alliance released a technical specification TS 10–1.0.0 to explain how to use SCHC as an adaptation layer to enable LoRaWAN end-devices to use IPv6-based stacks over LoRaWAN and expands its certification program to include SCHC over LoRaWAN® Enabling IPv6 Solutions. In addition, SCHC is being adopted in a joint standardization effort carried out by the DLMS User Association and the LoRa Alliance for the smart metering industries.

See also LPWAN: Low Power Wide Area Networks IPv6: Version 6 of the Internet Protocol 6LoWPAN: IPv6 over Low-Power Wireless Personal Area Networks RoHC: Robust Header Compression CoAP: Constrained Application Protocol

References

External links IPv6 over Low Power Wide-Area Networks (LPWAN) Working group at IETF RFC 8724 – SCHC: Generic Framework for Static Context Header Compression and Fragmentation RFC 9011 – SCHC over LoRaWAN RFC 8824 – SCHC for CoAP RFC 9363 – YANG Data Model for SCHC RFC 8376 – Low-Power Wide Area Network (LPWAN) Overview

Worked examples

Example 1 — a first encounter with Static Context Header Compression

Start with the simplest possible case. Write down what Static Context Header Compression claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Static Context Header Compression before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Static Context Header Compression ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Static Context Header Compression

In research: Static Context Header Compression appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses Static Context Header Compression in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: Static Context Header Compression is common in secondary-school and first-year university syllabi. It links to neighbouring topics Data compression, IPv6, Internet layer protocols, so understanding it makes those chapters shorter.
In everyday life: Look for Static Context Header Compression outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Static Context Header Compression in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what Static Context Header Compression means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain Static Context Header Compression out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Static Context Header Compression in simple terms?

Why does Static Context Header Compression matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Static Context Header Compression?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Static Context Header Compression.