CORESET frequency resource configuration for wideband operation in NR-U

By adjusting the configuration of CORESET and RB sets in NR-U broadband operation, the problem of CORESET resource allocation mismatch between the size of the RB set is solved, the PDCCH monitoring protocol is improved, the efficiency of channel sensing and data transmission is improved, and the NR is solved -The problem of low channel resource utilization efficiency under the U spectrum.

CN113497699BActive Publication Date: 2024-11-19SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110361230.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-09-22
Filing Date
2021-04-02
Publication Date
2024-11-19
Estimated Expiration
2041-04-02

AI Technical Summary

Technical Problem

In NR-U broadband operation, the problem of CORESET resource allocation and RB set misalignment due to the changing RB set size, which causes the UE to face the problem of mismatch in frequency and time domain resource configuration when monitoring downlink control signals, affecting the channel The efficiency of sensing and data transmission.

Method used

By determining the CORESET configuration and searching for the space set configuration, the CORESET resources in the frequency domain monitoring timing are identified, and the PDCCH monitoring protocol is adjusted, so that the CORESET resources are only partially limited to the first RB set, and the CORESET that is not in the RB set is ignored or modified Resource allocation to ensure that resource configuration is suitable for RB set configuration.

Benefits of technology

The performance of CORESET resources is improved, information loss and decoding performance degradation caused by punching PDCCH candidates is avoided, and the transmission efficiency and reliability of UEs under the NR-U spectrum is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113497699B_ABST
    Figure CN113497699B_ABST
Patent Text Reader

Abstract

A network communication method is provided for solving the problem that CORESET resource allocation is not aligned with a first RB set due to a changing RB set size, the method comprising: determining a CORESET configuration, a search space set configuration and / or an RB set configuration; determining that the search space set includes a plurality of frequency domain monitoring opportunities; identifying a CORESET resource in each of the frequency domain monitoring opportunities; determining that the CORESET resource is only partially confined to the first RB set; and adjusting a PDCCH monitoring protocol to improve the performance of the CORESET resource.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 004941, filed on April 3, 2020, entitled “CORSET FREQUENCY RESOURCE CONFIGURATION FOR WIDE-BAND OPERATION IN NR-U,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] Various aspects of some embodiments of the present disclosure relate to network communications and methods of monitoring downlink control signaling. Background Art

[0004] A base station (e.g., an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) Node B, also referred to as an evolved Node B or eNodeB) can communicate with multiple UEs at any given point in time. That is, a base station can function as hardware connected to a mobile phone network that communicates directly wirelessly with mobile handsets (e.g., user equipment, also referred to as UE) or transceivers within the network.

[0005] A base station can communicate with multiple UEs, although it should be noted that high communication traffic may potentially degrade UE performance. In order for a base station to handle multiple communications by multiple UEs, various configurations may be made to the UEs to communicate with the base station in a manner that avoids interfering with communications with other UEs.

[0006] For example, the UE may monitor signaling from the base station (e.g., a downlink control signal containing downlink control information (DCI)). That is, the UE may be configured in the time domain (e.g., may have a search space set configuration) and in the frequency domain (e.g., may have a control resource set (CORESET) configuration). Accordingly, multiple UEs may monitor a physical downlink control channel (PDCCH) in a serving cell including the base station at various times in the time domain while operating using various frequencies / bands in the frequency domain.

[0007] A CORESET is a set of time / frequency resources on which a PDCCH can be transmitted to a corresponding UE. A CORESET may be semi-statically configured by a network connected to a base station. Furthermore, there may be many CORESETs in a single carrier corresponding to a UE, and each CORESET may appear anywhere in a given time slot and within the frequency range of that carrier. However, a CORESET may generally have a maximum length of three (3) symbols.

[0008] Accordingly, CORESET indicates the time that the corresponding UE can reserve to search for control information from the base station. By using both the search space set configuration and the CORESET configuration, the UE can know what frequency or frequency band to use in monitoring the downlink control signal and at what point in time to monitor the downlink control signal. Summary of the invention

[0009] Various aspects of embodiments of the present disclosure relate to network communications and provide improvements to wideband operations within New Radio Unlicensed Spectrum (NR-U).

[0010] According to some embodiments of the present disclosure, a network communication method is provided for solving the problem that CORESET resource allocation is not aligned with a first RB set due to a changing RB set size, the method comprising: determining a CORESET configuration, a search space set configuration and / or an RB set configuration; determining that the search space set includes multiple frequency domain monitoring opportunities; identifying a CORESET resource in each of these frequency domain monitoring opportunities; determining that the CORESET resource is only partially confined to the first RB set; and adjusting a PDCCH monitoring protocol to improve the performance of the CORESET resource.

[0011] The CORESET resources in each of these frequency-domain monitoring opportunities may be based on the size of the zeroth RB set.

[0012] The method may further include: determining a CORESET configuration and / or an RB set configuration; and determining that there are no new restrictions on the CORESET configuration and / or the RB set configuration.

[0013] Adjusting the PDCCH monitoring protocol may include ignoring PDCCH candidates of the CORESET resources that are only partially confined to the first RB set.

[0014] Adjusting the PDCCH monitoring protocol may include rate matching PDCCH candidates of the CORESET resources, the PDCCH candidates being only partially confined to the first RB set.

[0015] Adjusting the PDCCH monitoring protocol may include modifying the CORESET resources to be within the first RB set.

[0016] Adjusting the PDCCH monitoring protocol may include ignoring CORESET resource allocations that are not within an RB set.

[0017] The method may further include: determining a CORESET configuration and a RB set configuration; and ensuring that the CORESET configuration is applicable to the RB set configuration.

[0018] According to other embodiments of the present disclosure, a communication device for executing a network communication method is provided, wherein the network communication method is used to solve the problem that CORESET resource allocation is not aligned with a first RB set due to a changing RB set size, and the communication device is configured to: determine a CORESET configuration, a search space set configuration, and / or an RB set configuration; determine that the search space set includes multiple frequency domain monitoring opportunities; identify a CORESET resource in each of these frequency domain monitoring opportunities; determine that the CORESET resource is only partially confined to the first RB set; and adjust a PDCCH monitoring protocol to improve the performance of the CORESET resource.

[0019] The CORESET resources in each of these frequency-domain monitoring opportunities may be based on the size of the zeroth RB set.

[0020] The communications device may be further configured to: determine a CORESET configuration and / or a RB set configuration; and determine that there are no new restrictions on the CORESET configuration and / or the RB set configuration.

[0021] The communications device may be configured to adapt the PDCCH monitoring protocol by ignoring PDCCH candidates of the CORESET resources, the PDCCH candidates being only partially confined to the first set of RBs.

[0022] The communications device may be configured to adapt a PDCCH monitoring protocol by rate matching PDCCH candidates of the CORESET resources, the PDCCH candidates being only partially confined to the first set of RBs.

[0023] The communications device may be configured to adjust the PDCCH monitoring protocol by modifying the CORESET resources to be within the first RB set.

[0024] The communications device is configured to adapt a PDCCH monitoring protocol by ignoring CORESET resource allocations that are not within an RB set.

[0025] The communications device may be further configured to: determine a CORESET configuration and a RB set configuration; and ensure that the CORESET configuration is applicable to the RB set configuration.

[0026] According to other embodiments of the present disclosure, a non-transitory computer-readable medium implemented in combination with a user equipment for communicating with a base station is provided, the non-transitory computer-readable medium having a computer code, and the computer code, when executed on a processor, implements a network communication method, the network communication method being used to solve the problem that CORESET resource allocation is not aligned with a first RB set due to a changing RB set size, the method comprising: determining a CORESET configuration, a search space set configuration and / or an RB set configuration; determining that the search space set includes a plurality of frequency domain monitoring opportunities; identifying a CORESET resource in each of these frequency domain monitoring opportunities; determining that the CORESET resource is only partially confined to the first RB set; and adjusting a PDCCH monitoring protocol to improve the performance of the CORESET resource.

[0027] The CORESET resources in each of these frequency-domain monitoring opportunities may be based on the size of the zeroth RB set.

[0028] The computer code, when executed on a processor, may further implement the method by: determining a CORESET configuration and / or a RB set configuration; and determining that there are no new restrictions on the CORESET configuration and / or the RB set configuration.

[0029] The computer code, when executed on a processor, may further implement the method by: determining a CORESET configuration and a RB set configuration; and ensuring that the CORESET configuration is applicable to the RB set configuration.

[0030] Accordingly, embodiments of the present disclosure provide improvements to wideband operation within NR-U by providing improved methods for manipulating CORESET resource allocations or PDCCH candidates for the CORESET resource allocations that are not completely within a single RB set. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Non-limiting and non-exhaustive embodiments of the described embodiments will be described with reference to the following figures, wherein like parts are referred to by like reference numerals throughout the various views unless otherwise specified.

[0032] Figure 1 is a block diagram illustrating an example of a CORESET resource allocation problem that may occur when different RB sets have different sizes, according to some embodiments of the present disclosure.

[0033] Figure 2 is a block diagram depicting an example of punctured PDCCH candidates when RB sets have different sizes, wherein the punctured PDCCH candidates may be ignored, according to some embodiments of the present disclosure.

[0034] Figure 3is a block diagram depicting an example of rate matching PDCCH candidates when RB sets have different sizes according to some embodiments of the present disclosure;

[0035] Figure 4 is a block diagram depicting an example of adjusting CORESET resource configuration when RB sets have different sizes according to some embodiments of the present disclosure; and

[0036] Figure 5 is a flow chart depicting a method of network communications according to some embodiments of the present disclosure.

[0037] The corresponding components are always indicated by corresponding reference numerals in the several illustrations of these drawings. Those skilled in the art will recognize that the elements in the drawings are illustrated for simplicity and clarity and are not necessarily drawn to scale. For example, the sizes of certain elements, layers, and regions in the drawings may be exaggerated relative to other elements, layers, and regions to help improve clarity and enhance understanding of the various embodiments. Moreover, common and well-understood elements and parts that are not relevant to the description of the embodiments may not be shown to help provide a reduced obstruction view for these various embodiments and make the description clear. DETAILED DESCRIPTION

[0038] By referring to the detailed description of the embodiments and the accompanying drawings, it is easier to understand the features of the principles of the present invention and the methods for realizing them. Hereinafter, the embodiments will be described in more detail with reference to the accompanying drawings. However, the described embodiments may be embodied in various different forms and should not be understood as being limited to the embodiments illustrated in the text. On the contrary, these embodiments are provided as examples so that the disclosure is thorough and complete, and the various aspects and features of the principles of the present invention will be fully conveyed to those skilled in the art. Accordingly, those processes, elements and technologies that are not necessary for those skilled in the art to thoroughly understand the various aspects and features of the present invention may not be described.

[0039] Unless otherwise noted, similar numbers, letters or combinations thereof are shown throughout the drawings and text descriptions to represent similar elements, and thus descriptions thereof will not be repeated. In addition, for the sake of clarity of description, parts that are not related to the description of the embodiments may not be shown. In the accompanying drawings, the relative sizes of elements, layers and regions may be exaggerated for the sake of clarity. In addition, the use of cross hatching and / or shadows in the accompanying drawings is generally provided for the sake of clarity of the boundaries between adjacent elements. As such, the presence or absence of cross hatching or shadows cannot convey or indicate that any particular material, material properties, size, ratio, commonality between illustrative elements and / or any other characteristics, attributes, characteristics, etc. of the elements are preferred or required, unless otherwise specified.

[0040] In the detailed description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. However, it is apparent that the various embodiments can be practiced without these specific details or with the aid of one or more equivalent arrangements.

[0041] It should be understood that although the words "zeroth", "first", "second", "third" and the like may be used herein to describe various elements, components, regions, layers and / or sections, these elements, components, regions, layers and / or sections should not be limited by these terms. These terms are only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section. Thus, the first element, component, region, layer or section discussed below may be referred to as the second element, component, region, layer or section without departing from the essence and scope of the present disclosure.

[0042] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the words "include", "comprise", "have" and "contain" when used in this specification specify the presence of stated features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. As used herein, the term "and / or" includes any and all combinations of one or more of the associated enumerated items.

[0043] As used herein, the words "substantially", "approximately", "approximately" and similar words are used as approximate words, rather than being related to degree, and are intended to illustrate the inherent deviations in measured or calculated values ​​that can be recognized by those skilled in the art. As used herein, "approximately" and "approximately" include the stated value and mean to be within an acceptable deviation range for that particular value, which can be determined by those skilled in the art taking into account the measurement in question and the errors associated with the measurement of the particular quantity (i.e., the limitations of the measurement system). For example, "approximately" can mean within one or more standard deviations, or within ±30%, 20%, 10%, 5% of the stated value. In addition, when describing embodiments of the present disclosure, the use of "may" relates to "one or more embodiments of the present disclosure".

[0044] When one or more embodiments can be implemented differently, the specific process order can be performed differently than the described order. For example, two processes described in connection can be performed substantially simultaneously or in an order opposite to the described order.

[0045] Any suitable hardware, firmware (e.g., an application specific integrated circuit), software, or a combination of software, firmware, and hardware may be used to implement the electronic or electronic devices and / or any other related devices or components according to the embodiments of the present disclosure described herein. For example, the various components of these devices may be formed onto an integrated circuit (IC) chip or onto a separate IC chip. In addition, the various components of these devices may be implemented onto a flexible printed circuit film, a tape carrier package (TCP), a printed circuit board (PCB), or may be formed on a substrate.

[0046] In addition, the various components of these devices can be processes or threads that run on one or more processors in one or more computing devices to execute computer program instructions and interact with other system components to perform the various functions described herein. Computer program instructions are stored in memory, which can be implemented in a computing device using a standard storage device (e.g., a random access memory (RAM)). Computer program instructions can also be stored in other non-transitory computer-readable media, such as a CD-ROM or a flash drive. Moreover, it should be appreciated by those skilled in the art that the functions of various computing devices can be combined or integrated into a single computing device, or the functions of a particular computing device can be distributed across one or more computing devices without departing from the essence and scope of the embodiments of the present disclosure.

[0047] Unless otherwise defined, all terms (including technical terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the principles of the present invention belong. It should be further understood that words such as those defined in commonly used dictionaries should be interpreted as having the same meaning as they have in the context of the relevant art and / or this specification, and should not be interpreted according to an idealized or overly rigid meaning, unless so defined in the text.

[0048] As mentioned above, a search space set configuration and a control resource set (CORESET) configuration may be provided for a user equipment (UE) so that the UE can monitor downlink control information (DCI) in a physical downlink control channel (PDCCH) from a base station (eg, eNodeB) in a serving cell.

[0049] The search space set configuration enables the UE to perform PDCCH monitoring for timing information in the time domain (e.g., enables the UE to know when it should monitor DCI). The CORESET configuration provides information that enables the UE to perform PDCCH monitoring in the frequency domain (e.g., enables the UE to know what frequency / band it should use to monitor DCI).

[0050] Accordingly, the search space set configuration provides PDCCH monitoring of opportunity information in the time domain, and each PDCCH monitoring opportunity is associated with a CORESET configuration associated with the search space set configuration.

[0051] The CORESET configuration may provide a set of resource blocks (RBs) and may also provide a symbol duration for monitoring PDCCH candidates. For example, the CORESET frequency domain resources may be indicated by a bitmap in the frequency domain. The bits in the bitmap may have a one-to-one mapping relationship with each contiguous non-overlapping RB group within the bandwidth of a downlink (DL) bandwidth part (BWP). Each RB group may have six (6) physical resource blocks (PRBs).

[0052] Accordingly, by receiving information in the form of a CORESET configuration from the base station, the UE does not have to monitor the entire corresponding bandwidth (for example, it does not have to monitor the entire bandwidth of the New Radio Unlicensed Spectrum (NR-U)), but instead can monitor only a portion thereof (for example, it can only monitor the corresponding BWP that can be determined by the CORESET configuration).

[0053] When no offset configured by the base station is provided (e.g., RB-Offset-r16, "r16" refers to the Release 16 standard, and "RB-Offset-r16" refers to the existing Release 16 radio resource control (RRC) parameters), the first group of six (6) physical resource blocks (PRBs) within the DL BWP corresponding to the first bit in the bitmap may start at the common RB index However, when providing a public RB index ( is provided by RB-Offset-r16), the first bit corresponds to (In the provision hour), may correspond to the first common BR index of the DL BWP, and RB-Offset-r16 may be an offset configured by the base station for communicating with the UE.

[0054] In addition, the PDCCH candidates within the CORESET resource allocation may include a set of control channel elements (CCE) depending on the corresponding aggregation level. The CCE may include six (6) resource element groups (REGs). Each REG may be a group of twelve (12) consecutive resource elements (REs). Accordingly, the UE may monitor the RE set of PDCCH candidates located in the corresponding time domain and frequency domain based on the CORESET configuration and the search space set configuration.

[0055] However, for UEs operating in NR-U (NR-U is an unlicensed spectrum in which Wi-Fi and others can operate, making coordination with various UEs more complicated), a carrier bandwidth portion (BWP) larger than the sub-band bandwidth used for single channel sensing may not be fully utilized for transmission due to unpredictable channel sensing results. Since the BWP in NR-U is relatively large, when performing channel sensing, the UE may segment the relative BWP (e.g., having a bandwidth of approximately 80 MHz) into various units or segments (e.g., into four 20 MHz segments), where one or more of these segments are unavailable or occupied. For example, if the BWP is large, it may not be fully utilized for transmission.

[0056] Accordingly, UEs seeking to transmit information may face increased difficulties in NR-U. For example, since there may be multiple UEs, it may not be guaranteed that the UE can transmit at every expected time. Therefore, each UE may perform channel sensing to determine whether a given channel is idle. When the channel is idle, the UE may transmit information to the base station.

[0057] RBs available for transmission in one subband bandwidth (a unit for channel sensing) may be referred to as an RB set, and each RB set within a BWP may be identified by an index starting at 0. Accordingly, all available resources may be encoded into the subband bandwidth as RB sets.

[0058] Furthermore, the UE may not be required to monitor a PDCCH overlapping with any RB from an RB set indicated as an unusable RB set by a received downlink control information (DCI) format (eg, DCI 2_0).

[0059] When there are several RB sets (e.g., when there are several monitoring positions), the CORESET resources may be configured to be within each RB set. As mentioned above, a bitmap may be used for each RB set. For the features of multiple frequency domain monitoring positions, in order to simplify the configuration of the CORESET, the CORESET frequency domain resource bitmap may be reinterpreted. For example, the CORESET frequency domain may be represented by a bitmap having a one-to-one mapping relationship for six (6) consecutive RBs. Accordingly, the UE may avoid monitoring the entire bandwidth and may monitor only the relevant BWP.

[0060] For example, the CORESET frequency domain resource allocation can be determined by the first number of bits in the frequency resource bitmap. Determine, among which, in, The number of available RBs in RB set 0 (e.g., the zeroth / 0th RB set) corresponding to the BWP, and wherein, is provided by the higher layer parameter RB-offset, or when RB-offset is not provided,

[0061] For the zeroth RB set, each bit of the frequency resource bitmap has a one-to-one mapping relationship with each non-overlapping group of six (6) consecutive RBs, which follows the ascending order of the RB index in the downlink (DL) BWP, where the starting / starting common RB index is The first common RB of the first group of six (6) RBs has a common RB index

[0062] If the base station allocates a CORESET configuration to the UE, the UE can understand the frequency range. As described above, the frequency range in the frequency domain can be mapped to an RB index, where the first bit of the CORESET configuration bitmap can be mapped to a PRB index, where Indicates the starting point (the lowest available frequency associated with the CORESET configuration).

[0063] That is, the first bit corresponding to the number of available RBs in the RB set may be used. The CORESET resource allocation may be determined by associating a first bit to six (6) RBs including a first RB to be set as a common RB. The six (6) RBs may have indices at frequency domain monitoring locations limited to a set of RBs (e.g., RB set k). in, is the index of the first RB of RB set k.

[0064] Figure 1 is a block diagram illustrating an example of a CORESET resource allocation problem that may occur when different RB sets have different sizes, according to some embodiments of the present disclosure.

[0065] refer to Figure 1 For a CORESET spanning multiple RB sets (eg, RB set 0 / zeroth RB set 110 and RB set 1 / first RB set 111), there may be one or more PDCCH candidates not limited to a single RB set. That is, one or more PDCCH candidates may span several RB sets.

[0066] Similar CORESET frequency domain resource allocations may be applied to multiple RB sets. For example, the UE may copy common CORESET resources (e.g., CORESET resource allocations 130, 131) to different RB sets 110, 111. However, although the CORESET may occupy the entire zeroth RB set 110, the first RB set 111 may be smaller than the zeroth RB set 110, such that the CORESET resource allocation 131 may not be completely within the first RB set 111. In addition, not all RB sets may be available for use.

[0067] Accordingly, it may be useful to puncture the PDCCH candidate (e.g., truncate or erase portions of the PDCCH candidate). The UE may detect a punctured PDCCH candidate when any of the associated RB sets is not available from the channel sensing results. However, it may not be desirable for the UE to use a punctured PDCCH from a PDCCH decoding performance perspective because information loss may have occurred during data transmission. For example, the UE may not understand which particular portion of the PDCCH was erased, which may adversely affect decoding.

[0068] Multiple frequency domain monitoring positions of CORESET can be included in the search space set configuration so that each CORESET monitoring position in the frequency domain is associated with a CORESET in the RB set for wideband operation, thereby solving the problem caused by puncturing PDCCH. Accordingly, PDCCH candidates can be completely detected in a single RB set, provided that the associated sensing of the channel is successful and the RB set is available.

[0069] Due to the size and index of the RB set Due to the configurability of the part, the number of available RBs in the zeroth / 0th RB set (e.g., RB set 0) 110 may be different from the number of available RBs in other RB sets (e.g., RB set 1 / first RB set 111). As an example, the first RB set 111 may include 52 RBs and may be separated from the zeroth RB set including 54 RBs by a guard band 120 having a size of four (4) RBs.

[0070] Therefore, in the first bit based on the frequency resource bitmap When determining CORESET resources, CORESET resource allocation 131 for the first RB set 111 (and other RB sets except the zeroth RB set 110) may not be confined within the first RB set 111, although the CORESET resource allocation 130 for the zeroth RB set 110 is completely confined thereto.

[0071] For example, if the i-th RB set (eg, RB set i) such as the first RB set 111 has much fewer RBs than the zero-th RB set 110 due to its configuration, then the first bit corresponding to the frequency resource bitmap The CORESET resources of the first RB set 111 (e.g., the CORESET resource allocation 131 of the first RB set 111) may exceed the i-th RB set. The manner in which the UE will interpret the portion of the CORESET resource allocation that is not limited to the i-th RB set (e.g., the manner in which the UE will interpret the portion 141 of the CORESET resource allocation 131 that is not limited to the first RB set 111) is generally not specified.

[0072] Accordingly, as described below Figure 2-4 Provides a method for handling the above contact Figure 1 Describe the various methods of the program.

[0073] Figure 2 is a block diagram depicting an example of punctured PDCCH candidates when RB sets have different sizes, wherein the punctured PDCCH candidates may be ignored, according to some embodiments of the present disclosure.

[0074] refer to Figure 2 , in order to solve the above connection Figure 1 To summarize the problem, the UE can follow the same PDCCH monitoring procedure based on the PDCCH monitoring configuration, regardless of whether the monitored PDCCH candidates are (completely) within a given RB set.

[0075] Therefore, the UE may detect a punctured PDCCH candidate when any portion of the PDCCH candidate is not within the corresponding RB set. For example, the UE may detect a punctured PDCCH candidate 251 that includes both a portion 262 included in the first RB set 111 and a portion 261 not included in the first RB set 111. Other non-punctured PDCCH candidates 252, 253, 254 may be found within their corresponding RB sets 110, 111.

[0076] As described above, the use of punctured PDCCH candidates 251 may improve the performance of a PDCCH decoding operation. Accordingly, according to some embodiments of the present disclosure, the UE may determine a mapping of PDCCH candidates corresponding to a configured RB set. The PDCCH candidate mapping may be based on a first number of bits of a frequency resource bitmap provided by a CORESET configuration.

[0077] The UE may ignore PDCCH candidates (e.g., PDCCH candidate 251) that do not completely overlap with the RB set due to RB set size misalignment. In this case, the PDCCH candidate mapping may be the same in all RB sets 110, 111, but the number of PDCCH candidates processed by the UE in each RB set may be different. For example, the UE may only process PDCCH candidates 252, 253, and 254.

[0078] However, alternatively, the UE may instead ignore all (including non-punctured PDCCH candidates 252) of the CORESET resource allocation 131 containing the punctured PDCCH candidate 251, while only processing the PDCCH candidates 253, 254 of the CORESET resource allocation 130 that does not contain the punctured PDCCH candidate. That is, a simpler UE behavior may completely ignore any CORESET resource allocation that is not limited to an RB set, and instead may only monitor RB sets whose allocated CORESET resource configurations completely overlap with the corresponding RB set.

[0079] Figure 3 is a block diagram illustrating an example of rate matching PDCCH candidates when RB sets have different sizes according to some embodiments of the present disclosure.

[0080] refer to Figure 3 In order to maintain the same number of PDCCH candidates in each of the RB sets and to avoid puncturing the PDCCH candidates, the base station may perform rate matching so that the PDCCH candidates that would otherwise be punctured (e.g., Figure 2The PDCCH candidate 251 of FIG. 1 is reduced in size, but still completely within the corresponding RB set (e.g., PDCCH candidate 362 is within the first RB set 111). Rate matching can achieve slightly improved performance compared to puncturing the PDCCH candidates because the UE may not have to deal with as much noise / interference.

[0081] It should be noted that when the base station wants to transmit some information (e.g., upload a file), the transmission process may incur some noise. Accordingly, the base station may not blindly transmit the data corresponding to the file without taking any protection to avoid data corruption, because the file received by the receiver may have some noise. In order to avoid possible data corruption, the base station may not simply transmit the file alone, but may add some redundancy to the information contained in the file to reduce the impact that would otherwise be caused by noise. Accordingly, the content transmitted by the base station may be larger than the file size. For example, if the coding rate is relatively very low (e.g., 1 / 10), the base station may transmit a real value of 10mb of data for a 1mb file. At the same time, it should be noted that a large coding rate provides less protection against noise. Accordingly, an appropriate approach may be to use resources (e.g., RBs) as much as possible to prevent the coding rate from being too low.

[0082] Accordingly, a UE that knows that the base station is capable of performing rate matching can perform decoding and can decode the entire PDCCH candidate 362, although the coding rate may be relatively high. The UE can select the first bit of the frequency resource bitmap provided by the CORESET configuration. Determine the mapping of PDCCH candidates in the configured RB set. Accordingly, if any of these resources are not in the RB set, the UE can rate match the PDCCH candidates.

[0083] Figure 4 is a block diagram illustrating an example of adjusting CORESET resource configuration when RB sets have different sizes according to some embodiments of the present disclosure.

[0084] refer to Figure 4 According to an embodiment of the present disclosure, it is possible to enable the UE to ignore the portion of the CORESET resource allocation that is not confined to the RB set (e.g., the UE may ignore Figure 2 The problem caused by the presence of punctured PDCCH candidates is solved by using the punctured portion 261 shown in FIG. 1 . That is, the UE can use CORESET resource allocations 431, 130 with different sizes. Within the smaller CORESET resource allocation 431, the positions of the PDCCH candidates 451, 252 can be redefined (e.g., from Figure 2PDCCH candidates 251, 251 shown in FIG.

[0085] That is, the UE may ignore the resource allocation corresponding to the CORESET 131 (eg Figure 2 261 of the punctured PDCCH candidate 251). Therefore, the UE can detect two non-punctured PDCCH candidates 451 and 252 within the first RB set 111. It should be noted that by ignoring the punctured portion 261 of the PDCCH candidate 251 and by identifying the non-punctured PDCCH candidate 451 instead, Figure 4 The CORESET resource allocation of 431 is less than Figure 2 CORESET resource allocation 231. It should be noted that Figure 4 The PDCCH candidates 451 and 252 of the first RB set 111 have RBs located therebetween. Figure 2 The first RB set 111 has fewer PDCCH candidates 251 and 252 .

[0086] Accordingly, in those other RB sets (eg, the first RB set 111 ) having fewer RBs than the zeroth RB set 110 , the CORESET resource allocation may be different, and the associated PDCCH candidate mapping may be changed accordingly.

[0087] It should be noted that in other embodiments, the network configuration can be used to avoid puncturing PDCCH candidates, thereby ensuring the front of the frequency resource bitmap. The bit may be applied to all RB sets. For example, all RB sets may have the same available RBs, or the zeroth RB set may have the lowest number of RBs among all RB sets, so that establishing the size of the CORESET resource allocation based on the size of the zeroth RB set will ensure that a copy of the CORESET resource allocation fits perfectly into any RB set, because the CORESET resource allocation is small enough to fit into all RB sets of varying sizes, which may be adopted in the 5G standard. That is, if a UE is provided with an RB set within a DL BWP, the UE can manipulate the RBs of the CORESET as if they are within the union of the PRBs in the RB set of the DL BWP. Accordingly, although the complexity of the UE implementation is not affected, the base station configuration flexibility is compromised due to the CORESET configuration restrictions or RB set configuration restrictions. Such an embodiment may introduce new UE behaviors with respect to PDCCH monitoring and PDCCH processing, and the potential UE implementation complexity may need to be considered accordingly.

[0088] Figure 5 is a flow chart depicting a method of network communications according to some embodiments of the present disclosure.

[0089] refer to Figure 5 In S501, the UE may receive (from a base station) a CORESET configuration and a search space set configuration.

[0090] In S502, the UE may receive (eg, from a base station) an RB set configuration (if one is available), or may apply a default RB set configuration.

[0091] In S503, the UE may determine by checking whether the search space set configuration includes multiple frequency domain monitoring opportunities.

[0092] If not (None), then in S504, the UE may operate according to a previously decided protocol (eg, Rel-15), and may monitor the PDCCH based on the received CORESET configuration and search space set configuration.

[0093] If it is determined in S503 that the search space set includes a plurality of frequency domain monitoring opportunities (yes), then in S505, the UE may determine the CORESET resources in each of the frequency domain monitoring opportunities based on the size of the zeroth RB set.

[0094] In S506, the UE may determine that new restrictions on CORESET configuration and / or RB set configuration are applicable, and may monitor PDCCH based on CORESET configuration and search space set configuration according to the new restrictions. For example, the base station may ensure that the CORESET resource configuration is applicable to all configured RB sets.

[0095] Otherwise, if no new restrictions on CORESET configuration and / or RB set configuration are applicable (otherwise), then in S507, the UE may determine whether the CORESET is restricted to any RB set.

[0096] If there is a CORESET completely confined within the RB set (yes), then in S508, the UE may monitor the PDCCH based on the CORESET configuration and the search space set configuration.

[0097] However, if there is a punctured CORESET (No), then in S509, the UE may apply the above Figure 2-4 A new PDCCH monitoring solution.

[0098] For example, the UE may ignore PDCCH candidates that are not limited to the RB set (see, for example, Figure 2), or the entire CORESET that is not completely within the RB set may be ignored, the UE may puncture PDCCH candidates that are not limited to the RB set (bearing the risk of increased noise associated with the PDCCH candidate), the UE may use rate matching candidates that are not limited to the RB set (e.g., rate matching is performed by the base station) (e.g., see Figure 3 ), or the UE may modify the CORESET resources to be within the RB set (see, for example, Figure 4 ).

[0099] Accordingly, embodiments of the present disclosure provide improvements to network communications by providing methods for dealing with problems that would otherwise arise due to the presence of punctured PDCCH candidates.

[0100] Although the embodiments of the present disclosure have been specifically shown and described with reference to the accompanying drawings, the specific wording used herein is only used to achieve the purpose of describing the present invention, and is not intended to define the meaning of the present invention or to limit the scope of the present invention set forth in the claims. Therefore, it will be understood by those skilled in the art that various modifications to the present disclosure and other equivalent embodiments of the present disclosure are also possible. Therefore, the actual technical protection scope of the present disclosure must be determined based on the technical essence of the attached claims, and its functional equivalence.

Claims

1. A network communication method for solving the problem that CORESET resource allocation is not aligned with the first RB set due to a changing RB set size, the method include: Determine the search space set configuration; Determining that the search space set includes a plurality of frequency domain monitoring opportunities; identifying a CORESET resource in each of the frequency domain monitoring opportunities; determining that the CORESET resources are only partially confined to the first RB set; as well as Adjust the PDCCH monitoring protocol to improve the performance of the CORESET resources, Wherein, adjusting the PDCCH monitoring protocol includes rate matching the PDCCH candidates of the CORESET resources, and the PDCCH candidates are only partially confined to the first RB set.

2. The method according to claim 1, in, The CORESET resources in each of the frequency-domain monitoring opportunities are based on a size of a zeroth RB set.

3. The method according to claim 1, further comprising: include: Determine CORESET configuration and / or RB set configuration; as well as Determine that there are no new restrictions on CORESET configuration and / or RB set configuration.

4. The method according to claim 1, in, Adjusting the PDCCH monitoring protocol further includes ignoring PDCCH candidates of the CORESET resources, the PDCCH candidates being only partially confined to the first RB set.

5. The method according to claim 1, in, Adjusting the PDCCH monitoring protocol further includes modifying the CORESET resources to be within the first RB set.

6. The method according to claim 1, in, Adjusting the PDCCH monitoring protocol further includes ignoring CORESET resource allocations that are not within an RB set.

7. The method according to claim 1, further comprising: include: Determine the CORESET configuration and RB set configuration; as well as Make sure that the CORESET configuration is applicable to the RB set configuration.

8. A communication device for performing a network communication method for resolving a problem in which a CORESET resource allocation is not aligned with a first RB set due to a varying RB set size, the communication device being configured to: Determine the search space set configuration; Determining that the search space set includes a plurality of frequency domain monitoring opportunities; identifying a CORESET resource in each of the frequency domain monitoring opportunities; determining that the CORESET resources are only partially confined to the first RB set; as well as Adjust the PDCCH monitoring protocol to improve the performance of the CORESET resources, Wherein, the communication device is configured to adjust the PDCCH monitoring protocol by rate matching PDCCH candidates of the CORESET resources, and the PDCCH candidates are only partially confined to the first RB set.

9. The communication device according to claim 8, in, The CORESET resources in each of the frequency-domain monitoring opportunities are based on a size of a zeroth RB set.

10. The communication device according to claim 8, in, The communication device is further configured to: Determine CORESET configuration and / or RB set configuration; and Determine that there are no new restrictions on CORESET configuration and / or RB set configuration.

11. The communication device according to claim 8, in, The communications device is further configured to adapt the PDCCH monitoring protocol by ignoring PDCCH candidates of the CORESET resources, the PDCCH candidates being only partially confined within the first set of RBs.

12. The communication device according to claim 8, in, The communications device is further configured to adjust the PDCCH monitoring protocol by modifying the CORESET resources to be within the first RB set.

13. The communication device according to claim 8, in, The communications device is further configured to adapt the PDCCH monitoring protocol by ignoring CORESET resource allocations that are not within an RB set.

14. The communication device according to claim 8, in, The communication device is further configured to: Determine the CORESET configuration and the RB set configuration; and Make sure that the CORESET configuration is applicable to the RB set configuration.

15. A non-transitory computer readable medium implemented in combination with a user equipment for communicating with a base station, the non-transitory computer readable medium having computer code, the computer code when executed on a processor implementing a network communication method, the network communication method for resolving the problem of CORESET resource allocation and first RB set misalignment due to a changed RB set size, the method include: Determine the search space set configuration; Determining that the search space set includes a plurality of frequency domain monitoring opportunities; identifying a CORESET resource in each of the frequency domain monitoring opportunities; determining that the CORESET resources are only partially confined to the first RB set; as well as Adjust the PDCCH monitoring protocol to improve the performance of the CORESET resources, Wherein, adjusting the PDCCH monitoring protocol includes rate matching the PDCCH candidates of the CORESET resources, and the PDCCH candidates are only partially confined to the first RB set.

16. The non-transitory computer readable medium of claim 15, in, The CORESET resources in each of the frequency-domain monitoring opportunities are based on a size of a zeroth RB set.

17. The non-transitory computer readable medium of claim 15, in, The computer code, when executed on a processor, further implements the method by: Determine CORESET configuration and / or RB set configuration; and Determine that there are no new restrictions on CORESET configuration and / or RB set configuration.

18. The non-transitory computer readable medium of claim 15, in, When the computer code is executed on a processor, the method is further implemented by: Determine the CORESET configuration and the RB set configuration; and Make sure that the CORESET configuration is applicable to the RB set configuration.