Method and apparatus for designing a CORESET for a UE supporting NR IOT applications
By designing CORESET with more than three OFDM symbols and appropriate frequency domain resource configuration, the problem of insufficient coverage and channel utilization efficiency of NR IoT applications is solved, and the requirements of NR IoT applications with high data rates and low latency are achieved.
Patent Information
- Application Number
- CN201980098778.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-08-16
- Publication Date
- 2025-05-06
- Estimated Expiration
- 2039-08-16
AI Technical Summary
The coverage and channel utilization efficiency of existing NR IoT applications are insufficient, resulting in the inability to meet the high data rate and low latency requirements of NR IoT applications.
By designing a control resource set (CORESET) designed for user equipment (UE) supporting NR IoT applications, the CORESET occupies more than three orthogonal frequency division multiplexing (OFDM) symbols in the time domain and configures appropriate resource blocks in the frequency domain to improve the transmission efficiency and channel utilization efficiency of the downlink control channel.
Improved coverage and channel utilization efficiency of NR IoT applications, meets the needs of NR IoT applications for high data rates and low latency, and reduces the implementation complexity and power consumption of NR UEs.
Smart Images

Figure CN114175787B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present application generally relate to 5G wireless communication technology in the Third Generation Partnership Project (3GPP), and more particularly to technology for designing a control resource set (CORESET) for a user equipment (UE) supporting New Radio (NR) Internet of Things (IoT) applications. Background Art
[0002] In 3GPP Release 17, NR-based IoT applications are also named NR-lite, NR-light, NR Machine Type Communication (MTC), NR Internet of Things, or Massive MTC (mMTC). 3GPP 5G NR-based IoT applications are designed to address new use cases with IoT-type requirements that cannot be met by LTE enhanced machine type communication (eMTC) applications and LTE narrowband (NB)-IoT applications. For example, IoT-type requirements include low complexity, enhanced coverage, long battery life, a large number of devices, higher data rates, and / or lower latency. 3GPP 5G NR-IoT applications are designed to meet some of these requirements that cannot be achieved by LTE eMTC applications and LTE NB-IoT applications. To achieve the above goals, technologies for designing CORESET for UEs that support NR IOT applications are developed. Summary of the invention
[0003] Some embodiments of the present application provide a method for wireless communication performed by a base station (BS). The method includes: transmitting signaling to configure a control region on a broadband carrier to a user equipment (UE), wherein the control region occupies more than three orthogonal frequency division multiplexing (OFDM) symbols in the time domain; and transmitting a downlink control channel within the control region to the UE.
[0004] Some embodiments of the present application also provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuit system; a transmitting circuit system; and a processor coupled to the non-transitory computer-readable medium, the receiving circuit system, and the transmitting circuit system, wherein the computer-executable instructions cause the processor to implement the above method performed by the BS.
[0005] Some embodiments of the present application provide a method for wireless communication performed by a UE. The method includes: receiving signaling for configuring a control region on a broadband carrier from a BS, wherein the control region occupies more than three OFDM symbols in the time domain; and receiving a downlink control channel within the control region from the BS.
[0006] Some embodiments of the present application provide a device for wireless communication. The device includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuit system; a transmitting circuit system; and a processor coupled to the non-transitory computer-readable medium, the receiving circuit system, and the transmitting circuit system, wherein the computer-executable instructions cause the processor to implement the above method performed by the UE. BRIEF DESCRIPTION OF THE DRAWINGS
[0007] In order to describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is presented by reference to specific embodiments of the present application illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered to limit its scope.
[0008] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application.
[0009] Figure 2 An exemplary IoT sub-band deployment according to some embodiments of the present application is described.
[0010] Figure 3 An exemplary CORESET configuration according to some embodiments of the present application is described.
[0011] Figure 4 Further exemplary CORESET configurations according to some embodiments of the present application are described.
[0012] Figure 5 Additional exemplary CORESET configurations according to some embodiments of the present application are described.
[0013] Figure 6 Additional exemplary CORESET configurations according to some embodiments of the present application are described.
[0014] Figure 7 Additional exemplary CORESET configurations according to some embodiments of the present application are described.
[0015] Figure 8 Further exemplary CORESET configurations according to some embodiments of the present application are described.
[0016] Fig. 9 Additional exemplary CORESET configurations according to some embodiments of the present application are described.
[0017] Fig.10 A flow chart illustrating a method for wireless communication according to some embodiments of the present application.
[0018] Fig.11Another flow chart illustrating a method for wireless communication according to some embodiments of the present application.
[0019] Fig.12 A block diagram illustrating an exemplary apparatus according to some embodiments of the present application. DETAILED DESCRIPTION
[0020] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application, rather than being intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be implemented by different embodiments intended to be included in the spirit and scope of the present application.
[0021] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service scenarios (e.g., 3GPP 5G, 3GPP LTE Release 8, etc.). It is considered that, with the development of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems; and in addition, the terms cited in the present application may be changed, which should not affect the principles of the present application.
[0022] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application.
[0023] like Figure 1 , a wireless communication system 100 includes at least one user equipment (UE) 101 and at least one base station (BS) 102. Specifically, for illustration purposes, the wireless communication system 100 includes two UEs 101 (eg, UE 101a and UE 101b) and one BS 102. Figure 1 A specific number of UEs 101 and BSs 102 are depicted in FIG. 1 , but it is contemplated that any number of UEs 101 and BSs 102 may be included in the wireless communication system 100 .
[0024] (Multiple) UE 101 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs), tablet computers, smart TVs (e.g., TVs connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle-mounted computers, network devices (e.g., routers, switches, and modems), etc. According to some embodiments of the present application, (multiple) UE 101 may include portable wireless communication devices, smart phones, cellular phones, flip phones, devices with subscriber identity modules, personal computers, selective call receivers, or any other devices capable of sending and receiving communication signals on a wireless network. In some embodiments of the present application, (multiple) UE 101 includes wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. In addition, (multiple) UE 101 may be referred to as subscriber units, mobile phones, mobile stations, users, terminals, mobile terminals, wireless terminals, fixed terminals, subscriber stations, user terminals, or devices, or described using other terms used in the art. (Multiple) UE 101 may communicate directly with BS 102 via uplink (UL) communication signals.
[0025] In some embodiments of the present application, each of (multiple) UEs 101 may deploy IoT applications, eMBB applications, and / or URLLC applications. For example, UE 101a may implement IoT applications and may be named IoT UE, while UE 101b may implement eMBB applications and / or URLLC applications and may be named eMBB UE, URLLC UE, or eMBB / URLLC UE. It is contemplated that (multiple) specific types of applications deployed in UE 101 may vary without limitation.
[0026] (Multiple) BSs 102 may be distributed over a geographic area. In certain embodiments of the present application, each of (multiple) BSs 102 may also be referred to as an access point, an access terminal, a base station, a base station unit, a macro cell, a Node B, an evolved Node B (eNB), a gNB, a native Node B, a relay node or a device, or described using other terms used in the art. (Multiple) BSs 102 are typically part of a wireless access network that may include one or more controllers communicatively coupled to one or more corresponding BSs 102.
[0027] The wireless communication system 100 may be compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 may be compatible with a wireless communication network, a cellular telephone network, a network based on time division multiple access (TDMA), a network based on code division multiple access (CDMA), a network based on orthogonal frequency division multiple access (OFDMA), an LTE network, a network based on 3GPP, a 3GPP 5G network, a satellite communication network, a high altitude platform network, and / or other communication networks.
[0028] In some embodiments of the present application, the wireless communication system 100 may be compatible with 5G NR of the 3GPP protocol, wherein (multiple) BSs 102 transmit data using an OFDM modulation scheme on the DL, and (multiple) UEs 101 transmit data using a discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) or cyclic prefix OFDM (CP-OFDM) scheme on the UL. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocols (e.g., WiMAX) as well as other protocols.
[0029] In some embodiments of the present application, (multiple) BS 102 may communicate using other communication protocols, such as the IEEE 802.11 series of wireless communication protocols. In addition, in some embodiments of the present application, (multiple) BS 102 may communicate via licensed spectrum, while in other embodiments, (multiple) BS 102 may communicate via unlicensed spectrum. The present application is not intended to be limited to implementations of any particular wireless communication system architecture or protocol. In still other embodiments of the present application, (multiple) BS 102 may communicate with (multiple) UE 101 using 3GPP 5G protocols.
[0030] In the 3GPP LTE eMTC protocol, the physical layer channel design is based on a bandwidth of 1.4 MHz, because 1.4 MHz is the minimum supported LTE bandwidth. With a minimum bandwidth of 1.4 MHz, eMTC devices can greatly reduce costs and implementation complexity. The 1.4 MHz bandwidth includes 6 physical resource blocks (PRBs), in which the LTE primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH) are accommodated in these 6 PRBs. Therefore, a UE with 1.4 MHz bandwidth capability can access a wideband carrier with a bandwidth greater than 1.4 MHz. In addition, in order to utilize frequency diversity gain, a UE with 1.4 MHz bandwidth capability can dynamically change its operating bandwidth from one subband to another, where each subband has a bandwidth of 1.4 MHz.
[0031] In 3GPP NR Release 15, the minimum bandwidth is defined as 5MHz. PSS, SSS and PBCH are designed to occupy 20 resource blocks (RBs) regardless of the subcarrier spacing. Therefore, for NR IoT applications, if the minimum bandwidth is less than 5MHz and the subcarrier spacing is 15kHz, or if the minimum bandwidth is less than 10MHz and the subcarrier spacing is 30kHz, it is inevitable to redesign the new PSS / SSS / PBCH, which leads to huge standardization work. Therefore, for NRIoT applications with a subcarrier spacing of 15kHz, 5MHz should be the minimum bandwidth. In addition, for a subcarrier spacing of 30kHz, 10MHz should be the minimum bandwidth for NR IoT applications.
[0032] Existing NR UEs have very high costs in terms of implementation, complexity, and power consumption. For example, an NR UE may require 100MHz bandwidth for FR1 or 200MHz bandwidth for FR2, at least 2 Rx antennas or 4 Rx antennas, dynamic time division duplex (TDD), 15kHz, 30kHz, or 60kHz subcarrier spacing (SCS) for FR1, no always-on signal, etc. Therefore, it is necessary to customize existing NR features in terms of cost, implementation complexity, and power consumption for NR IoT use cases. In addition, the existing NR coverage may not meet the requirements of NR IoT applications. Therefore, coverage enhancement for NR IoT applications is also necessary.
[0033] The embodiments of the present application are intended to provide a solution for designing a CORESET for a UE supporting NR IoT applications, so as to further improve the channel utilization efficiency and the downlink control channel transmission efficiency. More details about the embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0034] Figure 2 An exemplary IoT sub-band deployment according to some embodiments of the present application is described. Figure 2 The embodiment deploys NR IoT applications in a broadband carrier within a time slot. Figure 2 As shown in FIG. 1 , a broadband carrier with a bandwidth of 20 MHz in a time slot is used to deploy NR IoT applications, eMBB applications and / or URLLC applications. For example, a sub-band 201 with a bandwidth of 5 MHZ is used to deploy NR IoT applications, such as Figure 2 Displayed in.
[0035] The synchronization signal (SS) / PBCH block is also referred to as an SSB or NR SSB. In some embodiments, the SSB may be transmitted using a 15kHz subcarrier spacing and occupies 20 RBs in the frequency domain. When deploying NR IoT applications, a simple approach is to reuse the existing SSB and the initial access procedure of the IoT UE so that the IoT UE can access the channel. Therefore, the IoT UE should have a minimum bandwidth capability of 5MHz with a 15kHz subcarrier spacing or a minimum bandwidth capability of 10MHz with a 30kHz subcarrier spacing so that the existing NR SSB can be reused to access the channel without designing a new SSB.
[0036] exist Figure 2 In the embodiment of FIG. 1 , assuming that a 5 MHz bandwidth with a 15 kHz subcarrier spacing is used for an NR IoT application, the IoT UE will search for SSBs based on the synchronization raster and a given frequency band (e.g., Figure 2 SS / PBCH blocks shown in ). After the IoT UE completes the initial access procedure, the IoT UE can transmit or receive signals on a 5 MHz bandwidth with a 15 kHz subcarrier spacing. From the perspective of this IoT UE, it is operating on a carrier with a 5 MHz bandwidth.
[0037] In some embodiments of the present application, the NR IoT bandwidth is fixed to 5 MHz, and the subcarrier spacing of the NR IoT bandwidth is fixed to 15 kHz. In some other embodiments, the NR IoT bandwidth is fixed to 10 MHz, and the subcarrier spacing of the NR IoT bandwidth is fixed to 30 kHz. In some additional embodiments, the NR IoT bandwidth can be configured between 5 MHz, 10 MHz, 15 MHz, 20 MHz, or other bandwidths, and the subcarrier spacing of the NR IoT bandwidth can be configured between 15 kHz, 30 kHz, or other values.
[0038] A more general control channel structure designed in NR is the CORESET. A CORESET is a configured time-frequency resource where the UE attempts to decode a downlink control channel in one or more search spaces. For example, a UE may attempt to decode a physical downlink control channel (PDCCH) in one or more search spaces using a CORESET. Unlike the LTE PDCCH, the NR PDCCH does not necessarily span the full wideband carrier, as not all NR UEs are capable of receiving the full wideband carrier. The size and position of the CORESET in the time-frequency domain may be semi-statically configured by the BS. Therefore, the size of the CORESET may be set to be smaller than the wideband carrier. The CORESET is defined from the UE's perspective and only indicates where the UE can detect downlink control channels (e.g., PDCCH). The CORESET in NR may have a fixed size.
[0039] NR PDCCH consists of 1, 2, 4, 8 or 16 control channel elements (CCEs) depending on different channel conditions and coverage requirements. CCE consists of 6 resource element groups (REGs). REG represents one resource block (RB) in the frequency domain and one OFDM symbol in the time domain. In the time domain, the CORESET can be up to three OFDM symbols in duration and is usually located at the beginning of the time slot. The demodulation reference signal (DMRS) of the PDSCH can be located in the third OFDM symbol or the fourth OFDM symbol within a time slot. In response to the DMRS of the PDSCH being located in the third OFDM symbol of the time slot, the maximum duration of the CORESET occupies two OFDM symbols. In response to the DMRS of the PDSCH being located in the fourth OFDM symbol of the time slot, the maximum duration of the CORESET occupies three OFDM symbols. However, in some cases, such a CORESET configuration cannot accommodate one PDCCH with a specific aggregation level (AL).
[0040] Specifically, as defined in 3GPP 5G TS38.101, when NR IoT is deployed using a 5MHz bandwidth and a 15kHz subcarrier spacing, the maximum number of available RBs is 25. In Table 7.3.2.1-1 of 3GPP 5G TS38.211, a set of ALs is defined. Since each CCE includes 6 REGs, in response to a maximum of 3 OFDM symbols configured for the CORESET, the CORESET occupies 75 REGs, indicating that only 12 CCEs are available in the CORESET. When NR IoT requires coverage enhancement or reliability improvement of the PDCCH, this CORESET configuration cannot accommodate a PDCCH with an AL of 16, because a PDCCH with an AL of 16 requires at least 16 CCEs. On the other hand, the CORESET configuration in the frequency domain is defined in multiples of six common resource blocks (CRBs). From the perspective of the IoT UE, the six CRBs may not be aligned with the first PRB of the NR IoT bandwidth. Due to this reason, the total number of available REGs in the CORESET is further reduced.
[0041] Figure 3 An exemplary CORESET configuration according to some embodiments of the present application is described. Figure 3 In the embodiment, a time slot includes OFDM symbols 0 to 13. Figure 3 Point A in represents the position of subcarrier 0 of CRB 0, which is used as a common reference for RB index.
[0042] like Figure 3In Figure 1, 5 MHz bandwidth is used to deploy NR IoT applications. With 15 kHz subcarrier spacing, up to 25 RBs are available. When the first PRB in the IoT CORESET is aligned with the first CRB in a six-CRB group, up to 24 RBs can be configured for the NR IoT CORESET. When the master information block (MIB) indicates that the DMRS is located at Figure 3 , the NR IoT CORESET can have up to three OFDM symbols in the time domain, namely OFDM symbols 0 to 2, when the OFDM symbol 3 is marked in the figure. Since each CCE includes 6 REGs, the NR IoT CORESET includes 72 REGs (24x3=72 REGs) and 12 CCEs. Obviously, the 12 CCEs in the NR IoT CORESET can only support PDCCH with a maximum AL of 8. In this case, for the purpose of coverage enhancement and reliability improvement, it is necessary to enhance the CORESET configuration and PDCCH.
[0043] In some embodiments of the present application, the duration in the time domain and the bandwidth in the frequency domain of the NR IoT CORESET are preconfigured or configured by radio resource control (RRC) signaling. For example, the time domain duration of one NR IoT CORESET is configured to have more than 3 OFDM symbols, and the CORESET configuration of NR IoT ensures that the NR IoT CORESET does not cross the time slot boundary between two time slots.
[0044] For example, the NR IoT CORESET may be configured to include 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, or 14 OFDM symbols in one time slot. For another example, the NR IoT CORESET may be configured to include multiple OFDM symbols in one time slot, and the total number of OFDM symbols is an integer multiple of 6.
[0045] NR IoT CORESET with more than 3 OFDM symbols in one time slot may be continuous in the time domain. On the other hand, since the DMRS indicated by the MIB may exist in an OFDM symbol (e.g., OFDM symbol 2 or OFDM symbol 3), NR IoT CORESET with more than 3 OFDM symbols may be non-continuous in the time domain. If the NR IoT CORESET includes the DMRS indicated by the MIB located in OFDM symbol 2 or OFDM symbol 3, the DMRS indicated by the MIB in OFDM symbol 2 or OFDM symbol 3 is not included in the NR IoT CORESET.
[0046] REG represents one RB in the frequency domain and one OFDM symbol in the time domain. Considering the variable duration of NR IoT CORESET in the time domain, and the variable duration of NR IoT CORESET may not be a factor of 6 or an integer multiple of 6, compared with the NR version 15 standard document, the embodiment of the present application redesigns the numbering of REG.
[0047] REG represents an RB during an OFDM symbol. In some embodiments of the present application, within the NR IoT CORESET, REGs are numbered in ascending order in a frequency first and time second manner. Specifically, in the first OFDM symbol of the NR IoT CORESET, starting from REG 0 of the lowest numbered RB in the CORESET, then increasing the REG number of the second lowest numbered RB in the CORESET until the highest numbered RB in the CORESET; then, in the second OFDM symbol of the CORESET, increasing the REG number from the lowest numbered RB in the CORESET until the highest numbered RB in the CORESET; then, repeating the procedure in the third OFDM symbol of the CORESET until the last OFDM symbol of the CORESET.
[0048] Such an embodiment can maintain 6 REGs for one CCE and maintain the frequency domain resource configuration of the CORESET in a bitmap, where each bit in the bitmap corresponds to 6 consecutive RBs. In other words, the total number of RBs of the CORESET is an integer multiple of 6, which is very consistent with the size of one CCE. Figure 4 Specific examples are shown in .
[0049] Figure 4 Further CORESET configurations according to some embodiments of the present application are described. Figure 3 Similar to the embodiment of Figure 4 In the embodiment of the present invention, a time slot includes OFDM symbols 0 to 13, and as Figure 4 As shown in , the DMRS is located in OFDM symbol 3. Figure 4 The NR IoT CORESET shown in FIG. 1 includes 4 OFDM symbols (i.e., OFDM symbols 0 to 2 and OFDM symbol 4) and includes REGs 400 to 495 in total. Figure 4 The CORESET shown in Figure 1 is configured with frequency first and time second in the REG numbering format. Figure 4 In the NR IoT CORESET shown in Figure 1, REGs are numbered in ascending order with frequency first and time second.
[0050] like Figure 4As shown in FIG. 4 , since the DMRS indicated by the MIB exists in OFDM symbol 3, the NR IoT CORESET with 4 OFDM symbols is non-contiguous in the time domain. For example, REG 400 represents the lowest RB in the IoT CORESET during OFDM symbol 0; REG 424 represents the lowest RB in the IoT CORESET during OFDM symbol 1; REG 448 represents the lowest RB in the IoT CORESET during OFDM symbol 2; REG 472 represents the lowest RB in the IoT CORESET during OFDM symbol 4.
[0051] Specifically, according to Figure 4 In an embodiment, in OFDM symbol 0 of the CORESET, starting from REG 400 of the lowest numbered RB in the CORESET, the REG number of the second lowest numbered RB in the CORESET (i.e., REG 401) is then increased until the highest numbered RB in the CORESET (i.e., REG 423); in OFDM symbol 1 of the CORESET, the REG number is increased from the lowest numbered RB in the CORESET (i.e., REG 424) until the highest numbered RB in the CORESET (i.e., REG 447); in OFDM symbol 2 of the CORESET, the REG number is increased from the lowest numbered RB in the CORESET (i.e., REG 448) until the highest numbered RB in the CORESET (i.e., REG 471); and then, in OFDM symbol 4 of the CORESET, the REG number is increased from the lowest numbered RB in the CORESET (i.e., REG 472) until the highest numbered RB in the CORESET (i.e., REG 495).
[0052] More specifically, in Figure 4 In the embodiment of , the NR IoT application is deployed with a 5 MHz bandwidth and a 15 kHz subcarrier spacing, and there are a maximum of 25 RBs available for transmission. Therefore, there are a maximum of 25 REGs available for transmission in each OFDM symbol. In the case where there are 25 REGs available for transmission in OFDM symbol 0, only the first REG (i.e., REG 400) to the twenty-fourth REG (i.e., REG 423) in OFDM symbol 0 can be configured to be included in the NR IoT CORESET, because a maximum of 24 REGs can be configured for the CORESET in the frequency domain, where 24 is a multiple of 6. In other words, the CORESET does not include the twenty-fifth REG in OFDM symbol 0. Similarly, Figure 4 As shown in FIG. 1 , CORESET does not include the twenty-fifth REG in each of OFDM symbols 1, 2, and 4. Therefore, Figure 4An embodiment of the present invention maintains 6 REGs for one CCE and maintains the frequency domain resource configuration of the CORESET in a bitmap, wherein each bit in the bitmap corresponds to 6 consecutive RBs.
[0053] In some other embodiments of the present application, within the NR IoT CORESET, REGs are numbered in ascending order in a time-first frequency-second manner. Specifically, in the NR IoT CORESET, starting from REG 0 of the lowest numbered RB in the CORESET and in the first OFDM symbol of the CORESET, then increasing the REG number of the second OFDM symbol of the CORESET until the last OFDM symbol of the CORESET; then, in the second lowest numbered RB in the CORESET, increasing the REG number from the first OFDM symbol in the CORESET until the last OFDM symbol in the CORESET; and repeating the procedure in the third lowest numbered RB of the CORESET until the highest numbered RB in the CORESET.
[0054] This embodiment maintains the REG numbering order defined in NR Release 15. However, the duration of the NR IoT CORESET needs to be limited, that is, the duration of the NR IoT CORESET should be a factor of 6 or an integer multiple of 6. For example, the duration of one NR IoT CORESET can be 1, 2, 3, 6 or 12 consecutive OFDM symbols in a time slot. It should be noted that 1, 2 or 3 OFDM symbols cannot accommodate a PDCCH with a high AL. 6 or 12 OFDM symbols can easily bundle 6 consecutive REGs into one CCE. Figure 5 Specific examples are shown in .
[0055] Figure 5 Additional exemplary CORESET configurations according to some embodiments of the present application are described. Figure 3 and 4 Similar to the embodiment of Figure 5 In the embodiment of the present invention, a time slot includes OFDM symbols 0 to 13, and as Figure 5 As shown in , the DMRS is located in OFDM symbol 3. Figure 5 The NR IoT CORESET shown in FIG. 1 includes 6 OFDM symbols (i.e., OFDM symbols 0 to 2 and OFDM symbols 4 to 6) and includes REGs starting from REG 500. In addition, as Figure 5 The CORESET shown in Figure 1 is configured with REG numbering in a time-first, frequency-second order. In other words, in Figure 5 In the NR IoT CORESET shown in Figure 1, REGs are numbered in ascending order with time first and frequency second.
[0056] like Figure 5 As shown in FIG. 5 , the NR IoT CORESET with 6 OFDM symbols is non-contiguous in the time domain because the DMRS indicated by the MIB is present in OFDM symbol 3. For example, REG 500 represents the lowest RB in the IoT CORESET during OFDM symbol 0; REG 501 represents the lowest RB in the CORESET during OFDM symbol 1; REG 502 represents the lowest RB in the CORESET during OFDM symbol 2; REG 503 represents the lowest RB in the CORESET during OFDM symbol 4; REG 504 represents the lowest RB in the CORESET during OFDM symbol 5; and REG 505 represents the lowest RB in the CORESET during OFDM symbol 6.
[0057] More specifically, according to Figure 5 In an embodiment of the present invention, in the NR IoT CORESET, starting from REG 500 of the lowest numbered RB in the CORESET and in OFDM symbol 0 of the CORESET, the REG number of OFDM symbol 1 of the CORESET (i.e., REG 501), the REG number of OFDM symbol 2 of the CORESET (i.e., REG 502), the REG number of OFDM symbol 4 of the CORESET (i.e., REG 503), the REG number of OFDM symbol 5 of the CORESET (i.e., REG 504), and the REG number of OFDM symbol 6 of the CORESET (i.e., REG 505) are sequentially increased respectively; then, in the second lowest numbered RB in the CORESET, the REG number is increased from OFDM symbol 0 in the CORESET (i.e., REG 506) until OFDM symbol 6 in the CORESET (i.e., REG 511); and in the third lowest numbered RB in the CORESET (i.e., REG 512 to REG 513), the REG number of OFDM symbol 4 of the CORESET (i.e., REG 503) is sequentially increased. 517) until the highest numbered RB in CORESET ( Figure 5 Specific REG numbers are not marked in the table). It may be considered that Figure 5 In the embodiment, 6 OFDM symbols can easily bundle 6 consecutive REGs into one CCE of the CORESET.
[0058] In some embodiments of the present application, two or more REGs may be bundled into one REG bundle for precoding. Specifically, the size of one REG bundle may be configured through RRC signaling according to the frequency domain and time domain configuration of the CORESET. The granularity of the precoder may be configured as the size of one REG bundle. Alternatively, the granularity of the precoder may be configured as all consecutive RBs in the frequency domain.
[0059] For example, the total number of REGs within one REG bundle is configured by RRC signaling in the frequency domain. For example, regardless of the duration of the CORESET in the time domain, 2, 3, 6, 12, 18, 24, 48, or 96 REGs may be bundled into one REG bundle, and therefore, the size of the REG bundle is 2, 3, 6, 12, 18, 24, 48, or 96 REGs.
[0060] For further examples, the total number of REGs within one REG bundle is configured by RRC signaling in the time domain. In this case, the size of the REG bundle can be an integer multiple of 6, 12, 18, 24, 48, 96, etc. For example, if 6 REGs in the frequency domain and 2 OFDM symbols in the time domain are bundled together, the size of one REG bundle is 12 REGs; if 6 REGs in the frequency domain and 3 OFDM symbols in the time domain are bundled together, the size of one REG bundle is 18 REGs; if 6 REGs in the frequency domain and 4 OFDM symbols in the time domain are bundled together, the size of the REG bundle is 24 REGs; if 6 REGs in the frequency domain and 8 OFDM symbols in the time domain are bundled together, or 12 REGs in the frequency domain and 4 OFDM symbols in the time domain are bundled together, the size of the REG bundle is 48 REGs.
[0061] Since a time slot contains 14 OFDM symbols in total (e.g. Figures 2 to 9 0 to 13 shown in the time slot), so the time domain duration of the long CORESET can be 13 OFDM symbols without considering the MIB-indicated DMRS present in OFDM symbol 2 or OFDM symbol 3 within the time slot. Alternatively, the time domain duration of the long CORESET can be 12 OFDM symbols without considering the MIB-indicated DMRS present in OFDM symbol 2 or OFDM symbol 3 and the additional DMRS present in the additional OFDM symbols within the time slot.
[0062] In some embodiments of the present application, a long CORESET occupies a portion of the NR IoT bandwidth. The portion of the NR IoT bandwidth includes one or more resource block groups (RBGs) in the frequency domain, and each RBG includes a predefined number of consecutive resource blocks in the frequency domain. For example, since the CORESET in the frequency domain is configured in groups of 6 consecutive RBs, the frequency resources of the CORESET may occupy one or more RBGs, and each RBG includes 6 RBs. One or more RBGs may be consecutive in the frequency domain to obtain frequency selective gain and more accurate channel estimation. In this case, the granularity of the precoder can be set to all consecutive RBs in the frequency domain. The remaining RBs in the frequency domain can be used for PDSCH transmission. Figure 6Specific examples are shown in .
[0063] Figure 6 Additional exemplary CORESET configurations according to some embodiments of the present application are described. Figure 6 Refers to the continuous CORESET configuration in the frequency domain for NR IoT applications. Figures 3 to 5 Similar to the embodiment of Figure 6 In the embodiment of FIG. 1 , a time slot includes OFDM symbols 0 to 13, and two DMRS symbols for PDSCH demodulation are located in OFDM symbols 3 and 11, as shown in FIG. Figure 6 Marked in . Figure 6 In the embodiment the CORESET duration is one time slot.
[0064] according to Figure 6 In the embodiment, assuming that two RBGs and 12 OFDM symbols are configured for the NR IoT CORESET, there are a total of 144 REGs (2x12x6=144 REGs) in the CORESET, and therefore there are a maximum of 24 CCEs (144 REGs / 6=24 CCEs) available for transmission. 24 CCEs can accommodate one PDCCH with an AL of 16 and another PDCCH with an AL of 8.
[0065] More specifically, according to Figure 6 In an embodiment of the present invention, each OFDM symbol includes three groups of 6 RBs (i.e., three RBGs) and the remaining RBs in the frequency domain, and the NR IoT CORESET includes two consecutive RBGs (e.g., Figure 6 The remaining RBs in the frequency domain in each OFDM symbol may be used for PDSCH transmission or PDCCH transmission of (multiple) other UEs.
[0066] In some other embodiments of the present application, the long CORESET occupies a portion of the NR IoT bandwidth, and the frequency resources of the long CORESET may occupy one or more RBGs that are not continuous in the frequency domain to obtain frequency diversity gain. The remaining RBs in the frequency domain can be used for PDSCH transmission. Figure 7 Specific examples are shown in .
[0067] Figure 7 Additional exemplary CORESET configurations according to some embodiments of the present application are described. Figure 7 Refers to non-contiguous CORESET configuration in the frequency domain for NR IoT applications. Figure 7 As depicted in FIG, two non-contiguous RBGs (eg, the first and third groups of 6 RBs) are used as CORESETs. Figures 3 to 6 Similar to the embodiment of Figure 7 In the embodiment of FIG. 1 , a time slot includes OFDM symbols 0 to 13, and two DMRS symbols for PDSCH demodulation are located in OFDM symbols 3 and 11, as shown in FIG. Figure 7 Marked in . Figure 7 In the embodiment the CORESET duration is one time slot.
[0068] according to Figure 7 In the embodiment, assuming that two RBGs and 12 OFDM symbols are configured for the NR IoT CORESET, there are a total of 144 REGs (2x12x6=144 REGs) in the CORESET, and therefore there are a maximum of 24 CCEs (144 REGs / 6=24 CCEs) available for transmission. 24 CCEs can accommodate one PDCCH with an AL of 16 and another PDCCH with an AL of 8.
[0069] More specifically, according to Figure 7 In an embodiment, each OFDM symbol includes three groups of 6 RBs (i.e., three RBGs) and the remaining RBs in the frequency domain, and the NR IoT CORESET includes two non-contiguous RBGs (e.g., Figure 7 The remaining RBs in the frequency domain in each OFDM symbol may be used for PDSCH transmission.
[0070] In case of the presence of MIB for DMRS indication in OFDM symbol 2 or OFDM symbol 3, for short CORESET configuration with full NR IoT bandwidth (e.g. Figure 4 and 5 In the embodiment of FIG. 1 , OFDM symbol 2 or OFDM symbol 3 is left blank in the area of the NR IoT bandwidth. This avoids interference of neighboring cells to the DMRS.
[0071] In case of the presence of MIB indicated by DMRS in OFDM symbol 2 or OFDM symbol 3, for long CORESET configuration with partial NR IoT bandwidth (e.g. Figure 6 and 7 In the embodiment of the present invention, OFDM symbol 2 or OFDM symbol 3 is left blank in the area of NR IoT CORESET and used as DMRS in the data area of NR IoT bandwidth.
[0072] For a CORESET containing 4 OFDM symbols in a 5 MHz bandwidth (e.g. Figure 4In some embodiments, each OFDM symbol includes 24 available REGs, and there are 96 available REGs in total in the CORESET, which corresponds to 16 CCEs in the CORESET. Therefore, a CORESET including 4 OFDM symbols is the minimum duration to accommodate a PDCCH with an AL of 16. In some embodiments, CORESET0, which transmits PDCCHs for scheduling system information blocks (SIBs) during the initial access procedure, has a default duration of 4 OFDM symbols and a default width of 24 consecutive RBs. In some other embodiments, the duration and / or width of CORESET 0 is configured by RRC signaling, and the width of CORESET 0 is configured to have the number of RBGs indicated in the MIB.
[0073] In some other embodiments of the present application, the index of the lowest numbered RB in the control resource set and the index of the lowest numbered RB in the wideband carrier are offset relative to the same subcarrier spacing by an integer multiple of 6. The lowest numbered RB in the wideband carrier may be CRB 0, where subcarrier 0 of CRB 0 is aligned with point A (e.g., Figure 3 The NRIoT CORESET configuration in the frequency domain is aligned with the boundary of the group of 6 consecutive CRBs. For example, Figure 6 and 7 The groups of 6 RBs in the embodiment may be aligned with the boundary(s) between the groups of 6 CRBs within the NR IoT bandwidth. The index of the CRB corresponding to the lowest numbered RB within the NR IoT bandwidth is an integer multiple of 6. Thus, since a maximum of 24 REGs may be configured for the NR IoT CORESET, a maximum of four groups of 6 CRBs within the NR IoT bandwidth may be configured for the NR IoT CORESET.
[0074] According to some embodiments of the present application, two or more CORESETs are configured in the same time slot, and the two or more CORESETs in the time slot are combined to transmit one PDCCH with a high aggregation level (AL). The duration of each CORESET of the combined CORESET is no more than 3 consecutive OFDM symbols, and the duration of each CORESET is related to the DMRS position in the OFDM symbol indicated in the MIB.
[0075] For example, if OFDM symbol 2 is indicated in the MIB for DMRS, the duration of each CORESET is no greater than 2 due to the presence of DMRS in OFDM symbol 2. Alternatively, the duration of the first CORESET may be no greater than 2, while the other CORESETs may have a duration greater than 2 OFDM symbols. If OFDM symbol 3 is indicated in the MIB for DMRS, the duration of each CORESET is no greater than 3 due to the presence of DMRS in OFDM symbol 3. Alternatively, the duration of the first CORESET may be no greater than 3, while the other CORESETs may have a duration greater than 3 OFDM symbols.
[0076] According to the embodiment described above, Figure 4 Similar to the embodiment in , the REG numbering in each CORESET of the combined CORESET can be in a frequency first time second manner. Alternatively, similar to Figure 5 In the embodiment, the REG number in each CORESET of the combined CORESET can be in the manner of time first and frequency second. The CORESETs in a time slot can be concatenated in REG number or CCE number. When the first CORESET cannot accommodate a PDCCH with a high AL, the CCE in the second CORESET is used starting from the first CCE of the second CORESET to accommodate the PDCCH. Figure 8 Specific examples are shown in .
[0077] Figure 8 Another exemplary CORESET configuration according to some embodiments of the present application is described. Figure 8 In the embodiment, CCEs in two CORESETs are concatenated for one PDCCH transmission, and each CORESET uses a frequency-first, time-second REG numbering scheme.
[0078] and Figures 3 to 7 Similar to the embodiment of Figure 8 In the embodiment of the present invention, a time slot includes OFDM symbols 0 to 13, and as Figure 8 As shown in , the DMRS is located in OFDM symbol 3. Figure 8 The NR IoT CORESET 1 shown in FIG. 1 includes 3 OFDM symbols (i.e., OFDM symbols 0 to 2) and a total of REGs 800 to 871. Figure 8 The NR IoT CORESET 2 shown in FIG. 1 includes 3 OFDM symbols (i.e., OFDM symbols 4 to 6) and a total of REGs 872 to 943. In addition, as Figure 8 Both CORESET 1 and CORESET 2 shown in FIG. 5 are configured with REG numbering in the order of frequency first and time second.
[0079] More specifically, according to Figure 8 In an embodiment, in OFDM symbol 0 of CORESET 1, starting from REG 800 of the lowest numbered RB in CORESET 1, the REG number of the second lowest numbered RB in CORESET 1 (i.e., REG 801) is then increased until the highest numbered RB in CORESET 1 (i.e., REG 823); then, in OFDM symbol 1 of CORESET 1, the REG number is increased from the lowest numbered RB in CORESET 1 (i.e., REG 824) to the highest numbered RB in CORESET 1 (i.e., REG 847); and then, in OFDM symbol 2 of CORESET 1, the REG number is increased from the lowest numbered RB in CORESET 1 (i.e., REG 848) to the highest numbered RB in CORESET 1 (i.e., REG 871).
[0080] Similarly, in OFDM symbol 4 of CORESET 2, starting from REG 872 of the lowest numbered RB in CORESET 2, the REG number of the second lowest numbered RB in CORESET 2 (i.e., REG 873) is then increased until the highest numbered RB in CORESET 2 (i.e., REG 895); and then, in OFDM symbol 5 of CORESET 2, the REG number is increased from the lowest numbered RB in CORESET 2 (i.e., REG 896) until the highest numbered RB in CORESET 2 (i.e., REG 919); and then, in OFDM symbol 6 of CORESET 2, the REG number is increased from the lowest numbered RB in CORESET 2 (i.e., REG 920) until the highest numbered RB in CORESET 2 (i.e., REG 943).
[0081] according to Figure 8 In an embodiment of the present invention, the NR IoT application is deployed with a 5 MHz bandwidth and a 15 kHz subcarrier spacing, and there are a maximum of 25 RBs available for transmission. Therefore, there are a maximum of 25 REGs available for transmission in each OFDM symbol. In the case where there are 25 REGs available for transmission in OFDM symbol 0, only the first REG (i.e., REG 800) to the twenty-fourth REG (i.e., REG 823) in OFDM symbol 0 can be configured to be included in CORESET 1, because a maximum of 24 REGs can be configured for CORESET 1. In other words, CORESET 1 does not include the twenty-fifth REG in OFDM symbol 0. Similarly, Figure 8, CORESET 1 does not include the 25th REG in each of OFDM symbols 1 and 2. CORESET 2 does not include the 25th REG in each of OFDM symbols 4, 5, and 6. Therefore, Figure 8 In an embodiment, one CCE maintains 6 REGs, and maintains the frequency domain resource configuration of CORESET 1 and CORESET 2 in a bitmap, wherein each bit in the bitmap corresponds to 6 consecutive RBs.
[0082] According to some other embodiments of the present application, two or more CORESETs are configured in different time slots, and the two or more CORESETs in different time slots are combined to transmit one PDCCH with a high AL. The duration of each CORESET of the combined CORESET is no more than 3 OFDM symbols, and the duration of each CORESET is related to the DMRS position in the OFDM symbol indicated in the MIB. For example, if OFDM symbol 2 is indicated in the MIB of DMRS, the duration of each CORESET is no more than 2. If OFDM symbol 3 is indicated in the MIB of DMRS, the duration of each CORESET is no more than 3.
[0083] According to the embodiment described above, the periodicity and offset of a PDCCH transmission may be configured by RRC signaling, wherein two or more CORESETs in the periodicity are concatenated with REG numbers or CCE numbers. Figure 4 and 5 Similar to the embodiment in, the REG number in each CORESET of the combined CORESET can be in the manner of frequency first and time second or time first and frequency second. When the first CORESET cannot accommodate the PDCCH with a high AL, the CCE in the second CORESET is used starting from the first CCE of the second CORESET to accommodate the PDCCH. Fig. 9 Specific examples are shown in .
[0084] Fig. 9 Additional exemplary CORESET configurations according to some embodiments of the present application are described. Fig. 9 In the embodiment of FIG. 1 , CCEs in two CORESETs are concatenated for one PDCCH transmission, and each CORESET uses a REG numbering scheme of frequency first and time second. In other words, in Figures 3 to 8 In the embodiment of , a PDCCH transmission cycle includes one time slot; and Fig. 9 In the embodiment, one PDCCH transmission period includes two time slots.
[0085] Specifically, Fig. 9The embodiment of shows two time slots, time slot 1 and time slot 2. Figures 3 to 8 Similar to the embodiment of Fig. 9 In the embodiment of FIG. 1 , each time slot contains OFDM symbols 0 to 13, and as Fig. 9 As shown in , DMRS is located in OFDM symbol 3 in each time slot. Fig. 9 The NR IoT CORESET 1 shown in FIG. 1 includes 3 OFDM symbols (i.e., OFDM symbols 0 to 2 in slot 1) and a total of REGs 100 to 171. Fig. 9 The NR IoT CORESET 2 shown in FIG. 2 includes 3 OFDM symbols (i.e., OFDM symbols 0 to 2 in slot 2) and a total of REGs 172 to 243. In addition, as Fig. 9 Both CORESET 1 and CORESET 2 shown in FIG. 5 are configured with REG numbering in the order of frequency first and time second.
[0086] More specifically, according to Fig. 9 In an embodiment, in OFDM symbol 0 in time slot 1 of CORESET 1, starting from REG 100 of the lowest numbered RB in CORESET 1, the REG number of the second lowest numbered RB in CORESET 1 (i.e., REG 101) is then increased until the highest numbered RB in CORESET 1 (i.e., REG 123); in OFDM symbol 1 in time slot 1 of CORESET 1, the REG number is increased from the lowest numbered RB in CORESET 1 (i.e., REG 124) to the highest numbered RB in CORESET 1 (i.e., REG 147); and then, in OFDM symbol 2 in time slot 1 of CORESET 1, the REG number is increased from the lowest numbered RB in CORESET 1 (i.e., REG 148) to the highest numbered RB in CORESET 1 (i.e., REG 171).
[0087] Similarly, in OFDM symbol 0 in time slot 2 of CORESET 2, start from REG 172 of the lowest numbered RB in CORESET 2, and then increase the REG number of the second lowest numbered RB in CORESET 2 (i.e., REG 173) until the highest numbered RB in CORESET 2 (i.e., REG 195); in OFDM symbol 1 in time slot 2 of CORESET 2, increase the REG number from the lowest numbered RB in CORESET 2 (i.e., REG 196) until the highest numbered RB in CORESET 2 (i.e., REG 219); and then, in OFDM symbol 2 in time slot 2 of CORESET 2, increase the REG number from the lowest numbered RB in CORESET 2 (i.e., REG 220) until the highest numbered RB in CORESET 2 (i.e., REG 243).
[0088] according to Fig. 9 In an embodiment of the present invention, the NR IoT application is deployed with a 5 MHz bandwidth and a 15 kHz subcarrier spacing, and there are a maximum of 25 RBs available for transmission. Therefore, there are a maximum of 25 REGs available for transmission in each OFDM symbol in each time slot. In the case where there are 25 REGs available for transmission in OFDM symbol 0 in time slot 1, only the first REG (i.e., REG 100) to the twenty-fourth REG (i.e., REG 123) in OFDM symbol 0 can be configured to be included in CORESET 1, because a maximum of 24 REGs can be configured for CORESET 1. In other words, CORESET 1 does not include the twenty-fifth REG in OFDM symbol 0 in time slot 1. Similarly, Fig. 9 As shown in FIG. 1 , CORESET 1 does not include the twenty-fifth REG in each of OFDM symbols 1 and 2 in slot 1. CORESET 2 does not include the twenty-fifth REG in each of OFDM symbols 0, 1, and 2 in slot 2. Therefore, Fig. 9 In an embodiment, one CCE maintains 6 REGs, and maintains the frequency domain resource configuration of CORESET 1 and CORESET 2 in a bitmap, wherein each bit in the bitmap corresponds to 6 consecutive RBs.
[0089] It can be considered that Figure 8 and 9 Each CORESET in the embodiment may alternatively use a REG numbering scheme of time first and frequency second. The details are similar to Figure 5 Embodiment of the invention.
[0090] Fig.10 A flow chart illustrating a method for wireless communication according to some embodiments of the present application.
[0091] In such Fig.10 In the exemplary method 1000 shown in FIG. 1 , in operation 1001, a BS (e.g., Figure 1 BS102 shown in FIG. 102 ) to a UE (eg, Figure 1 101a) transmits signaling for configuring a control region on a wideband carrier, wherein the control region occupies more than three OFDM symbols in the time domain. In operation 1002, the BS transmits a downlink control channel within the control region to the UE. In one example, the downlink control channel is a PDCCH.
[0092] The details described in all the previous embodiments of the present application (e.g., how IoT UE can work normally with very high AL-PDCCH support in narrowband) are applicable to Fig.10 The embodiments shown in .
[0093] Fig.11 Another flow chart illustrating a method for wireless communication according to some embodiments of the present application.
[0094] In such Fig.11 In the exemplary method 1100 shown in FIG. 1 , in operation 1101, a UE (e.g., Figure 1 UE 101a shown in FIG. 101b) receives a signal from a BS (eg, Figure 1 102) receives signaling for configuring a control region on a wideband carrier, wherein the control region occupies more than three OFDM symbols in the time domain. In operation 1102, the UE receives a downlink control channel within the control region from the BS. In one example, the downlink control channel is a PDCCH.
[0095] The details described in all the above embodiments of the present application (e.g., how IoT UE can work normally in the case of supporting very high AL-PDCCH in narrowband) are applicable to the following embodiments: Fig.11 The embodiments shown in .
[0096] Fig.12 A block diagram illustrating an exemplary device according to some embodiments of the present application. Fig.12 , apparatus 1200 includes receive circuitry 1202, transmit circuitry 1204, a processor 1206, and a non-transitory computer-readable medium 1208. Processor 1206 is coupled to non-transitory computer-readable medium 1208, receive circuitry 1202, and transmit circuitry 1204.
[0097] After consideration, for simplicity, Fig.12 In some embodiments, receive circuitry 1202 and transmit circuitry 1204 may be integrated into a single component (eg, a transceiver).
[0098] In some embodiments, the non-transitory computer-readable medium 1208 may have computer-executable instructions stored thereon to cause the processor to perform operations related to (multiple) UEs as described above. For example, when executing the computer-executable instructions stored in the non-transitory computer-readable medium 1208, the processor 1206, the receiving circuit system 1202, and the transmitting circuit system 1204 perform Fig.10 The method includes controlling the transmitting circuit system 1204 to transmit a signaling to configure a control region on a wideband carrier to a UE, wherein the control region occupies more than three OFDM symbols in the time domain, and transmitting a downlink control channel within the control region to the UE.
[0099] In some embodiments, the non-transitory computer-readable medium 1208 may have computer-executable instructions stored thereon to cause the processor to perform operations related to (multiple) BSs as described above. For example, when executing the computer-executable instructions stored in the non-transitory computer-readable medium 1208, the processor 1206, the receiving circuit system 1202, and the transmitting circuit system 1204 perform Fig.11 The method includes controlling the receiving circuit system 1202 to receive signaling for configuring a control region on a broadband carrier from a BS, wherein the control region occupies more than three OFDM symbols in the time domain, and receiving a downlink control channel within the control region from the BS.
[0100] The method of the present application can be implemented on a programmed processor. However, the controller, flow chart and modules can also be implemented on a general or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit components, an integrated circuit, a hardware electronic or logic circuit (such as a discrete component circuit), a programmable logic device or the like. In general, any device on which a finite state machine capable of implementing the flow chart shown in the figure resides can be used to implement the processor functions of the present application.
[0101] Those skilled in the art will appreciate that the steps of the methods described in conjunction with the aspects disclosed herein may be directly embodied in hardware, a software module executed by a processor, or a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In addition, in some aspects, the steps of the method may reside as one or any combination or set of codes and / or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.
[0102] Although the present invention has been described by its specific embodiments, it is apparent that many alternatives, modifications and variations may be apparent to those skilled in the art. For example, the various components of the embodiments may be interchangeable, added or replaced in other embodiments. In addition, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, a person skilled in the art of the disclosed embodiments will be able to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present invention as described herein are intended to be illustrative rather than restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.
[0103] In this document, the term "include", "comprises" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment including the list of elements not only include these elements, but may also include other elements that are not clearly listed or inherent to such process, method, article or equipment. In the absence of more constraints, the element performed by "one", "one" or the like does not exclude the presence of additional identical elements in the process, method, article or equipment including the element. In addition, the term "another" is defined as at least the second or more. As used herein, the term "include", "have" and the like are defined as "include".
Claims
1. A method for wireless communication performed by a base station BS, comprising: Transmitting signaling for configuring a control region on a wideband carrier to a user equipment UE, wherein the control region occupies more than three orthogonal frequency division multiplexing OFDM symbols in the time domain, wherein the more than three OFDM symbols are in the same time slot and are not continuous in the time domain and are interrupted by one or more OFDM symbols used for a demodulation reference signal DMRS; and A downlink control channel within the control region is transmitted to the UE. 2 . The method of claim 1 , wherein the more than three OFDM symbols are within the same time slot and are consecutive in the time domain. The method of claim 1 , wherein a total number of the more than three OFDM symbols is an integer multiple of 6. 4 . 4 . The method according to claim 1 , wherein the control region comprises a plurality of resource element groups (REGs), and the REGs in the control region are numbered in ascending order in a frequency first and time second manner. 5 . The method according to claim 4 , wherein the total number of REGs within one REG bundle in the frequency domain is configured by radio resource control (RRC) signaling. 6 . The method according to claim 1 , wherein the control region comprises a plurality of resource element groups (REGs), and the REGs in the control region are numbered in ascending order in a manner of time first and frequency second. 7 . The method according to claim 6 , wherein the total number of REGs in one REG bundle in the time domain is configured by RRC signaling.
8. The method of claim 1, wherein a periodicity and an offset for transmitting the downlink control channel are configured by Radio Resource Control (RRC) signaling.
9. The method according to claim 1, wherein the duration in the time domain and the bandwidth in the frequency domain of the control region are preconfigured or configured by RRC signaling.
10. The method of claim 1, wherein the control region comprises a set of control resources within a time slot.
11. The method according to claim 10, wherein the control resource set occupies a portion of the wideband carrier, and the portion of the wideband carrier includes one or more resource block groups (RBGs) in the frequency domain, and each RBG includes a predetermined number of consecutive resource blocks in the frequency domain.
12. The method of claim 11, wherein the one or more RBGs are consecutive RBGs in the frequency domain. The method of claim 11 , wherein the one or more RBGs are non-contiguous RBGs in the frequency domain.
14. The method according to claim 11, wherein the offset between the index of the lowest numbered resource block (RB) in the control resource set and the index of the lowest numbered RB in the wideband carrier relative to the same subcarrier spacing is an integer multiple of 6.
15. The method of claim 1, wherein the control region comprises two or more control resource sets.
16. The method of claim 15, wherein the two or more control resource sets are within the same time slot.
17. The method of claim 15, wherein two or more sets of control resources are in different time slots.
18. The method of claim 15, wherein the REGs in the two or more control resource sets are numbered in the same increasing order across the control resource sets, wherein the same increasing order is frequency first and time second or time first and frequency second.
19. The method of claim 15, wherein control channel elements (CCEs) in the two or more control resource sets are concatenated for transmitting the downlink control channel.
20. The method according to claim 1, wherein the downlink control channel carries control information for scheduling system information, and the control region includes at least four OFDM symbols in the time domain and twenty-four resource blocks (RBs) in the frequency domain.
21. The method according to claim 1, wherein the downlink control channel carries control information for scheduling system information, and a duration in the time domain and a bandwidth in the frequency domain of the control region are indicated in a master information block (MIB).
22. A method for wireless communication performed by a user equipment UE, comprising: receiving signaling for configuring a control region on a broadband carrier from a base station BS, wherein the control region occupies more than three orthogonal frequency division multiplexing OFDM symbols in the time domain, wherein the more than three OFDM symbols are in the same time slot and are not consecutive in the time domain and are interrupted by one or more OFDM symbols used for a demodulation reference signal DMRS; and A downlink control channel within the control region is received from the BS.
23. The method of claim 22, wherein the more than three OFDM symbols are within the same time slot and are consecutive in the time domain.
24. The method of claim 22, wherein a total number of the more than three OFDM symbols is an integer multiple of 6. 25 . The method according to claim 22 , wherein the control region comprises a plurality of resource element groups (REGs), and the REGs within the control region are numbered in ascending order in a frequency first, time second manner.
26. The method of claim 25, wherein the total number of REGs within one REG bundle in the frequency domain is configured by radio resource control (RRC) signaling. 27 . The method according to claim 22 , wherein the control region comprises a plurality of resource element groups (REGs), and the REGs in the control region are numbered in ascending order in a manner of time first and frequency second.
28. The method according to claim 27, wherein the total number of REGs in one REG bundle in the time domain is configured by RRC signaling.
29. The method of claim 22, wherein a periodicity and an offset for receiving the downlink control channel are configured by Radio Resource Control (RRC) signaling.
30. The method of claim 22, wherein the duration in the time domain and the bandwidth in the frequency domain of the control region are preconfigured or configured by RRC signaling.
31. The method of claim 22, wherein the control region comprises a set of control resources within a time slot.
32. The method of claim 31, wherein the control resource set occupies a portion of the broadband carrier, and the portion of the broadband carrier includes one or more resource block groups (RBGs) in the frequency domain, and each RBG includes a predetermined number of consecutive resource blocks in the frequency domain.
33. The method of claim 32, wherein the one or more RBGs are contiguous RBGs in the frequency domain.
34. The method of claim 32, wherein the one or more RBGs are non-contiguous RBGs in the frequency domain.
35. The method of claim 32, wherein the offset between the index of the lowest numbered resource block (RB) in the control resource set and the index of the lowest numbered RB in the wideband carrier relative to the same subcarrier spacing is an integer multiple of 6.
36. The method of claim 22, wherein the control region comprises two or more sets of control resources.
37. The method of claim 36, wherein the two or more sets of control resources are within the same time slot.
38. The method of claim 36, wherein two or more sets of control resources are in different time slots.
39. The method of claim 36, wherein the REGs in the two or more control resource sets are numbered in the same increasing order across the control resource sets, wherein the same increasing order is an increasing order of frequency first and time second or an increasing order of time first and frequency second.
40. The method of claim 36, wherein control channel elements (CCEs) within the two or more control resource sets are concatenated for receiving the downlink control channel.
41. The method according to claim 36, wherein the downlink control channel carries control information for scheduling system information, and the control region includes at least four OFDM symbols in the time domain and twenty-four resource blocks (RBs) in the frequency domain.
42. The method according to claim 22, wherein a downlink control channel carries control information for scheduling system information, and a duration in the time domain and a bandwidth in the frequency domain of the control region are indicated in a master information block (MIB).
43. A base station BS, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the BS to: Transmitting signaling for configuring a control region on a wideband carrier to a user equipment UE, wherein the control region occupies more than three orthogonal frequency division multiplexing OFDM symbols in the time domain, wherein the more than three OFDM symbols are in the same time slot and are not continuous in the time domain and are interrupted by one or more OFDM symbols used for a demodulation reference signal DMRS; and A downlink control channel within the control region is transmitted to the UE.
44. A user equipment UE, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the UE to: receiving signaling for configuring a control region on a broadband carrier from a base station BS, wherein the control region occupies more than three orthogonal frequency division multiplexing OFDM symbols in the time domain, wherein the more than three OFDM symbols are in the same time slot and are not consecutive in the time domain and are interrupted by one or more OFDM symbols used for a demodulation reference signal DMRS; and A downlink control channel within the control region is received from the BS.
Citation Information
Patent Citations
Method and apparatus for transmitting or receiving control channel in communication system
CN109565430A
Design on pdcch DMRS mapping and coreset resource allocation
CN110121912A
Communication method, terminal device and network device
WO2019029014A1