3GPP TSG RAN1/2 ITRI TW4G RAN1 RAN2 3GPP LTE-Advanced Rel9: 3GPP Rel9 study item LTE-Advanced feasibility study LTE-Advanced ITU-R ITRI LTE-Advanced f

Size: px

Start display at page:

Download "3GPP TSG RAN1/2 ITRI TW4G RAN1 RAN2 3GPP LTE-Advanced Rel9: 3GPP Rel9 study item LTE-Advanced feasibility study LTE-Advanced ITU-R ITRI LTE-Advanced f"

象视华
6 years ago
Views:

1 3GPP TSG RAN WG1 #55bis WG2 #64bis

2 3GPP TSG RAN1/2 ITRI TW4G RAN1 RAN2 3GPP LTE-Advanced Rel9: 3GPP Rel9 study item LTE-Advanced feasibility study LTE-Advanced ITU-R ITRI LTE-Advanced features ITRI Home enb Rel9: Home enb, Rel9 home enb SA2 work item work item working group 3GPP LTE Rel8: LTE Rel8 (freezing) change request Rel8 ITRI review Rel8 Rel8 change request LTE-Advance Home enb TDD LTE 3GPP LTE 1. Join GPP RAN1discussion Find out potential research topics for LTE-Advance 2. Capture the ideas of contributions provided by some companies. 1. Following the status of LTE Rel8/9 & LTE-A Rel9 2. Looking for the potential issues on HeNB & MBMS for LTE Rel8/9 and LTE-A Rel9 1. Joining discussion of RRC and system architecture issues 2. Obtain the new LTE C-plan isssues 1. LTE-A RAN2 2. contributions 3GPP RAN1 RAN2 (Slovenia) 2

3 (Ljubljana) RAN LTE LTE-Advanced LTE-Advanced DFT precoding OFDM LTE RAN1 : LTE LTE-A LTE LTE-Advanced RAN2 LTE Rel8/9 LTE-A Rel9 HeNB Rel8/9 LTE U-plane C-plane Obtaining the latest work items, schedule, and working principles for LTE Rel9 & LTE-A Rel9 Obtaining potential issues on HeNB & MBMS for LTE Rel8/9 & LTE-A Rel9 U-plane MAC Layer Obtain the status and discussion on LTE MAC layer. Obtain the potential research issues on LTE MAC layer. C-plane RRC Obtain the status and discussion as well as the remaining issues on LTE RRC layer. Acquire the updated status and discussion for HeNB.Obtain the status and discussion on LTE MAC layer. RAN2 U-plane C-plane 3

5 3GPP TSG RAN WG1 #55b Meeting 3GPP TSG RAN WG2 #64b Meeting RAN1 Slovenia Ljubljana 3GPP RAN1 #55bis LTE LTE-Advanced : ( ). LTE (TS ~36.213) (feature frozen) ( ). LTE-A ( ). LTE-A study item LTE-Advance : LTE-Advanced ( ). RAN2 Obtaining the latest work items, schedule, and working principles for LTE Rel9 & LTE-A Rel9 Obtaining potential issues on HeNB & MBMS for LTE Rel8/9 & LTE-A Rel9 Obtain the status and discussion on LTE MAC layer. Obtain the potential research issues on LTE MAC layer. Obtain the status and discussion as well as the remaining issues on LTE RRC layer. Acquire the updated status and discussion for HeNB January (Slovenia), (Ljubljana) 5

6 RAN1 Mon: 09:00-19:30 Opening the meeting Call for IPR Approval of the minutes from previous meeting Approval Agenda Liaison statement handling Maintenance of Evolved UTRA and UTRAN Correction for TS Correction for TS Tues: 09:00-18:25 Correction for TS In Ad hoc room, below topics are discussed Continuous Connectivity for Packet Data Users for 1.28Mcps TDD Discussion on UTRA Multi-Carrier Evolution Maintenance of Rel-99~Rel-8 Wed: 09:00-20:00 Study item on LTE-A UL transmission scheme Bandwidth extension In Ad hoc room, DL MIMO extension up to 8x8 Thur: 09:00-20:00 DL MIMO extension up to 8x8 Relaying Coordinated Multipoint Transmission/Reception (CoMP) In Ad hoc room, UL MIMO extension up to 4x4 and DL MIMO extension up to 8x8 Fri: 09:00 17:15 Revision of some documents that discussed in previous days Positioning support for LTE Study item on E-UTRAN mobility Evaluation and Enhancement 6

7 RAN2 LTE U-plane session LTE C-plane session Draft schedule Session 1 Session 2 Session 3 Monday Morning Organisation [2, 3] LTE [5] UMTS [7] starts from coffee break Monday Afternoon LTE [5] UMTS [7] Monday 18:00 -> Joint [4] Tuesday LTE [5] Will split during the day UMTS [7] in CP/UP LTE UP [6.1] Wednesday LTE CP [6.2] LTE UP [6.1] UMTS [7] Thursday LTE CP [6.2] LTE UP [6.1] Friday Reporting LTE CP/UP Left-overs [5, 6.3] Outgoing LTE liaisons coffee break LTE UMTS session LTE UMTS LTE session C-plane U-plane session The meeting agenda and timetable is shown in Tab 1. I attended the U-plan session. The following are agreements that are achieved during RAN 64 meeting for U-plane session: RAN1: : 1. LTE-A : (1) PUSCH MIMO non-mimo, SC-FDMA DFT-Precoding cubic metric SC-FDMA : Alcatel-Lucent, AT&T, Ericsson, Huawei, NEC, Nokia, Nokia Siemens Networks, Qualcomm Europe, RIM, Sharp, Texas Instruments, ZTE, Freescale, RITT, CATT, Philips, Orange, Panasonic, Magnolia BB, CEWiT, 7

8 TD-Tech. OFDMA : Nortel, DoCoMo, LGE, Samsung, Fujitsu, Toshiba, Mitsubishi, T-Mobile, Icera Semiconductor, Wavesat, KDDI, Vodafone Also supported by LG-NT, HTC. OFDMA SC-FDMA (2) PUSCH PUCCH PUSCH PUCCH TDM multiplexing (Rel-8) 2. component carrier (CC) DFT RB : FFS: Rel-8 DL (RB allocation type 0 and/or 1) FFS: DCI format 3. CoMP (1) UE single cell (anchor cell) PDCCH (2) CoMP UE active CoMP cell 4. DL RS(for CoMP, multiple-stream beamforming, and >4TX antenna ports MIMO) (1) 2 RS: DM RS (for PDSCH) CQI-RS (for CQI/PMI/RS reporting) Rel-8 RS DM/CQI RS (2) precoded RS non-precoded RS (3) Rel-8 transmission scheme Rel-8 cell-specific and/or UE-specific RS 5. LTE (1) TDD mode special subframe UpPTS/DwPTS/GI (2) PUSCH mirroring function Nsb=2, Nsb>2 hopping (3) DCI format 1B gap ASUS RAN2: U-plane 1. ACK/NACK repetition: 8

9 1-1 RAN1 UE cell edge UE ACK/NACK ACK/NACK( ) MAC TDD mode DRX mode HARQ RTT Timer ACK/NACK ACK/NACK HARQ RTT Timer DRX Retransmission Timer Timer MAC discussion liaison RAN1 RAN1 1-2 ACK/NACK repetition measurement gap ACK/NACK MAC liaison RAN1 RAN1 2. ACK for UL SPS Explicit Release UL SPS explicit release enb UE release SPS UE ACK UE release message enb UE enb UE release message ACK ( ) RAN1 liaison RAN1 RAN1 ACK 3. TTI bundling TTI bundling UE UL HARQ process ID TTI bundling pattern UE pattern HARQ process ID xx2222xx0000xx3333 process ID round trip time (16 subframe) schedule HARQ process ID pattern Ericson enb schedule 4. DRX and SPS alignment RIM DL SPS activation/reconfiguration DRX mode On Duration Ericson enb scheduling Active Time On Duration SPEC enb enb Short DRX Cycle On Duration( Long DRX Cycle On Duration) Short DRX Cycle DRX Short Cycle Timer expires Long DRX Cycle UE DL SPS enb Active Time 9

10 On Duration UE DL SPS 5. R : The some meeting principlas are agreed. 6. R : UE can prioritize CSG selection for inter-frequency but not decided for intra-frequency 7. R : They are discussion the order to perform PLMAC selection for CSG selection. Someone thinks there is less impact on RAN2 but someone thinks it bring big impact on CT1. It then is proposed to make the CT1 decide on this issues and then RAN2 look at it. 8. R : For non-drx mode, PHY is responsible for detecting out-of-sync and in-sync and indicating it to upper layer 9. R : LS on dependency analyses on feature lists. The high priority feature includes High VoIP optimization (SPS) VoIP optimization (TTI bundling) UL Hopping type 1 & 3 in feature list (for Nsb > 1) VRB to PRB mapping: Distributed Resource allocation type 1,2 (except for BCH, PCH, RACH response) Related functions (HARQ, timing relationship for TTI bundling) 10. R : Reply LS to "LS on maximum PDCP SDU size". There are no practical limits on the size of messages to be encrypted using the SNOW3G-based encryption algorithm 128-EEA1, nor the AES-based encryption algorithm 128-EEA2. There are also no practical limits on the size of messages to be integrity protected using the SNOW3G-based integrity algorithm 128-EIA1 or the AES-based integrity algorithm 128-EIA2. The restriction of bits (i.e octets) on the maximum input length for UTRAN algorithms is not based on cryptographic considerations but on protocol implementation considerations. This has been taken as a design requirement within TS clause that specifies that the length indicator LENGTH is 16 bits long for UMTS algorithms which is far beyond the bits protocol implementation consideration. 11. R : Ericsson prefer to have only one description in one place 12. R : Mapping of the RNTIs to different transport channels. Ericson 10

11 introduces this table. Chairman says DCCH is for RRC reestablishment. Revised to R R : Clarification on the first occasion for using the Long/Short DRX Cycle. This problem has been discussed and the conclusion is that I don t need to do anything. 14. R : HARQ RTT Timer and N/A Repetition in DRX. CATT says the purpose of N/A repetition is for saving power of UE in cell edge. But it seems that RAN 1 still doesn t have a consensus on this. Ericsson doesn t agree to send a LS to RAN 1 to ask their decision. 15. R : An issue on contention resolution. It is confirmed that UE can send RRC connection message in Msg3 and enb can response an RRC connection message in Msg R : Discussion on Truncated BSRR Discussion on Truncated BSR. Proposal 1 is a English syntax problem, Proposal 2 is a UE implementation issues. 17. R : About ACK/NACK repetition. The contents include ACK/NACK repetition is enabled or disabled by higher layers with a 1-bit UE specific parameter [ACKNACKRepetitionEnable]. By default, ACK/NACK repetition is disabled. ACK/NACK repetition factor N ANRep (including the initial ACK/NACK transmission) is a 2-bit UE specific parameter configured by higher layers. The suggested values of N ANRep are {2, 4, 6, reserved}. Once enabled, UE repeats any ACK/NACK transmission until it is disabled by higher layers. UE repeats ACK/NACK NANRep times in NANRep consecutive UL subframes. For an initial semi-persistently scheduled PDSCH transmission without a corresponding DCI format detected, the UE shall transmit the corresponding ACK/NACK response NANRep times using PUCCH resource (1) n configured by higher layers. Note n is the PUCCH resource (1) PUCCH PUCCH configured during the (re)initialization of the semi-persistent transmission. 11

12 For a dynamically scheduled PDSCH transmission, the UE shall first transmit the corresponding ACK/NACK response once using PUCCH resource derived from the corresponding PDCCH CCE index (as described in Section 10.1 [1]), and repeat the transmission of the corresponding ACK/NACK response N times using PUCCH resource (1) n ANRep 1 PUCCH, ANRep configured by higher layers. In the subframes where a UE is repeating the transmission (including the initial one) of ACK/NACK, the UE shall only transmit the corresponding ACK/NACK and shall not transmit any other signal. 18. R : Correction to contents of BSR. If logical channel group is not configured, enb will ignore any value set in Long BSR. Ericsson says it is implied that UE will set the value to zero. Some clarification is needed but this is not agreed. 19. R : Correction on PHR. This contribution proposes if the Padding bit number is enough to fill in the PH control element and related sub-header, the MAC PDU includes the latest PHR. Ericson thinks CATT creates new functionality and should modify prioritization. NSN feel sympathy and think this should be consider in Rel R : Correction to Handling of triggered PHR. It proposed to give higher priority to PHR and this is agreed. 21. R : Clarification on UL-SCH resource availability. Some clarification on current text which is ambiguous. LGE says it is clear in the spec and no change is required. 22. R : MAC PDU subheaders corresponding to Padding. The purpose of proposal 2 is to reduce the freedom and thus complexity. 23. R : CR On Backoff table. Here are three values which are not specified. Samsung prefers to specify a value but LGE think it should be discarded. Again, it is left to offline discussion. 24. R : Clarification of MAC PDU structure. CATT suggests fixing MAC CE size. If there is a variable size of MAC CE in the future, it proposes to 12

13 indicate the size by LCID. But this is not agreed. 25. R : Correction to Release of SPS. Samsung mentions that it is current assumption that when measurement gap collides with transmission of empty BSR, 26. R : ACK for UL SPS Explicit Release. RIM proposes having UE send an ACK to acknowledge the reception of implicit release. Motolora thinks the gain is small. So does Ericson. C-plane Connection control 27. Removal of spare values (R , R , R , R , R , R , R , R , R , R ) 12 TS v Error handling in missing essential information (R , R , R , R ) UE UE cell cell selection UE cell contribution 29. RRC processing delay discussion process delay UE enb RRC UE enb grant 13

14 RRC procedure delay DL at enb RRC CONNECTION SETUP UL Grant 4ms UL at enb RRC CONNECTION SETUP COMPLETE UL at UE 3.33ms RRC CONNECTION SETUP COMPLETE processing delay RRC delay 15 msec TDD processing delay FDD 30. Handling for reconfiguration failure in connection (re)establishment (R , R ) enb RRC reconfiguration message radio link UE UE enb UE DRB measurement delta signaling 31. CSG/HeNB issue CSG cell selection priority (R , R ) UE UE CSG cell CSG cell selection cell selection CSG cell CSG cell cell selection cell reselection to CSG cell - different if coming from CSG cell or macro cell - different if going to the same CSG or different CSG cell reselection from CSG cell - different for going to other CSG cell or macro cell - different for going to same CSG or different CSG inter/intra-frequency cell selection UMTS LTE Manual CSG selection (R , R , R ) 14

15 SA1 LTE HeNB T-Mobile CR manual CSG selection cell cell RAT operator CSG indicator (R , R , R , R , R , R , R , R R ) CSG indicator CSG ID HeNB enb CSG ID Rel LTE discussion 1) RRC rapporteur CR [Samsung] 2) Inter-Node AS signalling [NEC] 3) CSG related cell reselection details [QC] 4) UE capability transfer [Ericsson] 5) UL HARQ process usage for TTI bundling [SunPlus] 6) RAN1/RAN2 spec conflict re TA setting at random access [Samsung] 7) How timers should be handled when timer values are reconfigured by RRC [Ericsson] 8) HARQ RTT Timer for ACK/NACK repetition in DRX for TDD [CMCC] 9) TTT and DRX [Nokia] RAN1: LTE-Advanced 2010 IEEE802.16m IMT-Advanced NTT DoCoMo Verizon LTE-advanced 2. LTE-A control channel 15

16 3. RAN2: 1. LTE Release 8 RAN2 PHY RAN2 discussion 2. LTE Rel. 8 (2009 ) RRC text proposal control plan open issue LTE Rel GPP RAN2 #64bis Invitation 2. 3GPP RAN2 #64bis Agenda 3. 3GPP RAN2 $64bis TDoc Lists 4. 3GPP RAN2 $64bis Participant Lists 5. 16

17 Name Company Neng Wang Nortel Yi Song Nortel Lai-King(Anna)Tee Nortel Elliot Jen HTC Richard Kuo Asus Richie Zen Asus Fang-chen Cheng Alcatel Lucent MAN-ON Simon PUN Mitsubishi Shen Jia CATR Xia Yuan Huawei Li Guoqing Datang Mobile Xu Xiaodong China Mobile 17

2

1 2 3 4 PHY (RAN1) LTE/LTE-A 6.3 Enhanced Downlink Multiple Antenna Transmission 6.3.1 CSI RS 6.4 Uplink Multiple Antenna Transmission 6.4.1 Transmission modes and Signalling requirements for SU-MIMO 6.5