Description of how the TR impacts the TS/Section
impact description
Specification clauses affected by this CR (e.g., '5.3.1, 5.3.2')
clauses affected
Section title text from heading (excluding sectionNumber)
section title
Meeting where this Resolution was made (1..*; admits dual-Meeting placement under hybrid e-meeting sessions)
made at
Resolution content with OMML equations converted to inline LaTeX ($...$). For LLM answer generation and UI rendering (Spec §8).
content with equations
Discussion conclusion (may or may not have consensus)
Conclusion
A table within a 3GPP Technical Specification document, identified by TH-style caption
TS Table
Chart(s) referenced in this Resolution content
has chart
Work Item code name (e.g., NR_MIMO_Ph5-Core)
work item code
Table unique identifier (e.g., TBL-112-001 for Report Table, 38.214-T5.1.3.2-1 for TSTable)
table ID
TS (Spec) affected by this TRImpact
impacts spec
Whether consensus was reached for this conclusion
has consensus
Work Item(s) related to this TDoc
related to
3GPP Technical Specification (TS) or Technical Report (TR)
Specification
Summary of the changes made by this CR (from CR document 'Summary of change' field)
summary of change
Caption text for Figure, Table, or Chart (optional for Figure/Table, required for Chart)
caption
A named 3GPP standardization feature spanning one or more IEs/Sections/Capabilities/Releases (e.g., 'Rel-16 Enhanced Type-II codebook', 'Rel-18 LTM', 'BFD/BFR'). Independent class — not a subclass of Tdoc/Section/CR. Instances are curated per working group in a feature catalog.
3GPP Standard Feature
TSTable(s) contained in this Section
contains table
TDoc that replies to this TDoc (allows multiple replies across different WGs)
reply in
Liaison Statement for official communication between Working Groups or external organizations
Liaison Statement
O&M Specification(s) affected by this CR (from 'Other specs affected' section)
affects OM spec
Section(s) referenced by this Section's content (clause/subclause patterns)
references section
Section number from heading (e.g., 5.1.3.2, A.1, 8.1.4A). Body: ^[0-9]+(\.[0-9]+)*[a-zA-Z]?$, Annex: ^[A-Z](\.[0-9]+)*$
section number
Technical table embedded in Final Report (captioned or structural heuristic)
Table
Meeting agenda item with hierarchical numbering (e.g., 9.1, 9.1.1)
Agenda Item
Figure(s) referenced in this Resolution content
has figure
Section number affected by this TR impact (e.g., 5.2, 8.1)
affected section
Chart unique identifier (e.g., CHT-114b-001)
chart ID
TRImpact(s) that affect this Spec
spec impacted by
Path to the extracted file (image for Figure, HTML for Table)
file path
Direct parent Section (exactly one, null for level-1)
parent section
TSG plenary meeting where this CR Pack was submitted (e.g., RAN#103)
TSG meeting
Individual UE capability row in 3GPP capability spec (e.g., 38.306 §4.2.7.2 BandNR `codebookParametersAddition-r16`, `ltm-MCG-IntraFreq-r18`). Independent class — not a subclass of Section.
UE Capability Item
Core Specification(s) affected by this CR (from 'Other specs affected' section)
affects core spec
Table(s) referenced in this Resolution content
has table
TS table caption text from TH-style paragraph (e.g., 'Supported CSI-RS resource configurations')
table caption
Hierarchical agenda number (e.g., 9.1, 9.1.1)
agenda number
Normalized meeting number without -e suffix for COVID e-meeting matching (e.g., RAN1#101-e → RAN1#101). Used for Resolution linking.
canonical meeting number
LS direction. Values: in (received), out (sent)
direction
Whether this section contains only 'Void' text (true) or has real content (false)
is void
Chart type extracted from XML (scatterChart, lineChart, barChart, pieChart, etc.)
chart type
TRImpact(s) that affect this Section
section impacted by
Whether this CR affects CN (Core Network)
affects CN
Meeting that contains this Figure/Table/Chart
contained in
TRImpact node(s) for this TR's influence on TS/Section
has TR impact
Alternative names/spellings for this company
aliases
Notes from the meeting secretary (e.g., 'Late contribution')
secretary remarks
Contact person responsible for a TDoc
Contact
CR category. Values: F (Fix), A (Mirror), B (Addition), C (Functional modification), D (Editorial), E (Early implementation)
CR category
Company or organization that submits TDocs
Company
TS figure caption text (e.g., 'PDSCH resource allocation procedure')
figure caption
Working Group(s) that originated/sent this LS. Cardinality 0..*: cross-WG LSs are frequently issued by, or addressed to, multiple WGs simultaneously.
originated from
Target 3GPP Release version for this TDoc or TechnicalReport
target release
Agenda Item under which this Resolution was made
resolution belongs to
Top-level Section(s) contained in this Spec
has section
Original LS document from another WG (for LS in)
original LS
Official CR number (e.g., 0693). DraftCR and pCR may not have this.
CR number
Previous version TDoc that this TDoc revises
is revision of
TDoc that this TDoc replies to (typically for LS responses)
reply to
Session information (e.g., 'Friday session', 'Online')
session context
3GPP Release version (e.g., Rel-18, Rel-19)
Release
Section unique identifier (pattern: {specNumber}-{sectionNumber}, e.g., 38.214-5.1.3.2)
section ID
Title of the TDoc
title
Type of the TDoc. Values: discussion, CR, draftCR, pCR, LS out, LS in, other, report, agenda, Work Plan, draft TR, draft TS, response, WID new, SID new, WI summary
type
Meeting identifier (e.g., RAN1#120)
meeting number
Meeting where this TDoc was presented/discussed. Cardinality is 0..* in practice: a small fraction of TDocs are re-tabled at consecutive meetings under the same identifier (rare in the released RAN1 KG (1 case in current snapshot)).
presented at
Tentative assumption that may be promoted to Agreement
Working Assumption
Whether this CR affects RAN (Radio Access Network)
affects RAN
CR(s) included in this CRPack
has CR
Section(s) that reference this Section
referenced by section
FL Summary or Moderator Summary document from Final Report
Summary
Section affected by this TRImpact (optional, for NewSection/ExtendSection)
impacts section
Scope/objectives of the TR research (from Scope section, 1-10 sentences)
scope
Test Specification(s) affected by this CR (from 'Other specs affected' section)
affects test spec
Direct child Section(s) of this Section
has sub-section
Chart embedded in Final Report (<c:chart> XML, no <a:blip> image)
Chart
Company whose employee chaired this session
chaired by
Version of the TR (e.g., 2.0.0, 18.0.0)
TR version
Additional note attached to the resolution
note
Numeric part of meeting number for proper sorting (e.g., RAN1#122 → 122, RAN1#122b → 122). Extracted via regex #(\d+).
meeting number integer
Change Request document that modifies a 3GPP specification (TS/TR). Includes CR, draftCR, and pCR types.
Change Request
Unique identifier for the TDoc (e.g., R1-2500001). Format: R1-YYNNNNN
TDoc number
Section(s) modified by this CR (derived from clausesAffected field)
modifies section
Path to the extracted chart XML file
chart path
Work Item RP number from TR Scope (pattern: RP-xxxxxx, e.g., RP-213599)
work item RP number
Working Group name (e.g., RAN1, SA2)
WG name
Company/organization that submitted the TDoc. Multiple companies can co-submit.
submitted by
Type of impact on TS. Values: NewTS (new spec created), NewSection (new section added), ExtendSection (existing section extended), NoChange (reference only)
impact type
Agreement that this WorkingAssumption was promoted to
promoted to
Title of the specification (e.g., 'Physical channels and modulation')
spec title
A figure within a 3GPP Technical Specification document, identified by figure caption
TS Figure
Reification node for TR→TS impact relationship with impactType attribute (NewTS, NewSection, ExtendSection, NoChange).
TR Impact
Hierarchy level (1-6). Derived from heading style: Heading 1-5 → 1-5, H6/Heading 6 → 6, Heading 8/9 → 1 (Annex)
level
Working Group(s) copied on this LS
cc to
TR that this TRImpact belongs to
impact of TR
Other TR(s) referenced by this TR (from References section)
references TR
Canonical name of the company/organization
company name
Study Item RP number from TR Scope (pattern: RP-xxxxxx, e.g., RP-213599)
study item RP number
TDoc(s) referenced in this Resolution content
references
Whether the agreement contains 'For Further Study' marker
has FFS
3GPP conformance test specifications body — by spec body nature (test procedure / test environment / verdict / applicability), regardless of working group. Examples: RAN5 UE test (38.508-x, 38.509, 38.521-x, 38.523-1, 38.533), RAN4 BS test (38.141-1 conducted, 38.141-2 radiated, 38.181 AAS BS). Independent class. Distinct from Procedure (protocol procedure in spec body, not conformance test).
Conformance Test Specification
Decision status. Values: approved, agreed, noted, revised, postponed, withdrawn, not treated, available, reserved, merged, not concluded, conditionally agreed, endorsed, not pursued, treated
status
TSG CR Pack number (e.g., RP-250233) for approved CRs
TSG CR pack
Original number from caption (e.g., 6.3.2-1)
chart number
3GPP ASN.1 IE body — covers RRC IE (38.331 CodebookConfig-r16, etc.), NGAP IE (38.413), XnAP IE (38.423), F1AP IE (38.473), E1AP IE (38.463). The class name 'RRCParameter' is retained for continuity, but the class semantically represents any 3GPP-spec ASN.1 IE. Independent class — not a subclass of Section.
ASN.1 IE (RRC + interface IE)
3GPP Technical Report (TR) - research/study documents that may lead to TS changes. Contains scope, conclusions, and TR-TS impact analysis.
Technical Report
SPECTRA: A Traceability Ontology for 3GPP RAN Standardization
OWL 2 ontology modeling the 3GPP RAN standardization document lifecycle (Tdoc, Resolution, CR, LS, Section, Spec, TechnicalReport, TRImpact, Meeting, Company, WorkingGroup). Designed from RAN1 competency questions and validated by cross-WG instantiation against RAN2-RAN5 with no additional process-layer classes required. Also declares six entity-layer classes (RRCParameter, CapabilityItem, Feature, Procedure, PerformanceRequirement, ConformanceTest) modeling spec-body entities: ASN.1 IEs, UE capability items, named standardization features, protocol procedures, performance requirements, and conformance test specifications.
Creative Commons Attribution 4.0 International (CC BY 4.0)
Unique identifier for the resolution (e.g., AGR-112-8.1-001)
resolution ID
Description/title of the agenda item
agenda description
Technical figure embedded in Final Report (captioned or structural >50KB)
Figure
3GPP system unique ID for the contact
contact ID
Work Item (SI/WI) related to this TR, identified by RP-xxxxxx in TR Scope
related to work item
Date/time when the TDoc number was reserved
reservation date
TR(s) that reference this TR
referenced by TR
3GPP Working Group meeting
Meeting
SPECTRA Ontology Project
TSFigure(s) contained in this Section
contains figure
Type of summary: FL (Feature Lead) or Moderator
summary type
Figure unique identifier (e.g., FIG-112-001 for Report Figure, 38.214-F5-1 for TSFigure)
figure ID
3GPP Release version name (e.g., Rel-18, Rel-19)
release name
Research conclusions of the TR (from Conclusions section, 1-10 sentences)
conclusions
3GPP Work Item (WI) or Study Item (SI)
Work Item
Working Group hosting the meeting (e.g., RAN1)
working group
Session notes for ad-hoc discussions from Final Report
Session Notes
Date/time when the TDoc file was uploaded
uploaded date
TSG CR Pack - a bundle of CRs submitted to TSG plenary meeting (e.g., RP-250233). Identified by Cover Sheet.
CR Pack
Status of the TR. Values: Draft (v0.x.x), Completed (vX.0.0), Living (vX.Y.Z continuous updates)
TR status
A section within a 3GPP Technical Specification document, identified by heading style
Section
Technical agreement reached in the meeting
Agreement
Version of the specification (e.g., 18.5.0)
spec version
Resolution text with equations replaced by [EQUATION] markers. For Text-to-Cypher search (Spec §8).
content
Name of the contact person
contact name
Reason why this CR change is needed (from CR document 'Reason for change' field)
reason for change
Section that contains this TSFigure (exactly one)
figure in section
Original figure number from caption (e.g., Figure 1 for Report, 5-1 for TSFigure)
figure number
Newer version TDoc that revises this TDoc
revised to
3GPP Working Group (e.g., RAN1, RAN2, SA2)
Working Group
Resolutions made under this AgendaItem
has resolutions
Specification number (e.g., 38.212)
spec number
Round number for the summary (0, 1, 2, ...)
round number
Original table number from caption (e.g., Table 7.8-1 for Report, 5.1.3.2-1 for TSTable)
table number
Unique identifier for TRImpact (e.g., 38.769-38.291, 38.885-38.211-S8)
TR impact ID
Specification(s) that this CR modifies. Cardinality 1..*: a single CR may amend more than one Spec (e.g., paired stage-2 and stage-3 updates).
modifies
Contact person responsible for the TDoc
has contact
A protocol procedure spanning one or more sections (e.g., 'BFR Procedure' in 38.321 §5.17, 'RACH Procedure' in 38.321 §5.1). Independent class; a procedure may span multiple sections.
Procedure
Whether this CR affects UICC (Universal Integrated Circuit Card)
affects UICC
Order within the same Agenda Item (1-based)
sequence
CR(s) that modify this Section
modified by CR
Whether this CR affects ME (Mobile Equipment)
affects ME
CR Pack unique identifier from Cover Sheet directory name (e.g., RP-250233)
CR pack ID
Spec that this Section belongs to (exactly one)
belongs to spec
Agenda Item under which this TDoc is discussed
belongs to
TR(s) related to this Work Item (inverse of relatedToWorkItem)
has related TR
Full title of the Technical Report (e.g., 'Study on Ambient IoT')
TR title
Whether the agreement contains 'To Be Determined' marker
has TBD
CRPack that this CR belongs to (at most one)
belongs to CR pack
Abstract/summary of the TDoc (often empty)
abstract
Technical Report number (e.g., 38.769, 38.901)
TR number
Company whose employee moderated this Summary discussion
moderated by
Abstract base class for meeting resolutions (Agreement, Conclusion, WorkingAssumption)
Resolution
Quantitative performance requirements specs body (38.133 RRM perf req, 38.101-x RF/EMC requirements, 38.104 BS RF requirements). Includes evaluation periods (TEvaluate_*), scaling factors (FR1/FR2/FR2-1/FR2-2), scheduling availability windows, minimum requirements per RS type, timing budgets (e.g., T = T1 × Ceil((T2+D)/T1)). Independent class. Distinct from CapabilityItem (UE capability declarations) and Procedure (protocol procedures).
RRM/RF Performance Requirement
LaTeX equations found within the table cells (multi-valued)
equations
3GPP Technical Document - base class for all meeting documents
TDoc
Working Group(s) that receive this LS
sent to
Consequences if this CR is not approved (from CR document 'Consequences if not approved' field)
consequences if not approved
Purpose of the TDoc. Values: Decision, Discussion, Approval, Agreement, Endorsement, Information, Presentation, Action
for
CR revision number (1-9). Indicates how many times this CR has been revised.
CR revision
Section that contains this TSTable (exactly one)
table in section