text
stringlengths 1
761
| file_name
stringclasses 554
values |
|---|---|
Scope | 21900-i10.docx |
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 | 21900-i10.docx |
. 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. | 21900-i10.docx |
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 nonspecific.
- For a specific reference, subsequent revisions do not apply. | 21900-i10.docx |
- 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". | 21900-i10.docx |
[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". | 21900-i10.docx |
[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". | 21900-i10.docx |
[6] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[7] IETF RFC 3629: "UTF-8, a transformation format of ISO 10646".
2 Definitions and abbreviations
For the purposes of the present document, the following terms and those in 3GPP TR 21.905 [2] apply. | 21900-i10.docx |
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: release status in which no changes of any kind to the specification are permitted. | 21900-i10.docx |
closed: release 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. | 21900-i10.docx |
feature: new or substantially enhanced functionality which represents added value to the existing system.
frozen: release status in which only essential corrections are permitted.
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. | 21900-i10.docx |
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.
Mobile Competence Centre (MCC): The permanent secretariat, or support team, of 3GPP. | 21900-i10.docx |
pseudo Change Request (pCR): similar to a Change Request but has no CR number and is intended to propose new or revised text for inclusion in 3GPP TSs or TRs not yet under change control (i.e. still in the drafting phase). Known in some groups as "text proposal".
specification: generic term standing for Technical Specification and Technical Report. | 21900-i10.docx |
specification: generic term standing for Technical Specification and Technical Report.
Study Item (SI): type of Work Item which will conduct feasibility studies and will result in a Technical Report
Study Item description (SID): description of a Study Item in a standard Work Item Description sheet.
TSG: Technical Specification Group.
TSG change control: specification status in which the Technical Specification Group is responsible for approval of Change Requests. | 21900-i10.docx |
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. | 21900-i10.docx |
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. | 21900-i10.docx |
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. | 21900-i10.docx |
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. | 21900-i10.docx |
It furthermore includes liaison with other bodies and relevant groups and institutions.
3.2 Registration of code points | 21900-i10.docx |
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/). | 21900-i10.docx |
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.
4 Handling of Specifications
4.0 Numbering scheme | 21900-i10.docx |
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). | 21900-i10.docx |
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 | 21900-i10.docx |
Table 1: Specification number ranges aa
Range for GSM up to and including Release 1999
Range for GSM Release 4 onwards
Range for UMTS Release 1999 onwards
Use
Remarks
01.bb
41.bbb
21.bbb
Requirements specifications | 21900-i10.docx |
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 | 21900-i10.docx |
02.bb
42.bbb
22.bbb
Service aspects | 21900-i10.docx |
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. | 21900-i10.docx |
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 CN) | 21900-i10.docx |
24.bbb
Signalling protocols (UE to CN)
Detailed and bit-exact stage 3 specifications of protocols between MS/UE and the Core Network.
05.bb
45.bbb
25.bbb
Radio access aspects | 21900-i10.docx |
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 | 21900-i10.docx |
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 | 21900-i10.docx |
48.bbb
28.bbb
Signalling protocols (RSS to CN)
Detailed and bit-exact stage 3 specifications of protocols between radio subsystem (eg BSS) and periphery of CN (eg MSC). (Not used in Release 1999.)
09.bb
49.bbb
29.bbb | 21900-i10.docx |
49.bbb
29.bbb
Core Network signalling protocols
Detailed and bit-exact stage 3 specifications of protocols within the Core Network.
10.bb
50.bbb
30.bbb
Programme management
3rd Generation Mobile System, project plans / project work programme and stand-alone documents for major Work Items. | 21900-i10.docx |
11.bb
51.bbb
31.bbb
SIM / UIM
Subscriber / User Identity Module and the interfaces between it and other entities.
12.bb
52.bbb
32.bbb
Charging and OAM&P (Operations, Administration, Maintenance & Provisioning) | 21900-i10.docx |
Charging and OAM&P (Operations, Administration, Maintenance & Provisioning)
Application of TMN for the 3GPP 3rd Generation Mobile System and other functions for operation, administration and maintenance of a 3rd Generation Mobile System network.
13.bb
Regulatory test specifications. (Transferred from ETSI TC SMG to ETSI TC MSG.) | 21900-i10.docx |
33.bbb
Security aspects
34.bbb
Test specifications
55.bbb
35.bbb
Algorithms
Specifications of encryption algorithms for confidentiality and authentication, etc. | 21900-i10.docx |
36.bbb
Evolved Universal Terrestrial Radio Access (Network)
Introduced in Release 8 for the so-called "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 technology aspects | 21900-i10.docx |
37.bbb
Multiple radio access technology aspects
Such as handover, fallback, interworking.
38.bbb
5G "New Radio"
Release 14: first studies.
NOTE: Column 1 refers to the original GSM specification series used up to Release 1999. | 21900-i10.docx |
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. | 21900-i10.docx |
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]). | 21900-i10.docx |
Table 2: Specification number ranges bbb
Range
Use
Remarks
aa.bb
Specification applicable to pre-Release-4 GSM systems.
Continue to be maintained by 3GPP. Not propagated beyond Release 1999.
aa.0bb
Specifications applicable to both 2G (GSM) and 3G systems. | 21900-i10.docx |
Specifications applicable to both 2G (GSM) and 3G systems.
aa in range 21 to 39:
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: | 21900-i10.docx |
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 (GSM) specification, but with technical modification; or (b) new specifications.
aa in range 21 to 39: | 21900-i10.docx |
aa in range 21 to 39:
For most specifications in this range for a given 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. | 21900-i10.docx |
aa in range 41 to 59:
New GSM specification for Release 4 or later.
aa.2bb to aa.7bb
New specifications.
Not, in general, derived from pre-Release 4 GSM predecessors.
NOTE 1: See table 1 for specific allocation within 25.bbb series. | 21900-i10.docx |
NOTE 1: See table 1 for specific allocation within 25.bbb series.
NOTE 2: For some specification series, the stock of aa.8bb TRs has been exhausted, and in these cases, further internal TRs are allocated aa.7bb numbers.
aa.8bb
Technical Reports not intended for publication. | 21900-i10.docx |
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.
4.0A Version nomenclature | 21900-i10.docx |
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
also referred to as "release" | 21900-i10.docx |
x
major
also referred to as "release"
0: draft
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) | 21900-i10.docx |
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 | 21900-i10.docx |
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. | 21900-i10.docx |
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. | 21900-i10.docx |
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 | 21900-i10.docx |
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. | 21900-i10.docx |
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 4 also shows for comparison the equivalent significance of the GSM Releases.
For further details on Release control, see clause 4.10.
Table 4: Version numbers vs. Releases
Spec under change control for …
spec number format and version | 21900-i10.docx |
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 | 21900-i10.docx |
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
(pure GERAN-based system)
aa.bb v8.y.z
pure UTRAN-based system and common UTRAN- & GERAN-based systems Release 1999 | 21900-i10.docx |
aa.bbb v3.y.z
GERAN- & UTRAN-based systems Release 4
aa.bbb v4.y.z
GERAN- & UTRAN-based systems Release 5
aa.bbb v5.y.z
GERAN- & UTRAN-based systems Release 6
aa.bbb v6.y.z | 21900-i10.docx |
aa.bbb v6.y.z
GERAN- & UTRAN-based systems Release 7
aa.bbb v7.y.z
…
…
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). | 21900-i10.docx |
4.1 Overview
Where appropriate, the three-stage methodology defined in ITUT 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. | 21900-i10.docx |
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 | 21900-i10.docx |
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 clause 4.1.2. | 21900-i10.docx |
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. | 21900-i10.docx |
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 | 21900-i10.docx |
. 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. | 21900-i10.docx |
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 clause 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. | 21900-i10.docx |
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 | 21900-i10.docx |
. 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 | 21900-i10.docx |
. The modalities governing the introduction of changes shall be decided on a case by case basis by the WG concerned. | 21900-i10.docx |
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. | 21900-i10.docx |
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. | 21900-i10.docx |
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. | 21900-i10.docx |
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 specification rapporteur | 21900-i10.docx |
4.1.2 Role of the specification 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: | 21900-i10.docx |
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 (WG, TSG, inside or outside 3GPP), where appropriate.
- Serve as focal point for technical questions. | 21900-i10.docx |
- 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. | 21900-i10.docx |
- 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. | 21900-i10.docx |
- 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).
- The specification is a Technical Report or a Technical Specification
- A specification has versions which are identified by three numbers (see 4.0A). | 21900-i10.docx |
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: | 21900-i10.docx |
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. | 21900-i10.docx |
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: In the description above, attribute values are bold. | 21900-i10.docx |
NOTE: In the description above, attribute values are bold.
4.4 Characteristics of a version of a specification
0.x.y
- draft (or withdrawn)
- TSG internal
- no version of the specification has been presented for information to the TSG yet
- no major version of the specification is under TSG change control yet | 21900-i10.docx |
- no major version of the specification is under TSG change control yet
1.0.0
- draft (or withdrawn)
- TSG internal
- this version 1.0.0 is presented to TSG
- for information
- or for information and approval
- no major version of the specification has been under TSG Change Control yet | 21900-i10.docx |
- no major version of the specification has been under TSG Change Control yet
1.x.y (x > 0 or y > 0)
- draft (or withdrawn)
- earlier version 1.0.0 has been presented for information to the TSG
- no major version of the specification is under TSG Change Control yet
2.0.0 | 21900-i10.docx |
2.0.0
- draft or withdrawn
- TSG internal
- earlier version 1.0.0 has been presented for information to the TSG
- this version 2.0.0 is presented to the TSG for approval
- no version of the specification has been approved yet
- no major version of the specification has been under TSG Change Control yet | 21900-i10.docx |
- no major version of the specification has been under TSG Change Control yet
2.x.y (x > 0 or y > 0)
- draft
- TSG internal
[- earlier version 1.0.0 has been presented for information to the TSG]
- no major version of the specification is under TSG Change Control yet | 21900-i10.docx |
- no major version of the specification is under TSG Change Control yet
- earlier version 2.0.0 had been presented to the TSG for approval but had not been approved by the TSG
x.y.z (x 3)
- under TSG Change Control or closed
- TSG internal or authorized for publication | 21900-i10.docx |
- TSG internal or authorized for publication
[- earlier version 1.0.0 has been presented for information to the TSG]
- earlier major versions of the specification, if any, shall be under TSG Change Control or closed or withdrawn
draft y.z of version x
- under TSG WG Change Control
- TSG internal | 21900-i10.docx |
- under TSG WG Change Control
- TSG internal
[- earlier version 1.0.0 has been presented for information to TSG]
- earlier major versions of the specification, if any, shall be under TSG Change Control or closed or withdrawn | 21900-i10.docx |
NOTE: In the table above, statements between square brackets are true but not relevant. The first two lines of each row are implied by clause 4.2.
4.5 (void)
4.6 Change Request regime
4.6.1 Change Requests | 21900-i10.docx |
4.6 Change Request regime
4.6.1 Change Requests
Once a specification has been approved by the TSG and version x.0.0 (where x >= 3, corresponding to the Release - see table 4) has been produced, it shall be considered to be under change control. Any technical change which may be identified for inclusion in the specification from this point on shall be accomplished by means of a Change Request (CR). | 21900-i10.docx |
A CR may be raised by any individual member and brought to the attention of the responsible Group. | 21900-i10.docx |
A Change Request shall relate to a specific version of a specification. A unique (for that specification) reference number shall be allocated to the CR by the 3GPP portal or the Support Team. CR details shall be entered into a CR database maintained by the Support Team and made available on the 3GPP file server | 21900-i10.docx |
. CR numbers shall not be re-used, even if a CR is ultimately rejected by the TSG (see note). A CR may undergo one or more revisions before a final decision is made on it. The database shall show all revisions of each CR. | 21900-i10.docx |
NOTE: The CR status "rejected", and indeed this status for any other TDoc type has become unacceptable in some groups, and is replaced by "not pursued". Unless evident from the context, in the present document, any reference to the status "rejected" applies equally to status "not pursued". | 21900-i10.docx |
The TSG WG Secretary shall collate all CRs agreed by the WG and shall send them to the parent TSG for approval. For specifications which are directly under the control of a TSG, the CR shall be brought directly to the attention of the TSG. | 21900-i10.docx |
Following approval at TSG level, the Support Team person responsible for the specification shall edit the original specification to incorporate the changes of all Change Requests approved by the TSG. The new version of the specification shall then be made available on the 3GPP file server. | 21900-i10.docx |
The TSG should approve, reject or postpone a CR in its entirety (after revision, if necessary). That is, the modifications proposed by the CR should either be accepted without change, or unconditionally rejected. For ease of management, a single Change Request should therefore pertain to a single technical topic only. Each topic can thus be cleanly accepted or rejected by the TSG. | 21900-i10.docx |
Where two or more CRs pertain to the same (version of a) specification, the responsible Group shall check for potential interaction amongst those CRs to ensure that, if all are approved by the TSG, each is implementable without contradicting any other. | 21900-i10.docx |
The TSG Secretary shall record the TSG's decisions (see table 9.2-1) on each CR in the meeting report and those decisions shall be reflected in the CR database and on the 3GPP portal.
4.6.2 Change Request forms | 21900-i10.docx |