ETSI TR 121 900 V15.1.1 (2018-11)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Technical Specification Group working methods (3GPP TR 21.900 version 15.1.1 Release 15)

RTR/TSGS-0021900vf11

General Information

• Status: Published
• Publication Date: 08-Nov-2018
• Technical Committee: 3GPP SA - Technical Specification Group Services and System Aspects
• Current Stage: 12 - Completion
• Completion Date: 09-Nov-2018

Standards Content (Sample)

TECHNICAL REPORT
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Technical Specification Group working methods
(3GPP TR 21.900 version 15.1.1 Release 15)

3GPP TR 21.900 version 15.1.1 Release 15 1 ETSI TR 121 900 V15.1.1 (2018-11)

Reference
RTR/TSGS-0021900vf11
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 2 ETSI TR 121 900 V15.1.1 (2018-11)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 3 ETSI TR 121 900 V15.1.1 (2018-11)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
1A References . 6
2 Definitions and abbreviations . 6
3 General responsibilities of the Support Team . 7
3.1 Specifications, meetings and liaisons . 7
3.2 Registration of code points . 7
4 Handling of Specifications . 8
4.0 Numbering scheme . 8
4.0A Version nomenclature . 11
4.0B Releases . 11
4.1 Overview . 12
4.1.1 General . 12
4.1.2 Role of the rapporteur . 13
4.2 Characteristics of a specification . 13
4.3 Characteristics of a major version of a specification . 14
4.4 Characteristics of a version of a specification . 15
4.5 (void) . 15
4.6 Change Request regime . 15
4.6.1 Change Requests . 15
4.6.2 Change Request forms . 16
4.6.3 Contents of Change Requests . 18
4.6.4 Handling of the Change Requests . 18
4.6.5 Updating and release of new versions of the specifications . 19
4.6.6 Other changes to specifications . 19
4.7 "Freezing" of specifications . 19
4.8 "Closing" of specifications . 20
4.9 "Withdrawing" of specifications . 20
4.9A "Withdrawing" of functionality . 20
4.9B Procedure for withdrawing of specifications and functionality . 20
4.9B.2 Diligent assessment. 20
4.9B.3 Changes to affected specifications . 20
4.9B.4 Considerations for ongoing maintenance, enhancement and new Release versions of specifications . 21
4.10 Release control . 21
4.10.1 Creation of a new Release version of a specification . 21
4.10.1.1 With no technical changes compared to the previous Release . 21
4.10.1.2 When introducing technical changes . 21
4.10.1.3 Specifications not propagated to next Release . 21
4.10.2 Mirror Change Requests . 21
4.10.3 Release mechanisms . 22
4.10.3.1 Corrections to Releases . 22
4.10.3.2 New features . 23
4.10.3.3 Release naming . 23
4.10.3.4 Introduction of features into Releases . 23
4.10.3.5 Early implementation of features . 24
5 Availability and distribution of specifications . 24
5A File naming conventions . 25
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 4 ETSI TR 121 900 V15.1.1 (2018-11)
6 Work Items . 27
6.0 Introduction . 27
6.0.1 Introduction: why manage a project? . 27
6.0.2 How to manage a project? . 27
6.0.3 Types of modifications to specifications . 29
6.1 Creation of a Work Item . 29
6.2 Type of Work Items . 29
6.3 Start and continuation of the work and responsibilities . 30
6.3.1 General . 30
6.3.2 Role of the rapporteur . 30
6.4 Realization of Work Items. 31
6.4.1 Planning and categorization of the deliverables (and control thereof) . 31
6.4.2 Choice of deliverables . 31
6.4.3 Contents of deliverables . 31
6.4.3.1 Service requirements . 31
6.4.3.2 Technical realization specifications . 32
6.4.3.3 Test specifications . 32
6.4.4 Early implementation . 32
6.4.5 Late completion . 32
6.5 Status tracking of Work Items . 33
6.6 Work Item model. 33
7 Management documents and tools . 34
7.1 Status List of Specifications . 34
7.2 Work Item Status List . 34
7.3 Change Request data base . 34
7.4 Mailing lists and Membership data bases . 34
7.5 Electronic tools used/preferred . 34
7.6 WEB and FTP services . 35
7.7 E-mail reflectors . 35
8 E-mail decisions . 35
8.1 E-mail drafting phase . 35
8.2 E-mail decision declaration . 35
8.3 Status reporting . 35
8.4 Decision announcement . 36
8.5 Timing . 36
8.6 General . 36
9 Meeting contribution document types and status values . 36
9.1 Terminology . 36
9.2 TDoc status values. 38
Annex A: Change history . 41
History . 43

ETSI
3GPP TR 21.900 version 15.1.1 Release 15 5 ETSI TR 121 900 V15.1.1 (2018-11)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
In order to ensure correctness and consistency of the specifications (i.e., technical specifications and technical reports)
rd
under responsibility of the Technical Specification Groups (TSG) of the 3 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.
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 6 ETSI TR 121 900 V15.1.1 (2018-11)
1 Scope
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.
1A References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.801: "Specification drafting rules".
[2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[3] 3GPP TS 21.101: "Technical Specifications and Technical Reports for a UTRAN-based 3GPP
system".
[4] 3GPP TS 41.101: "Technical Specifications and Technical Reports for a GERAN-based 3GPP
system".
[5] ITU-T Recommendation I.130: "Method for the characterization of telecommunication services
supported by an ISDN and network capabilities of an ISDN".
2 Definitions and abbreviations
For the purposes of the present document, the following terms and those in 3GPP TR 21.905 [2] apply.
building block: sub-division of a feature, representing a coherent set of technical functionality which would generally
be expected to reside in a single system element.
change control: procedure whereby proposed modifications to a specification are presented for approval to the TSG as
formal Change Requests.
closed: specification status in which no changes of any kind to the specification are permitted.
Change Request (CR): formal proposal presented on a standard form to modify a specification which is under change
control.
draft: specification status prior to change control, in which changes may be made without formal Change Requests.
early implementation: implementation of a particular feature on a platform of a release earlier than the release that
contains the feature.
feature: new or substantially enhanced functionality which represents added value to the existing system.
frozen: specification status in which only essential corrections are permitted.
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 7 ETSI TR 121 900 V15.1.1 (2018-11)
functionality: normative text contained in one or more Technical Specifications, corresponding either to a feature or to
some portion of a feature.
Group: TSG or TSG Sub-Group.
major version: For version x.y.z of a specification, x is called the major version.
Example: For version 3.2.0 of a specification, the major version is 3.
specification: generic term standing for Technical Specification and Technical Report.
Study Item: type of Work Item which will conduct feasibility studies and will result in a Technical Report
TSG: Technical Specification Group.
TSG change control: specification status in which the Technical Specification Group is responsible for approval of
Change Requests.
TSG Sub-Group: Working Group or subgroup of a Working Group or of a Sub-Group.
Working Group (WG): official subgroup of a TSG reporting to that TSG.
WG Change Control: specification status in which the Working Group is responsible for agreeing Change Requests
for submission to the TSG for approval.
version: unique identifier in the form x.y.z for a specification at a given point in time.
Example: version 3.12.3.
withdrawn: specification status in which the given version of the specification no longer belongs to the appropriate set
of valid specifications.
Work Item (WI): description of an enhancement to a technical area, which may be categorized as Study Item, Feature,
Building Block or Work Task.
Work Item description (WID): description of a Work Item in a standard Work Item Description sheet.
work task: sub-division of a building block, representing a self-contained, well-scoped and well-scheduled item of
work.
3 General responsibilities of the Support Team
3.1 Specifications, meetings and liaisons
The Support Team is responsible for the management of the work of the TSGs. This includes editorship and
management of specifications once they have been put under TSG change control. It also includes preparation of and
support for the meetings (including meeting reports) of the TSGs and their Working Groups, and subgroups in
descending priority.
It furthermore includes liaison with other bodies and relevant groups and institutions.
3.2 Registration of code points
In the course of 3GPP's work, it will from time to time be necessary to register code points in protocols maintained by
bodies other than 3GPP, for example, Multipurpose Internet Mail Extensions (MIME) types registered with the Internet
Assigned Numbers Authority (IANA, http://www.iana.org/).
Wherever possible, registration of such code points shall be entrusted to the 3GPP Support Team rather than being
performed by an individual delegate. Since 3GPP is not a legally constituted entity, the Support Team shall register
such code points in the name of one of the Organizational Partners on behalf of all the Organizational Partners of 3GPP.
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 8 ETSI TR 121 900 V15.1.1 (2018-11)
4 Handling of Specifications
4.0 Numbering scheme
The specifications shall be numbered according to the following scheme:
3GPP TS aa.bbb (for Technical Specifications); or
3GPP TR aa.bbb (for Technical Reports).
The fields aa and bbb shall be selected according to the nature of the specification as given in tables 1 and 2. The
provisions of table 1 shall be strictly enforced, but those of table 2 should be used for guidance: it is acceptable to
deviate from these provisions for backwards compatibility or other reasons.
Table 1: Specification number ranges aa
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 9 ETSI TR 121 900 V15.1.1 (2018-11)
Range for Range for Range for Use Remarks
GSM up GSM UMTS
to and Release 4 Release
including onwards 1999
Release onwards
01.bb 41.bbb 21.bbb Requirements specifications Often transient specifications containing
requirements leading to other specifications;
may become obsolete when technical
solutions have been fully specified; they could
then, e.g., be replaced by reports describing
the performance of the system, they could be
deleted without replacement, or be kept for
historical reasons but treated as background
material.
02.bb 42.bbb 22.bbb Service aspects Services, service features, building blocks or
platforms for services (a service feature or
service building block may provide certain
generic functionality for the composition of a
service, including the control by the user; a
platform may comprise one or more network
elements, e.g. UIM, mobile terminal, auxiliary
system to the core network etc.); also
appropriate stage 1 specifications; also reports
defining services which can be realized by
generic building blocks etc.
03.bb 43.bbb 23.bbb Technical realization Mainly stage 2 specifications (or specifications
of a similar nature describing interworking over
several interfaces, the behaviour in
unexceptional cases, etc.).
04.bb 44.bbb 24.bbb Signalling protocols (UE to Detailed and bit-exact stage 3 specifications of
CN) protocols between MS/UE and the Core
Network.
05.bb 45.bbb 25.bbb Radio access aspects 25.1bb: UTRAN radio performance
25.2bb: UTRA layer 1
25.3bb: UTRA layers 2 & 3
25.4bb: UTRAN Iub, Iur & Iu interfaces
06.bb 46.bbb 26.bbb Codecs Speech and other codecs (video etc.).
07.bb 47.bbb 27.bbb Data Functions necessary to support data
applications.
08.bb 48.bbb 28.bbb Signalling protocols (RSS to Detailed and bit-exact stage 3 specifications of
CN) protocols between radio subsystem (eg BSS)
and periphery of CN (eg MSC). (Not used in
Release 1999.)
09.bb 49.bbb 29.bbb Core Network signalling Detailed and bit-exact stage 3 specifications of
protocols protocols within the Core Network.
rd
10.bb 50.bbb 30.bbb Programme management 3 Generation Mobile System, project plans /
project work programme and stand-alone
documents for major Work Items.
11.bb 51.bbb 31.bbb SIM / UIM Subscriber / User Identity Module and the
interfaces between it and other entities.
rd
12.bb 52.bbb 32.bbb Charging and OAM&P Application of TMN for the 3GPP 3
(Operations, Administration, Generation Mobile System and other functions
Maintenance & Provisioning) for operation, administration and maintenance
rd
of a 3 Generation Mobile System network.
13.bb  Regulatory test specifications. (Transferred
from ETSI TC SMG to ETSI TC MSG.)
33.bbb Security aspects
34.bbb Test specifications
55.bbb 35.bbb Algorithms Specifications of encryption algorithms for
confidentiality and authentication, etc.
36.bbb Evolved Universal Terrestrial Introduced in Release 8 for the so-called
Radio Access (Network) "Long Term Evolution" of the radio technology.
A similar subdivision to that used for the 25-
series above is used.
37.bbb Multiple radio access Such as handover, fallback, interworking.
technology aspects
38.bbb 5G "New Radio" Release 14: first studies.
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 10 ETSI TR 121 900 V15.1.1 (2018-11)
Range for Range for Range for Use Remarks
GSM up GSM UMTS
to and Release 4 Release
including onwards 1999
Release onwards
NOTE: Column 1 refers to the original GSM specification series used up to Release 1999.
Column 2 refers to the specifications peculiar to GSM implementations for Release 4 onwards – that is,
those specifications relating solely to GSM/EDGE radio access.
Column 3 refers to the specifications created by 3GPP for Release 1999 onwards implementations having a
UTRAN radio access. Many of these are common to GSM/EDGE and UTRAN systems (see table 2).
Separate specifications list the specs required to implement Releases GSM/EDGE and UTRAN systems
(3GPP TSs 21.101 [3], 01.01 / 41.101 [4]).

Table 2: Specification number ranges bbb
Range Use Remarks
aa.bb Specification applicable to pre-Release-4 GSM Continue to be maintained by 3GPP. Not propagated
systems. beyond Release 1999.
aa.0bb Specifications applicable to both 2G (GSM) and aa in range 21 to 39:
3G systems. For most specifications in this range for a given
Release, a GSM specification numbered [aa - 20].[bb]
will have existed for earlier Releases.
Example: 3GPP TS 28.032 replaces GSM 08.32 for
Release 1999 onwards.
aa in range 41 to 59:
Direct equivalent to aa.bb GSM specification for
previous Releases.
aa.1bb Specification either (a) derived from earlier 2G aa in range 21 to 39:
(GSM) specification, but with technical For most specifications in this range for a given
modification; or (b) new specifications. Release, a GSM specification numbered
[aa - 20].[bbb - 100] will have existed for earlier
Releases, and may continue to exist (in parallel) for the
same Release.
Example: 3GPP TS 28.133 will have been based on
GSM 08.33, but both specifications exist for
Release 1999 onwards.
aa in range 41 to 59:
New GSM specification for Release 4 or later.
aa.2bb New specifications. Not, in general, derived from pre-Release 4 GSM
to predecessors.
aa.7bb NOTE: See table 1 for specific allocation within
25.bbb series.
aa.8bb Technical Reports not intended for publication. Working documents of 3GPP Groups not intended to be
transposed into publications by the Partner
Organizations.
aa.9bb Technical Reports intended for publication. As distinct from those of the aa.8bb series.

ETSI
3GPP TR 21.900 version 15.1.1 Release 15 11 ETSI TR 121 900 V15.1.1 (2018-11)
4.0A Version nomenclature
Each specification is associated with a "version number" in the form x.y.z which uniquely identifies the document. The
significance of the three fields is defined in table 3.
Table 3: Version number fields
Field Use Remarks
x major 0: draft
also referred to as "release" 1: presented to TSG for information
(specification estimated by prime responsible
Group to be at least 60% stable)
2: presented to TSG for approval (specification
estimated by prime responsible Group to be
at least 80% stable)
3 or greater: approved by TSG and under change
control; the value indicates the Release
according to table 4.
y technical Incremented every time a technical change is
introduced into the specification. Once under change
control, such changes shall only occur when the TSG
approves one or more Change Requests. Reset to zero
every time the "major" field is incremented.
z editorial Incremented every time a purely editorial change is
introduced into the specification. Reset to zero every
time the "technical" field is incremented or reset to zero.

Table 3 shows the estimated degree of stability to be used as a guideline for determining when to raise a specification to
version 1.y.z and to 2.y.z. Such figures are obviously subjective, and the decision is ultimately at the discretion of the
responsible Group.
A TS or TR having reached at least 60% stability and presented to the TSG for the first time shall be presented with its
major version number set to 1, i.e. as version 1.y.z.
4.0B Releases
Specifications are grouped into "Releases". A mobile system can be constructed based on the set of all specifications
which comprise a given Release. A Release differs from the previous Release by having added functionality introduced
as a result of ongoing standardization work within the Groups.
Specifications pertaining to a given Release shall be distinguished by the first field of the version number ("x" in x.y.z)
according to table 4. Table 0 also shows for comparison the equivalent significance of the GSM Releases.
For further details on Release control, see subclause 4.10.
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 12 ETSI TR 121 900 V15.1.1 (2018-11)
Table 4: Version numbers vs. Releases
Spec under change control for … spec number
format and
version
GSM Phase 1 aa.bb v3.y.z
GSM Phase 2 aa.bb v4.y.z
GSM Phase 2+ Release 1996 aa.bb v5.y.z
GSM Phase 2+ Release 1997 aa.bb v6.y.z
GSM Phase 2+ Release 1998
aa.bb v7.y.z
GSM Phase 2+ Release 1999
aa.bb v8.y.z
(pure GERAN-based system)
pure UTRAN-based system and common aa.bbb v3.y.z
UTRAN- & GERAN-based systems
Release 1999
GERAN- & UTRAN-based systems aa.bbb v4.y.z
Release 4
GERAN- & UTRAN-based systems
aa.bbb v5.y.z
Release 5
GERAN- & UTRAN-based systems
aa.bbb v6.y.z
Release 6
GERAN- & UTRAN-based systems aa.bbb v7.y.z
Release 7
… …
NOTE: From Release 4 onwards the 3GPP format for
specification numbers and versions applies to all
specifications (including those only relevant for
implementation of a stand-alone GSM system).

4.1 Overview
Where appropriate, the three-stage methodology defined in ITU-T Recommendation I.130 should be employed:
Stage 1 is an overall service description from the user’s standpoint.
Stage 2 is an overall description of the organization of the network functions to map service requirements into
network capabilities.
Stage 3 is the definition of switching and signalling capabilities needed to support services defined in stage 1.
In addition, it is often appropriate to perform a feasibility study prior to formal specification work. This is sometimes
referred to as "stage 0".
Furthermore, it will often be appropriate to follow stage 3 with the production of test specifications – a stage 4.
4.1.1 General
A new specification shall be created in a Group. At creation, a rapporteur shall be appointed. The rapporteur shall
produce an initial draft, version 0.0.0, and subsequent revised versions (version 0.1.0, possibly 0.1.1, 0.1.2 and so on,
then version 0.2.0 etc.). Details of the role of the rapporteur are described in subclause 4.1.2.
The rules for drafting specifications, and the software tools to be used are listed in 3GPP TR 21.801 [1].
Versions 0.1.0, 0.2.0, 0.3.0 etc. should be presented to the responsible Group. Versions 0.i.1, 0.i.2 etc. may be internal
to the drafting group.
Further drafts may be produced, with appropriate increments in the "technical" / "editorial" fields of the version
number. Every new draft with an incremented "technical" version field shall be presented to the responsible Group.
Although two or more Groups may have an interest in contributing to the development of a specification, ultimate
responsibility vests in a single (responsible) Group. The responsible Group shall ensure that all other Groups which
might have an interest are given the opportunity to participate in the drafting. The objectives intended to be provided or
decided by a working group with secondary responsibility shall be made clear in a corresponding Work Item
Description document, identifying additional rapporteurs from such secondary group(s) if necessary.
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 13 ETSI TR 121 900 V15.1.1 (2018-11)
The Support Team is responsible for allocating specification numbers. As soon as title, scope and some other
information on the specification is stable, the Support Team shall assign a specification number according to the
provisions of subclause 4.0 and shall enter the specification into the Status List of Specifications (see clause 7). The
TSG Sub-Group responsible for the specification shall inform its parent TSG that such a new specification is under
construction.
When a specification is sufficiently stable (see table 3), it shall be converted to version 1.0.0 (with no technical changes
with respect to the previous version 0.y.z) by the Support Team, and presented to the TSG for information. Further
drafts bearing version numbers 1.y.z may be produced until the specification is sufficiently stable to be approved by the
TSG. At this stage, and until formal approval by the TSG, the specification is, unless it belongs directly to a TSG, under
the control of the responsible TSG Sub-Group. The modalities governing the introduction of changes shall be decided
on a case by case basis by the WG concerned.
Once the responsible Group considers that the draft is sufficiently stable (see table 3) that it is desirable to place it under
change control, the latest version 1.y.z shall be converted to version 2.0.0 (with no technical changes with respect to the
previous version 1.y.z) by the Support Team and presented for approval at the TSG.
If the TSG does not approve the draft, further drafts version 2.y.z may be produced by the responsible Group.
If the TSG does approve the draft, the approved version (with no technical changes) shall be converted to version x.0.0
where "x" corresponds to the Release identity given in table 4.
NOTE: It is thus quite normal that a 3GPP specification approved for, say, Release 4, jumps directly from version
2.0.0 to version 4.0.0; there is no Release 1999 document, therefore no version 3.y.z.
The specification shall now be under TSG change control. Further changes shall be made by means of formal Change
Requests, to be approved by the TSG. On approval of a CR, the middle number shall be incremented and the right-most
number reset to 0 (e.g., from 7.2.1 to 7.3.0).
4.1.2 Role of the rapporteur
The role of the rapporteur is to:
- Serve as Editor (following the guidance of the WG) until the specification is placed under change control.
- Deliver a clean specification to the MCC for editorial clean-up before submission for TSG approval to come
under change control.
and, in co-operation with MCC, to:
- Review all CRs to the specification prior to agreement in the Working Group. This includes identifying and
resolving clashes.
- Oversee the technical quality of the specification.
- Explain the specification to any other group (TSC, TSG, inside or outside 3GPP), where appropriate.
- Serve as focal point for technical questions.
4.2 Characteristics of a specification
- The specification has a prime responsible TSG.
- The specification may have a prime responsible TSG WG.
- The specification may have one or more secondary responsible TSGs and/or TSG WGs. WIDs will express the
specific objectives justifying changes to the specification or any other action by any Group with secondary
responsibility.
- The specification may have a prime responsible TSG Sub-Group below a Working Group as decided by the
prime responsible TSG Working Group.
- The specification shall have a rapporteur: a delegate from a member company (or, in exceptional cases, a
Support Team expert); the delegate should participate regularly in the prime responsible TSG WG (and further
TSG SG if applicable).
ETSI
3GPP TR 21.900 version 15.1.1 Release 15 14 ETSI TR 121 900 V15.1.1 (2018-11)
- The specification is a Technical Report or a Technical Specification
- A specification has versions which are identified by three numbers (see 4.0A).
4.3 Characteristics of a major version of a specification
A major version 0 or 1 or 2 of a specification has the following characteristics:
- It is either a draft or withdrawn.
- It is TSG internal.
A major version w > 2 of a specification has the following characteristics:
- It is either under TSG WG Change Control or under TSG Change Control or closed or withdrawn.
- It is either authorized for publication or TSG internal.
A major version of a specification under TSG WG Change Control is TSG internal.
A major version under TSG WG Change Control or TSG Change Control is called major version under Change
Control.
A major version of a specification under TSG Change Control is
- either not yet frozen or frozen.
Note
...