3GPP TSG RAN WG2 #79 /

3GPP TSG RAN WG2 #79 / 101 8 12 101 8 18 101 9 24

3GPP TSG RAN2 2012 8 13 8 17 5 5 1. [ ] DRX TDD stage-3 Control Plane User Plane SPEC Rel-12 2. [Enhancement of Diverse Data Applications] edda Power Preference Indication Mobility assistance information edda edda Release 12 3. [ ] (Enhanced Inter-cell Interference Coordination, eicic) (Heterogeneous Network, HetNet) (macro enb) (1) 2

(Cell-specific Reference Signal Interference) (2) (Cell Detection) (3) (Reduced Power Almost Blank Subframe) CRS Interference Reduced Power ABS E-mail RAN2 eicic 4. [ ] stage 3 36.331 36.304 5. [Minimization of Drive Tests]enhancement of MDT (rapporteur) Stage3 /Qos / / CHTTL RAN2 MDT RAN2 10 4 3GPP LTE Rel-11 9 RAN plenary stage 3 LTE Rel-11 3

LTE Release 11 LTE-Advanced Release 12 3GPP LTE-Advanced 3GPP TSG RAN #79 (Carrier Aggregation) edda (Enhancement of Diverse Data Applications) (Heterogeneous Network, HetNet) MBMS 1. [ ] a) b) c) d) e) PDCCH-subframe f) stage 3 control plane user plane SPEC 2. [edda] RAN2#78 4

cell reselection mobility state estimation Release 12 3. [ ] (a) (Cell-specific Reference Signal Interference) E-mail discussion [78#48] ( R2-124033) CR(Change Request) ( R2-124362) Network CRS Assistant Information UE CRS Interference Cancellation/Mitigation CRS Assistant Information List of Neighboring Cells (Physical Cell ID) Antenna Port MBSFN Configuration CRS Interference Cancellation/Mitigation Measurement Demodulation (b) (Cell Detection) (Cell Range Expansion, CRE) UE Aggressor Cell UE SIB-1 (System Information Block Type 1) MIB (Master Information Block) SIB-1 Dedicated Signaling UE MIB RAN4 4. [ ] 36.331 36.304 (common specification text) PCell SIB15 5

5. [Minimization of Drive Tests] a) MDT PLMN PLMN b) c) {1024 ms, 2048 ms,5120 ms, 10240 ms, 1 min } QCI d) e) (Received Interference Power, RIP) {100ms, 1s, 10s} 6

...2...8...8...8...8...8... 10... 27 7

3GPP TSG RAN2 #79 Meeting LTE-A CA enhancement eicic (enhanced Inter-Cell Interference Coordination) MBMS MDT (Minimization Driving Test) 13th -17th August 2012 Le Méridien, Qingdao, China RAN2 13th -17th August 2012 Schedule Main room LTE UP room UMTS room Mon 09:00 -> [2],[3],[4], [5.1] EAB, [5.2] MDT Tue 08:30 -> 10:30 [5.4] Joint Other WIs 8

[5.3] Joint TEI11 Tue 11:00 -> 12:30 [6] LTE Rel-8/9/10 [8] Rel-789 non-tdd Tue 14:00 -> [10.1] FE FACH discussions Wed 08:30 -> 12:30 [7.1] CA (common + CP) [9] Rel-10 non-tdd [7.3] MBMS Wed 14:00 -> [7.11] Capabilities & ASN.1 [8,9] All TDD [7.2] EDDA [10.2] Mflow [10.6] rsrvcc Thu 8:30 -> 12:30 [7.7] CoMP [6] Rel-10 UP leftovers Comebacks [7.5] feicic [7.1.2] CA MTA UP aspects [10.1] FE FACH CRs [7.1.3] CA TDD UP aspects [10.3] CLTD [7.1.4] PDCP SN ext. [10.7] Other Rel-11 WI Thu 14:00 -> 18:30 [7.6] IDC [7.8] TEI11 - UP Aspects Comebacks [10.4] DL 4x4 MIMO Thu 18:30 -> Comebacks [10.5] UL MIMO 64QAM [7.4] NBP [10.8] Rel-11 SI [10.9] TEI 11 Fri 8:30 -> Comebacks Comebacks and leftovers [7.9] HetNet Mob [7.10] Other LTE WIs [7.8] LTE TEI11 Fri: 14:00 -> Left-overs, Comebacks (Joint until 17:00 topics), [12][13][14] 9

1. Carrier Aggregation (Rel-11) a) R2-123381 Whether to associate DL-only SCell with a TAG; CATT 0 Agreements 1 A DL-only SCell may be associated with a secondary TA group that contains at least one UL SCell. b) R2-123538 RA response window for stag; Huawei, HiSilicon, Ericsson, ST-Ericsson; R2-123378 Discussion on SCell RA Response Window; CATT, Nokia Siemens Networks; 1: 2: 2 1 The ra-responsewindowsize for SCells the same as for the PCell: [20] 10

The ra-responsewindowsize can be explicitly signalled for the RACH on SCell: [6] Agreements 1 The ra-responsewindowsize for SCells the same as for the PCell that means it is not configurable. c) R2-124031 Open issues on TAG management; Huawei, HiSilicon; Huawei Agreements 1 The enb releases an stag only when the stag is an empty stag. d) R2-123375 SFN alignment among aggregated serving cells; Panasonic Rel-10 Rel-11 Rel-10 Agreements 1 RAN2 confirms that also for Rel-11 radio frames and SFN are aligned for cells which can be aggregated by a UE. (does not require any change to specifications) e) R2-123715 drx-retransmissiontimer with different TDD configurations Ericsson, ST-Ericsson R2-123429 Remaining issues on DRX for CC specific TDD configurations Nokia Siemens Networks, Nokia Corporation PDCCH-subframe 11

PDCCH-subframe Option A) Counting for Scheduling cell DL and Special subframe (Change to drxretransmissiontimer definition) Option B) Counting for UE PDCCH subframe (No change to current text) - Clarification is needed for PDCCH-subframe so that it is defined for scheduling serving cells? HARQ Indicative voting: Option A) Counting for Scheduling cell DL and Special subframe [10] Option B) Counting for UE PDCCH subframe [9] B B Agreements 1 Go for option B. no change to the current text. drxretransmissiontimer is counted by UE PDCCH subframe. 2. Enhancements of Diverse Data Applications (Rel-11) edda Power Preference Indication Mobility assistance information (1) R2-123413 Summary of email discussion [78#43] LTE/EDDA: Power preference indication; ZTE Corporation; Report; related to email discussion [78#43] 12

vendor MediaTek ZTE ALU Nokia signaling overhead MediaTek Nokia 0 1 prohibit 13

timer Agreements 1 The UE may indicate whether it prefers the power efficient or normal state but it is not allowed to send the same indication in consecutive PPI reports. The indication is not seen in relation to the current configuration but rather as a general UE preference 2 At least for certain services running on dedicated bearers such as VoIP, the UE can assume that the NW will choose settings suitable to fulfil the QCI characteristics of that bearer. FFS whether the UE knows or may assume whether and for which other bearers and QCIs the QoS characteristics will still be met after sending the low power indication. 3 Introduce a UE capability indicator for the Power Preference indication 4 Using RRCConnectionReconfiguration the network selectively enables UEs to send power preference indications. (when the network enables the UE to send power preference indications it implicitly indicates it supports the feature so that no other network indicator is needed) 5 The UE is allowed to send the indication whenever its preference changes compared to the previously indicated preference. It is not allowed to send the same preference in consecutive indications. Consecutive indications (with different values) are subject to prohibit timer mechanism to avoid excessive signalling where the timer value is configured by the NW via RRC in the RRCConnectionReconfiguration. (FFS whether it is alternatively OK to rely on that the NW de-configures the feature for a misbehaving UE) 6 The Power Preference Indication is conveyed by means of a new UL RRC message (FFS whether a common UL status information could be used). 7 It is up to NW implementation whether, how and when to reacti to the UEs PPI. The network does not signal an explicit response upon reception of a PPI. 8 No explicit NAS->AS trigger is introduced in the specification (2) R2-123590 Summary of email discussion [78#44] LTE/EDDA: Mobility assistance information; Nokia Corporation (Email discussion rapporteur); Report; related to email discussion [78#44] 14

cell reselection mobility state estimation 1 2 pico cell femto cell edda RAN Rel-12 HetNet 3. MBMS Service Continuity (Rel-11) R2-124095: Report on [78#46] LTE/MBMS: MBMS 36.331 CR [Samsung]; Samsung (rapporteur); Report; related to email discussion [78#46]; RAN2#79 RRC Rapporteur (Samsung) open issues 36.331 36.304 15

(common specification text) : Agreements 1 Do not introduce common specification text, but use 36.331 alike style (i.e. broken down in dependant bullets) for the concerned text in 36.304 2 We do not use a bullet list for potential triggers these are left to UE implementation. But we specify constraints when the UE is allowed to trigger an indication. These constraints are mandatory ( shall ). Exact formulation to be discussed offline. 3 The UE is allowed to indicate MBMS interest only if the PCell broadcasts SIB15 4 Forward the entire MBMS interest indication message upon handover, placed within a container => We confirm the agreement that a UE is only required to support simultaneous reception of MBMS services listed in an MBMSInterestIndication. The indication shall match at least one band combination in the supportedbandcombination IE. => Discuss how to word this in stage-3. => Should be captured in 36.331 (where the message is constructed) and in 36.306. => A UE indicating interest in MBMS shall also support reading SIB13 on the indicated frequencies no matter whether the frequency is configured as SCell or not R2-123868 R2-123628 MBMS prioritisation; Samsung; UE behaviour based on MBMS services broadcast status; Nokia Corporation, Nokia Siemens Networks; R2-124250 R2-124058 Incorporated; MBMS Service Continuity upon leaving connected mode; HTC Additional Assistance Information for MBMS UEs; Qualcomm Stage 3 RAN2 a) Prohibit mechanism? b) Specify time within which the UE has to indicate that it is no longer interested? If so, configurable or in specification? c) Is the UE required to read SIB13 and SIB15 from its SCells? Or does the enb provide it based on UE s interest? d) Adjust definition of prioritization rules to allow the UE to disregard frequencies preventing MBMS reception? e) Clarification regarding congestion handling needed? f) MBMS based prioritization during Cell Selection or redirection? g) Add a list of Physical Cell ID (PCI) information associated with each SAI? h) Broadcast the relationship between MBSFN area and SAI? 16

i) Mandate the UE not to provide interest based on MCCH but only based on SAI in SIB? j) MBSFN area reserved cell? k) Inter-RAT support Rel-11 a) prohibit timer SCell SIB15 open issues : Agreements 1 Assumption: There is no prohibit mechanism for sending MBMSInterestIndications 2 No need to specify time constrains within which the UE is required to send an MBMSInterestIndication when the UE is no longer interested in a service. 3 UE shall provide MBMS Interest Indication or perform prioritization of the MBMS carrier based on information provided in SIB 15, if present, but not based on MCCH (=> Can discuss offline whether it is possible to include this in the) 4. Further Enhanced Non CA-based ICIC for LTE (Rel-11) (a) (Cell-specific Reference Signal Interference) E-mail discussion [78#48] UE CRS Assistant Information UE ( R2-124033) Proposal 1: RAN2 specification will specify that the received CRS assistant information over RRC will be passed to the physical layer. RAN2 may make reference to the relevant RAN4 specification in the future. 17

RAN2 UE CRS Assistant Information Physical Layer Proposal 2: CRS cancellation can be applied to pattern1, pattern 2 and one of pattern 3 corresponding to ABS. RAN2 needs to specify that the UE shall not perform CRS IC on the pattern 3-2, while the UE may apply CRS cancellation to pattern 3-1. Pattern 1 Pattern 2 Pattern3-1 CRS Interference Cancellation Measurement Proposal 3: At least for the aggressor cells with colliding CRS, RAN2 needs to specify that the UE assumes that the assistance information are provided only for aggressor cells that are utilizing ABS during the subframes indicated by UE measurement restrictions. For the aggressor cells with non-colliding CRS, further discussion is needed. Aggressor Cell Victim Cell CRS Offset Measurement CRS Interference Cancellation Proposal 4: The CRS assistant data is included in RadioResourceConfigDedicated IE. CRS Assistant Information RadioResourceConfigDedicated IE List of Neighboring Cells (Physical Cell ID) Antenna Port MBSFN Configuration Proposal 5: Detection of UE interference condition at handover can use existing inter-node signalling, and is left to enb implementation. Network CRS Assistant Information UE enb implementation off-line discussion CR(Change Request) ( R2-124362) release CRS Assistant Information CRS Interference Cancellation/Mitigation Measurement Demodulation 18

RadioResourceConfigDedicated information element [[ neighcellscrsinfo-r11 NeighCellsCRSInfo-r11 OPTIONAL NeighCellsCRSInfo-r11 ::= CHOICE { -- Need ON ]] release setup NULL, CRS-AssistanceInfoList-r11 } CRS-AssistanceInfoList-r11 ::= SEQUENCE (SIZE (1.. maxcellreport)) OF CRS-AssistanceInfo CRS-AssistanceInfo ::= SEQUENCE { physcellid-r11 antennaportscount-r11 mbsfn-subframeconfiglist-r11 PhysCellId, ENUMERATED {an1, an2, an4, spare1} MBSFN-SubframeConfigList } RadioResourceConfigDedicated field descriptions neighcellscrsinfo This field contains assistance information for UE to mitigate interference from CRS while performing RRM/RLM/CSI measurement or data demodulation. The UE forwards the received CRS assistance information to lower layers. When the received CRS assistance information is for a cell with CRS colliding with that of the CRS of the cell to measure, the UE may use the CRS assistance information to mitigate CRS interference (as specified in [FFS]) on the subframes indicated by meassubframepatternpcell, meassubframepatternconfigneigh and csi-meassubframeset1.furthermore, the UE may use CRS assistance information to mitigate CRS interference from the cells in the IE for the demodulation purpose as specified in [FFS]. (a1) De-configure the assistance information de-configure the assistance information? (a2) The size of the cell list CRS Assistant Information the number of cells to cancel interference RAN4 maxcellreport(=8) 19

(b) (Cell Detection) RAN1 LS( R1-114468) Network assistance to simplify UE implementation of cell detection for 9 db CRE (Cell Range Expansion ) bias Higher-layer signaling is utilized to aid the UE (Cell Range Expansion, CRE) UE Aggressor Cell UE SIB-1 (System Information Block Type 1) MIB (Master Information Block) (b1) SIB-1 SIB1 (1) modification period systeminfomodification (2) UE PDCCH SI-RNTI PDSCH SIB1 (1) systeminfomodification (2) RAN1 LS( R1-123076) As a current working assumption, RAN 1 will assume: enb signalling solution to aid acquisition of SIB-1 contents in the presence of dominant interferers with 9dB bias The victim cell may send its SIB-1 contents to the victim UE using higher layer signaling in the protected resources Exact signaling solution to be decided by RAN2 SIB1 Normal Subframe Aggressor Cell PDSCH Victim UE Victim Cell PDSCH SIB1 SIB1 Aggressor Cell ABS PDSCH Aggressor Cell PDCCH Control Signal Victim UE Victim 20

UE PDCCH SI-RNTI PDSCH SIB1 UE 9dB bias CRE Aggressor Cell Interference SIB1 Connected UE Connected UE RRC Connection Radio Link Failure Contributions R2-123781 SIB-1 and MIB related signalling for eicic; Alcatel-Lucent; Disc; R2-124048 SIB-1 acquisition for pico CRE UEs; Qualcomm Incorporated; Disc; : (1) Subframe Shifting SIB1 paging FDD the SFN of the aggressor cell and that of the victim cell differs by 1 aggressor cell victim cell SIB1 TDD ( R2-124044 R2-123934) (2) Broadcasting signalling in the victim cell victim cell paging SIB1 UE victim cell Aggressor Cell ABS PDCCH SI-RNTI PDSCH SIB1 RNTI ( R2-123582) (3) Dedicated Signalling in the aggressor cell serving cell Aggressor Cell ABS dedicated signaling victim cell SIB1 dedicated signaling SIB1 Aggressor Cell ABS Network UE SIB1 Broadcast dedicated signaling ( R2-123425 R2-123735) 21

dedicated signaling E-mail Agreements 1 We will introduce dedicated signalling of provisioning of SIB1 for UEs in CRE zone. Details are FFS [LTE/feICIC] Email discussion until next meeting to specify the details of provisioning the required information. Can take into account that handover signalling already provide some of these IEs. (ALU) (1) If dedicated signalling, in which message to send the SIB? RRCConnectionReconfiguration? (2) How does the NW know that a UE needs SIB1 via dedicated signalling? Up to NW implementation? (3) Does the UE still attempt to receive SIB from broadcast? Or may it skip normal acquisition when receiving dedicated SIB1? (b2) MIB RAN1 LS( R1-123058) As a current working assumption, RAN 1 will assume: enb signalling solution to aid detection of PBCH in the presence of dominant interferers with 9dB bias Related MIB information from the victim cell may also be supplied by aggressor cell during handover from aggressor to victim cells RAN 1 also made an observation that: SFN offset between victim and aggressor cell Possible alternative to enb signalling is the PBCH interference cancelation capable receiver based solution (1) SFN offset between victim and aggressor cell (2) interference cancelation capable receiver 22

RAN4 RAN4 => We focus on SIB1 assuming that RAN4 is progressing on PBCH detection possibilities 5. WI: Enhancement of Minimization of Drive Tests for E-UTRAN and UTRAN emdt RAN2#79 90% Stage3 CR TS36.331 36.304 36.3142 Email discussions Plenary emdt General: CR PLMN R2-123817 R2-123995 Agreements 1. E-UTRAN and UTRAN configures the MDT PLMNs by explicitly signalling the PLMN identities (i.e.not using a bitmap). 2. The UE accepts the PLMN identities without verifying if they are part of the EPLMN list (neither upon time of reception of the MDT PLMN list nor upon change of the UE s EPLMN list) (applies to LTE and UTRAN) QoS Verification: (Preambles) 23

Agreements For LTE and UMTS 1 Time stamp shall be supported 2 The time stamp can be derived by using a relative timer counting the time between failure and reporting 3 The timer resolution shall to be on per second granularity. 4 The storing time for accessibility measurements should be 48 hours For LTE: 1) Reporting the Number of Random access preambles transmitted shall be supported. 2) The Indication that maximum power level was reached should be included. 3) The measurement of Contention detected shall be included. For UTRA FDD: 4) The measurement of Number of RRC Connection Request attempts (e.g. T300 expiry after receiving ACK and AICH) shall be supported 5) Indication of probable contention shall be included. For UTRA TDD: 6) The measurement of Number of RRC Connection Request attempts shall be supported 7) Indication of probable contention shall be included 8) Whether the FPACH is received or whether the maximum number Mmax of synchronisation attempts is reached. (one bit indication) 9) Failure indication of the E-RUCCH transmission. It is only applied for common E-DCH is supported by UE and network. (one bit indication) PLMN related 1) The UE stores the Selected PLMN (as in 36.331) upon Connection Establishment Failure. Only if that PLMN is the same as the RPLMN in the subsequently established connection, the UE may report establishment failure. 2) Shall capture this in Stage-2, with a NOTE saying that performance is considered to be the same as if the UE would have been able to report to eplmns also. QCI/RAB UMTS PS 24

Agreements 1 For LTE, for throughput and data volume measurement, the value range for measurement collection interval to be {ms1024, ms2048, ms5120, ms10240, min1}. 2 For LTE Data volume measurement results per QCI shall be collected and logged. 3 For LTE and UMTS the throughput measurement, whether to log per RAB or per UE do not need to be configured. The enb will always log both. For UMTS: For UMTS there is a measurement collection period for the throughput measurement, where one measurement result is provided for each period when there is data transmission. 2 For UMTS, for both throughput and data volume measurement, the value range for measurement collection interval should be possible to be aligned with those for the M1 measurement (could be specified as integer number of seconds) 3 Data volume measurement results shall be collected and logged per QoS class, where the QoS classes are (at least): {conversational, interactive, streaming, background}. 4 Data volume measurements are only need to be done for PS domain traffic. 5 MDT Throughput measurements are only need to be done for PS domain traffic. 6 We specify Data Volume and MDT Throughput measurements for UMTS only on stage-2 level. The description will be provided in an Annex of 37.320. (Detailed wording to be discussed offline) Offline discussion: 1) 36.314 shall capture data volume measurement per QCI 2) For UMTS, for both throughput and data volume measurement, the value range for measurement collection interval is 1..64 [s] Availability of Location Information: LOGED MDT GNSS GNSS SUOL (Secure User Plane location) 25

Agreements : A Requested location is not supported for logged MDT in Rel-11 1 It is assumed that the UE GNSS activation can fail, and that UE GNSS de-activation can happen, and that UE acquisition of location info can fail. We don t specify in detail what would be the conditions for this and the UE does not need to provide success / failure response or indication. 2) activategnss is valid only if the UE is configured with Immediate MDT (i.e. with includelocationinfo). It shall be clear in the stage-3 for which times the network request the UE to keep GNSS activated for MDT, and when the network is no longer requesting the UE to keep GNSS activated for MDT. 3) Regarding how often to get GNSS location, it is left to UE implementation. There shall be descriptive text that it is desired to have fresh location info with M1 measurements. 4) The attempt to do UE GNSS activation for MDT shall be explicitly ordered by OAM, but it is assumed that OAM do not know UE capability. 5) Usage of E-CID shall be explicitly ordered by OAM. 6) It shall be possible to configure usage of both UE GNSS and E-CID, meaning that E-CID is then a backup location method, applied when UE does not provide GNSS location. 7) Remove the SUPL is not precluded text from stage-2. 8) Introduce an additional capability bit to indicate whether the UE supports to report UE Rx-Tx time difference measurement results via RRC signalling, to allow usage of this measurement for MDT. 9) Content of R2-123341 can be merged into the Rel-11 Capability CR maintained by DOCOMO. 10) Both confidence and uncertainty information are included, when available, in the positioning results collected with MDT, for both logged MDT and immediate MDT. Coverage optimization: TS36.331 (A1 A2) (B1) emdt RCC emdt (Received interference Power) UPH(Uplink Power Headroom) UMTS 26

Agreements 1 For LTE: Logging of measurement reports configured for RRM, with location information, for events A1, A2, A3, A4, A5, A6, B1, B2, is supported for MDT. FFS whether For UMTS Logging of measurement reports configured for RRM, with location information, for measurement types intra-frequency measurement, inter-frequency For collection of LTE Received Interference Power measurement 1 Periodic RIP measurement collection shall be supported with periodicity {100ms, 1s, 10s} 2 For each measurement collection period one sample is logged, where one sample corresponds to a 100ms measurement period as specified in TS 36.133. 3 Add a note in stage-2 that RIP is considered to be a cell measurement. For collection of UMTS UPH and RTWP measurement, 1 After taking into account current Iub Common measurement support in 25.433, it is concluded that the following measurement collection triggers for UPH would be useful for MDT. d) periodic e) when (measurement value < threshold) and (periodic) f) node B reports all available UPH to RNC. 2 For a) and b), one available UPH report relevant for the measurement period is sent to RNC for each measurement period. 3 It is assumed that UPH reporting from the UE is done according to the normal RRM configuration. There is no MDT specific trigger for UE reporting. 4 For RTWP periodic measurement collection trigger shall be supported, where the measurement period can be set by the OAM system, and the periodicity values currently supported by current Iub-reporting shall be used. 5 For RTWP, Unspecified measurement collection trigger shall be supported, where RTWP is collected whenever it becomes available in the RNC measurement and inter-rat measurement is supported for MDT. DRX TDD stage-3 Control Plane User Plane SPEC Stage 3 SPEC 27

edda stage3 RAN Release 11 Rel-11 (Enhanced Inter-cell Interference Coordination, eicic) CRS interference SIB1 MIB Cell Detection eicic Working Item RAN2#79bis Minimization of drive-tests RAN1 MDT MTC RAN2 ( NTT DOCOMO Vodafone ) Relays Latency reduction Carrier aggregation RAN2 3GPP LTE-Advanced 28