Description
Static conformance review (SCR) is a formal conformance assessment activity defined in the 3GPP terminal conformance testing framework. It is a non-executable, document-based check: the reviewer compares the answers recorded in the Implementation Conformance Statement (ICS) — a structured questionnaire in which the UE manufacturer declares which optional features, capabilities and procedures the User Equipment Under Test (UEUT) supports — against the static conformance requirements (SCRs) expressed in the relevant core, radio or terminal specification. The purpose is to determine whether the set of claimed capabilities is internally consistent and permissible according to the specification's normative rules, before any dynamic (executable) testing is performed.
The mechanism relies on the ICS proforma defined in the conformance test specification series. For each feature, the specification states whether support is mandatory, optional, conditional, or excluded, and often expresses dependencies (for example, 'if feature A is supported, then feature B shall also be supported'). The manufacturer completes the ICS by marking each item as supported or not supported. The static conformance review then applies the dependency and consistency rules to the completed ICS. If a manufacturer claims support for a feature whose prerequisite is not claimed, the review identifies a static conformance deficiency. This is a purely logical check on the declaration, not a measurement of the device's behaviour.
In the 3GPP test specification architecture, the SCR is the first of two conformance assessment stages. The second stage is dynamic conformance testing, in which test cases are executed against the UEUT to verify that the claimed capabilities actually operate as specified. The static review therefore acts as a gatekeeper and scoping mechanism: it establishes which test cases are applicable to a given device (test selection), and it prevents a device from claiming a feature in the ICS while avoiding the corresponding dynamic tests. The relevant specifications include the UE conformance specification (38.521 for NR radio transmission and reception, 36.521 for LTE), the UE conformance specification for protocol conformance (38.523, 36.523), and the common test specifications 38.508 and 38.522, together with the RF and protocol test specifications 37.571 and 37.579 for positioning.
Operationally, the SCR is performed by a test laboratory or a manufacturer's own conformance team, typically as part of a Global Certification Forum (GCF) or PTCRB certification programme. The reviewer produces a static conformance review report that lists the claimed features, the applicable static conformance requirements, and any discrepancies. The report accompanies the device's test evidence. Because the review is document-based, it is inexpensive and can be completed early in the product lifecycle, allowing design issues to be caught before expensive dynamic testing begins.
The concept is release-independent in nature: the ICS proforma and the static conformance requirements are updated with each 3GPP release as new features (for example, NR positioning, RedCap, or non-terrestrial network access) are added, but the review methodology itself remains stable. This stability is why the definition text has been carried over essentially unchanged from Rel-15 through Rel-20, even as the underlying feature set and specification numbers have grown.
Purpose & Motivation
Static conformance review exists to solve a practical problem in terminal certification: a modern UE implements hundreds of optional features, and executing dynamic tests for every possible feature combination is prohibitively expensive and slow. By requiring manufacturers to declare their supported feature set in an ICS and then logically checking that declaration against the specification's dependency rules, the industry can scope the dynamic test campaign to only the features actually claimed, while still ensuring that no device can silently omit a mandatory dependency.
Historically, before structured ICS/SCR methodologies were widely applied, conformance assessment risked being either incomplete (features untested because they were not declared) or unbounded (every optional feature tested regardless of support). The ICS/SCR framework, standardised across the 3GPP terminal conformance specifications, introduced a formal, auditable link between what a device claims and what it must be tested for. It also provides a common language for operators, manufacturers and test houses when negotiating acceptance criteria.
The approach is motivated by the need for regulatory and operator confidence at scale. Certification programmes such as GCF and PTCRB rely on the SCR as the entry point to their test regimes, ensuring that the declared capability baseline is consistent and that dynamic testing is both necessary and sufficient for the claimed feature set.
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 Static conformance review, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.521 vj11 | E-UTRA UE Conformance Testing for Satellite Access | Rel-19 read |
| TS 36.523 vj20 | E-UTRA UE Conformance ICS Proforma | Rel-19 read |
| TS 37.571 vj00 | UE Conformance for Positioning | Rel-19 read |
| TS 37.579 vi50 | Mission Critical (MC) services | Rel-18 read |
| TS 38.508 vj31 | 5G NR UE ICS Proforma | Rel-19 read |
| TS 38.522 vk00 | NR UE Conformance Test Applicability | Rel-20 read |
| TS 38.523 vj40 | UE Conformance Specification for 5G NR | Rel-19 read |