incoming LSs for RAN2 #63bis in Prague, Czech Republic, 29.09.-03.10.2008: status Thu 09.10.08 (56 incoming LSs) Agenda item 5.1: Incoming LS to LTE: 51 LSs R2-084942$ LS on Terminology alignment for Home Node B and Home eNode B (S1-082397; to: GERAN, RAN, CT; cc: -; contact: T-Mobile) SA1 R2-084943$ Reply LS to R2-083785 on additional RSRP trigger for ICIC (R1-083272; to: RAN2; cc: RAN3; contact: Ericsson) RAN1 R2-084944$ LS on TBS table and UL TTI bundling adjustments (R1-083273; to: RAN2; cc: RAN4; contact: Ericsson) RAN1 R2-084945$ LS on Consequence analysis of Low/ Medium features in LTE Rel-8 (R1-083364; to: RAN2, RAN5; cc: RAN4; contact: NTT DOCOMO) RAN1 R2-084946$ LS on PRACH power control (R1-083365; to: RAN2; cc: RAN4; contact: LG) RAN1 R2-084947$ LS on E-UTRA RRM Main Open Issues in RAN5 (R5-083801; to: RAN4, RAN2; cc: -; contact: Motorola) RAN5 R2-084948 LS on access control for CSG cells (C1-083429; to: SA2, CT4; cc: RAN2, RAN3; contact: Qualcomm) CT1 R2-084949 LS on Identifiers for HeNB (C1-083612; to: RAN2, RAN3, SA2; cc: -; contact: Vodafone) CT1 R2-084950 Reply LS to R2-083786 on ETWS (C1-083623; to: RAN2, RAN3; cc: SA1, SA2; contact: NTT DOCOMO) CT1 R2-084951 Reply LS to S1-082341 = R2-084521 on HNB/HeNB Open Access Mode (C1-083625; to: SA1; cc: RAN2; contact: Telecom Italia) CT1 R2-084952 LS on NAS message concatenation and multiple EPS bearer setup (C1-083626; to: RAN2, RAN3; cc: CT4; contact: Qualcomm) CT1 R2-084953 LS on Protocol Decision on GTP User Plane (C4-082382; to: SA2, RAN2, RAN3; cc: CT1, CT3; contact: Ericsson) CT4 R2-084954 LS on Definition of Globally Unique Temporary UE Identity (C4-082513; to: SA2, SA1, SA3, RAN2, RAN3, CT1, CT3; cc: -; contact: Alcatel-Lucent) CT4 R2-084955 Reply LS to S1-080769 = R2-083082 on CSG related mobility (stage 2 text) (GP-081307; to: SA1; cc: SA2, RAN2, RAN3, RAN4, RAN1; contact: Huawei) GERAN R2-084956 LS on ETWS (GP-081310; to: SA1, SA2, SA3, CT1; cc: RAN2, RAN3; contact: Ericsson) GERAN R2-084957 LS on reporting E-UTRAN measurements (GP-081347; to: RAN4; cc: RAN2; contact: NSN) GERAN R2-084958 LS on SRVCC target cell selection (GP-081425; to: SA2; cc: RAN2; contact: NSN) GERAN R2-084960 LS on PDCCH DCI format 1C (R1-083416; to: RAN2; cc: -; contact: LG) RAN1 R2-084961 LS on CSG cell identification (R1-083424; to: RAN2, RAN4; cc: RAN3; contact: Qualcomm) RAN1 R2-084962 LS reply to R2-084764 on considerations on transport block sizes for VoIP (R1-083429; to: RAN2; cc: RAN4; contact: Ericsson) RAN1 R2-084963 LS Reply to R2-083779 on Uplink grant format in Random Access Response (R1-083431; to: RAN2; cc: -; contact: Qualcomm) RAN1 R2-084964 LS Response to LS R2-082893 on information about new PDCCH Format 1C and LS on SI Scheduling (R1-083432; to: RAN2; cc: -; contact: Motorola) RAN1 R2-084966 LS on UL SRI Parameters Configuration (R1-083450; to: RAN2; cc: -; contact: CATT) RAN1 R2-084967 LS on timing adjustment (R1-083452; to: RAN2, RAN4; cc: -; contact: LG) RAN1 R2-084968 LS on measurement gap (R1-083454; to: RAN2; cc: RAN4; contact: Panasonic) RAN1 R2-084969 LS on support of TDD ACK/NACK multiplexing in Rel-8 (R1-083465; to: RAN2; cc: RAN4; contact: Texas Instruments) RAN1 R2-084970 LS on Coding of Global Cell id and Global eNB ID (R3-082363; to: RAN2, SA2; cc: -; contact: Alcatel-Lucent) RAN3 R2-084971 LS on SAE Bearer/ E-RAB definition for E-UTRAN specification (R3-082366; to: SA2, RAN2, CT1, CT4; cc: -; contact: Alcatel-Lucent) RAN3 R2-084972 LS on E-UTRAN security related issues (R3-082373; to: SA3; cc: RAN2; contact: Qualcomm) RAN3 R2-084973 LS reply to R1-082762 = R2-083821 on CSG cell identification (R4-082190; to: RAN1, RAN2; cc: -; contact: Motorola) RAN4 R2-084974 LS on Special Conformance Testing functions for UE (TS 36.509) (R5-083665; to: RAN2; cc: RAN; contact: Rohde & Schwarz) RAN5 R2-084977 Reply LS to R2-084902 on Paging UE Identity for CS Fallback (S2-086147; to: RAN2; cc: CT1, RAN3; contact: Huawei) SA2 R2-084978 Response LS to R2-082895 and C1-082800 = R2-083672 on Connection recovery by NAS (S2-086378; to: CT1, RAN2, RAN3; cc: RAN1; contact: Vodafone) SA2 R2-084979 Reply LS to R3-081607 = R2-083072 on Load balancing signalling on QCI (S2-086388; to: RAN3; cc: RAN2; contact: Ericsson) SA2 R2-084980 Reply LS to R2-083781 on AMBR Enforcement (S2-086390; to: RAN2; cc: RAN3, CT1; contact: Qualcomm) SA2 R2-084982 Reply LS to C4-082513 = R2-084954 on Definition of Globally Unique Temporary UE Identity (S2-086397; to: CT4, CT; cc: SA1, SA3, RAN2, RAN3, CT1, CT3; contact: Alcatel-Lucent) SA2 R2-084983 LS on Guidance for ARP Values (S2-086405; to: SA1; cc: RAN2, RAN3; contact: Motorola) SA2 R2-084984 LS on UE Radio Capabilities (S2-086410; to: RAN; cc: SA, RAN2; contact: Vodafone) SA2 R2-084985 LS reply to R2-082899 on CSG cell identification (R4-082191; to: RAN2, RAN1; cc: -; contact: Motorola) RAN4 R2-085697 LS on work split for definition of L2 measurements (S5-081376; to: RAN2; cc: -; contact: Huawei) SA5 R2-085771#* LS on PCI Clarification (S3-081118; to: RAN2; cc: RAN3; contact: Qualcomm) SA3 R2-085772#* Reply LS to R2-084907 on KeNB handling at handover (S3-081121; to: RAN2, RAN3; cc: -; contact: NTT DOCOMO) SA3 R2-085773#* Reply LS to R2-083787 on "LS NULL integrity protection algorithm" (S3-081129; to: RAN2, RAN5, CT1; cc: -; contact: NSN) SA3 R2-085774#* Reply LS to R2-084876 on "AS Message Exception list" (S3-081130; to: RAN2; cc: -; contact: Nokia) SA3 R2-085775#* Reply LS to R2-084898 on "counter check procedure" (S3-081135; to: RAN2; cc: -; contact: Nokia) SA3 R2-085776#* Reply LS to R2-084909 on “Intersystem RAT handover security” (S3-081138; to: RAN2; cc: -; contact: NSN) SA3 R2-085777#* LS on preventing inter-RAT HO for UE with SIM access (S3-081150; to: RAN3; cc: RAN2, CT1, CT4; contact: Huawei) SA3 R2-085786#* Reply LS to R3-082373 = R2-084972 on E-UTRAN security related issues (S3-081175; to: RAN3; cc: RAN2; contact: Ericsson) SA3 R2-085814#@ LS on UE emission control (R4-082585; to: RAN1, RAN2; cc: RAN3; contact: Motorola) RAN4 R2-085857#* LS on the start of security on IRAT handover from GERAN/UTRAN (S3-081139; to: CT1, RAN2; cc: -; contact: Nokia) SA3 R2-085910#@ Reply LS to S1-082418 = R2-084550 on UE-Aggregate Maximum Bit Rate for GERAN/UTRAN (G2-080614; to: SA1, SA2; cc: RAN3, RAN2, CT1, CT4; contact: Vodafone) GERAN2 Agenda item 7.1: Incoming LSs on UTRA (all releases): 5 LSs R2-084959 Response to 3GPP to C4-081019 = R2-082067 on Messaging Support for Network Based Location Technologies on User Plane (OMA-LS_751; to: CT4, SA2; cc: RAN2, RAN3; contact: Sprint) LOCATION WG of OMA R2-084965 LS on Improved EUL power control at UE power limitation (R1-083440; to: RAN2, RAN3; cc: -; contact: Ericsson) RAN1 R2-084975 LS on the addition of CS voice over HSPA radio bearer combinations to TS 34.108 (R5-083690; to: RAN1, RAN2; cc: -; contact: Nokia) RAN5 R2-084976 Response LS to R2-084823 on HSPA Rel-8 Feature Dependencies (RP-080748; to: RAN2; cc: -; contact: Nokia) RAN R2-084981 Reply-LS to G2-080228 = R2-082024 and R2-082884 on Applicability of “subscriber type” indication for UTRAN & GERAN (S2-086392; to: GERAN2; cc: RAN2, RAN3; contact: Huawei) SA2 $: 6 LSs resubmitted from RAN2 #63: R2-084942 =R2-084527 =S1-082397 R2-084943 =R2-084719 =R1-083272 R2-084944 =R2-084710 =R1-083273 R2-084945 =R2-084888 =R1-083364 R2-084946 =R2-084889 =R1-083365 R2-084947 =R2-084746 =R5-083801 #: 11 LSs received during RAN2 #63bis: R2-085771 = S3-081118 R2-085772 = S3-081121 R2-085773 = S3-081129 R2-085774 = S3-081130 R2-085775 = S3-081135 R2-085776 = S3-081138 R2-085777 = S3-081150 R2-085786 = S3-081175 R2-085814 = R4-082585 R2-085857 = S3-081139 R2-085910 = G2-080614 45 of the 56 incoming LSs were treated during RAN2 #63bis, *: 9 LSs are for email discussion R2-085771 = S3-081118 R2-085772 = S3-081121 R2-085773 = S3-081129 R2-085774 = S3-081130 R2-085775 = S3-081135 R2-085776 = S3-081138 R2-085777 = S3-081150 R2-085786 = S3-081175 R2-085857 = S3-081139 @: 2 LSs were not treated and they will be resubmitted to the next meeting (RAN2 #64): R2-085814 = R4-082585 R2-085910 = G2-080614