Rate matching behavior for bundled CORESETs

Abstract

A method and apparatus for determining rate matching behavior for a plurality of control resource sets (CORESETs) is provided. A base station (BS) bundles a plurality of CORESETs into a global resource set. The BS configures a user equipment (UE) with the global resource set. The BS determines that resources assigned to a downlink data channel overlap at least a portion of the global resource set and determines whether data on the downlink data channel is to be rate matched around the global resource set or to use resources in the global resource set. The BS transmits the data on the downlink data channel based on the determination of rate matching.

Description

[0001] This application is a divisional application of the application filed on June 29, 2018, with application number 201880043045.3 (international application number PCT / US2018 / 040235) entitled "Rate Matching Behavior of Cluster CORESET".

[0002] (various) cross-references to related applications

[0003] This application claims priority to U.S. Application No. 16 / 022,136, filed June 28, 2018, which claims priority to U.S. Provisional Application S / N. 62 / 527,014, filed June 29, 2017, entitled “BUNDLED CORESET INDICATION”, both of which are expressly incorporated by reference. Technical Field

[0004] The techniques discussed below generally relate to wireless communication systems, and more particularly to the reuse of control resources for transmitting payload data in wireless communication.

[0005] introduction

[0006] New Radio (NR) is part of the next generation of 5G mobile broadband networks. Compared to current 3G and / or 4G technologies, 5G NR can deliver enhanced performance in wireless broadband communications at a lower cost per bit. 5G NR can achieve higher levels of latency, reliability, and security, and can be scaled to efficiently connect large numbers of wireless devices, such as Internet of Things (IoT) devices. While 5G NR offers significantly wider bandwidth and greater capacity than current networks, not all network devices may require and / or be able to support or utilize the full bandwidth available for wireless communication.

[0007] As the demand for mobile broadband access continues to grow, research and development are constantly advancing wireless communication technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance the user experience of mobile communications.

[0008] Brief Overview

[0009] The systems, methods, and apparatus of this disclosure each have several aspects, and their desired properties are not solely attributed to any single aspect. Without limiting the scope of this disclosure as set forth in the appended claims, some features will now be briefly discussed. Upon consideration of this discussion, and especially after reading the section entitled "Detailed Description," it will be understood how the features of this disclosure provide advantages including improved communication between access points and stations in a wireless network.

[0010] Certain aspects of this disclosure provide a method for wireless communication by a base station (BS). The method generally includes: clustering multiple control resource sets (CORESETs) into a global resource set; configuring the global resource set for a user equipment (UE); determining that resources assigned to a downlink data channel overlap with at least a portion of the global resource set; determining whether data on the downlink data channel should be rate-matched around the global resource set or use resources within the global resource set; and transmitting data on the downlink data channel based on the rate-matching determination.

[0011] Certain aspects of this disclosure provide a method for wireless communication by a user equipment (UE). The method generally includes: receiving configuration information relating to a global resource set comprising multiple bundled control resource sets (CORESETs); determining that resources assigned to a downlink data channel overlap with at least a portion of the global resource set; determining whether data on the downlink data channel is rate-matched around the global resource set or uses resources within the global resource set; and receiving data on the downlink data channel based on the rate-matching determination.

[0012] This disclosure provides an apparatus for wireless communication by a base station (BS). The apparatus generally includes: means for clustering multiple control resource sets (CORESETs) into a global resource set; means for configuring the global resource set for a user equipment (UE); means for determining that resources assigned to a downlink data channel overlap with at least a portion of the global resource set; means for determining whether data on the downlink data channel should be rate-matched around the global resource set or should use resources within the global resource set; and means for transmitting data on the downlink data channel based on the rate-matching determination.

[0013] Certain aspects of this disclosure provide an apparatus for wireless communication by a user equipment (UE). The apparatus generally includes: means for receiving configuration information relating to a global resource set comprising a plurality of bundled control resource sets (CORESETs); means for determining that resources assigned to a downlink data channel overlap with at least a portion of the global resource set; means for determining whether data on the downlink data channel is rate-matched around the global resource set or uses resources within the global resource set; and means for receiving data on the downlink data channel based on the rate-matching determination. Brief description of the attached diagram

[0014] Figure 1 This is a conceptual diagram illustrating an example of a radio access network according to some aspects of this disclosure.

[0015] Figure 2This is a block diagram that conceptually illustrates an example of a scheduling entity communicating with one or more scheduled entities according to some aspects of this disclosure.

[0016] Figure 3 This is a block diagram illustrating an example of a hardware implementation of a scheduling entity of a processing system according to some aspects of this disclosure.

[0017] Figure 4 This is a block diagram illustrating an example of a hardware implementation of a scheduled entity employing a processing system according to some aspects of this disclosure.

[0018] Figure 5 This is a diagram illustrating an example of a downlink-centric time slot according to some aspects of this disclosure.

[0019] Figure 6 This is a diagram illustrating an example of an uplink-centric timeslot based on some aspects of this disclosure.

[0020] Figure 7 This is a diagram illustrating an example of a resource grid based on some aspects of this disclosure.

[0021] Figure 8 This is an explanation of some aspects based on this disclosure. Figure 7 A diagram showing a portion of the resource grid.

[0022] Figure 9 This is a diagram illustrating examples of various search spaces according to some aspects of this disclosure.

[0023] Figure 10 Example operation 1000, performed by a base station (BS) (e.g., gNB) according to certain aspects of this disclosure, is described to determine rate matching behavior of multiple CORESETs.

[0024] Figure 11 Example operation 1100, performed by the UE according to certain aspects of this disclosure, is described for determining rate matching behavior of multiple CORESETs. Detailed description

[0025] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0026] 5G New Radio (NR) can provide significantly more bandwidth to support wireless communication for a large number of wireless devices. However, due to limitations such as hardware or resources, some wireless devices may not need or be able to utilize the full bandwidth or available resources. In some examples, a device may not utilize all available control resources (e.g., time and / or frequency resources) for transmitting / receiving control information. In this situation, it may be possible to reuse or reallocate unused control resources to carry payload data.

[0027] Various methods and apparatuses are provided in this disclosure for reusing or reallocating unused control resources (e.g., downlink (DL) control resources) for DL ​​payload data. However, this disclosure is not limited to the DL examples described below, and the concept can be extended to reuse control resources for uplink (UL) data transmission in both frequency division duplex (FDD) and time division duplex (TDD) configurations.

[0028] The various concepts presented throughout this disclosure can be implemented across a wide range of telecommunications systems, network architectures, and communication standards. Now refer to... Figure 1 The illustrative example of radio access network 100 is provided as an explanatory example rather than a limitation.

[0029] The geographical area covered by the radio access network 100 can be divided into several cellular areas (cells), which can be uniquely identified by the user equipment (UE) based on an identifier broadcast in the geographical area from an access point or base station. Figure 1 Macrocells 102, 104, and 106, and small cell 108, are described, each of which may include one or more sectors. A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. Radio links within a sector may be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, the multiple sectors within the cell may be formed by separate antenna groups, where each antenna is responsible for communication with UEs in a portion of the cell.

[0030] Generally, a base station (BS) serves each cell. More broadly, a base station is a network element in a radio access network responsible for radio transmissions to and from a UE in one or more cells. A BS may also be referred to by those skilled in the art as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), B-node (NB), evolved B-node (eNB), or any other suitable term.

[0031] exist Figure 1In the illustration, two high-power base stations 110 and 112 are shown in cells 102 and 104; and a third high-power base station 114 is shown as a remote radio head (RRH) 116 controlling cell 106. That is, the base stations may have integrated antennas, or they may be connected to the antenna or RRH via feed cables. In the illustrated example, cells 102, 104, and 106 may be referred to as macrocells because high-power base stations 110, 112, and 114 support cells with large sizes. Furthermore, a low-power base station 118 is shown in a small cell 108 (e.g., microcell, picocell, femtocell, home base station, home B-node, home evolved B-node, etc.), which may overlap with one or more macrocells. In this example, cell 108 may be referred to as a small cell because low-power base station 118 supports cells with relatively small sizes. Cell size settings can be determined based on system design and component constraints. To understand, the radio access network 100 may include any number of radio base stations and cells. Furthermore, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 110, 112, 114, and 118 provide radio access points to the core network for any number of mobile devices.

[0032] Figure 1 Further includes a quadcopter or drone 120, which can be configured to be used as a base station. That is, in some examples, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station (such as the quadcopter 120).

[0033] Generally, a base station may include a backhaul interface for communicating with the backhaul portion of the network. The backhaul provides a link between the base station and the core network, and in some examples, it provides interconnection between respective base stations. The core network is part of the wireless communication system and is generally independent of the radio access technology used in the radio access network. Various types of backhaul interfaces can be used, such as direct physical connections using any suitable transport network, virtual networks, etc. Some base stations can be configured as integrated access backhaul (IAB) nodes, where radio spectrum can be used for both access links (i.e., radio links with the UE) and backhaul links. This approach is sometimes referred to as radio self-backhaul. By using radio self-backhaul (instead of requiring each new base station deployment to have its own hard-wired backhaul connection), radio spectrum used for communication between the base station and the UE can be utilized for backhaul communication, enabling the rapid and easy deployment of highly dense small cellular networks.

[0034] Radio access network 100 is described as supporting wireless communication for multiple mobile devices. Mobile devices are typically referred to as User Equipment (UE) in standards and specifications issued by the Third Generation Partnership Project (3GPP), but such devices may also be referred to by those skilled in the art as mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handheld device, terminal, user agent, mobile client, client, or any other suitable term. The UE can be a device that provides users with access to network services.

[0035] In this document, a “mobile” device does not necessarily need to be mobile and may be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. For example, some non-limiting examples of mobile devices include mobile devices, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), laptops, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems, such as those corresponding to the “Internet of Things” (IoT). Mobile devices may additionally be self-propelled or other transportation vehicles, remote sensors or actuators, robots or robotic devices, satellite radios, Global Positioning System (GPS) devices, object tracking devices, drones, multi-rotor aircraft, quadcopters, remote control devices, consumer and / or wearable devices (such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers), digital audio players (e.g., MP3 players), cameras, game consoles, and so on. Mobile devices may also be digital home or smart home devices, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, and so on. Mobile devices may additionally include smart energy equipment, security equipment, solar panels or solar arrays, urban infrastructure equipment for controlling electrical power (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weapons, etc. Furthermore, mobile devices can provide networked healthcare or telemedicine support, i.e., remote health care. Remote health care devices may include remote health monitoring devices and remote health supervision devices, whose communications may be prioritized, for example, in the form of priority access for critical service data transmission and / or relevant QoS for critical service data transmission, or priority access over other types of information.

[0036] Within the radio access network 100, a cellular cell may include UEs capable of communicating with one or more sectors of each cellular cell. For example, UEs 122 and 124 may communicate with base station 110; UEs 126 and 128 may communicate with base station 112; UEs 130 and 132 may communicate with base station 114 via RRH 116; UE 134 may communicate with low-power base station 118; and UE 136 may communicate with mobile base station 120. Here, each base station 110, 112, 114, 118, and 120 may be configured as an access point provided to the core network (not shown) for all UEs in the corresponding cellular cell.

[0037] In another example, a mobile network node (e.g., quadcopter 120) may be configured to act as a UE. For example, quadcopter 120 may operate within cell 102 by communicating with base station 110. In some aspects of this disclosure, two or more UEs (e.g., UEs 126 and 128) may communicate with each other using peer-to-peer (P2P) or sidelink signals 127 without relaying the communication through a base station (e.g., base station 112).

[0038] Unicast or broadcast transmissions of control information and / or traffic information from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124) may be referred to as downlink (DL) transmissions, while transmissions of control information and / or traffic information originating at a UE (e.g., UE 122) may be referred to as uplink (UL) transmissions. Furthermore, uplink and / or downlink control information and / or traffic information may be temporally divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol may refer to a time unit carrying one resource element (RE) per subcarrier in an OFDM waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes may be grouped together to form a single frame or radio frame. Of course, these definitions are not mandatory, and any suitable scheme may be used to organize the waveform, and various time divisions of the waveform may have any suitable duration.

[0039] The air interface in the radio access network 100 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication between various devices. For example, multiple access for uplink (UL) or reverse link transmissions from UEs 122 and 124 to base station 110 can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. Furthermore, multiplexing for downlink (DL) or forward link transmissions from base station 110 to UEs 122 and 124 can be provided using Time Division Multiplexing (TDM), Code Division Multiplexing (CDM), Frequency Division Multiplexing (FDM), Orthogonal Frequency Division Multiplexing (OFDM), Sparse Code Multiplexing (SCM), or other suitable multiplexing schemes.

[0040] Furthermore, the air interface in the radio access network 100 can utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with each other in both directions. Full-duplex means that both endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time. In a wireless link, a full-duplex channel generally relies on the physical isolation between the transmitter and receiver, and appropriate interference cancellation techniques. Full-duplex simulation for wireless links is typically achieved using Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated using time division multiplexing. That is, at some times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in the other direction, where the direction can change very rapidly, for example, several times per time slot.

[0041] In radio access network 100, the ability of a UE to communicate independently of its location while on the move is referred to as mobility. The various physical channels between the UE and the radio access network are generally established, maintained, and released under the control of a Mobility Management Entity (MME). In various aspects of this disclosure, radio access network 100 may utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., the transfer of the UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, UE 124 (which can be interpreted as a vehicle, but may be any suitable form of UE) may move from a geographic area corresponding to its serving cell 102 to a geographic area corresponding to a neighboring cell 106. When the signal strength or quality from the neighboring cell 106 exceeds the signal strength or quality of its serving cell 102 for a given amount of time, UE 124 may transmit a report message indicating this condition to its serving base station 110. In response, UE 124 may receive a handover command, and the UE may undergo a handover to cell 106.

[0042] In a network configured for UL-based mobility, UL reference signals from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 110, 112, and 114 / 116 can broadcast unified synchronization signals (e.g., unified primary synchronization signal (PSS), unified secondary synchronization signal (SSS), and unified physical broadcast channel (PBCH)). UEs 122, 124, 126, 128, 130, and 132 can receive unified synchronization signals, derive carrier frequencies and time slot timings from these synchronization signals, and transmit uplink pilots or reference signals in response to the derived timings. The uplink pilot signal transmitted by a UE (e.g., UE 124) can be received concurrently by two or more cells (e.g., base stations 110 and 114 / 116) within the radio access network 100. Each of these cells can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 110 and 114 / 116 and / or a central node within the core network) can determine the serving cell for UE 124. As UE 124 moves through radio access network 100, the network can continue to monitor the uplink pilot signal transmitted by UE 124. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, network 100 can, with or without notification to UE 124, switch UE 124 from the serving cell to that neighboring cell.

[0043] Although the synchronization signal transmitted by base stations 110, 112, and 114 / 116 can be uniform, it does not necessarily identify a specific cell. Instead, it can identify a zoning that includes multiple cells operating on the same frequency and / or with the same timing. Using zoning in 5G networks or other next-generation communication networks enables uplink-based mobility frameworks and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0044] In various implementations, the air interface in the radio access network 100 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by means of a mobile network operator that has purchased a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without a government-granted license. While some technical rules generally still need to be followed to access unlicensed spectrum, access can be obtained by any operator or device. Shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum may provide Licensed Shared Access (LSA) to share that spectrum with other parties, for example, by utilizing conditions determined by a suitable licensee.

[0045] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communication between some or all devices and equipment within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, the UE or the scheduled entity utilizes resources allocated by the scheduling entity.

[0046] A base station is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs). In other examples, sidelink signaling can be used between UEs without relying on scheduling or control information from the base station. For example, UE 138 is interpreted as communicating with UEs 140 and 142. In some examples, UE 138 is acting as a scheduling entity or a primary sidelink device, and UEs 140 and 142 can be used as scheduled entities or non-primary (e.g., secondary) sidelink devices. In yet another example, a UE can be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network, and / or a mesh network. In a mesh network example, UEs 140 and 142 may optionally communicate directly with each other in addition to communicating with scheduling entity 138.

[0047] Therefore, in a wireless communication network with scheduled access to time-frequency resources and with cellular, P2P, or mesh configurations, a scheduling entity and one or more scheduled entities can communicate using the scheduled resources. Now refer to Figure 2The block diagram illustrates scheduling entity 202 and multiple scheduled entities 204 (e.g., 204a and 204b). Here, scheduling entity 202 may correspond to base stations 110, 112, 114, and / or 118. In additional examples, scheduling entity 202 may correspond to UE 138, quadcopter 120, or any other suitable node in radio access network 100. Similarly, in various examples, scheduled entities 204 may correspond to UEs 122, 124, 126, 128, 130, 132, 134, 136, 138, 140, and 142, or any other suitable node in radio access network 100.

[0048] like Figure 2 As explained, scheduling entity 202 may broadcast traffic 206 (which may be referred to as downlink traffic) to one or more scheduled entities 204. According to certain aspects of this disclosure, the term downlink may refer to point-to-multipoint transmission originating at scheduling entity 202. Broadly, scheduling entity 202 is a node or device responsible for scheduling traffic (including downlink transmissions and, in some examples, uplink traffic 210 from one or more scheduled entities to scheduling entity 202) in a wireless communication network. Another way to describe the system may be using the term broadcast channel multiplexing. According to various aspects of this disclosure, the term uplink may refer to point-to-point transmission originating at scheduled entity 204. Broadly, scheduled entity 204 is a node or device that receives scheduling control information (including, but not limited to, scheduling permission, synchronization, or timing information) or other control information from another entity in the wireless communication network (such as scheduling entity 202).

[0049] Scheduling entity 202 may broadcast control information 208 to one or more scheduled entities 204, including one or more control channels (such as PBCH; PSS; SSS; Physical Control Format Indicator Channel (PCFICH); Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH); and / or Physical Downlink Control Channel (PDCCH), etc.). PHICH carries HARQ feedback transmissions, such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well-known to those skilled in the art, in which packet transmissions can be checked for accuracy at the receiving side, and if acknowledged, an ACK can be transmitted, while if not acknowledged, a NACK can be transmitted. In response to a NACK, the transmitting device can send a HARQ retransmission, which enables catch-up combining, incremental redundancy, etc.

[0050] Uplink traffic 210 and / or downlink traffic 206, including one or more traffic channels (such as the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH) (and in some examples, the System Information Block (SIB)), can additionally be transmitted between the scheduling entity 202 and the scheduled entity 204. The transmission of control and traffic information can be organized by subdividing the carrier into appropriate Transmission Time Intervals (TTIs).

[0051] Furthermore, the scheduled entity 204 may transmit uplink control information 212, including one or more uplink control channels, to the scheduling entity 202. The uplink control information may include a wide variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink traffic transmissions. In some examples, the control information 212 may include a scheduling request (SR), i.e., a request to the scheduling entity 202 to schedule uplink transmissions. Here, in response to the SR transmitted on the control channel 212, the scheduling entity 202 may transmit downlink control information 208, which may schedule TTIs for uplink packet transmissions.

[0052] Uplink and downlink transmissions can generally utilize appropriate error-correcting block codes. In typical block codes, an information message or sequence is broken into blocks, and an encoder at the transmitting device then mathematically adds redundancy to that information message. Utilizing this redundancy in the encoded information message improves the reliability of the message, thereby enabling the correction of any bit errors that may occur due to noise. Some examples of error-correcting codes include Hamming codes, Bosch-Choherry-Heim (BCH) codes, turbo codes, low-density parity-check (LDPC) codes, and polar codes. Various implementations of the scheduling entity 202 and the scheduled entity 204 may include suitable hardware and capabilities (e.g., encoders and / or decoders) to utilize one or more of these error-correcting codes for wireless communication.

[0053] In some examples, scheduled entities (such as first scheduled entity 204a and second scheduled entity 204b) may utilize sidelink signals for direct D2D communication. Sidelink signals may include sidelink traffic 214 and sidelink control 216. Sidelink control information 216 may include a request-to-send (RTS) channel and a clear-to-send (CTS) channel. The RTS allows scheduled entity 204 to request the duration for which a sidelink channel is to be held available for sidelink signals; and the CTS allows scheduled entity 204 to indicate, for example, the availability of the sidelink channel during the requested duration. The exchange of RTS and CTS signals (e.g., a handshake) allows different scheduled entities performing sidelink communication to negotiate the availability of the sidelink channel before the communication of sidelink traffic information 214.

[0054] Figure 2 The channels or carriers described are not necessarily all the channels or carriers available between the scheduling entity 202 and the scheduled entity 204, and those skilled in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be available in addition to those described.

[0055] Figure 3 This is a block diagram illustrating an example of the hardware implementation of the scheduling entity 300 using the processing system 314. For example, the scheduling entity 300 could be as follows: Figure 1 The user equipment (UE) described in either or both of 2. In another example, the scheduling entity 300 may be as follows: Figure 1 The base station described by any one or more of 2.

[0056] The scheduling entity 300 may be implemented using a processing system 314 including one or more processors 304. Examples of processors 304 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, the scheduling entity 300 may be configured to perform any one or more functions described herein. That is, the processor 304 utilized in the scheduling entity 300 may be used to implement the following descriptions and in Figure 5-11 The process and procedures explained in the Chinese text, including any one or more of them.

[0057] In this example, the processing system 314 may be implemented with a bus architecture generally represented by bus 302. Depending on the specific application and overall design constraints of the processing system 314, bus 302 may include any number of interconnect buses and bridges. Bus 302 communicatively couples together various circuits including one or more processors (generally represented by processor 304), memory 305, and computer-readable media (generally represented by computer-readable media 306). Bus 302 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 308 provides an interface between bus 302 and transceiver 310. Transceiver 310 provides a communication interface or means for communicating with various other devices over a transmission medium. Depending on the characteristics of the device, a user interface 312 (e.g., keypad, display, speaker, microphone, joystick) may also be provided.

[0058] In some aspects of this disclosure, processor 304 may include being configured to implement the following regarding Figure 5-11A circuit system that describes one or more functions.

[0059] Processor 304 is responsible for managing bus 302 and general processing, including the execution of software stored on computer-readable medium 306. When executed by processor 304, the software causes processing system 314 to perform various functions described below for any particular device. Computer-readable medium 306 and memory 305 may also be used to store data manipulated by processor 304 during software execution.

[0060] One or more processors 304 in the processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. The software may reside on a computer-readable medium 306. The computer-readable medium 306 may be a non-transitory computer-readable medium. As examples, non-transient computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical discs (e.g., compact discs (CDs) or digital universal discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable media for storing software and / or instructions accessible and readable by a computer. As examples, computer-readable media may also include carrier waves, transmission lines, and any other suitable media for transmitting software and / or instructions accessible and readable by a computer. Computer-readable medium 306 may reside in processing system 314, be external to processing system 314, or be distributed across multiple entities including processing system 314. Computer-readable medium 306 may be implemented in a computer program product. As an example, a computer program product may include a computer-readable medium in encapsulation material. Those skilled in the art will recognize how the functionality described throughout this disclosure can be best achieved, depending on the specific application and the overall design constraints imposed on the system as a whole.

[0061] In one or more examples, computer-readable storage medium 306 may include components configured to implement the above-mentioned... Figure 5-11 Software that describes one or more functions.

[0062] Figure 4This is a conceptual diagram illustrating an example hardware implementation of an exemplary scheduled entity 400 employing a processing system 414. According to various aspects of this disclosure, elements, or any part thereof, or any combination thereof, can be implemented using a processing system 414 including one or more processors 404. For example, the scheduled entity 400 may be as shown in... Figure 1 User equipment (UE) as described in either or both of 2.

[0063] Processing system 414 can be with Figure 3 The processing system 314 described above is essentially the same, including a bus interface 408, a bus 402, a memory 405, a processor 404, and a computer-readable medium 406. Furthermore, the scheduled entity 400 may include components similar to those described above. Figure 3 The user interfaces and transceivers described herein are substantially similar to those in user interface 412 and transceiver 410. That is, the processor 404 utilized in the scheduled entity 400 can be used to implement the following description and in... Figure 5-11 Any one or more processes explained in the text.

[0064] In some aspects of this disclosure, processor 404 may include being configured to implement the following regarding Figure 5-11 A circuit system that describes one or more functions.

[0065] Figure 5-6 This is a schematic diagram illustrating the structure of various time slot formats according to various aspects of this disclosure. For example... Figure 5 As explained herein, in each of these explanations, the horizontal dimension represents time, and the vertical dimension represents frequency. These dimensions are not intended to be drawn precisely to scale, but are merely used as a scheme to explain the time-varying characteristics of different waveforms as they may be configured in the respective examples and embodiments. Figure 5 This is a diagram illustrating an example of a DL-centered timeslot 500. The DL-centered timeslot may include a control section 502. The control section 502 may exist in the initial or beginning portion of the DL-centered timeslot. The control section 502 may include various scheduling information and / or control resources corresponding to the various portions of the DL-centered timeslot. In some configurations, the control section 502 may include a physical DL control channel (PDCCH), such as... Figure 5 As indicated in the text. The DL-centralized time slot may also include a DL data portion 504. The DL data portion 504 may sometimes be referred to as the payload of the DL-centralized time slot. The DL data portion 504 may include communication resources for conveying DL data from the scheduling entity 202 (e.g., eNB) to the scheduled entity 204 (e.g., UE). In some configurations, the DL data portion 504 may be a Physical DL Shared Channel (PDSCH).

[0066] The DL-centered timeslot may also include a shared UL portion 506. The shared UL portion 506 may sometimes be referred to as a UL burst, shared UL burst, and / or various other suitable terms. The shared UL portion 506 may include feedback information corresponding to various other portions of the DL-centered timeslot. For example, the shared UL portion 506 may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include ACK signals, NACK signals, HARQ indicators, and / or various other suitable types of information. The shared UL portion 506 may include additional or alternative information, such as information related to the Random Access Channel (RACH) protocol, scheduling requests (SR), and various other suitable types of information. Figure 5 As explained herein, the end of the DL data portion 504 may be temporally separated from the start of the common UL portion 506. This temporal separation may sometimes be referred to as a gap, a protection period, a protection interval, and / or various other suitable terms. This separation provides the time for switching from DL communication (e.g., a reception operation performed by the scheduled entity 204 (e.g., the UE)) to UL communication (e.g., a transmission performed by the scheduled entity 204 (e.g., the UE)). Those skilled in the art will understand that the foregoing is merely one example of a DL-centered subframe, and alternative structures with similar characteristics may exist without departing from the aspects described herein.

[0067] Figure 6 This is a diagram illustrating an example of a UL central time slot 600. The UL central time slot may include a control section 602. The control section 602 may be present in the initial or beginning portion of the UL central time slot. Figure 6 The control section 602 in the above reference can be similar to the one described above. Figure 5 The control portion 502 is described. The UL-centric timeslot may also include a UL data portion 604. The UL data portion 604 may sometimes be referred to as the payload of the UL-centric timeslot. This UL portion may refer to the communication resources used to transmit UL data from the scheduled entity 204 (e.g., UE) to the scheduling entity 202 (e.g., eNB). In some configurations, the control portion 602 may be a Physical UL Shared Channel (PUSCH). Figure 6 As explained herein, the end of control section 602 may be time-separated from the start of UL data section 604. This time separation may sometimes be referred to as a gap, protection period, protection interval, and / or various other suitable terms. This separation provides time for switching from DL communication (e.g., a reception operation performed by scheduling entity 202 (e.g., UE)) to UL communication (e.g., a transmission performed by scheduling entity 202 (e.g., UE)). UL-centralized time slots may also include a shared UL section 606. Figure 6 The common UL portion 606 in the above reference can be similar to the above reference. Figure 5The common UL portion 506 is described. The common UL portion 506 may include additional or alternative information relating to the Channel Quality Indicator (CQI), the Probe Reference Signal (SRS), and various other suitable types of information. Those skilled in the art will understand that the foregoing is merely one example of a UL-centered timeslot, and that alternative structures with similar characteristics may exist without necessarily departing from the aspects described herein.

[0068] Figure 7 This is a diagram illustrating a resource grid 700 for wireless communication according to one aspect of this disclosure. Figure 7 In this configuration, the frequency increases vertically, and the horizontal direction represents the symbol (OFDM symbol) timing. Each resource element 702 represents a combination of symbol time and bandwidth (e.g., carrier) that can be allocated or scheduled to transmit information or data. Some resource elements in resource element 702 can be grouped together to be allocated as units or blocks.

[0069] Figure 8 This section explains a portion of resource grid 700, which includes several resource elements, up to grid 800. Figure 8 In this model, the frequency or bandwidth (BW) extends vertically, and the time dimension extends horizontally. The frequency or BW dimension is divided into units, which may be called frequency modulation, OFDM modulation, or subcarrier; and the time dimension is divided into units, which may be symbol duration or OFDM symbol. These intersecting divisions form a pattern similar to... Figure 7 The resource element (RE) shown is a grid of resource elements. In this example, each RE may correspond to a cell of one OFDM frequency modulation and one OFDM symbol.

[0070] Resource elements corresponding to the same OFDM symbol can be grouped into resource element groups (e.g., resource element group 802). In this example, each resource element group (REG) may include four resource elements. Figure 8 The diagram illustrates nine REGs, each comprising four REs (e.g., REG 1 to REG 9). In other aspects of this disclosure, and in other examples, REGs may have more or fewer resource elements. Resource elements may also be grouped differently from... Figure 8 The resource element groups shown in the figure. Figure 8 Four exemplary reference signals 804 are shown distributed in the first OFDM symbol. In other examples, more or fewer reference signals may be used, and the reference signals may be located in different positions than those in the first OFDM symbol. Figure 8 Among the REs shown in the diagram.

[0071] Several REG 802s can be grouped or mapped to several control channel elements (CCEs), which can be logically represented by their index numbers (see [link to documentation]). Figure 9 In some examples, nine REGs can be mapped to one CCE. The PDCCH can include any number of CCEs based on different aggregation levels, and the PDCCH can carry downlink control information (DCI) and / or other control messages. One or more CCEs can be assigned to the search space of one or more UEs or scheduled entities, and the UE can find its PDCCH in the assigned CCE.

[0072] The number of CCEs available for carrying the PDCCH can vary depending on the number of OFDM symbols used, the system bandwidth, and / or the number of antenna ports present at the scheduling entity. In some examples, coherent CCEs can be mapped to frequency-distributed (i.e., non-coherent) REGs. A coherent CCE can refer to a CCE that is coherently numbered or ordered in logical space. Two REGs are not coherent when they are not adjacent to each other (i.e., separated by one or more REs). This is called a distributed CCE-to-REG mapping. In some examples, coherent CCEs are mapped to frequency-contiguous REGs. This is called a localized CCE-to-REG mapping. For example, coherent or adjacent REGs are not separated by one or more REs.

[0073] The aggregation level (AL) of PDCCH transmission refers to the number of CCEs used for transmission. In some examples, AL1, AL2, AL4, and / or AL8 can be used to transmit PDCCH. For AL1, one CCE can be used to carry PDCCH. For AL2, two CCEs can be used to carry PDCCH. For AL4, four CCEs can be used to carry PDCCH. For AL8, eight CCEs can be used to carry PDCCH. Therefore, a higher AL can accommodate a larger payload or more bits in PDCCH transmission compared to a lower AL.

[0074] The search space (SS) refers to the resources within a time slot assigned or allocated to a UE for finding its PDCCH. That is, the search space includes a set of CCEs from which the UE can find its PDCCH. There are two types of search spaces: the shared search space (CSS) and the UE-specific search space (USS). The shared search space can carry shared downlink control information (DCI) broadcast to all UEs or a group of UEs, while the UE-specific search space can carry DCI specific to a particular UE. Each UE can monitor the PDCCH area of ​​the DL time slot (e.g., ...). Figure 5 The predefined search space in the control area 502).

[0075] Reference Figure 9 Different UEs (e.g., UE1, UE2, UE3) may have the same CSS 902 and different USS 904. For example, CSS 902 may include the first sixteen CCEs (e.g., CCE0 to CCE16) that are the same for all UEs. The USS of each UE may include CCEs that are different from the available CCEs, and the corresponding USS 904s of these UEs may overlap. That is, some CCEs may be included in multiple USS 904s. For example, CCE96 is included in the USS of UE1 and UE2, and CCE93 is included in the USS of UE2 and UE3.

[0076] Because 5G NR can support significantly wider bandwidth than current 3G / 4G networks, control resources (e.g., REs, CCEs) can be partitioned or clustered into different control resource sets. Each control resource set (CORESET) contains one or more search spaces as described above. CORESETs can be determined based on subbands or carriers so that UEs with limited bandwidth can be assigned to a suitable CORESET within the bandwidth that can be supported by that UE. In some examples, the control resources of a CORESET can reside in a subset of subband areas or carriers supported by the scheduling entity across the entire bandwidth. A CORESET can be a shared CORESET (C-CORESET) or a UE-specific CORESET (U-CORESET). The scheduling entity can configure a C-CORESET for all UEs and optionally configure one or more U-CORESETs for different UEs. A C-CORESET can include the CSS and USS of one or more UEs, and a U-CORESET can include the USS. CORESETs can be configured and reconfigured using Radio Resource Control (RRC) configuration or other semi-static procedures. For example, when UEs with different capabilities join and / or leave the network, C-CORESET can be reconfigured to other frequencies.

[0077] In some aspects of this disclosure, DL control area 502 (see...) Figure 5 Some control resources can be reused by the DL data section 504 to carry DL data. This may occur when the DL control region has more than enough resources to transmit DL control information (e.g., PDCCH) in a time slot.

[0078] Resources in the DL control area can be reused or reallocated to the DL data portion in two different ways. The time-domain-only method extends the DL data portion only in the time domain relative to the PDSCH. That is, the scheduling entity can notify the UE of the starting symbol position of its PDSCH in the time domain. For example, if the PDSCH was initially scheduled to start at symbol 3 in time slot, the extended PDSCH can start at symbol 1 or 2, which was initially scheduled for the DL control portion.

[0079] In another approach, the scheduling entity can notify the UE of the time and frequency locations of resources that can be reassigned to the DL data portion. This approach allows these resources to be identified independently of the PDSCH. For example, in the time domain, the scheduling entity can indicate only the start symbol location, or both the start and end symbol locations. In the frequency domain, the scheduling entity can indicate the start and end frequencies corresponding to the reassigned control resources or (e.g.) reused CCEs.

[0080] When control resources are reallocated for DL ​​data, the scheduling entity can configure the UE to rate match the PDSCH based on various rules to utilize additional resources. Rate matching functions by matching the number of bits in a transport block (TB) or cell with the number of bits that can be transmitted in a given allocation or resource. For example, rate matching can involve sub-block interleaving, bit collection, and culling.

[0081] In one aspect of this disclosure, a scheduling entity can configure a UE to rate match its PDSCH outside of a CORESET. In one example, the scheduling entity ensures that resource elements (REs) overlapping with other UEs' CORESETs are not configured or reallocated. The UE then rate matches its PDSCH around or outside of the C-CORESET and its own U-CORESET. In another example, the scheduling entity notifies the UE of other UEs' U-CORESETs, and the UE can then rate match its PDSCH around or outside of all the notified CORESETs.

[0082] In another aspect of this disclosure, the UE can rate match its PDSCH outside of the configured search space. In one example, the scheduling entity ensures that resource elements overlapping with the USS of other UEs are not configured or reallocated, and then the primary UE can rate match around or outside the CSS and its own USS. In the case where a wideband (WB) reference signal (RS) is used in the C-CORESET, the UE can rate match around all WB RS in the C-CORESET. In another example, the scheduling entity informs the UE about the USS of other UEs, and then the UE can rate match around or outside all the informed search spaces. In the case where a WB RS is used in the C-CORESET, the UE can rate match around all WB RS in the C-CORESET.

[0083] In another aspect of this disclosure, the UE can rate match its PDSCH around all decoded PDCCHs. In one example, the scheduling entity ensures that resource elements overlapping with the PDCCHs of other UEs are not configured. In the case where WB RS is used in C-CORESET, the UE can rate match around all WB RS in the C-CORESET.

[0084] In some aspects of this disclosure, the scheduling entity may transmit indicators in the DL control section to inform the UE how to use the reallocated control resources in the DL data section or PDSCH. For example, the scheduling entity may transmit indicators to provide predetermined or selected rules in the DCI or via RRC or other semi-static signaling. For example, the rule informs the UE how to rate match the PDSCH to utilize the reallocated control resources. The scheduling entity may also transmit indicators to provide predetermined or selected resource reuse types in the DCI or via RRC or other semi-static signaling. The resource reuse type may be the same as the time-domain-only extension of the PDSCH as described above, or the time-domain and frequency-domain extension independent of the PDSCH.

[0085] In some aspects of this disclosure, the scheduling entity can use multi-slot scheduling to configure control over resource reuse. In one example, the type of resource reuse for subsequent slots can be the same as the current slot, a different type for each slot (as specified in the DCI or RRC signaling), starting from the first symbol, or no reuse. The scheduling entity can configure the UE to rate match its PDSCH for subsequent slots based on various rules. For example, rate matching for subsequent slots can use the same rules as the current slot, different rules for each slot (as specified in the DCI or RRC signaling), and always apply conservative rules (as described above) to rate match outside of CORESET and / or SS.

[0086] Example rate matching behavior for clustered CORESET

[0087] In some respects, resources assigned to downlink data channels (e.g., PDSCH) may overlap (at least partially) with resources assigned to CORESET. In this context, for example, based on whether the resources assigned to CORESET are reusable, and to what extent they are reusable, the gNB may decide to rate match the PDSCH around the CORESET or to reuse (at least partially) the resources assigned to the CORESET for PDSCH. For example, if the CORESET is not assigned to control transmissions, or a limited portion of the CORESET (e.g., REs) is assigned to control transmissions, the gNB may decide to reuse the CORESET or its unused portions for PDSCH data transmissions. Alternatively, if most or all of the CORESET is assigned to control transmissions, the gNB may decide to rate match the PDSCH around the CORESET by assigning PDSCH data to resources around the CORESET without reusing the CORESET for PDSCH data.

[0088] In some respects, according to current 3GPP standards, a gNB typically indicates rate matching behavior, including whether to rate match PDSCH data around a specific CORESET, by including an indication of rate matching behavior as part of the DCI transmitted in the PDCCH. In one aspect, this indication generally includes a one-bit indication of whether a CORESET is reused for PDSCH data (i.e., whether PDSCH data is rate matched around a CORESET).

[0089] However, in some respects, multiple CORESETs can be configured for a UE (e.g., via multiple user-specific search spaces (USS) and / or multiple shared search spaces (CSS)). These CORESETs may include CORESETs assigned to one or more other UEs. In this context, a separate one-bit indicator may be needed to indicate rate matching behavior for each CORESET. Furthermore, it may be necessary to provide the UE with information about resource assignments for each CORESET (e.g., via RRC signaling) so that the UE can identify a specific CORESET and determine rate matching behavior for that specific CORESET. This can significantly increase system overhead.

[0090] This disclosure describes techniques for defining rate matching behavior associated with multiple CORESETs configured for a UE, without substantially increasing resource overhead.

[0091] In some respects, multiple CORESETs are clustered into a global resource set. The UE is configured with a global resource set (e.g., via RRC signaling). In one respect, no information is communicated to the UE regarding resource allocation for individual CORESETs, and the UE is not configured with a total resource allocation for the global resource set. Alternatively or additionally, instead of using separate bits to indicate rate matching behavior for each CORESET, a single bit indication (e.g., in DCI) is used to indicate rate matching behavior associated with the global resource set. In one respect, the single bit indicates whether the gNB has already rate-matched PDSCH data around the global resource set or whether resources (e.g., REs) of the global resource set have been used to schedule at least a portion of the PDSCH data.

[0092] In some respects, not communicating resource assignments for individual CORESETs to the UE and / or using a single DCI bit to provide rate matching information for a global resource set comprising multiple CORESETs reduces system overhead and improves system efficiency.

[0093] On the one hand, the UE can be configured with resource assignments for individual CORESETs in a global resource set, while still using a single DCI bit to convey rate matching behavior for the global resource set.

[0094] In one aspect, in addition to including one or more bundled cores, the global resource set may also include additional resources for signaling outside the scope of this disclosure. However, the global resource set includes at least the resources assigned to one or more cores configured for one or more UEs. In another aspect, the global resource set includes only the resources configured for one or more cores, without additional resources. In yet another aspect, it is not necessary to assign coherent time and / or frequency resources from the global resource set to bundled cores. Each bundled core may be assigned to a different non-coherent (e.g., in the time or frequency domain) portion of the global resource set.

[0095] Figure 10 Example operation 1000, performed by a base station (BS) (e.g., gNB) according to certain aspects of this disclosure, is described to determine rate matching behavior of multiple CORESETs.

[0096] At 1002, operation 1000 begins by clustering multiple CORESETs into a global resource set. At 1004, the BS (e.g., via RRC signaling) configures the global resource set for the UE. At 1006, the BS determines that the resources assigned to the downlink data channel (e.g., PDSCH) overlap with at least a portion of the global resource set. At 1008, the BS determines whether data on the downlink data channel should be rate-matched around the global resource set or use resources within the global resource set. At 1010, the BS transmits data on the downlink data channel based on the determined rate-matching behavior.

[0097] Figure 11 Example operation 1100, performed by the UE according to certain aspects of this disclosure, is described for determining rate matching behavior of multiple CORESETs.

[0098] At 1102, operation 1100 begins by receiving configuration information (e.g., via RRC signaling from the gNB) relating to a global resource set comprising multiple bundled CORESETs. At 1104, the UE determines that the resources assigned to the downlink data channel (e.g., PDSCH) overlap with at least a portion of the global resource set.

[0099] In step 1006, the UE determines whether data on the downlink data channel is rate-matched around a global resource set or uses resources within that global resource set. In one aspect, this determination can be based on semi-static configuration from the gNB (e.g., via RRC signaling) or explicit dynamic indications (e.g., DCI signaling).

[0100] In 1008, the UE receives data on the downlink data channel based on the determination of rate matching behavior. For example, if the UE determines that the PDSCH data is rate-matched around a global resource set, the UE does not process the global resource set for receiving PDSCH data. On the other hand, if the UE determines that at least a portion of the PDSCH data has been scheduled on resources of a resource set, the UE processes that resource set or a portion thereof to receive the PDSCH data.

[0101] On one hand, the gNB (e.g., via RRC signaling) uses resources assigned to the global resource set to configure the UE. This configuration does not include communicating information to the UE about the resources assigned to individual CORESETs clustered within the global resource set. As mentioned above, this reduces system overhead.

[0102] On one hand, multiple CORESETs clustered into a global resource set include one or more CORESETs assigned to different UEs. Additionally or alternatively, multiple CORESETs include at least one CORESET assigned to a UE, but which the UE cannot use for control channel monitoring at this time. For example, a CORESET configured for a UE may not be used in the active bandwidth portion.

[0103] On one hand, the gNB transmits an indication regarding whether the PDSCH data is rate-matched around the global resource set or uses resources within the global resource set. That is, the indication tells the UE whether resources in the global resource set are available for scheduling PDSCH data. The UE decides whether to monitor the global resource set to find PDSCH data based on this indication. For example, if the indication indicates that the PDSCH data is rate-matched around the global resource set, the UE does not process the global resource set for the PDSCH data. On the other hand, if the indication indicates that the PDSCH data uses at least a portion of the resources assigned to the global resource set, the UE processes the global resource set to receive the PDSCH data.

[0104] On one hand, the indication includes a one-bit indication of whether the PDSCH is rate-matched around the global resource set. For example, "0" indicates that the PDSCH data is rate-matched around the global resource set, and "1" indicates that at least a portion of the resources in the global resource set are reused for the PDSCH. Alternatively, "1" may indicate rate matching around the global resource set, and "0" may indicate that the global resource set is reused for the PDSCH.

[0105] On one hand, this instruction is transmitted by the gNB as part of the DCI in the PDCCH.

[0106] In some respects, when configuring a global resource set, the gNB can block a set of resources within the global resource set from being reused for data transmission (e.g., PDSCH data). Therefore, even if the gNB decides to reuse the global resource set for PDSCH, it can define exceptions to this reuse so that resources blocked in the global resource set are not reused for transmitting PDSCH data. For example, if a PDSCH transmitted as part of the UE's CORESET within the global resource set includes a one-bit indicator for rate matching behavior for reuse, rate matching of the PDSCH can be performed around the resources (e.g., REs) assigned to that PDSCH, while still reusing other parts of the global resource set for PDSCH. This ensures that the UE receives the indication for rate matching behavior and receives PDSCH data based on the received indication. In one aspect, PDSCH includes group-shared PDSCH (GC-PDCCH).

[0107] On the one hand, when the PDSCH is configured to reuse resources from the global resource set, the gNB avoids assigning those resources assigned to the PDCCH (e.g., GC-PDCCH) to the PDSCH. In this context, the UE does not process PDCCH resources for the PDSCH.

[0108] In some respects, because detailed resource information about each component CORESET in the global resource set is not transmitted to the UE, it may be difficult to block specific resources assigned within the global resource set.

[0109] On the one hand, PDCCH (e.g., GC-PDCCH) can always be scheduled at a fixed resource location within the global resource set (e.g., the first few symbols of the global resource set). Thus, the UE knows that it does not monitor PDSCH in these resources.

[0110] Several aspects of wireless communication networks have been described with reference to exemplary implementations. As will be readily apparent to those skilled in the art, the various aspects described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0111] As examples, these aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2 (3GPP2), such as CDMA2000 and / or Evolved Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0112] Within this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" need not be construed as superior to or better than other aspects of this disclosure. Similarly, the term "aspect" does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term "coupling" is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C can still be considered coupled to each other—even if they are not in direct physical contact. For example, a first object can be coupled to a second object, even if the first object never directly contacts the second object. The terms "circuit" and "circuit system" are used broadly and are intended to include both hardware implementations of electronic devices and conductors, and software implementations of information and instructions, which, when connected and configured, enable the performance of the functions described in this disclosure, without limitation on the type of electronic circuit, and which, when executed by a processor, enable the performance of the functions described in this disclosure.

[0113] Figure 1-11 One or more of the components, steps, features, and / or functions described herein may be rearranged and / or combined into a single component, step, feature, or function, or may be implemented in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1-11 The apparatus, devices, and / or components described herein can be configured to perform one or more methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0114] It should be understood that the specific order or hierarchy of the steps in the disclosed methods is an explanation of an exemplary process. Based on design preferences, it should be understood that the specific order or hierarchy of the steps in these methods can be rearranged. The appended method claims present the elements of various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented, unless specifically stated herein.

[0115] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by those skilled in the art, and the universal principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element are not intended to mean “one and only one”—unless specifically stated otherwise—but are intended to mean “one or more.” Unless specifically stated otherwise, the term “a” refers to one or more. The phrase “at least one of” referring to a list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the various aspects described throughout this disclosure that are currently or hereafter known to a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. No element of a claim shall be construed under the provisions of 35 U.S.SC §112(f) unless the element is expressly described using the phrase “means for…” or, in the case of a method claim, the element is described using the phrase “steps for…”.

Claims

1. A network element for wireless communication, comprising: Memory including computer-executable instructions; as well as One or more processors, the one or more processors being configured to execute the computer-executable instructions and cause the network element to: Cluster multiple control resource sets (CORESET) into a global resource set; Configure the global resource set for the user equipment (UE); Determine whether data on the downlink data channel should be rate-matched around the global resource set or use resources in the global resource set; Based on the determination regarding whether the data on the downlink data channel should be rate-matched around the global resource set or whether resources in the global resource set should be used to transmit the data on the downlink data channel; as well as A one-bit indication of whether the data transmitted on the downlink data channel is to be rate-matched around the global resource set or to use resources in the global resource set.

2. The network element of claim 1, wherein, In order to configure the global resource set for the user equipment (UE), the one or more processors are further configured to cause the network element to transmit information related to the resources assigned to the global resource set to the user equipment.

3. The network element of claim 1, wherein, In order to configure the global resource set for the user equipment (UE), the one or more processors are further configured to cause the network element to suppress the transmission of information relating to resources assigned to individual CORESETs from the plurality of CORESETs.

4. The network element of claim 1, wherein, The one or more processors are further configured to cause the network element to determine that the resources assigned to the downlink data channel overlap with at least a portion of the global resource set.

5. The network element of claim 1, wherein, The one or more processors are further configured to cause the network element to transmit the indication in downlink control information in the Physical Downlink Control Channel (PDCCH).

6. The network element as claimed in claim 5, wherein: The downlink data channel is configured to use the resources in the global resource set; and The one or more processors are further configured to prevent the network element from assigning resources to the PDCCH to the downlink data channel.

7. The network element of claim 5, wherein, The PDCCH includes the group-shared PDCCH (GC-PDCCH).

8. The network element of claim 1, wherein, The plurality of CORESETs includes at least one CORESET assigned to different user equipment or said user equipment is temporarily unavailable.

9. The network element of claim 1, wherein, The downlink data channel includes the Physical Downlink Shared Channel (PDSCH).

10. A user equipment for wireless communication, comprising: Memory including computer-executable instructions; as well as One or more processors, the one or more processors being configured to execute the computer-executable instructions and equip the user: Receive configuration information relating to a global resource set that includes multiple bundled control resource sets (CORESET); Determine whether data on the downlink data channel is rate-matched around the global resource set or uses resources within the global resource set; Based on the determination regarding whether the data on the downlink data channel should be received by rate matching around the global resource set or by using resources in the global resource set; as well as Receive a one-bit indication of whether the data on the downlink data channel should be rate matched around the global resource set or whether resources in the global resource set should be used.

11. The user equipment of claim 10, wherein, The configuration includes information relating to the resources assigned to the global resource set.

12. The user equipment of claim 11, wherein, The configuration does not include information relating to resources assigned to individual CORESETs from the bundled CORESETs.

13. The user equipment of claim 10, wherein, The one or more processors are further configured to cause the user equipment to determine that the resources assigned to the downlink data channel overlap with at least a portion of the global resource set.

14. The user equipment of claim 10, wherein, The one or more processors are configured to enable the user equipment to receive the indication in downlink control information in the physical downlink control channel (PDCCH).

15. The user equipment as claimed in claim 14, wherein: The instruction indicates that the downlink data channel is configured to use the resources in the global resource set; and The one or more processors are further configured to enable the user equipment to monitor the resources assigned to the PDCCH for receiving the data suppression on the downlink data channel.

16. The user equipment of claim 14, wherein, The PDCCH includes the group-shared PDCCH (GC-PDCCH).

17. The user equipment of claim 10, wherein, The clustered CORESET includes at least one CORESET assigned to different user equipment or where the user equipment is temporarily unavailable.

18. The user equipment of claim 10, wherein, The downlink data channel includes the Physical Downlink Shared Channel (PDSCH).

Images