3GPP CWTS Workshop 03a Freezing of Specs and Releases

3GPP CWTS workshop
Beijing, 28 January 2003

• Click to edit Master text styles
• Second level Presentation 3:
• Third
The level
“freezing” of Specs and Releases
• Fourth level
• Fifth level John M Meredith
3GPP Specifications Manager
ETSI Mobile Competence Centre
1
The 3GPP Release mechanism
• Second level describes the mechanism for handling
This presentation
technical enhancements to the digital telecommunications
• Third level
system defined by the Third Generation Partnership Project.
• Fourth level
In particular, the phased approach embodied in the Release
mechanism is described, hitherto unclear terms are better
• Fifth level
defined, and some procedural recommendations given.
2
What’s in a Release?

• Second level
• Third level
• Fourth level
• Fifth level
3
A 3GPP system definition consists of
all the technical specifications of a
given “Release”.
• Second level
• Third level
• Fourth level
• Fifth level Together, these
specifications define a set of
features provided by the
system.
4
A new Release consists of the features of the old
Release augmented with additional features of the
new Release:
Feature X
Feature Y
• Second level
• Third level Release N+1
• Fourth level
• FifthN level
Release
Feature Z
5
A new Release consists of the features of the old
Release augmented with additional features of the
new Release:

• Second level
• Third level Y
X
• Fourth level
• Fifth level Release N+1
6
Some features may not be ready in time to be
included in the new Release, and are held over till
a later Release:
Feature X
Feature Y
• Second level
• Third level
• Fourth level
• Fifth level
Release N
Feature Z
To Release N+2
7
A “Feature” is defined by
its “Work Item Description”
sheet. It is manifested by a set of
new technical specifications
• Click to edit Masterand
text stylesto existing
changes
• Second level specifications.
• Third level
• Fourth level
• Fifth level
8
Remember that a Feature is defined as:
"new or substantially enhanced functionality which
represents added value to the existing system"
[3GPP TR 21.900].
This definition presumes that Features are defined in a
• Secondnon-technical
commercial, level way. Thus even senior
management may see at a glance the commercial and financial
• Third level
implications of adding, or not adding, a feature to the system.
• Fourth level
• Fifth level
9
Premise 1:
New Features should be named and described in
• Second level
non-technical terms which can be comprehended
• Third
by companylevel
management, so that their commercial
• Fourth
(rather level
than technical) merits can be evaluated.
• Fifth level
10
A Feature can be broken down into “building blocks”, which
can in turn be broken down into “work tasks”. In fact, the
functional decomposition of a Feature into lower level tasks is
rather ad hoc, and depends on the complexity of each
• Second
individual level
Feature.
Third
• the
As levellevel
of break-down increases, the lower levels will be
defined in progressively more technical terms. The number of
• Fourth level
levels of decomposition should be sufficient to allow
• Fifth level
reasonably accurate estimation and progress tracking of the
work. The number of levels should be restricted by this aspect,
and not continued to artificially deep nesting simply because
further breakdown is possible; it is only necessary to go into
sufficient detail to allow a reasonably accurate degree of
project management.
11
Premise 2:
Each feature should be broken down into a
• Second level
sufficient number of levels to enable the work to be
• Third level
achieved. Successively lower levels should be
• Fourth
defined level
in progressively more technical and less
commercial
• Fifth levelterms.
12
The standardization activity is typically arranged
into the well-known three stages.
Defines the service

aspects of a feature (or
part thereof) from the
• Second level end-user's point of view.
Stage 1
• Third level Defines the logical
functionality and
information flows
• Fourth
Stage 2
level amongst the functional
entities involved in
• Fifth level providing the service.
Specifies any necessary

Stage 3 functionality of physical
entities (equipment) and
the detailed protocols of
the signalling between
them.
13
For complex Features, stage 1 may be preceded by a feasibility
study (sometimes called "stage 0") to analyse the market and
potential technical difficulties of a given service or approach.
Sometimes TSGs (notably RAN) create pre-standardization
• Second
"study items" level
which produce reports forming the foundation
for subsequent concrete standardization in "work items".
• Third level
• Fourth level
• Fifth level
14
Stage 1 specifications are normally produced by TSG SA1,
and stage 2 specifications by SA2, though the stage 2 may
need specialist knowledge from other TSGs' working groups.
• Second level
• Third level
• Fourth level
• Fifth level
15
A separate stage 3 specification will be required for each
protocol concerned with providing the service, which may well
impact the whole equipment chain from User Equipment,
• Click
through theto editAccess
Radio Master text tostyles
Network, the Core Network, and
• toSecond
on network level
management interfaces, and to fixed networks.
The service may require new codecs. Depending on the nature
of Third
• the level
Feature, it may only be necessary to change existing
• Fourth level
specifications rather than to create completely new ones. This
is particularly so at stage 3, where the service has to co-exist
• Fifth
with level
all other services. However, this will vary from case to
case.
16
Each feature has the three stages. Stages 1 and 2
usually require the production of new TSs. Stage 3
may also require new TSs but may simply be
implemented by a number of change requests to
existing
• Click protocol TSs.Master text styles
to edit
• Second levelFeature X Stage 1
Stage 2
• Third level Stage 3
• Fourth level
Feature Y Stage 1
• Fifth levelStage 2
Stage 3
Feature Z Stage 1
Stage 2
Stage 3
17
Further stages not originally envisaged by CCITT
are the development of Operations and
Maintenance (O&M) specifications (mainly within
• SA5)
Click andtoof edit Master text(mainly
Test specifications stylesT1,
GERAN3, GERAN4 and GERAN5). Whilst O&M
• specs
Second level
can be developed more or less at the same
Third
• time level
as the stage 3 protocols, it is usually prudent to
wait until the protocols are fairly stable (i.e. field
• tested)
Fourth level
before embarking on detailed test
• specifications.
Fifth level Thus whilst the O&M specs may be
only six months behind the stages 3, the test specs
follow a year or more later.
18
Premise 3:
Wherever possible, each Feature should be broken
• Second level
down into (at least) the following elements:
• Third level
Stage 1;
• Fourth level
Stage 2;
Stage(s) 3;
• Fifth level
O&M aspects;
Test specifications.
19
Development of the TSs and CRs needed to
implement each feature starts with stage 1,
progresses to stage 2, and concludes with stage 3.

• Second level
• Third level
• Fourth
Feature level
X Stage 1
• FifthStage
level2
Stage 3
20
In practice, there is feedback from stage 2 to stage 1
and from stage 3 to stage 2 (and even from stage 3 to
stage 1), so the real progress is more like this:

• Second level
• Third level
• Fourth
Feature level
X Stage 1
• FifthStage
level2
Stage 3
21
Overall progress is estimated and monitored by the
sum of the individual features.
Feature X Stage 1
Stage 2
• ClickStage
to edit
3
Master text styles
• Second level
Feature Y Stage 1
• ThirdStage
level
2
• Fourth level
Stage 3
• Fifth
Feature level1
Z Stage
Stage 2
Stage 3
22
For good technical and commercial reasons, a “freeze” date is set for
each Release. At the point of freezing a Release, the list of features
to be included in the Release is fixed, and any features under
development which cannot be completed within an agreed time
• are
frame Second level
postponed to a later Release. A feature is “completed”
when all its component specifications are stable enough to be
• Third level
published by the SDOs and implemented by equipment
• Fourthand
manufacturers level
network operators.
• toFifth
Prior levelthe following milestones must have been
“freezing”,
achieved:
23
Prior to “freezing”, the following milestones must have been achieved:
• The features to be included in the Release will have been

determined.
• Click(And any features
to edit Masterwhich
textare to be delayed to a later
styles
Release will have been identified.)
•
• Second level
For each feature, the stage 1 specifications must have been
• Third level
completed.
•
• Fourth level
In addition, the stage 2 specifications should have been
• Fifthor level
completed, very nearly so.
• Further, the stage 3 specifications should have been
completed, or are planned to be completed within a fairly short
time span.
24
Release frozen
Feature X Stage 1
Stage 2
• ClickStage
to edit
3
Master text styles
• Second level
Feature Y Stage 1
• ThirdStage
level
2
• Fourth level
Stage 3
• Fifth
Feature level1
Z Stage
Stage 2
Stage 3
25
The justification for these requirements is that
• It must be declared which features are provided by the new
Release (and which
• Click are not).
to edit Master text styles
• • Second
It must belevel
clear what benefits each new feature will bring to
users (i.e. the stage 1 specs must be stable).
• Third level
• It must be clear that the feature can be implemented with no
• Fourth
fundamental level(i.e. the stage 2 specs must be reasonably
obstacle
stable).
• Fifth level
• The protocols needed to implement the features must be
available, or at least it must be clear when they will be available
(i.e. the stage 3 specs must be reasonably well developed and a
definite target date envisaged for them to be considered stable
enough implement with acceptable commercial risk).
26
At the moment of freezing the Release, all
outstanding issues for each feature must be
identified, and target dates set for their
resolution.
•All specs should be planned to be stable
Second level
within a reasonably short time – say six
Third(two
•months level
plenary meetings) at the most.
• Fourth level
• Fifth level
27
Feature X
Feature Y
In summary:
Release N
Feature Z

• Second level Release N+1 frozen
Outstanding issues
• Third level
Feature X
Stage 1
identified and lead time to
“completion” planned.
Stage 2
• Fourth level
Feature Y
Stage 3
• Fifth level
Stage 1
Stage 2
Stage 3
All specs
Feature Z
Stage 1 available,
Stage 2 under change
Stage 3 control, and
stable.
28
total number (new specs, CRs)
Number of new CRs
For all frozen specs, essential

corrections only from this point on.

Number of new specs
• Second level
time (meeting)
• Third level
• Fourth level
• Fifth level Release frozen.
All new specs Production of new CRs (for this

identified. Release) per meeting diminishes.
29
In the past, confusion has been expressed about
what is meant by the term "freezing" in connection
with Releases. The following definition is offered:
•TheClick to edit Master text styles
act of "freezing" a Release is the
•documented
Second levelagreement of which Features shall
and which Features shall not be included in the
•setThird level
of specifications which comprise (and define)
•that
Fourth level
Release.
• Fifth level
30
The decision to freeze a Release is taken by TSG SA at a
plenary meeting, and is recorded in the report of the
meeting.
SA should base its decision on the likelihood of stage 3
• specifications
Second level for the necessary Features being ready
• within
Thirda reasonable
level time. As shown in earlier slides, in
order for SA to have confidence in such an assurance, it
• isFourth level
necessary that the stages 1 and 2 specifications be
• complete, and that the stage 3 specifications should be
Fifth level
reasonably well advanced.
(In this presentation, the terms “stable” and “complete”
are used more or less synonymously with respect to
Specifications.)
31
Premise 4:
For a Feature to be eligible for inclusion in a given
• Second level
Release, at the moment of freezing, the stage 1 and
• Third
stage level
2 specifications relating to that Feature must
• Fourth
be level
stable and the stage 3 specifications started with
planned completion dates no further than six
• Fifth level
months in the future.
32
At the point when the Release as a whole is
declared “frozen”, all its component specs are also
“frozen” except those explicitly identified as
•incomplete.
Click to Foreditthese,
Master text
a target datestyles
for freezing
must be identified by the responsible TSG.
• Second level
Once frozen, only “essential correction” category
Third
•change level
requests are allowed to a spec.
•When
Fourth level
all specs for a Release are frozen, the
•Release
Fifthaslevel
a whole may be considered stable and
implementable.
33
If necessary, individual work items can be declared
to be “completed” when all the specifications
affected by work within the scope of the work item
•areClick
stable. to edit Master
However, text implications
the practical styles of
“completing” a WI are minimal; much more
•important
Secondis thelevel
freezing of individual
Third level
•specifications and of the complete Release, and the
ultimate stability of the specifications.
• Fourth level
• Fifth level
34
Notice the difference between the terms “frozen” and
“stable” as applied to Specifications:
A frozen spec is one which is:

• under change control (see 21.900);
• Second level
• contains all the envisaged elements of functionality,
• Third level
even if some of these elements are not yet fully defined
• Fourth level
/ specified.
• Fifth level
A stable spec is one which is:
• frozen (see above);
• has all aspects defined in sufficient detail to be
implementable – i.e. equipment can confidently be
designed and built to it.
35
Some implications of the foregoing
discussion …
• Second level
• Third level
• Fourth level
• Fifth level
36
Explicitly breaking down every Feature into
distinct phases helps to focus on the timescales
involved, even before a detailed appreciation of the
• technicalities
Click to edit Master
has been text
arrived at. styles
A Gantt chart
• can be prepared
Second levelcontaining all new Features and
showing “fixed” points such as TSG (and, if
Third WG)
• desired, levelmeeting dates and the desired Release
• freeze
Fourthdate:level
• Fifth level
37
• Second level
• Third level
• Fourth level
• Fifth level
38
Note that "freezing" a Release does not imply that all the
necessary specifications are immediately available.
• Click
Thus to edit itMaster
upon freezing, text styles
will in general not be possible
immediately to implement the Release - i.e. it will not be
• Second level
possible to design and build equipment in conformity with the
• Third
services levelin the Release. It is necessary to await stable
included
stage 3 specifications, and even then, the likelihood is that there
• Fourth level
will be no usable test specifications until some considerable time
• Fifth level
later.
39
New Releases,
Richer Features
Release 99 is available for 3G system roll-out now.
•The
Click to
additional edit
features Master
included text styles
in Releases 4, 5, and beyond position
3GPP’s W-CDMA systems on the leading edge of future customer
•demands:
Second level
• Wideband AMR codec for high-quality speech.
• Third level
• High-Speed Download Packet Access for data transfer rates up
• Fourth level
to 10Mbit/s.
• Innovative modulation methods to make optimal use of scarce
• Fifth level
spectrum.
40
Stability of the 3GPP Specifications

• The specifications are a logical evolution of the GSM system.
• the
• Only Second
UTRA radiolevel
access network technology is radically new.
• The working methods have been derived from those used for GSM development.
• Third level
• The introduction of new features is carefully managed:
•• New
Fourth
featureslevel
are grouped into Releases.
•• Once
Fifth levelis frozen, new functionality is not introduced, so cannot
a Release
destabilise earlier Release systems.
41
Is Release 99 stable? Chart the number of Change Requests (CRs) against
R99 specs on a rolling six-month monthly average:
• Second level
Release frozen
• Third level
• Fourth level
• Fifth level
42
At first site, this graph looks disconcerting.
Release frozen
Does it imply that the specifications were frozen too
early?
NO •! Second level
• Third
Consider level
an analogy with software development:
Typically, 90% of the cost of software development for an application programme
• after
comes Fourth level release.
the commercial
This•is because
Fifth level
errors are detected, and desirable refinements made, only after a
system has been put into service.
The same is true for complex technology such as 3G communications systems:
despite rigorous theoretical analysis, only when real systems start to be designed
to the specs, and are actually built and tested, are problems found.
43

• Second level
• Third level
• Fourth level
• Fifth level
Show me a communications
computer programme
system where no
bugs are reported and I will show you a
computer programme
communications system which nobody uses!
44
The term “functionally frozen” means just that: the
functions of that particular Release of the system
specifications are complete. Once a Release has
been declared to be functionally frozen, no more new
• Second level
features may be added to that Release.
All new features must be added to the next Release.
• Third level
• Fourth level freezing of a Release does not imply that all the
The functional
specifications are complete.
• FifthIt does
level imply that all the stage 1 specifications are complete (except
for corrections arising from completion of later stages). It also
implies that most of the stage 2 specifications are also complete, or
nearly so.
Stage 3 specifications may take a further six months or more to
complete, and O&M and test specifications may take a further year
or more.
45
Doing a similar exercise for the later Releases shows similar curves.
Rel-4:
• Second level
• ThirdRelease
levelfrozen
• Fourth level
• Fifth level
46
Rel-5:
• Second level
• ThirdRelease
levelfrozen
• Fourth level
• Fifth level
47
Rel-6:
• Second level
• Third level
• Fourth level
• Fifth level
48
Conclusions
The 3GPP system is well specified, and the specification process is
well managed.
The presence of a large number of Change Requests is not an
• Second
indication level rather of active equipment development.
of instability,
Third
•Release 99 islevel
stable, this being shown by the trend to fewer and fewer
CRs each meeting.
•Release
Fourth level stable.
4 is similarly
•Release
Fifth5 will
level
be stable within a year.
Development will continue with Release 6 and beyond.
The 3GPP system can be enhanced with new features in a controlled

manner, as and when the market conditions demand them.
49
• Click
Fortomore
edit Master text styles
information please visit
• Second level
• Third levelhttp://www.3gpp.org
• Fourth level Or contact
• Fifth level
john.meredith@etsi.org
50

3GPP CWTS Workshop 03a Freezing of Specs and Releases

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3GPP CWTS Workshop 03a Freezing of Specs and Releases

Uploaded by

Copyright:

Available Formats

3GPP CWTS workshop

Beijing, 28 January 2003

• Click to edit Master text styles

• Click to edit Master text styles

Defines the service

Specifies any necessary

• Click to edit Master text styles

• Click to edit Master text styles

• The features to be included in the Release will have been

• Click to edit Master text styles

Number of new CRs

For all frozen specs, essential

• Click to edit Master text styles

All new specs Production of new CRs (for this

A frozen spec is one which is:

• Click to edit Master text styles

• Click to edit Master text styles

Development will continue with Release 6 and beyond.

The 3GPP system can be enhanced with new features in a controlled

You might also like