Overview of 3GPP Change Control Procedures. Presentation to 3GPP2 TSG-A

Transcription

1 Overview of 3GPP Change Control Procedures Presentation to 3GPP2 TSG-A

2 Drafts Drafts are not under change control Future Technical Specification (TS) or Technical Report (TR) number is assigned during drafting. Version numbers 0.y.z - 1.y.z are used for drafts When ready, WG presents a draft in version to the TSG plenary for approval. It then becomes a TR or TS. Upon approval, the version number is uped to version if it belongs to Release if it belongs to Release if it belongs to Release 5

3 Release 3GPP maintains several releases, which are distinguished by their supported features R99 completed in March 2000 Rel-4, completed in March 2001 Rel-5, to be completed in December 2001 Later versions of the same TS/TR within the same release supersede earlier versions. After completion of a release, no new TRs or TSs and only essential corrections may be approved.

4 Change Request (CR) All changes to a TS/TR must be submitted in the form of a CR. A CR consists of a cover sheet, explaining the change(s) modified sections with revision marks Normal path: Company delegate presents CR to WG who owns the TR/TS WG agrees to the CR TSG plenary approves CR CR is incorporated into next version of the TR/TS (4x/y)

5 3GPP TSG-CN WG1 Meeting #14 Tdoc N Cardiff, South Wales, November 2000 (revised from N ) CHANGE REQUEST! CR 262! rev 1! Current version: 4.0.0! CR-Form-v3 For HELP on using this form, see bottom of this page or look at the pop-up text over the! symbols. Proposed change affects:! (U)SIM ME/UE X Radio Access Network X Core Network Title:! The Group or Broadcast Call Reference from the mobile station to the network Source:! STF139 / SAGEM Work item code:! ASCI Date:! 23 Nov Category:! C Release:! REL-4 Use one of the following categories: F (essential correction) A (corresponds to a correction in an earlier release) B (Addition of feature), C (Functional modification of feature) D (Editorial modification) Detailed explanations of the above categories can be found in 3GPP TR Use one of the following releases: 2 (GSM Phase 2) R96 (Release 1996) R97 (Release 1997) R98 (Release 1998) R99 (Release 1999) REL-4 (Release 4) REL-5 (Release 5) Reason for change:! Summary of change:! Consequences if! not approved: The purpose is to distinguish relevant information send by the network to the mobile from the relevant information send by the mobile to the network. Add separate specifications for the information sent by the network and sent by the mobile station. Unnecessary implementations in the mobile. Clauses affected:! Other specs! Other core specifications! affected: Test specifications O&M Specifications Other comments:! How to create CRs using this form: Comprehensive information and tips about how to create CRs can be found at: Below is a brief summary: 1) Fill out the above form. The symbols above marked! contain pop-up help information about the field that they are closest to. 2) Obtain the latest version for the release of the specification to which the change is proposed. Use the MS

6 Annex N (informative): Change Record Release 4 for 3GPP TS v4.0.0 is based on 3GPP TS version Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New TSG-CN- 9 New release 4 for , based on V3.5.0 which was approved at the same Plenary NP-09 NP CC Enhancements for Codec Selection NP-09 NP Emergency Call Additions NP-10 NP The Group or Broadcast Call Reference from the mobile station to the network NP-10 NP GSM 700 addition into MS classmark & radio access capability IE NP-10 NP Clarification to the network initiated GPRS detach procedure (IMSI detach) NP-10 NP Correction of update status on Authentication Reject NP-10 NP Description Of Timer T3317 on expiry NP-10 NP Removal of recently deactivated condition for PDP contexts and some references corrections NP-10 NP The application of security procedures to emergency calls NP-10 NP Updating of Bearer Capability IE NP-10 NP khz multimedia calls at 33.6 kbit/s data rate NP-10 NP kbit/s UDI/RDI multimedia NP-10 NP Change of reference to for use of codec bitmap in the Supported Codec List NP-10 NP Introduction of EGPRS for DTM NP-10 NP Clarification of response handling of Service Request NP-10 NP Clarification of RAB re-establishment NP-10 NP APN used for detection of duplicated PDP context activation NP-10 NP Unsynchronized PDP contexts handling - MS less NP-10 NP Correction on TFT setting condition NP-10 NP Correction of the timer list NP-10 NP Correction of PDP context duplication handling NP-10 NP DRX parameter range correction NP-10 NP RR connection replaced with PS signalling connection Jan-01 Correction of the version and date in the Header title /Page

7 The CR database Meeting-1st-Level NP-10 Doc-1st-Level NP Status-1st-Level approved Spec CR 262 Rev 1 Phase Rel-4 Subject The Group or Broadcast Call Reference from the mobile station to the network Cat C Version-Current Version-New Date 11/29/00 Source-1st-Level N1 WG-Responsible N1 Meeting-2nd-Level N1-14 Doc-2nd-Level N Status-2nd-Level agreed Workitem ASCI Presentation No Remarks Rel4 Record-Trace

8 Benefits of Change Control Eases revision tracking for the users of the standards (i.e., vendors and carriers) Categorization of changes into editorial, essential corrections, new/enhanced features, etc. Natural grouping of related changes into one CR. Exact correspondence between approved CRs and actual changes in the standards Formal approach, leaves less to editor s discretion and (mis)understanding. Obsoletes V&V procedures! Reasons for changes are recorded.

9 Drawbacks More discipline and preparation time required from the delegate submitting the CR. The delegate submitting the CR is in charge of revising the CR according to comments and ensuring that it can be approved at the closing plenary session => more work for delegate during meeting Requires specification to be fairly mature to avoid too many CRs Does not allow comments to be postponed to V&V. Plan sufficient time for CR handling during meetings. 3GPP2 member organizations (SDOs) may not adopt the same change control procedures. Ballot comments need to be reflected as CRs.

10 Further Reading 3GPP TR V3.6.0 Technical Specification Group working methods