3GPP Work Item description - home page

This area of the 3GPP web gives a brief, largely non-technical, description of new Features being incorporated into the next Release of 3GPP Technical Specifications.  The official Work Item Description (held in a dedicated directory)  is maintained by the responsible TSG, and its development schedule and progress can be monitored via the 3GPP Work Plan.  Consult the Work Plan to determine the most up to date Work Item Description document, since the WID may be revised from time to time.

Click here to see the current work programme, top-level tasks (features) only.

Click here to see the current work programme, all tasks.

Click here to see a simple list of Work Items.

Click here to see a list of Features per Release, with summary descriptions and status.

A note on WI codes:   

Each and every Work Item in the 3GPP Work Plan has a unique, numerical, identifier ("Unique ID").  These values are allocated by the Support Team.  They are used for cross referencing and hyperlinking purposes in the 3GPP Specifications Status database and on this web site. 

However, for human readable purposes, and in particular for use on CR coversheets and on Work Item Description sheets, it is more convivial to use alphabetic codes (sometimes referred to as acronyms) which have some relationship to the full title of the WI.  Not all WIs have been allocated these codes.  If you wish to write a CR in the context of a WI for which no alpha code exists, then either (a) ask the Support Team to allocate a code or (b) use the code for the next higher WI in the hierarchy.  All Features and all Study Items - the top level WIs - have alpha codes.

The structure of an alpha code indicates the hierarchical level of the WI:

• Top-level WIs (Features and Study Items) have a single field eg LCS3

• Second-level WIs (Building Blocks) have two fields: the first is the code of its parent Feature (or Study Item); the second is the code unique to that BB eg LCS3-UEpos

• Third-level WIs (Work Tasks) have three fields: the first is the field of the grandparent Feature (or Study Item); the second is the code for the parent BB; the third is the code unique to that WT eg LCS3-UEPos-UTDOA

For the sake of brevity, each field should be kept to no more than seven characters (excluding the separator hyphen) if possible.  Each (composite) code is unique.  If necessary, the technique can be continued to a fourth level or even beyond, but such extension should be avoided if possible.