Description
OBS (Output Bit Stream) is a term used in 3GPP security specifications to denote the output bit stream generated by cryptographic algorithms, such as those used for encryption, integrity protection, and key derivation. It appears in specifications like 26.955, 33.771, 35.240, 35.243, and 35.246, which cover security assurance, test vectors, and algorithm specifications. OBS is not a standalone technology but a fundamental concept in defining and verifying the correct operation of security functions.
In cryptographic algorithm specifications, the output bit stream is the result of applying a cryptographic function to an input (e.g., plaintext, key, or parameters). For example, in the 3GPP confidentiality and integrity algorithms (e.g., NEA, NIA), the output bit stream is the ciphertext or the integrity tag. These bit streams are precisely defined in test vector documents to allow implementers to validate their implementations against known-good outputs. OBS thus serves as a reference for conformance testing and interoperability.
The term is particularly relevant in the context of 3GPP security assurance specifications (SCAS) and algorithm test specifications. For instance, 3GPP TS 33.771 defines the security assurance methodology for 5G, while TS 35.240, 35.243, and 35.246 provide test vectors for 5G security algorithms. In these documents, OBS is used to describe the expected output of a cryptographic operation under given input conditions. This enables vendors and operators to verify that their security implementations are correct and compliant.
OBS is also used in the context of key derivation functions (KDFs) and random number generators. For example, the output of a KDF is a bit stream that is used as a key or as input to another cryptographic process. The precise definition of these bit streams ensures that different implementations produce identical results, which is critical for interoperability in multi-vendor networks.
In Release 19, OBS was introduced as a term in the context of security testing and assurance. Release 20 continues to use the term, with specifications updated to reflect new algorithms and test cases. The concept remains unchanged in its fundamental meaning: it is the bit stream output by a cryptographic function, used for validation and testing.
Purpose & Motivation
OBS exists to provide a precise, unambiguous reference for the output of cryptographic algorithms in 3GPP specifications. In security engineering, it is essential to have standardized test vectors to ensure that different implementations of the same algorithm produce identical results. Without a clear definition of the output bit stream, interoperability between network elements from different vendors would be impossible, and security vulnerabilities could arise from implementation errors.
The term was introduced in Release 19 as part of 3GPP's ongoing efforts to enhance security assurance for 5G and future networks. As networks become more complex and security threats evolve, the need for rigorous testing and validation of cryptographic functions has increased. OBS provides a common language for specifying expected outputs in test specifications, enabling conformance testing and certification.
Previous approaches to security testing often relied on informal descriptions or vendor-specific test vectors, which led to inconsistencies and potential interoperability issues. By standardizing the concept of OBS, 3GPP ensures that all stakeholders—network equipment vendors, device manufacturers, and test labs—have a common understanding of cryptographic outputs. This is particularly important for 5G, where security is a cornerstone of the architecture and spans multiple domains, including radio, core, and management.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference OBS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 26.955 vj00 | Video Codec Analysis for 5G Services | Rel-19 read |
| TS 33.771 vk00 | 6G AEAD Security Support | Rel-20 read |
| TS 35.240 vk10 | 5G 256-bit Security Algorithm Set | Rel-20 read |
| TS 35.243 vk00 | AES 256-bit Algorithm Set Specification | Rel-20 read |
| TS 35.246 vk00 | ZUC based 256-bit Algorithm Set Specification | Rel-20 read |