spec_id string | spec_number string | spec_type string | title string | release string | clause string | section_title string | parent_clause string | depth int32 | body string | body_chars int32 | document_order int32 | images images list | image_hashes list |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 1 | 1 Scope | 2 | ## 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 me... | 767 | 0 | [] | ||
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.0 | Numbering scheme | 4 | 2 | ## 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... | 19,758 | 1 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.0A | Version nomenclature | 4 | 2 | ## 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**
Table 3 shows the estimated degree of stability to be used as a guideline for... | 2,738 | 2 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.0B | Releases | 4 | 2 | ## 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.
Spe... | 4,212 | 3 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.10.1 | Creation of a new Release version of a specification | 4.10 | 3 | ### 4.10.1 Creation of a new Release version of a specification
##### 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 a... | 2,411 | 4 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.10.2 | Mirror Change Requests | 4.10 | 3 | ### 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 ver... | 916 | 5 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.10.3.2 | New features | 4.10.3 | 4 | #### 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.
**Table 1**
| CR category<br>(see t... | 2,057 | 6 | [
"7e1c9b51e067a48cd0fcc9748d8bd8d8"
] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.10.3.4 | Introduction of features into Releases | 4.10.3 | 4 | #### 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](../sections/s06_work_items.md)) shall be estimated by the resp... | 2,784 | 7 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.10.3 | Release mechanisms | 4.10 | 3 | ### 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 docum... | 2,150 | 8 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.10 | Release control | 4 | 2 | ## 4.10 Release control
| 24 | 9 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.1.1 | General | 4.1 | 3 | ### 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... | 3,772 | 10 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.1.2 | Role of the specification rapporteur | 4.1 | 3 | ### 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 contro... | 691 | 11 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.1 | Overview | 4 | 2 | ## 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 capabi... | 709 | 12 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.2 | Characteristics of a specification | 4 | 2 | ## 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 an... | 911 | 13 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.3 | Characteristics of a major version of a specification | 4 | 2 | ## 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... | 842 | 14 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.4 | Characteristics of a version of a specification | 4 | 2 | ## 4.4 Characteristics of a version of a specification
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.
**Table 1**
| | ... | 4,015 | 15 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.5 | (void) | 4 | 2 | ## 4.5 (void)
| 14 | 16 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.6.1 | Change Requests | 4.6 | 3 | ### 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 o... | 2,663 | 17 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.6.2 | Change Request forms | 4.6 | 3 | ### 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 re... | 7,476 | 18 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.6.3 | Contents of Change Requests | 4.6 | 3 | ### 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 w... | 1,171 | 19 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.6.4 | Handling of the Change Requests | 4.6 | 3 | ### 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... | 6,653 | 20 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.6 | Change Request regime | 4 | 2 | ## 4.6 Change Request regime
| 29 | 21 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.8 | "Closing" of specifications | 4 | 2 | ## 4.8 "Closing" of specifications
A TSG may decide that a specification will no longer be maintained. That is, no further Change Requests should be considered. The specification remains available, but no further Change Requests should be produced, even corrective ones to align with the equivalent specification of a s... | 429 | 22 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.9 | "Withdrawing" of specifications | 4 | 2 | ## 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 shal... | 574 | 23 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | s04_9b_2_diligent_assessment | 4.9B.2 Diligent assessment | 3 | ### 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 sha... | 1,727 | 24 | [] | ||
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4.9B | Procedure for withdrawing of specifications and functionality | 4 | 2 | ## 4.9B Procedure for withdrawing of specifications and functionality
#### 4.9B.1 (void)
#### 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... | 951 | 25 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 4 | Handling of Specifications | 1 | # 4 Handling of Specifications
### 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... | 445 | 26 | [] | ||
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 5.1 | General | 5 | 2 | ## 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 ... | 1,386 | 27 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 5.2 | Choice of availability and distribution of stage 3 specification files | 5 | 2 | ## 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... | 519 | 28 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 5 | Availability and distribution of specifications | 1 | # 5 Availability and distribution of specifications
| 52 | 29 | [] | ||
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.0.2 | How to manage a project? | 6.0 | 3 | ### 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 ... | 5,608 | 30 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.0.3 | Types of modification to specifications | 6.0 | 3 | ### 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 service... | 1,455 | 31 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.1 | Creation of a Work Item | 6 | 2 | ## 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 responsib... | 1,185 | 32 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.2 | Types of Work Item | 6 | 2 | ## 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... | 4,008 | 33 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.3.1 | General | 6.3 | 3 | ### 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... | 2,786 | 34 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.3.2 | Role of the work item rapporteur | 6.3 | 3 | ### 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.
- R... | 598 | 35 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.3 | Start and continuation of the work and responsibilities | 6 | 2 | ## 6.3 Start and continuation of the work and responsibilities
| 63 | 36 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.4.1 | Planning and categorization of the deliverables (and control thereof) | 6.4 | 3 | ### 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 prin... | 1,814 | 37 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.4.2 | Choice of deliverables | 6.4 | 3 | ### 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 a... | 452 | 38 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.4.3.1 | Service requirements | 6.4.3 | 4 | #### 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 act... | 1,514 | 39 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.4.3.2 | Technical realization specifications | 6.4.3 | 4 | #### 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 ... | 705 | 40 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.4.3.3 | Test specifications | 6.4.3 | 4 | #### 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.
| 229 | 41 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.4.3 | Contents of deliverables | 6.4 | 3 | ### 6.4.3 Contents of deliverables
| 35 | 42 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.4.4 | Early implementation | 6.4 | 3 | ### 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 includ... | 1,834 | 43 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.4.5 | Late completion | 6.4 | 3 | ### 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 neces... | 1,317 | 44 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.4 | Realization of Work Items | 6 | 2 | ## 6.4 Realization of Work Items
| 33 | 45 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.5 | Status tracking of Work Items | 6 | 2 | ## 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**
**Table 1**
| <b>Status</b> | <b>Description</b> ... | 2,922 | 46 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6.6 | Work Item model | 6 | 2 | ## 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 b... | 4,304 | 47 | [
"1ad662a678c4f002de911d403f00de8e"
] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 6 | Work Items | 1 | # 6 Work Items
### 6.0 Introduction
#### 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 wh... | 412 | 48 | [] | ||
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 7.1 | Status List of Specifications | 7 | 2 | ## 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.
| 265 | 49 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 7.2 | Work Item Status List | 7 | 2 | ## 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 relat... | 397 | 50 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 7.3 | Change Request data base | 7 | 2 | ## 7.3 Change Request data base
The Change Request data base records all CRs to specifications.
| 97 | 51 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 7.4 | Membership data bases | 7 | 2 | ## 7.4 Membership data bases
The members data base contains information of all delegates in the 3GPP TSGs.
| 108 | 52 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 7.5 | Electronic tools used/preferred | 7 | 2 | ## 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]<!-- xref:unresolved 21801 --> are permitted.
| 249 | 53 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 7.6 | WEB and FTP services | 7 | 2 | ## 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... | 341 | 54 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 7.7 | E-mail reflectors | 7 | 2 | ## 7.7 E-mail reflectors
TSGs, WGs and SWGs have their own e-mail lists. There are also several additional lists per topic. Further information can be found on 3GPP web pages.
| 177 | 55 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 7 | Management documents and tools | 1 | # 7 Management documents and tools
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.
| 241 | 56 | [] | ||
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 8.1 | E-mail drafting phase | 8 | 2 | ## 8.1 E-mail drafting phase
An e-mail drafting session can be launched, either on a dedicated exploder list as a cybermeeting or as an informal discussion between interested delegates. Objectives can extend from debating an existing contribution, a Liaison Statement or a Change Request to progressing the service requ... | 829 | 57 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 8.2 | E-mail decision declaration | 8 | 2 | ## 8.2 E-mail decision declaration
Authority for an e-mail decision to take place should usually be agreed at plenary meeting. If this is not possible, there shall be a clear notification (i.e. status report) indicating that there will be an e-mail decision. This notification shall be sent on the main mailing lists in... | 660 | 58 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 8.3 | Status reporting | 8 | 2 | ## 8.3 Status reporting
During the e-mail decision period, there shall be a clear message stating what the status of each open item is. It is recommended to have a weekly summary of the status of all items, from the previous plenary listing:
- the name of the open item;
- the name of the responsible delegate;
- time ... | 517 | 59 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 8.4 | Decision announcement | 8 | 2 | ## 8.4 Decision announcement
When a decision is made (Agreed, rejected, postponed, ...) a clear notification on what has been agreed shall be sent on the main mailing lists of the relevant groups.
| 198 | 60 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 8.5 | Timing | 8 | 2 | ## 8.5 Timing
E-mail decision procedure should start at the latest 3 weeks before relevant plenary:
- the e-mail decision period is two weeks (one status report required);
- the procedure shall be completed one week before the relevant TSG, WG or SWG plenary, due to practical arrangements.
| 293 | 61 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 8.6 | General | 8 | 2 | ## 8.6 General
- in exceptional cases when the procedure cannot be followed a clear notice from Chair is required;
- e-mails on mailing lists shall contain a subject with meaningful keywords, e.g. SA1 Tdoc xxx on Charging and/or 22xxx-CR012r4;
- if there are no comments during the allowed period, agreement is granted ... | 536 | 62 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 8 | E-mail decisions | 1 | # 8 E-mail decisions
WGs may apply e-mail decision procedures for decisions they are entitled to take, as defined by superior bodies (e.g. on specifications, CRs, Liaison statements, etc.). Each WG may set its rules for making e-mail decisions, however, it is required that:
- the rules are clearly defined and documen... | 529 | 63 | [] | ||
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 9.1 | Terminology | 9 | 2 | ## 9.1 Terminology
Written contributions to 3GPP meetings are called "TDocs".
NOTE: The term "TDoc" is an abbreviation of "Temporary Document" and is a legacy of when such documents were prepared in paper form. Temporary Documents were not intended to be retained after the end of the meeting at which they were discus... | 9,571 | 64 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 9.2 | TDoc status values | 9 | 2 | ## 9.2 TDoc status values
Each TDoc having a formal allocated TDoc number has an associated status chosen from table 9.2-1 below.
**Table 9.2-1: TDoc status values**
# --- Annex A: Change history
**Table 1**
| Status value | Meaning ... | 35,077 | 65 | [] | |
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 9 | Meeting contribution document types and status values | 1 | # 9 Meeting contribution document types and status values
| 58 | 66 | [] | ||
21900 | 21.900 | TR | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specification Group working methods | Rel-18 | 5A | File naming conventions | 3 | ### 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 (s... | 10,971 | 67 | [] |
End of preview. Expand in Data Studio
3GPP Specifications
938 3GPP technical specifications and reports decomposed into self-contained sections with tables and figures inlined. Pre-validation dataset.
Releases: Rel-18, Rel-19
Usage
from datasets import load_dataset
# Load Rel-18 NR radio specs
ds = load_dataset("GSMA/3GPP", "rel-18", split="38_series")
# Get a specific section
section = ds.filter(lambda r: r["spec_id"] == "38331" and r["clause"] == "5.2.1")[0]
print(section["body"]) # self-contained: tables and figures are inlined
# Reconstruct full spec
spec = ds.filter(lambda r: r["spec_id"] == "38331").sort("document_order")
full_text = "\n\n".join(spec["body"])
# Load Rel-19
ds19 = load_dataset("GSMA/3GPP", "rel-19", split="38_series")
Schema
| Column | Type | Description |
|---|---|---|
spec_id |
string | Spec identifier, e.g. 38331 |
spec_number |
string | Dotted form, e.g. 38.331 |
spec_type |
string | TS or TR |
title |
string | Full spec title |
release |
string | Rel-18 or Rel-19 |
clause |
string | Section number, e.g. 5.2.1 |
section_title |
string | Section heading |
parent_clause |
string | Parent section, e.g. 5.2 |
depth |
int32 | Heading depth (1-6) |
body |
string | Self-contained markdown (tables/figures inlined) |
body_chars |
int32 | Character count |
document_order |
int32 | Position within spec |
images |
list[Image] | Images referenced in this section |
image_hashes |
list[string] | MD5 hashes of images |
Original DOCX Files
The original 3GPP Word documents (549 files for Rel-18, 442 files for Rel-19) are available under original/:
original/
rel-18/
rel-19/
Filenames follow the 3GPP convention: {spec_id}-{version}[_{part}].docx.
Large specs may be split across multiple files (e.g., 38101-1-j10_cover.docx,
38101-1-j10_s00-0504.docx).
Download a single file
from huggingface_hub import hf_hub_download
path = hf_hub_download(
"GSMA/3GPP",
"original/rel-18/38331-i00.docx",
repo_type="dataset",
)
License
See 3GPP Legal Matters.
- Downloads last month
- 752