BER

Basic Encoding Rules

Protocol →
Introduced in R99 Also in: Services

BER is the standardized set of rules for encoding ASN.1-defined data structures into a binary stream, used extensively in 3GPP signaling protocols to ensure unambiguous data exchange between network elements.

Category
Protocol
Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Also touches
1 segments
Specifications
54 specs
BER Description Purpose Related Classification Detected Changes Specifications

Description

Basic Encoding Rules (BER) is a method for encoding data objects described in Abstract Syntax Notation One (ASN.1) into a string of octets (bytes). ASN.1 is a standard interface description language used to define the structure of protocol data units (PDUs) in a platform-independent way. BER provides the concrete translation from this abstract definition to a concrete bit-level representation that can be transmitted over a network or stored. It is a tag-length-value (TLV) encoding scheme, which makes the encoded data self-describing.

Architecturally, BER operates on individual ASN.1 types. The encoding process for any data element produces three consecutive fields: the Identifier (Tag) octets, the Length octets, and the Contents (Value) octets. The Tag identifies the type of the data (e.g., INTEGER, SEQUENCE, OCTET STRING) and whether it is primitive or constructed. The Length field specifies the number of octets in the Contents field. The Contents field contains the actual encoded value of the data. For simple types like INTEGER, the value is directly encoded. For constructed types like SEQUENCE or SET, the Contents field contains the concatenated BER encodings of each component element.

How it works involves a recursive process. An encoder traverses the ASN.1 data structure, applying the TLV rule to each node. A key feature is its flexibility; BER offers multiple encoding forms for some data types (e.g., definite vs. indefinite length forms). In 3GPP, BER is specified as the transfer syntax for numerous Layer 3 signaling protocols, especially in the core network. For instance, protocols like Radio Resource Control (RRC), Non-Access Stratum (NAS), and many application-layer protocols in the core (often using the ASN.1 PER variant) have their roots in BER encoding principles. Its role is to guarantee that a message generated by one vendor's equipment can be correctly parsed and understood by another vendor's equipment, providing the essential interoperability for multi-vendor telecommunications networks.

Purpose & Motivation

BER exists to solve the fundamental problem of heterogeneous data representation in distributed systems and telecommunications networks. Different computer architectures represent data in different ways (e.g., byte order, integer size). Without a common, unambiguous encoding rule, two systems could agree on the abstract structure of a message (via ASN.1) but still fail to exchange data correctly because of low-level representation differences. BER provides a canonical, external representation that is independent of any machine-specific details.

Its creation was motivated by the need for robust, interoperable protocol specifications in the early days of digital telecommunications and data networking (OSI model). Before such standards, protocol specifications were often ambiguous, leading to costly and time-consuming integration problems. BER, in conjunction with ASN.1, allows protocol designers to define complex, nested data structures precisely and provides a standardized way to serialize them. This dramatically reduces implementation errors and ensures that network elements from different manufacturers can communicate seamlessly, which is a cornerstone principle of public standards like those from 3GPP. It addresses the limitation of ad-hoc or proprietary encoding schemes that locked networks into single-vendor solutions.

Classification

Part ofDER
Specific typesGBERXER
Related approachesPER

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 1 change

In Release 16, a correction was introduced to align the BER function with drafting rules. This update specifically addressed the technical description of ancillary equipment, clarifying that such equipment can be operated with but is not dependent on for basic functionality. The change ensured consistency in the specification's terminology and structure.

  • Correction for alignment with drafting rules TS 32.298CR0852

Explore further

Broader topics and technologies where BER plays a role.

Defining Specifications

3GPP specifications that define or reference BER, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 22.101 vk00 Service Principles for PLMNs Rel-20
TS 22.105 vj00 Telecommunication Services Framework Rel-19
TR 22.925 v1311 UMTS QoS and Network Performance Parameters Rel-4
TS 23.050 v1100 UMTS Network Principles and Architecture R99
TS 23.107 vj00 UMTS QoS Framework Rel-19
TS 23.171 v1300 LCS Stage 2 Specification for UMTS Rel-4
TS 23.207 vj00 End-to-End QoS Framework for GPRS Rel-19
TS 23.271 vj00 LCS Stage 2 Specification Rel-19
TR 23.979 vj00 PoC over 3GPP Systems Architectural Requirements Rel-19
TS 25.101 vj00 UTRA FDD UE RF Requirements Rel-19
TS 25.102 vj00 UTRA TDD RF Characteristics Rel-19
TS 25.104 vj00 UTRA FDD Base Station RF Characteristics Rel-19
TS 25.105 vj00 UTRA TDD Base Station RF Requirements Rel-19
TS 25.111 vj00 LMU RF Characteristics for UTRA FDD Rel-19
TS 25.123 vj00 Radio Resource Management for TDD Rel-19
TS 25.133 vj00 UTRAN RRM Requirements for FDD Rel-19
TS 25.141 vj00 UTRA FDD Base Station RF Conformance Testing Rel-19
TS 25.142 vj00 UTRA TDD Base Station RF Test Methods Rel-19
TS 25.201 vj00 UTRA Physical Layer General Description Rel-19
TS 25.212 vj00 UTRA FDD Layer 1 Multiplexing & Channel Coding Rel-19
TS 25.215 vj00 UTRA FDD Measurement Definitions Rel-19
TS 25.222 vj00 UTRA TDD Multiplexing & Channel Coding Rel-19
TS 25.225 vj00 UTRA TDD Physical Layer Measurements Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TS 25.411 vj00 Iu Interface Layer 1 Specification Rel-19
TS 25.415 vj00 Iu Interface User Plane Protocol Rel-19
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19
TS 25.427 vj00 UTRAN Iub/Iur User Plane Protocols Rel-19
TR 25.914 vj00 3G UE Radio Performance Test Methods Rel-19
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19
TS 26.077 vj00 AMR Noise Suppression Minimum Performance Requirements Rel-19
TS 31.114 v1800 USAT Interpreter Transmission Protocol Rel-8
TS 32.298 vj30 Charging Data Record (CDR) Parameter Specification Rel-19
TS 32.300 vj00 3GPP Network Resource Naming Convention Rel-19
TS 32.401 vj00 Performance Management Concept & Requirements Rel-19
TS 32.404 vj00 Performance Management Definitions & Template Rel-19
TS 32.405 vj00 UTRAN Performance Measurements Specification Rel-19
TS 32.406 vj00 Performance Management for CN PS Domain Rel-19
TS 32.436 vj00 ASN.1 file format for performance measurement Rel-19
TS 33.108 vj00 LI Handover Interface Specification Rel-19
TS 34.114 vc20 Radiated Performance Test Procedure for UE/MS Rel-12
TS 37.104 vj10 MSR Base Station RF Characteristics Rel-19
TS 37.105 vj10 AAS Base Station Transmission & Reception Requirements Rel-19
TS 37.113 vj00 EMC Requirements for Multi-Standard Radio Base Stations Rel-19
TS 37.141 vj10 RF Test Methods for Multi-Standard Radio Base Stations Rel-19
TS 37.145 vj10 AAS Base Station Conducted Conformance Testing Rel-19
TS 37.544 vg70 UE Radiated Performance Test Procedures Rel-16
TS 37.802 va10 MSR BS RF Requirements for Non-Contiguous Spectrum Rel-10
TS 37.812 vb30 Multi-band Multi-standard Radio BS Requirements Rel-11
TR 37.900 vj00 Multi-Standard Radio (MSR) Base Station Requirements Rel-19
TR 45.903 vj00 SAIC Feasibility Study for GSM Networks Rel-19
TR 45.913 vj00 Optimized Transmit Pulse Shape for EGPRS2-B Rel-19
TR 45.914 vj00 MUROS Feasibility Study for Voice Capacity Rel-19