1 / 11

19 - 23 May, 2014 Seoul, Korea Tuomo Säynäjäkangas RAN4 Chairman

3GPP RAN4#71 Meeting Arrangement. 19 - 23 May, 2014 Seoul, Korea Tuomo Säynäjäkangas RAN4 Chairman. Meeting arrangement. Common session Mon morning and Fri afternoon (Harmony ballroom 3) RF and frequency bands Mon - Fri (Harmony ballroom 3) RRM and demodulation

lam
Download Presentation

19 - 23 May, 2014 Seoul, Korea Tuomo Säynäjäkangas RAN4 Chairman

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 3GPP RAN4#71 Meeting Arrangement 19 - 23 May, 2014 Seoul, Korea Tuomo Säynäjäkangas RAN4 Chairman

  2. Meeting arrangement • Common session • Mon morning and Fri afternoon • (Harmony ballroom 3) • RF and frequency bands • Mon - Fri (Harmony ballroom 3) • RRM and demodulation • Mon – Fri (Jupiter)

  3. ADN guideline • Deadline for Tdoc number request: 10:59 pm UTC, Thu 8 May • Secretary allocate CR numbers and provide Tdoc list by 10:59 pm UTC on Fri 9 May • Delay the CR submission until you get the CR number • Deadline for Tdoc submission: 10:59 pm UTC, Mon 12 May • Send documents to secretary by mail • Documents received after deadline will not be uploaded and be marked as late • Info to ADN • Abstract field • Summary the content of the document • Following information is needed in specific new fields • Specification  => Mandatory for all CR • CR category      => Mandatory for all CR • Release            => To be filled for all Documents (Mandatory for all CR) • WI code            => To be filled for all Documents (Mandatory for all CR) • Document for     => CR/Approval/Discussion… to be filled for all Documents

  4. Document handling guideline • ADN for Tdoc request will be closed on Thu, 8 May, 10:59 pm UTC • Not possible to reserve Tdoc numbers or update information fields after 8 May • Documents missing Tdoc submission deadline 10:59 pm UTC on Mon, 12 May will be marked as late and won’t be treated • Please pay attention to presentation time => brief summaries • Chairmen will distribute meeting minutes daily • Revisions / new tdoc numbers allocated only by the judgment of the chairmen • During meeting the deadline for tdoc request is Thu, 22 May, end of the meeting session • During meeting the deadline for tdoc submission is Fri, 23 May, 2:00 pm • Note: Inbox will be closed at 2:00 pm • Please pay attention when you use the reflector to circulate draft documents. If the attachment name matches the pattern ‘R4-14xxxx.zip’, it will be automatically uploaded to the 3gpp ftp server as an official document • Only official Tdocs (with proper number) from the inbox/documents folder are formally discussed in the meeting

  5. CR guideline • Use the latest CR cover sheet, CR-Form-v11 • No revision marks on the CR cover sheet • Use 4 digits CR numbers • As source to TSG use the format ”R4” • Correct version/release of specification must be used as a baseline • Regarding WI codes • RULE 1: Avoid TEIx whenever possible • RULE 2: Cat.A CRs have the same WI code as their Cat.F CRs • Use the same agenda for both Cat.F and corresponding Cat.A CRs • RULE 3: The WI code of a REL-x Cat.F CR has to indicate a REL-x WI code/acronym • Category A CR handling • Do not submit Cat A CRs before the meeting • Request Tdoc numbers for Cat A CRs before the deadline • Submit Cat A CRs only once the Cat F CR is agreed during the meeting • Cat A CR is a mirror CR • Same changes as those proposed in the CR for an earlier release • Cat A CR does not need to be in line to the last comma with the Cat F CR but it has to achieve the same functionality/behaviour • E.g. mirror CRs for 36.307/25.307 can be 'A' instead of 'F' even though they have different band lists in each release

  6. CR handling • RAN4 do direct agreement of the CRs in Bis-meetings • No endorsements to be ratified in following regular meeting • Same base line specs will be used as a basis for CRs in both Bis meetings and regular meetings • Mar 2014 specs (RP#63) as a basis for CRs in both RAN4#70bis and RAN4#71 • Agreed CRs in Bis-meeting shall not be used as a basis for CRs in following regular meeting RAN4#71 • Possible conflicts with CRs will be treated case by case in regular meeting • Proponent of the CR has responsibility to check possible overlapping parts and possible references to new clauses in agreed CRs • In RAN4#71 mark overlapping parts / references to new clauses by highlight / comment and mention in the cover sheet + during the presentation

  7. Monday, 19 May, 2014

  8. Tuesday, 20 May, 2014

  9. Wednesday, 21 May, 2014

  10. Thursday, 22 May, 2014

  11. Friday, 23 May, 2014

More Related