Tdoc List

2016-08-22 13:44

Agenda Topic TDoc Title Source Type For Avail Treated Decision Wdrn Replaced-by Replaces
1 Opening of the meeting (Monday, 9 a.m.)                      
2 Approval of the agenda R6‑160001 Draft Agenda Convener (Nokia) agenda Approval Yes
YesNicklas JOHANSSON (Ericsson) volunteered to keep track of the RAN6 workplan in the future (see AI 9) The convener also presented a draft schedule of the meeting for which no comments were raised.
 		agreed No    
    R6‑160004 Void ETSI MCC discussion discussion No
Yes
 		withdrawn Yes    
3 General matters                      
3.1 Matters related to organization and way of working of the group R6‑160063 TSG RAN WG6 meeting organization and way of working convener (Nokia) discussion discussion Yes
Yesconclusion: GERAN #70 report will be reviewed by email over RAN6 reflector after RAN6 #1 to have a final report; Qualcomm: RAN6 may not need 5 days in the future conclusion: let's look at this again at the end of RAN6 #1 Qualcomm: probably enough to use one reflector, so no need for drafts reflector conclusion: let's see now many documents we will see on the drafts reflector in the future, if not really used then was can change the process and use one reflector only MCC: old reflectors will not be removed from the archive, just no longer be used Ericsson: can we have an earlier deadline for Tdocs? conclusion: Tdoc request and submission deadline will be 9pm CET (CEST in summer) on Fri one week before the meeting
 		noted No    
4 Liaisons / reports from other groups / meetings R6‑160055 LS on CS/PS coordination in GERAN Shared Networks (R3-161501; to: SA2; cc: GERAN2 = RAN6; contact: Ericsson) RAN3 LS in discussion Yes
Yespresented by Nicklas JOHANSSON (Ericsson) convener: RAN3 is fine with the proposal from SA2 to apply same approach as suggested by GERAN; no comments conclusion: no reply from RAN6 convener: GERAN #69 sent LSs to CT1 and SA3 where we are still wating for replies, GERAN #70 sent LSs to CT1 and CT4 as well also no response here so far; we will check what happened with them
 		noted No    
    R6‑160064 LS on Legacy Security Issues (S3-161224; to: RAN6, CT1; cc: CT6; contact: Qualcomm) SA3 LS in discussion Yes
No
 		available No    
5 Work related to Rel-13 or earlier features                      
5.1 eDRX_GSM R6‑160023 Clarification of CCCH_GROUP Determination Ericsson Inc. CR Decision Yes
No
 		available No    
    R6‑160024 Clarification of PEO codepoint usage Ericsson Inc. CR Decision Yes
No
 		available No    
    R6‑160025 Clarification of PEO codepoint usage Ericsson Inc. CR Decision Yes
No
 		available No    
5.2 CIoT_EC_GSM                      
5.2.1 Radio aspects R6‑160010 Miscellaneous corrections for EC-GSM-IoT Ericsson LM CR Decision Yes
No
 		available No    
    R6‑160026 Miscellaneous corrections for EC-GSM-IoT Ericsson LM CR Approval Yes
No
 		available No    
    R6‑160009 Miscellaneous corrections for EC-GSM-IoT Ericsson LM CR Decision Yes
No
 		available No    
    R6‑160050 Corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
No
 		available No    
    R6‑160030 Miscellaneous corrections for EC-GSM-IoT Ericsson LM CR Approval Yes
No
 		available No    
    R6‑160052 Corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
No
 		available No    
    R6‑160049 Corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
No
 		available No    
    R6‑160051 Corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
No
 		available No    
    R6‑160008 Miscellaneous corrections for EC-GSM-IoT Ericsson LM CR Decision Yes
No
 		available No    
    R6‑160047 Corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
Nomoved from AI 5.2.2 to AI 5.2.1
 		available No    
    R6‑160053 Corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
No
 		available No    
5.2.2 Performance aspects R6‑160002 CR 45.005 - EC-GSM-IoT UE Rx performance requirements MediaTek Inc. CR Approval Yes
No
 		available No    
    R6‑160013 Incremental redundancy requirement for EC-GSM-IoT Ericsson LM discussion Discussion Yes
No
 		available No    
    R6‑160014 Incremental redundancy requirement for EC-GSM-IoT Ericsson LM CR Decision Yes
No
 		available No    
    R6‑160027 Normalized coherency error requirements for EC-GSM-IoT MS Ericsson LM discussion Discussion Yes
No
 		available No    
    R6‑160028 Normalized coherency error requirements for EC-GSM-IoT MS Ericsson LM CR Approval Yes
No
 		available No    
    R6‑160015 BTS interference performance requirements for EC-GSM-IoT Ericsson LM, Nokia CR Decision No
No
 		reserved No    
    R6‑160016 BTS sensitivity performance requirements for EC-GSM-IoT Ericsson LM, Nokia CR Decision No
No
 		reserved No    
    R6‑160029 BTS sensitivity performance requirements for Overlaid CDMA Ericsson LM CR Approval No
No
 		reserved No    
    R6‑160048 Corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
No
 		available No    
5.2.3 Protocol aspects R6‑160019 44.014 Miscellaneous EC-GSM-IoT Changes Ericsson Inc. CR Decision Yes
Yesmoved from AI 5.2 to AI 5.2.3; presented by John DIACHINA (Ericsson); Nokia: there can be also gaps Ericsson: we could drop the "consecutive" Nokia: consequences if not approved has a typo Ericsson: can be fixed convener: source to TSG should be R6 44.014 as Core or Perf spec? Ericsson: is more related to mobile conformance testing convener: agrees there are no Perf. figures, we can keep it under Core part
 		revised No R6‑160056  
    R6‑160056 44.014 Miscellaneous EC-GSM-IoT Changes Ericsson Inc. CR Decision No
No
 		reserved No   R6‑160019
    R6‑160020 Miscellaneous EC-GSM-IoT Changes Ericsson Inc. CR Decision Yes
Yesmoved from AI 5.2 to AI 5.2.3; presented by John DIACHINA (Ericsson) MCC: should say -Core in WI code and instead of R6.2 use R6 Ericsson: instead of PG1 it should have PG with superscript 1 but the formatting change is not visible convener: 3.3.1.2: text should be in italics or in primes? Ericsson: tried to follow 24.008 but can double-check convener: remove one "to", should say just "is set to" (problem occurs in multiple places) Nokia: 3.5.1a.1: "last reported" correct? means last reported to core network or expected DL coverage class? Ericsson: last reported in UL unit data Nokia: "last reported to core network" would be clear but not sure whether core network is intended here; or also possible "last selected" convener: what is the ambiguity that we see here? Ericsson: BSS may overwrite what MS considered and then "last reported" may not be so clear/relevant Qualcomm: thinks that sentence is ok, MS can not do anything if BSS does something else Ericsson: "last reported in a system access" would probably be better after offline discussion: Ericsson: we will clarify that "last reported" is related to what MS reports (i,e EC-packet channel request message) Nokia: "selected DL coverage class" Ericsson: but network may assign something else than what mobile selects Nokia: is "selected" the final one? Ericsson: yes
 		revised No R6‑160057  
    R6‑160057 Miscellaneous EC-GSM-IoT Changes Ericsson Inc. CR Decision No
No
 		reserved No   R6‑160020
    R6‑160021 Miscellaneous EC-GSM-IoT Changes Ericsson Inc. CR Decision Yes
Yesmoved from AI 5.2 to AI 5.2.3; presented by John DIACHINA (Ericsson) convener: -Core missing in WI code, R6.2 => R6, some spaces missing in CR text Qualcomm: 2nd sentence confusing: transmission in DL? Ericsson: yes, as we talk about DL coverage class; but fine to rephrase Qualcomm: needs to be corrected in 2 places
 		revised No R6‑160058  
    R6‑160058 Miscellaneous EC-GSM-IoT Changes Ericsson Inc. CR Decision No
No
 		reserved No   R6‑160021
    R6‑160022 Miscellaneous EC-GSM-IoT Changes Ericsson Inc. CR Decision Yes
Yesmoved from AI 5.2 to AI 5.2.3; presented by John DIACHINA (Ericsson) convener: -Core missing in WI code, R6.2 => R6 Nokia: cat.D? MCC: please make sure the change is visible
 		revised No R6‑160059  
    R6‑160059 Miscellaneous EC-GSM-IoT Changes Ericsson Inc. CR Decision No
No
 		reserved No   R6‑160022
    R6‑160003 Updates of the naming convention from EC-EGPRS to EC-GSM-IoT CATR CR   Yes
Yespresented by Yuan DONG (CATR) Ericsson: this CR is completely included in R6-160020 conclusion: CR was merged into R6-160020
 		merged No    
    R6‑160037 Miscellaneous corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
Yespresented by Deepak PRABHU KANLUR (Nokia) Ericsson: changes to table Table 3.5.1a.1 not needed as covered in R6-160020; Nokia: ok, will be removed convener: use WI code -Core
 		revised No R6‑160060  
    R6‑160060 Miscellaneous corrections to EC-GSM-IoT Nokia Networks CR Decision No
No
 		reserved No   R6‑160037
    R6‑160038 Miscellaneous corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
Yespresented by Deepak PRABHU KANLUR (Nokia) convener: use WI code -Core Ericsson: 2nd sentence in defintion: should better say "EC-TBF uses"; TB-flow identity: under5.2.2 better remove "concurrently"; table change unclear Nokia: fine with definition change; agrees to remove "concurrently" but we talk about one mobile convener: agrees that for same mobile "concurrent" is unclear Qualcomm: same value possible for different mobiles but only one will react; so "concurrent" is needed; Ericsson: we could add one additional sentence: "EC-devices do not support concurrent TBFs" convener: we do not need to have (E)GPRS and EC-GSM-IoT in the same sentence, i.e. we could have an extra sentence for EC-GSM-IoT Qualcomm: or just clarify that last part of sentence is different for EC-GSM-IoT
 		revised No R6‑160061  
    R6‑160061 Miscellaneous corrections to EC-GSM-IoT Nokia Networks CR Decision No
No
 		reserved No   R6‑160038
    R6‑160039 Miscellaneous corrections to EC-GSM-IoT Nokia Networks CR Decision Yes
Yespresented by Deepak PRABHU KANLUR (Nokia) Ericsson: maybe better split 2nd bullet in 6.2 into 2 bullets; 7.1a.1 & 7.1a.3 c change: clear from the title so not really needed; Qualcomm: 6.2: change linked to UL TBF mode convener: for 2nd change in 7.1a.1 we wanted to clarify this Ericsson: worried to that addtiional text can cause additional confusion conclusion: first change will be modified, changes in 7.1a.1 & 7.1a.3 not needed
 		revised No R6‑160062  
    R6‑160062 Miscellaneous corrections to EC-GSM-IoT Nokia Networks CR Decision No
No
 		reserved No   R6‑160039
    R6‑160040 Uplink Transmission Opportunities indicated in FUA Nokia Networks discussion discussion Yes
No
 		available No    
    R6‑160041 Start First UL data Block coding bit Nokia Networks CR Decision Yes
No
 		available No    
5.3 CSPS_Coord_GERAN R6‑160007 Correction to CSPS coordination in shared networks Ericsson LM CR Agreement Yes
No
 		available No    
5.4 Any other documents related to Rel-13 or earlier features                      
6 Work related to Rel-14                      
6.1 Positioning enhancements for GERAN (work item ePOS_GERAN) R6‑160006 Multilateration Energy Consumption Analysis Ericsson LM discussion Discussion Yes
No
 		available No    
    R6‑160018 Multilateration Signaling Procedures Ericsson Inc. discussion Discussion Yes
No
 		available No    
    R6‑160034 Radio Interface Enhancements for TA based multilateration Nokia Networks discussion Discussion Yes
Yes
 		revised No R6‑160054  
    R6‑160054 Radio Interface Enhancements for TA based multilateration Nokia Networks discussion Discussion No
No
 		reserved No   R6‑160034
    R6‑160035 Energy efficient hybrid TA/OTD multilateration for neighbour cells in extended coverage Nokia Networks discussion Discussion Yes
No
 		available No    
    R6‑160036 Energy Consumption Analysis of Radio Interface Procedures for Positioning Enhancements Nokia Networks discussion Discussion Yes
No
 		available No    
6.1.1 Radio aspects                      
6.1.2 Performance aspects R6‑160011 Simulations for positioning enhancements – Assumptions Ericsson LM discussion Discussion Yes
No
 		available No    
    R6‑160012 System level simulations for positioning enhancements – Methods and Results Ericsson LM discussion Discussion Yes
No
 		available No    
6.1.3 Protocol aspects                      
6.2 Dedicated core networks for GERAN (work item DECOR-GERAN) R6‑160017 DECOR - Way forward Ericsson Inc. discussion Discussion Yes
No
 		available No    
    R6‑160005 Introduction of Dedicated Core Networks in GERAN Ericsson LM CR Agreement Yes
No
 		available No    
6.3 Small technical enhancements and improvements (work item TEI)                      
6.4 Downlink MIMO for GERAN (study item DOMIMO) R6‑160042 pCR 45.871 Downlink MIMO – Mode and Link Adaptation Nokia Networks pCR Decision Yes
No
 		available No    
    R6‑160043 pCR 45.871 Downlink MIMO – Signalling Nokia Networks pCR Decision Yes
No
 		available No    
    R6‑160044 Compatibility Analysis of Downlink MIMO for GERAN Nokia Networks discussion discussion Yes
No
 		available No    
    R6‑160045 pCR 45.871 Downlink MIMO – Compatibility Analysis Nokia Networks pCR Decision Yes
No
 		available No    
    R6‑160046 pCR 45.871 Downlink MIMO – Conclusion Nokia Networks pCR Decision Yes
No
 		available No    
6.5 Any other Rel-14 documents R6‑160031 Alternative mappings for EC-GSM-IoT higher coverage classes Nokia Networks discussion Discussion Yes
No
 		available No    
    R6‑160032 EC-GSM-IoT New Channel Formats for Short Packets with NIDD CN Nokia Networks discussion Discussion Yes
No
 		available No    
    R6‑160033 New WID on Radio Interface Enhancements for EC-GSM-IoT Nokia Networks WID new Agreement Yes
No
 		available No    
7 Any other technical work                      
8 Liaison and output to other groups                      
9 Revision of the work plan                      
10 Future meetings                      
11 Any other business                      
12 Close of the meeting (no later than Friday, 5.30 p.m.)