TR 21.900
SA
★
Technical Specification Group Working Methods
use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V16.2.0 (Wzip)
2019/09 43 p.
V15.2.0 (PDF)
2018/12 9 p.
V14.2.0
2018/09 10 p.
V13.2.0
2017/06 10 p.
V12.1.0
2016/03 9 p.
V11.2.0
2016/03 9 p.
V10.1.0
2011/12 8 p.
V9.1.0
2011/06 8 p.
V8.4.0
2010/04 8 p.
V7.3.0
2007/10 8 p.
V6.4.0
2005/01 8 p.
V5.1.0
2004/01 8 p.
V4.1.0
2004/01 8 p.
V3.7.0
2004/01 8 p.
Rapporteur: Mr. Meredith, John M
Here are reproduced the Introduction and the Scope:
In order to ensure correctness and consistency of the specifications (i.e., technical specifications and technical reports) under responsibility of the Technical Specification Groups (TSG) of the 3rd Generation Partnership Project (3GPP), clear, manageable and efficient mechanisms are necessary to handle version control, change control, document updating, distribution and management.
Also, the fact that the specifications are/will be implemented by industry almost in parallel with the writing of them requires strict and fast procedures for handling of changes to the specifications.
It is very important that the changes that are brought into the standard, from the past, at present and in the future, are well documented and controlled, so that technical consistency and backwards tracing are ensured.
The 3GPP TSGs, and their sub-groups together with the Support Team are responsible for the technical content and consistency of the specifications whilst the Support Team alone is responsible for the proper management of the entire documentation, including specifications, meeting documents, administrative information and information exchange with other bodies.
This document outlines the working methods to be used by the 3GPP Technical Specification Groups and their Working
Groups and their Sub-Groups, and by the 3GPP Support Team in relation to document management, i.e. handling of
specifications, updating procedures, Change Request procedures, version control mechanisms, specifications status
information etc. It complements the rules and procedures defined for 3GPP. This document does not stipulate the details
of the internal working of the TSG Sub-Groups. From the Technical Specification Group point of view, a task and
responsibility is given to a Working Group directly answering to the Technical Specification Group. In practice, the
work/task may be carried out in a subgroup of that Working Group.
full Table of Contents for TR 21.900 Word version: 16.2.0
1 Scope Word-p. 6
1A References
2 Definitions and abbreviations
3 General responsibilities of the Support Team Word-p. 7
4 Handling of Specifications Word-p. 9
4.0 Numbering scheme
4.0A Version nomenclature Word-p. 11
4.0B Releases Word-p. 12
4.1 Overview 
4.2 Characteristics of a specification
4.3 Characteristics of a major version of a specification
4.4 Characteristics of a version of a specification Word-p. 15
4.5 Void
4.6 Change Request regime
5 Availability and distribution of specifications
5A File naming conventions
5B Availability and distribution of OpenAPI specification files Word-p. 27
6 Work Items Word-p. 28
4.2 Characteristics of a specification
4.3 Characteristics of a major version of a specification
4.4 Characteristics of a version of a specification Word-p. 15
4.5 Void
4.6 Change Request regime
4.6.1 Change Requests
4.6.2 Change Request forms Word-p. 16
4.6.3 Contents of Change Requests Word-p. 18
4.6.4 Handling of the Change Requests
4.6.5 Updating and release of new versions of the specifications Word-p. 19
4.6.6 Other changes to specifications
4.7 "Freezing" of specifications
4.8 "Closing" of specifications Word-p. 20
4.9 "Withdrawing" of specifications
4.9A "Withdrawing" of functionality
4.9B Procedure for withdrawing of specifications and functionality
4.6.5 Updating and release of new versions of the specifications Word-p. 19
4.6.6 Other changes to specifications
4.9B.2 Diligent assessment
4.9B.3 Changes to affected specifications Word-p. 21
4.9B.4 Considerations for ongoing maintenance, enhancement and new Release versions of specifications
4.10 Release control
6.0 Introduction
7 Management documents and tools Word-p. 36
6.0.1 Introduction: why manage a project?
6.0.2 How to manage a project?
6.0.3 Types of modification to specifications Word-p. 29
6.1 Creation of a Work Item Word-p. 30
6.2 Types of Work Item
6.3 Start and continuation of the work and responsibilities Word-p. 31
6.4 Realization of Work Items
6.4.1 Planning and categorization of the deliverables (and control thereof)
6.4.2 Choice of deliverables Word-p. 33
6.4.3 Contents of deliverables
6.5 Status tracking of Work Items
6.6 Work Item model Word-p. 35
6.4.3.1 Service requirements
6.4.3.2 Technical realization specifications
6.4.3.3 Test specifications Word-p. 34
6.4.4 Early implementation
6.4.5 Late completion
6.4.3.2 Technical realization specifications
6.4.3.3 Test specifications Word-p. 34
7.1 Status List of Specifications
7.2 Work Item Status List
7.3 Change Request data base
7.4 Mailing lists and Membership data bases
7.5 Electronic tools used/preferred
7.6 WEB and FTP services Word-p. 37
7.7 E mail reflectors
8 E mail decisions
7.4 Mailing lists and Membership data bases
7.5 Electronic tools used/preferred
7.6 WEB and FTP services Word-p. 37
7.7 E mail reflectors
8.1 E mail drafting phase
8.2 E mail decision declaration
8.3 Status reporting Word-p. 38
8.4 Decision announcement
8.5 Timing
8.6 General
9 Meeting contribution document types and status values
A Change history Word-p. 42
8.6 General
