Content for TR 21.900 Word version: 18.1.0
9 Meeting contribution document types and status values
9.1 Terminology
9.2 TDoc status values
$ Change history
9 Meeting contribution document types and status values p. 39
9.1 Terminology p. 39
Written contributions to 3GPP meetings are called "TDocs".
Each TDoc shall be one of the following types:
| TDoc type | Remarks |
|---|---|
| agenda | Meeting agendas, including those showing allocation of TDocs to agenda items, also timing schedules |
| Work Plan | Ordered list of work items |
| LS in | Liaison Statement, received from some other 3GPP group or an external body |
| LS out | Liaison Statement issued by a group and directed to one or more other 3GPP groups or external bodies. |
| pCR | Pseudo-Change-Request: 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". |
| draftCR | Similar to a Change Request, but unnumbered; proposes new or revised text for a TS or TR already under change control. May ultimately be revised into a regular Change Request. |
| CR | A formal proposal to make changes to a TS or TR which is under change control - i.e. which has a version number with the first field greater than 2 (see clause 4.0A). |
| CR Pack | One or more Change Requests which have been agreed (or endorsed) at working group level and are being presented as a package to TSG for approval. |
| ToR | Terms of reference for a TSG or working group. |
| WID new | Work item description for a new work item - i.e. one not already approved at TSG level. |
| WID revised | Proposes changes to an already TSG-approved Work item description. |
| SID new | As "WID new", where the work item is of type "study". |
| SID revised | As "WID revised", where the work item is of type "study". |
| WI status report | Rapporteur's report (reviewed by the lead WG) of the current state of completion of a work item (degree of completion, target date, contentious issues, …). |
| WI exception request | Request to TSG to permit an overrun in the schedule for the completion of a work item. |
| TS or TR cover | Stand-alone cover sheet for a draft TS or TR being presented (normally at TSG level). Typically used in conjunction with a "draft TS" or "draft TR" type where the actual draft TS or TR and its cover are not included in the same TDoc. |
| draft TS | A complete TS, still in draft state, being presented either for information or approval at TSG level. May also be used at WG level. At TSG level, normally includes a separate "TS or TR cover" indicating the state of development of that TS; if the cover sheet is not included, it can be provided in a separate TDoc of type "TS or TR cover". |
| draft TR | As "draft TS" but pertaining to a TR rather than a TS. |
| report | Any report (other than "WI status report", see above). Typically documents the proceedings of a TSG or WG, or a subgroup thereof. |
| discussion | A TDoc which is intended to be discussed. |
| response |
A TDoc which has been prepared to provide support for, or a counter argument to, another TDoc.
Note:
This type is pecular to one particular working group (RAN3). |
| other | Any other kind of TDoc, for which none of the above types is appropriate. |
9.2 TDoc status values p. 41
Each TDoc having a formal allocated TDoc number has an associated status chosen from Table 9.2-1 below.
| Status value | Meaning | Used for TDocs of type … |
|---|---|---|
| - | Retained for compatibility with legacy TDocs. | None |
| reserved |
TDoc number allocated, document not yet available. If this status remains at the end of the meeting, it will be reported in the minutes as "not available".
Note:
It is not uncommon for revised TDocs to be agreed or approved in principle prior to their becoming available, in which case the appropriate status is set against the TDoc immediately. 3GU keeps a separate field indicating whether the TDoc is, in fact, available. If a TDoc remains unavailable at the end of the meeting, or at the end of any post-meeting decision period, then the Secretary will revert its status to "reserved", and the meeting report will indicate it as being "not available".
|
Any |
| available | TDoc available, not yet treated. If this status remains at the end of the meeting, it will be reported in the minutes as "not treated". | Any |
| approved | Favourable conclusion; the group in question (TSG or WG) has the final say. | Any |
| agreed | Favourable conclusion; the decision has to be confirmed by a higher body (e.g. WG decision has to be confirmed by TSG). | Any |
| noted | TDoc has been presented, no specific action results. | Any except for CRs, where interpretation is ambiguous. |
| postponed | TDoc has been presented but no final decision could be reached; subject is likely to be raised at a subsequent meeting. | Any |
| withdrawn | Prior to discussion of the TDoc, its author has decided not to present it. | Any |
| treated | TDoc has been presented, but no other status is appropriate (for example, in the case of a CR pack, some CRs in it were revised, some postponed, and some reissued - none was approved). | Any, but principally intended for CR packs. |
| revised | TDoc will be modified and presented in a new TDoc. | Any |
| partially approved | Used for CR packs only. One or more CRs contained in the TDoc has been approved at TSG level; other CRs may have status revised, postponed, not pursued, etc. | CR packs |
| endorsed | The group believes that the TDoc is valid but has not reached a conclusion of "agreed" or "approved". May be used as a WG status where alternative solutions to a technical matter have been identified, and the choice between them is being left to the TSG. Also by a WG when asked to give an opinion on a matter (typically a WID) for which another WG is responsible. |
Any, but principally intended for
|
| merged | The TDoc is combined with one or more others and presented in a new, composite TDoc. | Any, but principally intended for pCRs, draftCRs and CRs. |
| reissued | Only used for the status of CRs in a CR Pack. Indicates that the CR appears unchanged in a different CR Pack created because one or more other CRs in the original pack is revised or withdrawn. | CRs within CR packs only. |
| replied to | Used for incoming Liaisons only. Indicates that an outgoing Liaison has been prepared in reply to this incoming Liaison. | LS in |
| conditionally agreed | Agreed, but conditional on a decision taken on a different TDoc, possibly in a different group. | Any, but principally intended for CRs. |
| conditionally approved | Approved, but conditional on a decision taken on a different TDoc, possibly in a different group. | Any, but principally intended for CRs (typically in a CR pack at TSG level) |
| not concluded | Discussion has started but has not finished. Typically used as a temporary status between the end of a meeting any post-meeting review or agreement/approval (for example, by email). | Any |
| not pursued | No further action to be taken. Replacement for "rejected", without the emotive implications sometimes inferred for "rejected". | Any |
| rejected | Retained for compatibility with legacy TDocs. Meaning identical to "not pursued". May be used by groups which are not sensitive to this value. | Any |
$ Change history p. 44
