Technical Report (TR)
Description
Informative 3GPP reports covering feasibility studies, investigation results, and explanatory material that supports the normative TS documents. Same identifier shape as TS but with TR prefix. Often the precursor to a future TS — when a TR concludes that a feature is feasible, the work item is transferred to a TS.
Syntax
3GPP identifiers use a type prefix (TS for Technical Specification, TR for Technical Report) followed by a dotted number, optional letter suffix (U, dcs, ext), 1-2 hyphenated parts, release token (REL-N, Ph1, UMTS, Release 2000), and three-part version (X.Y.Z). Default form has no publisher token; with_publisher=true adds '3GPP ' prefix.
Examples 3
Components Used
3GPP Technical Report (TR) identifiers are composed of these elements:
Publisher
3GPP — omitted by default, added when with_publisher=true
3GPPType Prefix
TS for Technical Specification, TR for Technical Report
TSNumber
Dotted core (e.g. 23.207), kept as string to preserve leading zeros
23.207Suffix
Optional letter suffix directly after number: 'U', 'dcs', 'ext'
UParts
1-2 hyphenated parts (e.g. -1, -04-1), strings preserve zero-padding
-04-1Release
Raw release token: 'REL-4', 'Ph1', 'UMTS', 'Release 2000'
REL-4Version
Three-part version string (X.Y.Z)
2.0.0Algebraic Relations
Relations that can involve Technical Report (TR) identifiers:
| Relation | Description | Syntax | Example |
|---|---|---|---|
| Default Form | No publisher prefix (default) | <TS|TR> <number>[<suffix>][<parts>]:<release>/<version> | TS 23.207:REL-4/2.0.0 |
| With Publisher | Publisher prefix added | 3GPP <TS|TR> <number>[<suffix>][<parts>]:<release>/<version> | 3GPP TS 23.207:REL-4/2.0.0 |
| Multi-part | Multi-part spec with hyphenated parts | <TS|TR> <number>-<part1>[-<part2>]:<release>/<version> | TS 29.198-04-1:REL-5/5.0.0 |
| Legacy Release | Pre-REL-4 release tokens | <TS|TR> <number>:<Ph1|Ph2|UMTS|Release 2000>/<version> | TR 00.01U:UMTS/3.0.0 |
URN Mapping
urn:3gpp:[type]:[number]:[release]:[version]