Download presentation
Presentation is loading. Please wait.
Published byLucas Lyons Modified over 9 years ago
1
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 Workshop Frankfurt, 15 September 2003 A Phased Approach to Standardization John M Meredith 3GPP Specifications Manager ETSI Mobile Competence Centre (john.meredith@etsi.org) john.meredith@etsi.org
2
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 2 1Introduction 2Rules and procedures 3Meetings 4Following the work 5Phased approach, Releases 6Project management, the Work Plan 7Specs: drafting, maintaining, …
3
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 3 1Introduction 2Rules and procedures 3Meetings 4Following the work 5Phased approach, Releases 6Project management, the Work Plan 7Specs: drafting, maintaining, …
4
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 4 The 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 Family GSM W-CDMA FDD3.84 Mcps TDD1.28 Mcps (aka: TD-SCDMA) SC GPRS
5
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 5 Evolution from GSM to 3G 19921993199419961997199819992000200120021995 GSMUMTS Phase 1Rel '96Rel '97 Phase 2 2003 Rel '98Rel '99Rel-4 Rel-5 GPRS EDGE
6
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 6 1Introduction 2Rules and procedures 3Meetings 4Following the work 5Phased approach, Releases 6Project management, the Work Plan 7Specs: drafting, maintaining, …
7
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 7 Rules and procedures (1) 3GPP operates according to the following rules and guidelines based upon the Collaborative Agreement http://www.3gpp.org/About/3gppagre.pdf as follows: http://www.3gpp.org/About/3gppagre.pdf The Working Procedures http://www.3gpp.org/About/WP.htm http://www.3gpp.org/About/WP.htm TSG 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 http://www.3gpp.org/ftp/Specs/html-info/21801.htm http://www.3gpp.org/ftp/Specs/html-info/21801.htm
8
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 8 Rules and procedures (2) The Working Procedures http://www.3gpp.org/About/WP.htm http://www.3gpp.org/About/WP.htm These cover procedural issues such as holding meetings, electing officials, 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 downwards. If you have a question on rules and procedures, look here first.
9
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 9 Rules and procedures (3) TSG working methods http://www.3gpp.org/ftp/Specs/html-info/21900.htm http://www.3gpp.org/ftp/Specs/html-info/21900.htm TR 21.900 gives detailed procedural guidance on the creation of new specifications 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 of TSGs and their WGs (e-mail exploders, e-mail decision making, etc.).
10
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 10 Rules and procedures (4) Spec drafting rules http://www.3gpp.org/ftp/Specs/html-info/21801.htm http://www.3gpp.org/ftp/Specs/html-info/21801.htm Based on rules originally developed within ISO and long since adapted for use in most other international and national standardization bodies, TR 21.801 provides 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 (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, graphics software, etc.).
11
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 11 1Introduction 2Rules and procedures 3Meetings 4Following the work 5Phased approach, Releases 6Project management, the Work Plan 7Specs: drafting, maintaining, …
12
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 12 http://www.3gpp.org/TB/home.htm Where does the work get done?
13
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 13 TSG and WG meetings (1) Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec http://www.3gpp.org/Meetings/meetings.htm
14
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 14 TSG and WG meetings (2) Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
15
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 15 TSG and WG meetings (3) Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
16
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 16 TSG and WG meetings (4) Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
17
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 17 TSG and WG meetings (5) Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
18
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 18 TSG and WG meetings (6) The calendar of future 3GPP meetings can be found on the web at http://www.3gpp.org/Meetings/meetings.htm
19
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 19 TSG and WG meetings (7) Information on past 3GPP meetings can be found on the web at http://www.3gpp.org/ftp/Specs/html-info/PlenaryMeetings.htm
20
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 20 1Introduction 2Rules and procedures 3Meetings 4Following the work 5Phased approach, Releases 6Project management, the Work Plan 7Specs: drafting, maintaining, …
21
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 21 How do I follow what is happening where? Help!! 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 whole community of subscribers / users, network operators, equipment manufacturers, and national administrators can benefit from the fruits of 3GPP’s labours, whether or not they have been active participants. All information is publicly available on the 3GPP web site http://www.3gpp.org/. http://www.3gpp.org/
22
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 22 Following the work (1) 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 a particular area of work. http://www.3gpp.org/TB/home.htm 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 representatives of 3GPP Individual Members, to active participants, etc – anybody can join. http://www.3gpp.org/email/lists.htm The meeting calendar for all groups is set well in advance. Increasingly, registration of intended participation in meetings can be done on-line. http://www.3gpp.org/Meetings/meetings.htm#calendarhttp://www.3gpp.org/Meetings/meetings.htm#calendar. http://www.3gpp.org/Meetings/meetings.htm#calendar
23
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 23 Following the work (2) All meeting documents – invitation, agenda, contributions (so called “temporary documents”), meeting report, etc – are available on the file server, and remain there indefinitely. All TSGs and WGs use a standardized file naming convention. From the file name, you can determine the originating TSG or WG the year in which the document was created, and via the table at: http://www.3gpp.org/ftp/Specs/html-info/PlenaryMeetings.htm the meeting number* at which it was presented. You can thus easily get to a given document of interest. http://www.3gpp.org/ftp/Specs/html-info/PlenaryMeetings.htm * At the time of writing, this table only covers plenary TSG meetings. It is hoped to expand it to cover WGs in due course..
24
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 24 Following the work (3) 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 management of the work plan are given later in this presentation.) http://www.3gpp.org/Management/WorkPlan.htm 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 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.) http://www.3gpp.org/specs/numbering.htm
25
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 25 Following the work (4) If, after all that, you still cannot find the information you need... The contact coordinates of all TSG and WG officials (Chairmen, Vice-Chairmen, Secretaries) are available, as are those of the Support Team. http://www.3gpp.org/tb/officials.htm http://www.3gpp.org/Support/MCC_photos.htm
26
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 26 1Introduction 2Rules and procedures 3Meetings 4Following the work 5Phased approach, Releases 6Project management, the Work Plan 7Specs: drafting, maintaining, …
27
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 27 3GPP Releases (1) Specifications are grouped into “Releases ” A mobile system can be constructed based on the set of all specifications which comprise a given Release. A Release differs from the previous Release by having added functionality introduced as a result of ongoing standardization work. http://www.3gpp.org/specs/releases.htm
28
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 28 A 3GPP system definition consists of all the technical specifications of a given “Release”. Together, these specifications define a set of features provided by the system. 3GPP Releases (2)
29
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 29 Release N A new Release consists of the features of the old Release augmented with additional features of the new Release: Feature X Feature Y Feature Z Release N+1 3GPP Releases (3)
30
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 30 1Introduction 2Rules and procedures 3Meetings 4Following the work 5Phased approach, Releases 6Project management, the Work Plan 7Specs: drafting, maintaining, …
31
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 31 Feature 1 specFeature 2 specFeature 3 spec Traditional systems analysis and project management techniques break the idea down into progressively more manageable elements. Until it is possible to identify individual component specifications. Project Management (1)
32
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 32 Feature 1 spec A named individual – the “rapporteur” - is identified for each feature and, where necessary, for each component subtask of the feature. It is the rapporteur’s responsibility to monitor work, and, for example, to hold extra ad hoc meetings to ensure progress is made. He will also prepare a short report on the feature to each TSG meeting, and will maintain the WID, presenting any changes to the TSG for approval. To be adopted onto the work programme of 3GPP, each feature must have the support of at least four 3GPP individual member organizations, which agree to contribute actively to the development of the necessary technical specifications. A Work Item Description (WID) is prepared using a standard form, and is approved by the TSG. Project Management (2)
33
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 33 Feature 1 spec Most “features” are too complex to be handled as a whole, so each is broken down into a number component tasks (“building blocks”). Each of these components is managed independently, with the feature rapporteur coordinating progress. Project Management (3)
34
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 34 Project Management (4) Feature 1 spec Even building blocks may be too complicated to manage as a whole, and further functional decomposition to smaller “work tasks” is possible. } Features, building blocks and work tasks are generically known as “work items”. work items
35
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 35 Release N A new Release consists of the features of the old Release augmented with additional features of the new Release: Feature X Feature Y Feature Z Release N+1
36
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 36 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 X Feature Y Feature Z To Release N+2
37
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 37 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.
38
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 38 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.
39
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 39 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.
40
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 40 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.
41
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 41 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".
42
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 42 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.
43
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 43 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.
44
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 44 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 1 Stage 2 Stage 3 Feature Y Stage 1 Stage 2 Stage 3 Feature X Stage 1 Stage 2 Stage 3 Feature Z
45
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 45 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.
46
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 46 Stage 1 Stage 2 Stage 3 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.
47
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 47 Stage 1 Stage 2 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:
48
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 48 Stage 1 Stage 2 Stage 3 Feature Y Overall progress is estimated and monitored by the sum of the individual features. Stage 1 Stage 2 Stage 3 Feature X Stage 1 Stage 2 Stage 3 Feature Z
49
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 49 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:
50
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 50 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.
51
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 51 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 frozen
52
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 52 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).
53
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 53 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.
54
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 54 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.
55
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 55 Active project management
56
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 56 The 3GPP work plan can be consulted at: http://www.3gpp.org/ftp/Information/WORK_PLAN/ Active project management 3G Release 99 contained more or less the same functionality as GSM R99, but of course using the new UTRA radio access network technology (W-CDMA).
57
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 57 Release 4
58
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 58 Release 5
59
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 59 Release 6
60
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 60 Take a closer look at the project management techniques …
61
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 61 Take a closer look at the project management techniques …
62
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 62
63
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 63 The work plan is reviewed at every TSG SA meeting …
64
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 64
65
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 65
66
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 66 Every Feature (top level functional enhancement) is examined in sufficient detail to ensure that Its definition is (still) correct, and that Its definition is (still) correct, and that It is making adequate progress according to plan. It is making adequate progress according to plan.
67
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 67
68
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 68 Its Work Item Definition sheet is updated if necessary and re-issued as a TSG meeting document. This is the document which will be referred to in the next issue of the Work Plan. The Work Item Definition sheets are re-issued after each TSG SA meeting. You can find them at http://www.3gpp.org/ftp/Information/WI_Sheethttp://www.3gpp.org/ftp/Information/WI_Sheet. http://www.3gpp.org/ftp/Information/WI_Sheet
69
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 69 Its Work Plan is re-issued after each TSG SA meeting. You can find it at http://www.3gpp.org/ftp/Information/WORK_PLANhttp://www.3gpp.org/ftp/Information/WORK_PLAN. http://www.3gpp.org/ftp/Information/WORK_PLAN
70
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 70 1Introduction 2Rules and procedures 3Meetings 4Following the work 5Phased approach, Releases 6Project management, the Work Plan 7Specs: drafting, maintaining, …
71
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 71 Drafting and maintaining the technical specifications The work items result in new technical specifications, or enhancements to existing ones …
72
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 72 A named individual – the “rapporteur” - is identified for each spec. It is the rapporteur’s responsibility to initiate the drafting of the spec, and to maintain it throughout the drafting process. scribble scribble scribble scribble Spec numbers are allocated by the Support Team. The drafting process (1)
73
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 73 The rapporteur issues the specification as version 0.0.0 Release field Technical field Editorial field The Editorial field of the version number is incremented each time an editorial change is made to the document. It is reset to zero every time the Technical field is updated. The Technical field of the version number is incremented each time a technical change is made to the document. It is reset to zero every time the Release field is updated. The Release field of the version number is incremented each time major new functionality is made to the system (rather than to the individual document). The drafting process (2)
74
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 74 The initial draft is discussed in the working group. v0.0.0 v0.1.0 And a new draft is produced, bearing technical changes. The drafting process (3)
75
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 75 v0.1.0v0.2.0v0.3.0 … The process is iterative, until … v0.8.0 … the working group is happy with the draft. v1.0.0 Draft 1.0.0 is presented for information to the plenary TSG (Technical Body). The drafting process (3)
76
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 76 v1.0.0v1.1.0v1.2.0 … The document returns to the working group, and drafting continues until … v1.5.0 … the working group believes the draft to be stable enough to come under formal “change control”. v2.0.0 Draft 2.0.0 is presented for approval to the plenary TSG (Technical Body). The drafting process (4)
77
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 77 v2.0.0v2.1.0v2.2.0 … If the TSG does not approve the draft, it may return to the working group for further refinement. This is exceptional. v3.0.0v2.3.0 When the draft is approved to come under change control, it is upgraded to version 3.0.0 (assuming Release 1999 – see later). The drafting process (5)
78
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 78 The “system” is composed of a coherent set of related specifications. Change control (1) It is still possible to develop the standard further, to add the missing parts, and to correct errors and omissions as the overall system becomes better defined.
79
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 79 Consider an individual standard … v3.0.0 If the responsible working group wishes to make a change to it, however small, … … the working group must raise a Change Request. The CR consists of a cover page … … and an extract from the specification under consideration showing, using revision marks, all additions and deletions. http://www.3gpp.org/specs/CR.htm Change control (2)
80
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 80 For example, a CR to TS 23.456 may be twice revised during the course of 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. Change control (3)
81
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 81 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 together by the Support Team* prior to each TSG plenary. A single temp doc is created, with a cover page introducing each individual CR. * In practice, by the Secretary of the WG responsible for the spec. 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 number). Change control (4)
82
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 82 CR 4 rev 2 to 23.456 CR 5 rev 1 to 23.456 The Support Team (MCC) incorporates the approved CRs into the base specification … v3.0.0v3.1.0 Change control (5)
83
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 83 v3.1.0v3.2.0v3.3.0 … The controlled revision of specifications can continue in the same manner, with CRs being produced and approved. CRs allow full traceability of the changes wrought on a document since its original approval. Change control (6)
84
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 84 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 prove to be flawed. If necessary, back-track by de-implementing Change Requests which 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. Change control (7)
85
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 85 The initial “system” is composed of a coherent set of related standards. All these standards have version numbers of the form 3.y.z and are known as Release1999. Eventually, the functionality of Release 1999 became stable. The Release was “frozen”. Once frozen, no more functionality may be added to a Release (or, therefore, to its component specifications). Only essential corrections are permitted. Change control (8)
86
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 86 It is now possible to add further functionality in carefully designed features forming part of a new “Release”. Feature 1 specFeature 2 specFeature 3 spec Change control (9)
87
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 87 … it is possible to raise Change Requests to each specification to include the new functionality. v3.3.0 Change control (10)
88
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 88 v3.3.0v4.0.0v4.1.0 … The addition of the new features to the system implies an upgrade to the next “Release” of the entire system specification. Change control (11)
89
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 89 New functionality may equally result in an entirely new specification rather than a change to an existing one. v0.0.0 v1.0.0 2.0.0 v4.0.0 Change control (12)
90
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 90 Release 1999Release 4 The result, in due course, is two complete sets of specifications: one for each Release. Implementors (operators and equipment vendors) can choose which Release to build their systems to. Generally, newer Releases will be richer in features, but less tried and tested. Change control (13)
91
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 91 A disadvantage of the “release” approach … Release 1999Release 4 An error discovered here … … may require not one CR but two to fix it … … because the same error may have been inherited from the earlier Release! Note that maintaining several parallel releases of the same specification implies very well defined procedures and highly disciplined handling !! Change control (14)
92
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 92 A change control system along the lines described has enabled the GSM specifications to have undergone nine controlled releases, and has allowed a smooth transition from second generation digital mobile communications to third generation, re-using as many of the basic elements as possible. This mechanism requires meticulous project planning and control… Change control (15)
93
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 93 3GPP system Releases R99 functionally frozen December 1999. The basis for early 3G deployment in Japan, Isle of Man, Monaco, Italy, UK, and …many more in preparation.R99 functionally frozen December 1999. The basis for early 3G deployment in Japan, Isle of Man, Monaco, Italy, UK, and …many more in preparation. Rel-4 functionally frozen March 2001. Defines the low chip rate TDD mode of particular interest to China, but with high potential in other markets.Rel-4 functionally frozen March 2001. Defines the low chip rate TDD mode of particular interest to China, but with high potential in other markets. Rel-5 functionally frozen March/June 2002 – IMS phase 1Rel-5 functionally frozen March/June 2002 – IMS phase 1 Rel-6 expected to be functionally frozen in mid-2004Rel-6 expected to be functionally frozen in mid-2004
94
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 94 Short answer: on the 3GPP file server. http://www.3gpp.org/specs/specs.htm So where do I find the 3GPP Technical Specifications?
95
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 95 Longer answer: on the 3GPP file server. The following directories are maintained: So where do I find the 3GPP Technical Specifications? Meeting-related directories Hold all specs current as a result of implementing the approvals at the corresponding SA plenary meeting. Latest Holds the latest version of each spec currently under change control. Latest drafts Holds the latest version of each draft spec (i.e. those not yet under change control). Archive Holds every version of every spec, including stopped / withdrawn ones.
96
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 96 For more information please visit http://www.3gpp.org Or contact john.meredith@etsi.org
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.