click to edit master text stylesclick to edit master text styles second levelsecond level third...

• Click to edit Master text stylesClick to edit Master text styles• Second levelSecond level• Third levelThird level• Fourth levelFourth level• Fifth levelFifth level

John M Meredith – 2003-09-15 1

3GPP – OMA Workshop3GPP – OMA WorkshopFrankfurt, 15 September 2003Frankfurt, 15 September 2003

A Phased Approach to StandardizationA Phased Approach to Standardization

John M MeredithJohn M Meredith3GPP Specifications Manager3GPP Specifications Manager

ETSI Mobile Competence CentreETSI Mobile Competence Centre([email protected])([email protected])



11 IntroductionIntroduction

22 Rules and proceduresRules and procedures

33 Meetings Meetings

44 Following the workFollowing the work

55 Phased approach, ReleasesPhased approach, Releases

66 Project management, the Work PlanProject management, the Work Plan

77 Specs: drafting, maintaining, …Specs: drafting, maintaining, …



The paths to 3GPP technologiesThe paths to 3GPP technologies

Circuit Switched

Voice & low-speed data

Packet Switched

Voice & medium-speed data

IP (option)

Voice & high-speed data

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

EDGE

DS

TC

IMT-2000

FamilyGSM W-CDMAFDD 3.84 McpsTDD 1.28 Mcps (aka: TD-SCDMA)

SC

GPRS



Evolution from GSM to 3GEvolution from GSM to 3G

1992 1993 1994 1996 1997 1998 1999 2000 2001 20021995

GSM UMTS

Phase 1 Rel '96 Rel '97Phase 2

2003

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

GPRS EDGE



Rules and procedures (1)Rules and procedures (1)3GPP operates according to the following rules and guidelines based upon the 3GPP operates according to the following rules and guidelines based upon the Collaborative Agreement http://www.3gpp.org/About/3gppagre.pdf as follows:Collaborative Agreement http://www.3gpp.org/About/3gppagre.pdf as follows:

The Working Procedures The Working Procedures http://www.3gpp.org/About/WP.htmhttp://www.3gpp.org/About/WP.htm

TSG working methodsTSG working methods http://www.3gpp.org/ftp/Specs/html-info/21900.htm http://www.3gpp.org/ftp/Specs/html-info/21900.htm

Spec drafting rules Spec drafting rules http://www.3gpp.org/ftp/Specs/html-info/21801.htmhttp://www.3gpp.org/ftp/Specs/html-info/21801.htm



Rules and procedures (2)Rules and procedures (2)

The Working Procedures The Working Procedures http://www.3gpp.org/About/WP.htmhttp://www.3gpp.org/About/WP.htm

These cover procedural issues such as holding meetings, electing officials, These cover procedural issues such as holding meetings, electing officials, participation rights, IPR policy, and so on. The Working Procedures are the top level participation rights, IPR policy, and so on. The Working Procedures are the top level of rules, and apply to all groups working under the banner of 3GPP from PCG of rules, and apply to all groups working under the banner of 3GPP from PCG downwards. If you have a question on rules and procedures, look here first.downwards. If you have a question on rules and procedures, look here first.




TSG working methodsTSG working methods http://www.3gpp.org/ftp/Specs/html-info/21900.htm http://www.3gpp.org/ftp/Specs/html-info/21900.htm

TR 21.900TR 21.900 gives detailed procedural guidance on the creation of new specifications gives detailed procedural guidance on the creation of new specifications and their management (drafting, change control, filenames, etc.). It also covers the and their management (drafting, change control, filenames, etc.). It also covers the creation and management of work items, and gives further guidance on the running creation and management of work items, and gives further guidance on the running of TSGs and their WGs (e-mail exploders, e-mail decision making, etc.).of TSGs and their WGs (e-mail exploders, e-mail decision making, etc.).




Spec drafting rules Spec drafting rules http://www.3gpp.org/ftp/Specs/html-info/21801.htmhttp://www.3gpp.org/ftp/Specs/html-info/21801.htm

Based on rules originally developed within ISO and long since adapted for use in Based on rules originally developed within ISO and long since adapted for use in most other international and national standardization bodies, most other international and national standardization bodies, TR 21.801TR 21.801 provides provides detailed instructions on the creation and modification of TSs and TRs. It covers both detailed instructions on the creation and modification of TSs and TRs. It covers both general guidance (e.g. the use of modal auxiliary verbs) and specific conventions general guidance (e.g. the use of modal auxiliary verbs) and specific conventions (which word processor styles to use for different purposes). It also includes a list of (which word processor styles to use for different purposes). It also includes a list of permissible software tools (word processor, SDL chart generator, TTCN tool, permissible software tools (word processor, SDL chart generator, TTCN tool, graphics software, etc.).graphics software, etc.).


John M Meredith – 2003-09-15 12http://www.3gpp.org/TB/home.htm

Where does the work get done?Where does the work get done?



TSG and WG meetings (1)TSG and WG meetings (1)

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov DecJan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

http://www.3gpp.org/Meetings/meetings.htm




The calendar of future 3GPP meetings can be found on the web at The calendar of future 3GPP meetings can be found on the web at

http://www.3gpp.org/Meetings/meetings.htm http://www.3gpp.org/Meetings/meetings.htm




Information on past 3GPP meetings can be found on the web at Information on past 3GPP meetings can be found on the web at

http://www.3gpp.org/ftp/Specs/html-info/PlenaryMeetings.htm http://www.3gpp.org/ftp/Specs/html-info/PlenaryMeetings.htm



How do I follow what is How do I follow what is happening where? Help!!happening where? Help!!

The guiding principles of 3GPP are openness and ease of access to the results.The guiding principles of 3GPP are openness and ease of access to the results.

The following slides show the means by which those principles are upheld, so that The following slides show the means by which those principles are upheld, so that the whole community of the whole community of

subscribers / users, subscribers / users, network operators, network operators, equipment manufacturers, and equipment manufacturers, and national administrators national administrators

can benefit from the fruits of 3GPP’s labours, whether or not they have been active can benefit from the fruits of 3GPP’s labours, whether or not they have been active participants.participants.

All information is publicly available on the 3GPP web site http://www.3gpp.org/ .All information is publicly available on the 3GPP web site http://www.3gpp.org/ .



Following the work (1)Following the work (1)

Each TSG and each Working Group have declared terms of reference. This makes Each TSG and each Working Group have declared terms of reference. This makes it relatively easy to determine which group you need to follow if you are interested in it relatively easy to determine which group you need to follow if you are interested in a particular area of work.a particular area of work.

http://www.3gpp.org/TB/home.htmhttp://www.3gpp.org/TB/home.htm

Every TSG and every WG has an e-mail exploder. In most cases, anybody can join Every TSG and every WG has an e-mail exploder. In most cases, anybody can join the exploder(s) in which he has an interest. There is no restriction to the exploder(s) in which he has an interest. There is no restriction to representatives of 3GPP Individual Members, to active participants, etc – anybody representatives of 3GPP Individual Members, to active participants, etc – anybody can join.can join.

http://www.3gpp.org/email/lists.htmhttp://www.3gpp.org/email/lists.htm

The meeting calendar for all groups is set well in advance. Increasingly, The meeting calendar for all groups is set well in advance. Increasingly, registration of intended participation in meetings can be done on-line.registration of intended participation in meetings can be done on-line.

http://www.3gpp.org/Meetings/meetings.htm#calendar.http://www.3gpp.org/Meetings/meetings.htm#calendar.




All meeting documents – invitation, agenda, contributions (so called “temporary All meeting documents – invitation, agenda, contributions (so called “temporary documents”), meeting report, etc – are available on the file server, and remain there documents”), meeting report, etc – are available on the file server, and remain there indefinitely.indefinitely.

All TSGs and WGs use a standardized file naming convention. From the file name, All TSGs and WGs use a standardized file naming convention. From the file name, you can determineyou can determine

the originating TSG or WGthe originating TSG or WGthe year in which the document was created, andthe year in which the document was created, andvia the table at:via the table at:

http://www.3gpp.org/ftp/Specs/html-info/PlenaryMeetings.htm http://www.3gpp.org/ftp/Specs/html-info/PlenaryMeetings.htm the meeting number* at which it was presented. the meeting number* at which it was presented.

You can thus easily get to a given document of interest.You can thus easily get to a given document of interest.* At the time of writing, this table only covers plenary TSG meetings. It is hoped to expand it to cover WGs in due course..* At the time of writing, this table only covers plenary TSG meetings. It is hoped to expand it to cover WGs in due course..




The agreed work plan is published after every TSG SA meeting, and forms the The agreed work plan is published after every TSG SA meeting, and forms the basis for the programme for the next three months. (More details on the basis for the programme for the next three months. (More details on the management of the work plan are given later in this presentation.)management of the work plan are given later in this presentation.)

http://www.3gpp.org/Management/WorkPlan.htmhttp://www.3gpp.org/Management/WorkPlan.htm

The specifications resulting from the Working Groups’ activities are available on the The specifications resulting from the Working Groups’ activities are available on the file server, and can be downloaded individually or en masse. For a given spec, you file server, and can be downloaded individually or en masse. For a given spec, you can also track the change history from version to version. (More details on how to can also track the change history from version to version. (More details on how to find the spec which interests you are given later in this presentation.)find the spec which interests you are given later in this presentation.)

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




If, after all that, you still cannot find the information you need ...If, after all that, you still cannot find the information you need ...

The contact coordinates of all TSG and WG officials (Chairmen, Vice-Chairmen, The contact coordinates of all TSG and WG officials (Chairmen, Vice-Chairmen, Secretaries) are available, as are those of the Support Team.Secretaries) are available, as are those of the Support Team.

http://www.3gpp.org/tb/officials.htmhttp://www.3gpp.org/tb/officials.htm

http://www.3gpp.org/Support/MCC_photos.htmhttp://www.3gpp.org/Support/MCC_photos.htm



3GPP Releases (1)3GPP Releases (1)

Specifications are grouped into “ReleasesSpecifications are grouped into “Releases””

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

A Release differs from the previous Release by having added A Release differs from the previous Release by having added functionality introduced as a result of ongoing standardization functionality introduced as a result of ongoing standardization work.work.

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



A 3GPP system definition consists of all the A 3GPP system definition consists of all the technical specifications of a given “Release”.technical specifications of a given “Release”.

Together, these specifications Together, these specifications define a set of features provided by define a set of features provided by the system.the system.




Release N

A new Release consists of the features of the A new Release consists of the features of the old Release augmented with additional old Release augmented with additional features of the new Release:features of the new Release:

Feature XFeature Y

Feature Z

Release N+1




Feature 1 spec Feature 2 spec Feature 3 spec

Traditional systems analysis and project management Traditional systems analysis and project management techniques break the idea down into progressively more techniques 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 Management (1)Project Management (1)



Feature 1 spec

A named individual – the “rapporteur” - is A named individual – the “rapporteur” - is identified for each feature and, where identified for each feature and, where necessary, for each component subtask of necessary, for each component subtask of the feature. the feature.

It is the rapporteur’s responsibility to It is the rapporteur’s responsibility to monitor work, and, for example, to hold monitor work, and, for example, to hold extra ad hoc meetings to ensure progress extra ad hoc meetings to ensure progress is made. He will also prepare a short is made. He will also prepare a short report on the feature to each TSG meeting, report on the feature to each TSG meeting, and will maintain the WID, presenting any and will maintain the WID, presenting any changes to the TSG for approval.changes to the TSG for approval.

To be adopted onto the work programme of 3GPP, each feature To be adopted onto the work programme of 3GPP, each feature must have the support of at least four 3GPP individual member must have the support of at least four 3GPP individual member organizations, which agree to contribute organizations, which agree to contribute activelyactively to the development to the development of the necessary technical specifications.of the necessary technical specifications.

A Work Item Description (WID) is prepared using a standard form, A Work Item Description (WID) is prepared using a standard form, and is approved by the TSG.and is approved by the TSG.




Feature 1 spec

Most “features” are too complex to be handled as a whole, so Most “features” are too complex to be handled as a whole, so each is broken down into a number component tasks (“building each is broken down into a number component tasks (“building blocks”).blocks”).

Each of these components is managed independently, with the Each of these components is managed independently, with the feature rapporteur coordinating progress.feature rapporteur coordinating progress.





Feature 1 spec

Even building blocks may be too complicated to manage as a Even building blocks may be too complicated to manage as a whole, and further functional decomposition to smaller “work whole, and further functional decomposition to smaller “work tasks” is possible.tasks” is possible.

}}Features, building blocks and work tasks Features, building blocks and work tasks are generically known as “work items”.are generically known as “work items”.

wo

rk i

tem

s



Release N

A new Release consists of the features of the old Release augmented with additional features of the new Release:

Feature XFeature Y

Feature Z

Release N+1



Release N

Some features may not be ready in time to be included in the new Release, and are held over till a later Release:

Feature XFeature Y

Feature Z

To Release N+2



A “Feature” is defined by its “Work Item Description” sheet. It is manifested by a set of

new technical specifications and changes to existing specifications.



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 commercial, non-technical way. Thus even senior management may see at a glance the commercial and financial implications of adding, or not adding, a feature to the system.



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 individual Feature.

As the level of break-down increases, the lower levels will be defined in progressively more technical terms. The number of levels of decomposition should be sufficient to allow 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.



The standardization activity is typically arranged into the well-known three stages.

Stage 1

Stage 2

Stage 3

Defines the service aspects of a feature (or part thereof) from the

end-user's point of view.

Defines the logical functionality and information flows

amongst the functional entities involved in

providing the service.

Specifies any necessary functionality of physical entities (equipment) and the detailed protocols of the signalling between

them.



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 "study items" which produce reports forming the foundation for subsequent concrete standardization in "work items".



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.



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, through the Radio Access Network, to the Core Network, and on to network management interfaces, and to fixed networks. The service may require new codecs. Depending on the nature of the Feature, it may only be necessary to change existing specifications rather than to create completely new ones. This is particularly so at stage 3, where the service has to co-exist with all other services. However, this will vary from case to case.



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 protocol TSs.

Stage 1Stage 2Stage 3

Feature Y


Feature X


Feature Z



Further stages not originally envisaged by CCITT are the development of Operations and Maintenance (O&M) specifications (mainly within SA5) and of Test specifications. Whilst O&M specs can be developed more or less at the same time as the stage 3 protocols, it is usually prudent to wait until the protocols are fairly stable (i.e. field tested) before embarking on detailed test specifications. Thus whilst the O&M specs may be only six months behind the stages 3, the test specs follow a year or more later.




Feature X

Development of the TSs and CRs needed to implement each feature starts with stage 1, progresses to stage 2, and concludes with stage 3.




Feature X

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:




Feature Y

Overall progress is estimated and monitored by the sum of the individual features.


Feature X


Feature Z



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 frame are postponed to a later Release. A feature is “completed” when all its component specifications are stable enough to be published by the SDOs and implemented by equipment manufacturers and network operators.

Prior to “freezing”, the following milestones must have been achieved:



Prior to “freezing”, the following milestones must have been achieved:

• The features to be included in the Release will have been determined. (And any features which are to be delayed to a later Release will have been identified.)

• For each feature, the stage 1 specifications must have been completed.

• In addition, the stage 2 specifications should have been completed, or very nearly so.

• Further, the stage 3 specifications should have been completed, or are planned to be completed within a fairly short time span.




Feature Y


Feature X


Feature Z

Release frozen



The justification for these requirements is that

• It must be declared which features are provided by the new Release (and which are not).

• It must be clear what benefits each new feature will bring to users (i.e. the stage 1 specs must be stable).

• It must be clear that the feature can be implemented with no fundamental obstacle (i.e. the stage 2 specs must be reasonably stable).

• 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 to implement with acceptable commercial risk).



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 within a reasonably short time – say six months (two plenary meetings) at the most.



Release N

Feature X

Feature Y

Feature Z

Stage 1

Stage 2

Stage 3

Feature Y

Stage 1

Stage 2

Stage 3

Feature X

Stage 1

Stage 2

Stage 3

Feature Z

Release N+1 frozen

All specs available,

under change control, and

stable.

In summary:

Outstanding issues identified and lead time to

“completion” planned.



Active project managementActive project management



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 GSM 3G Release 99 contained more or less the same functionality as GSM R99, but of course using the new UTRA radio access network technology R99, but of course using the new UTRA radio access network technology (W-CDMA).(W-CDMA).



Release 4Release 4



Release 5Release 5



Release 6Release 6



Take a closer look at the project management techniques …Take a closer look at the project management techniques …



The work plan is reviewed at every TSG SA meeting …The work plan is reviewed at every TSG SA meeting …



Every Feature (top level functional enhancement) is examined Every Feature (top level functional enhancement) is examined in sufficient detail to ensure thatin sufficient detail to ensure that

• Its definition is (still) correct, and thatIts definition is (still) correct, and that

• It is making adequate progress according to plan.It is making adequate progress according to plan.



Its Work Item Definition sheet is Its Work Item Definition sheet is updated if necessary and re-issued updated if necessary and re-issued as a TSG meeting document. This as a TSG meeting document. This is the document which will be is the document which will be referred to in the next issue of the referred to in the next issue of the Work Plan.Work Plan.

The Work Item Definition sheets The Work Item Definition sheets are re-issued after each TSG SA are re-issued after each TSG SA meeting.meeting.

You can find them atYou can find them at

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



Its Work Plan is Its Work Plan is re-issued after re-issued after each TSG SA meeting.each TSG SA meeting.

You can find it atYou can find it at

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



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 temp doc together 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, 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 has enabled the GSM A change control system along the lines described has enabled the GSM specifications to have undergone nine controlled releases, and has specifications to have undergone nine controlled releases, and has allowed a smooth transition from second generation digital mobile allowed a smooth transition from second generation digital mobile communications to third generation, re-using as many of the basic communications to third generation, re-using as many of the basic elements as possible.elements as possible.

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




3GPP system Releases3GPP system Releases

• R99R99 functionally frozen December 1999. The functionally frozen December 1999. The basis for early 3G deployment in Japan, Isle basis for early 3G deployment in Japan, Isle of Man, Monaco, Italy, UK, and …many more of Man, Monaco, Italy, UK, and …many more in preparation.in preparation.

• Rel-4Rel-4 functionally frozen March 2001. Defines the low functionally frozen March 2001. Defines the low chip rate TDD mode of particular interest to chip rate TDD mode of particular interest to

China, China, but with high potential in other but with high potential in other markets.markets.

• Rel-5Rel-5 functionally frozen March/June 2002 – IMS functionally frozen March/June 2002 – IMS phase 1phase 1

• Rel-6Rel-6 expected to be functionally frozen in mid-2004expected to be functionally frozen in mid-2004



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

http://www.3gpp.org/specs/specs.htmhttp://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 please visitFor more information please visit

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

Or contactOr contact

[email protected]@etsi.org

click to edit master text stylesclick to edit master text styles second levelsecond level third...

Documents