Dataset Viewer
hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
f193e84844076b4f7262087f58142986 | 21.801 | 1 Scope | The present document specifies rules for the structure and drafting of documents intended to become a 3GPP Technical Specification or Technical Report. These rules are intended to ensure that such documents are drafted in as uniform a manner as is practicable, irrespective of the technical content.
The present document is based on the ISO/IEC Directives, Part 3, but is a self-contained document that will be maintained as such.
These drafting rules complement the 3GPP Working Procedures. |
f193e84844076b4f7262087f58142986 | 21.801 | 2 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] ISO/IEC Directives - Part 3 (1997): "Rules for the structure and drafting of International Standards".
[2] ISO/IEC Guide 2:1996: "Standardization and related activities - General vocabulary".
[3] 3GPPย TRย 21.905: "Vocabulary for 3GPP Specifications".
[4] ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework".
[5] ETSI ES 201ย 873 (all parts): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3". |
f193e84844076b4f7262087f58142986 | 21.801 | 3 Definitions and abbreviations | |
f193e84844076b4f7262087f58142986 | 21.801 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TRย 21.905ย [3] and the following apply:
informative elements: those elements that provide additional information intended to assist the understanding or use of the 3GPP TS or 3GPP TR
instruction: provision that conveys an action to be performed [ISO/IEC Guide 2:1996, definition 7.3]
normative element: an element setting out provisions to which it is necessary to conform in order to be able to claim compliance with the Technical Specification
provision: expression in the content of a normative document, that takes the form of a statement, an instruction, a recommendation or a requirement [ISO/IEC Guide 2:1996, definition 7.1]
NOTE: These types of provision are distinguished by the form of wording they employ; e.g. instructions are expressed in the imperative mood, recommendations by the use of the auxiliary "should" and requirements by the use of the auxiliary "shall" (see annex E).
recommendation: provision that conveys advice or guidance [ISO/IEC Guide 2:1996, definition 7.4]
requirement: provision that conveys criteria to be fulfilled [ISO/IEC Guide 2:1996, definition 7.5]
statement: provision that conveys information [ISO/IEC Guide 2:1996, definition 7.2] |
f193e84844076b4f7262087f58142986 | 21.801 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TRย 21.905ย [3] and the following apply:
ICS Implementation Conformance Statement
OMML Office Math Markup Langugage
PDF Portable Document Format
SDL Specification and Description Language
TR Technical Report
TS Technical Specification
TTCN-2 Tree and Tabular Combined Notation
TTCN-3 Testing and Test Control Notation |
f193e84844076b4f7262087f58142986 | 21.801 | 4 General principles | |
f193e84844076b4f7262087f58142986 | 21.801 | 4.1 Objective | The objective of a 3GPP Technical Specification or Technical Report is to define clear and unambiguous provisions in order to facilitate international trade and communication. To achieve this objective, the 3GPP TS or TR shall:
- be as complete as necessary within the limits specified by its scope;
- be consistent, clear and accurate;
- provide a framework for future technological development; and
- be comprehensible to qualified persons who have not participated in its preparation. |
f193e84844076b4f7262087f58142986 | 21.801 | 4.2 Homogeneity | Uniformity of structure, of style and of terminology shall be maintained not only within each 3GPP TS or 3GPP TR, but also within a series of associated 3GPP TSs or 3GPP TRs. The structure of associated 3GPP TSs or 3GPP TRs and the numbering of their clauses shall, as far as possible, be identical. Analogous wording shall be used to express analogous provisions; identical wording shall be used to express identical provisions.
The same term shall be used throughout each 3GPP TS or 3GPP TR or series of 3GPP TSs or 3GPP TRs to designate a given concept. The use of an alternative term (synonym) for a concept already defined shall be avoided. As far as possible, only one meaning shall be attributed to each term chosen.
These requirements are particularly important not only to ensure comprehension of the 3GPP TS or 3GPP TR but also to derive the maximum benefit available through automated text processing techniques.
See also clause 5.3. |
f193e84844076b4f7262087f58142986 | 21.801 | 4.3 Consistency of 3GPP TSs and 3GPP TRs | In order to achieve the aim of consistency within the complete body of 3GPP TSs and 3GPP TRs, the text of every 3GPP TS and 3GPP TR shall be in accordance with the relevant provisions of existing basic 3GPP TSs and 3GPP TRs. This relates particularly to:
- standardized terminology;
- principles and methods of terminology;
- quantities, units and their symbols;
- abbreviations;
- bibliographic references; and
- graphical symbols.
In addition, for specific technical aspects, the relevant provisions of general 3GPP TSs or 3GPP TRs dealing with the following subjects shall be respected:
- limits;
- tolerancing of dimensions and uncertainty of measurement;
- preferred numbers;
- statistical methods;
- environmental conditions and associated tests. |
f193e84844076b4f7262087f58142986 | 21.801 | 4.4 Equivalence of official language versions | 3GPP TSs or 3GPP TRs shall be in the English language only. |
f193e84844076b4f7262087f58142986 | 21.801 | 4.5 Fitness for implementation as a national, regional or international standard | The content of a 3GPP TS or 3GPP TR shall be drawn up in such a way as to facilitate its direct application and its adoption without change as a national, regional or international standard. |
f193e84844076b4f7262087f58142986 | 21.801 | 4.6 Planning | In order to ensure the timely publication of a 3GPP TS or 3GPP TR or of a series of associated 3GPP TSs or 3GPP TRs, the intended structure and any interrelationships shall be established before detailed drafting begins. In particular, consideration shall be given to the subdivision of the subject matter (see clauseย 5.1). In the case of a multi-part 3GPP TS or 3GPP TR, a list of the intended parts together with their titles shall be drawn up. The rules given in the present document shall be applied from the very beginning of the work and throughout all subsequent stages to avoid delay at any stage. |
f193e84844076b4f7262087f58142986 | 21.801 | 4.7 (void) | |
f193e84844076b4f7262087f58142986 | 21.801 | 4.8 Use of inclusive language | 3GPP TSs and TRs should not contain non-inclusive terminology.
Terms that have been deemed to fall into this category are listed in Annexย K and should be replaced by inclusive terminology.
Where a change in terminology would introduce backwards incompatibilities or interoperability issues, a deliverable may contain such terminology. |
f193e84844076b4f7262087f58142986 | 21.801 | 5 Structure | |
f193e84844076b4f7262087f58142986 | 21.801 | 5.1 Subdivision of the subject matter | |
f193e84844076b4f7262087f58142986 | 21.801 | 5.1.1 General | 3GPP TSs or 3GPP TRs are so diverse that no universally acceptable rules can be established for the subdivision of the subject matter.
However, as a general rule, an individual 3GPP TS or 3GPP TR shall be prepared for each subject to be standardized, and published as a complete entity. In specific cases and for practical reasons, for example:
- the 3GPP TS or 3GPP TR is likely to become too voluminous;
- subsequent portions of the content are interlinked;
- portions of the 3GPP TS or 3GPP TR could be referred to in regulations; or
- portions of the 3GPP TS or 3GPP TR are intended to serve for certification purposes,
the 3GPP TS or 3GPP TR may be split into separate parts under the same number. This has the advantage that each part can be changed separately when the need arises.
In particular, the aspects of a product which will be of separate interest to different parties (e.g. manufacturers, operators, certification bodies, legislative bodies) shall be clearly distinguished, preferably as parts of a 3GPP TS or 3GPP TR or as separate 3GPP TSs or 3GPP TRs.
Such individual aspects are, for example:
- performance requirements;
- maintenance and service requirements; and
- quality assessment.
The terms that shall be used to designate the divisions and subdivisions that a 3GPP TS or 3GPP TR may have are shown in table 1.
Table 1: Names of divisions and subdivisions
Term
Example of numbering
part
clause
clause
clause
annex
clause
clause
3GPP TS 21.299-1
1
1.1
1.1.1
A
A.1
A.1.1 |
f193e84844076b4f7262087f58142986 | 21.801 | 5.1.2 Subdivision of the subject matter within a series of parts | There are two systems in use for subdividing into parts:
a) Each part deals with a specific aspect of the subject and can stand alone.
b) There are both common and specific aspects to the subject. The common aspects shall be given in part 1. Specific aspects (which may modify or supplement the common aspects and therefore cannot stand alone) shall be given in individual parts.
Where the system described in b) is used, care shall be taken that the references from one part to another are always to the latest version. There are two ways to achieve this:
- If reference is made to a particular element, the reference shall be specific (see clauseย 6.6.6.5.2).
- Since the complete series of parts is normally under the control of the same TSG, the use of non-specific references (see clauseย 6.6.6.5.3) is permitted, provided that corresponding changes are implemented simultaneously in all parts.
The use of non-specific references requires a high degree of discipline by the TSG responsible for the 3GPP TS or 3GPP TR.
Their use is not permitted between 3GPP TSs or 3GPP TRs of different Technical Bodies except where the reference is intentionally non-specific, i.e. it is accepted that it will be possible to use all future changes of the text referred to for the purposes of the referring 3GPP TS or 3GPP TR.
Each part of a multi-part 3GPP TS or 3GPP TR shall be drafted in accordance with the rules for an individual 3GPP TS or 3GPP TR as specified in the present document. |
f193e84844076b4f7262087f58142986 | 21.801 | 5.1.3 Subdivision of the subject matter within an individual 3GPP TS or 3GPP TR | Table 2: Example of a typical arrangement of elements in a 3GPP TS or 3GPP TR
Type of element
Arrangement of elements in
3GPP TS or 3GPP TR (note 1)
Permitted content of element(s) in 3GPP TS or 3GPP TR (note 1)
Informative preliminary
Title pages
title, number, logo(s), copyright statement, etc
Table of contents
(generated content, see clause 6.1.2)
Foreword
text (noteย 3)
Introduction
text, figures, tables, notes
Scope
text, figures, tables, notes
References
stock text followed by numbered references of documents specifically cited in the TS/TR (noteย 4)
Definition of
terms,
symbols and
abbreviations
stock text plus specific definitions
(note 4)
text, notes
Normative technical (TS)
Informative technical (TR)
Clauses comprising the main body of the document
text, figures, tables, notes, equations
(note 2)
Normative supplementary (TS)
Annexes
text, figures, tables, notes, equations
(notes 2, 5)
Informative supplementary
Annexes
text, figures, tables, notes, equations
(notes 2, 5)
Bibliography
unnumbered list of documents for further reading not specifically cited elsewhere in the TS/TR
Index
Change history annex
table (notes 3, 6)
NOTE 1: Bold type = required element. These elements shall not be removed from the skeleton TS/TR. Elements in normal weight type are optional and shall be omitted from the TS/TR if not required.
NOTE 2: Informative elements shall not contain normative content. Normative elements may additionally contain informative content.
NOTE 3: Provided by the 3GPP Support Team.
NOTE 4: Partly provided by the 3GPP Support Team.
NOTE 5: The order of inclusion of annexes and the mix of normative and informative annexes is not mandated by the present document. There is no requirement that all normative annexes precede any informative annexes.
NOTE 6: The change history annex shall always be the last annex of the TS/TR.
A 3GPP TS or 3GPP TR may also contain notes to figures and tables (see clausesย 6.6.4.8, 6.6.4.9, 6.6.5.6 and 6.6.5.7). |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2 Description and numbering of divisions and subdivisions | |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2.1 Parts and sub-parts | The number of a part shall be indicated by arabic numerals, beginning with 1, following the 3GPP TS or 3GPP TR number and preceded by a hyphen, for example:
- 3GPP TR 21.999-1, 3GPP TR 21.999-2.
5.2.1A General numbering issues
Every attempt shall be made to use continuous numbering as described in the remainder of 5.2. However, if continuous numbering cannot be maintained, a new element may be inserted in existing text using an appropriate alphanumeric designation that does not disturb the existing numbering scheme. This applies to all elements (e.g. clause, annex, figure, table, note, list).
EXAMPLE 1: It is necessary to update a 3GPP TS. A new clause needs to be inserted between the existing clauses 8 and 9. A new clause 8A may be inserted in preference to re-numbering the existing clauses.
EXAMPLE 2: A new figure needs to be inserted between existing figures 4 and 5. A new figure 4A may be inserted to avoid re-numbering of all subsequent figures.
Similarly, an existing element may be deleted and replaced with the term "Void." to minimize disruption to the numbering scheme. However, the title of the deleted element may be retained. See clause 5.2.1B for further details.
EXAMPLE 3: During the updating of a 3GPP TS, it is decided that annex C is no longer required. The title of annex C remains while the content simply becomes "Void.". Later annexes may therefore remain unchanged.
EXAMPLE 4: It is decided to delete a note 3, so the text of note 3 becomes "Void." and there is no need to reโnumber note 4.
Once a TS or TR is under change control, changing existing clause, figure, table, annex, etc. numbers is strongly deprecated, since external documents might reference specific clauses (figures, tables, ...) of the TS/TR.
5.2.1B Removal of redundant numbered elements
As described in clause 5.2.1A, it is occasionally necessary to remove text which has become obsolete or redundant. If an entire clause, or figure, table, or other numbered element having a title is concerned, the preferred method is to eliminate the text of the clause and to replace the title with the word "Void" in round brackets. Alternatively, if it is felt important to leave some trace of the clause's subject material prior to its removal, the author of the Change Request could leave the title of the element unchanged, and delete just the body of the text of the clause (or figure, or table, โฆ), replacing the text with the word "Void" in round brackets.
EXAMPLE 1: The following clause is to be removed:
11.2 Functional procedures associated with lunch
If a DISSOCIATE message is received containing the indicator "User out to lunch", then the equipment shall start timer T100 and respond with an ACKNOWLEDGE message containing the indicator "Have a nice siesta".
The preferred method, replacing the title of the clause with "Void" and deleting completely the text of the clause, yields:
11.2 (Void)
The alternative is to retain the title, and delete only the body text:
11.2 Functional procedures associated with lunch
(Void)
Whichever method is used, the author of a Change Request provoking such a change shall ensure that any reference to the clause in question from elsewhere in the same TS or TR is eliminated by appropriate inclusion in the same Change Request. Ideally, the author should also check for references to that specific clause in other 3GPP TSs or TRs if he suspects there might be any, and raise appropriate Change Requests to those TSs or TRs to modify or eliminate those references.
5.2.1C Avoidance of re-use of a voided element for a new purpose
A clause which has been voided using the procedures of clause 5.2.1B above shall not be re-used for a different purpose if at some subsequent moment it is necessary to add another clause in the same logical position as the clause previously voided.
That is, based on the example in clause 5.2.1B, a subsequent Change Request to add a clause entitled "Colour options for the on/off switch" โ which patently has no relationship to the original clause 11.2 โ shall not re-use clause 11.2, but shall be added as a clause with a completely new number (e.g. 11.3 or 11.2A).
The only circumstances in which re-use of a voided clause number might be appropriate is if the new clause were to have exactly or very nearly the same title as the original clause (in this case, "Functional procedures associate with lunch").
The same considerations apply to other numbered elements such as figures and tables. |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2.2 Clause | The clauses in each 3GPP TS or 3GPP TR or part shall be numbered with arabic numerals, beginning with 1 for the "Scope" clause. The numbering should be continuous, see also clauseย 5.2.1A.
Each clause shall have a title (for formatting see clauseย 5.2.3). |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2.3 Subclause | A subclause is a numbered subdivision of a clause. A primary subclause (e.g. subclauseย 5.1, 5.2, etc.) may be subdivided into secondary subclauses (e.g. subclausesย 5.1.1, 5.1.2, etc.) and this process of subdivision may be continued as far as the sixth heading level (e.g. subclauseย 6.5.4.3.2.1).
It is unnecessary to use the term "subclause" unless using the term "clause" would be ambiguous, for example, if in the context, it were not clear if the term "clause" referred only to the top level clause ("4") or to all the subclauses ("4.1", "4.1.1", "4.1.2", "4.2" etc) beneath the clause. Such ambiguity can only occur where there are hanging paragraphs; these are sometimes encountered in older 3GPP Technical Specifications and Technical Reports produced before the outlawing of hanging paragraphs (see clause 5.2.4).
Subclauses shall be numbered with arabic numerals, see also clauseย 5.2.1A.
A subclause should not be created unless there is at least one further subclause at the same level. For example, a piece of text in clause 10 should not be designated subclause "10.1" unless there is also a subclause "10.2".
Each subclause shall be given a title, which shall be placed after its number.
(Sub)clause titles shall be treated as normal text i.e. no additional capitalization; there should be no full stop at the end of a (sub)clause title.
- Use the Heading style appropriate to its level.
- Separate the number of the heading and the text of the heading with a tab.
- Do not use automatic heading numbering; you may, however, use it as an initial aid when outlining the structure of your document, as long as it is eliminated before handover to the 3GPP Support Team. |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2.4 Paragraph | "Hanging paragraphs" such as those shown in the following example shall be avoided since reference to them is ambiguous.
EXAMPLE: In the following example, the hanging paragraphs indicated cannot be uniquely identified as being in "clause 5" since strictly speaking the paragraphs in 5.1 and 5.2 are also in clause 5. To avoid this problem it would be necessary either to identify the unnumbered paragraphs as clause "5.1ย Xxxxxxxxxxxx" and to renumber the existing 5.1 and 5.2 accordingly (as shown), or to add a new clause header immediately below the header for clause 5 numbered it 5.0.
If hanging paragraphs are to be removed from a TS or TR already under change control, the renumbering of existing clauses being deprecated (see clause 5.2.1A), the newly introduced clause shall be numbered 5.0 (using the above example) and clauses 5.1 and 5.2 remain unchanged.
Permitted
Not permitted
5 Designation
5.1 Xxxxxxxxxxx
xxxxxxx x xxxxxxxxxxxxx xxxxxxxxxxxxxxxxx
xxxxxxx x xxxxxxxxxxxxx xxxxxxxxxxxxxxxxx
5.2 Xxxxxxxxxxx
xxxxxxx x xxxxxxxxxxxxx xxxxxxxxxxxxxxxxx
5.3 Xxxxxxxxxxx
xxxxxxx x xxxxxxxxxxxxx xxxxxxxxxxxxxxxxx
xxxxxxxxxxxx xxxxxxxxxxxxx
6 Test report
5 Designation
xxxxxxx x xxxxxxxxxxxxxย ย ย }
xxxxxxx x xxxxxxxxxxxxxย ย ย } hanging paragraphs
xxxxxxx x xxxxxxxxxxxxxย ย ย }
5.1 Xxxxxxxxxxx
xxxxxxx x xxxxxxxxxxxxx xxxxxxxxxxxxxxxxx
5.2 Xxxxxxxxxxx
xxxxxxx x xxxxxxxxxxxxx xxxxxxxxxxxxxxxxx
xxxxxxxxxxxx xxxxxxxxxxxxx
6 Test report |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2.5 Lists | Lists may be introduced by a sentence, a complete grammatical proposition followed by a colon, or by the first part of a proposition (without a colon), completed by the items in the list.
Each item in a list shall be preceded by a dash.
EXAMPLE 1:
- list item 1;
- list item 2.
If necessary for identification, a lower-case letter followed by a parenthesis may be used. If it is necessary to subdivide an item further in this type of list, arabic numerals followed by a parenthesis shall be used (see also clauseย 5.2.1A).
EXAMPLE 2:
a) list item a;
b) list item b;
1) list item a1;
2) list item a2.
Respect normal rules of punctuation: if the elements of a list are cast as phrases of a sentence which introduces the list, start each element with a lower case letter and end it with a semicolon. End the last item in the list with a full stop, unless the introductory sentence continues after the end of the list, in which case use the most appropriate punctuation (semicolon, comma, or none). If, however, each element of a list is a self-contained sentence, begin each with a capital letter and end each with a full-stop.
Use "and" or "or" at the end (following the semicolon) of the penultimate element of a list to indicate unambiguously whether the elements are combinable or whether they are mutually exclusive.
- Use the appropriate bullet styles, i.e. stylesย B1 to B5.
- Separate the list item identifier (e.g. bullet) and the text with a tab (if not using automatic bullets and numbering).
- Ensure that the formatting of the lists is consistent throughout the deliverable. |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2.6 Annex | Each annex shall start on a new page.
Note: This is one of the very few places in a TS or a TR where a manual page break is likely to be legitimate. The skeleton model TS and TR documents contain other page or section breaks, for example at the end of the cover page, before the Contents page, before the Foreword and before the Scope clauses, and these are intended to remain in the final document. Elsewhere in 3GPP TSs and TRs, page breaks are better controlled by the use of the "keep lines together" and "keep with next" properties of paragraphs.
For the description of normative and informative annexes, see clausesย 6.3a and 6.4.1.
Each annex shall be designated by a heading comprising the word "Annex" followed by a capital letter designating its serial order, beginning with "A", e.g. "Annex A" (see also clauseย 5.2.1A). The annex heading of a TS shall be followed by the indication "(normative):" or "(informative):", and by the title on the next line. In the case of a TR, the entire document is informative, so the text "(normative):" or "(informative):" shall be omitted.
EXAMPLE: Annex A (normative):
Title of annex A
Numbers given to the clauses, tables, figures and mathematical formulae of an annex shall be preceded by the letter designating that annex followed by a full-stop (e.g. figure B.1-1, table C.4-3). The numbering shall start afresh with each annex. A single annex shall be designated "Annexย A".
Clauses in annex A shall be designated "A.1", "A.2", "A.3", etc. (see also clauseย 5.2.1A).
For endorsement of documents from other standards organizations, see annex J.
- Insert a manual page break before the title line of each annex. Use the Heading 8 style (for 3GPP TSs) or Heading 9 style(for 3GPP TRs) for the annex heading. Insert a line break (๏ฟ "shift" + "enter") between the colon and the title.
- For all clause headings use the appropriate Heading styles, starting from Headingย 1, e.g. for clause A.1 use Heading 1, for A.1.1 use Heading 2. Do not insert manual page breaks before each clause of an annex. |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2.7 Bibliography | A bibliography, if present, shall appear after the penultimate annex entitled "Bibliography". |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2.8 Index | An index, if present, shall appear as the last element. The title shall be "Index".
- Use Heading 1 style for the title. |
f193e84844076b4f7262087f58142986 | 21.801 | 5.2.9 Change history | Shall appear as the last element (informative annex).
- Use Heading 8 (for TS) or Heading 9 (for TR) style for the Annex title. |
f193e84844076b4f7262087f58142986 | 21.801 | 5.3 Consistency amongst Releases | In line with the general provisions of clause 4.2 (homogeneity), it is essential to preserve insofar as possible the structure of a TS or TR from one Release to another.
This is particularly important when voiding clauses (or figures, notes, etc) and when adding new clauses (figures, notes, etc). If a new clause is introduced, it shall be added in the logically correct place and shall be given a new clause number. It is not acceptable to re-use an existing, redundant, clause (ie one which had previously been used but has subsequently been voided).
Similarly, if an identical or near identical provision is introduced into two or more Releases, the provision should use the same clause (or figure, note, etc) number in each Release instance of the TS or TR. This may mean introducing void padding clauses (or figures, notes, etc) in older Release instances in order to keep the numbering aligned.
Example: The structure of the Release 10 version of a TS is
โฆ
5.3 Some provision
5.4 Another provision
5.5 A third provision
and, due to extra functionality having been added in the Release 11 instance, the structure of the Release 11 version of the TS has become
โฆ
5.3 Some provision
5.4 Another provision
5.5 A third provision
5.6 A new provision for Rel-11 only
5.7 Another new Rel-11 requirement
5.8 Something else peculiar to Rel-11
It is now decided to retrospectively add some requirement at Release 10, which will be mirrored in Release 11. The new clause shall have the same number in both Releases, with void padding clauses introduced into the Release 10 instance as necessary. Thus the structure of the Release 10 TS becomes
โฆ
5.3 Some provision
5.4 Another provision
5.5 A third provision
5.6 Void
5.7 Void
5.8 Void
5.9 An afterthought
and that of the Release 11 TS becomes
โฆ
5.3 Some provision
5.4 Another provision
5.5 A third provision
5.6 A new provision for Rel-11 only
5.7 Another new Rel-11 requirement
5.8 Something else peculiar to Rel-11
5.9 An afterthought
That is, the new provision takes the clause number 5.9 in each both Releases. |
f193e84844076b4f7262087f58142986 | 21.801 | 6 Drafting | |
f193e84844076b4f7262087f58142986 | 21.801 | 6.1 Preliminary informative elements | |
f193e84844076b4f7262087f58142986 | 21.801 | 6.1.1 Title page | The title page shall contain the title of the 3GPP TS or 3GPP TR.
The wording of the title shall be established by the TSG with the greatest care. While being as concise as possible, it shall indicate, without ambiguity, the subject matter of the 3GPP TS or 3GPP TR in such a way as to distinguish it from that of other 3GPP TSs or 3GPP TRs, without going into unnecessary detail. Any necessary additional particulars shall be given in the scope.
The title shall be composed of separate elements, each as short as possible, proceeding from the general to the particular. In general, not more than the following three elements shall be used:
a) an introductory element "3rd Generation Partnership Project; Technical Specification Group nn;" (where nn is the full name of theTSG which produced the TS/TR);
NOTE 1: If prime responsibility for a TS/TR moves from one TSG to another, subsequent versions of that TS/TR will bear the name of the new TSG.
b) a main element (obligatory) indicating the principal subject treated within that general field;
c) a complementary element (optional) indicating the particular aspect of the principal subject or giving details that distinguish the 3GPP TS or 3GPP TR from other 3GPP TSs or 3GPP TRs, or other parts of the same 3GPP TS or 3GPP TR.
d) in parentheses, "Release yyyy" where yyyy indicates the Release identifier of the Release (e.g. Releaseย 1999, Releaseย 4).
When modifying the Release text, editors shall take care not to modify the style of that text from the style preset in the skeleton document. The style is used to replicate the Release in the header of subsequent pages of the TS/TR.
See also annex D.
NOTE 2: The 3GPP Secretariat is responsible for the final preparation of the title page.
For multi-part deliverables, all the individual titles in a series of parts shall contain the same introductory element (if present) and main element, while the complementary element shall be different in each case in order to distinguish the parts from one another. The complementary element shall be preceded in each case by the designation "Partย โฆ:".
For endorsement of documents from other standards organizations, see annex J. |
f193e84844076b4f7262087f58142986 | 21.801 | 6.1.2 Table of contents | The table of contents shall be generated automatically and shall not be set manually. The title shall be "Contents". - Use the TT style for the title. - Use the field {TOC \o} for the table itself. NOTE: The 3GPP Support Team is responsible for the final layout of the table of contents. 6.1.2A (void) 6.1.3 Foreword The foreword shall appear in each 3GPP TS or 3GPP TR. It shall not contain requirements, figures or tables. It consists of a general part giving information on: - the designation and name of the TSG that prepared the 3GPP TS or 3GPP TR; - information regarding the approval of the 3GPP TS or 3GPP TR; and a specific part that shall give as many of the following as are appropriate: - an indication of any other organization that has contributed to the preparation of the 3GPP TS or 3GPP TR; - a statement that the 3GPP TS or 3GPP TR cancels and replaces other documents in whole or in part; - a statement of significant technical changes from the previous version of the 3GPP TS or 3GPP TR; - the relationship of the 3GPP TS or 3GPP TR to other 3GPP TSs or 3GPP TRs or other documents. For multi-part deliverables, the first part shall include in its foreword an explanation of the intended structure of the series. In the foreword of each part belonging to the series, a reference shall be made to the titles of all other parts, if they are known. 6.1.3A (void) 6.1.4 Introduction The introduction is an optional preliminary element used, if required, to give specific information or commentary about the technical content of the 3GPP TS or 3GPP TR, and about the reasons prompting its preparation. It shall not contain requirements. The introduction shall not be numbered unless there is a need to create numbered subdivisions. In this case, it shall be numbered 0 with subclauses being numbered 0.1, 0.2, etc. Any numbered figure, table or displayed formula shall be numbered normally beginning with 1 (see also clause 5.2.1A). 6.1.5 Scope This element shall be clause 1 of each 3GPP TS or 3GPP TR and define without ambiguity the subject of the 3GPP TS or 3GPP TR and the aspect(s) covered, thereby indicating the limits of applicability of the 3GPP TS or 3GPP TR or particular parts of it. It shall not contain requirements. The scope shall be succinct so that it can be used as a summary for bibliographic purposes. This element shall be worded as a series of statements of fact. Forms of expression such as the following shall be used: "The present document - specifies the functional requirements for โฆ" a method of โฆ" the characteristics of โฆ" - establishes a system for โฆ" general principles for โฆ" - gives guidelines for โฆ" - gives terms and definitions โฆ" Statements of applicability of the 3GPP TS or 3GPP TR shall be introduced by the following wording: "The present document is applicable to โฆ" 6.1.6 References References should be given to Standards and Recommendations issued by recognized standardization bodies. Referencing of documents other than Standards and Recommendations are allowed under the following conditions: - all referenced text shall be publicly available in the English language during the approval phases and for the expected lifetime of the 3GPP TS or 3GPP TR, via the originating body or via the 3GPP Support Team; - if public availability cannot be guaranteed over a period of time as stated above, the 3GPP Support Team will endeavour to secure the rights from the copyright holder (normally the originating body of the referenced text) to reproduce the text; in this case: - agreement permitting 3GPP or its Organizational Partners to take over the copying and distribution rights shall have been obtained, in which case it shall be made available to 3GPP or its Organizational Partners in an agreed electronic format; - all copyright and other IPR issues shall have been settled; - the 3GPP Support Team shall establish and maintain a list of the referenced documents and the relevant external bodies, for document tracking and cross-referencing purposes, and keep the necessary liaison with the originating body; - if agreement with the copyright holder along the above lines cannot be achieved, the TSG/WG responsible shall make appropriate changes to the document and remove the reference from the 3GPP TS or TR. The list of references shall be introduced by the wording given in the approved 3GPP TS / TR template. The list shall not include the following: - documents that are not publicly available; - documents which are not explicitly cited in the body of the deliverable (such documents may be listed in a bibliography (see clause 6.4.2)). For each entry in the normative references list, all information necessary to identify the referenced document shall be provided. This may include the issuing organization, the document number, and the title. - Use the EX style; enclose the numbers in square brackets and separate the numbering from the title with a tab (you may use sequence fields for automatically numbering references, see clause H.4: "Sequence numbering"). EXAMPLE 1: [1] 3GPP TS 21.299 (V1.1): "Title". In documents intended to be formally issued as publications of the Standards Development Organizations which comprise the Organizational Partners of 3GPP, references shall not be made to internal working documents of 3GPP which are not issued as such formal publications. Examples of documents which shall not be referenced are: - Contributions to meetings ("TDocs"); - Reports of meetings; - Internal Technical Reports, in particular, those of the following series: - 10.xx - 30.xxx - 50.xxx - xx.8xx - xx.7xx (for some series, especially if 8xx is not available) If the use in a TS or in a TR (other than those TRs in the list above) of text from such a document is unavoidable the text shall be reproduced in the TS or TR itself (possibly in an annex). Such text may need to be corrected to make it abide by the rules contained in the present TR. The foregoing restriction does not apply to TRs not intended to be formally published by the Organizational Partners. For further instructions on references, see clause 6.6.6. 6.1.7 Terms This is a mandatory element giving formal definitions of terms used in the 3GPP TS or 3GPP TR. The introductory wording given in the 3GPP TS / TR template shall be used. Rules for the drafting and presentation of terms and definitions are given in annex C, together with special rules for terminology standards, such as vocabularies, or nomenclatures. - Order the terms alphabetically, unless some logical grouping dictates otherwise. - The term shall be in bold, and shall start with a lower case letter (unless it is always rendered with a leading capital) followed by a colon, one space, and the definition. - Use the Normal style. EXAMPLE: requirement: a provision that conveys criteria to be fulfilled 6.1.8 Symbols This is a mandatory element listing the symbols used in the 3GPP TS or 3GPP TR. Unless there is a need to list symbols in a specific order to reflect technical criteria, symbols should be listed in alphabetical order in the following sequence: - upper case Latin letter followed by lower case Latin letter (A, a, B, b, etc.); - letters without indices preceding letters with indices, and with letter indices preceding numerical ones (B, b, C, Cm, C2, c, d, dext, dint, d1, etc.); - Greek letters following Latin letters (Z, z, ๏, ๏ก, ๏, ๏ข, โฆ ๏, ๏ฌ, etc.); - any other special symbols. See also clause 6.6.2. The entries in the "Symbols" clause shall not be numbered. - Use the EW style. EXAMPLE: fl lower reference frequency 6.1.9 Abbreviations This is a mandatory element listing the abbreviations used in the 3GPP TS or 3GPP TR. Unless there is a need to list symbols in a specific order to reflect technical criteria, all abbreviations should be listed in alphabetical order in the following sequence: - upper case Latin letter followed by lower case Latin letter (A, a, B, b, etc.); - letters without indices preceding letters with indices, and with letter indices preceding numerical ones (B, b, C, Cm, C2, c, d, dext, dint, d1, etc.); - Greek letters following Latin letters (Z, z, ๏, ๏ก, ๏, ๏ข, โฆ ๏, ๏ฌ, etc.); - any other special symbols. This list shall contain all technical abbreviations/acronyms and their corresponding full terms which are used within the 3GPP TS or 3GPP TR. See also clause 6.6.2. The entries in the "Abbreviations" clause shall not be numbered. - Use the EW style. - Separate the abbreviation/acronym from the full term with a tab. EXAMPLE: dB decibel 6.2 (void) 6.2.1 (void) 6.2.2 (void) 6.3 Technical normative elements 6.3.1 (void) 6.3.2 (void) 6.3.3 Requirements This element is only applicable to TSs. It shall contain the following: a) all characteristics relevant to the aspect(s) of the product(s), process(es) or service(s) covered by the 3GPP TS or 3GPP TR, either explicitly or by reference; b) the required limiting values of quantifiable characteristics. For test methods see clause 6.3.5. A clear distinction shall be made between requirements, statements and recommendations. Contractual requirements concerning claims, guarantees, covering of expenses, etc. shall not be included. In some product 3GPP TSs or 3GPP TRs, it may be necessary to specify that the product shall be accompanied by warning notices or by instructions to the user or installer, and to specify their nature. On the other hand, requirements concerning use or installation as such shall be included in a separate part or a separate 3GPP TS or 3GPP TR since they are not requirements applicable to the product itself. 3GPP TSs or 3GPP TRs listing characteristics for which suppliers are required to state values that are not specified by the 3GPP TS or 3GPP TR itself shall specify how such values are to be measured and stated. For endorsement of documents from other standards organizations, see annex J. 6.3.3a Technical analysis This element is option and may appear in both TSs and TRs. It shall not contain any normative requirements. It gives technical analysis of investigations, for example, of a feasibility study, and conclusions and recommendations. It may also contain guidance on the use or interpretation of TSs or external normative material without in itself being normative. In a TS, requirements and technical analysis clauses may be freely intermixed to provide a logical structure. The language (modal verbs) suffices to distinguish between normative and informative material. 6.3.4 Sampling This optional element specifies the conditions and methods of sampling, as well as the method for the preservation of the sample(s). This element may appear at the beginning of test methods. 6.3.5 Test methods This optional element gives all the instructions concerning the procedure for determining the values of characteristics, or for checking conformity to stated requirements, and for ensuring the reproducibility of the results. If appropriate, tests shall be identified to indicate whether they are type tests, routine tests, sampling tests and so on. Instructions relating to test methods may be subdivided in the following order (where appropriate): a) principle; b) apparatus; c) preparation and preservation of test samples and test pieces; d) procedure; e) test report. Test methods may be presented as separate clauses, or be incorporated in requirements, or be presented as annexes (see clause 6.3a) or as separate parts (see clause 5.2.1). A test method shall be prepared as a separate 3GPP TS if it is likely to be referred to in a number of other 3GPP TSs. The need for specification of test methods shall be evaluated on a case by case basis. A test specification enables verification that products designed to a standard conform to its requirements. When writing a 3GPP TS you should consider the need for an accompanying test specification. Every requirement of a 3GPP TS specifying a product (equipment, system or service) needs to be testable, and such requirements need to be clearly distinguishable from statements of fact or of supposition. EXAMPLE: Comparing the two sentences below: "On receiving a start call message, the terminal shall respond by sending an acknowledge message within a delay of t1." "On receiving a start call primitive, the layer 3 protocol of the terminal shall move to state call activated and shall start timer t2." It is clear that conformance to the first requirement can be verified by external stimulus and observation, whereas the second puts demands on a conceptual model which cannot be explicitly tested. Whilst requirements of the latter sort are useful - even essential - for describing operational details, the essential behavioural characteristics (normative provisions) are given by requirements of the type of the former, and only these are verifiable. 6.3.6 Classification and designation Void. 6.3.7 Marking, labelling and packaging Void. 6.3.8 (void) 6.3a Supplementary normative elements 6.3a.1 Normative annexes For reasons of convenience it may be decided to place some part of the normative text in an annex. Normative annexes contain provisions to which it is necessary to conform in order to be able to claim compliance with the 3GPP TS. Their status shall be indicated in the heading of the annex (see clause 5.2.6). Normative annexes shall not appear in 3GPP TRs. 6.4 Supplementary informative elements 6.4.1 Informative annexes For reasons of convenience it may be decided to place some part of the informative text in an annex. Informative annexes give additional information intended to assist the understanding or use of the 3GPP TS (or 3GPP TR) and shall not contain provisions to which it is necessary to conform in order to be able to claim compliance with the 3GPP TS. Their presence is optional and their status shall be indicated in the heading of the annex (see clause 5.2.6). All annexes in 3GPP TRs are "informative" since 3GPP TRs cannot contain normative provisions. Therefore, the word "informative" shall not appear in the title line of annexes in 3GPP TRs. 6.4.2 Bibliography The Bibliography identifies documents which are not explicitly cited in the body of the 3GPP TS or 3GPP TR. Format references as described in clause 6.2.2. 6.4.3 Index - Format the index in a section having two columns separated by 0,5 cm using the field {INDEX \e "๏ฎ" \c "2"}. 6.4.4 Change history A history box is provided by the 3GPP Support Team as the final element in a 3GPP TS or 3GPP TR and shows the major milestones in the life of a document. See also clause H.6. NOTE: The 3GPP Support Team is responsible for the final preparation of the history box. 6.5 Other informative elements 6.5.1 Notes and examples integrated in the text Notes and examples integrated in the text of a 3GPP TS or 3GPP TR shall only be used for giving additional information intended to assist the understanding or use of the 3GPP TS or 3GPP TR. They shall not contain provisions to which it is necessary to conform in order to be able to claim compliance with a 3GPP TS. Notes and examples should preferably be placed at the end of the clause, or after the paragraph to which they refer. A single note in a clause shall be preceded by "NOTE:", placed at the beginning of the first line of the text of the note. When several notes occur within the same element (e.g. subclause), they shall be designated "NOTE 1:", "NOTE 2:", "NOTE 3:", etc. (see also clause 5.2.1A). The word NOTE shall appear in upper case. - Use the NW or NO style. - Separate NOTE: from the text of the note with a tab. A single example in a clause shall be preceded by "EXAMPLE:", placed at the beginning of the first line of the text of the example. When several examples occur within the same element (e.g. clause), they shall be designated "EXAMPLE 1:", "EXAMPLE 2:", "EXAMPLE 3:", etc. (see also clause 5.2.1A). When there is a danger that it might not be clear where the example ends and the normal text continues, then the end of the example may be designated by "END of EXAMPLE". The word EXAMPLE shall appear in upper case. - Use the EX style. - Separate EXAMPLE: from the text of the example with a tab. EXAMPLE 1: NOTE 1: Note text formatted with the NW style will be formatted without a space after the paragraph. NOTE 2: Note text formatted with the NO style will be formatted with a space after the paragraph. END of EXAMPLE 1 6.5.2 Footnotes to the text Footnotes shall not be used in 3GPP TSs or 3GPP TRs. 6.6 Common rules and elements 6.6.1 Verbal forms for the expression of provisions A 3GPP TS does not in itself impose any obligation upon anyone to follow it. However, such an obligation may be imposed, for example, by legislation or by a contract. In order to be able to claim compliance with a 3GPP TS, the user needs to be able to identify the requirements that are obligatory. The user also needs to be able to distinguish these requirements from other provisions where there is a certain freedom of choice. Clear rules for the use of verbal forms (including modal auxiliaries) are therefore essential. Annex E gives, in the first column of each table, the verbal form that shall be used to express each kind of provision. The equivalent expressions given in the second column shall be used only in exceptional cases when the form given in the first column cannot be used for linguistic reasons. 6.6.2 Spelling and abbreviation of names of organizations, and style The spelling of the names of organizations, and their abbreviations, shall be as used by those organizations. To facilitate understanding by all readers, the style shall be as simple and concise as possible. This is particularly important for those readers whose first language is not English. The "Shorter Oxford English Dictionary" and the "Concise Oxford Dictionary" are suggested. Abbreviations shall be used with care, and their use shall be limited to those cases where it is not likely to cause confusion. An abbreviation shall be defined only if used subsequently in the 3GPP TS or 3GPP TR. The general rule is that abbreviations consisting of the initial letters of words be printed in lower-case letters (for example, "a.c." for "alternating current") and a full-stop be placed after each letter. Where, however, an abbreviation comprises capital letters, no full-stops are required. 6.6.2A Use of capital letters Unnecessary use of capital letters should be avoided. EXAMPLE: "user" is preferred to "User". 6.6.2B Pagination Unnecessary pagination, (i.e. use of hard page breaks) should be avoided. - Use Format | Paragraph | Text Flow | Keep Lines Together and Keep with Next attributes instead of "hard" page breaks. 6.6.3 Use of trade names A correct designation or description of a product shall be given rather than a trade name (brand name). Proprietary trade names (i.e. trade marks) for a particular product should as far as possible be avoided, even if they are in common use. If, exceptionally, trade names cannot be avoided, their nature shall be indicated, e.g. by the symbol ๏ for a registered trade mark (see example 1). EXAMPLE 1: Instead of "Teflon๏ข", write "polytetrafluoroethylene (PTFE)". If it is known that only one product is currently available that is suitable for the successful application of the standard, the trade name of the product may be given in the text of the standard but shall be associated with a note as shown in example 2. EXAMPLE 2: NOTE: "โฆ [trade name of product] โฆ is the trade name of a product supplied by โฆ [supplier] โฆ. This information is given for the convenience of users of the present document and does not constitute an endorsement by 3GPP of the product named. Equivalent products may be used if they can be shown to lead to the same results." If it is considered to be essential to give an example (or examples) of commercially available products suitable for successful application of the standard because the product characteristics are difficult to describe in detail, trade names may be given in a note as shown in example 3. EXAMPLE 3: NOTE: " โฆ [trade name(s) of product(s)] โฆ is (are) an example(s) of a suitable product(s) available commercially. This information is given for the convenience of users of the present document and does not constitute an endorsement by 3GPP of this (these) product(s)." 6.6.4 Figures 6.6.4.1 Usage Figures should be used wherever appropriate to present information in an easily comprehensible form. 6.6.4.2 Format - Use the TH style on the paragraph which contains the figure itself. - Maximum size for figures is 17 cm by 22 cm. Where SDL, Program Code, ICS, or TTCN is included in figures it shall be prepared in accordance with annex I. 6.6.4.3 Numbering Figures may be numbered sequentially throughout the document without regard to the clause numbering, e.g. first figure is figure 1 and the twentieth figure (in, say clause 7) is figure 20. Figures may also be numbered taking account of clause numbering. EXAMPLE 1: First figure in clause 7 is figure 7-1, fifth figure in clause 7 is figure 7-5. EXAMPLE 2: First figure in clause 7.3.2 is figure 7.3.2-1, fifth figure in clause 7.3.2 is figure 7.3.2-5. One level of subdivision only is permitted (e.g. figure 1 may be subdivided as 1 a), 1 b), 1 c), etc.). See also clause 5.2.1A. For the numbering of figures in annexes, seeclause 5.2.6. - You may use sequence fields for automatically numbering figures. See clause H.4: "Sequence numbering". 6.6.4.4 Layout of title The figure title shall be below the figure. An explicit figure name is optional. See the following examples: EXAMPLE 1: Figure 1: Details of apparatus EXAMPLE 2: Figure 1 - Use the TF style. - If applicable, the figure number is followed by a colon, a space and the figure name 6.6.4.5 Choice of letter symbols, style of lettering, and labelling - Use Arial font. - Use a font size of at least 8 points (final size), to ensure legibility. 6.6.4.6 Technical drawings Void. 6.6.4.7 Diagrams Void. 6.6.4.8 Notes to figures Notes to figures shall be treated independently from notes integrated in the text (see clause 6.5.1). They shall be located above the title of the relevant figure. A single note in a figure shall be preceded by "NOTE:". When several notes occur in the same figure, they shall be designated "NOTE 1:", "NOTE 2:", "NOTE 3:", etc. (see also clause 5.2.1A). A separate numbering sequence shall be used for each figure. Notes to figures may contain requirements. - Write notes to a figure using the word processor rather than embedding them in the figure itself. - Use the NF style. - Separate NOTE: from the text of the note with a tab. 6.6.4.9 Footnotes to figures Footnotes shall not be used in 3GPP TSs or 3GPP TRs. 6.6.5 Tables 6.6.5.1 Usage Tables should be used wherever appropriate to present information in an easily comprehensible form. A table within a table is not permitted. Subdivision of a table into subsidiary tables is not permitted. - Centre tables horizontally. - The "space between columns" is 0,1 cm. - Maximum width for tables in portrait orientation: 17 cm and for landscape orientation: 22 cm. - Set table columns widths in centimetres (not inches). - Use borders to separate the rows and columns of tables, as appropriate; the precise format will depend on the structure of each table, but be consistent throughout a deliverable (or series of related deliverables). Borders should be ยพ pt single line. - Each table shall be followed by an empty "Normal" style paragraph ("Enter" key). 6.6.5.2 Numbering Tables may be numbered sequentially throughout the document without regard to the clause numbering, e.g. first table is table 1 and the twentieth table (in, say clause 7) is table 20. Tables may also be numbered taking account of clause numbering. EXAMPLE 1: First table in clause 7 is table 7-1, fifth table in clause 7 is table 7-5. EXAMPLE 2: First table in clause 7.3.2 is table 7.3.2-1, fifth table in clause 7.3.2 is table 7.3.2-5. See also clause 5.2.1A. For the numbering of tables in annexes, see clause 5.2.6. - You may use sequence fields for automatically numbering tables. See clause H.4: "Sequence numbering". 6.6.5.3 Layout of title The title shall be above the table. An explicit table name is optional. See the following examples: EXAMPLE 1: Table 1: Electrical properties EXAMPLE 2: Table 1 - Use the TH style. - If applicable, the table number is followed by a colon, a space and the table name 6.6.5.4 Headings The first word in the heading of each column shall begin with a capital letter. The units used in a given column shall generally be indicated under the column heading. EXAMPLE: Type Linear density (kg/m) Inside diameter (mm) Outside diameter (mm) - Use of the table headings tool (Table, Heading row repeat) is encouraged for tables that require more than one page. - Use the following styles: - Table Headings TAH - Text Left justified TAL - Text Centred TAC - Text Right justified TAR 6.6.5.5 Continuation of tables The column headings shall be repeated on all pages after the first (see clause 6.6.5.4). 6.6.5.6 Notes to tables Notes to tables shall be treated independently from notes integrated in the text (see clause 6.5.1). They shall be located within the frame of the relevant table. A single note in a table shall be preceded by "NOTE:". When several notes occur in the same table, they shall be designated "NOTE 1:", "NOTE 2:", "NOTE 3:", etc. (see also clause 5.2.1A). A separate numbering sequence shall be used for each table. Notes to tables may contain requirements. - Use the TAN style. - Include notes to a table within its borders in one cell, at the bottom. - Merge all cells to one, as in the following example: EXAMPLE: Column 1 cell Column 2 cell Column 3 cell Column 4 cell NOTE: This cell is a merged cell. 6.6.5.7 Footnotes to tables Footnotes shall not be used in 3GPP TSs or 3GPP TRs. 6.6.6 References 6.6.6.1 General As a general rule, references to particular pieces of text shall be used instead of repetition of the original source material, since such repetition involves the risk of error or inconsistency and increases the length of the document. However, if it is considered necessary to repeat such material, its source shall be identified precisely. If it is necessary to reproduce text from a work other than a 3GPP TS or TR, appropriate copyright permission shall be obtained. References shall be made in the forms indicated in clauses 6.6.6.2 to 6.6.6.5 and shall not be made to page numbers. 6.6.6.2 References to the 3GPP TS or 3GPP TR as a whole in its own text The form "the present document โฆ" shall be used. 6.6.6.3 References to elements of text Use, for example, the following forms: - "in accordance with clause 3"; - "according to clause 3.1"; - "as specified in clause 3.1 b)"; - "details as given in clause 3.1.1"; - "see annex B"; - "the requirements given in clause B.2"; - "see the note in table 2"; - ''see example 2 in clause 6.6.3"; - "see note 3 in clause 6.6.1". It is required to use the terms clause and annex where applicable. If there is a need to refer to an unnumbered list item in another standard, the following formulation shall be used: "as specified in TS 21.299 [n] in clause 3.1, second list item". Lower case letters are recommended (e.g. clause 1, annex A), however capital letters are also acceptable (e.g. Clause 1, Annex A). Usage should be consistent throughout the document. 6.6.6.4 References to tables and figures Every table and figure included in the 3GPP TS or 3GPP TR shall be referred to in the text. Use, for example, the following forms: - "given in table 2"; - "(see table B.2)"; - "shown in figure A.6"; - "(see figure 3)". Lower case letters are recommended (e.g. table 1, figure 2), however capital letters are also acceptable (e.g. Table 1, Figure 2). Usage should be consistent throughout the document. 6.6.6.5 References to other documents 6.6.6.5.1 General References to other documents may be specific or non-specific. All references, specific and non-specific, shall be given in the "References" clause (see clause 6.1.6). 6.6.6.5.2 Specific references Except as provided for in clause 6.6.6.5.3, references shall be specific (identified by date of publication, edition number, version number, etc.). In the body of the text, use the following form: - " โฆ in accordance with TS 21.299 [n] โฆ ". For specific references, it is permissible to refer to a specific clause, figure or table of the referenced document. However, great care needs to be taken, especially when referencing documents still under development, and such referencing of specific clauses, figures or tables is to be avoided if there is a reasonable chance that the structure of the referenced document may change in time. 6.6.6.5.3 Non-specific references Non-specific references may be made only if it is accepted that it will be possible to use future changes of the document referred to for the purposes of the referring 3GPP TS or 3GPP TR. In the case of references to 3GPP TSs and TRs, unless otherwise indicated, a non-specific reference refers to the TS or TR in the same Release as that of the referring TS or TR. It is implicitly to the latest version of the referenced TS or TR in the Release in question. For non-specific references, it is not permissible to cite particular clauses, figures or tables, since it cannot be guaranteed that the numbering will be unchanged in later versions of the referenced document. In the body of the text, use the forms as given in clause 6.6.6.5.2. 6.6.6.6 Numbering References in clause 2 shall be numbered sequentially. If a reference is removed when a specification is under change control, the entry in clause 2 shall be replaced by a [void] entry, using the same principle as for deletion of clauses. - You may use sequence fields for automatically numbering references. See clause H.4: "Sequence numbering". 6.6.7 Representation of numbers and numerical values For decimal and thousands separator characters, one of the following options shall be employed: Option 1: The decimal sign shall be a comma. The thousands separator shall be a space. Option 2: The decimal sign shall be a full-stop (period). The thousands separator shall be a comma. The chosen option shall be used throughout the TS or TR. It is not permissible to mix the two systems in a single document. If there is any ambiguity as to which system is in use, the characters in question shall be defined as symbols in clause 3.3 of the TS or TR. For example, unless there are other instances nearby in the document, the string 234,557 is ambiguous (is it two hundred and thirty four point five five seven or two hundred and thirty four thousand five hundred and fifty seven?). The present document uses Option 1. NOTE: In the text below, ยฐ represents the non-breaking space character. If a value less than 1 is written in decimal form, the decimal sign shall be preceded by a zero. EXAMPLE 1: 0,001 (not ,001) Each group of three digits reading to the left or to the right of a decimal sign shall be separated by a space from preceding digits or following digits respectively, except for four-digit numbers designating years. EXAMPLE 2: 23ยฐ456 / 2ยฐ345 / 2,345 / 2,345ยฐ6 / 2,345ยฐ67 but the year 1997 For clarity, the symbol ๏ด or a lower case x (rather than a point or any other symbol) shall be used to indicate multiplication of numbers and numerical values. EXAMPLE 3: write 1,8ยฐ๏ดยฐ10-3 (not 1,8 * 10-3 or 1,8 ๏ 10-3 or 1,8 . 10-3) To express numbers of items (as opposed to numerical values of physical quantities), the numerals one to nine shall be spelt out in full. EXAMPLE 4: "Carry out the test on five tubes, each 5 m long." EXAMPLE 5: "Select a further 15 tubes for the pressure test." Preserve document identities as in the original titles. EXAMPLE 6: ISO/IECยฐ10531-1 (not ISO/IEC 10ยฐ531-1). EXAMPLE 7: 3GPPยฐTRยฐ21.801. Put a non-breaking space between a number and its unit - including the percent sign (%) - even if the unit is not abbreviated: EXAMPLE 8: 2ยบpages 4ยบseconds 15ยบ% Write a number preceded by an unary operator (sign) without an intervening space: EXAMPLE 9: โฆ a level of -3ยฐdB โฆ Put a non-breaking space both before and after binary operators (๏ซ, ๏ญ, ๏ด, etc.): EXAMPLE 10: aยฐ+ยฐbยฐ=ยฐc - Use non-breaking spaces (Ctrl + Shift + space) for the thousand separator, before and after binary operators and preceding units. - Use a non-breaking hyphen (Ctrl + Shift + -) for the minus sign. 6.6.8 Quantities, units, symbols and signs The units in which any values are expressed shall be indicated. 6.6.9 Mathematical formulae 6.6.9.1 Types of formulae Clause 6.6.9 covers two cases of mathematical formulae. The first case is equation, defined by the Oxford English dictionary as "a statement that asserts the equality of two expressions. In mathematics, it typically takes the form of two expressions set equal to each other". Equations between quantities are preferred to equations between numerical values. Equations shall be expressed in mathematically correct form, the variables being represented by letter symbols the meanings of which are explained in connection with the equations, unless they appear in a "Symbols and abbreviations" clause. Descriptive terms, acronyms or names of quantities shall not be arranged in the form of an equation. EXAMPLE 1 (equation): where: xj are samples of time errors data; N is the total number of samples; ๏ด is the time error sampling interval; n is the number of sampling intervals, with n = 1,2,...,integer part (N/3). The second case is symbol, defined by the Oxford English dictionary as "a sign, number, letter, etc., that has a fixed meaning". Note that symbol can be a component of an equation (for example, simply referring to in EXAMPLE 1 above), or it can be used in a sentence or provisions (see EXAMPLE 2 for the latter). EXAMPLE 2 (symbol, the first line as defined in symbols clause and the second line as used in provisions): Nnef NEF Northbound interface between NEF and AF NEF(s) can expose the capability of the 5G network to AF(s) via Nnef interface. 6.6.9.2 Presentation - Use the EQ style for equations. For symbols, use appropriate styles per context (e.g., use EW for Symbols clause, use Normal for indication within normal text provisions). - Insert one tab before the equation to center it. It is recommended to use Microsoft Word's built-in equation functionality (OMML) or basic text functionality. OMML is recommended for equations and symbols that are intended to be part of equation(s), as shown in EXAMPLE 1 of clause 6.6.9.1. Basic text functionality is recommended for symbols that are not intended to be part of equation(s), as shown in EXAMPLE 2 of clause 6.6.9.1. NOTE: For the equations and symbols defined in Release 19 or before, it is encouraged, but not mandatory, to replace them using OMML. 6.6.9.3 Numbering If it is necessary to number some or all of the equations in a 3GPP TS or 3GPP TR in order to facilitate cross-reference, arabic numbers in parentheses shall be used, beginning with 1: x2 + y2 < z2 (1) Equations may be numbered sequentially throughout the document without regard to the clause numbering, e.g. first equation is equation 1 and the twentieth equation (in, say clause 7) is equation 20. Equations may also be numbered taking account of clause numbering. EXAMPLE 1: First equation in clause 7 is equation 7-1, fifth equation in clause 7 is equation 7-5. EXAMPLE 2: First equation in clause 7.3.2 is equation 7.3.2-1, fifth equation in clause 7.3.2 is equation 7.3.2-5. See also clause 5.2.1A. For the numbering of equations in annexes see clause 5.2.6. - You may use sequence fields for automatically numbering tables. See clause H.4: "Sequence numbering". - Insert a tab between the equation and the number to right-align the number. 6.6.10 Indication of dimensions and tolerances Dimensions and tolerances shall be indicated in an unambiguous manner. EXAMPLE 1: 80 mmยฐ๏ดยฐ25 mmยฐ๏ดยฐ50 mm (not 80 ๏ด 25 ๏ด 50 mm) EXAMPLE 2: 80 ยตFยฐ๏ฑยฐ2 ยตF or (80 ๏ฑ 2) ยตF EXAMPLE 3: 16 kbit/s to 64 kbit/s (not 16 to 64 kbit/s) EXAMPLE 4: 0 ยฐC to 10 ยฐC (not 0 to 10 ยฐC) In order to avoid misunderstanding, tolerances on percentages shall be expressed in a mathematically correct form. EXAMPLE 5: Write "from 63ยฐ% to 67ยฐ%" to express a range. EXAMPLE 6: Write "(65ยฐ๏ฑยฐ2)ยฐ%" to express a centre value with tolerance. The form "65ยฐ๏ฑยฐ2ยฐ%" shall not be used. 7 Presentation of computer language and other code Portions of code (e.g. ASN.1, GDMO, C, C++, etc.) can be included in a 3GPP TS or 3GPP TR but should be clearly marked as such. - Use the PL style. Annex A (informative): (void) Annex B (informative): (void) Annex C (normative): Drafting and presentation of terms and definitions C.1 General principles C.1.1 Rules for development Void. C.1.2 Types of standard Terminology may take the form of an independent 3GPP terminology deliverable (a vocabulary or a nomenclature) or be included in a "Definitions" clause in a 3GPP TS or 3GPP TR that also deals with other aspects. C.1.3 Choice of concepts to be defined Any term which is not self-explanatory or commonly known and which can be differently interpreted in different contexts shall be clarified by defining the relevant concept. Common dictionary or current technical terms shall be included only if they are used with a specific meaning in the relevant context. Trade names (brand names) and archaic and colloquial terms shall be avoided. Deprecated terms may be included after the preferred term but their nature shall be indicated (by adding the word deprecated, see clause C.3.3). In an independent terminology deliverable, the concepts defined shall be restricted to the field corresponding to the scope of 3GPP. In other 3GPP TSs or 3GPP TRs, only such concepts shall be defined as are used in those 3GPP TSs or 3GPP TRs, apart from any additional concepts and their terms that may be deemed necessary for the understanding of these definitions. C.1.4 Avoidance of duplications and contradictions Before a term and a definition are established for a concept, it should be ascertained that no other term and definition for that concept exist in another 3GPP TS or 3GPP TR. If the concept is used in several 3GPP TSs or 3GPP TRs, it should be defined in the most general of those standards, or in an independent terminology deliverable. The other 3GPP TSs or 3GPP TRs should then refer to this deliverable, without repeating the definition of the concept. When the repetition of a definition is necessary, an informative reference shall be made to the document (3GPP TS or 3GPP TR or other) from which it is reproduced (see clause 6.6.6.5). If a term and a definition for a concept are established in one 3GPP TS or 3GPP TR, the introduction in another 3GPP TS or 3GPP TR of a different term (synonym) for the defined concept is strongly deprecated. C.1.5 Drafting of definitions - A definition shall not take the form of, or contain, a requirement. - The form of a definition shall be such that it can replace the term in context. Additional information shall be given only in the form of examples or notes (see clause C.3.9). - A definition given without an indication of its applicability may be taken as representing the general meaning of the term. Special meanings in particular contexts shall be indicated by designating the subject field (see clause C.3.6). C.2 Independent terminology deliverables C.2.1 Arrangement An independent terminology deliverable containing terms and definitions should be preferably classified according to the hierarchy of the concepts. The terms and definitions of general concepts shall precede those of less general concepts. If a mixed system of concepts is used in which several groupings (according to different criteria) appear, each grouping shall be kept separate and the relevant criteria shall be indicated. The grouping of terms shall be evident from their numbering. C.2.2 Languages other than official languages Void. C.3 Presentation C.3.1 Rules Void. C.3.2 Layout The preferred term (set in bold type) shall be placed on a new line, (after its reference number, if used), starting with a lower-case letter except for any capital letters required by the normal written form in running text. The definition shall follow, after a colon and a space. EXAMPLE: delamination: separation of two adjacent plies resulting from a lack of adhesion C.3.3 Synonyms Admitted terms (set in normal type in the printed publication) shall each be placed on a new line, after the preferred term. EXAMPLE 1: serializer; parallel-serial converter dynamicizer: functional unit that converts a set of simultaneous signals into a corresponding time sequence of signals Symbols shall be given following any admitted term(s). Information regarding the units applicable to a quantity shall be given in a note. EXAMPLE 2: resistance; R: electric difference divided by current when there is no electromotive force in the conductor NOTE: Resistance is expressed in ohms. Deprecated, obsolete and superseded terms (in normal type) shall each be placed after the recommended term, after any symbols, and shall be followed by an indication of their status, in parentheses. EXAMPLE 3: radix; base (deprecated): positive integer by which the weight of any digit place is multiplied to obtain the weight of the digit place with the next higher weight C.3.4 Grammatical form of terms Terms shall in general be presented in their basic grammatical form, i.e. nouns in the singular, verbs in the infinitive. C.3.5 Symbol for missing terms Void. C.3.6 Multiple meanings If a term is used to represent several concepts, the subject field to which each concept belongs shall be indicated between angle brackets, before the definition. EXAMPLE: die, noun: [extrusion] metal block with a shaped orifice through which plastic material is extruded die, noun: [moulding] assembly of parts enclosing the cavity from which the moulding takes its form die, noun: [punching] tool to punch sheet or film material C.3.7 Codes for countries and for languages Void. C.3.8 Parentheses and brackets Parentheses and square brackets shall be used only if they constitute part of the normal written form of the term. They shall not be used to show alternative terms. EXAMPLE: bis(dimethylthiocarbamyl) disulfide C.3.9 Examples and notes Examples of term usage, and notes concerning entries, shall be presented as shown below. radix; base (deprecated): [radix numeration system] positive integer by which the weight of any digital place is multiplied to obtain the weight of the digit place with the next higher weight EXAMPLE: In the decimal numeration system the radix of each digit place is 10. NOTE: The term "base" is deprecated in this sense because of its mathematical use. Annex D (normative): Drafting of the title of a 3GPP TS or 3GPP TR D.1 Elements of the title D.1.1 The introductory element See clause 6.1.1. D.1.2 The main element The main element shall always be included. If a complementary element is included, the main element shall be terminated with a semi-colon. If no complementary element is included, there shall be no terminating semicolon. D.1.3 The complementary element The complementary element is necessary if the 3GPP TS or 3GPP TR covers only one or a few aspects of the subject indicated in the main element. Experience has shown that the titles of most deliverables benefit from the precision supplied in the complementary element. In the case of a 3GPP TS or 3GPP TR published as a series of parts, the complementary element shall serve to distinguish and identify the parts (the introductory element and the main element remaining the same for each part). The complementary element shall be omitted if the 3GPP TS or 3GPP TR both: - covers all essential aspects of the subject indicated in the main element; and - is (and is intended to remain) the only 3GPP TS or 3GPP TR relating to this subject. The complementary element may be sudivided if necessary, with each sub-element adding further refinement to the topic covered. The first word of each sub-element shall start with a capital letter. Each sub-element other than the last shall be terminated with a semicolon. D.2 Avoidance of unintentional limitation of the scope The title shall not contain details that might imply a limitation of the scope of the 3GPP TS or 3GPP TR. However, if the 3GPP TS or 3GPP TR pertains to a specific type of product, this fact shall be reflected in the title. D.3 Wording The Work Item Description form which proposes the creation of a new TS or TR shall give a preliminary title for the TS or TR. This "working" title may be modified, within reason, during the drafting of the TS/TR. In establishing the title of the TS/TR, the following shall be taken into account: 1. The title should be as succinct as possible yet shall clearly state the main aspects covered in the document. 2. In drafting the title, the author should not make the text either too vague or so restrictive as to artificially limit the potential broadening of the scope of the TS/TR during its lifetime. 3. Any abbreviations used in the title shall be expanded in full, using initial capital letters as appropriate, and followed by the abbreviation in parentheses. This rule may be waived for commonly understood abbreviations if it would result in unnecessarily complex or unwieldy text (see example 2 below) EXAMPLE 1: Management Object (MO) EXAMPLE 2: IP Multimedia core network Subsystem (IMS) This is preferable to: Internet Protocol (IP) Multimedia core network Subsystem (IMS) 4. Other than capitalization mentioned above, no other letters of the title shall be capitalized. 5. The title shall not include redundant words such as "Technical Specification" or "Technical Report". D.4 Stability In preparing the TS/TR for presentation to the TSG for approval (bringing under change control), the responsible Project Manager should, in consultation with the Rapporteur and WG Chair, verify that the title conforms to the conventions given in the present annex, and modify it accordingly. If, for reasons of expediency, this step is omitted, it shall be carried out by the Specifications Manager prior to making the change-controlled version of the TS/TR available on the 3GPP server. Once under change control, the text of the title of a TS/TR shall not be changed, even by Change Request, other than for the correction of typographical errors. If it is wished to change the scope of a TS/TR to the extent that a change of title would be necessary, this is best achieved by the creation of a completely new TS/TR instead. NOTE: If it were allowed to change the title of a TS or TR when under change control, it would be necessary to identify all 3GPP TSs and TRs which reference the TS/TR in question, and raise Change Requests to all of them to change the title in that reference. Furthermore, if the title were to change, different versions of the TS/TR might appear in different places in any alphabetic index or catalogue of 3GPP documents, with predictable confusion for users. Annex E (normative): Verbal forms for the expression of provisions NOTE: Only singular forms are shown. The verbal forms shown in table E.1 shall be used to indicate requirements strictly to be followed in order to conform to the standard and from which no deviation is permitted. Table E.1: Requirement Verbal form Equivalent expressions for use in exceptional cases (see clause 6.6.1) shall is to is required to it is required that has to only ... is permitted it is necessary shall not is not allowed [permitted] [acceptable] [permissible] is required to be not is required that ... be not is not to be Do not use "must" as an alternative for "shall". (This will avoid any confusion between the requirements of a standard and external statutory obligations). Do not use "may not" instead "shall not" to express a prohibition. To express a direct instruction, for example referring to steps to be taken in a test method, use the imperative mood (e.g. "switch on the recorder"). The verbal forms shown in table E.2 shall be used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. Table E.2: Recommendation Verbal form Equivalent expressions for use in exceptional cases (see clause 6.6.1) should it is recommended that ought to should not it is not recommended that ought not to The verbal forms shown in table E.3 are used to indicate a course of action permissible within the limits of the 3GPP TS or 3GPP TR. Table E.3: Permission Verbal form Equivalent expressions for use in exceptional cases (see clause 6.6.1) may is permitted is allowed is permissible need not it is not required that no ... is required Do not use "possible" or "impossible" in this context. Do not use "can" instead of "may" in this context. Do not use "may" or "may not" to indicate a possibility or lack of possibility โ see Table E.4 below. NOTE: "May" signifies permission expressed by the standard, whereas "can" refers to the ability of a user of the standard or to a possibility open to him. The verbal forms shown in table E.4 are used for statements of possibility and capability, whether material, physical or causal. Table E.4: Possibility and capability Verbal form Equivalent expressions for use in exceptional cases (see clause 6.6.1) can be able to there is a possibility of it is possible to cannot be unable to there is no possibility of it is not possible to Do not use "may" instead of "can" in this context. Do not use "may not" in this context. NOTE: "May" signifies permission expressed by the standard, whereas "can" refers to the ability of a user of the standard or to a possibility open to him. If there is uncertainty about whether an event will or will not happen, in particular where the normally expected behaviour will sometimes be impossible, a formulation such as "cannot always" should be used. The verbal forms shown in table E.5 shall be used to indicate behaviour of equipment or sub-systems outside the scope of the document in which they appear. For example, in a standard specifying the requirements of terminal equipment, these forms shall be used to describe the expected behaviour of the network or network simulator to which the terminal is connected. Table E.5: Inevitability Verbal form Equivalent expressions will will not Distinguish from "shall" / "shall not". Use to express behaviour of equipment or systems outside the scope of the document being drafted, where description of such behaviour is essential to the correct understanding of the requirements pertaining to equipment within the scope of the current document. EXAMPLE: Extract from standard specifying behaviour of terminal equipment: "โฆ On expiry of timer T3, the terminal shall send a TIMEOUT message to the network and start timer T4. The network will respond with a TIMOUT-ACKNOWLEDGE message. On receipt of a TIMEOUT-ACKNOWLEDGE message, the terminal shall stop timer T4 โฆ"; thus is distinguished the strong future ("the terminal shall") used for requirements and the normal future ("the network will") used to indicate expected events. The verbal forms shown in table E.6 shall be used to indicate statements of fact. Table E.6: Fact Verbal form Equivalent expressions is Any verb in the indicative mood, present tense. is not Distinguish from "shall" / "shall not". Do not use present indicative of verbs for expressing requirements. Annex F (informative): Checklist concerning quantities and units to be used in 3GPP TSs or 3GPP TRs Void. Annex G (informative): Example layout of a typescript Void. Annex H (informative): 3GPP styles and various information H.1 The 3GPP styles Use table H.1 when determining which style to use for various elements of the deliverable. Table H.1 Use this style For this type of element Heading 1 Clause (๏ฎ if numbered) Heading n Clause level n In exceptional cases, for level 6 or beyond, use Heading 5 if required in contents list or H6 if not to appear. ๏ฎ Heading 8 Annex title for TS Heading 9 Annex title for TR Normal Standard paragraph, Definition EX Reference, Example ๏ฎ EW Symbol, Abbreviation, Example continuation in text ๏ฎ Bn List element level n ๏ฎ FP Free paragraph (left justified) NO Note integrated in the text ๏ฎ NW Note continuation in text ๏ฎ NF Note in figure ๏ฎ TAN Note in table ๏ฎ TH Table title, Figures TAH Heading within table TAC Centred text within table TAL Left justified text within table TAR Right justified text within table TF Figure title TT Contents list title PL Programming language EQ Equation Header Header (portrait and landscape pages) ๏ฎ use "tab" between "item/number" and "text". EXAMPLE: The "tab" is preceding this example text. Other styles exist in the template, but are for use by the Support Team only. H.2 Page numbering, page headers and footers The skeleton document supplies fields for automatic page numbering and the identification of the deliverable in the page header. Do not add anything to or delete anything from the headers. - Use the HEADER style on all page headers (sections) except for the title page (section) H.3 Configuration of the Windows environment Set your Windows environment to use the English (International) conventions (via Control Panel, International). - Use centimetres as the preferred unit of measurement. - Do not select "Change 'Straight Quotes' to 'Smart Quotes'" in the AutoCorrect options. - Set Default Tab Stops to 0,5 cm. - The remaining configurable elements of Windows and of Word are at your discretion. H.4 Sequence numbering During the drafting of a TS or TR, you may use sequence numbering (Insert Field Seq) for tables, figures, equations, references, etc. Use the sequence identifiers shown in the following table. Table H.2: Sequence numberings Sequence Bookmark name Description seq bib bib_xx for bibliography entries seq equ equ_xx for equations (note 1) seq fig fig_xx for figures (note 1) seq ref ref_xx for references seq tab tab_xx for tables (note 1) NOTE 1: Reset the sequence numbering to one for the first item of each clause of a 3GPP TS or 3GPP TR by using the switch \r1 (e.g. { seq fig \r1 }).. NOTE 2: "xx" represents the identifier for the particular object concerned, e.g. fig_ProcessControl. Do not use bookmarks of the form "fig_fig1". You can use underscores as separators in sequence identifiers if necessary. Thus the title of a table will read: Table { seq tab }: Table title where the italic part represents the sequence field code. Bookmark each entry in a sequence (select it and use Edit Bookmark Add), using a bookmark name of the form shown in table H2. You can then refer to the table, figure, reference, etc. from the text by inserting a sequence field citing the same sequence identifier and the particular bookmark required. For example, table 1 has been bookmarked "tab_Seq_Num". Thus a reference to this table from the text reads: โฆ see table { seq tab tab_Seq_Num } โฆ where the italic part represents the sequence field code. You can force Word to recalculate and refresh the display of sequence numbers and their references by selecting the text and pressing F9. Do not use Word's cross-referencing tool (Insert, Cross-reference), since it implies the use of automatic heading or caption numbering. When drafting is complete and the TS or TR is ready to be presented to the TSG for placing under change control, hard code all automatic number sequences (CtrlโShiftโF9) that might have been used. Thereafter, manual numbering shall be used. This will avoid invalidating references from external documents to particular clauses / tables / etc. in the document under consideration (see clause 5.2.1A). You may use automatic clause numbering during the drafting phase of a TS or TR, but automatic clause numbering shall be disabled for a TS or TR under change control. H.5 Supported file formats Software tools to be used for document development within 3GPP are detailed in table H.3 Table H.3: Permitted software tools Type Tool(s) Comments Text Microsoft Word For .doc format, file compatibility with Word 2000 shall be retained for 3GPP TSs and TRs. For .docx format, file compatibility with Word 2007 shall be retained for 3GPP TSs and TRs. Word's built-in equation functionality OMML (Office Math Markup Language). Word's Equation 3.0 or Microsoft MathType are permitted for contents defined in Release 19 or before. Used for editing equations/symbols. Graphics Micrografx Designer version 3.x or 6.0 or 7.0 (preferred) Now part of CorelDraw, but older versions can be found for download. Retained for legacy documents. Not to be used for new graphics. Microsoft Visio For general graphics; the rapporteur shall supply the source file. File compatibility with version Professional 2003 or 2007 shall be maintained. Microsoft Word built-in drawing tools Final diagrams shall be visible in "normal" view (Word 2003 and earlier) or "draft" view (Word 2007 and later). For Unified Modeling Language (UML) graphics: Eclipse Papyrus (http://www.eclipse.org/papyrus/) Many earlier UML diagrams have been supplied as uneditable JPGs. For ease of maintenance, rapporteurs should provide editable source files for new UML diagrams, and authors of CRs are encouraged to recast UML diagrams originally supplied as JPGs to Papyrus in order to ease future maintenance. SDL, MSC IBM Telelogic Tau (NOTE 1 and NOTE 2) Msc-generator (NOTE 3) SDL diagrams and Message Sequence Charts can be copy-and-pasted into Word. Rapporteurs shall supply the source files. For SDLs, Microsoft Visio (see above) may be used. NOTE 1: Rapporteurs should contact their Support Team officer for access to this tool. NOTE 2: Retained for legacy documents. Not to be used for new documents. NOTE 3: Available from https://sourceforge.net/projects/msc-generator User manual at http://msc-generator.sourceforge.net/help/6.3/msc-gen.pdf TTCN-2 Any TTCN-2 tool that is compliant with ISO/IEC 9646 [4] Rapporteurs may contact their Support Team officer for access to a tool. TTCN-3 Any TTCN-3 tool that is compliant with ETSI ES 201 873 [5] Rapporteurs may contact their Support Team officer for access to a tool. Databases Microsoft Access Such databases are used principally by the Support Team for management and tracking purposes. File compatibility with Access 2000 or 2007 shall be maintained. General Tools Microsoft Office software suite (Excel, Powerpoint, etc.) File compatibility with Office version 2000 or 2007 shall be maintained if such documents form part of TSs or TRs. The file formats stipulated in table H.3 relating to Microsoftยฉ Office refer strictly to the file format. It is not intended to mandate that a particular version of MS Office or MS Office compatible software be used: any word processor which can save files in the above format is acceptable. Rapporteurs shall retain the source files of graphics where these exist, and they shall be retained within the zip file of the Spec for future maintenance of the document. H.6 Quick tips to working with your document When working with your 3GPP TS or 3GPP TR remember ... ... you shall do this... - use bold to emphasize text; - use italic for citations, linguistic expressions or when a word/text/expression is extracted from a specific context; - use non-breaking spaces (ยฐ) or hyphens (โ) in order to avoid unexpected wrap around between two words and/or numbers (e.g. 50ยฐcm, 1ยฐ000, clauseยฐ6, annexยฐA, tableยฐ1, figureยฐ1, TRยฐ21ยฐ801โ1, etc.). These characters appear as normal spaces ( ) or hyphens (-) when printed out; - use the default tab stops 0,5 cm; - use "straight" quotation marks (". . .") not "curly" or "smart" (". . .") ones. If a second set of quotations is needed (e.g. GDMO, ASN.1, etc.), single quotes ('. . .') may be used. โฆ but you shall not do this โฆ - alter existing styles or formats pre-set in the 3GPP template; - add new styles to the 3GPP template; - delete 3GPP styles; - use a font other than the one pre-set in the 3GPP styles; - put more than one space after a full stop; - precede comma (,), semicolon (;), colon (:), full stop (.), question mark (?) or exclamation mark (!) by spaces; - use spaces in place of tabs when indentation/alignment is required; this can cause text to be misaligned; - use footnotes or end-notes; - unnecessarily use capital letters; - use underlining to emphasize text (this can be confused with revision marking; see also clause H.7.1). - use "curly" or "smart" (". . .") quotes. H.7 Other formatting considerations H.7.1 Text decoration It is permissible to use italic and/or bold font for the purposes described in clause H.6. The use of underlining shall be restricted to the special case where a TS or TR cites text from an external source but makes changes to it; those changes are marked by underlining of newly inserted text and strikeout of text to be deleted. See annex J.3. Underlining shall not be used in any other circumstances due to the risk of confusion with revision marks. Coloured text shall not be used in TSs and TRs. The text colour shall be left as "automatic" which is normally rendered as black (but may vary depending on the user's setup). Other text decoration such as highlighting, blinking, shadow, embossed, etc shall not be used. H.7.2 Colours within figures It is acceptable to use colours for both graphic elements and text within figures, since this use cannot be confused with revision marks, where the whole figure is replaced rather than elements within the figure. Annex I (normative): Text containing SDL, program code, ICS and TTCN I.1 SDL diagrams Provide SDL diagrams in SDT binary files or, exceptionally, as CIF files when not using SDT. When using SDT use the .ini file supplied on the 3GPP server. Take into account the following when inserting SDL diagrams in Word documents - Do not include SDL headers or footers. I.2 Program code Large volumes of program code, source code or formal description language shall be placed in a separate file. I.3 Implementation Conformance Statement (ICS) proforma tables (For further study.) I.4 Tree and Tabular Combined Notation (TTCN-2) Provide TTCN as a separate file. Provide Machine Processable (MP) files. The following text should be used for ATSs using TTCN-2. The subdivision is recommended. This ATS has been produced using the Tree and Tabular Combined Notation (TTCN-2) according to ISO/IEC 9646โ3 [<x>]. The ATS was developed on a separate TTCN-2 software tool and therefore the TTCN-2 tables are not completely referenced in the table of contents. The ATS itself contains a test suite overview part which provides additional information and references. The TTCN-2 Machine Processable form (TTCN.MP) The TTCN.MP representation corresponding to this ATS is contained in an ASCII file (<filename>.MP contained in archive <filename>.ZIP) which accompanies the present document. I.5 Testing and Test Control Notation (TTCN-3) Provide TTCN as a separate set of files. The following text should be used for ATSs using TTCN-3. The subdivision is recommended. This ATS has been produced using the Testing and Test Control Notation (TTCN-3) according to ETSI ES 201 873-1 [<x>]. The ATS was developed on a separate TTCN-3 software tool and therefore the TTCN-3 definitions are not completely referenced in the table of contents. The ATS is contained in a set of ASCII files (<filename>.TTCN contained in archive <filename>.ZIP) which accompanies the present document. Annex J (normative): Endorsement of documents from other standards organizations J.1 General In the case that a 3GPP TS or 3GPP TR would become almost identical to a document from another standards organization, the TSG may decide to prepare a 3GPP TS or 3GPP TR defining only the differences, if any, between that document (commonly called "endorsed document") and the 3GPP TS or 3GPP TR. Such a 3GPP TS or 3GPP TR, commonly called "endorsement", shall be drafted in accordance with the present document, with the exceptions defined below. J.2 Title If the endorsed document is referred to without modifications, the title of the 3GPP TS or 3GPP TR should be as close as possible to the title of the endorsed document, but comply with the provisions of annex D. EXAMPLE 1: Endorsement of ITU-T Recommendation Q.1215 (1993): "Physical plane for intelligent network CS-1", gives the 3GPP TS the title: Intelligent Network (IN); Physical plane for intelligent network Capability Set 1 (CS1) [ITU-T Recommendation Q.1215 (1993)] If the endorsed document is referred to with textual (technical and/or editorial) modifications, the title of the 3GPP TS or 3GPP TR shall indicate that. EXAMPLE 2: Endorsement of ITU-T Recommendation G.957 (1993): "Optical interfaces for equipments and systems relating to the synchronous digital hierarchy", gives the 3GPP TS the title: Transmission and Multiplexing (TM); Optical interfaces for equipments and systems relating to the Synchronous Digital Hierarchy (SDH) [ITU-T Recommendation G.957 (1993), modified] J.3 Requirements This element is mandatory and shall be entitled "Endorsement notice". If the endorsed document is referred to without modifications, the following text should be used: "All elements of โฆ. apply." If the endorsed document is referred to with modifications, the following text should be used: "The elements of โฆ. apply , with the following modifications:" The modifications shall be presented in an order following the sequence of clauses of the endorsed document. General modifications shall precede specific modifications. - The use of manual revision marks for the presentation of the modifications is recommended. Deleted text should be struckout; inserted text should be underlined. Neither deleted nor inserted text should be coloured. J.4 Annex Designation of the serial order of an annex shall be with two letters, the first letter always being Z (i.e. ZA, ZB, ZC, etc.), in order to avoid confusion with any annexes of the endorsed document. Annex K (normative): Non-inclusive terminology and alternatives Table K.1 contains a list of non-inclusive terminology together with a non-exhaustive list of suggested alternatives. Table K.1: Non-inclusive terms and alternatives Non-inclusive term Examples of alternative terms master (when used in "master / slave" context) primary, controller, main slave secondary, standby white list (NOTE) allow list, accept list black list (NOTE) block list, drop list, forbidden list grey list (a term which has been used in conjunction with white list and black list) should be replaced with e.g. track list, inspect list (NOTE). NOTE: including single word and hyphenated versions. Annex L (informative): Change history Change history TSG SA# TDoc Version CR <Phase> New Version Subject/Comment 05-2000 - 0.0.0 First draft, internal to MCC. 06-2000 0.0.0 - 1.0.0 Editorial clean up SP-08 SP-000278 1.0.0 - 1.0.1 Presentation to SA#8 SP-08 1.0.1 Rel-4 4.0.0 Approved (Rel-4) SP-11 SP-010193 4.0.0 001 Rel-4 4.1.0 Automatic numbering of references SP-11 SP-010213 4.0.0 002r1 Rel-4 4.1.0 Clarification on use of automatically numbered figures, tables, etc. SP-13 SP-010482 4.1.0 003 Rel-4 4.2.0 Corrections of invalid clause reference SP-15 SP-020105 4.2.0 004 Rel-4 4.3.0 Correction of invalid table number, annex H. SP-16 4.3.0 Rel-5 5.0.0 Upgrade to Rel-5. 5.0.0 Rel-5 5.0.1 2002-07-19: Correct cover page. 5.0.1 Rel-5 5.0.2 2003-05-15: Correct cover page. SP-23 5.0.2 Rel-6 6.0.0 Upgrade without change to Release 6 SP-28 SP-050401 6.0.0 009 Rel-7 7.0.0 The use of 'void' SP-29 SP-050535 7.0.0 013 Rel-7 7.1.0 Introduction of MS Visio 014r1 Specification of versions of permitted software packages SP-30 SP-050689 7.1.0 015 Rel-7 7.2.0 Inclusion of version identity for Visio SP-34 SP-060914 7.2.0 017 Rel-7 7.3.0 Alignment of section 6.6.4.2 and annex I in respect of figure format. SP-37 SP-070527 7.3.0 018 Rel-8 8.0.0 Upgrade to Rel-8, allowing for more recent versions of application file formats SP-39 SP-080078 8.0.0 020 Rel-8 8.1.0 Correction of illegal text 021 Elimination of IPR provisions SP-46 8.1.0 9.0.0 Upgrade to Rel-9, no technical change SP-48 SP-100365 9.0.0 024r4 Rel-10 10.0.0 References to Figures and Tables SP-100422 026r1 Clarification on usage of "may", "may not", "can" and "cannot" SP-49 SP100655 10.0.0 028r3 Rel-10 10.1.0 Supported file formats 029r3 Rules on referencing unpublished documents SP-100629 030 Clarification on the use of References 10.1.0 Rel-10 10.1.1 Editorial correction to previous meeting's entry in this history table. 10.1.1 Rel-10 10.1.2 Editorial correction to table H.3 SP-55 SP-120112 10.1.2 031r1 Rel-11 11.0.0 Clarification on treatment of void clauses SP-56 SP-120317 11.0.0 033 Rel-11 11.1.0 Page breaks before annexes SP-57 SP-120610 11.1.0 034r1 Rel-11 11.2.0 TS and TR titles SP-61 SP-130365 11.2.0 035r1 Rel-12 12.0.0 Use of colour and other text decoration 036 Permissible file formats SP-64 SP-140201 12.0.0 037 Rel-12 12.1.0 Underlining SP-65 SP-140447 12.1.0 039 Rel-12 12.2.0 UML tool SP-67 SP-150115 12.2.0 040 Rel-12 12.3.0 On number stability and hanging paragraphs SP-70 Rel-13 13.0.0 Upgrade without technical change Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2016-09 SA#73 SP-160746 0043 1 B Precisions on how to void redundant clauses 13.1.0 2016-12 SA#74 SP-160800 0044 F Disambiguation of terminilogy 14.0.0 2017-06 SA#76 SP-170409 0046 F Updates to drafting rules on TTCN file formats 14.1.0 2017-10 Correction of spelling error 14.1.1 2018-06 SA#80 SP-180466 0047 B Introduction of new drawing tool 15.0.0 2018-09 SA#81 SP-180846 0049 F Allow specs in .docx format, forbid curly quotes, modify decimal point rules, allow automatic clause numbering during drafting 15.1.0 2018-12 SA#82 SP-181246 0050 1 B Introduction of MathType 16.0.0 2019-03 SA#83 SP-190025 0053 F Reduce use of the term "subclause" 16.1.0 2019-03 SA#83 SP-190257 0052 1 F Clarifications on References, including copyright issues for referenced works no longer publicly available 16.1.0 2019-03 SA#83 SP-190271 0054 2 F Minor restructuring as a result of more logical categorization of elements 16.1.0 2019-09 SA#85 SP-190665 0055 F Correction of internal references 16.2.0 2020-12 SA#90e SP-201142 0056 1 B Use of inclusive terminology 17.0.0 2021-03 SA#91e SP-210046 0057 F Permitted software tools update 17.1.0 2021-06 SA#92e SP-210307 0058 D Replacing 'Chairman' by 'Chair' 17.2.0 2024-03 SA#103 SP-240276 0061 F Clarifications to maintain symmetry and update of numbering and cross-references 18.0.0 2024-03 SA#103 SP-240277 0062 D Editorial clean-up 18.0.0 2025-03 SA#107 SP-250243 0065 C Update of mathematical formulae and tools used 19.0.0 |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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".
[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". |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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: release status or specification status in which no changes of any kind to the release or 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: release status or specification 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.
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.
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.
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.
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. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 3 General responsibilities of the Support Team | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4 Handling of Specifications | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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
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
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 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
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 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
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.
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)
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.)
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 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
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.
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 systems.
Continue to be maintained by 3GPP. Not propagated beyond Releaseย 1999.
aa.0bb
Specifications applicable to both GSM and UMTS 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:
Direct equivalent to aa.bb GSM specification for previous Releases.
aa.1bb
Specification either (a) derived from earlier GSM specification, but with technical modification; or (b) new specifications.
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.
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.
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.
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
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"
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)
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ย 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
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
(pure GERAN-based system)
aa.bb v8.y.z
pure UTRAN-based system and common UTRAN- & GERAN-based systems Releaseย 1999
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
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). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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 clauseย 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.
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.
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). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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:
- 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. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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).
- The specification is a Technical Report or a Technical Specification
- A specification has versions which are identified by three numbers (see 4.0A). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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: In the description above, attribute values are bold. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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
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
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
- 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
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
- 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
[- 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
[- 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
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. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.5 (void) | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.6 Change Request regime | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 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).
A CR may be raised by any individual member and brought to the attention of the responsible Group.
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. 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.
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".
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.
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.
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.
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.
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. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.6.2 Change Request forms | To ensure an appropriate and consistent way of presenting and documenting Change Requests, there exist standardized front covers (forms) for CRs as well as rules on how to accurately identify the modified parts of the specification.
The purpose of the CR form itself is to provide the relevant management information of the proposed changes, e.g. such as:
- Target specification with its version number (i.e. the original version to which CR is drafted),
- Source of the CR,
- Reason for the proposed change and consequences if not accepted,
- Category of proposed change (i.e. correction, Change Request corresponding to an earlier release Change Request, addition of feature, functional modification of feature, or editorial modification),
- Cross-phase compatibility aspects.
A CR to a major version of a specification can fall into any of the categories quoted below.
Table 4A: Categories of Change Requests
Category
Meaning
Remarks
A
Corresponds to a change to an earlier Release
Used to reflect functionally equivalent changes made to an earlier Release of the same Specification.
NOTE: The proposed change to the later Release of the Specification need not be absolutely identical to the proposed change to the earlier Release, since it is possible that, due to earlier change requests, the affected text is not identical in each Release. Category A should be used when the functional objective of the proposed changes is equivalent in the earlier and later Releases.
B
Addition or deletion of feature
The new feature is to be added to the Release; the reference is not to the Specification itself. This will normally correspond to an identified Work Item. This category shall not be used for a frozen Release, except for alignment CRs as described in clause 4.7.
C
Functional modification of feature
Any functional modification shall correspond to an identified Work Item. However backward compatibility shall be ensured when the issue has an impact on the UE. This category shall not be used for a frozen Release, except for alignment CRs as described in clause 4.7.
D
Editorial modification
Editorial modifications shall have no impact on an implementation. An editorial modification CR to a frozen Release shall not be permitted.
E
(not used)
F
Correction
Used:
1 to correct an error in the specification (i.e. a clear instruction in the specification which leads to incorrect operation of the system); or
2 to correct an ambiguity in the specification which could lead to different implementations which cannot inter-operate; or
3 (void); or
4 to remedy the incorrect implementation of a previously approved CR; or
5 to correct a misalignment between the specifications (stage 1, stage 2 & stage 3) for a feature or service when not introducing a new function or functional change.
Notwithstanding the provisions of tableย 4A, a TSG may approve a CR of category B or C to a frozen specification if it is the consensus of the meeting that such an exceptional action is justified; see clause 4.7.
On successful reservation of a Change Request TDoc, the 3GPP portal will push the completed CR cover page to the user. This cover page has all the relevant metadata already filled in, thus eliminating transcription errors on the part of the author. It is strongly recommended that the author make use of this facility rather than filling in a blank CR cover from the stock template. Tips on how to complete the remaining fields of the CR form can be found at https://www.3gpp.org/specifications-technologies/specifications-by-series/change-requests-step-by-step.For reference, the CR database is available from the 3GPP file server (https://www.3gpp.org/ftp/Information/Databases/Change_Request/).. Alternatively, the CRs for a given specification or from a given meeting can be consulted on the 3GU portal (https://portal.3gpp.org).
When a CR is presented for approval, the classification into which it falls shall be identified. If this cannot be done then the CR shall be automatically rejected.
The CR form bears a field to indicate the Release number to which the CR pertains. This field shall show the Release of the intended resulting specification โ that is, the Release of the specification after implementation of the CR. The Release shown on the CR form is not related to the Release of the feature to which the change relates, but to the Release of the specification being changed. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.6.3 Contents of Change Requests | Although the CR form shall indicate the details of change, each CR shall have attached the clauses of the specification that are affected by the CR, using the latest version of the major version. These clauses shall have the proposed modifications clearly marked, by means of the word processor's "revision mode".
In case there are more than one independent CR to the same part of the specification, neither of them should contain the proposed modifications from the other(s), however any potential interaction between the modifications should of course be resolved before presentation.
If the CR proposes changes to stage 3 specification files which are normatively documented in the 3GPP Forge repository according to clause 5C, then the proposed modifications shall be documented in the 3GPP Forge repository. In this case the cover page of the CR form shall contain a reference to a Forge Merge-Request clearly listing the proposed modifications in the "Other comments:" field, and excerpts of all affected stageย 3 specification files clearly showing the proposed changes shall be appended to the cover page of the CR form. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.6.4 Handling of the Change Requests | Entry to the TSG WG:
A proposed CR should be brought to the relevant Group primarily responsible for the specification concerned and discussed there, before presentation to the TSG. Comments from secondarily responsible Groups (if any) shall have been sought and comments shall have been taken into account before presentation to the TSG for approval.
To ease the work of the Group and of the Support Team , a proposed CR should be presented in a form suitable for TSG WG agreement and TSG approval. If a CR is not immediately accepted the originator shall update the CR taking into account comments and other guidelines from the relevant groups, including change of reference version if needed, and to re-present it to the Group.
All CRs shall be presented in electronic form.
CR identification:
During the course of its development, a CR may be modified, and the CR's progress shall be indicated by allocation of a revision number: rev. 1, 2, and so on. A given revision of a CR is uniquely defined by
- the specification to which it belongs, and
- the CR number (an alphanumeric string) and
- the revision number (default, i.e. the value if no number is given, is '-', i.e. the original, unrevised, CR).
A CR number shall be allocated by the 3GPP portal or the Support Team. For a given Specification, CR numbers shall be unique and shall never be reused (see clause 4.6.1). Numbers used for rejected CRs shall not be reused. If a CR is rejected, and the responsible Group considers it useful to bring a modification of the CR to a subsequent TSG for approval, the new CR shall be allocated a new CR number. That is, it shall not be presented as a revision of the same CR number previously rejected.
Impact on other specifications:
If the content of the CR is such that, in isolation, it makes the whole set of approved Specifications inconsistent, corresponding CRs shall also be considered and produced. This should be carried out by the originators of the CR (and their colleagues in other Groups) in advance. The Support Team is co-responsible for identifying and communicating cross-TSG and cross-TSG-WG impacts.
If a CR (or set of CRs) causes an inconsistency with an existing/approved test or O&M specification, the corresponding CRs should be presented together with the core specification CR in the same TSG cycle. Otherwise they may follow in a later TSG cycle.
Handling of the CR in the TSG:
When the TSG WG has agreed to a CR and comments from secondarily responsible Groups (if any) have been taken into account, the Support Team shall ensure that it is correctly formatted and assembled, and shall submit the CR to the primarily responsible TSG for formal approval.
The Support Team shall collate agreed CRs in CR packs.
The Support Team shall make available to the TSG summary lists of all CRs presented for decision. This list shall be updated to show the decision reached for each and every CR.
Decisions on CRs, and results:
The TSG shall consider and conclude on each CR independently; the verdict on each CR shall be one of the values listed in clause 9.2
Table 5: (void)
Control and notification of CR decisions:
At the end of each TSG meeting, the Support Team shall issue lists containing the detailed result of the CRs presented at the meeting, including information about the consequential new version numbers of the concerned specifications. These lists shall form an annex to the meeting report (and hence are part of a permanent document). These lists, being the evidence of which specifications have changed and how, are important management tools for both TSG delegates and the Support Team since it takes some time before the new versions of the specifications can be compiled and released. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.6.5 Updating and release of new versions of the specifications | If there is at least one Approved CR to a given specification, a new version number of the specification shall be allocated (see clause 4.2.3), and the Support Team shall produce and issue a new version of the specification. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.6.6 Other changes to specifications | The Support Team may update a specification to correct purely editorial deficiencies brought to its attention. In this case, only the "editorial" field (third digit) of the version number shall be incremented. Such changes should be avoided if possible: normally, they should be held over for inclusion next time a technical change is made to the specification.
All such changes shall be clearly explained in the "change history" annex of the specification. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.7 "Freezing" of specifications | A TSG may decide that a specification is sufficiently stable that it may be considered "frozen". That is, only CRs for essential corrections of errors shall be considered except as discussed below (see clauseย 4.6.2 and in particular the derogation statement below tableย 4A).
At the same time, a new major version may be developed for inclusion of new features.
Normally, all specifications of a Release will be frozen when the TSGs decide that the functionality of the Release is stable โ i.e that all new features to be included in the Release have been defined and that all new or modified functionality required to implement those features has been incorporated into the specifications. At this point, the Release as a whole shall be declared to be "frozen", and its constituent specifications shall likewise be "frozen".
A CR of category B or C (and any associated category A mirrors) to a frozen version of a specification (in a given Release) shall only be an alignment of the specification with the agreed functionality of the Release as provided for in other specifications of that Release, or for internal consistency of an individual specification. Such a CR may add to, remove from, or modify the functionality of a frozen specification to ensure a consistent specification set across a particular Release.
Correction CRs (category F and any associated category A mirrors) to a frozen version of a specification (in a given Release) shall fit into one of the following classifications:
- A CR to introduce an essential correction, i.e. where a frequently occurring case is not handled properly because there is some error or significant ambiguity in the specification.
NOTE: The CRs of the above category are sometimes referred to as "FASMO" CRs: "Frequent And Serious MisOperation".
- A CR to remedy the incorrect implementation of a previously approved CR (of any category). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.8 "Closing" of specifications | A TSG may decide that a specification of a certain Release will no longer be maintained that it may be considered "closed". That is, no further Change Requests to the specification of this Release shall be considered. The specification of the Release remains available (e.g., for referencing reasons), but no further Change Requests shall be produced, even corrective ones to align with the equivalent specification of a subsequent Release.
All specifications of a Release will be closed when the TSGs decide that the Release is no longer to be maintained (i.e., the Release is closed). A specification of a Release can only be closed if the specification(s) for previous Releases are closed. At the same time, higher major versions of the specification may be under development (i.e. for a later Release). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.9 "Withdrawing" of specifications | A TSG may decide to withdraw a specification which is obsolete if its remaining available would confuse implementors (for example, if it contained provisions which were contradictory to provisions of other, later, specifications).
Before withdrawing a specification, the TSG shall ensure that no references are made to it from any other 3GPP specification (and raise appropriate Change Requests to eliminate any such references discovered).
A TSG shall use the procedure in clause 4.9B to withdraw specifications and functionality.
4.9A "Withdrawing" of functionality
A TSG may decide to withdraw functionality.
Before withdrawing functionality, the TSG shall:
- raise Change Requests to eliminate any references made to this functionality from any 3GPP specifications; and
- move text within specifications which were created for the functionality, that is applicable to other functionality as well, to other appropriate specifications.
4.9B Procedure for withdrawing of specifications and functionality
4.9B.1 (void)
4.9B.2 Diligent assessment
The decision whether to withdraw (a) specification(s) or whether to remove functionality from within specifications shall only be taken once thorough consideration has been given to the implications and applicability of the action.
The withdrawing of a specification or functionality shall be explicitly identified as one of the objectives of a work item.
The withdrawing of a specification or functionality may be documented in:
a) a work item that defines new functionality that will obsolete the specification or functionality; or
b) documented in a work item that is solely for the purpose of withdrawing.
Technical Enhancements and Improvement (TEI) and other similar general purpose enhancement work items shall not be used for the withdrawing of a specification or functionality.
The assessment of whether to withdraw functionality may extend beyond 3GPP TSGs and their working groups. A notice shall be placed on the 3GPP site to solicit comments from other concerned parties and shall clearly indicate which specifications and functionality are considered for withdrawal, including which versions of the specification would be affected, the date at which a decision will be taken and the responsible TSG to which third parties may send related Liaison Statements or other correspondence.
A study item may contain, as one of its objectives and/or its conclusions, consideration of whether existing functionality should be withdrawn and the identification of the impact of the withdrawing of functionality or specifications.
4.9B.3 Changes to affected specifications
Removal of functionality shall be done using the normal change request procedure (see sub-clause 4.6).
4.9B.4 Considerations for ongoing maintenance, enhancement and new Release versions of specifications
When a specific version or all versions in a specific Release of a specification, are withdrawn further versions of the specification in the same Release shall not be created and the specification shall not be promoted to a subsequent Release.
Evolution of specifications and functionality in Releases unaffected by the withdrawal are allowed.
A Category B or Category C CR that adds to or modifies a specification or functionality that has been withdrawn in a subsequent version shall clearly state on the CR cover sheet in the Summary of change that the subsequent version of the specification or functionality has been withdrawn.
Category A CRs for Releases in which the specification or functionality has been withdrawn shall not be produced. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10 Release control | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.1 Creation of a new Release version of a specification | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.1.0 General | The concept of Releases was introduced in clause 4.0B. A given specification may simultaneously exist in several versions, each corresponding to a different Release.
In principle, a Release of the specification can be identified as consisting of all those specifications with a "major" version field of a given value. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.1.1 With no technical changes compared to the previous Release | A given Release consists of a set of specifications having a common "major" version field; therefore, for the set of specifications to be complete, a new specification needs to be produced even if its provisions are identical with those of the previous Release's version. The creation of such a specification shall be delayed until the latest possible moment - that is, until the TSG is on the point of declaring a given Release to be complete, having determined that no technical changes are needed in the specification compared with the previous Release.
The creation of the new version under these circumstances shall be via the responsible TSG's taking a decision to upgrade to the next Release of the specification.
This implies that all Groups need to conduct a rigorous review of all specifications for which they are responsible to determine which are to be propagated to the next Release and which are not. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.1.2 When introducing technical changes | A new version of a specification, corresponding to a new Release, shall be prepared when a technical change needs to be introduced to satisfy a requirement of a feature of that new Release. This shall be accomplished by the raising of a Change Request (see clause 4.6) in the usual way, with the version number of the resulting specification indicating the new Release. The CR shall bear the identity of the new Release (rather than the starting point Release โ see clauseย 4.6.2). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.1.3 Specifications not propagated to next Release | Specifications which are not propagated from Release N-1 to Release N in one of the above two methods shall be deemed not to form part of Release N. Under these circumstances, the responsible Group shall undertake a review of all other specifications of Release N to eliminate references to the specification concerned. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.2 Mirror Change Requests | When a Group produces a Change Request changing an early Release of a specification, it shall check whether the same change also needs to be made to later Releases of the specification. Changes which are corrective or clarifying in nature will generally be applicable to such other versions.
Where it is determined that several Releases are affected, an (independently numbered) Change Request shall be created for each such affected version of the specification. Such CRs are termed "mirror Change Requests". The principal CR and its related mirror CRs should be grouped together for the purpose of presentation to the TSG (unless some other grouping is more logical).
The TSG shall approve (or postpone or reject) a CR to a given Release together with the corresponding mirror CRs to later Releases. This will provide consistency between Releases.
See also subclauseย 4.6.2. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.3 Release mechanisms | It is important that the 3GPP release structure provides a sound basis for implementations and equipment interoperation. Key principles important to ensure this are:
- A Release shall consist of a well-defined, stable and internally consistent set of functions.
- A Release shall be documented in a maintained, consistent stream of specifications.
- Essential corrections to a stable or frozen release shall be included in the applicable Release.
- New or changed functionality shall be included in a new (rather than retrospectively in an old) Release.
These principles will ensure successful interoperability (roaming) amongst different instantiations of 3GPP systems. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.3.1 Corrections to Releases | Each release should be consistent and implementable to ensure interworking. This implies that essential corrections become normative parts of the Release as soon as possible. If essential changes to "old" functionality are made to a new release, similar corresponding changes shall be made to correct the same error in the specifications pertaining to all previous, non-closed, Releases. This is illustrated in figureย A. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.3.2 New features | New functionality shall be included in the latest, non-frozen, Release. New functionality shall not be included in previous, frozen, Releases. To do so would cause incompatibility amongst instantiations of those Releases. This is illustrated in figureย A.
CR category
(see table 4A)
Release
1999
Release
4
v3.0.0
C
๏ฏ
v3.1.0
C
๏ฏ
v3.2.0
C
๏ฏ
v3.4.0
C
๏ฏ
v3.5.0
B
๏ฎ
v4.0.0
F
A
๏ฏ
๏ฏ
v3.6.0
v4.1.0
C
๏ฏ
v4.2.0
C
๏ฏ
v4.3.0
F
A
๏ฏ
๏ฏ
3.7.0
4.4.0
Figureย A: Introduction and development of new features to the latest Release; and corrections to multiple Releases (example) |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.3.3 Release naming | GSM phase 2+ specifications were grouped into annual Releases from 1996 to 1999. The first 3rd generation specifications were grouped into an initial Releaseย 1999.
Subsequent Releases are not necessarily annual, and shall be referred to as Releaseย 4, Releaseย 5, etc., according to the major field of the version number (seeย tableย 4 and clauseย 4.3). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.3.4 Introduction of features into Releases | Development of the 3GPP system specifications shall be controlled by means of a work plan covering the inclusion of new features (functionality). Target dates for completion of Work Items (see clauseย 6) shall be estimated by the responsible Groups. Milestones may be defined to monitor the progress of Work Items. Based on the estimated completion of the desired features, a target date for freezing of the specifications pertaining to the next Release can โ and shall โ be calculated. Feature development should be based around approximately annual Releases.
Thus the work plan shall indicate (a) the estimated freeze date of forthcoming Releases and (b) the functional content of each such Release. The work plan shall show all projected work, regardless of Release; this will ease long term planning and the packaging of features into Releases. Completed Work Items shall be removed from the plan once the Release of which they form a part has been frozen.
3GPP technical coordination should set target dates for the freezing of each individual stage (cf. clause 4.1) on all currently worked-upon Releases (i.e. non-frozen).. On freezing stage 2 of Releaseย x, TSGs should propose a target freeze date for stagesย 1, 2 andย 3 of Releaseย x+1. It is possible that features of exceptional complexity may span more than one Release (eg new core network architecture, new radio interface).
The freezing date for a particular stage of a Release should insofar as is possible be adhered to, even if, due to delays, it is not possible to include all the features originally intended. Features which cannot be completed in time should be held over to the next Release. It will normally be the case that test specifications and O&M specifications will not necessarily be completed until some time after the base specifications; this shall not impede the freezing of the Release as a whole. However, if it becomes evident that, due to delays in a number of important features, a new Release would contain little new functionality, it may be preferable to delay the freezing of the stage of a Release to allow more of the originally intended features to be included.
The project plan shall clearly show the progress of each Work Item. When all component Work Items of a feature have been completed, the TSG shall declare the feature to be frozen. The only further development permitted from that point onwards shall be:
- the essential correction of errors;
- the completion of the test and O&M specifications; and
- unavoidable adjustments required to cater for interworking with other features in the same Release.
See clauseย 6 for further information on Work Items. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 4.10.3.5 Early implementation of features | 3GPP may identify certain features as being suitable for "early implementation". The selection of "early implementation" features shall be performed at the TSG level.
Additional documentation is provided for early implementation features (see clause 6.4.4).
All documentation for early implementation features is contained in the Release where the feature is introduced. The status or specification of older Releases shall not be changed by the introduction of early implementation features. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 5 Availability and distribution of specifications | 5.1 General
The Support Team shall make all approved versions of all specifications available as soon as possible after their approval (or after approval of CRs thereto) on a file server. The server shall allow anonymous access by any interested party.
The Support Team should also endeavour to make earlier drafts available on the server, even prior to approval, i.e. versions 0.y.z, 1.y.z and 2.y.z.
Such "availability" does not constitute formal "publication". Under the terms of the 3GPP partnership agreement, the Organizational Partners which are Standards Development Organizations will publish TSG-approved specifications in the form of their own standards. The modalities of such publication processes are specific to those individual Organizations and are beyond the scope of the present document.
The directory structure shall differentiate amongst approved and draft specifications, amongst versions of specifications approved at specific TSG meetings, amongst versions of specifications pertaining to different Releases, and between specifications relating to 2nd generation (GSM) only and 3rd generation (UMTS) systems.
A clear and unambiguous directory structure shall be adopted, and a guide to that structure provided on the server. A "status list" shall also be provided, showing the latest version of each Release of each specification.
5.2 Choice of availability and distribution of stage 3 specification files
For the availability and distribution of stage 3 specification files (e.g. OpenAPI specification, YANG, ASN.1, XSD, etc.) there are two optional alternatives, described in clauses 5B and 5C, and the principle of how the two alternatives are chosen is decided by the responsible Working Group. Clause 5C applies only for the choice when normative code parts of the stage 3 specification are normatively stored in the 3GPP Forge repository.
5A File naming conventions
Specifications shall be maintained in the form of computer-based files. The file name shall be of the form
aabbb-xyz.eee
where:
aa and bbb have the same significance as in the specification number (see tables 1 and 2);
x, y and z have the same significance as in the version number (see table 6);
eee is the de facto standard filename extension corresponding to the software tool used to create the file (normally "doc" for Microsoft Word ยฎ).
For multi-part specifications, the filename shall be extended to
aabbb-n-xyz.eee
Where:
n is the part number (see tables 6 and 6A).
To save storage space and to speed up uploading and downloading, source files shall be saved compressed in industry standard "Zip" ยฎ format. The filename of the zipped file shall be the same as that of the contained source file, and it shall bear the file extension ".zip".
If a specification consists of multiple source files - for example, when a very long document is divided into several smaller files for ease of editing and manipulation - , each file should be named with the above convention, but appending a file identifier in the form:
aabbb-xyz(m).eee
where:
m is the file number using characters from table 6 or 6A.
Where a specification has accompanying files - e.g. ASN.1 coding, C programming language code, TTCN test sequences, etc. - it may not be convenient or possible to abide by the last-mentioned rule. Under these circumstances, the associated files shall be contained in a separate zip file, which shall itself abide by the multiple-source-file rule. A "readme" text file should be included in that zip file to explain the nature of each other file.
EXAMPLE 1: 29341-420.zip is the compressed file of specification 29.341 version 4.2.0.
EXAMPLE 2: 31811-m-6g2.doc is the source file of specification 31.811 part 22 version 6.16.2.
EXAMPLE 3: 22354-480(1).doc and 22354-480(2).doc are the two files which make up specification 22.354 version 4.8.0 (and which will both be compressed into file 22354-480.zip).
EXAMPLE 4: 34101-300(1).doc and 34101-300(2).zip are the source text file and the compressed set of TTCN files respectively which together comprise 34.101 version 3.0.0.
Draft versions of specifications may be made available in the responsible Groups' directories. Such versions shall be clearly distinguishable from "official" versions by substituting "d" for the hyphen before the version code. Thus:
aabbbdxyz.eee
(for example, 28033d410.zip). Such files shall never appear in the official specification directories.
The foregoing file format using three characters for the version number is valid as long as none of the three version elements (major, technical, editorial) exceeds the value 35, since the characters 0..9, a..z represent a base-36 value. If any one or more of the three version elements exceeds 35 then the file format shall be modified to use two decimal characters in the range 00 to 99 for each element, i.e. six characters in all.
EXAMPLE 5: Version 15.35.0 of TS 29.341 would have the file name 29341-fz0.
Version 15.36.0 of TS 29.341 would have the file name 29341-153600.
(The file extension is omitted for clarity.)
For specification part and sub-part numbers, one or two characters may be used, 0..9 or 00..99. Ideally the intended number of parts and sub-parts should be known when the first specification numbers are allocated so that the correct number of digits can be used from the outset, ensuring that filenames are correctly sorted when listed.
EXAMPLE 6: Permissible filenames for multi-part specifications (file extensions omitted for clarity):
29341-1-5
29342-2-15
29343-13-21
29344-08-55
29345-19-6
Part and sub-part numbers shall not use characters a..z, but shall always be one- or two-digit decimal values.
Table 6: Characters used in filenames to represent numeric values โ single character
Value
Character
Remarks
0
0
Only for use in version number fields. Part / sub-part numbers and file numbers start at 0 or 1 (or 00 or 01 โ see table 6A).
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
10
a
11
b
12
c
13
d
14
e
15
f
16
g
17
h
18
i
19
j
20
k
21
l
22
m
23
n
24
o
25
p
26
q
27
r
28
s
29
t
30
u
31
v
32
w
33
x
34
y
35
z
Higher values โ see table 6A.
Table 6A: Characters used in filenames to represent numeric values โ two character
Value
Character
Remarks
0
00
1
01
2
02
...
9
09
10
10
11
11
...
34
34
35
35
36
36
37
37
...
98
98
99
99
Higher values for further study if necessary
5B Availability and distribution of OpenAPI specification files
As described in the clauseย 5.3.1 of 3GPPย TSย 29.501ย [6], 3GPP Technical Specifications describing an API or common data types shall include an annex documenting the corresponding OpenAPI specification file.
For a TS agreed by the WG to be sent to TSG for approval to come under change control, the responsible MCC officer, in preparing that version (normally v2.0.0) shall, in conjunction with its rapporteur, check that the OpenAPI specification file(s) is(are) syntactically correct. This exercise should be accomplished in time to meet the deadline for submission of TDocs to the TSG plenary meeting. If errors are detected at this stage, the rapporteur should ask delegates to raise corrective pCR(s) to be sent directly to the TSG to correct the draft TS. The TSG shall be requested to approve both the draft TS and any such pCRs as a package, and if the package is approved, MCC shall incorporate those pCRs into the TS when preparing the first under-change-control version.
Prior to a TSG plenary meeting, the responsible MCC officer shall prepare CR Packs for all WG-agreed CRs in the usual manner. For those CRs which change the OpenAPI specification file(s) of the TS, the MCC officer and/or the rapporteur shall perform a trial implementation of those CRs which affect the OpenAPI specification file(s), and again check that the resulting specification file(s) is(are) syntactically correct. If errors are detected at this stage, the rapporteur should request authors of problematic CRs to provide corrective revisions of those CRs to be sent directly to the TSG as company contributions. The TSG shall be asked to approve all WG-agreed CRs for which no problems were detected plus the company revision CRs addressing the problematic ones. Ideally, not only the CR Packs containing the original WG-agreed CRs but also the revised, company-provided, CRs should be provided in time to meet the deadline for submission of TDocs to the TSG plenary meeting.
Before making available any new version of a TS containing an OpenAPI specification file, the responsible MCC officer shall extract the (syntax checked and verified) OpenAPI specification file from the annex of the TS and make it available as a stand-alone file in UTF-8 format as specified in IETFย RFCย 3629ย [7]. The file name shall follow the conventions defined in 3GPPย TSย 29.501ย [6] clauseย 5.3.6 unless the TS containing an OpenAPI specification file indicates a different file name.
If a new version of a TS containing an OpenAPI specification file is approved without any change to the contained OpenAPI specification file(s), the responsible MCC officer shall not modify the existing UTF-8 formatted OpenAPI specification file.
All the UTF-8 formatted OpenAPI specification files documented by TS shall be stored by the MCC officer in the following locations:
- https://forge.3gpp.org/rep/all/5G_APIs, and
- in the zip file containing the Word file of the new version of the TS (which is itself stored in the usual places).
5C Normative availability and distribution of stage 3 specification files
In this option, the normative code parts of the stage 3 specification shall be normatively stored in the 3GPP Forge repository.
The TS document specifying the stage 3 definition shall indicate that the 3GPP Forge repository is normative for the corresponding stage 3 specification files and:
- The TS document shall contain a link to a 3GPP Forge repository tag that implicitly includes the versioning information about the TS, e.g. https://forge.3gpp.org/rep/sa5/MnS/-/tree/Tag_Rel18_SA100;
- The TS document shall contain the directory path where the files are stored, e.g. "yang-models";
- The TS document shall contain the name of the files specified by this TS;
- The TS document shall not contain a copy of the stage 3 specification files.
Before making available any new version of a TS specifying stage 3 files, the responsible MCC officer shall download the specification files from 3GPP Forge and store them in the zip file containing the new version of the TS document. This zip file shall be published in the usual places.
All OpenAPI stageย 3 specification files referenced by the TS document shall also be stored by the MCC officer in the following location:
- https://forge.3gpp.org/rep/all/5G_APIs. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6 Work Items | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.0 Introduction | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.0.1 Introduction: why manage a project? | In any complex engineering venture, it is necessary to plan the project, to monitor its progress, and to be able to determine whether it is being completed on schedule and within budget. In many ways, the concepts and constraints which apply to an engineering project can also be applied to system standardization activity. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.0.2 How to manage a project? | Any project needs to have its goals defined. It is then possible to analyse the steps needed to achieve each goal, starting from the status quo.
It will often be desirable to first produce a feasibility report, which is to be undertaken in the context of a Study Item.
Study Item:
An initial study, resulting in a Technical Report, which typically performs a feasibility study for additional functionality. If the results of the study are positive, one or more subsequent Feature-type Work Items may follow.
A feasibility study may include commercial as well as technical considerations. This analysis will naturally lead to defining the new features which it is wished to add to the existing system.
Feature:
New, or substantially enhanced functionality which represents added value to the existing system.
A feature should be more or less self-contained - that is, each feature can be viewed as an optional extra, which can be added or not as a function of market demand. Network operators and equipment manufacturers can decide using commercial considerations whether or not to implement a feature. The description of a feature need not be technically precise, but should represent a concept which can be understood at a service level. It should answer the question: what do I get for my money? A feature should normally embody an improved service to the customer and / or increased revenue generation potential to the supplier.
This being the case, most features would be the responsibility of TSG-SA WG1. The ensemble of the features of a particular release of the system represents the difference between that release and the previous release.
A feature can be considered as a high-level goal for project management purposes. But most features will be quite complex, and will need to be broken down into simpler elements or building blocks for the purpose of specifying precise functionality.
Work on a study item or feature may be carried out by multiple working groups spanning one or more TSGs. In the case of multi-TSG study items and features, all such TSGs should be shown in the work plan as being responsible for the study item or feature; this should be refined as soon as possible into an identification of the individual working groups responsible. To allow work to progress, the Work Item Descriptions (see clauseย 6.1) may be approved by one TSG before formal contribution has been received by other involved TSGs and WGs, which should review the Work Item Description in a timely manner, and provide their own input as soon as possible.
Building block:
A sub-division of a feature, representing a coherent set of technical functionality which would generally be expected to reside in a single system element.
A building block shall be defined in technical terms, and its description will require an understanding of the architecture of the overall system. A building block should generally be restricted to a single physical or logical entity or a single protocol such as "terminal" or "call control". This implies a generic or object-oriented approach. A building block should normally be the responsibility of a single TSG.
In the case of very simple features, a single building block may suffice, in which case the feature and its building block are synonymous.
To implement a building block it will generally be necessary further to subdivide the functionality into smaller tasks, each representing a closely specified and easily comprehended activity. Such work tasks may not only be divided by technical content, but potentially by phase. So, for example, it is necessary to define service aspects fully (one or more work tasks) before considering functional information flows (one or more work tasks) which in turn will be followed by detailed protocol specification (one or more work tasks).
Work task:
A sub-division of a building block, representing a self-contained, well-scoped and well-scheduled item of work.
It is at this lowest hierarchical level of breakdown that estimations of work content and thus time scales can be calculated. From the estimated schedules of all work tasks which comprise a building block, and from their inter-dependences, can be derived the overall schedule for the "parent" building block. From the schedules of all component building blocks, the time-to-completion of the parent feature can be estimated. A work task will almost certainly be the responsibility of a single Working Group.
The output of a work task shall be:
- One or more new Technical Specifications (or Reports); and / or
- Change Requests to existing TSs / TRs.
Features, building blocks and work tasks are the three specific types of "Work Item".
In the case of very simple building blocks, a single work task may suffice, in which case the building block and its work task are synonymous.
Work Item:
A generic term used to encompass study item, feature, building block and work task.
All Work Items, whatever their class (feature, building block or work task) require:
- A precise definition of content ("scope");
- An estimated schedule, with milestones to track progress if possible; (in the case of building blocks and features, the schedule can be derived from those of the component work tasks);
- A named person to act as rapporteur (in effect, the manager of the Work Item);
- At least four Member Organizations supporting the Work Item and willing to offer active participation in its realization. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.0.3 Types of modification to specifications | The possible modifications of the specifications are basically of different natures:
- Error corrections: modifications which correct overlooked errors or inconsistencies in the specifications.
- Enhancements: modifications that enhance the system, e.g. by new services or features, or by improving performance or decreasing costs.
Modifications of the correction category (i.e. Category F) are ongoing maintenance tasks and are handled with CRs bearing the code of the Work Item that was used to introduce the affected feature, for the original Release in which it was introduced. Corresponding mirror CRs (i.e. Category A) may be produced for subsequent releases as applicable, using the same Work Item code. See also clause 6.2 covering the case where such a CR is not introduced into the TS or TR at the Release with which that Work Item is associated.
Modifications of the enhancement category (i.e. Category B or C) are handled within the concept of Work Items or as "technical enhancements". (See clause 6.2.) Note that prior approval of the WID by the TSG is needed before any substantial work is launched. If that work can be completed within one TSG cycle, the new WID may be approved at the same TSG meeting at which the enhancement CRs are presented. See clause 6.1 for the creation of Work Items. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.1 Creation of a Work Item | When new or enhanced functionality of the 3GPP system is considered desirable an Individual Member of 3GPP (or group thereof) may make a proposal by submitting a Work Item Description (WID) sheet to the relevant TSG or TSG WG:
- For new services, features or functions, the TSG responsible for Services and System Aspects is the relevant TSG. This TSG shall assign prime and, if necessary, secondary responsible TSGs for the corresponding Work Items.
- For pure performance enhancements, other TSG WGs may be responsible.
The relevant TSG WG should study and refine the WID before passing it on to the TSG for adoption.
No substantial work shall commence in a TSG WG prior to a decision of the responsible TSG.
The actual WIDs to be used and guidance on how to apply them shall be distributed by the Support Team.
The TSG shall not approve a Work Item unless the WID has been properly filled in to the extent possible.
The Support Team shall maintain a database of Work Items, and make it available on the 3GPP file server and portal.
A Work Item normally implies the creation of new specification and Change Requests to existing specifications. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.2 Types of Work Item | Modifications of the standard could in principle be of two different types:
- New services/features/functions that in general affect several specifications and involve several TSGs / WGs;
- Technical enhancements or improvements that affect one or a small number of specifications and involve a single or a few Groups only.
Modifications of the latter type may be submitted to the Working Group(s) and then to the TSG directly as a Change Request without prior presentation/agreement of a WI Description sheet. Such CRs shall instead refer to the pseudo Work Item 'Technical Enhancements and Improvements'. The CRs relating to this type of modification shall be tagged with the work item code TEI<x> where <x> represents the Release number: e.g. for Release 16, the code would be "TEI16".
TEI Work Item codes shall not be used where an appropriate Work Item code exists.
TEI Work Item codes should not be used for the definition of new services/features/functions (i.e. Category B CRs).
TEI Work Item codes should not be used alone for functional modification of existing services/features/functions (i.e. Category C CRs).
Nevertheless, if a feature is functionally modified by a Category C CR using a TEI<x> Work Item code, the code(s) for the Work Item(s) which introduced that feature shall be used, plus the appropriate TEI<x> code for the first Release in which the CR is introduced.
If
- it is clear that the modification(s) can be completed within one TSG cycle, and
- the normal stage 1, 2, 3 sequence of CRs does not require one additional meeting cycle in each affected TSG,
then a TEI code may be used. TEI codes shall not be used where the development of modification(s) and interactions with other WGs are likely to prolong the outcome for a period of time greater than this; in such cases, a new specific Work Item shall be created instead.
For smaller features that are handled with Category B and/or Category C CRs within one TSG cycle, a provisional Work Item code shall be used before the CR(s) and the companion WID are submitted for approval to the TSG.
Notwithstanding the provisions of clause 4.10.2, TEI<x> is also to be used in a Category F and any related Category A CR(s) which add to or modify TR/TS content introduced in a Release prior to <x> and where no appropriate Release <x> Work Item exists. In this case the code(s) for the Work Item(s) which introduced the relevant TR/TS content shall be used, plus the appropriate TEI<x> code for the first Release in which the CR is introduced. The same TEI<x> shall be used in all mirror (i.e. Category A) CRs.
Example: TR/TS content is introduced into TS 23.456 under the Release 13 Work Item ABCD by means of a Rel-13 CR. Much later, an error is identified in the TR/TS content introduced by that Rel-13 CR which of course appears in the current Release 13 version of 23.456.
According to the provisions of clause 4.10.0, a category F CR would be introduced into the current Release 13 version tagged with Work Item ABCD, together with category A (mirror) CRs to the Release 14, 15, etc versions of 23.456, each also tagged with code ABCD.
However, it is felt that the seriousness of the error does not warrant taking the correction all the way back to Release 13, and so the category F CR is instead written to the current Release 15 version of 23.456. This is tagged with the Work Item codes ABCD and TEI15. Category A CRs are written to the Release 16, etc versions of 23.456, and these are also tagged with Work Item codes ABCD and TEI15.
NOTE : The order in which multiple Work Item codes appear on a CR cover sheet is not significant. (Thus in the foregoing example, the CRs could equally well show "ABCD, TEI15" or "TEI15, ABCD".)
The use of a TEI Work Item code alone should be avoided whenever possible, and any use of a TEI Work Item code should be considered very carefully.
For the other types of modification, the provisions of clause 6.3 apply. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.3 Start and continuation of the work and responsibilities | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.3.1 General | An early task when elaborating a Work Item is to identify the tasks related to the WI and to allocate them to the TSGs and TSG Sub-Groups.
In most cases the tasks from a WI can be split immediately into the following areas:
- Service requirements
- System/Architectural requirements and implications
- Protocol specifications
Service requirements:
The responsibility of the service requirements can usually be allocated immediately at the creation/adoption of the WI. Occasionally another Group may be given responsibility for the service requirements. In any case, however, it should be a single group and one that reports directly to the TSG.
System/Architectural requirements and implications:
In addition, the responsibility for system/architectural requirements should be allocated immediately, even though the implications and requirements normally will be seen only after the study on service/system requirements have been initiated. The responsibility for the system/architectural requirements shall be given to a single body to guarantee the consistency of the adopted solution.
The choice of group should not pre-determine the technical choices and in many cases, the responsibility for system and architectural requirement study needs a widening of the competency and a readiness to look at a variety of technical aspects. This can be obtained either by drawing the attraction of the suitable experts (e.g., by setting special meetings or clear meeting dates) or by the organization of joint meetings.
TSG SA shall maintain the overall consistency of the system architecture despite the numerous modifications due to various Work Items. TSG SA, shall ensure the co-ordination of the development of general architecture concepts and their applications to individual Work Items, and should thus also draw attention and expertise from other Groups.
Protocol specifications:
The responsibility for the elaboration of the protocol specifications cannot, in most cases, be allocated at the early stages since it depends on the technical implementation choices and hence on the results of the study of the service/system requirements as well as on the architectural conclusions.
The identification of new protocols to be specified and/or existing protocols to be enhanced shall be derived from the system/architectural requirements. In general, modifications of existing protocols shall be done by the TSG WG in charge of the protocol in question, whilst the responsibility for development of new protocols shall be allocated by the TSG based on proposals from the TSG WG on system/architecture. Then, whether the actual work is done in the TSG WG itself or in an ad hoc subgroup thereof is at the discretion of that TSG WG. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.3.2 Role of the work item rapporteur | Every Work Item shall have a rapporteur. The rapporteur should be selected from regular attendees of the primary responsible Group and shall be selected from supporting companies. The role of the rapporteur is to:
- Monitor the progress of the work in all WGs for the WI.
- Report to the responsible WG and produce a report to the WG plenary on progress.
- Provide feedback to allow the work plan to be updated.
- Keep the WI sheet up-to-date.
- Identify the completion of the WI.
NOTE: Updates of WI sheets require approval by the responsible WG/TSG. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.4 Realization of Work Items | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.4.1 Planning and categorization of the deliverables (and control thereof) | Planning:
An initial time plan should be set up at an early point. As a basis, the time plan should include at least the following points:
1. Presentation for principle agreement of the service requirements;
2. Presentation for principle agreement of the architectural/system implications and requirements;
3. Presentation for information of the drafts of all needed deliverables,
4. Presentation for approval of all needed deliverables.
The time plan shall include realistically achievable dates for each step.
The WI Status List shall also contain information about existing and planned permanent and semi-permanent documents related to the WI, e.g. future specifications as well as interim/temporary requirements "specifications", including the responsible Group, the rapporteur, the state of the documents, expected completion dates, etc.
Categorization:
Before the substantial work on a Work Item starts, the WI shall be examined in the light of its technical and commercial dependency with respect to the existing specifications as well as with respect to other Work Items. Aspects that shall be considered and settled at an early stage are:
- Required versus acceptable time scales;
- Whether the WI has an impact on User Equipment or not;
- Whether the WI has an architectural impact or not;
- To which degree the WI needs to specify (and hence how much can be left "open", to speed up the work);
- Whether the WI can be technically and/or commercially combined/grouped with other WIs;
Unless the above aspects are sorted out at the beginning of (or prior to) the work, the risk of getting inefficient and non-optimal specifications increases and the control of the work becomes difficult and unmanageable. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.4.2 Choice of deliverables | The SI will be realized as a new Technical Report ("feasibility study report").
The WI will be realized as new specifications and/or amendments to existing specifications; the exact structure lies with the individual TSG Sub-Groups and the TSG. Typically, a new feature may result in at least three completely new specifications (stages 1, 2 and 3) but may also cause amendments to the major protocol specifications. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.4.3 Contents of deliverables | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.4.3.1 Service requirements | This task, allocated and controlled according to the provisions above, consists in describing in details the aim of the Work Item, as seen by those for which a service is provided, e.g. end users, operators, service providers, etc.
In many cases it is desirable that, prior to the actual service requirements specification being produced, an initial combined service and system/architectural requirements and considerations document is produced, involving both service oriented and implementation expertise. In particular when an ad hoc task force is charged with performing a study on a certain WI (aspect) such a starting point document should be produced and then used as a basis for the TSG SGs when carrying out the detailed work on service requirements/descriptions and technical realization specifications. Such setting-the-basis documents should generally be kept for some time after the actual work on the detailed specifications has progressed to a mature level (mainly for the purpose of easing the understanding and to shorten the interaction and negotiation period between service requirements and system/architectural and technical restrictions).
Such 'setting-the-basis' document can also be used to describe the project management of a Work Item (to collect all prepared but not yet approved CRs related to the WI in question).
It may be appropriate to perform the above work in the context of a Study Item, prior to embarking on concrete specification work. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.4.3.2 Technical realization specifications | These cover both the overall architectural and interface specific detailed specifications. The architectural implications and requirements need to be identified at a very early stage, for the purpose of knowing which parts of the standard (and hence of the system) are affected by a WI, and for the purpose of supporting the identification of cross-WI similarities (and hence more overall efficient solutions).
The overall co-ordination of the architectural/system requirements is with a single group as stated above, whilst the ensuing detailed protocol definitions and specifications may be distributed over several groups (according to their scope). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.4.3.3 Test specifications | Changes to the core specifications may have impact on the test specifications. The corresponding changes to test specifications should be approved before publication the new core specifications. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.4.4 Early implementation | The responsible TSG may decide that a particular Work Item is a candidate for "early implementation". If a feature is a candidate for early implementation this shall be indicated in the 3GPP work plan.
Where a feature is a candidate for early implementation the deliverables shall include an early implementation Technical Report. The Technical Report shall give guidance on how to perform early implementation of a Work Item. This report shall not define any new technical requirements. It is there to help implementers identify which parts of the specifications are relevant to the Work Item and how they should be handled when early implementation is performed.
The early implementation Technical Report shall be identified in the list of impacted documents in the WID. The early implementation Technical Report is part of the same release as the feature to which is relates.
Where a single early implementation feature consists of several Work Items then the number of different TRs should be minimised. The aim shall be for a single report to be written for the appropriate highest level Work Item (typically the feature level). However, flexibility should be left to take account of different ways Work Items may be structured
Work on the early implementation Technical Report shall begin with the identification of the requirements for early implementation.
The contents of the early implementation Technical Report shall be developed in parallel to the overall progress on standardisation of the Work Item. The responsible Working Groups shall keep the report up to date โ particularly the clauses "specification impacts" and "Early Implementation Status" which must be completed before finalisation of the WI and maintained if they are subsequently impacted by any essential corrections. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 6.4.5 Late completion | If a Feature cannot be completed by the freeze date for a Release, two options are available:
1) If the functionality covered by the late-running work item is considered by the TSG not to be vital to the overall Feature, it may be abandoned, or form part of a later Release. It may be necessary to raise CRs to remove modifications from specifications which have already been implemented, so as not to leave unworking stubs of functionality and to ensure that stages 1, 2 and 3 are harmonized.
2) If the foreseen likely overrun is thought to be only a matter of a few months โ generally no more than two TSG plenary meeting cycles โ the responsible WG may raise an "exception sheet" to request a delay in completion until the next or next-but-one TSG meeting. In this case, the responsible WG undertakes to give high priority to completing the work within that time frame, while recognizing that progress can only be made on the basis of contributions to the work.
In the first case, where the delayed work is moved to a later Release, the responsible WG shall make appropriate changes to the 3GPP work plan.
In the second case, the exception sheet should contain enough information to enable the TSG to make a reasoned assessment of the case, and to accept or reject the proposal. |
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 50
Size of downloaded dataset files:
214 MB
Size of the auto-converted Parquet files:
214 MB
Number of rows:
465,224