From: Joern Krause <Joern.Krause@ETSI.ORG>

Sent: Donnerstag, 3. November 2016 03:21

To: 3GPP_TSG_RAN@LIST.ETSI.ORG

Subject: WI summary handling in RAN

Attachments: WI_summary_template.zip

Dear WI rapporteurs and all,

As you may remember, TSG #73 concluded to have such a WI summary

since WIDs alone do not provide a proper description that can be used e.g.

for REL summaries (e.g. for ITU-R) or for information for so called "verticals".

Please find attached the corresponding template to be used for RAN #74 (same template will be used in CT & SA).

1. Who has to provide such a WI summary?

- If you are a rapporteur of a Core part WI that you declare to be 100% complete at RAN #74 and that is not spectrum related,

then it is your task as a rapporteur to submit also a technically correct WI summary Tdoc (using the attached template) to RAN #74.

- This means: NO WI summary for SIs, RAN5 WIs, RAN4/RAN6 Perf. part WIs.

- Please do not forget this task and request a Tdoc for it via 3GU. If the WI summary is not provided, then we will not consider your WI complete.

- At the end of this email you find a list of all WIs that are planned to be completed by RAN #74 and that would then

require a WI summary. Of course if your WI is not complete by RAN #74, then also no WI summary is needed so far.

And if there is any other Core part WI (not spectrum related) which is completed at RAN #74 and earlier than originally planned

and therefore not listed in the table below, then you still have to provide a WI summary to RAN #74.

2. What is supposed to be in the WI summary?

- See the guidance text in the attached template.

- Remember that this is a description of the key functionalities of your WI that ended in the 3GPP specifications.

E.g. options that were discussed but not covered in the specs shall not be part of your WI summary.

- It is neither supposed to be pure "marketing blabla" with unrealistic promises

nor a stage 3 message flow where noone understands what the messages are for.

- The easiest test for a high quality WI summary is to give your WI summary to a colleague who was not at all involved in your WI,

let the colleague read your summary, and explain you afterwards in own words what does your WI do, why it is needed,

what are the advantages and limitations of your WI and what are its relations to the existing 3GPP standard.

The closer the colleague summary is getting to the reality, the better is your WI summary.

- In the same context: Make sure that the reader understands your abbreviations and terms/definitions.

3. How will we handle WI summaries at RAN?

- WI summaries will not be part of the block approval, i.e. they have to be presented and discussed (if necessary).

- WI summaries shall be technically correct. This means (like for status reports) the rapporteur is supposed to provide a draft

version via the reflector of the leading WG of the WI (and optionally also to reflectors of other involved WGs) for review

before a final version is submitted to RAN.

- RAN will note WI summaries and not approve them BUT it is strongly recommended to strive for high quality summaries because

- if the WI is not technically correct or missing an essential aspect, then the rapporteur will get a Tdoc number to revise the WI summary during the RAN meeting;

- your WI summary will be a reference document for your WI 3GPP internally and externally;

- the source of the WI summary will have your company's name

- I will be less picky with the submission deadline of WI summaries (as you may have last minute email discussions to finish your WI) BUT

please make sure that you request a Tdoc for your WI summary before the Tdoc request deadline

(if you are in doubt whether you reach the 100% or not, then better request a Tdoc for a WI summary; we can still withdraw it if it is not yet needed).

4. What will we do with your WI summary after the RAN meeting?

- We will archive them under ftp://ftp.3gpp.org/Information/WORK_PLAN/WI_summaries

- We will use them for producing REL summaries or other summaries.

- They may also be reused on the 3GPP web page or provided to external fora/companies who seek information.

5. Under which conditions will we update WI summaries of RAN #74 at future RAN meetings?

- When a WI is declared to be 100% complete, it is assumed that all key functions of a WI are clear and fixed.

That's why normally it is assumed that the WI summary is final, once it is found to be technically correct and noted by RAN.

- But there are cases where the TSG can consider a revision of a former WI summary: e.g.

- an essential correction is modifying the key functions of this WI so that the WI summary would be in contradition to the 3GPP specs

- a later extension or modification of the functionality via a TEI CR

6. How does the WI summary work for TSG wide features?

- The process described above applies to TSG RAN.

- TSG CT and TSG SA will also have WI summaries. However, as they may have multiple sub-WIs to one feature, the TSG CT/SA leaders

will coordinate how the summary will be produced (e.g. joint summaries of a few WGs, or enhancing summaries step by step whenever another WG has completed its work).

- Independent from WI summaries or REL summaries, the TSGs may decide to produce a feature summary based on the different WI summaries which together build a feature.

However, as it was found that immediate information is essential, the WI summary is the standard process and feature summaries may come later on a case by case basis.

In case you have any questions related to WI summaries, please send me an email.

BR

Joern

12 Core part WIs that are not spectrum related and that are planned to complete at RAN #74: The rapporteurs of these WIs are included in this email.

UID | Acronym | Title | REL | leading WG | other impacted WGs | started | finished or target | completion level in % | status | latest WID/SID | latest status report | F, BB, WT, SI | rapporteur | affected | comments | RAN #74 agenda item
700160 | LTE_eLAA-Core | Core part: Enhanced LAA for LTE | REL-14 | R1 | R2, R4 | Dec.15 | Dec.16 | 92 | open | RP-161832 | RP-161581 | BB | Ericsson | LTE | follow-up WI of REL-13 WI LTE_LAA | 10.04.01
700181 | LTE_high_speed-Core | Core part: Performance enhancements for high speed scenario in LTE | REL-14 | R4 | - | Dec.15 | Dec.16 | 45 | open | RP-160172 | RP-161483 | BB | NTT DOCOMO | LTE | follow-up WI of SI REL-13 FS_LTE_high_speed | 10.04.03
710178 | LTE_eMob-Core | Core part: Further mobility enhancements in LTE | REL-14 | R2 | R3, R4 | March 16 | Dec.16 | 50 | open | RP-160921 | RP-161700 | BB | ZTE | LTE | no Perf. part | 10.04.08
710182 | LTE_SRS_switch-Core | Core part: SRS (sounding reference signal) switching between LTE component carriers | REL-14 | R1 | R2, R4 | March 16 | Dec.16 | 55 | open | RP-160935 | RP-161662 | BB | Huawei | LTE |  | 10.04.11
710184 | LTE_MUST-Core | Core part: Downlink Multiuser Superposition Transmission for LTE | REL-14 | R1 | R2, R4 | March 16 | Dec.16 | 60 | open | RP-161019 | RP-161732 | BB | MediaTek | LTE |  | 10.04.12
730184 | LTE_4Rx_AP_DL_CA-Core | Core part: 4 receiver (RX) antenna ports with Carrier Aggregation (CA) for LTE downlink (DL) | REL-14 | R4 | - | Sep.16 | Dec.16 | 0 | new | RP-161897 | - | BB | Ericsson | LTE | related to REL-13 WI LTE_4Rx_AP_DL | 10.04.20
730185 | LTE_UE_cat_1RX-Core | Core part: Requirements for a new UE category with single receiver based on Category 1 for LTE | REL-14 | R4 |  | Sep.16 | Dec.16 | 0 | new | RP-161898 | - | BB | Qualcomm | LTE |  | 10.04.21
700180 | MB_BS_test_3B-Core | Core part: Multi-Band Base Station testing with three or more bands | REL-14 | R4 | - | Dec.15 | Dec.16 | 95 | open | RP-160063 | RP-161453 | BB | Alcatel-Lucent | UTRA, LTE | B8_B20_B28 as starting point | 10.05.01
710172 | UTRA_LTE_iPos_enh2-Core | Core part: Further Indoor Positioning Enhancements for UTRA and LTE | REL-14 | R2 | R1, R3, R4 | March 16 | Dec.16 | 60 | open | RP-161850 | RP-161851 | BB | Huawei | UTRA, LTE | follow-up WI of REL-13 WI UTRA_LTE_iPos_enh | 10.05.02
580137 | LTE_UTRA_TRP_TRS-Core | Core part: LTE UE TRP and TRS and UTRA Hand Phantom related UE TRP and TRS Requirements | REL-14 | R4 |  | Dec.12 | Dec.16 | 60 | open | RP-161323 | RP-161529 | BB | Telecom Italia | UTRA, LTE | no perf. part; follow-up WI of the RAN4 SIs FS_LTE_OTA and FS_OTA_phantoms_UTRA both completed at RAN #57; TRP = total radiated power, TRS = total radiated sensitivity; WI was shifted from REL-12 to REL-13 at RAN #66; WI was shifted from REL-13 to REL-14 at RAN #72; TS 37.144 | 10.05.04
700163 | FACH_DTXDRX-Core | Core part: DTX/DRX enhancements in CELL_FACH | REL-14 | R2 | R1, R3 | Dec.15 | Dec.16 | 65 | open | RP-160601 | RP-161658 | BB | Huawei | UTRA | no Perf. part | 11.2.1
720194 | UTRA_MCe-Core | Core part: Multi-Carrier Enhancements for UMTS | REL-14 | R2 | R1, R4 | June 16 | Dec.16 | 35 | open | RP-161259 | RP-161657 | BB | Huawei, HiSilicon | UTRA | no Perf. part; follow-up WI of REL-14 SI FS_UTRA_MCe | 11.2.2

------------------------------------

Joern Krause, ETSI MCC

joern.krause@etsi.org