3GPP CWTS Workshop 01 Phased Approach

8/8/2019 3GPP CWTS Workshop 01 Phased Approach

1/33

Click to edit Master text stylesClick to edit Master text styles

Second levelSecond level

Third levelThird level

Fourth levelFourth level

Fifth levelFifth level

1

3GPP CWTS workshop3GPP CWTS workshop

Beijing, 28 January 2003Beijing, 28 January 2003

Presentation 1:Presentation 1:

A Phased Approach to StandardizationA Phased Approach to Standardization

John M MeredithJohn M Meredith

3GPP Specifications Manager3GPP Specifications Manager

ETSI Mobile Competence CentreETSI Mobile Competence Centre


2/33






2

A reminderA reminder -- What does 3GPP do?What does 3GPP do?

3GPP p

repares and maintains specifications for the3GPP prepares and maintains specifications for thefollowing technologies:following technologies:

GSMGSM

GPRSGPRS

EDGEEDGE

WCDMAWCDMA FDDFDD (Frequency Division Duplex)(Frequency Division Duplex)

WCDMAWCDMA TDDTDD (Time Division Duplex(Time Division Duplex in both High Chipin both High ChipRate and Low Chip Rate (TDSCDMA)Rate and Low Chip Rate (TDSCDMA)

modes)modes)

And other modulation schemes currently under considerationAnd other modulation schemes currently under consideration


3/33






3

The paths to 3GPP technologiesThe paths to 3GPP technologies

Circuit

Switched

Voice & low-speed dataPacket

Switched

Voice & medium-speed dataIP (option)

Voice & high-speed data

Paths from other technologies, e.g. IS-136, PDC

EDGE

DS

TC

IMT-2000

FamilyGSMW-CDMAFDD 3.84 Mcps

TDD 1.28 Mcps(aka: TD-SCDMA)

SC

GPRS


4/33






4

3GPP Releases3GPP Releases

Sp

ecifications are grouped into ReleasesSpecifications are grouped into Releases

A mobile system can be constructed based on the set of allA mobile system can be constructed based on the set of allspecifications which comprise a given Release.specifications which comprise a given Release.

A Release differs from the previous Release by having addedA Release differs from the previous Release by having addedfunctionality introduced as a result of ongoing standardizationfunctionality introduced as a result of ongoing standardizationwork.work.


5/33






5

Evolution from GSM to 3GEvolution from GSM to 3G

1992 1993 1994 1996 1997 1998 1999 2000 2001 20021995

GSM 3G

Phase 1 Rel '96 Rel '97Phase 2

2003

Rel '98 Rel '99 Rel-4 Rel-5


6/33






6

Feature 1 spec Feature 2 spec Feature 3 spec

Traditional systems analysis and project managementTraditional systems analysis and project management

techniques break the idea down into progressively moretechniques break the idea down into progressively more

manageable elements.manageable elements.

Until it is possible to identify individual component specifications.Until it is possible to identify individual component specifications.

Project ManagementProject Management

andand

the Change Control cycle the Change Control cycle


7/33






7

The rapporteur issues theThe rapporteur issues the

specification as version 0.0.0specification as version 0.0.0

Release field

Technical field

Editorial fieldThe Editorial field of the version number is incremented eachThe Editorial field of the version number is incremented eachtime an editorial change is made to the document.time an editorial change is made to the document.

It is reset to zero every time the Technical field is updated.It is reset to zero every time the Technical field is updated.

The Technical field of the version number is incremented each time aThe Technical field of the version number is incremented each time atechnical change is made to the document.technical change is made to the document.

It is reset to zero every time the Release field is updated.It is reset to zero every time the Release field is updated.

The Release field of the version number is incremented each timeThe Release field of the version number is incremented each timemajor new functionality is made to the system (rather than to themajor new functionality is made to the system (rather than to theindividual document).individual document).


8/33






8

The drafting processThe drafting process

The initial draft is discussed in theThe initial draft is discussed in the

working group.working group.

v0.0.0

v0.1.0

And a new draft is produced,And a new draft is produced,

bearing technical changes.bearing technical changes.


9/33






9

v0.1.0 v0.2.0 v0.3.0

The process is iterative, until The process is iterative, until


v0.8.0

the working group is happy the working group is happy

with the draft.with the draft.

v1.0.0

Draft 1.0.0 is presentedDraft 1.0.0 is presented for informationfor information to the plenaryto the plenary

TSG (Technical Body).TSG (Technical Body).


10/33






10

v1.0.0 v1.1.0 v1.2.0

The document returns to the workingThe document returns to the working

group, and drafting continues until group, and drafting continues until


v1.5.0

the working group believes the draft the working group believes the draft

to be stable enough to come underto be stable enough to come under

formal change control.formal change control.v2.0.0

Draft 2.0.0 is presentedDraft 2.0.0 is presented for approvalfor approval to the plenary TSGto the plenary TSG

(Technical Body).(Technical Body).


11/33






11

v2.0.0 v2.1.0 v2.2.0

If the TSG does not approve the draft, itIf the TSG does not approve the draft, it

may return to the working group for furthermay return to the working group for further

refinement. This is exceptional.refinement. This is exceptional.


v3.0.0

v2.3.0

When the draft is approved to come under change control, it is upgradedWhen the draft is approved to come under change control, it is upgraded

to version 3.0.0to version 3.0.0 (assuming Release 1999(assuming Release 1999 see later)see later)..


12/33






12

The system is composedThe system is composedof a coherent set ofof a coherent set of

related specifications.related specifications.

Change controlChange control

It is still possible to develop the standard further,It is still possible to develop the standard further,

to add the missing parts, and to correct errorsto add the missing parts, and to correct errors

and omissions as the overall system becomesand omissions as the overall system becomes

better defined.better defined.


13/33






13

Consider an individual standard Consider an individual standard

v3.0.0

If the responsible working group wishes to make a change toIf the responsible working group wishes to make a change to

it,it, however smallhowever small, ,


the working group must raise a Change Request. the working group must raise a Change Request.

The CR consists of a coverThe CR consists of a coverpage page

and an extract from the and an extract from the

specification underspecification under

consideration showing, usingconsideration showing, usingrevision marks,revision marks, all additionsall additions

and deletionsand deletions..


14/33






14

For example, a CR to TS 23.456 may be twice revised during the course ofFor example, a CR to TS 23.456 may be twice revised during the course of

discussions in the WG before it is agreed.discussions in the WG before it is agreed.

CR 4

to 23.456

CR 4 rev 1

to 23.456

CR 4 rev 2

to 23.456


Several iterations of a CR may be required until the WG is happy with it.Several iterations of a CR may be required until the WG is happy with it.


15/33






15

CR 4 rev 2

to 23.456

CR 5 rev 1

to 23.456

CR 6

to 23.456

All CRs against a given specification (or a given work item) are gatheredAll CRs against a given specification (or a given work item) are gathered

together by the Support Team* prior to each TSG plenary. A single temp doctogether by the Support Team* prior to each TSG plenary. A single temp doc

is created, with a cover page introducing each individual CR.is created, with a cover page introducing each individual CR.

* In practice, by* In practice, bythe Secretary ofthe Secretary of

the WGthe WGresponsible forresponsible for

the spec.the spec.


The TSG examines each CR and approves or rejects each. Some CRs mayThe TSG examines each CR and approves or rejects each. Some CRs may

be reworked during the TSG meeting and rebe reworked during the TSG meeting and re--presented (with a new revisionpresented (with a new revision

number).number).


16/33






16

CR 4 rev 2

to 23.456

CR 5 rev 1

to 23.456

The Support Team (MCC)The Support Team (MCC)

incorporates the approved CRsincorporates the approved CRsinto the base specification into the base specification

v3.0.0 v3.1.0



17/33






17

v3.1.0 v3.2.0 v3.3.0

The controlled revision of specifications can continue in theThe controlled revision of specifications can continue in the

same manner, with CRs being produced and approved. CRssame manner, with CRs being produced and approved. CRs

allow full traceability of the changes wrought on a documentallow full traceability of the changes wrought on a documentsince its original approval.since its original approval.



18/33






18

Using the Change Control mechanism described, it is always possibleUsing the Change Control mechanism described, it is always possible

to:to:

See the differences from one version of a spec to the next.See the differences from one version of a spec to the next.

If necessary, backIf necessary, back--track by detrack by de--implementing Change Requests whichimplementing Change Requests which

prove to be flawed.prove to be flawed.

Know exactly what set of specifications a system is to be built to.Know exactly what set of specifications a system is to be built to.



19/33






19

The initial system isThe initial system is

composed of a coherentcomposed of a coherent

set of related standards.set of related standards.

All these standards have version numbers ofAll these standards have version numbers of

the formthe form 33.y.z and are known as.y.z and are known as

Release1999.Release1999.

Eventually, the functionality of Release 1999Eventually, the functionality of Release 1999

became stable. The Release was frozen.became stable. The Release was frozen.


Once frozen, no more functionality may be added to a ReleaseOnce frozen, no more functionality may be added to a Release(or, therefore, to its component specifications). Only(or, therefore, to its component specifications). Only essentialessential

correctionscorrections are permitted.are permitted.


20/33






20

It is now possible to add further functionality inIt is now possible to add further functionality in

carefully designed features forming part of a newcarefully designed features forming part of a newRelease.Release.

Feature 1 spec Feature 2 spec Feature 3 spec



21/33






21

it is possible to raise Change Requests to each it is possible to raise Change Requests to each

specification to include the new functionality.specification to include the new functionality.

v3.3.0



22/33






22

v3.3.0 v4.0.0 v4.1.0

The addition of the new features to the system implies anThe addition of the new features to the system implies an

upgrade to the next Release of the entire systemupgrade to the next Release of the entire system

specification.specification.



23/33






23

New functionality may equally result in an entirelyNew functionality may equally result in an entirely

new specification rather than a change to annew specification rather than a change to anexisting one.existing one.

v0.0.0v1.0.0 2.0.0 v4.0.0



24/33






24

Release 1999 Release 4

The result, in due course, is two complete sets of specifications: one forThe result, in due course, is two complete sets of specifications: one for

each Release.each Release.

Implementors (operators and equipment vendors) can choose whichImplementors (operators and equipment vendors) can choose which

Release to build their systems to. Generally, newer Releases will beRelease to build their systems to. Generally, newer Releases will be

richer in features, but less tried and tested.richer in features, but less tried and tested.


25/33






25

A disadvantage of the release approach A disadvantage of the release approach

Release 1999 Release 4

An error discovered here An error discovered here

may require not one CR but may require not one CR but

twotwo to fix it to fix it

because the same error may because the same error may

have been inherited from thehave been inherited from the

earlier Release!earlier Release!

Note that maintaining severalNote that maintaining several

parallel releases of the sameparallel releases of the same

specification implies very wellspecification implies very well

defined procedures and highlydefined procedures and highly

disciplined handling !!disciplined handling !!


26/33






26

A change control system along the lines described has enabled the GSMA change control system along the lines described has enabled the GSMspecifications to have undergone six controlled release, and has allowedspecifications to have undergone six controlled release, and has allowed

a smooth transition from second generation digital mobile communicationsa smooth transition from second generation digital mobile communications

to third generation, reto third generation, re--using as many of the basic elements as possible.using as many of the basic elements as possible.

This mechanism requires meticulous project planning and controlThis mechanism requires meticulous project planning and control


27/33






27

3GPP Releases3GPP Releases

Release '99Release '99 functionally frozen December 1999. Thefunctionally frozen December 1999. Thebasis for early 3G deployment in Japan, Islebasis for early 3G deployment in Japan, Isle

of Man, Monaco, and many more inof Man, Monaco, and many more in

preparation.preparation.

Release 4Release 4 functionally frozen March 2001.functionally frozen March 2001. Defines theDefines thelow chip rate TDD mode of particular interestlow chip rate TDD mode of particular interest

to China, but with high potential in otherto China, but with high potential in other

markets.markets. Release 5Release 5 functionally frozen March/June 2002functionally frozen March/June 2002

Release 6Release 6 expected to be functionally frozen in lateexpected to be functionally frozen in late20032003


28/33






28

Active project managementActive project management


29/33






29

The 3GPP work plan can be consulted at:The 3GPP work plan can be consulted at:

http://www.3gpp.org/ftp/Information/WORK_PLAN/http://www.3gpp.org/ftp/Information/WORK_PLAN/

Active project managementActive project management

3G Release 99 contained more or less the same functionality as GSM3G Release 99 contained more or less the same functionality as GSM

R99, but of course using the new UTRA radio access network technologyR99, but of course using the new UTRA radio access network technology

(W(W--CDMA).CDMA).


30/33






30

Release 4Release 4


31/33






31

Release 5Release 5


32/33






32

Release 6Release 6


33/33






33

For more information please visitFor more information please visit

http://www.3gpp.orghttp://www.3gpp.org

Or contactOr contact

[email protected]@etsi.org

3GPP CWTS Workshop 01 Phased Approach

Documents

Transcript of 3GPP CWTS Workshop 01 Phased Approach