WF on RA-RNTI design 3GPP TSG RAN WG1 Meeting NR#3 R1-171xxxx

Slides:



Advertisements
Similar presentations
Way forward for LTE DL 4Rx AP SI on RF
Advertisements

© NOKIAProduced as informative material for 3GPP RAN WG1 meeting No. 2 Downlink Shared Channel - DSCH DSCH associated with a dedicated channel (DCH) Downlink.
WF on design of physical downlink control channel for MTC CATT, Alcatel Lucent, Alcatel Lucent Shanghai Bell, Ericsson, ETRI, InterDigital, MediaTek, NTT.
WF on PBCH Coverage Enhancement
Way forward on eIMTA signaling to support up to 32 component carriers
WF on MCOT and CWS for LBT priority classes
WF on Regulation and MCOT
WF on SIB1bis Transmission
WF on LAA DL Multi-Channel LBT
Proposal for NB-IoT single-tone only UE
WF on UE capability signaling for FD-MIMO Class B LG Electronics, Intel Coorporation, NTT DOCOMO, Qualcomm 3GPP TSG RAN WG1 Meeting #84 R St Julian’s,
WF on MCOT limit Signaling and Modifying LBT type Ericsson, … 3GPP TSG RAN WG1 #85 R1-16xxxx Nanjing, China 23 rd – 27 th May 2016 Agenda item:
WF on Supporting different Numerologies in a NR carrier LG Electronics, [Huawei, HiSilicon, Panasonic], 3GPP TSG RAN WG1 Meeting #85R Nanjing,
Overview of open issues in
Offline discussion on remaining details on RRM measurements
WF on Bandwidth Part for DL common channel
3GPP TSG-RAN WG4 Meeting NR#3 Nagoya, Japan, 18 – 21 Sep, 2017
Summary on Beam Recovery Mechanism
Way Forward on UE measurement definition and capability
Summary of SLS for RRM NTT DOCOMO
Offline Discussion on remaining details about RACH Procedure
Draft WF on single Tx switched UL
Single Tx switched UL DRAFT 3GPP RAN #77 September , 2017
R GPP TSG RAN WG1 Meeting #90 Prague, P.R. Czechia, 21st – 25th August 2017 Agenda: WF.
WF on new NR CG sequences for PUCCH
Proposals on remaining issues on PDCCH structure
RACH configuration ZTE, Sanechips R1-171xxxx
Summary of offline discussion for PDCCH structure
Proposals on remaining issues on search space
3GPP RAN1 #90 meeting summary on LAA Enhancements
WF on Beam Indication for Beam Management
WF on NB-IoT Radio Link Monitoring Performance Test Procedure
WF on measurement capability and measurement gap for NR
Way forward on UE EIS Spherical Coverage and Beam Correspondence
3GPP TSG RAN WG1 Meeting #90bis
Summary on Beam Recovery Mechanism
R : SRS Enhancements for LTE-A
WF on remaining open items for allowing 1Tx transmission in LTE-NR DC
WF on Beam failure recovery
Illustration of RMSI monitoring windows (TDM)
WF on SS Block Index Reporting through RACH Procedure
Way forward on cell identification in NR
Discussion on TB-ack/CBG-Nack for initial transmissions
Intel Corporation, Apple
WF on transmit diversity for DFTsOFDM
Samsung, KT Corp., NTT DOCOMO, Verizon, [ZTE], [CATT], [Intel]
WF on beam reporting CATT, Intel R1-17xxxxx
WF on Beam-Related Indication
WF on CSI timing offset for PUSCH
TSG-RAN WG1 Meeting #60bis
LTE-A Relays and Repeaters
WF on Radio Link Monitoring in NR
Motorola Mobility, Lenovo, …
WF on UE mandatory channel bandwidth for NR bands
WF on LTE-NR DC with UL coexistence
Summary on CA Aspects Samsung 3GPP TSG RAN WG1#91
WF on 4Tx UL Codebook For CP-OFDM
Nortel Corporate Presentation
Summary of Offline Discussion on RMSI CORESET Configuration (Part 2)
WF on UL Beam Management
WF on UL Beam Management
Summary on CA Aspects Samsung 3GPP TSG RAN WG1#91
Intra LTE Handover.
WF on Phase discontinuity issue in intra-band EN-DC with 1-PA
WF on LTE-NR Coexistence
LAMAS Working Group June 2017
3GPP RAN1 status on NR-Unlicensed
Status of NR-U - Wi-Fi coexistence
Jing Sun, Qualcomm Incorporated Rapporteur of Rel.16 NR-U Work Item
Presentation transcript:

WF on RA-RNTI design 3GPP TSG RAN WG1 Meeting NR#3 R1-171xxxx Nagoya, Japan, 18th – 21st, September 2017 Agenda item: 6.1.4.2 WF on RA-RNTI design MediaTek

Background (1/5) In LTE, the time and frequency information of a detected preamble is indicated by RA-RNTI which is defined as RA-RNTI = 1 + t_id + 10*f_id t_id: the subframe number in a radio frame where the Msg1 is started to be transmitted. t_id = 0, 1, …, 9 f_id: the index of RACH resources in the frequency dimension with f_id = 0, 1, …, 5

Background (2/5) Agreements from RAN1 NR AH#1: For 4-step RACH procedure, a RACH transmission occasion is defined as the time-frequency resource on which a PRACH message 1 is transmitted using the configured PRACH preamble format with a single particular tx beam

Background (3/5) Agreements from RAN1 NR AH#2: For L=127/139 with option 1, formats with 1,2,4,6, and 12 OFDM symbols are supported Agreements from RAN2 #99 For multiple msg1 transmissions for contention free RACH A single RAR window is applied for multiple msg1 transmission. The RAR window is started after transmission of the first preamble after a “offset”. The UE monitors multiple RA-RNTIs. The RA-RNTI is associated to the RACH transmission occasion in which the preamble was transmitted. Once a RAR is received, the RAR reception is considered successful, as in LTE. The UE stops multiple preamble transmission. Details of RA-RNTI calculations are FFS

Background (4/5) In NR, preamble formats with L=127/139 can be as short as one to several OFDM symbols. If an RA-RNTI formula similar to LTE is adopted in NR with t_id defined the symbol number in a radio frame, the number of required RA-RNTI values can be very large. Assumptions: SCS = 120kHz, i.e. 80 slots in a frame, and f_id = 0, 1, …, 5 as same as LTE The maximum number of RA-RNTI values required: 14 symbols/slot * 80 slots/frame * f_id = 14*80*6 > 212 NR needs to discuss how to indicate the (time and frequency) information of RACH transmission occasions where the detected preambles were transmitted. by means of RA-RNTI and RAR

Background (5/5) Comparison among alternatives for RA-RNTI and RAR design with the following assumptions the time duration considered is a 10ms radio frame the numerology is (a) 120 kHz and (b) 480kHz (i.e. 80 and 320 slots per frame, respectively) RAN4 does not preclude 240kHz and 480kHz for data in later releases for forward compatibility [R4-1704401] Six copies of RACH resources in the frequency dimension, i.e. f_id = 0,…,5   Variable(s) used in RA-RNTI besides f_id Maximum number of RA-RNTI values with SCS=120 kHz and 𝒇 𝒊𝒅 =𝟎,…,𝟓 Impact on RAR design Alt.1 The slot number within a frame The starting symbol number within a slot SCS=120kHz: 14∗80∗6=6720 < 2 13 SCS=480kHz: 14∗320∗6=26880 < 2 15 None Alt.2 The RACH occasion (RO) index in a radio frame =2∗64∗6=768 < 2 10 (assuming 2*64 ROs in the time dimension, i.e. periodicity of RACH resource is 5ms) Alt.3 The slot number in a radio frame SCS=120kHz: 80∗6=480 < 2 9 SCS=480kHz: 320∗6=1920 < 2 11 Indication of RO or symbol index within the slot Alt.4 The slot number in a radio frame And the index of SS blocks within a slot (assuming RACH preambles/resources within a slot associated with 14 SS blocks) RAPID should be re- defined accordingly

Proposal In addition to f_id, NR down-selects one of the following alternatives for RA-RNTI calculation Alt.1: The slot number within a frame and the starting symbol index within a slot Alt.2: The RACH transmission occasion (RO) index in a radio frame Alt.3: The slot number in a radio frame Note: Besides RAPID, RAR indicates information of RO or symbol index within the slot when more than one RO is allocated within a slot Alt.4: The slot number in a radio frame and the index of SS blocks within a slot Note: RAPID in RAR should be redefined accordingly as the preamble index within the subset of RACH preamble indices and/or resources associated with one SS block Note: f_id is the index of RACH resources in the frequency dimension