Resource allocation indication for multi-carrier single cell operation
By defining a dedicated BWP configuration for multi-carrier single-cell operations, the inefficiencies in managing multiple narrowband carriers are addressed, enhancing communication efficiency and resource utilization in low-frequency bands.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- NOKIA TECHNOLOGIES OY
- Filing Date
- 2025-11-13
- Publication Date
- 2026-06-25
AI Technical Summary
Current communication systems face inefficiencies in managing multiple narrowband carriers due to per-carrier scheduling and resource allocation overhead, especially in low-frequency bands, which can be addressed by operating these carriers as a single logical cell to enhance efficiency and reduce resource utilization inefficiencies.
A dedicated bandwidth part (BWP) configuration is defined for multi-carrier single-cell operations, where frequency domain resources are determined based on carrier-specific grids, and control channel configurations are managed to support efficient resource allocation across multiple carriers.
This approach enhances communication efficiency by reducing overhead and improving resource utilization, particularly in fragmented spectrum scenarios, optimizing performance in low-frequency bands.
Smart Images

Figure IB2025061604_25062026_PF_FP_ABST
Abstract
Description
Resource allocation indication for Multi-Carrier single Cell OperationCROSS-REFERENCE TO RELATED APPLICATION
[0001] This application claims priority from, and the benefit of, US Provisional Application No. 63 / 736430, filed December 19, 2024, which is hereby incorporated by reference in its entirety.FIELD
[0002] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for resource allocation indication for multi-carrier single cell operation.BACKGROUND
[0003] Communication technologies are fundamental to enabling the exchange of information in modern systems. With the increasing demand for high-speed data transmission and efficient spectrum utilization, carrier aggregation (CA) has been developed as a technology to address these needs. Carrier aggregation allows the combination of multiple carrier frequencies, thereby enhancing data transmission efficiency and network capacity, and plays a significant role in improving communication performance.SUMMARY
[0004] In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive, from a second apparatus, a dedicated downlink bandwidth part (DL BWP), configuration including information of carrier specific frequency domain resource grids of two or more carriers; determine the dedicated DL BWP based on the information; in accordance with a determination of a reception of a DL control channel configuration including respective control resource sets (CORESETs) of the two or more carriers within the dedicated DL BWP, determine frequency domain resources configured for the respective CORESETs based on a plurality of radio resource control (RRC) configurations or a single RRC configuration in the DL control channel configuration; and monitor downlink control information (DCI) based on the determination of the frequency domain resources.
[0005] In a second aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: transmit, to a first apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; transmit, to the first apparatus, a DL control channelconfiguration including respective CORESETs of the two or more carriers within the dedicated DL BWP, wherein the respective CORESETs are configured by a plurality of RRC configurations separately or by a single RRC configuration jointly; and transmit, to the first apparatus, DCI based on the DL control channel configuration.
[0006] In a third aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive, from a second apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; in accordance with a determination that DCI scheduling a DL data channel transmission is received based on the DL control channel configuration, determine a frequency domain resource allocation (FDRA) for the DL data channel transmission of the two or more carriers based on one or more FDRA indications in the DCI and carrier specific frequency domain resource grids; and receive the DL data channel transmission based on the FDRA.
[0007] In a fourth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: transmit, to a first apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; transmit, to the first apparatus, DCI scheduling a DL data channel transmission indicating a FDRA the two or more carriers by using one or more FDRA indications; and transmit, to the first apparatus, the DL data channel transmission based on the FDRA.
[0008] In a fifth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive, from a second apparatus, a dedicated uplink bandwidth part (UL BWP), configuration including information of carrier specific frequency domain resource grids of two or more carriers; in accordance with a determination that DCI scheduling a UL data channel transmission is received, determine a FDRA for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP based on one or more FDRA indications in the DCI; and transmit the uplink data channel transmission based on the FDRA.
[0009] In a sixth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: transmit, to a first apparatus, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; transmit, to the first apparatus, DCI scheduling a UL data channel transmission indicating a FDRA for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP by using one or more FDRA indications in the DCI; andreceive the uplink data channel transmission on the FDRA.
[0010] In a seventh aspect of the present disclosure, there is provided a method. The method comprises: receiving, from a second apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; determining the dedicated DL BWP based on the information; in accordance with a determination of a reception of a DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP, determining frequency domain resources configured for the respective CORESETs based on a plurality of RRC configurations or a single RRC configuration in the DL control channel configuration; and monitoring DCI based on the determination of the frequency domain resources.
[0011] In an eighth aspect of the present disclosure, there is provided a method. The method comprises: transmitting, to a first apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; transmitting, to the first apparatus, a DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP, wherein the respective CORESETs are configured by a plurality of RRC configurations separately or by a single RRC configuration jointly; and transmitting, to the first apparatus, DCI based on the DL control channel configuration.
[0012] In a ninth aspect of the present disclosure, there is provided a method. The method comprises: receiving, from a second apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; in accordance with a determination that DCI scheduling a DL data channel transmission is received based on the DL control channel configuration, determining a FDRA for the DL data channel transmission of the two or more carriers based on one or more FDRA indications in the DCI and carrier specific frequency domain resource grids; and receiving the DL data channel transmission based on the FDRA.
[0013] In a tenth aspect of the present disclosure, there is provided a method. The method comprises: transmitting, to a first apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; transmitting, to the first apparatus, DCI scheduling a DL data channel transmission indicating a FDRA the two or more carriers by using one or more FDRA indications; and transmitting, to the first apparatus, the DL data channel transmission based on the FDRA.
[0014] In an eleventh aspect of the present disclosure, there is provided a method. The method comprises: receiving, from a second apparatus, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; in accordance with a determination that DCI scheduling a UL data channel transmission is received, determining a FDRA for the uplink data channel transmission of the two or more carriers within the dedicated ULBWP based on one or more FDRA indications in the DCI; and transmitting the uplink data channel transmission based on the FDRA.
[0015] In a twelfth aspect of the present disclosure, there is provided a method. The method comprises: transmitting, to a first apparatus, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; transmitting, to the first apparatus, DCI scheduling a UL data channel transmission indicating a FDRA for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP by using one or more FDRA indications in the DCI; and receiving the uplink data channel transmission on the FDRA.
[0016] In a thirteenth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving, from a second apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for determining the dedicated DL BWP based on the information; means for in accordance with a determination of a reception of a DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP, determining frequency domain resources configured for the respective CORESETs based on a plurality of RRC configurations or a single RRC configuration in the DL control channel configuration; and means for monitoring DCI based on the determination of the frequency domain resources.
[0017] In a fourteenth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for transmitting, to a first apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for transmitting, to the first apparatus, a DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP, wherein the respective CORESETs are configured by a plurality of RRC configurations separately or by a single RRC configuration jointly; and means for transmitting, to the first apparatus, DCI based on the DL control channel configuration.
[0018] In a fifteenth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving, from a second apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for in accordance with a determination that DCI scheduling a DL data channel transmission is received based on the DL control channel configuration, determining a FDRA for the DL data channel transmission of the two or more carriers based on one or more FDRA indications in the DCI and carrier specific frequency domain resource grids; and means for receiving the DL data channel transmission based on the FDRA.
[0019] In a sixteenth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for transmitting, to a first apparatus, a dedicated DL BWPconfiguration including information of carrier specific frequency domain resource grids of two or more carriers; means for transmitting, to the first apparatus, DCI scheduling a DL data channel transmission indicating a FDRA the two or more carriers by using one or more FDRA indications; and means for transmitting, to the first apparatus, the DL data channel transmission based on the FDRA.
[0020] In a seventeenth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving, from a second apparatus, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for in accordance with a determination that DCI scheduling a UL data channel transmission is received, determining a FDRA for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP based on one or more FDRA indications in the DCI; and means for transmitting the uplink data channel transmission based on the FDRA.
[0021] In an eighteenth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for transmitting, to a first apparatus, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for transmitting, to the first apparatus, DCI scheduling a UL data channel transmission indicating a FDRA for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP by using one or more FDRA indications in the DCI; and means for receiving the uplink data channel transmission on the FDRA.
[0022] In a nineteenth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the seventh aspect.
[0023] In a twentieth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the eighth aspect.
[0024] In a twenty-first aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the ninth aspect.
[0025] In a twenty-second aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the tenth aspect.
[0026] In a twenty-third aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the eleventh aspect.
[0027] In a twenty-fourth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing anapparatus to perform at least the method according to the twelfth aspect.
[0028] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0030] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0031] FIG. 2 illustrates a signaling flow for a process of an FDRA for a downlink control operation in accordance with some example embodiments of the present disclosure;
[0032] FIG. 3 illustrates an example of aggregating multi-carrier downlink resources to a single downlink bandwidth part in accordance with some example embodiments of the present disclosure;
[0033] FIG. 4 illustrates an example of an FDRA determination for a downlink control operation in accordance with some example embodiments of the present disclosure;
[0034] FIG. 5 illustrates a signaling flow for a process of an FDRA for a downlink data operation in accordance with some example embodiments of the present disclosure;
[0035] FIG. 6A illustrates an example of a jointly Type 0 frequency domain resource allocation in accordance with some example embodiments of the present disclosure;
[0036] FIG. 6B illustrates an example of differences between separately Type 1 and jointly Type 1 frequency domain resource allocation in accordance with some example embodiments of the present disclosure;
[0037] FIG. 7 illustrates a signaling flow for a process of an FDRA for an uplink data operation in accordance with some example embodiments of the present disclosure;
[0038] FIG. 8 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;
[0039] FIG. 9 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;
[0040] FIG. 10 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;
[0041] FIG. 11 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;
[0042] FIG. 12 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;
[0043] FIG. 13 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;
[0044] FIG. 14 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and
[0045] FIG. 15 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
[0046] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0047] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0048] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0049] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0050] It shall be understood that although the terms “first,” “second,”..., etc. in front of noun(s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun(s). For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0051] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of theelements, or at least all the elements.
[0052] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0053] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example 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 will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0054] As used in this application, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0055] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0056] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE- A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-loT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to anysuitable generation communication protocols, including, but not limited to, the first generation (1 G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G), 5.5G, the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0057] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (I AB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
[0058] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part ofan IAB node (e.g., a relay node). In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.
[0059] As used herein, the term “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other combination of the time, frequency, space and / or code domain resource enabling a communication, and the like. It is to be understood that the “resource block” may comprise a predefined number of subcarriers (such as 12) of an Orthogonal Frequency Division Multiple (OFDM) symbol. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0060] FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented. As shown in FIG. 1 , the communication network 100 may comprise a first apparatus 110 which may be, for example, a terminal device. In some example embodiments, the terminal device may also be discussed as a UE.
[0061] The communication network 100 may further comprise a second apparatus 120, which may be, for example, a network device. In some example embodiments, the network device may be discussed as a BS, a gNB, or an eNB.
[0062] A serving area provided by the second apparatus 120 is called a cell 102. The first apparatus 110 may communicate with the second apparatus 120 within the cell 102. The cell currently serving the first apparatus 110 may be considered as a serving cell.
[0063] In some example embodiments, if the first apparatus 110 is a terminal device and second apparatus 120 is a network device, a link from the second apparatus 120 to first apparatus 110 is referred to as a downlink (DL), while a link from the first apparatus 110 to second apparatus 120 is referred to as an uplink (UL). In DL, the second apparatus 120 is a transmitting (TX) apparatus (or a transmitter) and the first apparatus 110 is a receiving (RX) apparatus (or a receiver). In UL, the first apparatus 110 is a TX apparatus (or a transmitter) and the second apparatus 120 is a RX apparatus (or a receiver).
[0064] It is to be understood that the number of network devices and terminal devices shown in FIG.1 is given for the purpose of illustration without suggesting any limitations. The communication environment 100 may include any suitable number of network devices and terminal devices.
[0065] Communications in the communication environment 100 may be implemented according to any proper communication protocol(s), comprising, but not limited to, cellular communication protocols,wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0066] Communication technologies are fundamental to enabling the exchange of information in modern systems. With the increasing demand for high-speed data transmission and efficient spectrum utilization, carrier aggregation (CA) has been developed as a key technology to address these requirements. Carrier aggregation facilitates the combination of multiple carrier frequencies, thereby enhancing data transmission efficiency and network capacity. This technology plays a significant role in improving communication performance, particularly in scenarios involving fragmented spectrum resources.
[0067] In current communication systems, carrier aggregation (CA) has been developed as a technique for managing fragmented spectrum. However, CA operations introduce significant overhead and inefficiencies inherent to LTE or NR CA mechanisms when managing a terminal device and the overhead and inefficiencies mentioned above may play a role especially in the scenarios with multiple relatively narrowband component carriers e.g. in low frequency bands (such as FR1 ). Examples of such inefficiencies include but are not limited to:Per-carrier scheduling and resource allocation: In cases where the network transmits a larger amount of data to a UE, it must schedule independent data channel (PDSCH - physical downlink shared channel / PUSCH - physical uplink shared channel) transmissions for each carrier, typically with small transport blocks (TBs). This results in substantial downlink (DL) control overhead to manage the scheduling of individual PDSCH transmissions.Efficiency limitations of narrowband carriers: Compared to wideband carriers, operating multiple narrowband carriers independently is less efficient due to fragmented resource allocation. Wideband carriers allow resources to be jointly managed, reducing the likelihood of inefficient resource utilization (e.g., unused PRBs) and improving trunking efficiency.Importance of low-frequency bands: Low frequency bands in FR1 (< 2.6 GHz) are critical for providing cellular coverage. Maximizing the performance and efficiency of these bands is expected. This is especially important for fragmented spectrum scenarios involving multiple narrowband carriers, where managing them as a single logical cell for a UE can significantly enhance efficiency.
[0068] Accordingly, operating multiple carriers as a single logical cell, particularly in fragmentedspectrum scenarios, may provide substantial benefits, especially for low-frequency bands (e.g., below 2 GHz), which form the baseline coverage of mobile networks. This concept has also been recognized in recent 3GPP developments.
[0069] The present disclosure addresses the abovementioned challenges by defining the resource grid for a downlink (DL) or uplink (UL) bandwidth part (BWP) in multi-carrier single-cell operations. The resource grid contains the resources of multiple carriers, which may reside within the same or different frequency bands. Specifically, the invention clarifies how the resource grid is to be defined to support multi-carrier single-cell operations while maintaining compatibility with the normal operation of individual carriers as standalone cells.
[0070] In accordance with some example embodiments of the present disclosure, there is provided a solution for resource allocation indication for multi-carrier single cell operation. In this solution, a dedicated DL BWP configuration or a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers is transmitted from the second apparatus to the first apparatus. The first apparatus then determines the dedicated DL BWP or the dedicated UL BWP based on the information. If a DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP is received, the first apparatus determines frequency domain resources configured for the respective CORESETs based on a plurality of RRC configurations or a single RRC configuration in the DL control channel configuration. Then the first apparatus monitors the DCI based on the determination of the frequency domain resources.
[0071] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0072] Reference is now made to FIG. 2, which shows a signaling chart 200 for communication according to some example embodiments of the present disclosure. As shown in FIG. 2, the signaling chart 200 involves a first apparatus 110 and a second apparatus 120. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 200.
[0073] As shown in FIG. 2, the second apparatus 120 transmits (202) to the first apparatus 110, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers.
[0074] It is to be understood that the BWP used hereinafter may be a 5G term and / or a different term used in 6G. The same applies to BWP functionality - it may be slightly different in 6G. However, the functionalities relevant for the present disclosure (of dedicated BWP) are expected to be part of 6G.
[0075] For example, the information of the carrier specific frequency domain resource grids of two or more carriers may comprise respective reference points of the carrier specific frequency domain resource grids. As an example, a reference point of a carrier specific frequency domain resource gridmay be a Point A or a common resource block 0. The related information may be obtained based on received synchronization signal block (SSB) and system information block #1 (SIB1).
[0076] For example, the two or more carriers operated in a single cell mentioned hereinafter may include adjacent carriers or non-adjacent carriers within a frequency band or across frequency bands.
[0077] As an example, the dedicated DL BWP configuration may be transmitted from the second apparatus 120 to the first apparatus 110 via a higher layer signaling such as a RRC signaling.
[0078] Upon receiving the dedicated DL BWP configuration, the first apparatus 110 determines (204) the dedicated DL BWP based on the information of carrier specific frequency domain resource grids of two or more carriers.
[0079] Respective one or more resource sets may be associated with the carrier specific frequency domain resource grids of the two or more carriers. That is, each frequency domain resource grid may comprise one or more resource sets.
[0080] For example, the respective one or more resource sets may comprise resource blocks RBs or physical resource blocks PRBs. As another example, the resource sets may comprise resource- element-group (REG) bundles for DL control operation. It is also possible that the resource sets may comprise one or more resource block groups (RBGs) or one or more precoding resource block groups (PRGs) for shared data channel operation.
[0081] It is to be understood that the sizes of respective one or more resource sets on at least two carriers may be different. It is to be understood that 'size' of a resource set means number of RBs, REG bundles, RBGs, or PRGs, in a respective resource set.
[0082] For example, the first apparatus 110 may determine the dedicated DL BWP by concatenating the respective one or more resource sets in a configured order of the two or more carriers.
[0083] Details for determining the dedicated DL BWP by concatenating the respective one or more resource sets in a configured order will be further described with reference to FIG. 3.
[0084] FIG. 3 illustrates the PRB operation for determining a DL BWP containing the resources (PRBs) associated with, for example, 4 non-adjacent carriers.
[0085] The 4 non-adjacent carriers (e.g., carrier#1 to #4) shown in FIG. 3 may be in the same or in a different band. The total DL BWP may contain NPRB.B P PRBS which may be determined based on sum of the allocated number of PRBs to the BWP of each of the M=4 carriers {NPRB.I, NPRB,2, NPRB,3, NPRB, , i.e., NPRB BWP= m=iNPRB,m- For the example presented here it is assumed, that the PRBs in the DL BWP may be ordered from carrier#1 to #4 (i.e. from left to right in the figure) but the logical order of the carriers within the DL BWP across carriers may be defined by the order the carrier resources added to the DL BWP configuration, per serving cell index of the aggregated carriers or may be defined by a certain order as specified in RRC configurations. As can be noted, the carrier corresponding to the serving cell to which the first apparatus 110 has performed initial access and islogically assigned, identified as carrier#2 in FIG. 3, does not necessarily need to be considered as the first carrier in the ordering of the physical resources of the carriers within the DL BWP covering multiple carriers.
[0086] Referring back to FIG. 2, the second apparatus 120 may transmit (206) DL control channel configuration, e.g., a physical downlink control channel (PDCCH) configuration to the first apparatus 110.
[0087] For example, the DL control channel configuration may be transmitted from the second apparatus 120 to the first apparatus 110 using higher layer signaling such as an RRC signaling.
[0088] Respective control resource set (CORESET)s of the two or more carriers within the dedicated DL BWP may be included in the DL control channel configuration, which may contain frequency domain resources of more than one carrier of the dedicated DL BWP. As an example, the frequency domain resources of the CORESET in the DL control channel configuration may be allocated based on the carrier specific resource grids associated with the dedicated DL BWP.
[0089] Upon receiving the DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP, the first apparatus 110 determines (208) frequency domain resources configured for the respective CORESETs.
[0090] In some example embodiments, the frequency domain resources configured for the respective CORESETs may be indicated by a plurality of RRC configurations separately and each RRC configuration may indicate a frequency domain resource allocation per carrier for a CORESET.
[0091] In some other example embodiments, the frequency domain resources configured for the respective CORESETs may be indicated by a joint / single indication for a CORESET, which may indicate frequency domain resource allocation of a respective CORESET across the two or more carriers.
[0092] In a case where the frequency domain resources configured for the respective CORESETs is indicated by a plurality of RRC configurations separately per carrier, the first apparatus 110 may determine the frequency domain resources configured for the respective CORESETs based on each bit string per carrier for indicating frequency domain resources. The number of bit strings may be associated with the maximum number of carriers per BWP.
[0093] Furthermore, respective RB offset indications are included in the plurality of RRC configurations for indicating start locations per carrier of the respective CORESETs in a frequency domain. The start locations of the respective CORESETs in a frequency domain may be associated with locations of the carrier specific frequency domain resource grids. That is, an RB offset indication may indicate an offset between the start location of a CORESET in the frequency domain and the location of a carrier specific frequency domain resource grid in a same carrier.
[0094] Specifically, there may be separate configurations of frequencyDomainResources for eachof the sub-bandwidth parts of the carriers as part of the CORESET configuration, i.e., for each of the carriers the 45bit long bitmap would be configured.
[0095] An example of RRC configuration for this resource allocation is listed below:0096] As shown, regarding to the RRC code for this operation for up to maxNumCarriersPerBWP carriers within a BWP, instead of a single bitstring of 45bits, there may be up to maxNumCarriersPerBWP bit strings and each bit string may correspond to one carrier of the DL BWP. Moreover, the current CORESET configuration may support configuring an RB offset to position the CORESET within a carrier (or currently a BWP).
[0097] An offset indication may be configured to align the grids of the envisioned multi-carrier single cell operation with single-carrier single cell operation, to be able to align the CORESET resource grid for the first apparatus 110 configured with DL BWPs across multiple carriers and the first apparatus 110 configured with DL BWPs contained within a single carrier:
[0098] In a case where the frequency domain resources configured for the respective CORESETs is indicated by a joint indication across the two or more carriers, the first apparatus 110 may determine the frequency domain resources configured for the respective CORESETs based on bit string for indicating frequency domain resources. The bit string may be associated with the maximum number of CORESET PRB groups of a DL BWP.
[0099] Similarly, an RB offset indication is included in the single RRC configuration for indicating start locations of the respective CORESETs in a frequency domain. The start locations of the respective CORESETs in a frequency domain may be associated with locations of the carrier specific frequency domain resource grids. That is, an RB offset indication may indicate an offset between the start location of a CORESET in the frequency domain per carrier and the location of a carrier specific frequency domain resource grid in a same carrier.
[0100] For this option, the related RRC configuration may look as follows: there may be a single bitmap configured in frequencyDomainResources of up to maxNumCoresetPRBgroups CPGs (e.g. 45 for current NR). But there may still be the per carrier configuration of the rb-Offset (as rb-OffsetList) to enable the alignment of the CORESET resource grid for multi-carrier single cell and normal single cell operation:0101] As shown, the size of the frequencyDomainResources of 45bits may be given by the maximum supported carrier bandwidth or DL BWP size considering that a single bit may be indicating 6 consecutive PRBs in the frequency domain and depending on the number of PRBs of a carrier / DL BWP (or sub-bandwidth part on a carrier) actually only a fraction of the bits may be actually used for indication.
[0102] In case there may be a limit set on the maximum number of PRBs for a bandwidth part of two or more carriers, the really used bits of the carrier specific bit map may be concatenated to a single bit string. Similarly, there may be an assumption on the maximum number of PRBs in a single active BWP that may be aggregated across carriers which may be currently defined as 272 PRBs, resulting in 45 bits (i.e. number of required bits defined by the granularity G = 6PRB and the maximum number of PRBs in a BWP N^’?^=272 leads to [log2(w“'P / G)l = 45 bits).
[0103] FIG. 4 illustrates an example of frequency domain resource allocation indication in accordance with some example embodiments of the present disclosure. The example shown in FIG. 4 refers to 2 carriers of 25 & 52 PRBs and is based on the assumption that an PRB offset (i.e. rb- Offset) of 0 for carrier 1 and carrier 2, i.e., the first RB of the first 6RB group corresponds to the first RB of the carrier part of the BWP.
[0104] In FIG. 4, each group of 6 PRBs corresponding to 1 bit of the bitmap may be denoted as CPG (CORESET PRB Group). For single carrier indication, as shown in the upper part in FIG. 4, only the first 4 bits for carrier 1 may be applicable for the indication whereas the remaining 41 bits (corresponding to CPG1#4 to 44) may not be applicable for indication (i.e., UE expecting these to be set to 0). Similarly, for carrier 2 only the first 8 bits of the bitmap may be applicable and the remaining 37 bits (corresponding to CPG2#8 to 44) may not be applicable and set to 0 by the gNB.
[0105] In the lower part of the FIG. 4 the indication based on a single bitmap of length 45 bits (assuming the same restriction on the maximum number of PRBsas for 5G / NR - i.e. 272 PRBs and granularity of G=6 PRBs) is presented. The first 4 bits of the bitmap associated with CPGBWP#0 to #3 may correspond to the CPGs of carrier 1 (i.e. CPGi#0 to #3), the following 8 bits associated with CPGBWP#4 to #11 may correspond to the CPGs of carrier 2 (i.e. CPG2#0 to #7), and the remaining 33 bits associated with CPGBWP#12 to #44 may not be applicable and are to be set to 0. In other words, this may indicate that the ‘size or portion of the bitmap’ from the total bit string for one carrier would be determined according to the number of CPGs per carrier.
[0106] It is to be understood that the frequency domain resources configured for a CORESET contains resources of more than one carrier of the DL BWP.
[0107] Turning back to FIG. 2, as an example, the second apparatus 120 may transmit (210) a DCIon the PDCCH based on the configured DL control channel configuration. The first apparatus 110 may monitor (212) the PDCCH based on the determined frequency domain resources configured for the respective CORESETs.
[0108] In some example embodiments, the second apparatus 120 may transmit DCI for scheduling a DL data channel transmission. In some other example embodiments, the second apparatus 120 may transmit DCI for scheduling an UL data channel transmission. Therefore, DCI may indicate resource allocation of two or more carriers within a dedicated DL BWP for the DL data channel transmission or a dedicated UL BWP for the UL data channel transmission. The way to indicate the resource allocation of two or more carriers for data channel transmission will be further described with reference to FIG. 5 and 7.
[0109] Reference is now made to FIG. 5, which shows a signaling chart 500 for communication according to some example embodiments of the present disclosure. As shown in FIG. 5, the signaling chart 500 involves a first apparatus 110 and a second apparatus 120. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 500.
[0110] FIG. 5 illustrates a determination of frequency domain resource scheduled for PDSCH and the subsequent PDSCH transmission and detailed descriptions will be provided in the following.
[0111] The second apparatus 120 transmits (502) to the first apparatus 110, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers. The detailed discussion about the DL BWP configuration is provided in the aforementioned paragraphs referring to step 202 of FIG. 2 thus will not be discussed in detail again.
[0112] It is to be understood that when configuring the sizes of the carrier-specific BWP portions (e.g., NPRB1 , NPRB2, ..) the second apparatus 120 may select such values that RBGs and PRGs are confined within a carrier. In other words, each RBG and PRG of a dedicated (DL) BWP may cover just one carrier.
[0113] Upon receiving the dedicated DL BWP configuration, the first apparatus 110 determines (504) the dedicated DL BWP based on the information of carrier specific frequency domain resource grids of two or more carriers. The detailed discussion about the DL BWP determination is provided in the aforementioned paragraphs referring to step 204 of FIG. 2 thus will not be discussed in detail again.
[0114] The second apparatus 120 transmits (506) to the first apparatus 110 a DCI information scheduling a DL data channel transmission, e.g., a PDSCH transmission. Upon receiving the DCI information scheduling a DL data channel transmission, the first apparatus 110 determines (508) an FDRA for the DL data channel transmission on one or more carriers of the DL BWP based on one or more FDRA indications in the DCI and carrier specific frequency domain resource grids.
[0115] Depending on whether the FDRA indication in the DCI may be indicated separately per carrier or jointly across the carriers of the DL BWP, the DCI and the FDRA determination by the first apparatus110 may vary and detailed description is provided to discuss the different scenarios. For either case, the FDRA further comprises Type 0 FDRA (i.e., an RBG based bitmap) and Type 1 FDRA (i.e., an RIV based indication). The determination of the PDSCH resource will be described in detail below.
[0116] In a case where the FDRA indications in the DCI are indicated separately per carrier, the first apparatus may obtain, from the DCI, a plurality of FDRA indications indicating respective carrierspecific FDRAs of the two or more carriers.
[0117] For Type 0 FDRA, the plurality of FDRA indications may be indicated by corresponding fields in the DCI. That is, there may be separate FDRA DCI fields in the DCI format scheduling PDSCH included. The FDRA field in each DCI field may be carrier specific.
[0118] For Type 1 FDRA, if there are no Type 1 resource allocation granularity configured, for example, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers. A sub-BWP corresponds to a carrier specific frequency domain resource grid available for UE reception or UE transmission. A plurality of configured (or active) sub-BWPs form a dedicated BWP covering multiple carriers of the serving cell.
[0119] In this case, there may be separate DCI fields in the DCI format scheduling PDSCH included, either there would be a separate field or separate blocks for each of the carriers. An example of Type 1 FDRA without Type 1 resource allocation granularity is listed as below:0120] In a case where Type 1 resource allocation granularity are configured, for the Type 1 FDRA, the number of bits indicating frequency domain resources of the plurality of FDRA indications may be associated with the number of the two or more carriers, respective sizes and starts of active sub- BWPs on the two or more carriers and respective resource allocation Type 1 granularity per carrier. An example of Type 1 FDRA with Type 1 resource allocation granularity is listed as below:0121 ] For this case where the FDRA indication is indicated separately as described above, upon receiving the FDRA indications comprised in the DCI information, the first apparatus 110 may determine (508) the FDRA for the scheduled DL data channel transmission from the carrier specific frequency domain resource grids and the respective carrier-specific FDRAs indicated by the plurality of FDRA indications.
[0122] In addition to the abovementioned case where the FDRA indications may be indicated separately, the FDRA indications may further be indicated jointly and detailed description will be provided below.
[0123] In a case where the FDRA indication in the DCI is indicated jointly, the first apparatus 110 may obtain, from the DCI, a joint FDRA indication indicating FDRAs across the two or more carriers of the DL BWP. For example, the joint FDRA indication may be indicated by a single field in the DCI.
[0124] For jointly indicated Type 0 FDRA, instead of separate DCI fields the FDRA information may be concatenated in a single DCI field, where the individual blocks for each carrier may be determined following the behaviour of the BWP on that carrier, as described in the following:
[0125] For the case of M carriers in the DL BWP, there may be M blocks in the DCI field where the each of the blocks for the M carriers may follow the legacy definition in terms of size for Type 0 FDRA - i.e., given by the number of the RBGs on the respective carrier NRBG mfor the m-th carrier.
[0126] The total number of bits of the FDRA field (across the blocks) may therefore be given asZ ' m=l..MRBG,m
[0127] The blocks may be similarly defined as for multi-cell scheduling using for example a DCI formats 0_3 / 1_3 for N, with M = N^p-.
[0128] That is, for Type 0 resource allocation, for example, the number of bits indicating frequency domain resources in the joint FDRA indication may be associated with the number of the two or more carriers and respective numbers of the resource block groups, RBGs, in the two or more carriers.
[0129] For Type 0 FDRA, the different here may be: only if the blocks of the individual carriers may be mapped to separate DCI fields or if joint indication using a single DCI field may be implemented.
[0130] For each of the carriers of a BWP, there may be a separate / independent RBG granularity configured as part of the configuration of the DL BWP covering multiple carriers.
[0131] In FIG. 6A, an example is provided for jointly indicated Type-0 FDRA for 2 carriers with the following assumptions.
[0132] Carrier 1 refers to 5MHz / 25PRBs, RBG configuration set as ‘config 2’ with an RBG size of 4 PRBs a NRBG 1=7 RBGS (RBGI#0 ... RBGi#6) and Carrier 2 refers to 10MHz / 52PRBs, RBG configuration set as ‘config 1 ’ with an RBG size of 4 PRBs a WRBG 2=13 RBGs (RBG2#0 ... RBG?#12).
[0133] The FDRA field may therefore haveNRBGim= 7 + 13 = 20 bits andNRBG, BWP = NRBGI1+ NRBG 2=20 RBGs may be scheduled / indicated, where the first 7 RBGs of the BWP (RBGBWP#0 ... RBGBWP#6) may correspond to RBGi#0 ... RBGi#6 of carrier 1 and the remaining 13 RBGs of the BWP (RBGBWP#7 . . . RBGBWP#19) may correspond to RBG2#0 ... RBG2#12 of carrier 2.
[0134] For jointly indicated Type 1 FDRA, if there is no Type 1 resource allocation granularity, for example, the number of bits indicating frequency domain resources in the joint FDRA indication may be associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
[0135] In this situation, there is a single RIV applicable that is defined by a single starting RB RBstart and length in terms of consecutive RBs LRBS but this needs to consider the total / aggregated number of RBs of the sub-bandwidth parts of the carriers. Therefore, the size for the FDRA field is defined by the total number of RBs over the aggregated sub-bandwidth parts of the carriers, i.e. NRBvp,cel1=An example of Type 1 FDRA with Type 1 resource allocation granularity not being configured is listed as below:
[0136] In a case where Type 1 resource allocation granularity is configured, for the Type 1 FDRA,the number of bits indicating frequency domain resources in the joint FDRA indication may be associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and a resource allocation type 1 granularity. An example of Type 1 FDRA with Type 1 resource allocation granularity is listed as below:
[0137] In this case that the FDRA indications may be indicated jointly, upon receiving the FDRA indication comprised in the DCI information, upon receiving the FDRA indication comprised in the DCI information, the first apparatus 110 may determine (508) the FDRA scheduled for the DL data channel transmission from the carrier specific frequency domain resource grids based on the FDRAs across the two or more carriers. For example, the joint FDRA indication may be indicated by a single field in the DCI.
[0138] For jointly indicated Type 1 FDRA, there is only a RIV (single starting RB RBstart & length LRBS across all carriers of the BWP) and therefore if the resource allocation size covers more than one carrier (i.e. across the carrier boundary), the allocation on the m-th carrier (m>1) starts automatically from RB#0 on these carriers. In contrast, for separately indicated FDRA, following the Rel-18 multicarrier scheduling framework, individual RIV (i.e. RB start and length) per carrier of the BWP can be individually indicated - i.e. allocation of the start on the m-th carrier may not be from PRB#0. Therefore, separately indicated FDRA is clearly more flexible in terms of resource allocation but requires more signaling bits compared to jointly indicated FDRA - just as an example of 4 carriers with each having NRp,carrierof 52 RBs (i.e. NRBvp,cel1of 208 RBs) without Type 1 resource allocation granularity,
[0139] For a case where the Type 1 FDRA indications in the DCI are indicated separately:
[0140] For a case where the Type 1 FDRA indication in the DCI is indicated jointly:bits
[0141] The difference is illustrated in FIG. 6B for the example of the 2 carriers of 25RBs and 52RBs respectively of the dedicated DL BWP:
[0142] For separately indicated Type 1 FDRA, it is assumed that RIVi indicates RBstart, 1 =5 and LRBS =20, i.e. allocation from the 6thto 25thRB (RB# 5 to #24) for carrier and RIV2 indicates RBstart, 2 =8 and LRBS.I =20, i.e. allocation from the 9thto 28thRB for carrier 2 (i.e. RBs #8 to #27).
[0143] For jointly indicated FDRA, there may be only a single RIVceii for all carriers across thebandwidth part, again for an allocation of in total of 40 RBs, RBstart, ceii=5 and LRBs,ceii=40. Therefore, the first 20 RBs of the resource allocation may be mapped to carrier 1 as for separately indicated FDRA (i.e. RBs#5 to 24 allocation) and the remaining 20 PRBs that may not fit to carrier 1 anymore may be mapped to the second carrier starting from the lowest PRB (i.e. RB#0) of the second carrier and 20 PRBs are mapped up to RB#19 of the second carrier.
[0144] Moreover, reference signal transmission, such as demodulation reference signal (DM-RS) or a phase tracking reference signal (PT-RS) may be defined for a single PDSCH scheduled over multiple carriers. For example, reference signal sequence for single PDSCH may consist of multiple carrierspecific sequences. In some embodiments, sequences may have the same or different reference point for ‘k’. Additionally or optionally, sequences may be the same or different reference signal types (e.g., different sequence type and / or different pattern).
[0145] In some implementations, the DM-RS (and / or PT-RS) transmission associated with the PDSCH may be based on DM-RS (and / or PT-RS) sequence mapping to resources based on the received carrier specific resource grid (of step 502) or resource sets (of step 504). In this case, the first apparatus 110 may obtain a mapping between reference signal sequences and respective one or more resource sets associated with the carrier specific frequency domain resource grids.
[0146] For example, upon receiving the mapping, if a DL data channel transmission is scheduled via the DCI, the first apparatus 110 may determine, based on one or more FDRA indications in the DCI, a frequency domain resource allocation for the reference signal associated with the DL data channel transmission of the two or more carriers from the carrier specific frequency domain resource grids.
[0147] For example, the first apparatus 110 may determine, based on the determined frequency domain resource allocation and the mapping, respective sequences of the reference signal associated with the DL data channel transmission on one or more carriers of the DL BWP.
[0148] Referring to FIG. 5, the second apparatus 120 may perform (510) a PDSCH transmission to the first apparatus 110. It is to be understood that, in addition to the FDRA, other PDSCH parameters such as time-domain resource allocation (TDRA), MCS, precoding and number of layers etc. may also be determined for the PDSCH transmission.
[0149] As an option, a DM-RS (and / or PT-RS) transmission may be transmitted associated with the PDSCH transmission based on DM-RS (and / or PT-RS) sequence mapping to resources.
[0150] The first apparatus 110 may receive (512) the PDSCH transmission based on determined PDSCH FDRA. For example, the first apparatus 110 may perform some reception processing for the PDSCH separately at least for carriers in different bands, such as FFT, channel and interference estimation based on the carrier specific parameters. This may include to apply DM-RS (and / or PT-RS) sequence mapping to physical resources based on the carrier specific resource grid or resource setsto determine channel and interference estimate(s) for PDSCH decoding.
[0151] Reference is now made to FIG. 7, which shows a signaling chart 700 for communication according to some example embodiments of the present disclosure. As shown in FIG. 7, the signaling chart 700 involves a first apparatus 110 and a second apparatus 120. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 700.
[0152] Specifically, the signaling chart 700 illustrates a determination of frequency domain resource scheduled for PUSCH used for uplink data transmission. It should be understood that the essential steps for the scenario here for PUSCH such as BWP determination, DCI scheduling resources and the subsequent resource determination and transmission are in principle the same as those steps for the scenario discussed in detail for PDSCH with reference to FIG. 5 by considering a dedicated UL BWP for PUSCH transmission in Fig. 7 instead of a dedicated DL BWP for PDSCH transmission of Fig. 5. Therefore, the detailed description will not be repeated again.
[0153] As shown in FIG. 7, the second apparatus 120 transmits (702) to the first apparatus 110, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers.
[0154] For example, the information of the carrier specific frequency domain resource grids of two or more carriers may comprise respective reference points of the carrier specific frequency domain resource grids. As an example, a reference point of a carrier specific frequency domain resource grid may be a Point A or a common resource block 0.
[0155] For example, the two or more carriers of the dedicated UL bandwidth part may be adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0156] As an example, the dedicated UL BWP configuration may be transmitted from the second apparatus 120 to the first apparatus 110 via a higher layer signaling such as an RRC signaling.
[0157] Upon receiving the dedicated UL BWP configuration, the first apparatus 110 determines (704) the dedicated UL BWP based on the information of carrier specific frequency domain resource grids of two or more carriers.
[0158] Respective one or more resource sets may be associated with the carrier specific frequency domain resource grids of the two or more carriers. That is, each frequency domain resource grid may comprise one or more resource sets.
[0159] For example, the respective one or more resource sets may comprise resource blocks RBs or physical resource blocks PRBs. It is also possible that the source sets may comprise one or more resource block groups (RBGs) or one or more precoding resource block groups (PRGs).
[0160] It is to be understood that the sizes of respective one or more resource sets on at least two carriers may be different.
[0161] For example, the first apparatus 110 may determine the dedicated UL BWP by concatenatingthe respective one or more resource sets in a configured order of the two or more carriers.
[0162] The second apparatus 120 transmits (706) to the first apparatus 110 a DCI information scheduling an UL data channel transmission, e.g., a PUSCH transmission. Upon receiving the DCI information scheduling the UL data channel transmission, the first apparatus 110 determines (708) an FDRA for the UL data channel transmission on one or more carriers of the UL BWP based on one or more FDRA indications in the DCI and carrier specific frequency domain resource grids.
[0163] Depending on whether the FDRA indication in the DCI may be indicated separately or jointly, the DCI and the FDRA determination by the first apparatus 110 may vary and detailed description is provided to discuss the different scenarios. For either case, the FDRA further comprises Type 0 FDRA (i.e., an RBG based bitmap) and Type 1 FDRA (i.e., an RIV based indication). The determination of the PUSCH resource will be described in detail below.
[0164] In a case where the FDRA indications in the DCI are indicated separately, the first apparatus may obtain, from the DCI, a plurality of FDRA indications indicating respective carrier-specific FDRAs of the two or more carriers of the UL BWP.
[0165] For Type 0 FDRA, the plurality of FDRA indications may be indicated by corresponding fields in the DCI. That is, there may be separate FDRA DCI fields in the DCI format scheduling PUSCH included. The FDRA field in each DCI field may be carrier specific.
[0166] For Type 1 FDRA, if there are no Type 1 resource allocation granularity configured, for example, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers of the UL BWP.
[0167] In a case where Type 1 resource allocation granularity are configured, for the Type 1 FDRA, the number of bits indicating frequency domain resources of the plurality of FDRA indications may be associated with the number of the two or more carriers, respective sizes and starts of active sub- BWPs on the two or more carriers and respective resource allocation Type 1 granularity per carrier.
[0168] In a case where the FDRA indication in the DCI is indicated jointly, the first apparatus 110 may obtain, from the DCI, a joint FDRA indication indicating FDRAs across the two or more carriers of the UL BWP. For example, the joint FDRA indication may be indicated by a single field in the DCI.
[0169] For Type 0 resource allocation, for example, the number of bits indicating frequency domain resources in the joint FDRA indication may be associated with the number of the two or more carriers and respective numbers of the resource block groups, RBGs, in the two or more carriers.
[0170] For jointly indicated Type 1 FDRA, if there is no Type 1 resource allocation granularity, for example, the number of bits indicating frequency domain resources in the joint FDRA indication may be associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
[0171] In this situation, there is a single RIV applicable that is defined by a single starting PRB RBstart and length in terms of consecutive RBs LRBS but this needs to consider the total / aggregated number of PRBs of the sub-bandwidth parts of the carriers. Therefore, the size for the FDRA field is defined by the total number of RBs over the aggregated sub-bandwidth parts of the two or more carriers,
[0172] In a case where Type 1 resource allocation granularity is configured, for the Type 1 FDRA, the number of bits indicating frequency domain resources in the joint FDRA indication may be associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and a resource allocation type 1 granularity.
[0173] For this case where the FDRA indication is indicated separately as described above, upon receiving the FDRA indications comprised in the DCI information, the first apparatus 110 may determine (708) the FDRA scheduled for the UL data channel transmission from the carrier specific frequency domain resource grids by concatenating respective carrier-specific FDRAs indicated by the plurality of FDRA indications.
[0174] In this case that the FDRA indications may be indicated jointly, upon receiving the FDRA indication comprised in the DCI information, upon receiving the FDRA indication comprised in the DCI information, the first apparatus 110 may determine (504) the FDRA scheduled for the UL data channel transmission from the carrier specific frequency domain resource grids based on the FDRAs across the two or more carriers. For example, the joint FDRA indication may be indicated by a single field in the DCI.
[0175] Then the first apparatus 110 may transmit (710), to the second apparatus 120, a PUSCH transmission according to the FDRA for PUSCH determined based on separately indicated FDRA or jointly indicated FDRA.
[0176] It is to be understood that, in addition to the FDRA, other PDSCH parameters such as timedomain resource allocation (TDRA), MCS, precoding and number of layers etc. may also be determined for the PUSCH transmission.
[0177] Moreover, reference signal transmission, such as demodulation reference signal (DM-RS) or a phase tracking reference signal (PT-RS) may be defined for a single PUSCH scheduled over multiple carriers of the UL BWP. For example, reference signal sequence for single PUSCH may consist of multiple carrier-specific sequences. In some embodiments, sequences may have the same or different reference point for ‘k’. Additionally or optionally, sequences may be the same or different reference signal types (e.g., different sequence type and / or different pattern).
[0178] In some implementations, the DM-RS (and / or PT-RS) transmission associated with the PUSCH may be based on DM-RS (and / or PT-RS) sequence mapping to resources based on the received carrier specific resource grid (of step 202 in FIG. 2) or resource sets (of step 204 in FIG. 2).In this case, the first apparatus 110 may obtain a mapping between reference signal sequences and respective one or more resource sets associated with the carrier specific frequency domain resource grids.
[0179] For example, upon receiving the mapping, if a UL data channel transmission is scheduled via the DCI, the first apparatus 110 may determine, based on one or more FDRA indications in the DCI, a frequency domain resource allocation for the reference signal associated with the UL data channel transmission of the two or more carriers from the carrier specific frequency domain resource grids.
[0180] For example, the first apparatus 110 may determine, based on the determined frequency domain resource allocation and the mapping, respective sequences of the reference signal associated with the UL data channel transmission in the one or more carriers of the UL BWP.
[0181] In this case, the first apparatus 110 may transmit the PUSCH transmission (including the associated DM-RS and / or PT-RS) to the second apparatus 120.
[0182] The second apparatus 120 may receive (712) the PUSCH transmission based on indicated FDRA. For example, the second apparatus 120 may perform some reception processing for the PUSCH separately at least for carriers in different bands, such as FFT, channel and interference estimation based on the carrier specific parameters. This may include to apply DM-RS (and / or PT-RS) sequence mapping to physical resources based on the carrier specific resource grid or resource sets to determine channel and interference estimate(s) for PUSCH decoding.
[0183] Having the references in terms of frequency domain resource allocation still per carrier allows operation of multi-carrier single cell operation for some UEs, whereas still enabling single-carrier single-cell operation for other UEs on the same set of carriers based on the same (frequency-domain) resource grid.
[0184] Furthermore, some DCI overheads may be saved for FDRA indication (e.g., for Type 1 RA) as well as especially for the CORESET allocation in multiples of the CORESET allocation granularity.
[0185] FIG. 8 shows a flowchart of an example method 800 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the first apparatus 110 in FIG. 1.
[0186] At block 810, the first apparatus receives, from a second apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers.
[0187] At block 820, the first apparatus determines the dedicated DL BWP based on the information.
[0188] At block 830, in accordance with a determination of a reception of a DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP, at block 840, the first apparatus determines frequency domain resources configured for therespective CORESETs based on a plurality of RRC configurations or a single RRC configuration in the DL control channel configuration.
[0189] At block 850, the first apparatus monitors DCI based on the determination of the frequency domain resources.
[0190] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0191] In some example embodiments, the method 800 further comprises: determining respective one or more resource sets associated with the carrier specific frequency domain resource grids of the two or more carriers; and determining the dedicated DL BWP by concatenating the respective one or more resource sets in a configured order of the two or more carriers.
[0192] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0193] In some example embodiments, the respective one or more resource sets and the respective CORESETs comprises at least one of the following: resource blocks, RB, resource-element-group, REG, bundles, one or more resource block groups, RBGs, one or more precoding resource block groups, PRGs.
[0194] In some example embodiments, the frequency domain resources configured for a CORESET contains resources of more than one carrier of the DL BWP.
[0195] In some example embodiments, the method 800 further comprises: obtaining, from the DL control channel configuration, the plurality of RRC configurations for configuring the respective CORESETs; and determining frequency domain resources configured for the respective CORESETs based on respective frequency domain resource allocations, FDRAs, indicated in the plurality of RRC configurations.
[0196] In some example embodiments, an RRC configuration in the plurality of RRC, configuration indicates a frequency domain resource allocation of a CORESET of a carrier, and wherein the number of bit strings for indicating frequency domain resources are associated with the maximum number of carriers per BWP.
[0197] In some example embodiments, the method 800 further comprises: receiving the single RRC configuration for configuring the respective CORESETs; and determining the frequency domain resources of the respective CORESETs based on an FDRA indicated in the single RRC configuration.
[0198] In some example embodiments, the single RRC configuration indicates frequency domain resource allocation of respective CORESETs across the two or more carriers and a bit string in the single RRC configuration for indicating frequency domain resources are associated with the maximum number of CORESET PRB groups of the dedicated DL BWP.
[0199] In some example embodiments, respective one or more RB offset indications are included in the plurality of RRC configurations or the single RRC configuration for indicating start locations of the respective CORESETs in a frequency domain; and wherein start locations are associated with locations of the carrier specific frequency domain resource grids.
[0200] In some example embodiments, the two or more carriers operated within the dedicated DL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0201] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0202] FIG. 9 shows a flowchart of an example method 900 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described from the perspective of the second apparatus 120 in FIG. 1.
[0203] At block 910, the second apparatus transmits, to a first apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers.
[0204] At block 920, the second apparatus transmits, to the first apparatus, a DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP, wherein the respective CORESETs are configured by a plurality of RRC configurations separately or by a single RRC configuration jointly.
[0205] At block 930, the second apparatus transmits, to the first apparatus, DCI based on the DL control channel configuration.
[0206] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0207] In some example embodiments, the respective one or more resource sets and the respective CORESETs comprises at least one of the following: resource blocks, RB, resource-element-group, REG, bundles, one or more resource block groups, RBGs, one or more precoding resource block groups, PRGs.
[0208] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0209] In some example embodiments, the frequency domain resources configured for a CORESET contains resources of more than one carrier of the DL BWP.
[0210] In some example embodiments, an RRC configuration in the plurality of RRC, configuration indicates a frequency domain resource allocation of a CORESET of a carrier, and wherein the number of bit strings for indicating frequency domain resources are associated with the maximum number of carriers per BWP.
[0211] In some example embodiments, the single RRC configuration indicates frequency domain resource allocation of respective CORESETs across the two or more carriers and bit strings in the single RRC configuration for indicating frequency domain resources are associated with the maximum number of CORESET PRB groups of the dedicated DL BWP.
[0212] In some example embodiments, respective one or more RB offset indications are included in the plurality of RRC configurations or the single RRC configuration for indicating start locations of the respective CORESET in a frequency domain; and wherein start locations are associated with locations of the carrier specific frequency domain resource grids.
[0213] In some example embodiments, the two or more carriers operated within the dedicated DL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0214] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0215] FIG. 10 shows a flowchart of an example method 1000 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described from the perspective of the first apparatus 110 in FIG. 1.
[0216] At block 1010, the first apparatus receives, from a second apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers.
[0217] At block 1020, in accordance with a determination that DCI scheduling a DL data channel transmission is received based on the DL control channel configuration, at block 1030, the first apparatus determines a FDRA for the DL data channel transmission of the two or more carriers based on one or more FDRA indications in the DCI and carrier specific frequency domain resource grids.
[0218] At block 1040, the first apparatus receives the DL data channel transmission based on the FDRA.
[0219] In some example embodiments, the method 1000 further comprises: obtaining, from the DCI, a plurality of FDRA indications indicating respective carrier-specific FDRAs of the two or more carriers; and determining the FDRA scheduled for the DL data channel transmission from the carrier specific frequency domain resource grids by concatenating respective carrier-specific FDRAs indicated by the plurality of FDRA indications.
[0220] In some example embodiments, the plurality of FDRA indications is indicated by corresponding fields in the DCI.
[0221] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
[0222] In some example embodiments, the number of bits indicating frequency domain resources ofthe plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0223] In some example embodiments, the method 1000 further comprises: obtaining, from the DCI, a joint FDRA indication indicating FDRAs across the two or more carriers; and determining the FDRA scheduled for the DL data channel transmission from the carrier specific frequency domain resource grids based on the FDRAs across the two or more carriers.
[0224] In some example embodiments, the joint FDRA indication is indicated by a single field in the DCI.
[0225] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the resource block groups , RBGs, in the two or more carriers.
[0226] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
[0227] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0228] In some example embodiments, the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for a DL reception.
[0229] In some example embodiments, the method 1000 further comprises: obtaining a mapping between reference signal sequences and respective one or more resource sets associated with the carrier specific frequency domain resource grids; in accordance with a determination that a DL data channel transmission is scheduled via the DCI, determining based on one or more FDRA indications in the DCI, a frequency domain resource allocation for the reference signal associated with the DL data channel transmission of the two or more carriers from the carrier specific frequency domain resource grids; and determining, based on the determined frequency domain resource allocation and the mapping, respective sequences of the reference signal associated with the DL data channel transmission in the two or more carriers.
[0230] In some example embodiments, the reference signal comprises a demodulation reference signal or a phase tracking reference signal.
[0231] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0232] In some example embodiments, the method 1000 further comprises: determining respective one or more resource sets associated with the carrier specific frequency domain resource grids of the two or more carriers; and determining the dedicated DL BWP by concatenating the respective one or more resource sets in a configured order of the two or more carriers.
[0233] In some example embodiments, the respective one or more resource sets: resource blocks, RB, resource-element-group, REG, bundles, one or more resource block groups, RBGs, one or more precoding resource block groups, PRGs.
[0234] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0235] In some example embodiments, the two or more carriers operated within the dedicated DL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0236] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0237] FIG. 11 shows a flowchart of an example method 1100 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1100 will be described from the perspective of the second apparatus 120 in FIG. 1.
[0238] At block 1110, the second apparatus transmits, to a first apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers.
[0239] At block 1120, the second apparatus transmits, to the first apparatus, DCI scheduling a DL data channel transmission indicating a FDRA the two or more carriers by using one or more FDRA indications.
[0240] At block 1130, the second apparatus transmits, to the first apparatus, the DL data channel transmission based on the FDRA.
[0241] In some example embodiments, a plurality of FDRA indications is indicated by corresponding fields in the DCI.
[0242] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
[0243] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0244] In some example embodiments, the joint FDRA indication is indicated by a single field in theDCI.
[0245] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the RBGs in the two or more carriers.
[0246] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
[0247] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0248] In some example embodiments, the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for a DL reception.
[0249] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0250] In some example embodiments, respective one or more resource sets associated with the carrier specific frequency domain resource grids comprises at least one of the following: resource blocks, RB, resource-element-group, REG, bundles, one or more resource block groups, RBGs, one or more precoding resource block groups, PRGs.
[0251] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0252] In some example embodiments, the two or more carriers operated within the dedicated DL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0253] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0254] FIG. 12 shows a flowchart of an example method 1200 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1200 will be described from the perspective of the first apparatus 110 in FIG. 1.
[0255] At block 1210, the first apparatus receives, from a second apparatus, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers.
[0256] At block 1220, in accordance with a determination that DCI scheduling a UL data channel transmission is received, at block 1230, the first apparatus determines a FDRA for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP based on one or moreFDRA indications in the DCI.
[0257] At block 1240, the first apparatus transmits the uplink data channel transmission based on the FDRA.
[0258] In some example embodiments, the method 1200 further comprises: obtaining, from the DCI, a plurality of FDRA indications indicating respective carrier-specific FDRAs of the two or more carriers; and determining the FDRA scheduled for the UL data channel transmission from the carrier specific frequency domain resource grids by concatenating respective carrier-specific FDRAs indicated by the plurality of FDRA indications.
[0259] In some example embodiments, the plurality of FDRA indications is indicated by corresponding fields in the DCI.
[0260] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
[0261] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0262] In some example embodiments, the method 1200 further comprises: obtaining, from the DCI, a joint FDRA indication indicating FDRAs across the two or more carriers; and determining the FDRA scheduled for the UL data channel transmission from the carrier specific frequency domain resource grids based on the FDRAs across the two or more carriers.
[0263] In some example embodiments, the joint FDRA indication is indicated by a single field in the DCI.
[0264] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the RBGs in the two or more carriers.
[0265] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
[0266] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0267] In some example embodiments, the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for an UL transmission.
[0268] In some example embodiments, the method 1200 further comprises: obtaining a mapping between reference signal sequences and respective one or more resource sets associated with the carrier specific frequency domain resource grids; in accordance with a determination that an UL data channel transmission is scheduled via the DCI, determining based on one or more FDRA indications in the DCI, a frequency domain resource allocation for the reference signal associated with the UL data channel transmission of the two or more carriers from the carrier specific frequency domain resource grids; and determining, based on the determined frequency domain resource allocation and the mapping, respective sequences of the reference signal associated with the UL data channel transmission in the two or more carriers.
[0269] In some example embodiments, the reference signal comprises a demodulation reference signal or a phase tracking reference signal.
[0270] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0271] In some example embodiments, the method 1200 further comprises: determining respective one or more resource sets associated with the carrier specific frequency domain resource grids of the two or more carriers; and determining the dedicated UL BWP by concatenating the respective one or more resource sets in a configured order of the two or more carriers.
[0272] In some example embodiments, the respective one or more resource sets: resource blocks, RB, one or more resource block groups, RBGs, one or more precoding resource block groups, PRGs.
[0273] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0274] In some example embodiments, the two or more carriers operated within the dedicated UL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0275] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0276] FIG. 13 shows a flowchart of an example method 1300 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1300 will be described from the perspective of the second apparatus 120 in FIG. 1.
[0277] At block 1310, the second apparatus transmits, to a first apparatus, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers.
[0278] At block 1320, the second apparatus transmits, to the first apparatus, DCI scheduling a UL data channel transmission indicating a FDRA for the uplink data channel transmission of the two ormore carriers within the dedicated UL BWP by using one or more FDRA indications in the DCI.
[0279] At block 1330, the second apparatus receives the uplink data channel transmission on the FDRA.
[0280] In some example embodiments, a plurality of FDRA indications is indicated by corresponding fields in the DCI.
[0281] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
[0282] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0283] In some example embodiments, the joint FDRA indication is indicated by a single field in the DCI.
[0284] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the RBGs in the two or more carriers.
[0285] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
[0286] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0287] In some example embodiments, the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for an UL transmission.
[0288] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0289] In some example embodiments, respective one or more resource sets associated with the carrier specific frequency domain resource grids comprises at least one of the following: resource blocks, RB, one or more resource block groups, RBGs, one or more precoding resource block groups, PRGs.
[0290] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0291] In some example embodiments, the two or more carriers operated within the dedicated UL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0292] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0293] In some example embodiments, a first apparatus capable of performing any of the method 800 (for example, the first apparatus 110 in FIG. 1 ) may comprise means for performing the respective operations of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1 .
[0294] In some example embodiments, the first apparatus comprises means for receiving, from a second apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for determining the dedicated DL BWP based on the information; means for in accordance with a determination of a reception of a DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP, determining frequency domain resources configured for the respective CORESETs based on a plurality of RRC configurations or a single RRC configuration in the DL control channel configuration; and means for monitoring DCI based on the determination of the frequency domain resources.
[0295] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0296] In some example embodiments, the first apparatus further comprises: means for determining respective one or more resource sets associated with the carrier specific frequency domain resource grids of the two or more carriers; and means for determining the dedicated DL BWP by concatenating the respective one or more resource sets in a configured order of the two or more carriers.
[0297] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0298] In some example embodiments, the respective one or more resource sets and the respective CORESETs comprises at least one of the following: RB, REG bundles, one or more RBGs, or one or more PRGs.
[0299] In some example embodiments, the first apparatus further comprises: means for obtaining, from the DL control channel configuration, the plurality of RRC configurations for configuring the respective CORESETs; and means for determining frequency domain resources configured for the respective CORESETs based on respective frequency domain resource allocations, FDRAs, indicated in the plurality of RRC configurations.
[0300] In some example embodiments, an RRC configuration in the plurality of RRC, configuration indicates a frequency domain resource allocation of a CORESET of a carrier, and wherein the number of bit strings for indicating frequency domain resources are associated with the maximum number of carriers per BWP.
[0301] In some example embodiments, the first apparatus further comprises: means for receiving the single RRC configuration for configuring the respective CORESETs; and means for determining the frequency domain resources of the respective CORESETs based on an FDRA indicated in the single RRC configuration.
[0302] In some example embodiments, the single RRC configuration indicates frequency domain resource allocation of respective CORESETs across the two or more carriers and a bit string in the single RRC configuration for indicating frequency domain resources are associated with the maximum number of CORESET PRB groups of the dedicated DL BWP.
[0303] In some example embodiments, respective one or more RB offset indications are included in the plurality of RRC configurations or the single RRC configuration for indicating start locations of the respective CORESETs in a frequency domain; and wherein start locations are associated with locations of the carrier specific frequency domain resource grids.
[0304] In some example embodiments, the two or more carriers operated within the dedicated DL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0305] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0306] In some example embodiments, a second apparatus capable of performing any of the method 900 (for example, the second apparatus 120 in FIG. 1 ) may comprise means for performing the respective operations of the method 900. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 120 in FIG. 1.
[0307] In some example embodiments, the second apparatus comprises means for transmitting, to a first apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for transmitting, to the first apparatus, a DL control channel configuration including respective CORESETs of the two or more carriers within the dedicated DL BWP, wherein the respective CORESETs are configured by a plurality of RRC configurations separately or by a single RRC configuration jointly; and means for transmitting, to the first apparatus, DCI based on the DL control channel configuration.
[0308] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0309] In some example embodiments, the respective one or more resource sets and the respective CORESETs comprises at least one of the following: RB, REG bundles, one or more RBGs, or one or more PRGs.
[0310] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0311] In some example embodiments, an RRC configuration in the plurality of RRC, configuration indicates a frequency domain resource allocation of a CORESET of a carrier, and wherein the number of bit strings for indicating frequency domain resources are associated with the maximum number of carriers per BWP.
[0312] In some example embodiments, the single RRC configuration indicates frequency domain resource allocation of respective CORESETs across the two or more carriers and bit strings in the single RRC configuration for indicating frequency domain resources are associated with the maximum number of CORESET PRB groups of the dedicated DL BWP.
[0313] In some example embodiments, respective one or more RB offset indications are included in the plurality of RRC configurations or the single RRC configuration for indicating start locations of the respective CORESET in a frequency domain; and wherein start locations are associated with locations of the carrier specific frequency domain resource grids.
[0314] In some example embodiments, the two or more carriers operated within the dedicated DL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0315] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0316] In some example embodiments, a first apparatus capable of performing any of the method 1000 (for example, the first apparatus 110 in FIG. 1 ) may comprise means for performing the respective operations of the method 1000. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1 .
[0317] In some example embodiments, the first apparatus comprises means for receiving, from a second apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for in accordance with a determination that DCI scheduling a DL data channel transmission is received based on the DL control channel configuration, determining a FDRA for the DL data channel transmission of the two or more carriers based on one or more FDRA indications in the DCI and carrier specific frequency domain resource grids; and means for receiving the DL data channel transmission based on the FDRA.
[0318] In some example embodiments, the first apparatus further comprises: means for obtaining, from the DCI, a plurality of FDRA indications indicating respective carrier-specific FDRAs of the twoor more carriers; and means for determining the FDRA scheduled for the DL data channel transmission from the carrier specific frequency domain resource grids by concatenating respective carrier-specific FDRAs indicated by the plurality of FDRA indications.
[0319] In some example embodiments, the plurality of FDRA indications is indicated by corresponding fields in the DCI.
[0320] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
[0321] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0322] In some example embodiments, the first apparatus further comprises: means for obtaining, from the DCI, a joint FDRA indication indicating FDRAs across the two or more carriers; and means for determining the FDRA scheduled for the DL data channel transmission from the carrier specific frequency domain resource grids based on the FDRAs across the two or more carriers.
[0323] In some example embodiments, the joint FDRA indication is indicated by a single field in the DCI.
[0324] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the resource block groups (RBGs) in the two or more carriers.
[0325] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
[0326] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0327] In some example embodiments, the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for a DL reception.
[0328] In some example embodiments, the first apparatus further comprises: means for obtaining a mapping between reference signal sequences and respective one or more resource sets associated with the carrier specific frequency domain resource grids; means for in accordance with a determination that a DL data channel transmission is scheduled via the DCI, determining based on one or more FDRA indications in the DCI, a frequency domain resource allocation for the referencesignal associated with the DL data channel transmission of the two or more carriers from the carrier specific frequency domain resource grids; and means for determining, based on the determined frequency domain resource allocation and the mapping, respective sequences of the reference signal associated with the DL data channel transmission in the two or more carriers.
[0329] In some example embodiments, the reference signal comprises a demodulation reference signal or a phase tracking reference signal.
[0330] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0331] In some example embodiments, the first apparatus further comprises: means for determining respective one or more resource sets associated with the carrier specific frequency domain resource grids of the two or more carriers; and means for determining the dedicated DL BWP by concatenating the respective one or more resource sets in a configured order of the two or more carriers.
[0332] In some example embodiments, respective one or more resource sets associated with the carrier specific frequency domain resource grids comprises at least one of the following: RB, REG bundles, one or more RBGs, or one or more PRGs.
[0333] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0334] In some example embodiments, the two or more carriers operated within the dedicated DL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0335] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0336] In some example embodiments, a second apparatus capable of performing any of the method 1100 (for example, the second apparatus 120 in FIG. 1) may comprise means for performing the respective operations of the method 1100. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 120 in FIG. 1.
[0337] In some example embodiments, the second apparatus comprises means for transmitting, to a first apparatus, a dedicated DL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for transmitting, to the first apparatus, DCI scheduling a DL data channel transmission indicating a FDRA the two or more carriers by using one or more FDRA indications; and means for transmitting, to the first apparatus, the DL data channel transmission based on the FDRA.
[0338] In some example embodiments, a plurality of FDRA indications is indicated by corresponding fields in the DCI.
[0339] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
[0340] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0341] In some example embodiments, the joint FDRA indication is indicated by a single field in the DCI.
[0342] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the RBGs in the two or more carriers.
[0343] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
[0344] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0345] In some example embodiments, the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for a DL reception.
[0346] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0347] In some example embodiments, respective one or more resource sets associated with the carrier specific frequency domain resource grids comprises at least one of the following: RB, REG bundles, one or more RBGs, or one or more PRGs.
[0348] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0349] In some example embodiments, the two or more carriers operated within the dedicated DL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0350] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0351] In some example embodiments, a first apparatus capable of performing any of the method 1200 (for example, the first apparatus 110 in FIG. 1 ) may comprise means for performing therespective operations of the method 1200. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1 .
[0352] In some example embodiments, the first apparatus comprises means for receiving, from a second apparatus, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for in accordance with a determination that DCI scheduling a UL data channel transmission is received, determining a FDRA for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP based on one or more FDRA indications in the DCI; and means for transmitting the uplink data channel transmission based on the FDRA.
[0353] In some example embodiments, the first apparatus further comprises: means for obtaining, from the DCI, a plurality of FDRA indications indicating respective carrier-specific FDRAs of the two or more carriers; and means for determining the FDRA scheduled for the UL data channel transmission from the carrier specific frequency domain resource grids by concatenating respective carrier-specific FDRAs indicated by the plurality of FDRA indications.
[0354] In some example embodiments, the plurality of FDRA indications is indicated by corresponding fields in the DCI.
[0355] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
[0356] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0357] In some example embodiments, the first apparatus further comprises: means for obtaining, from the DCI, a joint FDRA indication indicating FDRAs across the two or more carriers; and means for determining the FDRA scheduled for the UL data channel transmission from the carrier specific frequency domain resource grids based on the FDRAs across the two or more carriers.
[0358] In some example embodiments, the joint FDRA indication is indicated by a single field in the DCI.
[0359] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the RBGs in the two or more carriers.
[0360] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of activesub-BWPs across the two or more carriers.
[0361] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0362] In some example embodiments, the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for an UL transmission.
[0363] In some example embodiments, the first apparatus further comprises: means for obtaining a mapping between reference signal sequences and respective one or more resource sets associated with the carrier specific frequency domain resource grids; means for in accordance with a determination that an UL data channel transmission is scheduled via the DCI, determining based on one or more FDRA indications in the DCI, a frequency domain resource allocation for the reference signal associated with the UL data channel transmission of the two or more carriers from the carrier specific frequency domain resource grids; and means for determining, based on the determined frequency domain resource allocation and the mapping, respective sequences of the reference signal associated with the UL data channel transmission in the two or more carriers.
[0364] In some example embodiments, the reference signal comprises a demodulation reference signal or a phase tracking reference signal.
[0365] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
[0366] In some example embodiments, the first apparatus further comprises: means for determining respective one or more resource sets associated with the carrier specific frequency domain resource grids of the two or more carriers; and means for determining the dedicated UL BWP by concatenating the respective one or more resource sets in a configured order of the two or more carriers.
[0367] In some example embodiments, respective one or more resource sets associated with the carrier specific frequency domain resource grids comprises at least one of the following: RB, one or more RBGs, or one or more PRGs.
[0368] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0369] In some example embodiments, the two or more carriers operated within the dedicated UL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0370] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0371] In some example embodiments, a second apparatus capable of performing any of the method1300 (for example, the second apparatus 120 in FIG. 1) may comprise means for performing the respective operations of the method 1300. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 120 in FIG. 1.
[0372] In some example embodiments, the second apparatus comprises means for transmitting, to a first apparatus, a dedicated UL BWP configuration including information of carrier specific frequency domain resource grids of two or more carriers; means for transmitting, to the first apparatus, DCI scheduling a UL data channel transmission indicating a FDRA for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP by using one or more FDRA indications in the DCI; and means for receiving the uplink data channel transmission on the FDRA.
[0373] In some example embodiments, a plurality of FDRA indications is indicated by corresponding fields in the DCI.
[0374] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
[0375] In some example embodiments, the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0376] In some example embodiments, the joint FDRA indication is indicated by a single field in the DCI.
[0377] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the RBGs in the two or more carriers.
[0378] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
[0379] In some example embodiments, the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub-BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.
[0380] In some example embodiments, the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for an UL transmission.
[0381] In some example embodiments, the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specificfrequency domain resource grids.
[0382] In some example embodiments, respective one or more resource sets associated with the carrier specific frequency domain resource grids comprises at least one of the following: RB, one or more RBGs, or one or more PRGs.
[0383] In some example embodiments, sizes of respective one or more resource sets on at least two carriers are different.
[0384] In some example embodiments, the two or more carriers operated within the dedicated UL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
[0385] In some example embodiments, the first apparatus comprises a terminal device and the second apparatus comprises a network node.
[0386] FIG. 14 is a simplified block diagram of a device 1400 that is suitable for implementing example embodiments of the present disclosure. The device 1400 may be provided to implement a communication device, for example, the first apparatus 110 or the second apparatus 120 as shown in FIG. 1. As shown, the device 1400 includes one or more processors 1410, one or more memories 1420 coupled to the processor 1410, and one or more communication modules 1440 coupled to the processor 1410.
[0387] The communication module 1440 is for bidirectional communications. The communication module 1440 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 1440 may include at least one antenna.
[0388] The processor 1410 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1400 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0389] The memory 1420 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1424, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 1422 and other volatile memories that will not last in the power-down duration.
[0390] A computer program 1430 includes computer executable instructions that are executed bythe associated processor 1410. The instructions of the program 1430 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 1430 may be stored in the memory, e.g., the ROM 1424. The processor 1410 may perform any suitable actions and processing by loading the program 1430 into the RAM 1422.
[0391] The example embodiments of the present disclosure may be implemented by means of the program 1430 so that the device 1400 may perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 13. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0392] In some example embodiments, the program 1430 may be tangibly contained in a computer readable medium which may be included in the device 1400 (such as in the memory 1420) or other storage devices that are accessible by the device 1400. The device 1400 may load the program 1430 from the computer readable medium to the RAM 1422 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e. , tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).
[0393] FIG. 15 shows an example of the computer readable medium 1500 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1500 has the program 1430 stored thereon.
[0394] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0395] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modulesmay be combined or split between program modules as desired in various embodiments. Machineexecutable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0396] Program code for carrying out methods of the present 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, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0397] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0398] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0399] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable subcombination.
[0400] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
WHAT IS CLAIMED IS:1 . A first apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive, from a second apparatus, a dedicated uplink bandwidth part, UL BWP, configuration including information of carrier specific frequency domain resource grids of two or more carriers; in accordance with a determination that downlink control information, DCI, scheduling a UL data channel transmission is received, determine a frequency domain resource allocation, FDRA, for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP based on one or more FDRA indications in the DCI; and transmit the uplink data channel transmission based on the FDRA.
2. The first apparatus of claim 1 , wherein the first apparatus is caused to: obtain, from the DCI, a plurality of FDRA indications indicating respective carrier-specific FDRAs of the two or more carriers; and determine the FDRA scheduled for the UL data channel transmission from the carrier specific frequency domain resource grids by concatenating respective carrier-specific FDRAs indicated by the plurality of FDRA indications.
3. The first apparatus of claim 2, wherein the plurality of FDRA indications is indicated by corresponding fields in the DCI.
4. The first apparatus of claim 3, wherein the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
5. The first apparatus of claim 3, wherein the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
6. The first apparatus of claim 1 , wherein the first apparatus is caused to:obtain, from the DCI, a joint FDRA indication indicating FDRAs across the two or more carriers; and determine the FDRA scheduled for the UL data channel transmission from the carrier specific frequency domain resource grids based on the FDRAs across the two or more carriers.
7. The first apparatus of claim 6, wherein the joint FDRA indication is indicated by a single field in the DCI.
8. The first apparatus of claim 7, wherein the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the RBGs in the two or more carriers.
9. The first apparatus of claim 7, wherein the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
10. The first apparatus of claim 7, wherein the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub- BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.11 . The first apparatus of any of claims 4, 5, 9 and 10, wherein the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for an UL transmission.
12. The first apparatus of claim 1 , wherein the first apparatus is caused to: obtain a mapping between reference signal sequences and respective one or more resource sets associated with the carrier specific frequency domain resource grids; in accordance with a determination that an UL data channel transmission is scheduled via the DCI, determine, based on one or more FDRA indications in the DCI, a frequency domain resource allocation for the reference signal associated with the UL data channel transmission of the two or more carriers from the carrier specific frequency domain resource grids; and determine, based on the determined frequency domain resource allocation and the mapping, respective sequences of the reference signal associated with the UL data channel transmission in the two or more carriers.
13. The first apparatus of claim 12, wherein the reference signal comprises a demodulation referencesignal or a phase tracking reference signal.
14. The first apparatus of any of claims 1 -13, wherein the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
15. The first apparatus of any of claims 1-14, wherein the first apparatus is caused to: determine respective one or more resource sets associated with the carrier specific frequency domain resource grids of the two or more carriers; and determine the dedicated UL BWP by concatenating the respective one or more resource sets in a configured order of the two or more carriers.
16. The first apparatus of claim 15, wherein the respective one or more resource sets : resource blocks, RB, one or more resource block groups, RBGs, one or more precoding resource block groups, PRGs.
17. The first apparatus of claim 15 or 16, wherein sizes of respective one or more resource sets on at least two carriers are different.
18. The first apparatus of any of claims 1-17, wherein the two or more carriers operated within the dedicated UL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
19. A second apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: transmit, to a first apparatus, a dedicated uplink bandwidth part, UL BWP, configuration including information of carrier specific frequency domain resource grids of two or more carriers; transmit, to the first apparatus, downlink control information, DCI, scheduling a UL data channel transmission indicating a frequency domain resource allocation, FDRA, for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP by using one or more FDRA indications in the DCI; and receive the uplink data channel transmission on the FDRA.
20. The second apparatus of claim 19, wherein a plurality of FDRA indications is indicated by corresponding fields in the DCI.
21. The second apparatus of claim 20, wherein the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers and respective sizes of active sub-BWPs of the two or more carriers.
22. The second apparatus of claim 20, wherein the number of bits indicating frequency domain resources of the plurality of FDRA indications is associated with the number of the two or more carriers, respective sizes and starts of active sub-BWPs on the two or more carriers and respective resource allocation type 1 granularity per carrier.
23. The second apparatus of claim 19, wherein the joint FDRA indication is indicated by a single field in the DCI.
24. The first apparatus of claim 23 wherein the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and respective numbers of the RBGs in the two or more carriers.
25. The first apparatus of claim 23, wherein the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers and a size of active sub-BWPs across the two or more carriers.
26. The first apparatus of claim 23, wherein the number of bits indicating frequency domain resources in the joint FDRA indication is associated with the number of the two or more carriers, a size of active sub- BWPs across the two or more carriers, a start carrier of the two or more carriers and respective resource allocation type 1 granularity per carrier.
27. The second apparatus of any of claims 21 , 22, 25 and 26, wherein the active sub-BWP corresponds to a carrier specific frequency domain resource grid available for an UL transmission.
28. The second apparatus of any of claims 19-27, wherein the information of the carrier specific frequency domain resource grids of two or more carriers comprises respective reference points of the carrier specific frequency domain resource grids.
29. The second apparatus of any of claims 19-28, wherein respective one or more resource sets associated with the carrier specific frequency domain resource grids: resource blocks, RB, one or more resource block groups, RBGs, one or more precoding resource block groups, PRGs.
30. The second apparatus of claim 29, wherein sizes of respective one or more resource sets on at least two carriers are different.31 . The second apparatus of any of claims 19-30, wherein the two or more carriers operated within the dedicated UL BWP are adjacent or non-adjacent carriers within a frequency band or across frequency bands.
32. A method comprising: receiving, from a second apparatus, a dedicated uplink bandwidth part, UL BWP, configuration including information of carrier specific frequency domain resource grids of two or more carriers; in accordance with a determination that downlink control information, DCI, scheduling a UL data channel transmission is received, determining a frequency domain resource allocation, FDRA, for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP based on one or more FDRA indications in the DCI; and transmitting the uplink data channel transmission based on the FDRA.
33. A method comprising: transmitting, to a first apparatus, a dedicated uplink bandwidth part, UL BWP, configuration including information of carrier specific frequency domain resource grids of two or more carriers; transmitting, to the first apparatus, downlink control information, DCI, scheduling a UL data channel transmission indicating a frequency domain resource allocation, FDRA, for the uplink data channel transmission of the two or more carriers within the dedicated UL BWP by using one or more FDRA indications in the DCI; and receiving the uplink data channel transmission on the FDRA.