What happens to DVB receivers when the 16-bit date counter rolls over in April 2038?

The counter that runs out

DVB transport streams carry dates as a 16-bit field. The field holds the least significant bits of the Modified Julian Date, a count of days since 17 November 1858. Sixteen bits cover 65 536 values. That range expires at midnight UTC on 23 April 2038. After that moment the transmitted value returns to zero.

Peter Cherriman of BBC R&D described the problem in DVB Scene issue 66 last September. BBC R&D and Nagra discovered it independently. They tested representative transport streams with dates near the rollover. Every tested receiver showed degraded behaviour. Receivers are likely to continue functioning for video and audio. Subtitles are likely to continue as well. Electronic programme guides are unlikely to work correctly. Age ratings and accessibility signalling face disruption. Internet connectivity fails when encrypted TLS traffic breaks because the receiver uses broadcast time to set its real-time clock. DRM schemes that rely on the broadcast date are also affected. The tests covered a small number of UK DVB-T/T2 receivers. The full impact across other markets is not yet known.

How the fix reuses the same 16 bits

No spare bits exist to widen the field. The solution keeps the 16-bit field but changes how receivers interpret it. Values 32 768 through 65 535 continue to represent MJDs from 5 August 1948 to 22 April 2038. Values 0 through 32 767 now represent MJDs from 23 April 2038 through 9 January 2127, calculated as MJD = value + 65 536. This approach mirrors a Y2K workaround where two-digit years 00–49 meant 2000–2049 and 50–99 meant 1950–1999. The new mapping buys at least 75 more years. A further extension is possible in roughly 50 years.

The guidance is now part of EN 300 468 V1.20.0. The specification is published as DVB BlueBook A038r19. It can be downloaded from the DVB Specification Library or the ETSI website.

What equipment needs changing

Headend systems that produce DVB-SI tables need no changes provided they already output the least significant 16 bits of the MJD correctly. Some headend and test equipment does not handle the rollover correctly. That means the issue reaches beyond receivers into many DVB systems. All of them will need fixes before 2038. Test streams used for the BBC experiments are available at dvb.org/date-teststreams for anyone who wants to verify device compatibility without a time machine.

Other clocks that roll over in the same year

2038 brings multiple rollovers. The 32-bit Unix and Linux timestamp rolls over in January. GPS experiences its third week-number rollover in November. The DVB-SI fix addresses only the broadcast date field. It does not address the Unix timestamp or the GPS week counter. Receivers that depend on those clocks for internal timekeeping will need separate updates. The specification does not say how many deployed devices currently handle any of these rollovers correctly.