Quick Start: For workflow overview and submission checklist, see references/workflow.md; for the number format, status table, document structure and databases, see references/cr-format.md; for the checklist, pitfalls and best practices, see references/cr-checklist.md; for revising an existing CR, see references/cr-revision.md.
Overview
Change Requests (CRs) are documents submitted to 3GPP Working Groups to create revised versions of specifications. They represent the formal mechanism for modifying 3GPP specs after initial approval.
What is a CR?
A CR is a temporary document (tdoc) to a meeting which specifies in precise detail changes to be made to a specification. It consists of:
- CR Cover Sheet: Describes why a change is needed and summarizes how the change is made
- Attached Parts of Spec: Word™ "Track Changes" (revision marks) identifying affected sections
- Summary of Changes: Brief explanation of the proposed modification
Why Changes Are Needed
Three main reasons for creating a CR:
- Add a new feature to a Release still under development
- Correct / clarify / enhance an existing feature in a Release still under development
- Correct an error in a spec which is functionally frozen
CR Number Format
<specnumber_no_dot>*_CR*<4-character_CR_number>*[r*<revision_number>*]
Component breakdown, examples, document sections and the file naming
convention: references/cr-format.md.
CR Categories
Three categories: F (corrective), A (mirror) and TEI (technical
enhancement or improvement). A mirror CR applies the same change to another
Release of the same spec. Definitions: references/cr-format.md.
Mirror CRs
A spec maintained in several parallel Releases needs one mirror CR per
Release, all sharing the same Work Item code. Concepts and checklist:
references/cr-checklist.md.
Change Request Workflow
- Create CR Member organization creates CR document, with the portal document type CR
- Submit to WG WG discusses and agrees CR is valid
- WG Presents to TSG WG presents CR at TSG plenary for approval
- TSG Approval TSG approves CR (becomes decision)
- MCC Incorporates MCC incorporates CR into new spec version
- Publish New spec version becomes available
Detailed steps, status transitions and the quick checklist:
references/workflow.md.
Revising a CR
Three rules: the CR number stays the same, the CR revision number increases, and it stays the same CR - a revision is a new version of an existing CR, not a new CR.
Never build the revised cover sheet by hand. Set Is revision of: on the
portal (it fills the CR number, the revision number and the meeting), then
download the cover sheet from the template generator for the new TDoc - that
page is the recommended starting point for every revision. The one thing it
does not cover is the right-aligned revision of <tdoc-nbr> marker on the
second cover line.
Procedure, cover-sheet fields, the marker's DOCX structure, file name and
worked example: references/cr-revision.md.
Reference Files
references/cr-format.md- CR number format, components and examples, CR status table, CR categories, document sections, revision history, file naming convention, work item codes, CR databases, resourcesreferences/cr-checklist.md- CR submission checklist, common pitfalls, best practices, mirror CR and editorial conceptsreferences/cr-revision.md- revising a CR: what changes, the portal procedure, the "revision of" marker on the cover sheet, file namereferences/cr-revision-marks.md- authorship of revision marks (agreed state under the meeting name), review of drafted changes, maintenance CR versus new workreferences/workflow.md- CR lifecycle, six-step submission and approval process, status transitions, quick checklist
Cross-References
3gpp-basics- 3GPP organization and structure3gpp-working-groups- Working Group responsibility for specs3gpp-tdocs- CRs as meeting documents (tdocs)3gpp-releases- Understanding Release structure3gpp-portal-authentication- Some CR documents may require EOL access3gpp-specifications- Spec numbering and structuresdo-drafting- TDoc template, frontmatter and revision workflow