Puncture control for control resource set #0

Abstract

Embodiments of the present disclosure relate to an apparatus, method, and computer-readable storage medium for controlling the puncturing of a control resource set (CORESET) #0. The method includes, in a first apparatus, determining whether a particular type of CORESET is punctured at a particular frequency position, based at least on detection of a synchronization signal block received from a second apparatus, that the punctured portion of the resource within the particular type of CORESET cannot carry downlink control information; obtaining a CORESET puncturing pattern in accordance with the determination that the particular type of CORESET is punctured; and determining the punctured portion of the resource within the CORESET, based at least on the CORESET puncturing pattern. Furthermore, the method includes indicating that a particular type of CORESET is punctured by transmitting a synchronization signal block at a particular frequency position from the second apparatus to the first apparatus.

Description

[[Technical Field]]

[0001] Cross-Reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 518380, filed on August 9, 2023. The entire content of the above-referenced application is incorporated herein by reference.

[0002] Various exemplary embodiments of the present disclosure generally relate to the field of telecommunications, and in particular to methods, devices, apparatuses, and computer-readable storage media for controlling puncturing of control resource set (CORESET) #0, especially in a 5MHz channel bandwidth and 20 resource block (RB) scenario. [[Background Art]]

[0003] In Release 18, a work item on New Radio (NR) support for dedicated spectrum less than 5MHz for Frequency Range 1 (FR1) has been approved. This work item relates to professional networks used to provide mission-critical communications for industries such as smart energy and infrastructure, public safety, and railway communications, and also relates to a 3MHz channel bandwidth in some scenarios. These networks benefit not only from the high spectral efficiency of 5G NR but also from other characteristics such as ultra-high reliability and low latency. [[Summary of the Invention]]

[0004] A first aspect of the present disclosure provides a first apparatus. The first apparatus includes at least one processor and at least one memory which stores instructions that, when executed by the at least one processor, cause the first apparatus to determine at least whether a particular type of CORESET is punctured at a particular frequency position, based at least on detection of a synchronization signal block received from a second apparatus, that the punctured portion of the resources in the particular type of CORESET cannot carry downlink control information; to obtain a CORESET puncturing pattern in accordance with the determination that the particular type of CORESET is punctured; and to determine the punctured portion of the resources in the CORESET based at least on the CORESET puncturing pattern.

[0005] A second aspect of the present disclosure provides a second device. The second device includes at least one processor and at least one memory which, when executed by the at least one processor, stores instructions causing the second device to at least: transmit a synchronous signal block to the first device at a specific frequency position to indicate that a particular type of CORESET is punctured; and transmit downlink control information to the first device based at least on the portion of the CORESET's resources that is not punctured.

[0006] A third aspect of the present disclosure provides a method, which includes determining whether a particular type of CORESET is punctured at a particular frequency position, based at least on the detection of a synchronization signal block received from a second device, that the punctured portion of the resources in the particular type of CORESET is unable to carry downlink control information; obtaining a CORESET puncturing pattern in accordance with the determination that the particular type of CORESET is punctured; and determining the punctured portion of the resources in the CORESET based at least on the CORESET puncturing pattern.

[0007] A fourth aspect of the present disclosure provides a method, which includes: indicating to a first device that a particular type of CORESET is punctured by transmitting a synchronization signal block at a particular frequency position; and transmitting downlink control information to the first device based at least on the portion of the CORESET's resources that is not punctured.

[0008] A fifth aspect of the present disclosure provides a first apparatus, the first apparatus includes means for determining whether a particular type of CORESET is punctured at a particular frequency position, based at least on detection of a synchronization signal block received from a second apparatus, such that the punctured portion of the CORESET is unable to carry downlink control information; means for obtaining a CORESET puncturing pattern in accordance with the determination that a particular type of CORESET is punctured; and means for determining the punctured portion of the CORESET's resources, based at least on the CORESET puncturing pattern.

[0009] A sixth aspect of the present disclosure provides a second device, the second device including means for indicating to the first device that a particular type of CORESET is punctured by transmitting a synchronization signal block at a particular frequency position, and means for transmitting downlink control information to the first device, based at least on the portion of the CORESET resources that is not punctured.

[0010] A seventh aspect of this disclosure provides a computer-readable medium, which includes instructions stored on the computer-readable medium that cause a device to perform a method according to at least the third aspect.

[0011] In an eighth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored on the computer-readable medium that cause a device to perform at least the method according to the fourth aspect.

[0012] It should be understood that the Summary of the Invention section is not intended to identify any important or essential features of the embodiments of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will become readily apparent through the following description.

[0013] Several exemplary embodiments are described herein with reference to the accompanying drawings. [Brief explanation of the drawing]

[0014] [Figure 1] This figure shows an exemplary communication environment in which exemplary embodiments of the present disclosure may be implemented. [Figure 2] This figure shows an example of frequency domain resource allocation for CORESET#0 according to some exemplary embodiments of the present disclosure. [Figure 3] This figure shows a signaling chart 300 for communication according to some exemplary embodiments of the present disclosure. [Figure 4A]This figure shows an example of CORESET puncturing according to some exemplary embodiments of the present disclosure. [Figure 4B] This figure shows an example of CORESET puncturing according to some exemplary embodiments of the present disclosure. [Figure 4C] This figure shows an example of CORESET puncturing according to some exemplary embodiments of the present disclosure. [Figure 4D] This figure shows an example of CORESET puncturing according to some exemplary embodiments of the present disclosure. [Figure 4E] This figure shows an example of CORESET puncturing according to some exemplary embodiments of the present disclosure. [Figure 4F] This figure shows an example of CORESET puncturing according to some exemplary embodiments of the present disclosure. [Figure 5] This figure shows a flowchart of an exemplary method 500 for controlling puncture in CORESET#0, according to some exemplary embodiments of the present disclosure. [Figure 6] This figure shows a flowchart of an exemplary method 600 for controlling puncture in CORESET#0, according to some exemplary embodiments of the present disclosure. [Figure 7] This figure shows a simplified block diagram of device 700 suitable for carrying out exemplary embodiments of the present disclosure. [Figure 8] This figure shows a block diagram of an exemplary computer-readable medium according to some exemplary embodiments of the present disclosure. [Modes for carrying out the invention]

[0015] Throughout the drawing, identical or similar reference numbers represent identical or similar elements.

[0016] The principles of the present disclosure will now be described with reference to several exemplary embodiments. These embodiments are described for illustrative purposes only, to assist those skilled in the art in understanding and implementing the present disclosure without implying any limitation on the scope of the disclosure. The embodiments described herein may be implemented in various ways other than those described below.

[0017] In the following description and the claims, unless otherwise specifically defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which the present disclosure belongs.

[0018] References in the present disclosure to "one embodiment", "an embodiment", "an exemplary embodiment" and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments necessarily need to include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described herein.

[0019] It should be understood that although terms such as "first", "second" before a noun may be used herein to describe various elements, such elements should not be limited by these terms. These terms are only used to distinguish one element from another, and are not intended to limit the order of nouns. For example, without departing from the scope of the exemplary embodiment, a first element could be termed a second element, and similarly, a second element could be termed a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed items.

[0020] As used herein, “at least one of the <list of two or more elements>” and “at least one of the <list of two or more elements>” and similar phrases mean at least one of the elements, or at least two or more of the elements, or at least all of the elements, when the lists of two or more elements are linked by “and” or “or”.

[0021] Unless expressly stated otherwise, performing a step "in response to A" as used herein does not indicate that the step will be performed immediately after "A" occurs, and that it may include one or more intervening steps.

[0022] The terminology used herein is for the purpose of describing only specific embodiments and is not intended to be an limitation of exemplary embodiments. 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 should be further understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including,” when used herein, indicate the presence of the described features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0023] As used in this application, the term “circuit” may refer to one or more or all of the following: (a) Hardware-only circuit embodiments (such as embodiments consisting only of analog and / or digital circuits) (b) combinations of hardware circuits and software, for example (to the extent applicable) (i) combination of analog and / or digital hardware circuits with software / firmware (ii) Any part of a hardware processor, software, and memory having software (including a digital signal processor) that cooperates to cause a device such as a mobile phone or server to perform various functions. (c) A processor such as a microprocessor or part of a microprocessor that requires hardware circuitry and / or software (e.g., firmware) for operation, but the software may not be present if it is not required for operation.

[0024] This definition of circuit applies to all use of this term in this application, including in any claim. Further examples include the term circuit as used herein, which also encompasses a mere hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor, and its associated software and / or firmware implementation. The term circuit also includes, for example, and applicable to the elements of a particular claim, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0025] As used herein, the term “communication network” refers to a network that conforms to any appropriate communication standard, such as New Radio (NR), Long-Term Evolution (LTE), LTE Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), and Narrowband Internet of Things (NB-IoT). Furthermore, communication between terminal devices and network devices within a communication network may be carried out in accordance with any appropriate generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5G Advanced, sixth-generation (6G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure may be applied to a variety of communication systems. Given the rapid development of communications, there will naturally be future communication technologies and systems to which this disclosure may be embodied. The scope of this disclosure should not be seen as being limited to the aforementioned systems only.

[0026] As used herein, the term “network device” refers to a node in a communications network through which terminal devices access the network and receive services from it. Depending on the applicable terminology and technology, a network device may also refer to a base station (BS) or access point (AP), such as a node B (node ​​B or NB), an evolved node B (enode B or eNB), an NR NB (also called a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an access backhaul integration (IAB) node, a low-power node such as a femto or pico, a non-terrestrial network (NTN) or satellite network device, a base station (BS) or access point (AP), such as a low orbit (LEO) satellite or geostationary (GEO) satellite, or an aircraft network device. In some exemplary embodiments, a radio access network (RAN) distribution architecture includes a central unit (CU) and a distributed unit (DU) in an IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves like a UE with respect to the parent node, and the DU portion of the IAB node behaves like a base station with respect to the next-hop IAB node.

[0027] The term “terminal device” refers to any end device that may be capable of wireless communication. For example, rather than being limited, terminal devices may also be called communication devices, user equipment (UE), subscriber stations (SS), portable subscriber stations, mobile stations (MS), or access terminals (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer equipment (CPEs), Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronic devices, and devices operating on commercial and / or industrial wireless networks. Terminal devices also correspond to the mobile terminal (MT) portion of IAB nodes (e.g., relay nodes). In the following description, the terms “terminal device,” “communication device,” “terminal,” “user equipment,” and “UE” may be used interchangeably.

[0028] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for communication, for example, communication between a terminal device and a network device, such as a time-domain resource, a frequency-domain resource, a spatial-domain resource, a code-domain resource, or any other combination of time, frequency, spatial, and / or code-domain resources that enables communication. Hereinafter, unless expressly stated, resources in both the frequency-domain and time-domain are used as examples of transmission resources to illustrate some exemplary embodiments of this disclosure. It should be noted that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains. In some embodiments, a frequency-domain resource may comprise one or more resource blocks, each having 12 subcarriers, and a time-domain resource may comprise one or more OFDM symbols.

[0029] Figure 1 shows an exemplary communication network 100 in which embodiments of the present disclosure may be implemented. As shown in Figure 1, the communication network 100 may include a first device 110. Hereinafter, the first device 110 may also be referred to as a UE or terminal device.

[0030] The communication network 100 may further include a second device 120. Hereinafter, the second device 120 may also be referred to as a gNB or network device. The first device 110 may communicate with the second device 120.

[0031] It should be understood that the number of network devices and terminal devices shown in Figure 1 are given for illustrative purposes only and do not imply any limitation. The communication network 100 may include any appropriate number of network devices and terminal devices.

[0032] In some exemplary embodiments, the link from the second device 120 to the first device 110 may be called a downlink (DL), and the link from the first device 110 to the second device 120 may be called an uplink (UL). In the DL, the second device 120 is the transmitting (TX) device (or transmitter), and the first device 110 is the receiving (RX) device (or receiver). In the UL, the first device 110 is the TX device (or transmitter), and the second device 120 is the RX device (or receiver).

[0033] Communication within the communication environment 100 may be conducted in accordance with any suitable communication protocol, including, but not limited to, cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G), wireless local network communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communication may utilize any suitable wireless communication technology, including, but not limited to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexing (FDD), time division duplexing (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technologies currently known or to be developed in the future.

[0034] As mentioned above, the consideration of NR support for dedicated spectra below 5 MHz in frequency range 1 (FR1) was discussed.

[0035] For example, the dedicated FDD spectrum for FR1 is intended to include the following purposes: ● Identify and specify the necessary changes to the NR physical layer with minimal impact on specifications, for operation with spectral allocations from approximately 3 MHz to less than 5 MHz. ○ Restrictions on the use of a 15 kHz subcarrier spacing (SCS) and normal cyclic prefixes. ○ Regarding the synchronization signal / physical broadcast channel block (SSB), ● Reuse PSS / SSS specifications without puncture ● PBCH based on the current design Identifying and specifying the minimum necessary changes to the physical downlink control channel (PDCCH), channel status information reference signal (CSI-RS) / tracking reference signal (TRS), physical uplink control channel (PUCCH), and physical random access channel (PRACH) for functional support based on existing designs without optimization.

[0036] Furthermore, several related embodiments can be cited as follows: ● For a 3MHz channel bandwidth in bandwidth n100 (i.e., the frequency band for the Future Railway Mobile Communication System (FRMCS)) (with a maximum channel usage of 15 physical resource blocks (PRB) as already agreed in RAN1 / RAN4): ○ The physical broadcast channel (PBCH) transmission bandwidth is 12PRB. ○ The transmission bandwidth of CORESET#0 will be determined by RAN1. ● RAN1 is required to consider whether the above applies to other bands having a 3MHz channel bandwidth, or whether the PBCH transmit bandwidth is 15PRB for such bands. ● For a 5MHz channel bandwidth: ○ The PBCH transmission bandwidth is 20 PRB. ○ The transmission bandwidth of CORESET#0 will be determined by RAN1. ● Further details (including details of the synchronized raster) will be handled by the workgroup.

[0037] Based on the current agreement, for a 3MHz channel bandwidth, CORESET operation is supported specifically for 12PRB and 15PRB. ● For a 3MHz channel bandwidth across the entire band (with a maximum channel usage of 15PRB, as already agreed in RAN1 / RAN4): ○ The PBCH transmission bandwidth is 12PRB. ○ For CORESET#0's transmit bandwidth, both 12PRB and 15PRB are supported. ● In the case of 12PRB, the mapping from legacy interleaved (R=2) CORESET CCE to REG is N RB CORESET It is used with =12, meaning that 12PRB is indicated without puncture. ● In the case of 15PRB, N RB CORESET CORESET#0 with value =24 is punctured. ● Both interleaved mapping (legacy interleaver size R=2) and non-interleaved mapping are supported. ● Some entries in the table relate to interleaved mapping, while others relate to non-interleaved mapping. ● A single table with a maximum of 16 entries can handle both cases. ● The maximum number of CORESET#0 symbols is 3. The minimum number of CORESET#0 symbols is 2. ● Multiplexing pattern 1 for SSB and CORESET#0 is used (Pattern 1 means that SSB and CORESET#0 are time-multiplexed). ● REG bundle size = 6.

[0038] As mentioned above, one of the objectives of the work item may be to "identify and specify" the minimum necessary changes to the PDCCH for functional support based on the existing design without optimization. While acquiring system information, the UE monitors the PDCCH at resource intervals of at least 4.32 MHz (i.e., 24 RB), i.e., beyond the targeted transmit bandwidths of 20 RB, 15 RB, and 12 RB. Therefore, any PDCCH changes required to support NR in narrow spectrum allocations should be concentrated on these PDCCH resources. Another aspect of the PDCCH that requires attention is its frequency domain position relative to SSB.

[0039] A PDCCH may also be mapped to a set of physical resources called a CORESET, which similarly consists of control channel elements (CCEs). A control channel element consists of six resource element groups (REGs), where a resource element group is equivalent to one resource block between one OFDM symbol.

[0040] CORESET can be flexibly configured to the UE after initial access. However, there are limited configuration options available for CORESET#0, such as Type0-PDCCH, which is used for PDCCHs that schedule the transmission of System Information Block 1 (SIB1).

[0041] First, the frequency domain location of CORESET#0 can be considered relative to SSB. Figure 2 shows an example of frequency domain resource allocation for CORESET#0.

[0042] As shown in Figure 2, after the UE detects the primary synchronization signal (PSS) 201 and secondary synchronization signal (SSS) 203 and demodulates the PBCH 202, the UE obtains the Master Information Block (MIB) on the PBCH 202. Next, the UE needs to obtain the remaining minimal system information carried by the SIB 1. The UE reads the CORESET#0 configuration index from the MIB on the PBCH 202, which indicates the time and frequency resource allocation parameters of CORESET 205. One of these parameters defines the frequency domain offset 204 between the first RB where the SSB is located and the first RB of CORESET#0.

[0043] Similar to PBCH transmission, puncturing may be necessary to constrain CORESET#0 within the available spectrum. This can lead to situations where the constrained CORESET#0 contains several partial CCEs. For example, if the available spectrum is not an integer multiple of the CCE size and is less than 24 RB (20 RB in a particular case), then at least one partial CCE will exist.

[0044] However, if PBCH puncture is not considered in the frequency domain allocation of CORESET#0, two punctured CCEs will be unnecessarily present. Since CCEs are used as the basic resource unit in channel estimation, partial CCEs can degrade channel estimation.

[0045] While the use of partial CCEs is unavoidable, it is reasonable to minimize the number of partial CCEs. Therefore, the frequency domain allocation of CORESET#0 may need to be reconsidered in order to keep CORESET#0 aligned with the uncropped RB and CCE levels of SSB, or in the case of 20 RB, in order to keep the uncropped portion of CORESET#0 aligned with the RB and CCE levels of SSB.

[0046] In this situation, when operating with a 5MHz channel bandwidth (particularly for bandwidth n100), the method of configuring a narrower bandwidth for CORESET#0 (particularly for Type0-PDCCH) in a 20RB CORESET#0 design may require further discussion to provide sufficient flexibility while minimizing the addition of complexity.

[0047] According to some exemplary embodiments of the present disclosure, a solution for controlling the puncturing of CORESET#0 is provided. In this solution, a first device 110 detects a synchronous signal block received from a second device at a specific frequency position and determines, based on the detection, whether a particular type of CORESET is punctured. If the first device 110 determines that a particular type of CORESET is punctured, the first device 110 determines the portion of the resources within the CORESET that is punctured, at least based on the CORESET puncturing pattern.

[0048] Based on this solution, flexible selection between punctured and undpunctured CORESET#0 and corresponding puncturing options may be supported.

[0049] Exemplary embodiments of this disclosure will be described in detail below with reference to the accompanying drawings.

[0050] Referring here to Figure 3, Figure 3 shows a signaling chart 300 for communication according to some exemplary embodiments of the present disclosure. As shown in Figure 3, the signaling chart 300 is accompanied by a first device 110 and a second device 120. For illustrative purposes, the signaling chart 300 will be described with reference to Figure 1. It should be understood that the process shown in Figure 3 can also be employed in other terminal devices and network devices shown in Figure 1.

[0051] The first device 110 may perform initial access to a channel associated with a specific bandwidth (e.g., n100, 5 MHz channel bandwidth (CBW)). As shown in Figure 1, the second device 120 may transmit (305) SSB. It should be understood that the SSB used herein may include a “synchronization signal” (SS) block and a PBCH block, and the SS block may be replaced by a synchronization signal, a primary synchronization signal, or a secondary synchronization signal.

[0052] Based on the detection of the SSB, the first device 110 determines the parameters of CORESET#0, such as the CORESET multiplexing pattern, the number of RBs, the number of symbols, and the offset (RB), from entries 0 to 5 in Table 1.

[0053] [Table 1]

[0054] When the first device 110 detects SSB at a specific frequency position, the first device 110 may determine that a specific type of CORESET is punctured (315). The term “specific type of CORESET” as used herein is sometimes referred to as CORESET#0, for example, Type0-PDCCH, which is used for a PDCCH that schedules the transmission of SIB1.

[0055] As used herein, the term “specific frequency position” may refer to the position of a sync raster point in a frequency domain, such as 921.45 MHz. This sync raster point may be set based on the lower bandwidth edge of n100, which is at 919.4 MHz. This means that the lowest channel raster point with channel BW in the band is 919.4 MHz + 2.5 MHz = 921.9 MHz. Since 5 MHz CBW means 25 RB, the lowest RB edge is 12.5 RB below the channel raster point. The sync raster point, with its lowest RB aligned with the channel's lowest RB (common raster), is then 12.5 - 10 = 2.5 RB (= 450 kHz) below the channel raster point, i.e., 921.9 - 0.45 = 921.45 MHz. In short, 921.45 is the sync raster point that allows SSB to be placed as low as possible within a band limited to 5 MHz CBW and a transmit bandwidth of 20 PRB. It is also a synchronous raster point that is not part of the normal / conventional synchronous raster used in the n100 with a normal 25PRB transmit bandwidth of 5MHz CBW.

[0056] For example, if the first device 110 determines that a primary or secondary synchronization signal has been detected at a specific frequency position, the first device 110 may determine that a specific type of CORESET is punctured.

[0057] CORESET#0 operates without puncturing the remaining synchronous raster points in the case of 5MHz CBW.

[0058] Furthermore, additional confirmation of CORESET puncture can be obtained by the first device through another method, such as MIB.

[0059] Various puncturing patterns can be acquired / determined by the first device 110. For example, the puncturing pattern may be configured by the second device 120 and transmitted to the first device 110, or it may be preconfigured / predefined in the specifications.

[0060] After determining that a specific type of CORESET is punctured, the first device 110 can determine a corresponding puncturing pattern for CORESET puncturing. Various puncturing patterns are described in detail below with reference to Figures 4A to 4F.

[0061] As an option (which may be referred to as Option 1 below), the RBs below the lowest RB of the PBCH (i.e., RB#0) are punctured. In some embodiments, the lowest subcarrier of the PBCH (i.e., RB#0) may be found as puncturing_threshold_low.

[0062] Figure 4A shows an example of CORESET puncturing using Table 1 notified in the MIB, according to some exemplary embodiments of the present disclosure. As shown, for index 0 or 3, index 1 or 4, and index 2 or 5 in Table 1, the RBs below RB#0 of the PBCH are punctured.

[0063] In another option (which may be referred to as Option 2), the RBs above the highest RB of the PBCH (i.e., RB#19) are punctured. In some embodiments, the highest subcarrier of the PBCH (i.e., RB#19) may be seen as the puncturing_threshold_high.

[0064] In a further option (which may be referred to as Option 3), the RBs below the lowest RB of the PBCH (i.e., RB#0) and above the highest RB of the PBCH (i.e., RB#19) are punctured to align the transmit bandwidth with that of the PBCH.

[0065] Figure 4B shows an example of CORESET puncturing using Table 1 as notified in the MIB, according to some exemplary embodiments of the present disclosure. As shown based on Option 3, for index 0 or 3, index 1 or 4, and index 2 or 5 in Table 1, the RBs below RB#0 and the RBs above RB#19 of the PBCH are punctured.

[0066] Furthermore, based on options 1-3 described above, only those indexes containing up to 20 RBs after the puncturing operation may be considered valid indexes. The first device 110 may not expect to receive invalid indexes. In addition, or optionally, puncturing is applied additionally at the granularity of the entire CCE (not the RBs). In other words, if at least one RB of a CCE needs to be punctured, the entire CCE (i.e., all RB portions of that CCE) will be punctured (this may be referred to as option 4 below). In this option, the unpunctured resources will contain integer multiples of 6 REGs.

[0067] Figure 4C shows an example of CORESET puncturing using Table 1 notified in the MIB, according to some exemplary embodiments of the present disclosure. Based on Option 1, i.e., puncturing RBs below the lowest RB of the PBCH (i.e., RB#0), Figure 4C shows a puncturing pattern (index 1 or 4) by Option 4, in which only complete CCEs are sent. In Figure 4C, the Option 1 pattern is shown as a reference (index 1 or 4) for the Option 4 pattern derived from the Option 1 pattern (one of which is index 4, with three OFDM symbols (OS), and the other is index 1, where two OSs are shown below the Option 1 pattern).

[0068] Figure 4D shows an example of CORESET puncturing using Table 1 notified in the MIB, according to some exemplary embodiments of the present disclosure. Based on Option 3, i.e., both the RBs below the lowest RB of the PBCH (i.e., RB#0) and the RBs above the highest RB of the PBCH (i.e., RB#19) are punctured, Figure 4D shows a puncturing pattern by Option 4 (for indices 0-5 in Table 1) in which only complete CCEs are sent.

[0069] In some variations, there is a threshold for the allocation of RBs in a CCE, which determines whether the entire CCE is punctured. For example, if the threshold is 0.5 (50%), the entire CCE is punctured if at least half of the RBs of the CCE need to be punctured.

[0070] Figure 4E shows an example of CORESET puncturing using Table 1 notified in the MIB, according to some exemplary embodiments of the present disclosure. Based on Option 3, i.e., both RBs below the lowest RB of the PBCH (i.e., RB#0) and RBs above the highest RB of the PBCH (i.e., RB#19) are punctured, Figure 4E shows a puncturing pattern by Option 4, i.e., PRBs are sent only when there are more than 50% of the PRBs of the CCE.

[0071] Furthermore, based on options 1-4 described above, IE, puncturing_threshold_low and / or puncturing_threshold_high can be determined by predefined offsets to the lowest RB of the PBCH (i.e., RB#0) and the highest RB of the PBCH (i.e., RB#19) (hereinafter referred to as option 5).

[0072] In some embodiments, the predefined offset is [offset_low,offset_high]=[x,y] subcarrier (where x and y are positive or negative integers). In some other embodiments, the predefined offset is [offset_low,offset_high]=[x,y]RB (where x and y are positive or negative integers).

[0073] A further option assumes that CORESET#0 and PBCH are subcarrier offset from each other. This option (which may be referred to as Option 6) is a variation of Options 1-3, where puncturing is applied at the subcarrier granularity. In this case, a partial RB (of CORESET#0) is considered a punctured RB. A partial RB can be considered as part of a symbol or subcarrier within the RB (which may be referred to as Option 6). A partial RB may also be called a punctured RB, and a partial RB has punctured subcarriers, the number of punctured subcarriers in a partial RB is greater than 0 and less than 12.

[0074] Furthermore, based on options 1-5 described above, puncturing may require additional implicit or explicit signaling or confirmation (otherwise, the UE will interpret the MIB content error and continue searching for other PSS / SSS, or alternatively, the UE will not apply puncturing without additional confirmation). Additional confirmation may be, for example, a specific value of k_SSB (the indicated gap between subcarrier 0 of the SS / PBCH block and the common resource block), e.g., 0 or a predefined k_SSB value corresponding to an indicated CORESET table index (which may hereafter be called option 7). k_SSB may indicate the frequency domain offset between the SSB and the common resource block by the number of subcarriers. k_SSB is indicated by the MIB.

[0075] Alternatively, a specific index (e.g., index 0 and / or index 3) might be considered the only valid option (which could be referred to as option 8) when the detected synchronous raster point is associated with n100, 5MHz CBW.

[0076] Figure 4F shows examples of CORESET puncturing using Table 1 notified in the MIB, according to some exemplary embodiments of the present disclosure. In some embodiments, if one predefined synchronous raster point is 921.45 MHz, as shown under Option 8, RB20-23 are punctured for index 0 or index 3 (Alternative 1). In some other embodiments shown in Alternative 2, RB18-23 are punctured for index 0 (with 2OS CORESET), and RB20-23 are punctured for index 3 (with 3OS CORESET), thus limiting puncturing to the granularity of the entire CCE.

[0077] As described above, using the CORESET puncturing pattern, the first device 110 can determine the portion of the punctured resources within the CORESET. Referring again to Figure 3, the first device 110 can decode (320) the PBCH and monitor the PDCCH based on the determined portion of the punctured resources within the CORESET.

[0078] In another case where a PSS / SSS can be found from another synchronous raster point defined for a 5MHz CBW on a specific channel, and it is determined that the CORESET is not punctured, the first device 110 may obtain information from the PBCH / MIB to decode the PBCH and determine the index that addresses rows (0-5) of Table 1. The first device 110 may then perform a Type0-PDCCH detection, assuming that the reception is not punctured.

[0079] In this way, the original table of CORESET#0 (i.e., Table 1) can be reused. Furthermore, flexible selection between punctured and undpunctured CORESET#0 and corresponding puncturing options can be supported.

[0080] Figure 5 shows a flowchart of an exemplary method 500 for controlling puncture of CORESET#0 according to some exemplary embodiments of the present disclosure. Method 500 may be implemented in a first apparatus 110 (which may be implemented as a terminal device) as shown in Figure 1. For illustrative purposes, Method 500 will be described with reference to Figure 1.

[0081] In block 510, the first device 110 determines, at least based on the detection of a synchronization signal block received from the second device, whether a particular type of CORESET is punctured at a particular frequency position, and the punctured portion of the resource within the particular type of CORESET is unable to carry downlink control information.

[0082] If the first device 110 determines that a specific type of CORESET is punctured, in block 520, the first device 110 obtains a CORESET puncturing pattern.

[0083] In block 530, the first device 110 determines the portion of the punctured resource within the CORESET based at least on the CORESET puncturing pattern.

[0084] In some exemplary embodiments, a particular type of CORESET is CORESET#0.

[0085] In some exemplary embodiments, method 500 further includes determining that a particular type of CORESET is punctured, according to at least one of the following determinations: that a primary or secondary synchronization signal is detected at a specific frequency position, or that additional confirmation of CORESET puncturing is obtained from a master information block.

[0086] In some exemplary embodiments, a specific frequency position is associated with the position of a synchronization raster point in the frequency domain.

[0087] In some exemplary embodiments, obtaining a CORESET puncturing pattern includes determining at least one puncturing threshold associated with the location of a set of broadcasting channel resource blocks, and determining that a portion of a resource is punctured, according to the determination that the portion of the resource in the CORESET does not satisfy at least one puncturing threshold.

[0088] In some exemplary embodiments, a portion of a resource in a CORESET failing to satisfy at least one puncturing threshold includes at least one of the following: one or more resource blocks in the CORESET are located below the lowest broadcasting channel resource block, or one or more resource blocks in the CORESET are located above the highest broadcasting channel resource block.

[0089] In some exemplary embodiments, at least one puncturing threshold is determined based on an offset to at least one of the lowest broadcasting channel resource blocks or the highest broadcasting channel resource block.

[0090] In some exemplary embodiments, Method 500 further includes determining that a puncturing threshold is determined based on an offset relative to the position of a set of broadcasting channel resource blocks, and that the offset has subcarrier granularity, thereby determining that a portion of a punctured resource in a CORESET includes at least one sub-resource block.

[0091] In some exemplary embodiments, Method 500 further includes determining that a CORESET puncturing pattern requires that the CORESET be punctured at the granularity of a control channel element CCE, and that, following the determination that at least one resource block in the CCE is punctured, a second portion of further resource blocks in the CCE is punctured.

[0092] In some exemplary embodiments, whether further resource blocks within the CCE are punctured is determined based on a threshold.

[0093] In some exemplary embodiments, method 500 further includes determining that only at least one specific index associated with a particular type of CORESET is valid, according to the determination that a synchronization raster point is associated with at least one of a particular bandwidth or a specific bandwidth, and determining that one or more specific resource blocks associated with at least one specific index are punctured, wherein the at least one specific index is indicated by a master information block.

[0094] In some exemplary embodiments, method 500 further includes determining that at least one specific index associated with a particular type of CORESET is valid if the associated CORESET contains up to 20 RBs after a puncturing operation.

[0095] In some exemplary embodiments, the first device includes a terminal device, and the second device includes a network device.

[0096] Figure 6 shows a flowchart of an exemplary method 600 for controlling puncture of CORESET according to some exemplary embodiments of the present disclosure. Method 600 may be implemented in a second device 120 (which may be implemented as a network device) as shown in Figure 1. For illustrative purposes, Method 600 will be described with reference to Figure 1.

[0097] In block 610, a specific type of CORESET is indicated to the first device by transmitting a synchronization signal block at a specific frequency position.

[0098] In block 620, downlink control information is transmitted to the first device, based at least on the unpunctured portion of the CORESET resources.

[0099] In some exemplary embodiments, a particular type of CORESET is CORESET#0.

[0100] In some exemplary embodiments, the device is configured to indicate that a particular type of CORESET is punctured by additional information in a master information block.

[0101] In some exemplary embodiments, a specific frequency position is associated with the position of a synchronization raster point in the frequency domain.

[0102] In some exemplary embodiments, the first device includes a terminal device, and the second device includes a network device.

[0103] In some exemplary embodiments, a first apparatus capable of performing any of the methods 500 (e.g., the first apparatus 110 in Figure 1) may include means for performing each operation of the methods 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module. The first apparatus may be implemented as the first apparatus 110, or may be included in the first apparatus 110.

[0104] In some exemplary embodiments, the first device includes means for determining whether a particular type of CORESET is punctured at a particular frequency position, based at least on detection of a synchronization signal block received from a second device, such that the punctured portion of the CORESET is unable to carry downlink control information; means for obtaining a CORESET puncturing pattern in accordance with the determination that a particular type of CORESET is punctured; and means for determining the punctured portion of the CORESET's resources, based at least on the CORESET puncturing pattern.

[0105] In some exemplary embodiments, a particular type of CORESET is CORESET#0.

[0106] In some exemplary embodiments, the first device further includes determining that a particular type of CORESET is punctured, based on at least one of the following determinations: that a primary or secondary synchronization signal is detected at a specific frequency position, or that additional confirmation of CORESET puncturing is obtained from a master information block.

[0107] In some exemplary embodiments, a specific frequency position is associated with the position of a synchronization raster point in the frequency domain.

[0108] In some exemplary embodiments, means for obtaining a CORESET puncturing pattern include means for determining at least one puncturing threshold associated with the location of a set of broadcasting channel resource blocks, and means for determining that a portion of a resource is punctured, according to the determination that the portion of the resource in the CORESET does not satisfy at least one puncturing threshold.

[0109] In some exemplary embodiments, a portion of a resource in a CORESET failing to satisfy at least one puncturing threshold includes at least one of the following: one or more resource blocks in the CORESET are located below the lowest broadcasting channel resource block, or one or more resource blocks in the CORESET are located above the highest broadcasting channel resource block.

[0110] In some exemplary embodiments, at least one puncturing threshold is determined based on an offset to at least one of the lowest broadcasting channel resource blocks or the highest broadcasting channel resource block.

[0111] In some exemplary embodiments, the first apparatus further includes means for determining that a portion of a punctured resource in the CORESET includes at least one sub-resource block, according to the determination that a puncturing threshold is determined based on an offset relative to the position of a set of broadcasting channel resource blocks, the offset having the granularity of a subcarrier.

[0112] In some exemplary embodiments, the first apparatus further includes means for determining that a CORESET puncturing pattern requires the CORESET to be punctured at the granularity of a control channel element CCE, and that, following the determination that at least one resource block in the CCE is punctured, a second portion of further resource blocks in the CCE is punctured.

[0113] In some exemplary embodiments, whether further resource blocks within the CCE are punctured is determined based on a threshold.

[0114] In some exemplary embodiments, the first device further includes means for determining that only at least one specific index associated with a particular type of CORESET is valid, according to the determination that a synchronous raster point is associated with at least one of a particular bandwidth or a specific bandwidth; and means for determining that one or more specific resource blocks associated with at least one specific index are punctured, wherein the at least one specific index is indicated by a master information block.

[0115] In some exemplary embodiments, the first device further includes means for determining that at least one particular index associated with a particular type of CORESET is valid if the associated CORESET contains up to 20 RBs after a puncturing operation.

[0116] In some exemplary embodiments, the first device includes a terminal device, and the second device includes a network device.

[0117] In some exemplary embodiments, the first apparatus further includes means for performing other operations in some exemplary embodiments of Method 500 or the first apparatus 110. In some exemplary embodiments, the means include at least one processor and at least one memory for storing instructions that, when executed by the at least one processor, cause the first apparatus to perform operations.

[0118] In some exemplary embodiments, a second apparatus capable of performing any of the methods 600 (e.g., the second apparatus 120 in Figure 1) may include means for performing each operation of the methods 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module. The second apparatus may be implemented as the second apparatus 120 in Figure 1, or may be included in the second apparatus 120 in Figure 1.

[0119] In some exemplary embodiments, the second device includes means for indicating to the first device that a particular type of CORESET is punctured by transmitting a synchronization signal block at a specific frequency position, and means for transmitting downlink control information to the first device, based at least on the portion of the CORESET resources that is not punctured.

[0120] In some exemplary embodiments, a particular type of CORESET is CORESET#0.

[0121] In some exemplary embodiments, the second device further includes means for indicating that a particular type of CORESET is punctured by additional information in a master information block.

[0122] In some exemplary embodiments, a specific frequency position is associated with the position of a synchronization raster point in the frequency domain.

[0123] In some exemplary embodiments, the first device includes a terminal device, and the second device includes a network device.

[0124] In some exemplary embodiments, the second apparatus further includes means for performing other operations in some exemplary embodiments of Method 600 or the second apparatus 120. In some exemplary embodiments, the means include at least one processor and at least one memory for storing instructions that, when executed by the at least one processor, cause the second apparatus to execute.

[0125] Figure 7 is a simplified block diagram of a device 700 suitable for carrying out exemplary embodiments of the present disclosure. The device 700 may be provided for carrying out a communication device, for example, the first device 110 or the second device 120 shown in Figure 1. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processors 710, and one or more communication modules 740 coupled to the processors 710.

[0126] The communication module 740 is for bidirectional communication. The communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interfaces necessary for communication with other network elements. In some exemplary embodiments, the communication module 740 may include at least one antenna.

[0127] The processor 710 may be of any type suitable for a local technology network and may include, in non-limiting examples, one or more of general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multicore processor architectures. The device 700 may have multiple processors, such as application-specific integrated circuit chips that are temporally slaves to a clock synchronized with the main processor.

[0128] Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact discs (CDs), digital video discs (DVDs), optical discs, laser discs, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random-access memory (RAM) 722 and other volatile memories that do not persist during power-down periods.

[0129] The computer program 730 includes computer-executable instructions that are executed by the associated processor 710. The instructions in program 730 may include instructions for performing actions / operations in some exemplary embodiments of the present disclosure. Program 730 may be stored in memory, for example, ROM 724. The processor 710 may perform any appropriate actions and operations by loading program 730 into RAM 722.

[0130] Exemplary embodiments of the present disclosure may be implemented by program 730 so that device 700 can perform any process of the disclosure as described with reference to Figures 2 to 6. Exemplary embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0131] In some exemplary embodiments, the program 730 may be tangibly contained in a computer-readable medium that may be contained in device 700 (such as memory 720) or other storage devices accessible by device 700. Device 700 may load the program 730 from the computer-readable medium into RAM 722 for execution. In some exemplary embodiments, the computer-readable medium may include any type of non-temporary storage medium such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term “non-temporary” as used herein is a limitation of the medium itself (i.e., tangible and not signaling), and not a limitation of data storage persistence (e.g., RAM vs. ROM).

[0132] Figure 8 shows an example of a computer-readable medium 800, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 800 has a program 730 stored thereon.

[0133] In general, various embodiments of the present disclosure may be implemented in hardware, dedicated circuitry, software, logic, or any combination thereof. Some embodiments may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Various embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or any other graphic representation, but it should be understood that any blocks, apparatus, systems, techniques, or methods described herein may be implemented, in non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers, or other computing devices, or any combination thereof.

[0134] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored in a computer-readable medium, such as a non-temporary computer-readable medium. The computer program product includes computer-executable instructions, such as those contained in a program module, running on a device on a target physical or virtual processor, for performing any of the methods described above. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. The functionality of a program module may be combined or separated as desired in various embodiments. The computer-executable instructions for a program module may run in a local or distributed device. In a distributed device, the program module may reside in both a local storage medium and a remote storage medium.

[0135] Program code for performing the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device such that when the program code is executed by the processor or controller, the functions / operations specified in the flowchart and / or block diagram are performed. The program code may be executed entirely on a computer, partially on a computer, as a standalone software package, partially on a computer and partially on a remote computer, or entirely on a remote computer or server.

[0136] In the context of this disclosure, computer program code or related data may be executed by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, and the like.

[0137] Computer-readable media may be computer-readable signal media or computer-readable storage media. Computer-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media include electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0138] Furthermore, although the operations are shown in a specific order, this should not be understood as requiring that such operations be performed in a specific illustrated or sequential order, or that all illustrated operations be performed to achieve a desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although the above description includes details of several specific embodiments, these should not be construed as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Unless expressly stated, certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the other hand, unless expressly stated, various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable partial combination.

[0139] While this disclosure has been described using terminology specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the attached claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. The first device, At least one processor, At least one memory, which, when executed by the at least one processor, provides at least the first device Based at least on the detection of a synchronization signal block received from a second device, determine whether a specific type of control resource set (CORESET) is punctured at a specific frequency position, and determine that the punctured portion of the CORESET of the specific type cannot carry downlink control information. Obtaining a CORESET puncturing pattern in accordance with the determination that the CORESET of the aforementioned specific type is punctured, Determining the portion of the punctured resource within the CORESET based at least on the CORESET puncturing pattern, At least one memory to store the instruction to perform the action, A first device comprising the following:

2. The first apparatus according to claim 1, wherein the aforementioned specific type of CORESET is CORESET #0.

3. The aforementioned device is The primary or secondary synchronization signal is detected at the specified frequency position, or Additional confirmation regarding CORESET puncturing is obtained from the master information block. The first apparatus according to claim 1 or 2, wherein it is determined that the particular type of CORESET is punctured according to at least one of the following determinations.

4. The first apparatus according to any one of claims 1 to 3, wherein the specific frequency position is associated with the position of a synchronization raster point in the frequency domain.

5. The acquisition of the aforementioned CORESET puncturing pattern is Determining at least one puncturing threshold associated with the location of a set of broadcasting channel resource blocks, The determination that the portion of the resource within the CORESET does not satisfy the at least one puncturing threshold, and that the portion of the resource is punctured, The first apparatus according to any one of claims 1 to 4, including

6. The portion of the resource within the CORESET that does not satisfy the at least one puncturing threshold means that One or more resource blocks of the aforementioned CORESET are located below the lowest broadcasting channel resource block, or One or more resource blocks of the aforementioned CORESET are located above the highest broadcasting channel resource block. The first apparatus according to claim 5, comprising at least one of the following.

7. The aforementioned at least one puncturing threshold is Minimum broadcasting channel resource block, or Highest broadcasting channel resource block, The first apparatus according to claim 5, determined based on an offset for at least one of the following:

8. The aforementioned device is The first apparatus according to claim 7, wherein the puncturing threshold is determined based on an offset of the set of broadcasting channel resource blocks relative to the position, and according to the determination that the offset has subcarrier granularity, it is determined that the punctured portion of the resource in the CORESET includes at least one sub-resource block.

9. The aforementioned device is The first apparatus according to any one of claims 1 to 4, wherein the CORESET puncturing pattern requires that the CORESET be punctured at the granularity of a control channel element CCE, and according to the determination that at least one resource block in the CCE is punctured, it is determined that a second portion of further resource blocks in the CCE is punctured.

10. The first apparatus according to claim 8, wherein whether the further resource blocks within the CCE are punctured is determined based on a threshold.

11. The aforementioned device is The aforementioned synchronized raster point is A specific bandwidth, or Specific bandwidth, In accordance with the determination that it relates to at least one of the above, it is determined that only at least one specific index associated with the CORESET of the particular type is valid. The first device according to claim 4, wherein it is determined that one or more specific resource blocks associated with the at least one specific index are punctured, and the at least one specific index is indicated by a master information block.

12. The first apparatus is The first apparatus according to claim 11, wherein it is determined that the at least one specific index associated with the specific type of CORESET is valid if the associated CORESET contains up to 20 RB after a puncturing operation.

13. The first device according to claims 1 to 11, wherein the first device includes a terminal device, and the second device includes a network device.

14. The second device, At least one processor, At least one memory, which, when executed by the at least one processor, provides at least the second device To the first device, a synchronization signal block is transmitted at a specific frequency position to indicate that a specific type of control resource set CORESET is punctured. To transmit downlink control information to the first device, based at least on the unpunctured portion of the CORESET resource, At least one memory to store the instruction to perform the action, A second device equipped with the following.

15. The second apparatus according to claim 14, wherein the aforementioned specific type of CORESET is CORESET #0.

16. The aforementioned device is The second apparatus according to claim 14 or 15, wherein the fact that the CORESET of a particular type is punctured is indicated by additional information in a master information block.

17. The second apparatus according to any one of claims 14 to 16, wherein the specific frequency position is associated with the position of a synchronization raster point in the frequency domain.

18. The second device according to any one of claims 14 to 17, wherein the first device includes a terminal device, and the second device includes a network device.

19. It is a method, In the first device, it is determined, at least based on the detection of a synchronization signal block received from the second device, whether a control resource set of a specific type is punctured at a specific frequency position, and that the punctured portion of the resource within the CORESET of the specific type cannot carry downlink control information. Obtaining a CORESET puncturing pattern in accordance with the determination that the CORESET of the aforementioned specific type is punctured, Determining the portion of the punctured resource within the CORESET based at least on the CORESET puncturing pattern, Methods that include...

20. It is a method, The second device transmits a synchronization signal block to the first device at a specific frequency position to indicate that a specific type of control resource set CORESET is punctured. To transmit downlink control information to the first device, based at least on the unpunctured portion of the CORESET resource, Methods that include...

21. The first device, A means for determining whether a specific type of control resource set CORESET is punctured at a specific frequency position, based at least on the detection of a synchronization signal block received from a second device, wherein the punctured portion of the CORESET of the specific type is unable to carry downlink control information. Means for obtaining a CORESET puncturing pattern in accordance with the determination that the CORESET of a specific type is punctured, Means for determining the portion of the punctured resource within the CORESET based at least on the CORESET puncturing pattern, A first device comprising the following:

22. The second device, A means for indicating that a specific type of control resource set CORESET is punctured by transmitting a synchronization signal block at a specific frequency position to the first device, Means for transmitting downlink control information to the first device, based at least on the unpunctured portion of the CORESET resources, A second device equipped with the following.

23. A computer-readable medium comprising instructions stored on the computer-readable medium for causing a device to perform at least the method according to claim 19 or the method according to claim 20.

Images