3GPP 21.900 v20.0.0 — the document's own text
9.2 TDoc status values
Taught in 8. How a 3GPP meeting decides, and the word it decides in (How standards actually get made, in depth), 1. Why anybody writes a standard down (How standards actually get made, overview), 6. Two ways of deciding (How standards actually get made, overview), 7. Reading either body's paper trail yourself (How standards actually get made, overview).
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
| 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 - CRs where two or more solutions are proposed,- WIDs belonging to another group. |
| 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 |