process of specifications

Here, we will explain the general flow of 3GPP standard development.

1. Work plan
   • A plan for what kind of item (Work Item) will be standardized in what kind of schedule in the future. See work plan for details.
2. Work Item
   • For the item decided in the Work Plan, show the background that this item was needed, what is needed to realize it, and what to decide. See work item for details.
3. Standard development in each Work Group
   1. meeting
      • We will meet for each Work Item to formulate the standard. Normally, meetings are held in a 3-month cycle, but if the schedule shown in the Work Plan is not met, additional meetings may be held as ad hoc meetings. In meeting, we prepare a document called tdoc in advance and discuss based on it. Documents discussed during the meeting will be tentatively placed in Meetings_3GPP_SYNC. (After the meeting period, you will be moved to the directory managed by the meeting number for each Working Group)
   2. Standard formulation
      • We will formulate standards based on the tdoc prepared in advance. The contents agreed within the meeting members are reflected in the CR (Change request). (In rare cases, the details may be written only in the tdoc without being reflected in the standard document. For this reason, if there is content that is difficult to read from the standard document alone, refer to the tdoc for the detailed content. In some cases, it may be stated. At least, it may be possible to understand the flow of standardization, so it is possible to make inferences based on that.)
   3. Create CR(Change Request)
      • We will create a document to reflect the contents agreed at the meeting in the standard. This document will be reflected in the standard by being approved by the Technical specification group.
   4. Report(Only some Working Groups)
      • A document is created that summarizes the progress for the Work Item for each meeting for each Working Group. This document is not always created and seems to vary from technical specification group to technical specification group.
4. CR approval
   • Performs CR approval work submitted by each Working Group belonging to each Technical specification group. If approved here, it will be reflected in the standard.
5. Spec Release
   • The CR approved for each Technical specification group is reflected in the standard and released to the Web. Basically, the meeting is a 3-month cycle, so the standard will be updated in a 3-month cycle. To find a published standard, see How to find a standard.

Reference ：ex. TS 23.401

※If you do not know the organizational structure such as Group that appears here, see Structure of specification.

Next, Will describe the Work Plan.