hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | 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... |
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.
- Fo... |
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 perf... |
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 a... |
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, cle... |
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 sh... |
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 terminolo... |
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.... |
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 suc... |
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 practic... |
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 theref... |
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
(gene... |
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.... |
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 us... |
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... |
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-c... |
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 be... |
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 int... |
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 ... |
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... |
e7022876aaebc1074115c0f4962825be | 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, sp... |
e7022876aaebc1074115c0f4962825be | 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 modi... |
e7022876aaebc1074115c0f4962825be | 21.900 | 3 General responsibilities of the Support Team
| |
e7022876aaebc1074115c0f4962825be | 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 subgr... |
e7022876aaebc1074115c0f4962825be | 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, regist... |
e7022876aaebc1074115c0f4962825be | 21.900 | 4 Handling of Specifications
| |
e7022876aaebc1074115c0f4962825be | 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 strictl... |
e7022876aaebc1074115c0f4962825be | 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 ... |
e7022876aaebc1074115c0f4962825be | 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 c... |
e7022876aaebc1074115c0f4962825be | 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:
- Revie... |
e7022876aaebc1074115c0f4962825be | 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 secondar... |
e7022876aaebc1074115c0f4962825be | 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.
- I... |
e7022876aaebc1074115c0f4962825be | 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... |
e7022876aaebc1074115c0f4962825be | 21.900 | 4.6 Change Request regime
| |
e7022876aaebc1074115c0f4962825be | 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... |
e7022876aaebc1074115c0f4962825be | 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... |
e7022876aaebc1074115c0f4962825be | 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 ca... |
e7022876aaebc1074115c0f4962825be | 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 prese... |
e7022876aaebc1074115c0f4962825be | 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.
|
e7022876aaebc1074115c0f4962825be | 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 techn... |
e7022876aaebc1074115c0f4962825be | 21.900 | 4.10 Release control
| |
e7022876aaebc1074115c0f4962825be | 21.900 | 4.10.1 Creation of a new Release version of a specification
| |
e7022876aaebc1074115c0f4962825be | 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.
|
e7022876aaebc1074115c0f4962825be | 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 de... |
e7022876aaebc1074115c0f4962825be | 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 re... |
e7022876aaebc1074115c0f4962825be | 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.
|
e7022876aaebc1074115c0f4962825be | 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... |
e7022876aaebc1074115c0f4962825be | 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, consist... |
e7022876aaebc1074115c0f4962825be | 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 t... |
e7022876aaebc1074115c0f4962825be | 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... |
e7022876aaebc1074115c0f4962825be | 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 ... |
e7022876aaebc1074115c0f4962825be | 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 ... |
e7022876aaebc1074115c0f4962825be | 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 conta... |
e7022876aaebc1074115c0f4962825be | 21.900 | 5 Availability and distribution of specifications
| |
e7022876aaebc1074115c0f4962825be | 21.900 | 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... |
e7022876aaebc1074115c0f4962825be | 21.900 | 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 ... |
e7022876aaebc1074115c0f4962825be | 21.900 | 6 Work Items
| |
e7022876aaebc1074115c0f4962825be | 21.900 | 6.0 Introduction
| |
e7022876aaebc1074115c0f4962825be | 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 activi... |
e7022876aaebc1074115c0f4962825be | 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 Te... |
e7022876aaebc1074115c0f4962825be | 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 dec... |
e7022876aaebc1074115c0f4962825be | 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 Aspec... |
e7022876aaebc1074115c0f4962825be | 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 ... |
e7022876aaebc1074115c0f4962825be | 21.900 | 6.3 Start and continuation of the work and responsibilities
| |
e7022876aaebc1074115c0f4962825be | 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 speci... |
e7022876aaebc1074115c0f4962825be | 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 r... |
e7022876aaebc1074115c0f4962825be | 21.900 | 6.4 Realization of Work Items
| |
e7022876aaebc1074115c0f4962825be | 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. Presen... |
e7022876aaebc1074115c0f4962825be | 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 speci... |
e7022876aaebc1074115c0f4962825be | 21.900 | 6.4.3 Contents of deliverables
| |
e7022876aaebc1074115c0f4962825be | 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 specificat... |
e7022876aaebc1074115c0f4962825be | 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... |
e7022876aaebc1074115c0f4962825be | 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.
|
e7022876aaebc1074115c0f4962825be | 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 Techni... |
e7022876aaebc1074115c0f4962825be | 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 m... |
e7022876aaebc1074115c0f4962825be | 21.900 | 6.5 Status tracking of Work Items
| The status of each Work Item shall be tracked and recorded throughout its life in the 3GPP work plan. The status may take the following values:
Table 6.5a: Status values of Work Item
Status
Description
Indication in work plan
Not TSG approved
This is a draft Work Item which has not yet been approved by a TSG
The... |
e7022876aaebc1074115c0f4962825be | 21.900 | 6.6 Work Item model
| The model described below can be thought of as a reference model for structuring the work. It is not the intention to rigorously enforce the usage of the model on all ongoing work, but merely to use it as the common reference model across the TSGs and to structure future work.
The description below uses TSG SA as an i... |
e7022876aaebc1074115c0f4962825be | 21.900 | 6.7 Guidance for Appointed Duties
| As part of progressing a work item or other business of 3GPP, delegates may be appointed to roles such as rapporteur, moderator, editor, etc. While operating in these roles, delegates are expected to carry out their assigned duties with impartiality and in the interests of 3GPP. While company support letters are not re... |
e7022876aaebc1074115c0f4962825be | 21.900 | 7 Management documents and tools
| |
e7022876aaebc1074115c0f4962825be | 21.900 | 7.0 Overview
| This clause summarizes and lists the various permanent or semi-permanent documents (and means of documenting).
All these documents/tools are within the responsibilities of the Support Team and or TSG SA.
|
e7022876aaebc1074115c0f4962825be | 21.900 | 7.1 Status List of Specifications
| This list (data base) contains information about all 3GPP specifications, in terms of specification number, title, latest version, rapporteur and other details. The current list shall be annexed to every TSG SA meeting report.
|
e7022876aaebc1074115c0f4962825be | 21.900 | 7.2 Work Item Status List
| This data base contains information about all 3GPP Work Items, in terms of identified future specifications, identified specifications to be amended, supplementary/temporary documentation, expected/planned completion dates and intermediary milestones, and other management information related to specifications, responsi... |
e7022876aaebc1074115c0f4962825be | 21.900 | 7.3 Change Request data base
| The Change Request data base records all CRs to specifications.
|
e7022876aaebc1074115c0f4962825be | 21.900 | 7.4 Membership data bases
| The members data base contains information of all delegates in the 3GPP TSGs.
|
e7022876aaebc1074115c0f4962825be | 21.900 | 7.5 Electronic tools used/preferred
| For the various types of documents and parts of documents of 3GPP, a minimum variety of word processors etc. should be used. Those identified in 3GPP TR 21.801 [1] are permitted.
|
e7022876aaebc1074115c0f4962825be | 21.900 | 7.6 WEB and FTP services
| The 3GPP website (https://www.3gpp.org) and portal (https://portal.3gpp.org) provide up-to-date information on specification work, such as: meeting calendars, meeting minutes, meeting documents and latest specifications. FTP links to file server areas of each TSG and WG can be found via the 3GPP web pages.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.