WO2022011685A1 - Nr-u pour une répétition de pdcch de bande rmsi de 6 ghz pour mode lpi - Google Patents

Nr-u pour une répétition de pdcch de bande rmsi de 6 ghz pour mode lpi Download PDF

Info

Publication number
WO2022011685A1
WO2022011685A1 PCT/CN2020/102708 CN2020102708W WO2022011685A1 WO 2022011685 A1 WO2022011685 A1 WO 2022011685A1 CN 2020102708 W CN2020102708 W CN 2020102708W WO 2022011685 A1 WO2022011685 A1 WO 2022011685A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless communications
communications device
rmsi pdcch
coreset
periodicity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/102708
Other languages
English (en)
Inventor
Luanxia YANG
Changlong Xu
Jing Sun
Xiaoxia Zhang
Hao Xu
Rajat Prakash
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2020/102708 priority Critical patent/WO2022011685A1/fr
Publication of WO2022011685A1 publication Critical patent/WO2022011685A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0045—Arrangements at the receiver end
    • H04L1/0046—Code rate detection or code type detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0072—Error control for data other than payload data, e.g. control data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0075—Transmission of coding parameters to receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • This application relates to wireless communication systems, and more particularly to improved downlink control channel communications, through coverage enhancement, in a wireless communication network.
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • a wireless multiple-access communications system may include a number of base stations (BSs) , each simultaneously supporting communications for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • BSs base stations
  • UE user equipment
  • NR next generation new radio
  • LTE long term evolution
  • NR next generation new radio
  • LTE long term evolution
  • NR next generation new radio
  • NR is designed to operate over a wide array of spectrum bands, for example, from low-frequency bands below about 1 gigahertz (GHz) and mid-frequency bands from about 1 GHz to about 6 GHz, to high-frequency bands such as millimeter wave (mmWave) bands.
  • GHz gigahertz
  • mmWave millimeter wave
  • NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed and shared spectrum. Spectrum sharing enables operators to opportunistically aggregate spectrums to dynamically support high-bandwidth services. Spectrum sharing can extend the benefit of NR technologies to operating entities that may not have access to a licensed spectrum.
  • the 6GHz unlicensed band is approved for use with NR technology, albeit with lower maximum power and a lower maximum power spectral density (PSD) than other bands.
  • PSD power spectral density
  • This lower power limit reduces the link budget, however, which particularly becomes an issue for lower power modes.
  • a method of wireless communication includes receiving, by a first wireless communications device in a low power indoor (LPI) mode, an indication of a repetition pattern for a remaining minimum system information (RMSI) physical downlink control channel (PDCCH) transmission from a second wireless communications device in the LPI mode.
  • the method further includes receiving, by the first wireless communications device, the RMSI PDCCH from the second wireless communications device.
  • the method further includes receiving, by the first wireless communications device, a repetition of the RMSI PDCCH from the second wireless communications device according to the repetition pattern identified in the indication.
  • LPI low power indoor
  • RMSI remaining minimum system information
  • PDCCH physical downlink control channel
  • a first wireless communications device includes a transceiver configured to receive in a low power indoor (LPI) mode, an indication of a repetition pattern for a remaining minimum system information (RMSI) physical downlink control channel (PDCCH) transmission from a second wireless communications device in the LPI mode.
  • the wireless communications device further includes a transceiver configured to receive the RMSI PDCCH from the second wireless communications device.
  • the wireless communications device further includes a transceiver configured to receive a repetition of the RMSI PDCCH from the second wireless communications device according to the repetition pattern identified in the indication.
  • a non-transitory computer-readable medium having program code recorded thereon includes code for causing a first wireless communications device to in a low power indoor (LPI) mode, an indication of a repetition pattern for a remaining minimum system information (RMSI) physical downlink control channel (PDCCH) transmission from a second wireless communications device in the LPI mode.
  • the non-transitory computer-readable medium further comprising code for causing the first wireless communications device to receive the RMSI PDCCH from the second wireless communications device.
  • the non- transitory computer-readable medium further comprising code for causing the first wireless communications device to receive a repetition of the RMSI PDCCH from the second wireless communications device according to the repetition pattern identified in the indication.
  • a first wireless communications device comprises means for receiving in a low power indoor (LPI) mode, an indication of a repetition pattern for a remaining minimum system information (RMSI) physical downlink control channel (PDCCH) transmission from a second wireless communications device in the LPI mode.
  • the first wireless communications device further comprises means for receiving the RMSI PDCCH from the second wireless communications device.
  • the first wireless communications device further comprises means for receiving a repetition of the RMSI PDCCH from the second wireless communications device according to the repetition pattern identified in the indication.
  • FIG. 1 illustrates a wireless communication network according to some embodiments of the present disclosure.
  • FIG. 2 illustrates a transmission frame for a communication network according to some embodiments of the present disclosure.
  • FIG. 3 illustrates a block diagram of a user equipment (UE) according to some embodiments of the present disclosure.
  • FIG. 4 illustrates a block diagram of an exemplary base station (BS) according to some embodiments of the present disclosure.
  • FIG. 5 illustrates a transmission frame structure for a communication network according to some embodiments of the present disclosure.
  • FIG. 6 illustrates a transmission frame for a communication network according to some embodiments of the present disclosure.
  • FIG. 7 illustrates a transmission frame for a communication network according to some embodiments of the present disclosure.
  • FIG. 8 illustrates a resource allocation table according to some embodiments of the present disclosure.
  • FIG. 9 illustrates a resource allocation table according to some embodiments of the present disclosure.
  • FIG. 10 illustrates a signaling diagram of a scheme for RMSI PDCCH monitoring according to some embodiments of the present disclosure.
  • FIG. 11 illustrates a signaling diagram of a scheme for RMSI PDCCH monitoring according to some embodiments of the present disclosure.
  • FIG. 12 illustrates a signaling diagram of a scheme for RMSI PDCCH monitoring according to some embodiments of the present disclosure.
  • FIG. 13 illustrates a flow diagram of a wireless communication method according to some embodiments of the present disclosure
  • FIG. 14 illustrates a flow diagram of a wireless communication method according to some embodiments of the present disclosure.
  • FIG. 15 illustrates a flow diagram of a wireless communication method according to some embodiments of the present disclosure.
  • wireless communications systems also referred to as wireless communications networks.
  • the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, Global System for Mobile Communications (GSM) networks, 5 th Generation (5G) or new radio (NR) networks, as well as other communications networks.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • LTE Long Term Evolution
  • GSM Global System for Mobile Communications
  • 5G 5 th Generation
  • NR new radio
  • An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA) , Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, orthogonal frequency division multiplexing (OFDM) and the like.
  • E-UTRA evolved UTRA
  • IEEE Institute of Electrical and Electronics Engineers
  • IEEE 802.20 IEEE 802.20
  • OFDM orthogonal frequency division multiplexing
  • UTRA, E-UTRA, and GSM are part of universal mobile telecommunication system (UMTS) .
  • LTE is a release of UMTS that uses E-UTRA.
  • UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided from an organization named “3rd Generation Partnership Project” (3GPP)
  • cdma2000 is described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • 3GPP 3rd Generation Partnership Project
  • LTE long term evolution
  • the 3GPP may define specifications for the next generation of mobile networks, mobile systems, and mobile devices.
  • the present disclosure is concerned with the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond with shared access to wireless spectrum between networks using a collection of new and different radio access technologies or radio air interfaces.
  • 5G networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface.
  • the 5G NR will be capable of scaling to provide coverage (1) to a massive Internet of things (IoTs) with an ultra-high density (e.g., ⁇ 1M nodes/km 2 ) , ultra-low complexity (e.g., ⁇ 10s of bits/sec) , ultra-low energy (e.g., ⁇ 10+years of battery life) , and deep coverage with the capability to reach challenging locations; (2) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., ⁇ 99.9999%reliability) , ultra-low latency (e.g., ⁇ 1 ms) , and users with wide ranges of mobility or lack thereof; and (3) with enhanced mobile broadband including extreme high capacity (e.g., ⁇ 10 Tbps/km 2 ) , extreme data rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates) , and deep awareness with advanced discovery and optimizations.
  • IoTs Internet of things
  • the 5G NR may be implemented to use optimized OFDM-based waveforms with scalable numerology and transmission time interval (TTI) ; having a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD) /frequency division duplex (FDD) design; and with advanced wireless technologies, such as massive multiple input, multiple output (MIMO) , robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility.
  • TTI transmission time interval
  • MIMO massive multiple input, multiple output
  • mmWave millimeter wave
  • Scalability of the numerology in 5G NR with scaling of subcarrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments.
  • subcarrier spacing may occur with 15 kHz, for example over 1, 5, 10, 20 MHz, and the like bandwidth (BW) .
  • BW bandwidth
  • subcarrier spacing may occur with 30 kHz over 80/100 MHz BW.
  • the subcarrier spacing may occur with 60 kHz over a 160 MHz BW.
  • subcarrier spacing may occur with 120 kHz over a 500 MHz BW.
  • the scalable numerology of the 5G NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. For example, shorter TTI may be used for low latency and high reliability, while longer TTI may be used for higher spectral efficiency.
  • QoS quality of service
  • 5G NR also contemplates a self-contained integrated subframe design with uplink/downlink scheduling information, data, and acknowledgement in the same subframe.
  • the self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink/downlink that may be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet the current traffic needs.
  • an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways.
  • an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein.
  • such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein.
  • a method may be implemented as part of a system, device, apparatus, and/or as instructions stored on a computer readable medium for execution on a processor or computer.
  • an aspect may comprise at least one element of a claim.
  • Communications can be in the form of radio frames.
  • a radio frame may be divided into a plurality of subframe, which can be divided into one or more slots. Each slot may be further divided into mini-slots.
  • a resource element comprises a single subcarrier in the frequency domain, and a single OFDM symbol in the time domain.
  • a resource element group (REG) may be comprised of a number of REs (e.g., 12) within a single OFDM symbol.
  • a control channel element (CCE) comprises a group of REGs.
  • a CORESET is a set of CCEs which is used to carry PDCCH transmissions, for example 1, 2, 4, 8, or 16 CCEs.
  • a CORESET is generally limited to span less than the full frequency range of a radio frame.
  • Each CORESET has an associated CCE to REG mapping. Frequencies within a CORESET can be contiguous or non-contiguous.
  • a CORESET may span one or more OFDM symbol time periods.
  • a set of potential PDCCH candidates is called a search space and is associated with a CORESET and can have configurable monitoring occasions defined.
  • a BS may configure a UE with one or more search spaces for PDCCH monitoring based on the predefined CORESET.
  • the UE may perform blind decoding in the search spaces to search for DL control information from the BS.
  • a BS may configure a UE with the BWPs, the CORESETS, and/or the PDCCH search spaces via RRC configurations.
  • BSs can broadcast system information associated with the network including a master information block (MIB) and remaining minimum system information (RMSI) to facilitate initial network access.
  • MIB master information block
  • RMSI remaining minimum system information
  • a BS can indicate to a UE scheduling for RMSI to be transmitted to a UE by RMSI PDCCH.
  • RMSI PDCCH When using a part of the spectrum that has reduced power requirements, it may be advantageous to increase the bandwidth of RMSI PDCCH or otherwise enhance the coverage of RMSI PDCCH in time (or in time and frequency) to ensure reliable delivery to the UE. This may be particularly useful in lower-power modes, such as low-power indoor (LPI) mode.
  • LPI low-power indoor
  • the LPI mode may refer to a mode that has a maximum allowed equivalent isotropically radiated power (EIRP) and power spectral density (PSD) that is low enough that a BS may use it in communicating with a UE without contacting an automated frequency coordination (AFC) function.
  • EIRP isotropically radiated power
  • PSD power spectral density
  • SP standard power
  • the LPI mode may have lower EIRP and PSD maximum, with the UE transmit power being less than the BS transmit power.
  • VLP very low-power
  • VLP very low-power
  • the present application describes mechanisms for providing repetitions of RMSI PDCCH so as to increase the effective bandwidth of the RMSI PDCCH waveform transmission (e.g., to mimic carrier aggregation) .
  • RMSI PDCCH repetitions may be in repetitions in time, either within a window of time or across windows of time.
  • RMSI PDCCH repetitions may alternatively be repetitions in frequency, such as in an instance of time.
  • both time and frequency repetitions may be used together.
  • a BS can indicate to the UE when and at what frequency repetitions may occur by sending information to that effect in an MIB.
  • the MIB may be, therefore, used to explicitly identify the repetition in time and/or frequency. This may be done by adding one or more fields to an allocation table, such as a frequency domain resource assignment (FDRA) table (such as with the same or similar format to the table provided in Section 13 of Version 16.1.0 of 3GPP TS 38.213, or equivalent) , as well as including all explicit signaling in rows that have been historically reserved in the FDRA table.
  • FDRA frequency domain resource assignment
  • an additional column may specify a time repetition pattern (where used) , the additional column being one column more than that currently in use.
  • a frequency repetition pattern may be specified in the field/column currently used for identifying the number of RBs for a CORESET. This may be signaled a variety of ways, including for example by specifying a sequence of values, starting with a number of RBs for a first CORESET, a number of RBs as a gap, then a next number of RBs for a second CORESET, another gap, and so forth until the last number of RBs for a last CORESET is provided.
  • the modified table may alternatively signal a combination of frequency and time repetitions for the UE to monitor. The UE can monitor the indicated repetitions according to the information in the MIB.
  • a UE may perform blind decoding on all or a subset of the repetitions indicated (e.g., in the MIB) .
  • the BS may signal the repetition pattern in a table, such as the FDRA table in the MIB.
  • the frequency and/or time repetitions may be signaled in additional columns of the table that have not previously been included in such tables.
  • One of the new columns may indicate the time repetition pattern by indicating the number of repetitions in time and the periodicity of the repetitions (whether intra-slot or inter-slot, for example) .
  • Another of the new columns may indicate the frequency repetition pattern by including an array with the number of frequency repetitions and the number of RBs as a guard band between each repetition (e.g., a sequence similar to that noted above that indicates a number of RMSI PDCCH replicated across frequencies) .
  • the modified table may signal a combination of frequency and time repetitions for the UE to attempt to blind decode.
  • a legacy UE receiving the table will be able to use all of the legacy fields of the table, while updated UEs will be able to access the additional information of the new columns. While discussed with respect to rows and columns, aspects of the present disclosure may be implemented another way or combination of ways in order to signal to UEs what resources to look for replicated RMSI PDCCHs.
  • a UE may begin with a hypothesis that no repetitions of the RMSI PDCCH exists, and therefore just perform blind decoding on the first RMSI PDCCH. This may be done, for example, based on the information signaled in the legacy fields of a table (e.g., in MIB) . If the blind decoding succeeds, then no further blind decoding may be necessary on any repetitions of the RMSI PDCCH. Alternatively, the UE may act according to a different hypothesis that assumes repetition occurs according to the additional parameters signaled in one or both of the new columns (e.g., for some combination of time and/or frequency repetition of the RMSI PDCCH) . The UE may soft combine all of the monitored resource blocks across time and/or frequency according to the signaled repetition pattern and then do blind decoding.
  • the blind decoding hypothesis may need to extend across slots (e.g., where a time repetition pattern signaled in the MIB indicates that some of the replicated RMSI PDCCHs will occur in different slots from each other) .
  • the first hypothesis may be performed at or after the start of each slot where the RMSI PDCCH is scheduled to occur.
  • the UE may soft combine the duplicates of the RMSI PDCCHs monitored at each of the occasions identified in the table and then attempt blind decoding once all collected (e.g., buffered or otherwise stored) . If blind decoding fails, the UE may puncture the first slot and soft combine the remaining RMSI PDCCHs in the remaining slot (s) and attempt blind decoding again. This may be repeated until the decoding is successful or the last RMSI PDCCH is left.
  • the UE may try the first hypothesis (e.g., no repetition) for a set period of time (e.g., on the order of multiple slots) , and then try the next hypothesis (e.g., repetition) for another set period of time.
  • Another example may try both hypotheses within the same slot, as described in some of the examples above.
  • aspects of the present disclosure can provide several benefits. For example, configuring a UE to monitor for RMSI PDCCH where the CORESETs cover different frequency ranges can provide frequency diversity. Such frequency diversity can help make the communication more robust, as any frequency-dependent weakness in the channel could be mitigated. Further, by repeating RMSI PDCCH in frequency, the effective power utilized can be increased without exceeding the allowed power budget. This can make RMSI PDCCH more reliable. Further, repeating in time may allow coverage enhancement without increasing transmit power to stay within the allowed power budget for a given power mode (such as LPI mode) . Embodiments may provide flexibility in the locations in time and frequency of the repetitions, allowing the BS and UE to optimize RMSI PDCCH transmission for the present condition in the communication environment.
  • FIG. 1 illustrates a wireless communication network 100 according to some aspects of the present disclosure.
  • the network 100 may be a 5G network.
  • the network 100 includes a number of base stations (BSs) 105 (individually labeled as 105a, 105b, 105c, 105d, 105e, and 105f) and other network entities.
  • a BS 105 may be a station that communicates with UEs 115 and may also be referred to as an evolved node B (eNB) , a next generation eNB (gNB) , an access point, and the like.
  • eNB evolved node B
  • gNB next generation eNB
  • Each BS 105 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to this particular geographic coverage area of a BS 105 and/or a BS subsystem serving the coverage area, depending on the context in which the term is used.
  • a BS 105 may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, and/or other types of cell.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a small cell such as a pico cell, would generally cover a relatively smaller geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a small cell such as a femto cell, would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG) , UEs for users in the home, and the like) .
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS or a home BS. In the example shown in FIG.
  • the BSs 105d and 105e may be regular macro BSs, while the BSs 105a-105c may be macro BSs enabled with one of three dimension (3D) , full dimension (FD) , or massive MIMO.
  • the BSs 105a-105c may take advantage of their higher dimension MIMO capabilities to exploit 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity.
  • the BS 105f may be a small cell BS which may be a home node or portable access point.
  • a BS 105 may support one or multiple (e.g., two, three, four, and the like) cells.
  • the network 100 may support synchronous or asynchronous operation.
  • the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time.
  • the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.
  • the UEs 115 are dispersed throughout the wireless network 100, and each UE 115 may be stationary or mobile.
  • a UE 115 may also be referred to as a terminal, a mobile station, a subscriber unit, a station, or the like.
  • a UE 115 may be a cellular phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, or the like.
  • PDA personal digital assistant
  • WLL wireless local loop
  • a UE 115 may be a device that includes a Universal Integrated Circuit Card (UICC) .
  • a UE may be a device that does not include a UICC.
  • UICC Universal Integrated Circuit Card
  • the UEs 115 that do not include UICCs may also be referred to as IoT devices or internet of everything (IoE) devices.
  • the UEs 115a-115d are examples of mobile smart phone-type devices accessing network 100.
  • a UE 115 may also be a machine specifically configured for connected communication, including machine type communication (MTC) , enhanced MTC (eMTC) , narrowband IoT (NB-IoT) and the like.
  • MTC machine type communication
  • eMTC enhanced MTC
  • NB-IoT narrowband IoT
  • the UEs 115e-115k are examples of various machines configured for communication that access the network 100.
  • a UE 115 may be able to communicate with any type of the BSs, whether macro BS, small cell, or the like. In FIG.
  • a lightning bolt (e.g., communication links) indicates wireless transmissions between a UE 115 and a serving BS 105, which is a BS designated to serve the UE 115 on the downlink and/or uplink, or desired transmission between BSs, and backhaul transmissions between BSs.
  • the BSs 105a-105c may serve the UEs 115a and 115b using 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity.
  • the macro BS 105d may perform backhaul communications with the BSs 105a-105c, as well as small cell, the BS 105f.
  • the macro BS 105d may also transmits multicast services which are subscribed to and received by the UEs 115c and 115d.
  • Such multicast services may include mobile television or stream video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.
  • the BSs 105 may also communicate with a core network.
  • the core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • IP Internet Protocol
  • At least some of the BSs 105 (e.g., which may be an example of a gNB or an access node controller (ANC) ) may interface with the core network through backhaul links (e.g., NG-C, NG-U, etc. ) and may perform radio configuration and scheduling for communication with the UEs 115.
  • the BSs 105 may communicate, either directly or indirectly (e.g., through core network) , with each other over backhaul links (e.g., X1, X2, etc. ) , which may be wired or wireless communication links.
  • the network 100 may also support mission critical communications with ultra-reliable and redundant links for mission critical devices, such as the UE 115e, which may be a drone. Redundant communication links with the UE 115e may include links from the macro BSs 105d and 105e, as well as links from the small cell BS 105f.
  • UE 115f e.g., a thermometer
  • UE 115g e.g., smart meter
  • UE 115h e.g., wearable device
  • the network 100 may also provide additional network efficiency through dynamic, low-latency TDD/FDD communications, such as in a vehicle-to-vehicle (V2V)
  • V2V vehicle-to-vehicle
  • the network 100 utilizes OFDM-based waveforms for communications.
  • An OFDM-based system may partition the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, bins, or the like. Each subcarrier may be modulated with data.
  • the subcarrier spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system BW.
  • the system BW may also be partitioned into subbands. In other instances, the subcarrier spacing and/or the duration of TTIs may be scalable.
  • the BSs 105 can assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RB) ) for downlink (DL) and uplink (UL) transmissions in the network 100.
  • DL refers to the transmission direction from a BS 105 to a UE 115
  • UL refers to the transmission direction from a UE 115 to a BS 105.
  • the communication can be in the form of radio frames.
  • a radio frame may be divided into a plurality of subframes or slots, for example, about 10. Each slot may be further divided into mini-slots. In a FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands.
  • each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band.
  • UL and DL transmissions occur at different time periods using the same frequency band.
  • a subset of the subframes (e.g., DL subframes) in a radio frame may be used for DL transmissions and another subset of the subframes (e.g., UL subframes) in the radio frame may be used for UL transmissions.
  • each DL or UL subframe may have pre-defined regions for transmissions of reference signals, control information, and data.
  • Reference signals are predetermined signals that facilitate the communications between the BSs 105 and the UEs 115.
  • a reference signal can have a particular pilot pattern or structure, where pilot tones may span across an operational BW or frequency band, each positioned at a pre-defined time and a pre-defined frequency.
  • a BS 105 may transmit cell specific reference signals (CRSs) and/or channel state information –reference signals (CSI-RSs) to enable a UE 115 to estimate a DL channel.
  • CRSs cell specific reference signals
  • CSI-RSs channel state information –reference signals
  • a UE 115 may transmit sounding reference signals (SRSs) to enable a BS 105 to estimate a UL channel.
  • SRSs sounding reference signals
  • Control information may include resource assignments and protocol controls.
  • Data may include protocol data and/or operational data.
  • Control information, such as PDCCH etc. has been discussed above and will be described further below with respect to embodiments of the present disclosure.
  • the BSs 105 and the UEs 115 may communicate using self-contained subframes.
  • a self-contained subframe may include a portion for DL communication and a portion for UL communication.
  • a self-contained subframe can be DL-centric or UL-centric.
  • a DL-centric subframe may include a longer duration for DL communication than for UL communication.
  • a UL-centric subframe may include a longer duration for UL communication than for UL communication.
  • the network 100 may be an NR network deployed over a licensed spectrum.
  • the BSs 105 can transmit synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) ) in the network 100 to facilitate synchronization.
  • the BSs 105 can broadcast system information associated with the network 100 (e.g., including a master information block (MIB) , remaining minimum system information (RMSI) , and other system information (OSI) ) to facilitate initial network access.
  • MIB master information block
  • RMSI remaining minimum system information
  • OSI system information
  • the BSs 105 may broadcast the PSS, the SSS, and/or the MIB in the form of synchronization signal blocks (SSBs) over a physical broadcast channel (PBCH) and may broadcast the RMSI and/or the OSI over a physical downlink shared channel (PDSCH) .
  • PBCH physical broadcast channel
  • PDSCH physical downlink shared channel
  • a UE 115 attempting to access the network 100 may perform an initial cell search by detecting a PSS from a BS 105.
  • the PSS may enable synchronization of period timing and may indicate a physical layer identity value.
  • the UE 115 may then receive a SSS.
  • the SSS may enable radio frame synchronization, and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell.
  • the PSS and the SSS may be located in a central portion of a carrier or any suitable frequencies within the carrier.
  • the UE 115 may receive a MIB.
  • the MIB may include system information for initial network access and scheduling information for RMSI and/or OSI.
  • the UE 115 may receive RMSI and/or OSI.
  • the RMSI and/or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource set (CORESET) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH) , physical uplink shared channel (PUSCH) , power control, and SRS.
  • RRC radio resource control
  • the UE 115 can perform a random access procedure to establish a connection with the BS 105.
  • the UE 115 may transmit a random access preamble and the BS 105 may respond with a random access response.
  • the UE 115 may transmit a connection request to the BS 105 and the BS 105 may respond with a connection response (e.g., contention resolution message) .
  • the UE 115 and the BS 105 can enter a normal operation stage, where operational data may be exchanged.
  • the BS 105 may schedule the UE 115 for UL and/or DL communications.
  • the BS 105 may transmit UL and/or DL scheduling grants to the UE 115 via a PDCCH.
  • the BS 105 may transmit a DL communication signal to the UE 115 via a PDSCH according to a DL scheduling grant.
  • the UE 115 may transmit a UL communication signal to the BS 105 via a PUSCH and/or PUCCH according to a UL scheduling grant.
  • the network 100 may operate over a system BW or a component carrier (CC) BW.
  • the network 100 may partition the system BW into multiple bandwidth parts (BWPs) (e.g., portions) .
  • BWPs bandwidth parts
  • a BS 105 may dynamically assign a UE 115 to operate over a certain BWP (e.g., a certain portion of the system BW) .
  • the assigned BWP may be referred to as the active BWP.
  • the UE 115 may monitor the active BWP for signaling information from the BS 105.
  • the BS 105 may schedule the UE 115 for UL or DL communications in the active BWP.
  • a BS 105 may assign a pair of BWPs within the CC to a UE 115 for UL and DL communications.
  • the BWP pair may include one BWP for UL communications and one BWP for DL communications.
  • the BS 105 may additionally configure the UE 115 with one or more CORESETs in a BWP.
  • a CORESET may include a set of frequency resources spanning a number of symbols in time.
  • the BS 105 may configure the UE 115 with one or more search spaces for PDCCH monitoring based on the CORESETS.
  • the UE 115 may perform blind decoding in the search spaces to search for DL control information from the BS.
  • the BS 105 may configure the UE 115 with the BWPs, the CORESETS, and/or the PDCCH search spaces via RRC configurations. Mechanisms for configuring search spaces are described in greater detail herein.
  • the network 100 may operate over a shared channel, which may include shared frequency bands or unlicensed frequency bands.
  • the network 100 may be an NR-U network.
  • the BSs 105 and the UEs 115 may be operated by multiple network operating entities.
  • the BSs 105 and the UEs 115 may employ a listen-before-talk (LBT) procedure to monitor for transmission opportunities (TXOPs) in the shared channel.
  • LBT listen-before-talk
  • TXOPs transmission opportunities
  • a BS 105 may acquire or reserve a TXOP or a channel occupancy time (COT) in the shared channel by performing a CAT4 LBT.
  • a CAT4 LBT refers to an LBT with a random backoff and a variable contention window.
  • the BS 105 may schedule one or more UEs 115 for DL communications and/or UL communications within the acquired COT.
  • the 6GHz band is being made available for unlicensed use (e.g., in addition to other unlicensed bands such as 5 GHz) . So as to not disrupt incumbent licensed use in the band, power levels are limited depending on the context. Allowed power levels are determined by the mode of operation and the context.
  • AFC automated frequency control
  • SP Standard-Power
  • a BS may be allowed 36 dBm maximum equivalent isotropic radiated power (EIRP) and 23 dBm/MHz maximum EIRP power spectral density (PSD) .
  • EIRP equivalent isotropic radiated power
  • PSD power spectral density
  • a Low-Power access point may be allowed 30 dBm maximum EIRP and 5 dBm/MHz maximum EIRP PSD across the entire 1, 200 MHz of the 6GHz band, without being under the control of an AFC function.
  • clients e.g. UEs
  • SP and LPI Low-Power indoor
  • a UE 115 attempting to access the network 100 via NR-U may receive a modified MIB.
  • the MIB may include system information for initial network access and scheduling information for RMSI and/or OSI.
  • the MIB may include one or more additional fields in a table of the MIB used to identify the CORESET on which RMSI PDCCH is repeated.
  • the table may utilize additional rows that would have been reserved otherwise to signal the time and/or frequency repetition details of the RMSI PDCCH.
  • the table may utilize additional columns to identify the time and/or frequency repetition details, so that legacy UEs may also be supported in operating with the table information in the MIB.
  • the UE 115 may monitor the identified CORESET (s) for the repetitions of the RMSI PDCCH.
  • the UE 115 may locate the RMSI PDCCHs as explicitly indicated in the MIB, while in other examples the UE 115 may implement one or more blind decoding hypotheses to obtain the RMSI PDCCHs. This may start with a hypothesis of no repetition. If successful, the UE 115 proceeds according to the information it locates in the identified RMSI and/or OSI. Otherwise, the UE 115 may proceed with another hypothesis that includes soft combining the information observed at the resource elements at which RMSI PDCCH is repeated according to embodiments of the present disclosure, and then blind decoding is attempted.
  • the UE 115 may start puncturing specific instances of the repeated RMSI PDCCHs monitored (e.g., starting with the first) and repeat the soft combining and decoding until successful, as will be discussed in more detail with respect to further figures below.
  • the RMSI may include information as noted above and the UE 115 may proceed with establishing a connection.
  • FIG. 2 is a timing diagram illustrating a transmission frame structure 200 according to some embodiments of the present disclosure.
  • the transmission frame structure 200 may be employed by BSs such as the BSs 105 and UEs such as the UEs 115 in a network such as the network 100 for communications.
  • the BS may communicate with the UE using time-frequency resources configured as shown in the transmission frame structure 200.
  • the x-axes represent time in some arbitrary units and the y-axes represent frequency in some arbitrary units.
  • the transmission frame structure 200 includes a radio frame 201.
  • the duration of the radio frame 201 may vary depending on the embodiments. In an example, the radio frame 201 may have a duration of about ten milliseconds.
  • the radio frame 201 includes M number of slots 20, where M may be any suitable positive integer. In an example, M may be about 10.
  • Each slot 202 includes a number of subcarriers 204 in frequency and a number of symbols 206 in time.
  • the number of subcarriers 204 and/or the number of symbols 206 in a slot 202 may vary depending on the embodiments, for example, based on the channel bandwidth, the subcarrier spacing (SCS) , and/or the cyclic prefix (CP) mode.
  • One subcarrier 204 in frequency and one symbol 206 in time forms one resource element (RE) 212 for transmission.
  • RE resource element
  • the UE 115 may perform blind decoding in the search spaces to search for DL control information (e.g., slot format information and/or scheduling information) from the BS 105.
  • DL control information e.g., slot format information and/or scheduling information
  • the UE 115 may search a subset of the search spaces based on certain rules, for example, associated with the UE 115’s channel estimation and/or blind decoding capabilities.
  • One such example of DL control information the UE 115 may be blind decoding for is a RMSI PDCCH from the BS 105.
  • a RMSI PDCCH may be repeated across the and/or frequency in order to increase coverage for the RMSI PDCCH while remaining within a specified PSD and EIRP (e.g., according to a low power mode such as LPI mode) .
  • the particular repetition pattern for RMSI PDCCH may be signaled by the BS 105 in one or more MIBs, such as in a modified FDRA table as will be discussed in more detail below.
  • FIG. 3 is a block diagram of an exemplary UE 300 according to embodiments of the present disclosure.
  • the UE 300 may be a UE 115 in the network 100 as discussed above in FIG. 1.
  • the UE 300 may include a processor 302, a memory 304, a RMSI PDCCH monitor module 308, a transceiver 310 including a modem subsystem 312 and a radio frequency (RF) unit 314, and one or more antennas 316.
  • RF radio frequency
  • the processor 302 may include a central processing unit (CPU) , a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
  • the processor 302 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the memory 304 may include a cache memory (e.g., a cache memory of the processor 302) , random access memory (RAM) , magnetoresistive RAM (MRAM) , read-only memory (ROM) , programmable read-only memory (PROM) , erasable programmable read only memory (EPROM) , electrically erasable programmable read only memory (EEPROM) , flash memory, solid state memory device, hard disk drives, other forms of volatile and non-volatile memory, or a combination of different types of memory.
  • the memory 304 includes a non-transitory computer-readable medium.
  • the memory 404 may store, or have recorded thereon, instructions 306.
  • the instructions 306 may include instructions that, when executed by the processor 302, cause the processor 302 to perform the operations described herein with reference to the UEs 115 in connection with embodiments of the present disclosure, for example, aspects of FIG. 5-15. Instructions 306 may also be referred to as program code.
  • the program code may be for causing a wireless communication device to perform these operations, for example by causing one or more processors (such as processor 302) to control or command the wireless communication device to do so.
  • the terms “instructions” and “code” should be interpreted broadly to include any type of computer-readable statement (s) .
  • the terms “instructions” and “code” may refer to one or more programs, routines, sub-routines, functions, procedures, etc. “Instructions” and “code” may include a single computer-readable statement or many computer-readable statements.
  • the RMSI PDCCH monitor module 308 may be implemented via hardware, software, or combinations thereof.
  • the RMSI PDCCH monitor module 308 may be implemented as a processor, circuit, and/or instructions 306 stored in the memory 304 and executed by the processor 302.
  • the RMSI PDCCH monitor module 308 can be integrated within the modem subsystem 312.
  • the RMSI PDCCH monitor module 308 can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 312.
  • the RMSI PDCCH monitor module 308 may be used for various aspects of the present disclosure, for example, aspects of FIGS. 5-14.
  • the RMSI PDCCH monitor module 308 is configured to receive a repetition pattern from a BS (e.g., BS 105 in FIG. 1) .
  • the repetition pattern may be contained, for example, in a table conveyed in an MIB from the BS 105.
  • the repetition pattern may indicate the time and frequency repetitions of RMSI PDCCH transmissions from the BS.
  • the MIB may be, therefore, used to explicitly identify the repetition in time and/or frequency.
  • the RMSI PDCCH monitor module 308 may access this information via one or more additional fields of an allocation table, such as an FDRA table (or equivalent) . This may be accessed via rows that have been historically reserved in the FDRA table, as well as in an additional column.
  • an additional column (beyond that currently in use, for example) may specify a time repetition pattern (where used) that the RMSI PDCCH monitor module 308 accesses.
  • a frequency repetition pattern may be specified in the field/column currently used for identifying the number of RBs for a CORESET. This may be signaled a variety of ways, including for example by specifying a sequence of values, starting with a number of RBs for a first CORESET, a number of RBs as a gap, then a next number of RBs for a second CORESET, another gap, and so forth until the last number of RBs for a last CORESET is provided.
  • the RMSI PDCCCH monitor module 308 may access this information and determine from it the number of RMSI PDCCH replicated across frequencies (e.g., different CORESETs corresponding to different RMSI PDCCHs) . Moreover, the modified table may alternatively signal a combination of frequency and time repetitions for the RMSI PDCCH monitor module 308 to monitor.
  • the UE 300 for example by way of the RMSI PDCCH monitor module 308, can monitor the indicated repetitions according to the information in the MIB.
  • the MIB may be used to signal repetitions of RMSI PDCCH in time and/or frequency that is compatible for multiple power modes, such as SP and LPI modes.
  • the RMSI PDCCH monitor module 308 may use the information signaled in the MIB to perform blind decoding on all or a subset of the repetitions indicated (obtained from) the MIB according to one or more hypotheses. Similar to the other example, the RMSI PDCCH monitor module 308 may access the additional information regarding repetition in a modified form of the FDRA table (as one example of a table) .
  • the frequency and/or time repetitions may be signaled in additional columns of the table that have not previously been included in such tables.
  • One of the new columns may indicate the time repetition pattern by indicating the number of repetitions in time and the periodicity of the repetitions (whether intra-slot or inter-slot, for example) .
  • Another of the new columns may indicate the frequency repetition pattern by including an array with the number of frequency repetitions and the number of RBs as a guard band between each repetition (e.g., a sequence similar to that noted above that indicates a number of RMSI PDCCH replicated across frequencies) .
  • a legacy UE receiving the table will be able to use all of the legacy fields of the table, while updated UEs will be able to access the additional information of the new columns. While discussed with respect to rows and columns, aspects of the present disclosure may be implemented another way or combination of ways in order to signal to UEs what resources to look for replicated RMSI PDCCHs.
  • the RMSI PDCCH monitor module 308 may access the RMSI PDCCH information in the modified table.
  • the RMSI PDCCH monitor module 308 may operate according to a first hypothesis that assumes no repetition of the RMSI PDCCH (e.g., the repetitions that would be signaled in additional/new fields of the table) .
  • the first hypothesis assumes that no repetitions of the RMSI PDCCH exists, and therefore the RMSI PDCCH monitor module 308 causes the UE 300 to perform blind decoding on the first RMSI PDCCH identified in the legacy fields of the table from the MIB. If the blind decoding succeeds, then the RMSI PDCCH monitor module 308 does not cause further blind decoding (e.g., such as on any repetitions of the RMSI PDCCH identified in the added fields of the table) .
  • the RMSI PDCCH monitor module 308 may act according to a second hypothesis that assumes repetition occurs according to the additional parameters signaled in one or both of the new columns (e.g., for some combination of time and/or frequency repetition of the RMSI PDCCH) .
  • the RMSI PDCCH monitor module 308 may cause the UE 300 to soft combine all of the monitored resource elements across time and/or frequency according to the signaled repetition pattern and then do blind decoding (e.g., by the RMSI PDCCH monitor module 308 or some other processor or controller of the UE 300) .
  • the blind decoding hypothesis may extend across slots (e.g., where a time repetition pattern signaled in the MIB indicates that some of the replicated RMSI PDCCHs will occur in different slots from each other) .
  • the RMSI PDCCH monitor module 308 may attempt the first hypothesis at or after the start of each slot where the RMSI PDCCH is scheduled to occur. Across the slots, the RMSI PDCCH monitor module 308 may soft combine the duplicates of the RMSI PDCCHs monitored at each of the occasions identified in the table and then attempt blind decoding once all collected (e.g., buffered or otherwise stored) .
  • the RMSI PDCCH monitor module 308 may puncture the first slot and soft combine the remaining RMSI PDCCHs in the remaining slot (s) and attempt blind decoding again. This may be repeated until the decoding is successful or the last RMSI PDCCH is left.
  • the transceiver 310 may include the modem subsystem 312 and the RF unit 314.
  • the transceiver 310 can be configured to communicate bi-directionally with other devices, such as the BSs 105.
  • the modem subsystem 312 may be configured to modulate and/or encode the data from the memory 304 according to a modulation and coding scheme (MCS) , e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.
  • MCS modulation and coding scheme
  • LDPC low-density parity check
  • the RF unit 314 may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.
  • the RF unit 314 may be further configured to perform analog beamforming in conjunction with the digital beamforming. Although shown as integrated together in transceiver 310, the modem subsystem 312 and the RF unit 314 may be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.
  • the RF unit 314 may provide the modulated and/or processed data, e.g. data packets (or, more generally, data messages that may contain one or more data packets and other information) , to the antennas 316 for transmission to one or more other devices.
  • the antennas 316 may further receive data messages transmitted from other devices, such as MIB and RMSI PDCCHs according to embodiments of the present disclosure.
  • the antennas 316 may provide the received data messages for processing and/or demodulation at the transceiver 310, and provide the information to the RMSI PDCCH monitor module 308.
  • the antennas 316 may include multiple antennas of similar or different designs in order to sustain multiple transmission links.
  • the RF unit 314 may configure the antennas 316.
  • the UE 300 can include multiple transceivers 310 implementing different Radio Access Technologies (RATs) (e.g., NR and LTE) .
  • RATs Radio Access Technologies
  • the UE 300 can include a single transceiver 310 implementing multiple RATs (e.g., NR and LTE) .
  • the transceiver 310 can include various components, where different combinations of components can implement RATs.
  • FIG. 4 is a block diagram of an exemplary BS 400 according to embodiments of the present disclosure.
  • the BS 400 may be a BS 105 in the network 100 as discussed above in FIG. 1.
  • the BS 400 may include a processor 402, a memory 404, a RMSI PDCCH module 408, a transceiver 410 including a modem subsystem 412 and a RF unit 414, and one or more antennas 416. These elements may be in direct or indirect communication with each other, for example via one or more buses.
  • the processor 402 may have various features as a specific-type processor. For example, these may include a CPU, a DSP, an ASIC, a controller, a FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
  • the processor 402 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the memory 404 may include a cache memory (e.g., a cache memory of the processor 402) , RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, a solid state memory device, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory.
  • the memory 404 may include a non-transitory computer-readable medium.
  • the memory 404 may store instructions 406.
  • the instructions 406 may include instructions that, when executed by the processor 402, cause the processor 402 to perform operations described herein, for example, aspects of FIGS. 2-3 and 6-11. Instructions 406 may also be referred to as code, which may be interpreted broadly to include any type of computer-readable statement (s) as discussed above with respect to FIG. 4.
  • the RMSI PDCCH module 408 may be implemented via hardware, software, or combinations thereof.
  • the RMSI PDCCH module 408 may be implemented as a processor, circuit, and/or instructions 406 stored in the memory 404 and executed by the processor 402.
  • the RMSI PDCCH module 408 can be integrated within the modem subsystem 412.
  • the RMSI PDCCH module 408 can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 412.
  • the RMSI PDCCH module 408 may be used for various aspects of the present disclosure, for example, aspects of FIGS. 5-15.
  • the RMSI PDCCH module 408 is configured to transmit a repetition pattern to a UE (e.g., UE 115 in FIG. 1) .
  • the repetition pattern may indicate the number of time repetitions and the periodicity of the repetitions.
  • the repetition pattern may also indicate the number of frequency repetitions and the guard band between each.
  • the repetition pattern may include both time and frequency repetitions together.
  • the repetition pattern may be signaled via the MIB, such as in an FDRA table as discussed above.
  • the RMSI PDCCH module 408 may populate the modified portions of the FDRA table with the repetition pattern information that will be signaled to one or more UEs 115.
  • This may include, in some embodiments, the explicit signaling via MIB that a UE 115 may implement.
  • This may include in other embodiments the signaling that may be used by different UEs 115 in different power modes, where a given UE 115 may operate according to one or more hypothesis for blind decoding as discussed above and further below.
  • the RMSI PDCCH module 408 may use one or more inputs or states to determine when and how to activate RMSI PDCCH repetitions. For example, the RMSI PDCCH module 408 may consider channel quality measurements, either direct or indirect. This may include, for example, the RMSI PDCCH module 408 selecting a repetition pattern with more time and/or frequency repetitions in environments where the channel quality information indicates a poor channel, and a repetition pattern (or no repetition pattern at all) in environments where the channel quality information indicates a much better channel. In addition or alternatively, the RMSI PDCCH module 408 may consider the operating mode of the BS and the UE (e.g. standard-power, low-power indoor, or very low-power modes) . In other examples, the RMSI PDCCH module 408 selects the repetitions for a UE 115 according to a preset determination.
  • the RMSI PDCCH module 408 selects the repetitions for a UE 115 according to a preset determination.
  • the transceiver 410 may include the modem subsystem 412 and the RF unit 414.
  • the transceiver 410 can be configured to communicate bi-directionally with other devices, such as the UEs 115 and/or another core network element.
  • the modem subsystem 412 may be configured to modulate and/or encode data according to a MCS, e.g., a LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.
  • the RF unit 414 may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.
  • the RF unit 414 may be further configured to perform analog beamforming in conjunction with the digital beamforming. Although shown as integrated together in transceiver 410, the modem subsystem 412 and/or the RF unit 414 may be separate devices that are coupled together at the BS 105 to enable the BS 105 to communicate with other devices.
  • the RF unit 414 may provide the modulated and/or processed data, e.g. data packets (or, more generally, data messages that may contain one or more data packets and other information) , to the antennas 416 for transmission to one or more other devices. This may include, for example, transmission of information to complete attachment to a network and communication with a UE 115 or 400 according to embodiments of the present disclosure.
  • the antennas 416 may further receive data messages transmitted from other devices and provide the received data messages for processing and/or demodulation at the transceiver 410.
  • the antennas 416 may include multiple antennas of similar or different designs in order to sustain multiple transmission links.
  • the BS 400 can include multiple transceivers 410 implementing different RATs (e.g., NR and LTE) .
  • the BS 400 can include a single transceiver 410 implementing multiple RATs (e.g., NR and LTE) .
  • the transceiver 410 can include various components, where different combinations of components can implement RATs.
  • FIG. 5 illustrates a transmission frame structure 500 according to some embodiments of the present disclosure.
  • the transmission frame structure 500 may be employed by BSs such as the BSs 400 or 105 and UEs such as the UEs 300 or 115 in a network, such as the network 100, for communications.
  • the BS 400 may communicate with the UE 300 using time-frequency resources configured as shown in the transmission frame structure 500.
  • the x-axes represent time in some arbitrary units and the y-axes represent frequency in some arbitrary units.
  • FIG. 5 illustrates four repetitions of RMSI PDCCH (RMSI PDSCH is not illustrated for simplicity and clarity in demonstrating aspects of the present disclosure) .
  • the four repetitions are exemplary –many other amounts of repetitions may occur according to embodiments of the present disclosure.
  • Each RMSI PDCCH (510, 512, 514, and 516 as the examples in FIG. 5) may span a number of symbols represented by time span 504, such as 1-3 symbols in some examples.
  • Each RMSI PDCCH (510, 512, 514, and 516) may span a bandwidth of some number of RBs represented by bandwidth 506. This may also be referred to as the PDCCH RMSI CORESET, or RMSI CORESET.
  • the bandwidth 406 may be identified by one or more fields of a table, such as an FDRA table, in an MIB from a BS 400.
  • the BS 400 may configure the UE 300 to monitor each repetition in time of RMSI PDCCH (such as the repetitions shown in timing diagram 500) .
  • the RMSI PDCCH repetitions may be inter-slot, or intra-slot, or both.
  • a slot may end at time 550, in which case the RMSI PDCCH repetitions would occur both inter-slot and intra-slot.
  • the entire timing diagram 500 may be within a single slot, in which case each repetition would be intra-slot.
  • the periodicity of repetitions could be such that repetitions only occur inter-slot.
  • the BS 400 may transmit RMSI PDCCH repeated in the time domain, with no repetitions in the frequency domain.
  • the BS 400 may indicate to the UE the periodicity 502 of the repetitions, and the number of repetitions in time. The manner in which this may be done will be described in more detail with respect the FIGS. 8-15 (e.g., explicitly indicated in one type of MIB table or another type of MIB table for use with hypothesis testing) .
  • UE 300 may decode all or a subset of the RMSI PDCCH repetitions as will be described with reference to FIGS. 10-15.
  • the transmission frame structure 600 may be similar to transmission frame structure 500 (e.g., with RMSI PDCCH spanning a number of symbols in the time domain, and a RMSI CORESET in the frequency domain, etc. ) .
  • the transmission frame structure 600 may be employed by BSs such as the BSs 400 or 105 and UEs such as the UEs 300 or 115 in a network such as the network 100 for communications.
  • the BS 400 may transmit RMSI PDCCH repetitions in the frequency domain with no repetitions in the time domain.
  • RMSI PDCCH 610, 612, 614, and 616 each occupy time span 604 in the time domain, such as 1-3 symbols within a given slot.
  • RMSI PDCCH 610, 612, 614, and 616 each have a respective bandwidth 606 occupying some number of RBs in the frequency domain.
  • Each repetition in the frequency domain may have a guard band 608 between other repetitions.
  • BS 400 may indicate to UE 300 the number of frequency repetitions, and their guard band size. Each amount may be specified in terms of numbers of RBs, for example. The number of repetitions illustrated in FIG.
  • UE 300 may decode all or a subset of the RMSI PDCCH repetitions as will be described with reference to FIGS. 10-15.
  • FIG. 7 is a timing diagram illustrating a transmission frame structure 700 according to some embodiments of the present disclosure.
  • the transmission frame structure 700 is similar to transmission frame structures 500 and 600 in that it includes RMSI PDCCH repetitions in both the time and frequency domains.
  • the transmission frame structure 700 may be employed by BSs such as the BSs 400 or 105 and UEs such as the UEs 300 or 115 in a network such as the network 100 for communications.
  • RMSI PDCCH repetitions may span both time and frequency domains.
  • RMSI PDCCHs 710-740 may be repeated in an array with periodicity 702 in time, length 704 in time, bandwidth 706 in frequency (e.g., in number of RBs) , and with guard band 708 in the frequency axis in some number of RBs.
  • BS 400 may indicate these parameters to UE 300 in a manner such as will be described in more detail with respect the FIGS. 8-15.
  • UE 300 may decode all or a subset of the RMSI PDCCH repetitions as will be described with reference to FIGS. 10-15.
  • time 750 may be a slot division in timing diagram 700. If time 750 is a slot division, then the RMSI PDCCH repetitions as illustrated occur on both an inter-slot and an intra-slot basis. Alternatively, timing diagram 700 may span a single slot, in which case the illustrated RMSI PDCCH repetitions are intra-slot. As another alternative, the periodicity of repetitions may be inter-slot.
  • FIG. 8 is an example of a table 800 according to some embodiments of the present disclosure.
  • the table 800 may be an FDRA table that has been modified as discussed further herein.
  • a BS e.g. BS 400 or 105
  • FDRA table 800 the first 8 rows (i.e., indexed 0-7 in FIG. 8) used for non-repeating RMSI PDCCH.
  • the FDRA table 800 utilizes the 8 additional rows to contain information for indicating to a UE 300 the RMSI PDCCH repetition parameters according to some embodiments of the present disclosure.
  • the FDRA table 800 contains 6 columns, i.e. one additional column 812 beyond those that normally exist in other non-modified FDRA tables.
  • the columns include index 802, multiplexing patter 804, RB array 806, number of symbols 808, offset 810, and time pattern 812.
  • the discussion herein will touch on the aspects modified according to embodiments of the present disclosure to identify time and/or frequency repetition parameters for RMSI PDCCH.
  • the fields identified by rows indexed by values 0 to 7, and by columns 802, 804, 806, 808, and 810 may be referred to also as legacy fields.
  • New fields correspond to the 8 reserved rows indexed from 8 to 15 in the table 800 as well as the new column, time pattern 812, that together are used to signal repetition patterns in time and/or frequency domains.
  • the particular repetition pattern that a UE 300 should use may be identified via an index value used to index into the proper row of the table 800.
  • the MIB may use 4 bits to identify what index value between 0 and 15 the UE 300 should use in the table 800.
  • the rows indexed by values 8 and 9 illustrate time domain repetition (with no frequency domain repetition) with the entries in time pattern column 812.
  • the row indexed by the value 8 has a tuple with values ⁇ 4, 4 ⁇ in the time pattern 812 column.
  • This represents the periodicity of repetitions and the number of overall repetitions –so, in this example, a periodicity of 4 (e.g., 4 symbols) and a total of 4 repetitions. While in the example the repetition periodicity is specified with symbols being the unit of measurement, other measurements may be used instead.
  • the example indexed by value 9 provides the tuple value ⁇ 14, 4 ⁇ , indicating a periodicity of 14 symbols and a total of 4 repetitions.
  • the rows indexed by values 10 and 11 illustrate frequency domain repetition (with no time domain repetition) with the entries in the RB array 806 column (also referred to at times as a number of RBs per CORESET column) .
  • the row indexed by value 10 has a tuple in the RB Array 806 column with the exemplary values ⁇ 48, 3, 48, 3, 48, 3, 48 ⁇ . These values provide information that identifies the number of RBs per RMSI PDCCH CORESET, as well as the number of RBs per guard band between frequency domain repetitions.
  • the first two entries of the tuple, ⁇ 48, 3 ⁇ represents a first CORESET having 48 RBs in bandwidth, and 3 RBs’ worth of gap in bandwidth before the next RMSI PDCCH repetition. Because the tuple ⁇ 48, 3, 48, 3, 48, 3, 48 ⁇ includes the value ⁇ 48 ⁇ four times, this illustrates four repetitions in the frequency domain at a given offset within a slot. These values represent four repetitions of RMSI PDCCH, each 48 RBs in frequency bandwidth, and with a 3 RB guard band between each one.
  • the number of RBs per RMSI PDCCH may depend upon the bandwidth of each repetition, such as 20 MHz, 40 MHz, 80 MHz, etc., with more RBs per repetition for the higher bandwidths, and vice versa for the lower bandwidths, further depending upon the subcarrier spacing.
  • the row indexed by value 11 has a tuple in the RB array 806 column with the exemplary values ⁇ 192, 25, 192, 25, 192, 25, 192 ⁇ , which again provides for 4 repetitions in the frequency domain, each repetition of the RMSI PDCCH using 192 RBs, with 25 RBs of guard band between each repetition.
  • Other manners may be used to signal the repetitions and guard band in the frequency domain, such a single number to identify the number of repetitions and a single number to identify the guard band between each repetition.
  • the rows indexed by values 12-15 provide for different combinations of time and frequency domain repetitions.
  • the row indexed by value 12 has a tuple with values ⁇ 48, 3, 48 ⁇ in the RB array 806 column. This means that the RMSI PDCCH is repeated twice in the frequency domain at a given time, with each repetition occupying 48 RBs with a 3 RB gap between them.
  • the row indexed by value 12 has a tuple with values ⁇ 4, 2 ⁇ in the time pattern 812 column.
  • the RMSI PDCCH also has a periodicity of 4 symbols and a total of 2 repetitions in the time domain (with two repetitions in the frequency domain at each time domain repetition in this example, pursuant to the field in the RB array 806 column) .
  • the example in the row indexed by value 13 is similar, but with 192 RBs per frequency domain repetition and a periodicity of 14 symbols instead of 4.
  • the row indexed by value 15 is similar to the row indexed by value 14, but with a periodicity of 14 instead of 4 symbols.
  • the values in a given row of the table 800 are exemplary to illustrated aspects of the present disclosure.
  • the exemplary periodicity and number of time repetitions of RMSI PDCCH in FRDA table 800 may represent repetitions which are either inter-slot, intra-slot, or both.
  • a UE 300 With the information provided by the table 800 in an MIB, a UE 300 is able to locate what frequency and time domain resources within a slot or across slots to monitor/decode in order to obtain the RMSI PDCCH repetitions according to embodiments of the present disclosure. In this manner, the BS 400 may indicate explicitly the repetition information to the UE 300 to use.
  • the UE 300 may use a blind-decoding based repetition approach.
  • a BS 400 implementing this approach may thereby support multiple power modes with one MIB signaling.
  • a different table structure e.g., FDRA table
  • FIG. 9 provides an example of a FDRA table 900 according to some embodiments of the present disclosure.
  • a BS e.g. BS 400 or 105 may transmit an FDRA table 900 to a UE (e.g. 300 or 115) as part of an MIB transmission.
  • FDRA table 900 the first 8 rows (indexed by values 0-7 in the index 902 column) may be used for non-repeating RMSI PDCCH, but unlike FDRA table 800, the table 900 does not utilize the 8 additional rows (e.g., indexed by values 8-15 in the index 902 column) or provide tuples of information in the RB array 906. Instead, FRDA table 900 contains two additional columns, time pattern 912 column and frequency pattern 914 column (which may alternatively be in a different order to each other and/or the other columns, so long as the BS 400 and UE 300 know the order) .
  • the FDRA table 900 supports so-called legacy UEs (e.g., operating according to a different power mode such as SP mode) without requiring separate signaling for UEs updated to support embodiments of the present disclosure for RMSI PDCCH repetitions.
  • the legacy UEs may not even recognize the additional information in the newly-added columns time pattern 912 and frequency pattern 914. In this way, legacy UEs that are not able to interpret repetition information may still use the first five columns of FDRA table 900, and still function by ignoring any repetitions. Similar to the tuples in time pattern 812 column from FIG. 8, the tuples in the time pattern 912 column of FIG. 9 contain time repetition information for RMSI PDCCH.
  • the tuples indicate the periodicity, and the number of repetitions for a given RMSI PDCCH. Similar again to FIG. 8, some rows may identify repetition in the time domain only, while other rows may identify repetition in the frequency domain only, while yet others may identify repetition in the time and frequency domains.
  • the row indexed by the value 0 illustrates an example with repetition in both time and frequency domains.
  • the row indexed by 0 has a tuple with values ⁇ 4, 2 ⁇ in the time pattern 912 column, meaning that the RMSI PDCCH repetition has a periodicity of 4 symbols and a total of 2 repetitions in the time domain.
  • the row indexed by value 0 identifies a frequency repetition pattern with the tuple ⁇ 3, 2 ⁇ in the frequency pattern 914 column. This identifies the number of RBs per guard band, and the number of repetitions in the frequency domain.
  • the rows indexed by values 1, 4, and 5 likewise identify time and frequency domain repetitions.
  • the rows indexed by values 2 and 6 provide examples of rows that specify repetitions in the time domain only (e.g., with no entries in their frequency pattern fields or zero values)
  • the rows indexed by values 3 and 7 provide examples of rows that specify repetitions in the frequency domain only (e.g., with no entries in their time pattern fields or zero values) .
  • the exemplary periodicity and number of time repetitions of RMSI PDCCH in FRDA table 900 may represent repetitions which are either inter-slot, intra-slot, or both.
  • FIG. 10 is a signaling diagram illustrating a communication method 1000 according to some embodiments of the present disclosure.
  • the method 1000 may be implemented between a BS (e.g., BS 105 or BS 400) and a UE (e.g., the UE 115 or UE 300) .
  • the first device 1002 may be an example of the UE 300 and the second device 1004 may be an example of the BS 400.
  • the method 1000 may employ similar mechanisms as in the structures 200 and/or 500 described above with respect to FIGS. 2 and 5 respectively, and/or method 1400 described herein with respect to FIG. 15.
  • aspects of FIG. 10 illustrate a scenario where the repetition information is explicitly indicated via MIB.
  • the second device 1004 transmits a resource assignment table to the first device 1002.
  • the resource assignment may include configuration information for defining repetitions of RMSI PDCCH in time and/or frequency.
  • method 1000 illustrates RMSI PDCCH repetition in time only.
  • the resource assignment table may be a FDRA table similar to tables 800 or 900 in FIGS. 8 and 9 respectively, and thus the action 1006 may involve transmitting the resource assignment table via MIB to the first device 1002.
  • the first device 1002 (e.g., UE 300) , after receiving the resource assignment table, extracts information from the resource assignment table at block 1008. For example, extracting periodicity of time repetitions, number of time repetitions, bandwidth of each repetition, guard band size of each frequency repetition, and/or number of frequency repetitions.
  • the format of this information may be in one of the forms described with respect to FIGS. 8 or 9, or some other format. In the specific example of FIG. 10, this involves extracting the periodicity and number of repetitions (as the example relates to time domain repetition) .
  • the second device 1004 transmits the first RMSI PDCCH to the first device 1002.
  • the first and second device respectively wait for the next transmission.
  • the devices may still be performing other actions during this time, but the periodicity of the repetitions identifies the amount of time between RMSI PDCCH 1010 and RMSI PDCCH 1016.
  • the time between repetitions is contained in the resource assignment table which was transmitted at action 1006 (e.g., the periodicity parameter) .
  • the second device 1004 transmits a RMSI PDCCH to the first device 1002.
  • the first device 1002 and second device 1004 each respectively wait for another periodicity time.
  • the second device 1004 transmits a RMSI PDCCH to the first device 1002.
  • This method illustrates a first RMSI PDCCH transmission with two repetitions. More or fewer repetitions may be indicated by the second device 1004.
  • FIG. 11 is a signaling diagram illustrating a communication method 1100 according to some embodiments of the present disclosure.
  • RMSI PDCCH repetition in method 1100 is only over the frequency domain.
  • the first device 1102 may be an example of the UE 300 and the second device 1104 may be an example of the BS 400.
  • the method 1100 may employ similar mechanisms as in the structure 200 and 600 described above with respect to FIGS. 2 and 6 respectively, and/or method 1400 described herein with respect to FIG. 14.
  • the second device 1104 transmits a resource assignment table to the first device 1102.
  • the resource assignment may include configuration information for defining repetitions of RMSI PDCCH in time and/or frequency.
  • method 1100 illustrates RMSI PDCCH repetition in frequency only.
  • the resource assignment table may be a FDRA table similar to tables 800 or 900 in FIGS. 8 and 9 respectively, and thus the action 1106 may involve transmitting the resource assignment table via MIB to the first device 1102.
  • the first device 1102 (e.g., UE 300) , after receiving the resource assignment table, extracts information from the resource assignment table at block 1108. In the specific example of FIG. 11, this includes extracting the bandwidth of each repetition, guard band size of each frequency repetition, and/or number of frequency repetitions.
  • RMSI PDCCH is transmitted at different frequencies.
  • the frequencies on which they are transmitted are those as defined in the resource assignment table, e.g. in terms of number of RBs per RMSI PDCCH repetition and number of RBs per guard band between repetitions. These may be transmitted substantially simultaneously to each other, such as all on the same symbol in time.
  • the first device 1102 receives the RMSI PDCCH repetitions, which by being repeated in the frequency domain may result in additional transmit power from the second device 1104.
  • FIGs. 10 and 11 may be combined with respect to scenarios where RMSI PDCCH is repeated in both the time and frequency domains, such as illustrated in FIG. 7 above and identified by some of the rows in FIG. 8’s table 800 (such as indexed by values 12-15) .
  • FIG. 12 is a signaling diagram illustrating a communication method 1200 according to some embodiments of the present disclosure based on blind decoding hypotheses aspects.
  • the first device 1202 may be an example of the UE 300 and the second device 1204 may be an example of the BS 400.
  • the second device 1204 transmits a resource assignment table to the first device 1202.
  • the resource assignment may include configuration information for defining repetitions of RMSI PDCCH in time and/or frequency. This may be in an MIB from the second device 1204.
  • Method 1200 may involve RMSI PDCCH repetition in time only, frequency domain repetition only, or a combination of time and frequency domain repetition.
  • the resource assignment table may be a FDRA table similar to table 900 in FIG. 9, for example.
  • the first device 1202 (e.g., UE 300) , after receiving the repetition pattern in the form of a resource assignment table, extracts information from the repetition pattern at block 1208. For example, extracting periodicity of time repetitions, number of time repetitions, bandwidth of each repetition, guard band size of each frequency repetition, and/or number of frequency repetitions.
  • the second device 1204 transmits the first RMSI PDCCH to the first device 1202.
  • the first device 1202 assumes that no RMSI PDCCH repetition occurs, and instead just looks for the first RMSI PDCCH transmission to occur. This may be based on the legacy fields of the resource assignment table, such as may be used by a legacy UE.
  • the first device 1202 may attempt to blind decode the RMSI PDCCH received at action 1210. If the first device 1202 is successful in blind decoding the RMSI PDCCH received at action 1210, then no further blind decoding is necessary and the method 1200 may end. If, instead, the blind decoding is not successful, then the method 1200 proceeds to block 1214 and a second hypothesis that assumes the repetition identified by the resource assignment table (e.g., time, frequency, or a combination of time/frequency domains) .
  • the resource assignment table e.g., time, frequency, or a combination of time/frequency domains
  • the first device 1202 buffers the information received at the RMSI PDCCH resources at action 1210 and waits for the next scheduled RMSI PDCCH as identified by the resource assignment table (if time domain repetitions occur) .
  • the actions at blocks 1214-1228 with respect to receiving and storing RMSI PDCCH repetitions may all occur around the same time with the frequency domain repetitions. Further, there may be a combination of time and frequency domain repetitions.
  • the first device 1202 waits at block 1214 and the second device 1204 likewise waits at block 1216 for the specified period of time (e.g., number of symbols specified by the periodicity parameter) .
  • the specified period of time e.g., number of symbols specified by the periodicity parameter
  • the second device 1204 repeats the RMSI PDCCH transmission to the first device 1202.
  • the first device 1202 may receive the RMSI PDCCH transmitted at action 1218, and at action 1222 buffers the RMSI PDCCH and waits for the next RMSI PDCCH (in situations where yet further repetitions in the time domain were identified from the resource assignment table) . Likewise, at action 1224 the second device 1204 waits for the next scheduled transmission occasion for the RMSI PDCCH repetition.
  • the second device 1204 repeats the RMSI PDCCH transmission to the first device 1202.
  • the periodicity e.g., in number of symbols
  • the first device 1202 may soft combine the three RMSI PDCCHs (e.g., the received information at the identified resource blocks) .
  • the first device 1202 may soft combine across all of the monitored resource blocks across time and/or frequency according to the signaled repetition pattern in the resource assignment table. Once the monitored resource blocks are soft combined, the first device 1202 may attempt to blind decode to recover the information contained in the RMSI PDCCH.
  • the method 1200 may end after block 1228. Alternatively, if blind decoding was not successful at block 1228, the method 1200 may proceed to block 1230.
  • the first device 1202 may puncture the first instance of RMSI PDCCH still stored for blind decoding, and then do blind decoding on the remaining soft combined RMSI PDCCH repetitions. For example, a first puncture may drop the RMSI PDCCH repetition received from action 1210 (the first transmission, for example) . This may continue, with further repetitions being punctured, until blind decoding is successful or the last RMSI PDCCH repetition remains for decoding.
  • the second blind decoding hypothesis may need to extend across slots (e.g., where a time repetition pattern signaled in the MIB indicates that some of the replicated RMSI PDCCHs will occur in different slots from each other) .
  • each of the RMSI PDCCH repetitions transmitted at actions 1210, 1218, and 1226 may occur in different slots from one another (other variations may occur, such as multiple repetitions in a slot, also extending across more than one slot) .
  • the first hypothesis (as explained with respect to block 1212 above) may be performed at or after the start of each slot where the RMSI PDCCH is scheduled to occur.
  • the first device 1202 may soft combine the duplicates of the RMSI PDCCHs monitored at each of the occasions identified in the table (and received at blocks 1212, 1220, and 1228 in the example of FIG. 12) and then attempt blind decoding once all collected (e.g., buffered or otherwise stored) . If blind decoding fails, the first device 1202 may puncture the first slot and soft combine the remaining RMSI PDCCHs in the remaining slot (s) and attempt blind decoding again, as discussed with respect to block 1230 above already. This may be repeated until the decoding is successful or the last RMSI PDCCH is left.
  • FIG. 13 is a flow diagram of a communication method 1300 according to some embodiments of the present disclosure. Steps of the method 1300 can be executed by a computing device (e.g., a processor, processing circuit, and/or other suitable component) of a wireless communication device or other suitable means for performing the steps.
  • a wireless communication device such as the UE 115 or UE 300, and may utilize one or more components, such as the processor 302, the memory 304, the RMSI PDCCH monitor module 308, the transceiver 310, the modem 312, and the one or more antennas 316, to execute the steps of method 1300.
  • the method 1300 may employ similar mechanisms as in the structure described above with respect to FIGS. 5-12.
  • the method 1300 includes a number of enumerated steps, but embodiments of the method 1300 may include additional steps before, after, and in between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.
  • a UE 300 receives an indication of a repetition pattern for a remaining minimum system information (RMSI) physical downlink control channel (PDCCH) transmission from a BS 400.
  • This repetition pattern indication may be in the form of an FDRA table such as those discussed with respect to FIGS. 8 and 9.
  • the table illustrated in FIG. 8 may be used to explicitly signal to the UE 300 where repetitions will occur.
  • the UE 300 extracts repetition pattern information from the indication, which may specify time domain repetitions only, frequency domain repetitions only, or a combination of time and frequency domain repetitions. For example, the UE 300 may extract periodicity of time repetitions, number of time repetitions, bandwidth of each repetition, guard band size of each frequency repetition, and/or number of frequency repetitions.
  • the UE 300 receives the RMSI PDCCH from the BS.
  • the UE 300 receives a repetition of the RMSI PDCCH from the BS according to the repetition pattern defined in the indication. In some examples, this may be occurring at the same or similar time as block 1330 where the repetition pattern is simply in the frequency domain. In other examples, this may be over time according to the repetition pattern specified in the time domain. In yet other examples, there may be multiple repetitions across frequency at a given time as well as multiple repetitions over time (with multiple repetitions across frequency at each instance) .
  • RMSI PDCCH coverage for RMSI PDCCH is enhanced and/or transmit power increased (such as where repeated in frequency) , and the UE 300 attempts to decode the RMSI PDCCH combined from the repeated transmissions.
  • FIG. 14 is a flow diagram of a communication method 1400 according to some embodiments of the present disclosure. Steps of the method 1400 can be executed by a computing device (e.g., a processor, processing circuit, and/or other suitable component) of a wireless communication device or other suitable means for performing the steps.
  • a wireless communication device such as the UE 115 or UE 300, and may utilize one or more components, such as the processor 302, the memory 304, the RMSI PDCCH monitor module 308, the transceiver 310, the modem 312, and the one or more antennas 316, to execute the steps of method 1400.
  • the method 1400 may employ similar mechanisms as in the structure described above with respect to FIGS. 5-7 and methods of FIGS. 10-13.
  • the method 1400 includes a number of enumerated steps, but embodiments of the method 1400 may include additional steps before, after, and in between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.
  • a UE 300 receives an indication of a repetition pattern for a RMSI PDCCH transmission from a BS 400.
  • an FDRA table such as FDRA table 800 or 900 contained in an MIB.
  • the table illustrated in FIG. 9 may be used in combination with blind decoding hypotheses as discussed below.
  • the UE 300 assumes that no repetition pattern exists according to a first hypothesis. This may involve the UE 300 extracting information regarding where to locate a non-repeating RMSI PDCCH from legacy fields of the resource assignment table (e.g., table 900) .
  • the UE 300 receives the RMSI PDCCH from the BS 400.
  • the UE 300 performs a first blind decoding on the RMSI PDCCH based on the assumption of the first hypothesis, e.g. that no RMSI PDCCH repetitions are occurring.
  • the UE 300 determines whether the blind decoding was successful. If the blind decoding was successful, then the method 1400 proceeds to block 1460. At block 1460, the UE 300 stops blind decoding. This may allow the UE 300 to run more efficiently when the blind decoding is not necessary, as well as enables the BS 400 to use one MIB that may be applicable to different UEs in different power modes, such as in SP and LPI modes.
  • the method 1400 proceeds to block 1470.
  • the UE 300 assumes that the repetition pattern exists according to a second hypothesis, as specified according to new fields of the table 900 as received at block 1410.
  • the UE 300 performs additional blind decoding on additional RMSI PDCCH candidates corresponding to the repetition RMSI PDCCH transmissions. This may occur in time and/or frequency domains, according to the various examples given with respect to the other figures above.
  • the UE 300 may soft combine the RMSI PDCCHs across all of the monitored resource blocks across time and/or frequency according to the signaled repetition pattern in the resource assignment table. Once the monitored resource blocks are soft combined, the UE 300 may attempt to blind decode to recover the information contained in the RMSI PDCCH.
  • the method 1400 proceeds to block 1460 and ends as noted above. If, instead, blind decoding was not successful, then the method 1400 may proceed to block 1495.
  • the UE 300 may puncture the first instance of RMSI PDCCH still stored for blind decoding.
  • the method 1400 may then return to block 1480 and do blind decoding on the remaining soft combined RMSI PDCCH repetitions. This may continue (e.g., to decision block 1490, ending at block 1460, or puncturing at block 1495) , with further repetitions being punctured, until blind decoding is successful or the last RMSI PDCCH repetition remains for decoding.
  • the second blind decoding hypothesis may need to extend across slots (e.g., where a time repetition pattern signaled in the MIB indicates that some of the replicated RMSI PDCCHs will occur in different slots from each other) .
  • each of the RMSI PDCCH repetitions may occur in different slots from one another (other variations may occur, such as multiple repetitions in a slot, also extending across more than one slot) .
  • the first hypothesis may be performed at or after the start of each slot where the RMSI PDCCH is scheduled to occur.
  • the UE 300 may soft combine the duplicates of the RMSI PDCCHs monitored at each of the occasions identified in the table and then attempt blind decoding once all collected (e.g., buffered or otherwise stored) . If blind decoding fails, the UE 300 may puncture the first slot and soft combine the remaining RMSI PDCCHs in the remaining slot (s) and attempt blind decoding again. This may be repeated until the decoding is successful or the last RMSI PDCCH is left.
  • FIG. 15 is a flow diagram of a communication method 1500 according to some embodiments of the present disclosure. Steps of the method 1500 can be executed by a computing device (e.g., a processor, processing circuit, and/or other suitable component) of a wireless communication device or other suitable means for performing the steps.
  • a wireless communication device such as the BS 105 or 400, and may utilize one or more components, such as the processor 402, the memory 404, the RMSI PDCCH module 408, the transceiver 410, the modem 412, and the one or more antennas 416, to execute the steps of method 1500.
  • the method 1500 may employ similar mechanisms as in the structure described above with respect to FIGS. 5-9.
  • the method 1500 includes a number of enumerated steps, but embodiments of the method 1500 may include additional steps before, after, and in between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.
  • a BS 400 prepares an indication of a repetition pattern for a remaining minimum system information (RMSI) physical downlink control channel (PDCCH) transmission to be transmitted to a UE 300.
  • the BS 400 may prepare this repetition pattern indication in the form of an FDRA table such as those discussed with respect to FIGS. 8 and 9.
  • the BS 400 transmits the indication to the UE 300, which may specify time domain repetitions only, frequency domain repetitions only, or a combination of time and frequency domain repetitions.
  • the UE 300 may extract this information as discussed with respect to the figures above.
  • the BS 400 transmits the RMSI PDCCH to the UE 300.
  • the UE 300 is implementing the two hypothesis, this may be where the UE 300 implements the first hypothesis and stops blind decoding if successful.
  • the BS 400 transmits a repetition of the RMSI PDCCH according to the repetition pattern defined in the indication. In some examples, this may be occurring at the same or similar time as block 1530 where the repetition pattern is simply in the frequency domain. In other examples, this may be over time according to the repetition pattern specified in the time domain. In yet other examples, there may be multiple repetitions across frequency at a given time as well as multiple repetitions over time (with multiple repetitions across frequency at each instance) . Where this was an explicit indicate to the UE 300, the UE 300 may use this information to access the RMSI PDCCH with greater coverage and/or power. Where the UE 300 is implementing the hypothesis, the UE 300 may apply the second hypothesis and soft combine the repetitions and attempt blind decoding.
  • Information and signals may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • “or” as used in a list of items indicates an inclusive list such that, for example, a list of [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Systèmes et procédés de communications sans fil concernant la surveillance et le décodage de PDCCH de RMSI. Un premier dispositif de communication sans fil reçoit, d'un second dispositif de communication sans fil, des informations de motif de répétition dans une table d'attribution de ressources. Les informations dans la table identifient les fréquences et les temps relatifs lorsque les signaux PDCCH de RMSI seront répétés par le second dispositif de communication sans fil. Le premier dispositif de communication sans fil surveille les répétitions aux moments et fréquences identifiés. Dans certains exemples, chaque répétition de PDCCH de RMSI est surveillée. Dans d'autres exemples, un décodage aveugle est effectué uniquement sur le premier PDCCH de RMSI. Dans d'autres exemples encore, un décodage aveugle est effectué sur un nombre variable de répétitions déterminées par le succès ou l'échec du décodage aveugle.
PCT/CN2020/102708 2020-07-17 2020-07-17 Nr-u pour une répétition de pdcch de bande rmsi de 6 ghz pour mode lpi Ceased WO2022011685A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/102708 WO2022011685A1 (fr) 2020-07-17 2020-07-17 Nr-u pour une répétition de pdcch de bande rmsi de 6 ghz pour mode lpi

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/102708 WO2022011685A1 (fr) 2020-07-17 2020-07-17 Nr-u pour une répétition de pdcch de bande rmsi de 6 ghz pour mode lpi

Publications (1)

Publication Number Publication Date
WO2022011685A1 true WO2022011685A1 (fr) 2022-01-20

Family

ID=79554433

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/102708 Ceased WO2022011685A1 (fr) 2020-07-17 2020-07-17 Nr-u pour une répétition de pdcch de bande rmsi de 6 ghz pour mode lpi

Country Status (1)

Country Link
WO (1) WO2022011685A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024211031A1 (fr) * 2023-04-05 2024-10-10 Qualcomm Incorporated Signalisation d'indication de motif de préemption de liaison descendante
US12413983B1 (en) 2022-08-18 2025-09-09 Cisco Technology, Inc. Adaptive channel assignment for 6GHZ radios
WO2026015357A1 (fr) * 2024-07-10 2026-01-15 Qualcomm Incorporated Distinction de signal de référence de démodulation pour prendre en charge une combinaison de canaux descendants
WO2026035410A1 (fr) * 2024-08-07 2026-02-12 Qualcomm Incorporated Combinaison d'informations de système minimales restantes adaptatives

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019033953A1 (fr) * 2017-08-18 2019-02-21 维沃移动通信有限公司 Procédé d'envoi et de réception d'informations, terminal et station de base
WO2019098769A1 (fr) * 2017-11-17 2019-05-23 엘지전자 주식회사 Procédé d'émission et de réception de signal de référence et dispositif associé
WO2019134636A1 (fr) * 2018-01-02 2019-07-11 Telefonaktiebolaget Lm Ericsson (Publ) Procédé, dispositif de réseau et dispositif terminal pour information de système minimum restante
US20190223163A1 (en) * 2017-11-17 2019-07-18 Lg Electronics Inc. Method of transmitting and receiving downlink channel and apparatus therefor

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019033953A1 (fr) * 2017-08-18 2019-02-21 维沃移动通信有限公司 Procédé d'envoi et de réception d'informations, terminal et station de base
WO2019098769A1 (fr) * 2017-11-17 2019-05-23 엘지전자 주식회사 Procédé d'émission et de réception de signal de référence et dispositif associé
US20190223163A1 (en) * 2017-11-17 2019-07-18 Lg Electronics Inc. Method of transmitting and receiving downlink channel and apparatus therefor
WO2019134636A1 (fr) * 2018-01-02 2019-07-11 Telefonaktiebolaget Lm Ericsson (Publ) Procédé, dispositif de réseau et dispositif terminal pour information de système minimum restante

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Remaining system information delivery consideration", 3GPP DRAFT; R1-1804776 REMAINING SYSTEM INFORMATION DELIVERY CONSIDERATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 15 April 2018 (2018-04-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051427043 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12413983B1 (en) 2022-08-18 2025-09-09 Cisco Technology, Inc. Adaptive channel assignment for 6GHZ radios
WO2024211031A1 (fr) * 2023-04-05 2024-10-10 Qualcomm Incorporated Signalisation d'indication de motif de préemption de liaison descendante
WO2026015357A1 (fr) * 2024-07-10 2026-01-15 Qualcomm Incorporated Distinction de signal de référence de démodulation pour prendre en charge une combinaison de canaux descendants
WO2026035410A1 (fr) * 2024-08-07 2026-02-12 Qualcomm Incorporated Combinaison d'informations de système minimales restantes adaptatives

Similar Documents

Publication Publication Date Title
US12375249B2 (en) Physical downlink control channel (PDCCH) monitoring with overlapping resources
WO2021151237A1 (fr) Surveillance de pdcch pour une planification multi-cellules à dci uniques
US11895634B2 (en) Control resource set (CORESET) configuration for narrowband new radio (NR)
US11611975B2 (en) Uplink (UL) transmission with flexible starting positions for new radio-unlicensed (NR-U)
WO2020197743A1 (fr) Commutation dynamique du mode de surveillance d'un canal physique de commande de liaison descendante (pdcch), configuration et commande
JP7787109B2 (ja) Ｐｄｃｃｈ監視アグリゲーションのための技法
WO2022072248A1 (fr) Configurations de décodage de canal de commande pour l'ordonnancement inter-porteuse perfectionné
US20210143954A1 (en) Qcl determination for a-csi-rs in full duplex systems
EP4111811B1 (fr) Transmission de canal d'accès aléatoire physique (prach) dans une nouvelle radio (nr)
US12225460B2 (en) Update of physical downlink control channel (PDCCH) parameters
US11910385B2 (en) Control channel monitoring configurations for cross-carrier scheduling
WO2021212300A1 (fr) Partage de signaux initiaux entre des dispositifs d'équipement utilisateur ayant différentes largeurs de bande dans une lumière new radio (nr)
WO2021138796A1 (fr) Limites de taille d'informations de contrôle de liaison descendante et de mise en mémoire tampon pour des dci combinées
WO2021109060A1 (fr) Conception d'ensemble de ressources de commande (coreset) pour des sous-bandes dans un système à porteuses multiples
US20230007632A1 (en) Configuring a search space set for downlink control information
WO2021212257A1 (fr) Validation de communication de liaison montante pour un mode d'équipement basé sur une trame dans un système new radio sans licence (nr-u)
EP4516039A1 (fr) Chevauchement de groupes de ressources dans une communication de liaison latérale

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20945096

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20945096

Country of ref document: EP

Kind code of ref document: A1