Configuration of control resource set and common search space for initial access of low-end user equipment

Abstract

Aspects of the present disclosure relate to wireless communication. In some aspects, a user equipment (UE) may receive a master information block that identifies a first control resource set (CORESET) for a first type of UE and a first common search space (CSS) associated with the first CORESET. The first CORESET and the first CSS may identify one or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids that include one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS. The UE may monitor physical downlink control channel candidates included in the first CORESET and the first CSS.

Description

Technical Field

[0001] Aspects of the present disclosure generally relate to wireless communications, and relate to techniques and apparatuses for configuring control resource sets and common search spaces for initial access by low-end user equipment. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ a multiple access technology capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE) systems. LTE / Advanced LTE is an enhanced set of the Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless communication network may include multiple base stations (BSs) capable of supporting communication with multiple user equipments (UEs). A user equipment (UE) may communicate with a base station (BS) via a downlink and an uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0004] The above multi-access technologies have been adopted in various telecommunication standards to provide common protocols that enable different user equipments to communicate at the municipal, national, regional, or even global level. New Radio (NR), which may also be referred to as 5G, is an enhanced set of LTE mobile standards promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access in the following ways: improving spectral efficiency, reducing costs, enhancing services, leveraging new spectrums, better integrating with other open standards (using Orthogonal Frequency Division Multiplexing with Cyclic Prefix (CP-OFDM) on the downlink (DL), and using CP-OFDM and / or SC-FDM (e.g., also referred to as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink (UL)), and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technology, and carrier aggregation. However, with the increasing demand for mobile broadband access, further improvements to LTE and NR technologies are needed. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies. Summary of the Invention

[0005] In some aspects, a wireless communication method performed by a User Equipment (UE) may include: receiving a Master Information Block that identifies a first Control Resource Set (CORESET) for a first type of UE and a first Common Search Space (CSS) associated with the first CORESET, wherein the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids that include one or more corresponding time-domain resources earlier than the time-domain resources of the second CORESET and the second CSS; and monitoring Physical Downlink Control Channel (PDCCH) candidates included in the first CORESET and the first CSS.

[0006] In some aspects, a wireless communication method performed by a base station may include: configuring a first CORESET for a first type of UE and a first CSS associated with the first CORESET, wherein the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids that include one or more corresponding time-domain resources earlier than the time-domain resources of the second CORESET and the second CSS; and transmitting a Master Information Block that identifies the first CORESET and the first CSS.

[0007] In some aspects, a UE for wireless communication may include: a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive a master information block that identifies a first CORESET for a first type of UE and a first CSS associated with the first CORESET, wherein the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency, and one or more non-overlapping resource grids that include one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and monitor physical downlink control channel (PDCCH) candidates included in the first CORESET and the first CSS.

[0008] In some aspects, a base station for wireless communication may include: a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: configure a first CORESET for a first type of UE and a first CSS associated with the first CORESET, wherein the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency, and one or more non-overlapping resource grids that include one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and transmit a master information block that identifies the first CORESET and the first CSS.

[0009] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to: receive a master information block that identifies a first CORESET for a first type of UE and a first CSS associated with the first CORESET, wherein the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency, and one or more non-overlapping resource grids that include one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and monitor PDCCH candidates included in the first CORESET and the first CSS.

[0010] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to: configure a first CORESET for a first type of UE and a first CSS associated with the first CORESET, wherein the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap, in time and frequency, with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids that include one or more corresponding time-domain resources earlier than the time-domain resources of the second CORESET and the second CSS; and transmit a master information block that identifies the first CORESET and the first CSS.

[0011] In some aspects, an apparatus for wireless communication may include: means for receiving a master information block that identifies a first CORESET for a first type of UE and a first CSS associated with the first CORESET, wherein the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap, in time and frequency, with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids that include one or more corresponding time-domain resources earlier than the time-domain resources of the second CORESET and the second CSS; and means for monitoring PDCCH candidates included in the first CORESET and the first CSS.

[0012] In some aspects, an apparatus for wireless communication may include: means for configuring a first CORESET for a first type of UE and a first CSS associated with the first CORESET, wherein the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap, in time and frequency, with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids that include one or more corresponding time-domain resources earlier than the time-domain resources of the second CORESET and the second CSS; and means for transmitting a master information block that identifies the first CORESET and the first CSS.

[0013] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems, as fully described and illustrated herein with reference to the accompanying drawings and the specification.

[0014] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their organization and method of operation, and related advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the drawings is provided for purposes of illustration and description and is not to be construed as a definition of the limits of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] To enable a more specific description of the features outlined briefly above in accordance with the various aspects of the present disclosure, a more detailed description may be obtained by reference to the various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings only illustrate specific exemplary aspects of the present disclosure and should not be considered as limiting its scope, as the description may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0016] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0017] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a UE in a wireless communication network in accordance with various aspects of the present disclosure.

[0018] Figure 3A 、 Figure 3B 、 Figure 3C and Figure 3D are diagrams illustrating examples of 5G / NR transmission time intervals in accordance with various aspects of the present disclosure.

[0019] Figure 4 is a diagram illustrating an example of a synchronization signal block (SSB) in accordance with various aspects of the present disclosure.

[0020] Figure 5A is a diagram illustrating an example of an SSB transmission with a 15 kilohertz (kHz) subcarrier spacing (SCS) in accordance with various aspects of the present disclosure.

[0021] Figure 5B is a diagram illustrating another example of an SSB transmission with a 30 kHz SCS in accordance with various aspects of the present disclosure.

[0022] Figure 6A is a diagram illustrating an example of an SSB transmission with a 120 kHz SCS in accordance with various aspects of the present disclosure.

[0023] Figure 6B FIG. is another example showing SSB transmission with 240 kHz SCS according to various aspects of the present disclosure.

[0024] Figure 7 FIG. is a diagram showing an example control resource set with control channel elements according to various aspects of the present disclosure.

[0025] Figures 8 - 11 FIG. is a diagram showing an example of the configuration of a control resource set and a common search space for initial access by a low-end user equipment according to various aspects of the present disclosure.

[0026] Figure 12 FIG. is a diagram showing an example process, such as performed by a user equipment, according to various aspects of the present disclosure.

[0027] Figure 13 FIG. is a diagram showing an example process, such as performed by a base station, according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0028] Aspects of the present disclosure will now be described more fully with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art should understand that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of any other aspect of the present disclosure or in combination with any other aspect of the present disclosure. For example, any number of the aspects set forth herein may be used to implement a device or practice a method. In addition, the scope of the present disclosure is intended to cover such a device or method that practices using other structures, functions, or a combination of structures and functions in addition to or apart from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0029] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0030] Note that while aspects of the present disclosure may be described herein using terms typically associated with 3G and / or 4G wireless technologies, aspects of the present disclosure may be applicable to communication systems based on other generations, such as 5G and later versions, including NR technology.

[0031] Figure 1 FIG. is a diagram of a wireless network 100 in which aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include a plurality of BSs 110 (shown as BSs 110a, 110b, 110c, and 110d) and other network entities. A BS is an entity that communicates with user equipment (UE) and may also be referred to as a base station, NR BS, Node B, gNB, 5G node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the coverage area of a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0032] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UEs having a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs having a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 the example shown, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "node B", "5GNB", and "cell" may be used interchangeably herein.

[0033] In some aspects, the cell may not necessarily be stationary, and the geographical area of the cell can move according to the position of the mobile BS. In some aspects, the BSs can be interconnected with each other and / or interconnected to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transmission network.

[0034] The wireless network 100 can also include relay stations. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or a UE) and sending data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. In Figure 1 the example shown, the relay station 110d can communicate with the macro BS 110a and the UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay station can also be referred to as a relay BS, a relay base station, a relay, etc.

[0035] The wireless network 100 can be a heterogeneous network, including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs can have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro BS can have a high transmit power level (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0036] The network controller 130 can be coupled to a set of BSs and can provide coordination and control for these BSs. The network controller 130 can communicate with the BSs via the backhaul. The BSs can also communicate directly or indirectly with each other, for example, via wireless or wired backhaul.

[0037] UE 120 (e.g., 120a, 120b, 120c, 120d, 120e) can be dispersed throughout the wireless network 100, and each UE can be fixed or mobile. A UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biosensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device or satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0038] Some UEs can be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity for a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as narrowband IoT (NB-IoT) devices. Some UEs can be considered customer premises equipment (CPE). UE 120 can be included within a housing that houses components of UE 120, such as a processor component, a memory component, etc.

[0039] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, an air interface, etc. A frequency can also be referred to as a carrier, a channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks of different RATs. In some cases, an NR or 5G RAT network can be deployed.

[0040] In some aspects, two or more UEs 120 (e.g., shown as UEs 120a and 120e) may communicate directly using one or more sidelink channels (e.g., without using the base station 110 as a medium for communicating with each other). For example, the UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, and the like. In such a case, the UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0041] As described above, provided Figure 1 as an example. Other examples may be different from those Figure 1 described with respect to

[0042] Figure 2 FIG. 200 is a block diagram of a design of a base station 110 and a UE 120, where the base station 110 and the UE 120 may be, respectively, Figure 1 one of the base stations and one of the UEs in

[0043] At the base station 110, a transmit processor 220 may receive data for one or more UEs from a data source 212, select one or more modulation and coding schemes (MCSs) for each UE at least in part based on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE at least in part based on the selected MCS(s) for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRSs)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable) and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process the corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively. According to various aspects described in more detail below, position coding may be utilized to generate synchronization signals to convey additional information.

[0044] At the UE 120, antennas 252a through 252r may receive downlink signals from the base station 110 and / or other base stations and may provide the received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator 254 may further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain the received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. A channel processor may determine a reference signal received power (RSRP), a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), a channel quality indicator (CQI), etc. In some aspects, one or more components of the UE 120 may be included in a housing.

[0045] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0046] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component(s) of the base station 110 may perform one or more techniques associated with configuring a control resource set (CORESET) and a common search space (CSS) for initial access by low-end user equipment, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component(s) may perform or direct e.g. Figure 12 The process 1200 Figure 13 The operations of process 1300 and / or other processes described herein may be performed by memory 242 and 282. The memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120, the one or more instructions may perform or direct, for example, Figure 12 The process 1200 Figure 13 The scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0047] In some aspects, UE 120 may include a device module for receiving a master information block that identifies a first CORESET for a first type of UE and a first CSS associated with the first CORESET, where the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids that include one or more corresponding time-domain resources earlier than the time-domain resources of the second CORESET and the second CSS; a device module for monitoring physical downlink control channel (PDCCH) candidates included in the first CORESET and the first CSS; and so on. In some aspects, these device modules may include one or more components of the UE 120 described in conjunction with Figure 2 such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.

[0048] In some aspects, base station 110 may include: a device module for configuring a first CORESET for a first type of UE and a first CSS associated with the first CORESET, where the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids that include one or more corresponding time-domain resources earlier than the time-domain resources of the second CORESET and the second CSS; a device module for transmitting a master information block that identifies the first CORESET and the first CSS; and so on. In some aspects, these device modules may include one or more components of the base station 110 described in conjunction with Figure 2 such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, etc.

[0049] As described above, provide Figure 2 as an example. Other examples may be different from those described with respect to Figure 2

[0050] Figures 3A - 3D ​FIG. is an example showing a 5G / NR transmission time interval (TTI) (e.g., frame, subframe, slot, mini-slot, etc.) according to various aspects of the present disclosure. Figure 3A FIG. is an example 300 showing the first slot within the 5G / NR frame structure, Figure 3B FIG. is an example 330 showing the downlink (DL) channels within a 5G / NR slot, Figure 3C FIG. is an example 350 showing the second slot within the 5G / NR frame structure, and Figure 3D FIG. is an example 380 showing the uplink (UL) channels within a 5G / NR slot.

[0051] In some aspects, the 5G / NR TTI structure can be a frequency division duplexing (FDD) structure, where, for a set of subcarriers (e.g., carrier system bandwidth), the slots within the set of subcarriers are dedicated to either DL or UL. In some aspects, the 5G / NR TTI structure can be a time division duplexing (TDD) structure, where, for a set of subcarriers (e.g., carrier system bandwidth), the slots within the set of subcarriers are dedicated to both DL and UL.

[0052] In Figure 3A , the TTI structure is TDD, where slot 4 is configured as the DL center slot (shown as D, where D is DL, U is UL, and X is flexibly used as either DL or UL). In Figure 3C , the TTI structure is TDD, where slot 3 is configured as the UL center slot. Although slots 3 and 4 are shown with specific slot formats, any particular slot can be configured with any one of the various available slot formats 0 - 61. The UE dynamically configures the slot format via downlink control information (DCI), or semi-statically configures the slot format via radio resource control (RRC) signaling using a slot format indicator (SFI). Although the TDD structure is shown, some aspects described herein also apply to the FDD TTI structure.

[0053] As shown, a frame (e.g., having 10 ms) can be divided into 10 equally sized subframes (e.g., having 1 ms). Each subframe can include one or more slots. A subframe can also include mini-slots, which can include 7, 4, or 2 symbols. Depending on the slot configuration, each slot can include 7 or 14 symbols. The number of slots within a subframe is based on the slot configuration and numerology. For slot configuration 0, different numerologies μ0 to 5 respectively allow 1, 2, 4, 8, 16, and 32 slots per subframe. For slot configuration 1, different numerologies 0 to 2 respectively allow 2, 4, and 8 slots per subframe. Accordingly, for slot configuration 0 and numerology μ, each slot has 14 symbols, and each subframe has 2 μtime slots. The subcarrier spacing and symbol duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15 kHz, where μ ranges from parameter set 0 to 5. Thus, parameter set μ = 0 has a subcarrier spacing of 15 kHz, and parameter set μ = 5 has a subcarrier spacing of 480 kHz. The symbol duration is inversely related to the subcarrier spacing. Figures 3A - 3D An example of slot configuration 0 with 14 symbols per time slot and parameter set μ = 0 with 1 time slot per subframe is provided. The subcarrier spacing is 15 kHz, and the symbol duration is approximately 66.7 microseconds.

[0054] A resource grid can be used to represent the frame structure. Each time slot includes resource blocks (RBs) (also known as physical RBs (PRBs)), which consist of 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0055] As Figure 3A shown, some REs carry reference (pilot) signals (RSs) for UE 120. The RS can include demodulation RS (DMRS) (indicated as R x , where 100x is the port number, but other DMRS configurations are also possible) and / or channel state information reference signal (CSI-RS) for channel estimation at UE 120. The RS can also include beam measurement RS (BRS or BMRS), beam refinement RS (BRRS), phase tracking RS (PTRS), etc.

[0056] Figure 3BShows examples of various DL channels within a time slot. The Physical Downlink Control Channel (PDCCH) carries DCI in one or more Control Channel Elements (CCEs). A CCE can include nine Resource Element Groups (REGs). Each REG can include four consecutive Resource Elements (REs) in one OFDM symbol. The Primary Synchronization Signal (PSS) can be in symbol 2 of one or more time slots in a frame. The UE 120 uses the PSS to determine subframe and / or symbol timing and the physical layer identity. The Secondary Synchronization Signal (SSS) can be in symbol 4 of one or more time slots in a frame. The UE 120 uses the SSS to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE 120 can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE 120 can determine the position of the aforementioned DMRS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB indicates the number of Resource Blocks (RBs) in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, paging messages, and / or broadcast system information not transmitted via the PBCH, such as System Information Blocks (SIBs).

[0057] As Figure 3C shown, some Resource Elements (REs) carry Demodulation Reference Signals (DMRS) for channel estimation at the base station 110 (indicated as R for one particular configuration, but other DMRS configurations are also possible). The UE 120 can transmit DMRS for the Physical Uplink Control Channel (PUCCH) and DMRS for the Physical Uplink Shared Channel. The PUSCH DMRS can be transmitted in the previous one or two symbols of the PUSCH. Depending on whether a short or long PUCCH is being transmitted, and depending on the particular PUCCH format used, the PUCCH DMRS can be transmitted in different configurations. Although not shown, the UE 120 can transmit a Sounding Reference Signal (SRS). The base station 110 can use the SRS for channel quality estimation to enable frequency - dependent scheduling on the UL.

[0058] Figure 3D Shows examples of various UL channels within a subframe of a frame. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indicator (RI), and / or HARQ ACK / NACK feedback. The PUSCH carries data and can additionally be used to carry a Buffer Status Report (BSR), a Power Headroom Report (PHR), and / or UCI.

[0059] As described above, provided Figures 3A - 3D as an example. Other examples may be different from those regarding Figures 3A - 3D described.

[0060] Figure 4 is a diagram illustrating examples of synchronization signal blocks (SSBs) according to various aspects of the present disclosure.

[0061] Certain UEs (e.g., light NR (NR-Light) UEs or low tier UEs) may be lower tier than other UEs (e.g., traditional UEs, high tier UEs), or may have reduced capabilities compared to other UEs. As an example, a low tier UE may have reduced transmit power (e.g., lower maximum transmit power) compared to a high tier UE. For example, the typical uplink transmit power of a low tier UE may be at least 10 dB lower than the uplink transmit power of a traditional enhanced mobile broadband (eMBB) UE. As another example, a low tier UE may have a reduced transmit bandwidth or receive bandwidth compared to other UEs. For example, compared to a high tier UE that may have a bandwidth of 20 - 100 MHz, a low tier UE may have an operating bandwidth between 5 MHz and 10 MHz for both transmission and reception. As a further example, a low tier UE may have a reduced number of receive antennas compared to other UEs. For example, a low tier UE may have only a single receive antenna, and thus a lower equivalent received signal-to-noise ratio (SNR) compared to other UEs that typically have, for example, four antennas. A low tier UE may also have reduced computational complexity compared to other UEs. Examples of low tier UEs may include, but are not limited to, smart wearable devices, industrial sensors, and video surveillance devices.

[0062] Low tier UEs and traditional UEs may receive synchronization signal blocks (SSBs). Figure 4 A conceptual diagram of an SSB is shown. The SSB includes a primary synchronization signal (PSS) 402 and a secondary synchronization signal (SSS) 404. The PSS 402 and SSS 404 may be used for radio frame synchronization and may each span one symbol of the SSB. The SSB may include a physical broadcast channel (PBCH) 406 that carries a master information block (MIB) 408 and spans at least two symbols of the SSB. The PSS, SSS, and PBCH are time domain multiplexed (TDM) in consecutive symbols, and the SSB may be used in single-beam and multi-beam scenarios. Additionally, depending on the operating frequency range of the base station, the PSS and SSS in the SSB may have different subcarrier spacings (SCSs). For example, if the operating frequency is below 6 GHz (e.g., sub-6 GHz), the SCS may be 15 kHz or 30 kHz. However, if the base station's operating frequency is above 6 GHz (e.g., millimeter wave (mmW)), the SCS may be 120 kHz or 240 kHz.

[0063] Base station 110 may transmit multiple SSBs in an SS burst set. Each SSB may contain its own PBCH and MIB, and each SSB may correspond to a different transmission beam from base station 110 during beam scanning. Although the SS burst set may have a specific period (e.g., 20 ms), the SSBs are typically restricted within a 5 - ms window in that period. In the 5 - ms window, the maximum number of possible candidate positions for SSBs can be defined as L, which may vary depending on the operating frequency or carrier - frequency range of the base station. For example, for a carrier - frequency range up to 3 GHz, L = 4; for a carrier - frequency range from 3 GHz to 6 GHz, L = 8; and for a carrier - frequency range from 6 GHz to 52.6 GHz, L = 64. Additional details are provided in conjunction with Figure 5A 、 Figure 5B 、 Figure 6A and Figure 6B below.

[0064] As Figure 4 shown, PBCH 406 includes MIB 408. As shown in Table 1 reproduced below, the MIB may include multiple parameters, which result in the same PBCH payload size in total for both sub - 6 - GHz and above - 6 - GHz frequency ranges. These parameters may at least include the system frame number (SFN), half - frame indicator, SSB index 410, grid offset, default downlink (DL) parameter set, remaining system information (RMSI) configuration 412, pre - demodulation reference signal (DMRS), cell barring, cell reselection, reserved bits, and cyclic redundancy check (CRC).

[0065]

[0066]

[0067] Table 1

[0068] Specifically, two of these MIB parameters include the SSB index 410 and the Remaining System Information (RMSI) configuration 412. Each SSB 400 in the SSB burst set has its own SSB index in the MIB. For the sub-6GHz frequency range, the UE can identify the SSB index 410 from the DMRS scrambling sequence in the PBCH 406. However, in above-6GHz or mmW frequencies, the MIB payload includes three additional bits for the UE to identify the SSB index 410 (giving a total of 64 possibilities for the SSB index). The 3 most significant bits (MSB) of the SSB index (or 3 reserved bits in above-6 frequencies), 1 bit of the half radio frame index, and the 4 least significant bits (LSB) of the SFN in the PBCH payload can be implemented as a signal generated by the physical layer. The rest of the PBCH payload can be provided by the upper layer with a transmission time interval (TTI) of, for example, 80 ms. Except for the SSB index 410, the PBCH content is the same for all SSBs within the SSB burst set of the same center frequency.

[0069] The RMSI configuration 412 is another parameter in the MIB. This parameter can consist of multiple bits including one or more MSBs 414 and one or more LSBs 416. For example, as Figure 4 shown, the RMSI configuration 412 can include a total of 8 bits, with four MSBs 414 and four LSBs 416. In other examples, the RMSI configuration 412 can include other numbers of bits, MSBs 414, and / or LSBs 416. For example, the RMSI configuration 412 can include 5 MSBs and 3 LSBs, and vice versa.

[0070] One or more MSBs 414 of the RMSI configuration 412 can identify the CORESET 418 carrying the PDCCH, and one or more LSBs 416 can identify the type 0 PDCCH CSS 420 of the CORESET 418 carrying the PDCCH. This CORESET 418 can be referred to as CORESET-0. The CORESET 418 is a collection of resource grids, including multiple consecutive RBs and multiple OFDM symbols. The CSS 420 is associated with the identified SSB index 410 and specifies the SFN 422, the slot index 424, and the starting symbol index 426 to search for the identified CORESET 418.

[0071] During the initial access to the base station, the UE first attempts to decode the received PBCH 406 and identify the payload of the MIB 408. Based on the DMRS sequence and / or the MIB, the UE identifies the SSB index 410 associated with the decoded PBCH 406. In addition, based on the RMSI configuration 412 in the MIB 408, the UE identifies the CORESET 418 (i.e., CORESET-0) corresponding to the SSB index 410 and the associated CSS 420. An aggregation level (AL) number (e.g., three) can be defined in association with the CORESET 418, where this aggregation level number identifies the number of control channel elements (CCEs) in which the UE can locate one or more PDCCH candidates. Based on the identified CORESET-0 and AL, the UE attempts blind decoding of the PDCCH candidates to identify the DCI in the PDCCH. Then, the UE can decode the DCI that schedules at least one physical downlink shared channel (PDSCH) carrying the RMSI payload. When the RMSI is received, the UE can continue to complete the initial access process.

[0072] The CORESET 418 can include many parameters, including the number of OFDM symbols and RBs, the resource element group (REG) corresponding to one physical resource block (PRB) in one OFDM symbol (e.g., 12 subcarriers), the CCE corresponding to 6 REGs, the CCE AL corresponding to the number of CCEs that constitute a PDCCH candidate, the REG bundle size (e.g., including consecutive REGs in the frequency domain and / or time domain), and the interleaving pattern of the REG bundle (i.e., in the frequency domain). Regarding the CORESET-0 received when the UE attempts an initial search for the PDCCH to access the base station, the number of OFDM symbols and RBs are based on one or more MSBs in the RMSI configuration 412, the CCE AL candidates can be 4 (e.g., 4 PDCCH candidates), 8 (e.g., 2 PDCCH candidates), or 16 (e.g., 1 PDCCH candidate), the REG bundle size can be fixed at 6 REGs, and the interleaving pattern can be fixed (e.g., R = 2). Compared with traditional UEs, low-end UEs with lower SNR or fewer receive antennas can benefit from PDCCH candidates with higher ALs because these PDCCH candidates can have lower coding rates.

[0073] Due to the interleaving pattern, the CCEs of PDCCH candidates typically span the entire resource bandwidth in CORESET-0. Therefore, the UE must be able to receive the entire CORESET to decode all PDCCH candidates. However, problems may arise when low-end UEs may not be able to receive CORESET-0. Depending on the SCS and the number of RBs of CORESET-0, the bandwidth of CORESET-0 may exceed the receiving bandwidth of low-end UEs. Table 2 shows different example combinations of SCS and RBs that may exist for CORESET-0 (where the bandwidth of the CORESET depends on the number of RBs).

[0074]

[0075]

[0076] Table 2

[0077] Therefore, depending on the SCS and the number of RBs configured for CORESET-0, low-end UEs may not be able to decode the PDCCH because in some cases, the receiving bandwidth of low-end UEs may be lower than the bandwidth of CORESET-0. For example, if a low-end UE only has a receiving bandwidth of 5 MHz, then if the SCS is 15 kHz and the number of RBs is 48 or 96, the low-end UE may not be able to receive the entire CORESET-0 because the CORESET bandwidth (8.64 MHz or 17.28 MHz) will be greater than the 5 MHz bandwidth of the UE.

[0078] Low-end UEs may not be able to solve this problem by attempting to decode the MIB in the PBCH through multiple rounds of receiving CORESET-0. For example, such a UE may not be able to simply receive a part of the PDCCH associated with one SSB index and receive another part of the PDCCH associated with another SSB index. The reason is that the PDCCH candidates within the CORESET-0 received in one SSB instance may not necessarily be the same as those received in another SSB instance. For example, the base station may attempt to dynamically change the position of the PDCCH resources between SSBs to provide flexibility in resource scheduling. In addition, as described above regarding the CORESET-0 parameters, the CCEs are typically interleaved across the entire frequency resources of CORESET-0 according to a fixed interleaving pattern. Therefore, if a low-end UE only receives a single part of CORESET-0 in a single instance, the UE may not be able to receive all the CCEs required to decode the PDCCH candidates.

[0079] As described above, provided Figure 4 as an example. Other examples may be different from those described regarding Figure 4 what is described.

[0080] Figure 5A and Figure 5B illustrates examples of different SSB positions and the maximum value L for different SCSs in the sub-6 frequency range. Specifically, Figure 5A illustrates the conceptual diagram 500, which shows the SSB positions within the 5 ms half-frame 502 at 15 kHz SCS, while Figure 5B illustrates the conceptual diagram 550, which shows the SSB positions within the 5 ms half-frame 552 at 30 kHz SCS. Referring to Figure 5A , for 15 kHz SCS, each subframe 504 of the half-frame 502 includes a 1 ms time slot 506 of fourteen OFDM symbols 508. Symbols 2-5 show an SSB 510 corresponding to one transmit beam, and symbols 8-11 show another SSB 510 corresponding to another beam. In this example, the SSB is transmitted within four subframes 504, resulting in a maximum of 8 SSBs (L = 8) in the half-frame 502. Referring to Figure 5B , for the higher 30 kHz SCS, each subframe 554 of the half-frame 552 includes two 0.5 ms time slots 556, each 0.5 ms time slot 556 having fourteen OFDM symbols 558. In this example, the transmission of 8 SSBs 560 (L = 8) occurs every 2 ms, rather than Figure 5A shown for 4 ms. Additionally, as Figure 5B shown, at 30 kHz SCS, there can be two frequency band-specific mapping options 562 for the SSB.

[0081] As described above, provide Figure 5A and Figure 5B as examples. Other examples may be different from those described with respect to Figure 5A and Figure 5B .

[0082] Figure 6A and Figure 6B illustrates examples of different SSB positions and the maximum value L for different SCSs in the above-6 GHz (mmW) frequency range. Specifically, Figure 6A illustrates the conceptual diagram 600, which shows the SSB positions within the 5 ms half-frame 602 at 120 kHz SCS, while Figure 6B illustrates the conceptual diagram 650, which shows the SSB positions within the 5 ms half-frame 652 at 240 kHz SCS. Referring to Figure 6A, for 120 kHz SCS, each time slot 604 of the half-frame 602 includes eight 0.125 ms time slots 606 of fourteen OFDM symbols 608. In this example, 4 SSBs 610 are transmitted within two time slots 604, resulting in up to 64 SSBs (L = 64) in the half-frame 602 (corresponding to 64 transmission beams from the base station). Refer to Figure 6B , for a higher 240 kHz SCS, each sub-frame 654 of the half-frame 652 includes 16 0.0625 ms time slots 656, and each 0.0625 ms time slot 656 has fourteen OFDM symbols 658. In this example, 8 SSBs 660 are transmitted within four time slots 604, resulting in up to 64 SSBs (L = 64) in the half-frame 602.

[0083] As described above, provide Figure 6A and Figure 6B as examples. Other examples may be different from those described with respect to Figure 6A and Figure 6B described.

[0084] Figure 7 is a diagram showing an example control resource set with control channel elements according to various aspects of the present disclosure.

[0085] As Figure 7 shown, CORESET-0 702 may include an interleaving pattern of CCEs 704. As further shown in Figure 7 , the CCEs 704 of a particular PDCCH candidate 706 may be located at all frequencies of CORESET-0 in an interleaved pattern (e.g., CCE#1, 3, 2, 4). Due to the interleaving of the CCEs 704 in CORESET-0 702, the UE 720 generally has to find the CCEs 704 spanning the entire bandwidth of CORESET-0, reorder them into the correct order as shown (e.g., CCE#1, 2, 3, 4), and decode the CCEs to identify the PDCCH. However, since the low-end UE 730 may only be able to receive a portion of CORESET-0 corresponding to its reception bandwidth 708, the low-end UE 730 may not be able to receive all the CCEs of the CORESET required to decode the PDCCH (e.g., Figure 7It is shown that in this example, the low-end UE 730 will only be able to receive CCE #2). Therefore, the low-end UE will not be able to decode the PDCCH due to its reduced receive bandwidth. Additionally, simply implementing a new CCE mapping pattern for PDCCH candidates within this reduced bandwidth 708 (e.g., placing CCE #1-4 within the receive bandwidth 708) will require sending additional signaling to the legacy UE 720 to inform them of this new pattern so that they can decode their own PDCCH candidates. Therefore, it is necessary to provide a low-bandwidth (low BW) CORESET-0 and associated CSS for the low-end UE that do not exceed the receive bandwidth of the low-end UE and can be interpreted from system configuration information (e.g., RMSI configuration) without the need to send additional signaling to the legacy UE in order to achieve coexistence between the low-end UE and the legacy UE, such that the legacy UE can continue to receive their own CORESET-0 (e.g., the legacy CORESET-0).

[0086] In some aspects, the system configuration information in the MIB (e.g., RMSI configuration) can be reused to enable the low-end UE to identify the low BW CORESET-0 and its associated search space based on a different interpretation of the system configuration information from that of the legacy UE, without the need for additional signaling for the legacy UE. The base station can configure the low BW CORESET-0 with a different structure from the legacy CORESET-0, including multiple resource grids (RG) and a CSS associated with the RG, where the low-end UE can identify these resource grids and CSS from the system configuration information. To improve the resource utilization of the low BW CORESET-0, the low BW CORESET-0 can be configured to include one or more overlapping RGs with the legacy CORESET-0, where the legacy CORESET-0 is also identified by the legacy UE through the same system configuration information. To provide a higher AL to reduce the coding rate, additional, non-overlapping RGs for the legacy CORESET-0 can be time-division-multiplexed (TDM) with one or more overlapping RGs. The low-end UE can be able to receive the overlapping and non-overlapping RGs and decode PDCCH candidates from the group of resource grids composed of these RGs. To prevent the non-overlapping RGs from conflicting with resources used by other CSS or SSB, the RGs associated with the low BW CORESET-0 can be persistent (or continuous) or non-persistent (or non-continuous) in the time domain or frequency domain.

[0087] As described above, provide Figure 7 as an example. Other examples may be different from those described with respect to Figure 7 what is described.

[0088] Figure 8FIG. 800 is a diagram illustrating an example of configurations of a CORESET and a CSS for initial access by a low-end UE according to various aspects of the present disclosure.

[0089] As shown by reference numeral 805, a conventional CORESET-0 (e.g., for a high-end UE) and a corresponding conventional CSS may span a wider bandwidth than the capabilities of a low-end UE. In this case, as shown by reference numeral 810, a light NR CORESET-0 (e.g., for a low-end UE) and a corresponding light NR CSS may be configured to be used by the low-end UE. As shown, the light NR CORESET-0 and the CSS may identify one or more overlapping resource grids 815 that overlap with one or more resource grids of the conventional CORESET-0 and the conventional CSS in a resource grid corresponding in time and frequency. Additionally or alternatively, the light NR CORESET-0 and the CSS may identify one or more non-overlapping resource grids 820 (e.g., resource grids time-division multiplexed with the conventional CORESET-0 and the conventional CSS) that do not overlap with the conventional CORESET-0 and the conventional CSS in time and frequency.

[0090] As shown, the non-overlapping resource grid 820 may include time-domain resources that occur later in time than the conventional CORESET-0 and the conventional CSS. For example, the conventional CORESET-0 and the conventional CSS are shown to occupy one or more time-domain resources at the start of a time slot (e.g., time slot j), and the non-overlapping resource grid 820 is shown to occupy time-domain resources at the end of the time slot and in subsequent time slots (e.g., time slot k, where k>j). Such a configuration may result in poor performance of the low-end UE.

[0091] For example, as shown by reference numeral 825, PDSCH communication scheduled by PDCCH in CORESET-0 (e.g., including SIB1) may occur in the same time slot (e.g., time slot j) as the conventional CORESET-0 and the conventional CSS. Due to the wider operating bandwidth, this scheduling works well for high-end UEs that can obtain and decode the PDCCH and PDSCH in the same time slot. However, due to the placement of the non-overlapping resource grid 820 that occurs during or after the transmission of the PDSCH, low-end UEs may not be able to obtain and decode the PDCCH until a later time (e.g., towards the end of time slot j) and / or a later time slot (e.g., time slot k). In this case, the low-end UE may need to buffer the communication received in time slot j until the low-end UE receives and decodes the PDCCH (e.g., in time slot k). However, due to reduced capabilities and / or less powerful hardware (e.g., smaller buffer size, less processing power, etc.), the low-end UE may not be able to buffer all of the communication in time slot j, especially when the PDSCH appears in a frequency resource different from the overlapping resource grid 815. Some of the techniques and apparatuses described herein allow low-end UEs to obtain PDSCH communication (e.g., including SIB1) scheduled in the same time slot as the conventional CORESET-0 and the conventional CSS, where the conventional CORESET-0 and the conventional CSS include PDCCH candidates that schedule the PDSCH communication.

[0092] As described above, provided Figure 8 as an example. Other examples may be different from those Figure 8 described with respect to

[0093] Figure 9 is a diagram illustrating another example 900 of the configuration of a CORESET and a CSS for initial access by a low-end UE in accordance with various aspects of the present disclosure.

[0094] As Figure 9As shown, base station 110 and UE 905 can communicate with each other. UE 905 can be included in a first type of UE, such as a low-end UE. In 5G, different types of UEs can operate with different capabilities. For example, compared to a second type of UE, a first type of UE (e.g., a light NR UE, a reduced-capability NR (NR-Lite) UE, a low-end UE, a mid-end UE, a reduced-feature set UE, etc.) can have lower capabilities and / or a reduced feature set. Similarly, compared to a first type of UE, a second type of UE (e.g., an NR UE, a high-end UE, a high-capability UE, a high-feature set UE, etc.) can have higher capabilities and / or a high-end feature set. For example, a first type of UE can communicate on a narrower maximum bandwidth part than a second type of UE (e.g., may not be able to communicate using as wide a bandwidth as a second type of UE), can support a lower maximum modulation and coding scheme (MCS) than a second type of UE (e.g., quadrature phase shift keying (QPSK) etc. compared to 256 quadrature amplitude modulation (QAM) etc.), can support a lower transmit power than a second type of UE (e.g., a lower maximum transmit power), can have a lower-level beamforming capability than a second type of UE, may not be able to communicate using a shortened transmission time interval (TTI) (e.g., a time slot length of 1 ms or shorter, 0.5 ms, 0.25 ms, 0.125 ms, 0.0625 ms, etc., depending on the subcarrier spacing) that a second type of UE can use for communication, and can have a smaller buffer size than a second type of UE.

[0095] As shown by reference numeral 910, base station 110 can configure a first CORESET (shown as a light NR CORESET-0) for a first type of UE (e.g., a low-end UE), and can configure a first CSS associated with the first CORESET. The first CORESET and the first CSS can be used by the first type of UE for initial network access before obtaining SIB1. For example, the first CORESET and the first CSS can be indicated in the MIB of the PBCH (e.g., in the SS / PBCH block). The first CORESET can be referred to as CORESET-0, and can carry type 0 PDCCHs for scheduling at least one PDSCH carrying SIB1. A CORESET can specify a set of resource grids (e.g., multiple consecutive RBs or subcarriers, and multiple OFDM symbols). A CSS can specify a set of time-domain resources where the CORESET is located (e.g., system frame number (SFN), slot index, start symbol index, etc.). Using the CORESET and the CSS, UE 120 can identify the set of resources to perform blind decoding for PDCCH candidates. In some aspects, each resource grid in the set of resource grids included in the CORESET includes one or more REGs of at least one CCE in the CORESET.

[0096] As shown by reference numeral 915, the first CORESET and the first CSS may identify one or more overlapping resource grids that overlap with one or more resource grids corresponding in time and frequency to a second CORESET (shown as a legacy CORESET-0) for a second type of UE (e.g., a high-end UE) and a second CSS associated with the second CORESET. By configuring at least one resource grid of the light NR CORESET-0 to overlap with the legacy CORESET-0, the base station 110 may save network resources by reusing some network resources for both the light NR CORESET-0 and the legacy CORESET-0.

[0097] As shown by reference numeral 920, the first CORESET and the first CSS may identify one or more non-overlapping resource grids that include one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS. For example, the non-overlapping resource grid (e.g., the time domain resources of the non-overlapping resource grid) is shown to appear in a first time slot (shown as time slot m), and the legacy CORESET-0 is shown to appear in a second time slot (shown as time slot j). The first time slot m may be a plurality of time slots before the second time slot j (e.g., the first time slot m appears before the second time slot j such that m < j). As described in more detail below in conjunction with Figure 10 and Figure 11 the first time slot m may be the time slot immediately before the second time slot j (e.g., the number of time slots may be equal to one), or the first time slot m may be more than one time slot before the second time slot j (e.g., the number of time slots may be greater than one).

[0098] In Figure 9 it, the non-overlapping resource grid (e.g., the time domain resources of the non-overlapping resource grid) is shown to appear at the start of the first time slot m and is shown as the first three OFDM symbols of the first time slot m (e.g., where the number of OFDM symbols may depend on the number of non-overlapping resource grids multiplexed in time). In this case, the non-overlapping resource grid may appear within a threshold number of OFDM symbols after the start (e.g., start boundary) of the first time slot m. As described in more detail below in conjunction with Figure 10 and Figure 11 in some aspects, the non-overlapping resource grid (e.g., the time domain resources of the non-overlapping resource grid) may appear at the end of the first time slot m. In this case, the non-overlapping resource grid may appear within a threshold number of OFDM symbols before the end (e.g., end boundary) of the first time slot m.

[0099] As shown by reference numeral 925, in some cases, the base station 110 may schedule PDSCH communications carrying SIB1 in the same time slot as the second CORESET. For example, the PDSCH with SIB1 may be scheduled by a type 0 PDCCH carried in CORESET-0 (e.g., both a legacy CORESET-0 and a light NR CORESET-0). As described above in connection with Figure 8 what is described, by configuring the non-overlapping resource grid of the light NR CORESET-0 to occur earlier in time than the legacy CORESET-0 (e.g., earlier in time than time slot j), compared to the case where the non-overlapping resource grid is configured to occur at a later time than the legacy CORESET-0, the low-end UE 905 may be able to obtain SIB1 without buffering the communications in time slot j and / or with reduced buffering.

[0100] As shown by reference numeral 930, the base station 110 may transmit and the UE 905 may receive a MIB that identifies the first CORESET and the first CSS. For example, the base station 110 may transmit the MIB in a PBCH (e.g., in an SS / PBCH block), as described elsewhere herein. The first CORESET and the first CSS may be identified in the MIB using a bit set, such as an 8-bit remaining minimum system information (RMSI) configuration. In some aspects, the most significant bit set of the RMSI configuration (e.g., the first four bits) identifies the first CORESET, while the least significant bit set of the RMSI configuration (e.g., the last four bits) identifies the first CSS. In some aspects, the same value of the RMSI configuration (e.g., the same 8-bit set) may indicate the first CORESET and the first CSS for a first type of UE and may also indicate the second CORESET and the second CSS for a second type of UE. In other words, the UE 120 may interpret the RMSI configuration at least in part based on the category of the UE 120, thereby saving overhead by reusing the RMSI configuration to indicate different CORESETs and corresponding CSSs for different categories of UEs.

[0101] As shown by reference numeral 935, the base station 110 may transmit one or more PDCCH communications in the first CORESET and the first CSS. As described above, the PDCCH communications (e.g., DCI) in the first CORESET and the first CSS may include a type 0 PDCCH that schedules the PDSCH carrying SIB1. As shown by reference numeral 940, the UE 905 may monitor one or more PDCCH candidates included in the first CORESET and the first CSS. For example, the UE 905 may perform blind decoding on the PDCCH candidates included in the first CORESET and the first CSS.

[0102] When the non-overlapping resource grid of the first CORESET is configured to appear before the second CORESET, the UE 905 may not need to buffer the communication in the entire configured bandwidth part (BWP) of the time slot in which the second CORESET appears in order to obtain SIB1 (e.g., which may appear anywhere in the bandwidth of time slot j). For example, the UE 905 may buffer the non-overlapping resource grid that appears in a bandwidth narrower than the entire BWP. When receiving an overlapping resource grid, the UE 905 may decode the PDCCH candidate(s) in the first CORESET to obtain SIB1 without buffering the communication in the entire BWP in which the overlapping resource grid appears. This may allow the low-end UE 905 to obtain SIB1, which otherwise may not be able to obtain SIB1 due to the complexity of processing and storing the communication across the entire BWP. Additionally, this may save resources (e.g., processing resources, memory resources, battery power, etc.) of the low-end UE 905 that may have limited resources.

[0103] As described elsewhere in this document, in some aspects, each resource grid (e.g., in one or more non-overlapping resource grids and one or more overlapping resource grids) includes one or more REGs of at least one CCE of the first CORESET. In some aspects, the base station 110 may configure the resource grid that appears earlier in time to include CCEs with lower indices compared to the indices of the CCEs included in the resource grid that appears later in time. In this way, the UE 905 may start decoding PDCCH candidates when receiving the earlier resource grid and may continue decoding PDCCH candidates (e.g., on-the-fly) when receiving the later resource grid. In some aspects, the order of the CCE indices corresponds to the order in which the corresponding CCEs appear in time. For example, the CCE that appears earliest in time may have the lowest index compared to other CCEs in the first CORESET, the CCE that appears second earliest in time may have the second lowest index, and so on, until the CCE that appears latest in time (e.g., in the overlapping resource grid), which may have the highest index. In some aspects, the overlapping resource grid may include CCEs with the highest indices regardless of the sorting of the CCE index values of the non-overlapping resource grid. Since there may be some time delay between when all non-overlapping resource grids are received and when the overlapping resource grid is received, this may allow the UE 905 to process (e.g., start decoding) PDCCH candidates when all non-overlapping resource grids are received and complete decoding when the overlapping resource grid is received. This may reduce the latency associated with PDCCH candidate decoding and / or may reduce the amount of buffering performed by the UE 905.

[0104] As described above, provide Figure 9As an example. Other examples may be different from those described with respect to Figure 9 which are described.

[0105] Figure 10 FIG. 1000 is a diagram illustrating another example of a configuration of a CORESET and a CSS for initial access by a low-end UE according to various aspects of the present disclosure.

[0106] In a first configuration 1010, a non-overlapping resource grid (e.g., time-domain resources of the non-overlapping resource grid) may appear in a first time slot (shown as time slot j-1), and a legacy CORESET-0 may appear in a second time slot (shown as time slot j). Thus, in some aspects, the first time slot including the non-overlapping resource grid may be one time slot before the second time slot including the legacy CORESET-0. In this way, the UE 905 may save UE resources by reducing the length of time that the information in the non-overlapping resource grid needs to be stored in the buffer of the UE 905.

[0107] In a second configuration 1020, a non-overlapping resource grid (e.g., time-domain resources of the non-overlapping resource grid) may appear in a first time slot (shown as time slot j-M), and a legacy CORESET-0 may appear in a second time slot (shown as time slot j). Thus, in some aspects, the first time slot including the non-overlapping resource grid may be M time slots before the second time slot including the legacy CORESET-0. In the first configuration 1010, M is equal to one. As further shown, the first time slot may be a downlink (DL) time slot, such as a DL time slot in the TDD UL / DL configuration of the base station 110 (e.g., the serving base station of the UE 905 described above in connection with Figure 9 This avoids a configuration where the non-overlapping resource grid is configured to appear in an uplink time slot, and thus avoids a configuration where the UE 905 cannot obtain the non-overlapping resource grid.

[0108] As Figure 10 shown (e.g., in both the first configuration 1010 and the second configuration 1020), a non-overlapping resource grid (e.g., time-domain resources of the non-overlapping resource grid) may appear at the end of the first time slot, shown as the last three OFDM symbols of the first time slot (e.g., where the number of OFDM symbols may depend on the number of time-division multiplexed non-overlapping resource grids). In this case, the non-overlapping resource grid may appear within a threshold number of OFDM symbols before the end (e.g., the end boundary) of the first time slot. For example, the non-overlapping resource grid may appear within a threshold number of OFDM symbols before the start OFDM symbol of the next consecutive time slot after the first time slot. In this way, the UE 905 may save UE resources by reducing the length of time that the information in the non-overlapping resource grid needs to be stored in the buffer of the UE 905.

[0109] As described above, provide Figure 10 as an example. Other examples may be different from those described with respect to Figure 10 what is described.

[0110] Figure 11 FIG. 1100 is a diagram illustrating another example of a configuration of a CORESET and a CSS for initial access by a low - end UE in accordance with various aspects of the present disclosure. Figure 11 An example of determining a first time slot of a non - overlapping resource grid including a first CORESET (e.g., light NR CORESET - 0) is shown, where the first time slot occurs a plurality of time slots before a second time slot including a second CORESET (e.g., legacy CORESET - 0).

[0111] In some aspects, UE 905 and / or base station 110 may determine the number of time slots (a plurality of time slots) at least in part based on a TDD UL / DL configuration. In some aspects, UE 905 may not be able to determine the TDD UL / DL configuration being used by base station 110 until UE 905 receives SIB1. Thus, in some aspects, UE 905 may determine the number of time slots at least in part based on a default TDD UL / DL configuration, which may be indicated in system information, specified according to a wireless communication standard, and so on. In some aspects, UE 905 and / or base station 110 may determine the number of time slots at least in part based on the period of a TDD UL / DL configuration (e.g., a default TDD UL / DL configuration). In some cases, the initial time slot (e.g., time slot 0) of a plurality of (e.g., all possible) TDD UL / DL configurations may be a DL time slot. Thus, in such cases, the first time slot including the non - overlapping resource grid may be the initial time slot of the TDD UL / DL configuration, and the time - domain position of the initial time slot may be determined at least in part based on the period of the TDD UL / DL configuration (e.g., 5 ms, 10 ms, etc.). In some aspects, the period may be the maximum period allowed by the TDD UL / DL configuration (e.g., it may be specified in a wireless communication standard). Additionally or alternatively, the period may be at least in part based on a period configured for UE 905 by the mobile network operator of UE 905's serving base station 110 (e.g., a default period, a maximum period, etc.).

[0112] In some aspects, UE 905 and / or base station 110 may determine the number of time slots at least in part based on a frequency range (e.g., sub-6 GHz frequency range, millimeter wave frequency range, etc.) including a first CORESET and a first CSS. Additionally or alternatively, UE 905 and / or base station 110 may determine the number of time slots at least in part based on a parameter set (e.g., subcarrier spacing) associated with a PDCCH candidate (e.g., a parameter set for PDCCH, for the first CORESET, for communication between UE 905 and base station 110, etc.). For example, for Frequency Range 1 (FR1) (e.g., sub-6 GHz), the number of time slots M may be determined from the set {2, 5} × 2 u where u is the parameter set index of the PDCCH (e.g., subcarrier spacing configuration index). For example, u may have values such as 0 (e.g., 15 kHz SCS), 1 (e.g., 30 kHz SCS), 2 (e.g., 60 kHz SCS), 3 (e.g., 120 kHz SCS), 4 (e.g., 240 kHz SCS), etc. In this example, if u equals zero, then M equals 2 or 5, indicating that the time slots 2 time slots earlier and / or 5 time slots earlier than the time slot including the conventional CORESET-0 are DL time slots. By determining the number of time slots M in this way, UE 905 can consider different symbol durations for different parameter sets to identify the DL time slots of the non-overlapping resource grid. As another example, for FR2 (e.g., millimeter wave), the number of time slots M may be determined from the set {2.5, 5, 7.5} × 2 × u

[0113] Additionally or alternatively, UE 905 and / or base station 110 may determine the number of time slots at least in part based on the time slot index of a second time slot including a second CORESET and a second CSS. For example, as indicated by reference numeral 1110, if the conventional CORESET-0 appears in time slot #0 (e.g., the time slot with a time slot index of 0), then the time slot one time slot earlier than time slot #0 (e.g., time slot #9 of the previous TDD UL / DL configuration cycle) may be an uplink time slot. In this case, the number of time slots M may be greater than one. In example 1100, if the time slot index of the second time slot is zero, then M is greater than one. As indicated by reference numeral 1120, in example 1100, the number of time slots M is determined by M = 5 × 2 u = 10 (e.g., where for a 30 kHz SCS, u = 1). In this case, the first time slot including the non-overlapping resource grid appears 10 time slots before the second time slot including the conventional CORESET-0. As shown, the first time slot is the initial time slot of the TDD UL / DL configuration cycle before the TDD UL / DL configuration cycle including the second time slot, and the first time slot is a DL time slot

[0114] As shown by reference numeral 1130, if a legacy CORESET-0 appears in slot #1 (e.g., the slot with a slot index of 1), then the slot that is one slot earlier than slot #1 (e.g., slot #0 of the same TDD UL / DL configuration cycle) can be a downlink slot. In this case, the number of slots M can be equal to one. In example 1100, if the slot index of the second slot is one, then M is equal to one. In this case, a non-overlapping resource grid appears at the end of slot #0 in the same TDD UL / DL configuration cycle as slot #1.

[0115] Additionally or alternatively, UE 905 and / or base station 110 can determine the number of slots at least in part based on one or more SSB indices associated with the legacy CORESET-0 and the legacy CSS. For example, as shown by reference numeral 1140, if the legacy CORESET-0 and the legacy CSS are associated with SSB indices 0 to 3, then the number of slots M is greater than one (e.g., as described above). As shown by reference numeral 1150, if the legacy CORESET-0 and the legacy CSS are associated with SSB indices 4 to 7, then the number of slots M is equal to one.

[0116] By determining the number of slots M as described herein, UE 905 and base station 110 can ensure that non-overlapping resource grids are transmitted and received in downlink slots, and thus avoid a configuration where UE 905 cannot obtain a non-overlapping resource grid (e.g., if the non-overlapping resource grid appears in an uplink slot). Additionally, resources of UE 905 (e.g., processing resources, memory resources, battery power, etc.) can be saved by reducing the length of time that information in the non-overlapping resource grid needs to be stored in the buffer of UE 905.

[0117] As described above, provided Figure 11 as an example. Other examples can be different from those described with respect to Figure 11 what is described.

[0118] Figure 12 is a diagram illustrating an example process 1200, for example, performed by a UE in accordance with various aspects of the present disclosure. Example process 1200 is an example where a UE (e.g., UE 120, UE 905, etc.) performs operations associated with the configuration of a CORESET and a CSS for initial access by a low-end UE.

[0119] As Figure 12As shown, in some aspects, process 1200 may include receiving a master information block that identifies a first CORESET for a first type of UE and a first CSS associated with the first CORESET, where the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap a resource grid corresponding to one or more of a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency, and one or more non-overlapping resource grids that include corresponding one or more time domain resources earlier than the time domain resources of the second CORESET and the second CSS (block 1210). For example, as described above, a UE (e.g., using the receiving processor 258, the controller / processor 280, the memory 282, etc.) may receive a master information block that identifies a first CORESET for a first type of UE and a first CSS associated with the first CORESET. In some aspects, the first CORESET and the first CSS identify one or more overlapping resource grids that overlap a resource grid corresponding to one or more of a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency. In some aspects, the first CORESET and the first CSS identify one or more non-overlapping resource grids that include corresponding one or more time domain resources earlier than the time domain resources of the second CORESET and the second CSS.

[0120] As Figure 12 further shown, in some aspects, process 1200 may include monitoring PDCCH candidates included in the first CORESET and the first CSS (block 1220). For example, as described above, a UE (e.g., using the receiving processor 258, the controller / processor 280, the memory 282, etc.) may monitor PDCCH candidates included in the first CORESET and the first CSS.

[0121] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects of one or more other processes described below and / or elsewhere incorporated herein.

[0122] In a first aspect, the corresponding one or more time domain resources are within a first time slot that is a plurality of time slots before a second time slot that includes the time domain resources of the second CORESET and the second CSS.

[0123] In a second aspect, either alone or in combination with the first aspect, the corresponding one or more time domain resources are within a threshold number of OFDM symbols before the start OFDM symbol of the next consecutive time slot after the first time slot.

[0124] In a third aspect, either alone or in combination with one or more of the first and second aspects, the number of time slots is one time slot.

[0125] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the first time slot is a downlink time slot in any time division duplex uplink / downlink configuration used by the serving base station.

[0126] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the number of time slots is determined at least in part based on the period of the time division duplex uplink / downlink configuration.

[0127] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the number of time slots is determined at least in part based on the frequency range including the first CORESET and the first CSS.

[0128] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the number of time slots is determined at least in part based on the parameter set or subcarrier spacing associated with the PDCCH candidate.

[0129] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the number of time slots is determined at least in part based on the time slot index of the second time slot in the time domain resource including the second CORESET and the second CSS.

[0130] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, if the time slot one time slot earlier than the second time slot is an uplink time slot, the number of time slots is greater than one, and the time slot one time slot earlier than the second time slot is identified at least in part based on the time slot index of the second time slot.

[0131] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, if the time slot one time slot earlier than the second time slot is a downlink time slot, the number of time slots is equal to one, and the time slot one time slot earlier than the second time slot is identified at least in part based on the time slot index of the second time slot.

[0132] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the number of time slots is determined at least in part based on the synchronization signal block index associated with the second CORESET.

[0133] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, a first resource grid in one or more non-overlapping resource grids includes a control channel element having an index lower than an index of a second resource grid that occurs later in time than the first resource grid in one or more non-overlapping resource grids or one or more overlapping resource grids.

[0134] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, each resource grid in one or more non-overlapping resource grids and one or more overlapping resource grids includes one or more resource element groups of at least one control channel element of a first CORESET.

[0135] Although Figure 12 illustrates example blocks of process 1200, in some aspects, process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks compared to those depicted in Figure 12 Additionally or alternatively, two or more blocks of process 1200 may be executed in parallel.

[0136] Figure 13 is a diagram illustrating an example process 1300, such as performed by a base station, in accordance with various aspects of the present disclosure. Example process 1300 is an example in which a base station (e.g., base station 110, etc.) performs operations associated with the configuration of a CORESET and a CSS for initial access by a low-end UE.

[0137] As Figure 13As shown, in some aspects, process 1300 may include configuring a first CORESET for a first type of UE and a first CSS associated with the first CORESET, wherein the first CORESET and the first CSS identify: one or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids (block 1310) that include one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS. For example, a base station (e.g., using a transmission processor 220, a controller / processor 240, a memory 242, etc.) may configure a first CORESET for a first type of UE and a first CSS associated with the first CORESET as described above. In some aspects, the first CORESET and the first CSS may identify one or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET. In some aspects, in some aspects, the first CORESET and the first CSS may identify one or more non-overlapping resource grids that include one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS.

[0138] As Figure 13 As further shown, in some aspects, process 1300 may include transmitting a master information block that identifies the first CORESET and the first CSS (block 1320). For example, a base station (e.g., using a transmission processor 220, a controller / processor 240, a memory 242, etc.) may transmit a master information block that identifies the first CORESET and the first CSS as described above.

[0139] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects of one or more other processes described below and / or elsewhere incorporated herein.

[0140] In a first aspect, process 1300 includes transmitting one or more physical downlink control channel communications in the first CORESET and the first CSS.

[0141] In a second aspect, either alone or in combination with the first aspect, the one or more corresponding time domain resources are within a first time slot that is a plurality of time slots before a second time slot that includes the time domain resources of the second CORESET and the second CSS.

[0142] In a third aspect, either alone or in combination with one or more of the first and second aspects, the corresponding one or more time-domain resources are within a threshold number of OFDM symbols before the start OFDM symbol of the next consecutive time slot after the first time slot.

[0143] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the number of time slots is one time slot.

[0144] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the first time slot is a downlink time slot in any time-division duplex uplink / downlink configuration used by the base station.

[0145] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the number of time slots is determined at least in part based on the period of the time-division duplex uplink / downlink configuration.

[0146] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the number of time slots is determined at least in part based on the frequency range including the first CORESET and the first CSS.

[0147] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the number of time slots is determined at least in part based on the parameter set or subcarrier spacing associated with the PDCCH candidate.

[0148] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the number of time slots is determined at least in part based on the time slot index of the second time slot of the time-domain resources including the second CORESET and the second CSS.

[0149] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, if the time slot one time slot earlier than the second time slot is an uplink time slot, the number of time slots is greater than one, and the time slot one time slot earlier than the second time slot is identified at least in part based on the time slot index of the second time slot.

[0150] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, if the time slot one time slot earlier than the second time slot is a downlink time slot, the number of time slots is equal to one, and the time slot one time slot earlier than the second time slot is identified at least in part based on the time slot index of the second time slot.

[0151] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the number of time slots is determined at least in part based on the synchronization signal block index associated with the second CORESET.

[0152] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, a first resource grid among one or more non-overlapping resource grids includes a control channel element having an index lower than that of a second resource grid that appears later in time than the first resource grid among one or more non-overlapping resource grids or one or more overlapping resource grids.

[0153] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, each resource grid among one or more non-overlapping resource grids and one or more overlapping resource grids includes one or more resource element groups of at least one control channel element of a first CORESET.

[0154] Although Figure 13 example blocks of process 1300 are shown, in some aspects, process 1300 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks compared to those depicted in Figure 13 . Additionally or alternatively, two or more blocks of process 1300 may be executed in parallel.

[0155] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure, or may be obtained from practice of the aspects.

[0156] As used herein, the term "component" is intended to be broadly construed as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented as hardware, firmware, and / or a combination of hardware and software.

[0157] As used herein, depending on the context, meeting a threshold may mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0158] Obviously, the systems and / or methods described herein can be implemented in different forms of hardware, firmware, and / or a combination of hardware and software. The actual specific control hardware or software code for implementing these systems and / or methods is not limited to these aspects. Thus, the operation and behavior of the systems and / or methods described herein are not referenced to a specific software code—it should be understood that the software and hardware can be designed to implement the systems and / or methods at least in part based on the description herein.

[0159] Even if a particular combination of features is recited in the claims and / or disclosed in the specification, such combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features can be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of the various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to "at least one" of a list of items means any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

[0160] Unless explicitly described, elements, acts, or instructions used herein should not be construed as critical or essential. Additionally, as used herein, the article "a, an" is intended to include one or more items and may be used interchangeably with "one or more." Further, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with "one or more." When only one item is meant, the phrase "only one" or similar language is used. Additionally, as used herein, the terms "has, have, having," etc. are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise explicitly stated.

Claims

1. A wireless communication method performed by a user equipment UE, comprising: receiving a master information block for identifying a first control resource set CORESET for a first type of UE and a first common search space CSS associated with the first CORESET, wherein the first CORESET and the first CSS are used to identify: one or more overlapping resource grids that overlap with one or more resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency, and one or more non-overlapping resource grids including corresponding one or more time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and monitoring physical downlink control channel PDCCH candidates included in the first CORESET and the first CSS.

2. The method according to claim 1, wherein, the corresponding one or more time domain resources are within a first time slot, and the first time slot is among a plurality of time slots before a second time slot of the time domain resources including the second CORESET and the second CSS.

3. The method according to claim 2, wherein, the corresponding one or more time domain resources are within a threshold number of orthogonal frequency division multiplexing OFDM symbols before a start OFDM symbol of a next consecutive time slot after the first time slot.

4. The method according to claim 2, wherein, the number of time slots is one time slot.

5. The method according to claim 2, wherein, the first time slot is a downlink time slot in any time division duplex uplink / downlink configuration used by a serving base station.

6. The method according to claim 2, wherein, the number of time slots is at least partially determined based on a period of a time division duplex uplink / downlink configuration.

7. The method according to claim 2, wherein, the number of time slots is at least partially determined based on a frequency range including the first CORESET and the first CSS.

8. The method according to claim 2, wherein, the number of time slots is at least partially determined based on a parameter set or subcarrier spacing associated with the PDCCH candidate.

9. The method according to claim 2, wherein, the number of time slots is at least partially determined based on a time slot index of the second time slot of the time domain resources including the second CORESET and the second CSS.

10. The method according to claim 9, wherein, if a time slot one time slot earlier than the second time slot is an uplink time slot, the number of time slots is greater than one, wherein the time slot one time slot earlier than the second time slot is identified at least partially based on the time slot index of the second time slot.

11. The method according to claim 9, wherein, if a time slot one time slot earlier than the second time slot is a downlink time slot, the number of time slots is equal to one, wherein the time slot one time slot earlier than the second time slot is identified at least partially based on the time slot index of the second time slot.

12. The method according to claim 2, wherein, The number of time slots is determined at least in part based on the synchronization signal block index associated with the second CORESET.

13. The method according to claim 1, wherein, a first resource grid in the one or more non-overlapping resource grids includes control channel elements, and the control channel elements have an index lower than that of a second resource grid that appears later in time than the first resource grid in the one or more non-overlapping resource grids or the one or more overlapping resource grids.

14. The method according to claim 1, wherein, each resource grid in the one or more non-overlapping resource grids and the one or more overlapping resource grids includes one or more resource element groups of at least one control channel element of the first CORESET.

15. A wireless communication method performed by a base station, comprising: configuring a first control resource set (CORESET) for a first type of user equipment (UE) and a first common search space (CSS) associated with the first CORESET, wherein the first CORESET and the first CSS are used to identify: one or more overlapping resource grids that overlap with one or more resource grids corresponding to a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency, and one or more non-overlapping resource grids including one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and transmitting a master information block for identifying the first CORESET and the first CSS.

16. The method according to claim 15, further comprising transmitting one or more physical downlink control channel communications in the first CORESET and the first CSS.

17. The method according to claim 15, wherein, the one or more corresponding time domain resources are within a first time slot, and the first time slot is among a plurality of time slots before a second time slot including the time domain resources of the second CORESET and the second CSS.

18. The method according to claim 17, wherein, the one or more corresponding time domain resources are within a threshold number of orthogonal frequency division multiplexing (OFDM) symbols before the start OFDM symbol of the next consecutive time slot after the first time slot.

19. The method according to claim 17, wherein, the number of time slots is one time slot.

20. The method according to claim 17, wherein, the first time slot is a downlink time slot in any time division duplex uplink / downlink configuration used by the base station.

21. The method according to claim 17, wherein, the number of time slots is determined at least in part based on the period of the time division duplex uplink / downlink configuration.

22. The method according to claim 17, wherein, the number of time slots is determined at least in part based on the frequency range including the first CORESET and the first CSS.

23. The method according to claim 17, wherein, The number of time slots is determined at least in part based on a set of parameters or subcarrier spacing associated with a physical downlink control channel associated with the first CORESET.

24. The method according to claim 17, wherein, The number of time slots is determined at least in part based on the time slot index of the second time slot including the time domain resources of the second CORESET and the second CSS.

25. The method according to claim 24, wherein, If the time slot one time slot earlier than the second time slot is an uplink time slot, the number of time slots is greater than one, wherein the time slot one time slot earlier than the second time slot is identified at least in part based on the time slot index of the second time slot.

26. The method according to claim 24, wherein, If the time slot one time slot earlier than the second time slot is a downlink time slot, the number of time slots is equal to one, wherein the time slot one time slot earlier than the second time slot is identified at least in part based on the time slot index of the second time slot.

27. The method according to claim 17, wherein, The number of time slots is determined at least in part based on the synchronization signal block index associated with the second CORESET.

28. The method according to claim 15, wherein, The first resource grid in the one or more non-overlapping resource grids includes control channel elements having a lower index than the index of a second resource grid that appears later in time than the first resource grid in the one or more non-overlapping resource grids or the one or more overlapping resource grids.

29. The method according to claim 15, wherein, Each resource grid in the one or more non-overlapping resource grids and the one or more overlapping resource grids includes one or more resource element groups of at least one control channel element of the first CORESET.

30. A user equipment UE for wireless communication, comprising: a memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: receive a master information block for identifying a first control resource set CORESET for a first type of UE and a first common search space CSS associated with the first CORESET, wherein the first CORESET and the first CSS are used to identify: one or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and one or more non-overlapping resource grids including one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and monitor physical downlink control channel PDCCH candidates included in the first CORESET and the first CSS.

31. A base station for wireless communication, comprising: a memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: Configure a first control resource set (CORESET) for a first type of user equipment (UE) and a first common search space (CSS) associated with the first CORESET, wherein the first CORESET and the first CSS are used to identify: One or more overlapping resource grids that overlap with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency, and One or more non-overlapping resource grids including one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and Transmit a master information block for identifying the first CORESET and the first CSS.

32. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the one or more processors to: Receive a master information block for identifying a first control resource set (CORESET) for a first type of UE and a first common search space (CSS) associated with the first CORESET, wherein the first CORESET and the first CSS are used to identify: One or more overlapping resource grids that overlap with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency, and One or more non-overlapping resource grids including one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and Monitor physical downlink control channel (PDCCH) candidates included in the first CORESET and the first CSS.

33. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions that, when executed by one or more processors of a base station, cause the one or more processors to: Configure a first control resource set (CORESET) for a first type of user equipment (UE) and a first common search space (CSS) associated with the first CORESET, wherein the first CORESET and the first CSS are used to identify: One or more overlapping resource grids that overlap with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET in time and frequency, and One or more non-overlapping resource grids including one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and Transmit a master information block for identifying the first CORESET and the first CSS.

34. A device for wireless communication, comprising: A device module for receiving a master information block for identifying a first control resource set (CORESET) for a first type of user equipment (UE) and a first common search space (CSS) associated with the first CORESET, wherein the first CORESET and the first CSS are used to identify: One or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and One or more non-overlapping resource grids including one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and A device module for monitoring physical downlink control channel (PDCCH) candidates included in the first CORESET and the first CSS.

35. A device for wireless communication, comprising: A device module for configuring a first control resource set (CORESET) for a first type of user equipment (UE) and a first common search space (CSS) associated with the first CORESET, wherein the first CORESET and the first CSS are used to identify: One or more overlapping resource grids that overlap in time and frequency with one or more corresponding resource grids of a second CORESET for a second type of UE and a second CSS associated with the second CORESET, and One or more non-overlapping resource grids including one or more corresponding time domain resources earlier than the time domain resources of the second CORESET and the second CSS; and A device module for transmitting a master information block for identifying the first CORESET and the first CSS.

36. A computer program product comprising computer-readable instructions that, when executed by one or more processors of a user equipment (UE), cause the one or more processors to perform the method according to any one of claims 1-14.

37. A computer program product comprising computer-readable instructions that, when executed by one or more processors of a base station, cause the one or more processors to perform the method according to any one of claims 15-29.

Images