© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP 2009 3GPP The Training...

© 3GPP 2009 Mobile World Congress, Barcelona, 19th February 2009© 3GPP 2009 3GPP The Training Course / Module 10 1

All you always wanted to know about 3GPP …

but were too afraid to ask.

The 3GPP SeminarThe 3GPP Seminar


The 3GPP SeminarModule 10

Drafting and maintaining the Technical Specifications


Drafting and maintaining Drafting and maintaining the technical specificationsthe technical specifications

The work items result in new The work items result in new technical specifications, or technical specifications, or enhancements to existing ones …enhancements to existing ones …


A named individual – the A named individual – the “rapporteur” - is identified for each “rapporteur” - is identified for each spec. spec.

It is the rapporteur’s responsibility to It is the rapporteur’s responsibility to initiate the drafting of the spec, and initiate the drafting of the spec, and to maintain it throughout the drafting to maintain it throughout the drafting process.process.

scribble scribble scribble scribble

Spec numbers are allocated by the Support Team.

The drafting process (1)The drafting process (1)


The rapporteur issues the The 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 each The Editorial field of the version number is incremented each time 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 a The Technical field of the version number is incremented each time a technical 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 time The Release field of the version number is incremented each time major new functionality is made to the system (rather than to the major new functionality is made to the system (rather than to the individual document).individual document).



The initial draft is discussed in the The initial draft is discussed in the working group.working group.

v0.0.0

v0.1.0And a new draft is produced, And a new draft is produced, bearing technical changes.bearing technical changes.



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 presented Draft 1.0.0 is presented for informationfor information to the plenary to the plenary TSG (Technical Body).TSG (Technical Body).



v1.0.0 v1.1.0 v1.2.0

…

The document returns to the working The 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 under to be stable enough to come under

formal “change control”.formal “change control”.v2.0.0

Draft 2.0.0 is presented Draft 2.0.0 is presented for approvalfor approval to the plenary TSG to the plenary TSG (Technical Body).(Technical Body).



v2.0.0 v2.1.0 v2.2.0

…

If the TSG does not approve the draft, it If the TSG does not approve the draft, it may return to the working group for further may 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 When the draft is approved to come under change controlchange control, it is upgraded , it is upgraded to version 3.0.0 to version 3.0.0 (assuming Release 1999 – see later)(assuming Release 1999 – see later)..



The “system” is composed The “system” is composed of a coherent set of related of a coherent set of related specifications.specifications.

Change control (1)Change control (1)

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 errors to add the missing parts, and to correct errors and omissions as the overall system becomes and omissions as the overall system becomes better defined.better defined.


Consider an individual standard …Consider an individual standard …

v3.0.0

If the responsible working group wishes to make a change to If 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 cover The CR consists of a cover page …page …

… … and an extract from the and an extract from the specification under specification under consideration showing, using consideration showing, using revision marks, revision marks, all additions all additions and deletionsand deletions..

http://www.3gpp.org/specs/CR.htm



For example, a CR to TS 23.456 may be twice revised during the course of For 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 4to 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.



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 gathered All CRs against a given specification (or a given work item) are gathered together by the Support Team* prior to each TSG plenary. A single TDoc is together by the Support Team* prior to each TSG plenary. A single TDoc is created, with a cover page introducing each individual CR.created, with a cover page introducing each individual CR.

* In practice, by * In practice, by the Secretary of the Secretary of the WG the WG responsible for the responsible for the spec.spec.

The TSG examines each CR and approves or rejects each. Some CRs may The TSG examines each CR and approves or rejects each. Some CRs may be reworked during the TSG meeting and re-presented (with a new revision be reworked during the TSG meeting and re-presented (with a new revision number).number).



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 CRs incorporates the approved CRs into the base specification …into the base specification …

v3.0.0 v3.1.0



v3.1.0 v3.2.0 v3.3.0

…

The controlled revision of specifications can continue in the The controlled revision of specifications can continue in the same manner, with CRs being produced and approved. CRs same manner, with CRs being produced and approved. CRs allow full traceability of the changes wrought on a document allow full traceability of the changes wrought on a document

since its original approval.since its original approval.



Using the Change Control mechanism described, it is always possible to:Using the Change Control mechanism described, it is always possible 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, back-track by de-implementing Change Requests which If necessary, back-track by de-implementing 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.



The initial “system” is The initial “system” is composed of a coherent composed of a coherent set of related standards.set of related standards.

All these standards have version numbers of All these standards have version numbers of the form the form 33.y.z and are known as .y.z and are known as Release1999.Release1999.

Eventually, the functionality of Release 1999 Eventually, 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 Release Once frozen, no more functionality may be added to a Release (or, therefore, to its component specifications). Only (or, therefore, to its component specifications). Only essential essential correctionscorrections are permitted. are permitted.



It is now possible to add further functionality in It is now possible to add further functionality in carefully designed features forming part of a new carefully designed features forming part of a new “Release”.“Release”.

Feature 1 spec Feature 2 spec Feature 3 spec



… … 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



v3.3.0 v4.0.0 v4.1.0

…

The addition of the new features to the system implies an The addition of the new features to the system implies an upgrade to the next “Release” of the entire system upgrade to the next “Release” of the entire system specification.specification.



New functionality may equally result in an entirely New functionality may equally result in an entirely new specification rather than a change to an new specification rather than a change to an existing one.existing one.

v0.0.0v1.0.0 2.0.0 v4.0.0



Release 1999 Release 4

The result, in due course, is two complete sets of specifications: one for The result, in due course, is two complete sets of specifications: one for each Release.each Release.

Implementors (operators and equipment vendors) can choose which Implementors (operators and equipment vendors) can choose which Release to build their systems to. Generally, newer Releases will be Release 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.



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 the have been inherited from the earlier Release!earlier Release!

Note that maintaining several Note that maintaining several parallel releases of the same parallel releases of the same specification implies very well specification implies very well defined procedures and highly defined procedures and highly disciplined handling !!disciplined handling !!



A change control system along the lines described enabled the GSM A change control system along the lines described enabled the GSM specifications to undergo five controlled releases before the creation of specifications to undergo five controlled releases before the creation of 3GPP, and has allowed a smooth transition from second generation digital 3GPP, and has allowed a smooth transition from second generation digital mobile communications to third generation and beyond, re-using as many mobile communications to third generation and beyond, re-using as many of the basic elements as possible.of the basic elements as possible.

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



Usually, an individual version of a spec may be withdrawn after its Usually, an individual version of a spec may be withdrawn after its production only if it is replaced with a revised version. For example, a production only if it is replaced with a revised version. For example, a new version of 23.456 v9.3.0 is produced after meeting SA#50. It is new version of 23.456 v9.3.0 is produced after meeting SA#50. It is immediately noticed that one CR was incorrectly implemented. A new immediately noticed that one CR was incorrectly implemented. A new version 9.3.1 is produced straight away to correct the fault, and version version 9.3.1 is produced straight away to correct the fault, and version 9.3.0 is withdrawn.9.3.0 is withdrawn.

Version 9.3.0 will never be transposed into a publication of the OPs.Version 9.3.0 will never be transposed into a publication of the OPs.

However …However …

Version 9.3.0 will remain in the archive directory on the 3GPP server for Version 9.3.0 will remain in the archive directory on the 3GPP server for ever.ever.

Withdrawing obsolete specs (1)Withdrawing obsolete specs (1)


Consider now that a new version of 23.456, v9.4.0, is produced after Consider now that a new version of 23.456, v9.4.0, is produced after SA#50.SA#50.

Version 9.3.0 is Version 9.3.0 is notnot withdrawn, but remains in the meeting directory withdrawn, but remains in the meeting directory pertaining to SA#50. It also remains in the archive directory. But it is pertaining to SA#50. It also remains in the archive directory. But it is obviously superseded by v9.4.0 at SA#51.obviously superseded by v9.4.0 at SA#51.

No maintenance will be done on v9.3.0 once 9.4.0 becomes available.No maintenance will be done on v9.3.0 once 9.4.0 becomes available.

Withdrawing obsolete specs (2)Withdrawing obsolete specs (2)


Short answer: on the 3GPP file server.Short answer: on the 3GPP file server.

http://www.3gpp.org/specs/specs.htm

So where do I find the So where do I find the 3GPP Technical 3GPP Technical Specifications?Specifications?


Longer answer: on the 3GPP file server.Longer answer: on the 3GPP file server.

The following directories are maintained:The following directories are maintained:

So where do I find the So where do I find the 3GPP Technical 3GPP Technical Specifications?Specifications?

Meeting-related directoriesMeeting-related directoriesHold all specs current as a result of implementing the Hold all specs current as a result of implementing the approvals at the corresponding SA plenary meeting.approvals at the corresponding SA plenary meeting.

LatestLatestHolds the latest version of each spec currently under Holds the latest version of each spec currently under change control.change control.

Latest draftsLatest draftsHolds the latest version of each draft spec (i.e. those not yet Holds the latest version of each draft spec (i.e. those not yet under change control).under change control).

ArchiveArchiveHolds every version of every spec, including stopped / Holds every version of every spec, including stopped / withdrawn ones.withdrawn ones.


For more information visit

http://www.3gpp.org

Or contact

[email protected]

© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP 2009 3GPP The Training...

Documents

Transcript of © 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP 2009 3GPP The Training...