Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TR 21.900  Word version:  16.3.0

Top   Top   None   None   Next
0…   4…   4.4…   5…   6…   7…   8…   9…

 

0  IntroductionWord‑p. 5
In order to ensure correctness and consistency of the specifications (i.e., technical specifications and technical reports) under responsibility of the Technical Specification Groups (TSG) of the 3rd Generation Partnership Project (3GPP), clear, manageable and efficient mechanisms are necessary to handle version control, change control, document updating, distribution and management.
Also, the fact that the specifications are/will be implemented by industry almost in parallel with the writing of them requires strict and fast procedures for handling of changes to the specifications.
It is very important that the changes that are brought into the standard, from the past, at present and in the future, are well documented and controlled, so that technical consistency and backwards tracing are ensured.
The 3GPP TSGs, and their sub-groups together with the Support Team are responsible for the technical content and consistency of the specifications whilst the Support Team alone is responsible for the proper management of the entire documentation, including specifications, meeting documents, administrative information and information exchange with other bodies.
Up

1  ScopeWord‑p. 6
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.
Up

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]  TR 21.801   "Specification drafting rules".
[2]  TR 21.905   "Vocabulary for 3GPP Specifications".
[3]  TS 21.101   "Technical Specifications and Technical Reports for a UTRAN-based 3GPP system".
[4]  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]  TS 29.501   "5G System; Principles and Guidelines for Services Definition; Stage 3".
[7]  RFC 3629:  "UTF-8, a transformation format of ISO 10646".
Up

2  Definitions and abbreviations

For the purposes of the present document, the following terms and those in TR 21.905 apply.
building block:
sub-division of a feature, representing a coherent set of technical functionality which would generally be expected to reside in a single system element.
change control:
procedure whereby proposed modifications to a specification are presented for approval to the TSG as formal Change Requests.
closed:
specification status in which no changes of any kind to the specification are permitted.
Change Request (CR):
formal proposal presented on a standard form to modify a specification which is under change control.
draft:
specification status prior to change control, in which changes may be made without formal Change Requests.
early implementation:
implementation of a particular feature on a platform of a release earlier than the release that contains the feature.
feature:
new or substantially enhanced functionality which represents added value to the existing system.
frozen:
specification status in which only essential corrections are permitted.
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.
specification:
generic term standing for Technical Specification and Technical Report.
Study Item:
type of Work Item which will conduct feasibility studies and will result in a Technical Report
TSG:
Technical Specification Group.
TSG change control:
specification status in which the Technical Specification Group is responsible for approval of Change Requests.
TSG Sub-Group:
Working Group or subgroup of a Working Group or of a Sub-Group.
Working Group (WG):
official subgroup of a TSG reporting to that TSG.
WG Change Control:
specification status in which the Working Group is responsible for agreeing Change Requests for submission to the TSG for approval.
version:
unique identifier in the form x.y.z for a specification at a given point in time.
  • Example: version 3.12.3.
withdrawn:
specification status in which the given version of the specification no longer belongs to the appropriate set of valid specifications.
Work Item (WI):
description of an enhancement to a technical area, which may be categorized as Study Item, Feature, Building Block or Work Task.
Work Item description (WID):
description of a Work Item in a standard Work Item Description sheet.
work task:
sub-division of a building block, representing a self-contained, well-scoped and well-scheduled item of work.
Up

3  General responsibilities of the Support TeamWord‑p. 7

3.1  Specifications, meetings and liaisons

The Support Team is responsible for the management of the work of the TSGs. This includes editorship and management of specifications once they have been put under TSG change control. It also includes preparation of and support for the meetings (including meeting reports) of the TSGs and their Working Groups, and subgroups in descending priority.
It furthermore includes liaison with other bodies and relevant groups and institutions.

3.2  Registration of code pointsWord‑p. 8
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.
Up


Up   Top   ToC