Method and apparatus for frequency domain resource allocation on multiple carriers
By configuring the processor in the wireless communication system, determining the payload size of the DCI format and allocating resource blocks on multiple carriers, virtual carriers and virtual activity BWP are used to solve the signaling overhead of multi-carrier frequency domain resource allocation in wireless communication systems. The major problem has achieved efficient spectrum and power utilization.
Patent Information
- Application Number
- CN202280094359.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-01
- Publication Date
- 2024-11-15
AI Technical Summary
In existing wireless communication systems, the allocation of frequency domain resources on multiple carriers scheduled by a single downlink control information (DCI) has problems such as large signaling overhead and difficulty in determining the size of the DCI payload.
By configuring the processor in user equipment (UE) and base station (BS), determining the payload size of the DCI format and allocating resource blocks (RBs) on multiple carriers based on the DCI format, adopting the concepts of virtual carriers and virtual active BWP , indicates resource allocation through the FDRA field, reduce signaling overhead and dynamically adjust the carrier configuration.
The frequency domain resource allocation of downlink and uplink is realized efficiently scheduling on multiple carriers, reducing signaling overhead, improving spectrum and power efficiency, and adapting to the utilization of different spectrum bands.
Smart Images

Figure CN118975375A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate generally to wireless communication techniques, and more particularly to frequency domain resource allocation on multiple carriers scheduled by a single downlink control information (DCI). Background Art
[0002] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, and broadcasts. Wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of wireless communication systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), or LTE-A Pro systems, and fifth-generation (5G) systems, which may also be referred to as New Radio (NR) systems.
[0003] In wireless communication systems, user equipment (UE) may monitor the Physical Downlink Control Channel (PDCCH) in one or more search spaces. The PDCCH may carry Downlink Control Information (DCI), which may schedule uplink channels (e.g., the Physical Uplink Shared Channel (PUSCH)) or downlink channels (e.g., the Physical Downlink Shared Channel (PDSCH)).
[0004] There is a need to handle frequency domain resource allocation for uplink and downlink transmissions scheduled by DCI in wireless communication systems. Summary of the Invention
[0005] Some embodiments of the present disclosure provide a user equipment (UE). The UE may include: a transceiver; and a processor coupled to the transceiver. The processor may be configured to: determine a payload size of a downlink control information (DCI) format, wherein the DCI format schedules a first plurality of carriers among a second plurality of carriers, wherein the second plurality of carriers is configured by a base station (BS); receive the DCI format from the BS according to the determined payload size, wherein the first plurality of carriers is indicated by a first indicator of the DCI format or is configured by the BS; determine resource blocks (RBs) allocated on the first plurality of carriers based on the DCI format; and, if the DCI format schedules a downlink transmission, receive the downlink transmission on the allocated RB, or if the DCI format schedules an uplink transmission, transmit the uplink transmission on the allocated RB.
[0006] Some embodiments of the present disclosure provide a base station (BS). The BS may include: a transceiver; and a processor coupled to the transceiver. The processor may be configured to: configure a second plurality of carriers for a user equipment (UE); transmit to the UE a downlink control information (DCI) format for scheduling a plurality of resource blocks (RBs) on a first plurality of carriers among the second plurality of carriers for transmission, wherein the first plurality of carriers is indicated by a first indicator in the DCI format or configured by the BS to the UE; and transmit a downlink transmission on the plurality of RBs if the DCI format schedules a downlink transmission, or receive an uplink transmission on the plurality of RBs if the DCI format schedules an uplink transmission.
[0007] Some embodiments of the present disclosure provide a method for wireless communication performed by a user equipment (UE). The method may include: determining a payload size of a downlink control information (DCI) format, wherein the DCI format schedules a first plurality of carriers among a second plurality of carriers, wherein the second plurality of carriers is configured by a base station (BS); receiving the DCI format from the BS according to the determined payload size, wherein the first plurality of carriers is indicated by a first indicator of the DCI format or is configured by the BS; determining resource blocks (RBs) allocated on the first plurality of carriers based on the DCI format; and receiving the downlink transmission on the allocated RBs if the DCI format schedules a downlink transmission, or transmitting the uplink transmission on the allocated RBs if the DCI format schedules an uplink transmission.
[0008] Some embodiments of the present disclosure provide a method for wireless communication performed by a base station. The method may include: configuring a second plurality of carriers for a user equipment (UE); transmitting a downlink control information (DCI) format to the UE for scheduling a plurality of resource blocks (RBs) on a first plurality of carriers among the second plurality of carriers for transmission, wherein the first plurality of carriers is indicated by a first indicator in the DCI format or configured by the base station to the UE; and transmitting a downlink transmission on the plurality of RBs if the DCI format schedules a downlink transmission, or receiving an uplink transmission on the plurality of RBs if the DCI format schedules an uplink transmission.
[0009] Some embodiments of the present disclosure provide an apparatus. According to some embodiments of the present disclosure, the apparatus may include: at least one non-transitory computer-readable medium having computer-executable instructions stored thereon; at least one receiving circuitry; at least one transmitting circuitry; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuitry, and the at least one transmitting circuitry, wherein the at least one non-transitory computer-readable medium and the computer-executable instructions may be configured to cause the apparatus to perform methods according to some embodiments of the present disclosure using the at least one processor. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] To illustrate the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is presented by reference to specific embodiments of the disclosure illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the disclosure and therefore should not be considered limiting of its scope.
[0011] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present disclosure;
[0012] Figure 2 A schematic diagram illustrating a DCI format for scheduling multiple transmissions according to some embodiments of the present disclosure;
[0013] Figure 3 illustrating exemplary radio resource allocation according to some embodiments of the present disclosure;
[0014] Figure 4 illustrating exemplary radio resource allocation according to some embodiments of the present disclosure;
[0015] Figure 5 illustrating exemplary radio resource allocation according to some embodiments of the present disclosure;
[0016] Figure 6 a flow chart illustrating an exemplary process for wireless communication according to some embodiments of the present disclosure;
[0017] Figure 7 a flowchart illustrating an exemplary process for wireless communication according to some embodiments of the present disclosure; and
[0018] Figure 8 A block diagram illustrating an exemplary apparatus according to some embodiments of the present disclosure. DETAILED DESCRIPTION
[0019] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present disclosure and is not intended to represent the only form in which the present disclosure can be practiced. It should be understood that the same or equivalent functions can be achieved by different embodiments intended to be included within the spirit and scope of the present disclosure.
[0020] Reference will now be made in detail to some embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. To facilitate understanding, the embodiments are provided in the context of specific network architectures and new service scenarios, such as 3rd Generation Partnership Project (3GPP) 5G (NR), 3GPP Long Term Evolution (LTE) Release 8, etc. It is contemplated that as network architectures and new service scenarios evolve, all embodiments of the present disclosure will also be applicable to similar technical issues. Furthermore, the terms used in the present disclosure may vary without affecting the principles of the present disclosure.
[0021] Figure 1 A schematic diagram illustrating a wireless communication system 100 according to some embodiments of the present disclosure.
[0022] like Figure 1 As shown in FIG, a wireless communication system 100 may include some UEs 101 (e.g., UE 101a and UE 101b) and a base station (e.g., BS 102). Figure 1 A specific number of UEs 101 and BSs 102 are depicted in FIG. 1 , but it is contemplated that any number of UEs and BSs may be included in the wireless communication system 100 .
[0023] UE 101 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), an in-vehicle computer, a network device (e.g., a router, a switch, and a modem), etc. According to some embodiments of the present disclosure, UE 101 may include a portable wireless communication device, a smartphone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals on a wireless network. In some embodiments of the present disclosure, UE 101 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, UE 101 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terms used in the art. UE 101 may communicate with BS 102 via uplink (UL) communication signals.
[0024] BSs 102 may be distributed throughout a geographic area. In certain embodiments of the present disclosure, BSs 102 may also be referred to as access points, access terminals, base stations, base units, macrocells, Node Bs, evolved Node Bs (eNBs), gNBs, home Node Bs, relay nodes, or devices, or other terms used in the art. BSs 102 are typically part of a radio access network, which may include one or more controllers communicatively coupled to one or more corresponding BSs 102. BSs 102 may communicate with UEs 101 via downlink (DL) communication signals.
[0025] The wireless communication system 100 is compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with wireless communication networks, cellular telephone networks, time division multiple access (TDMA)-based networks, code division multiple access (CDMA)-based networks, orthogonal frequency division multiple access (OFDMA)-based networks, LTE networks, 3GPP-based networks, 3GPP 5G networks, satellite communication networks, high altitude platform networks, and / or other communication networks.
[0026] In some embodiments of the present disclosure, the wireless communication system 100 is compatible with the 5G NR of the 3GPP protocol. For example, the BS 102 may transmit data on the DL using an Orthogonal Frequency Division Multiplexing (OFDM) modulation scheme, and the UE 101 may transmit data on the UL using a Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) or a Cyclic Prefix OFDM (CP-OFDM) scheme. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocols, such as WiMAX and other protocols.
[0027] In some embodiments of the present disclosure, BS 102 and UE 101 may communicate using other communication protocols (e.g., the IEEE 802.11 family of wireless communication protocols). Furthermore, in some embodiments of the present disclosure, BS 102 and UE 101 may communicate over a licensed spectrum, while in some other embodiments, BS 102 and UE 101 may communicate over an unlicensed spectrum. The present disclosure is not intended to be limited to implementations of any particular wireless communication system architecture or protocol.
[0028] Communication technologies (e.g., NR) can support a wide range of spectrum in different frequency ranges. For example, in markets with advanced 5G, the availability of spectrum is expected to increase, possibly due to re-farming of frequency bands originally used for previous-generation cellular networks. For example, for some low-frequency bands in frequency range 1 (FR1) (e.g., 410 MHz to 7125 MHz), the available spectrum bands tend to be more fragmented and dispersed with narrower bandwidths. In addition, for frequency bands in frequency range 2 (FR2) (e.g., 24250 MHz to 52600 MHz) and some frequency bands in FR1, the available spectrum may be wider, making intra-band multi-carrier operation necessary.
[0029] In order to meet different spectrum needs, it is important to ensure that these fragmented or dispersed spectrum bands or spectrum with wider bandwidth are utilized in a more spectrally and power-efficient and flexible manner, thereby providing higher throughput and appropriate coverage in the network.
[0030] For example, one motivation is to improve the spectrum / power efficiency and flexibility of scheduling data on multiple cells (including intra-band cells and inter-band cells). In some instances, the scheduling mechanism may only allow scheduling of a single PUSCH or PDSCH on a single cell per scheduling DCI. As more dispersed spectrum bands or spectrum with wider bandwidth become available, it is desirable to allow simultaneous scheduling of multiple cells.
[0031] A communication system (e.g., NR) may be designed to support a maximum of 16 component carriers (CCs) in the case of carrier aggregation (CA), or a maximum of 32 CCs in the case of dual connectivity (DC). In some embodiments of the present application, in the case of CA, one DCI may schedule up to one carrier through cross-carrier scheduling or self-scheduling. When the number of carriers configured for a UE is large, this requires a large amount of signaling overhead for the PDCCH to schedule the PDSCH or PUSCH. To reduce signaling overhead, it would be beneficial to use a single DCI to schedule multiple PDSCHs or PUSCHs on multiple carriers configured for the UE.
[0032] Figure 2 A diagram illustrating a DCI format for scheduling multiple transmissions according to some embodiments of the present disclosure.
[0033] In some embodiments of the present disclosure, multiple CCs (including but not limited to) may be configured for a UE. Figure 2 231 to 234 in the CCs). It should be understood that the subcarrier spacing (SCS) of the carriers configured for the UE may be the same or different. Each of the multiple CCs may correspond to a respective serving cell of the UE. Each serving cell may be associated with a serving cell index.
[0034] like Figure 2As shown in FIG, the BS can transmit a single DCI format 211 to schedule four transmissions on four carriers, rather than using four DCI formats to respectively schedule four transmissions on four carriers (eg, CCs 231 to 234) (eg, Figure 2 221 to 224). In some examples, transmissions 221 to 224 may be uplink transmissions (e.g., PUSCH). In some examples, transmissions 221 to 224 may be downlink transmissions (e.g., PDSCH).
[0035] Despite Figure 2 221 to 224, but it should be understood that DCI format 211 may be located on a carrier configured for the UE that is different from the carrier carrying scheduled transmissions 221 to 224 (i.e., CCs 231 to 234). It should also be understood that a carrier (e.g., CC) scheduled by a DCI format may carry more than one transmission (e.g., PDSCH or PUSCH). For example, a DCI format may schedule two PDSCHs on CC 232.
[0036] When a DCI format schedules a single transmission on a single carrier, the DCI format may indicate the frequency domain resources allocated on the scheduled carrier for the scheduled transmission. This may not be applicable when a single DCI format schedules multiple transmissions (e.g., PDSCH or PUSCH) on multiple carriers. For example, because different carriers may use different parameter sets and may have different bandwidths, a single frequency domain resource allocation (FDRA) in a single DCI format may not be applicable to multiple scheduled carriers, or it will result in significant scheduling restrictions. In some embodiments, a separate FDRA field in the DCI format for each of the scheduled carriers may be used. However, this will result in huge signaling overhead in the scheduling DCI. Embodiments of the present application propose an improved solution for indicating the FDRA for the scheduled carrier, which can reduce overhead.
[0037] On the other hand, before detecting a DCI format, the UE needs to know the exact payload size of the DCI format. Since the number of carriers scheduled by a DCI format may change dynamically, it will affect the DCI payload size. Therefore, how to determine the payload size of a DCI format should also be addressed.
[0038] More details about the embodiments of the present disclosure will be described below in conjunction with the accompanying drawings. It should be noted that the solution of the present disclosure is applicable to both downlink transmissions (eg, PDSCH) and uplink transmissions (eg, PUSCH) scheduled by DCI formats.
[0039] In some embodiments of the present disclosure, where a single DCI format can schedule multiple carriers (also referred to as "serving cells") for downlink or uplink transmission, an indicator in the DCI format (e.g., a single FDRA field) indicates the resource blocks (RBs) allocated on the scheduled carriers. Based on certain principles, the scheduled carriers can be virtually combined into a virtual carrier. The FDRA field in the DCI format indicates the allocated RBs on the virtual carrier.
[0040] For example, referring to the starting RB from the starting RB to the ending RB, all RBs on all scheduled carriers are virtually combined and numbered consecutively across all scheduled carriers. From the UE's perspective, the frequency resources of all scheduled carriers are combined and can be logically viewed as a wider carrier (e.g., a virtual carrier). Due to the consecutive RB numbering of all scheduled carriers, the bandwidth of the virtual carrier may exceed the predefined maximum number of RBs per carrier (e.g., 275 RBs).
[0041] Various methods may be applied to group the scheduled carriers and number the RBs. For example, the scheduled carriers may be grouped according to a predefined order (eg, carrier index or frequency position of the scheduled carriers).
[0042] In some embodiments, scheduled carriers may be combined into a virtual carrier according to an ascending order of their carrier indexes. In some instances, the lowest RB on the lowest carrier (e.g., lowest in the frequency domain) among the scheduled carriers in the virtual carrier may be used as the starting RB for numbering the RBs of the virtual carrier. The highest RB on the highest carrier (e.g., highest in the frequency domain) among the scheduled carriers in the virtual carrier may be used as the ending RB for numbering the RBs of the virtual carrier. In some other instances, the highest RB on the highest carrier among the scheduled carriers in the virtual carrier may be used as the starting RB for numbering the RBs of the virtual carrier. The lowest RB on the lowest carrier among the scheduled carriers in the virtual carrier may be used as the ending RB for numbering the RBs of the virtual carrier.
[0043] In some embodiments, scheduled carriers may be combined into a virtual carrier according to an ascending order of their carrier frequencies. In some instances, the lowest RB on the lowest carrier among the scheduled carriers in the virtual carrier may be used as the starting RB for numbering the RBs of the virtual carrier. The highest RB on the highest carrier among the scheduled carriers in the virtual carrier may be used as the ending RB for numbering the RBs of the virtual carrier. In some other instances, the highest RB on the highest carrier among the scheduled carriers in the virtual carrier may be used as the starting RB for numbering the RBs of the virtual carrier. The lowest RB on the lowest carrier among the scheduled carriers in the virtual carrier may be used as the ending RB for numbering the RBs of the virtual carrier.
[0044] Figure 3 An example method for combining CCs 231 to 234 scheduled by DCI format 211 in Figure 2 into a virtual carrier and numbering the virtual carrier is presented. It is assumed that the values of the serving cell indices of CCs 231 to 234 have the relationship of CC 231 < CC 232 < CC 233 < CC 234. In some examples, the CCs 231 to 234 carrying the scheduled transmissions 221 to 224 may be arranged as carrier 330 in ascending order of their carrier indices, as shown in Figure 3 . RB 341 represents the lowest RB of the lowest carrier (e.g., CC 231) among the scheduled carriers in carrier 330. RB 342 represents the highest RB of the highest carrier (e.g., CC 234) among the scheduled carriers in carrier 330. In some examples, RB 341 and RB 342 may be used as the starting RB and the ending RB for numbering the RBs of carrier 330. For example, the RBs on carrier 330 may be numbered continuously from RB 341 (RB0) to RB 342 (RB y-1 ), where y represents the total number of RBs on CCs 231 to 234. The FDRA field of DCI format 211 may indicate the allocated RBs on carrier 330. The UE may determine the allocated RBs on CCs 231 to 234 for transmissions 221 to 224 based on the FDRA field and the resource allocation type, which will be described in detail below.
[0045] Various methods may be applied to indicate the carriers scheduled by DCI format.
[0046] In some embodiments, the scheduled carriers may be dynamically indicated from multiple carriers configured for the UE by DCI format. For example, the scheduled carriers may be arranged continuously in the multiple configured carriers according to a predefined order (e.g., the carrier index or frequency position of the scheduled carriers). In some examples, the DCI format may jointly indicate the first scheduled carrier in the consecutive scheduled carriers and the number of consecutive scheduled carriers in the multiple configured carriers. In some examples, the DCI format may indicate the number of consecutive scheduled carriers in the multiple configured carriers. The carrier in which the DCI format is detected is assumed to be the first scheduled carrier in the consecutive scheduled carriers. In some examples, the DCI format may indicate a carrier combination from a set of carrier combinations. The set of carrier combinations may be configured by the BS via, for example, RRC signaling. In other examples, the DCI format may indicate a bitmap, where each bit corresponds to a respective carrier in the multiple configured carriers.
[0047] In some embodiments, the scheduled carriers may be configured by the BS via, for example, RRC signaling. For example, the BS may configure a carrier combination from a plurality of configured carriers. Thus, the scheduled carriers are known to the UE before detecting the scheduling DCI.
[0048] From the UE's perspective, if the scheduled carriers are dynamically indicated by the DCI format, the UE cannot know the DCI payload size before decoding the DCI because the number of bits in the FDRA field may vary depending on the number of scheduled carriers and the number of RBs on each scheduled carrier. To avoid additional blind DCI detection, the payload size of the DCI format should be predetermined, for example, based on the maximum number of schedulable carriers for a single DCI and the maximum number of RBs on a carrier.
[0049] In the following context, N represents the maximum number of carriers that can be scheduled by a single DCI, K represents the maximum number of RBs on a carrier, and Y represents the maximum total number of RBs that can be scheduled by a single DCI. In some examples, N can be configured through RRC signaling or predefined in the standard, for example.
[0050] In some embodiments, Y = K * N. In some instances, K is equal to a predefined maximum number of RBs per carrier (e.g., 275). For example, when N = 4 and K = 275, Y = 4 × 275 = 1100. In some instances, K is equal to the maximum number of RBs per carrier within the set of configured carriers. For example, assume that n carriers (e.g., carrier #1 to carrier #n) are configured for a UE, and carrier #1 includes k1 RBs, carrier #2 includes k2 RBs, carrier #3 includes k3 RBs, ..., and carrier #n includes k n RBs, then K=max{k1,k2,k3,...,k n In some embodiments, Y=Z1+Z2+...+Z N , where Z1, Z2, ..., Z N is the set {k1,k2,k3,...,k n} among the N largest values.
[0051] The UE may determine the FDRA field size based on the maximum total number of schedulable RBs (Y) and the configured or indicated resource allocation type (eg, resource allocation type 0, resource allocation type 1, or both as specified in 3GPP specifications).
[0052] For example, when only resource allocation type 0 is configured, assuming that N RBGThe FDRA field is indicated by a bit. The resource block allocation information includes a bitmap indicating the resource block group (RBG) allocated to the UE. An RBG is a set of contiguous RBs (e.g., virtual resource blocks (VRBs)) defined based on, for example, Table 1 below. It should be understood that Table 1 is for illustrative purposes only and should not be construed as limiting the embodiments of the present disclosure.
[0053] Table 1: RBG size of P
[0054] Y Configuration 1 Configuration 2 1 to 36 2 4 37 to 72 4 8 73 to 144 8 16 145 to 275 16 16 276 to 550 32 32 551 to 1100 64 64 >1100 128 128
[0055] Since the number of all RBs on a scheduled carrier may exceed the limit of the predefined maximum number of RBs per carrier (e.g., 275 RBs), entries with Y values greater than 275 are included to provide larger RBG sizes to control the number of bits required for the FDRA field.
[0056] The number of bits in the FDRA field is equal to the total number of RBGs of all RBs on the scheduled carrier (N RBG ), which is composed of N RBG =[Y / P]. According to Table 1 above, when the maximum total number of schedulable RBs (Y) is 280 (i.e., between "276 and 550"), the number of VRBs in an RBG is 32 in case of configuration 1 or configuration 2. The FDRA field may contain 9 bits (i.e., [280 / 32]).
[0057] For example, when configuring only resource allocation type 1, you might need Bit is used to indicate the FDRA field.
[0058] For example, when both resource allocation types 0 and 1 are configured, or when resource allocation (eg, indicated by a higher layer parameter "resourceAllocation") is configured as dynamic switching (eg, resourceAllocation = 'dynamicSwitch'), then it may be necessary A bit is used to indicate the FDRA field. A specific bit (e.g., the most significant bit (MSB)) of the FDRA field can be used to indicate resource allocation type 0 or resource allocation type 1. For example, a bit value of "0" of the MSB indicates resource allocation type 0, and a bit value of "1" of the MSB indicates resource allocation type 1; or vice versa. For resource allocation type 0, a specific bit of the FDRA field RBG bits (e.g., N RBG The least significant bits (LSBs) of the FDRA field may provide resource allocation according to Table 1. For resource allocation type 1, the specific bits (e.g., LSBs) may provide resource allocation according to an indication based on a resource indication value (RIV).
[0059] At the UE side, the UE may blindly detect the DCI format based on the payload size determined according to the maximum number of RBs that can be scheduled by the DCI format (e.g., Y) and the resource allocation type. In response to receiving the DCI format, the UE may determine the scheduled carriers and determine the RBs allocated on the scheduled carriers based on the DCI format. For example, the UE may group the scheduled carriers according to a predefined order (e.g., in order of carrier index or carrier frequency position), number all RBs in the virtual carrier from the start RB to the end RB, and determine the allocated RBs based on the FDRA field and the resource allocation type. Once the allocated RBs are determined, the UE knows the distribution of the allocated RBs on each scheduled carrier and receives the PDSCH or transmits the PUSCH on the scheduled carrier.
[0060] In the case where the scheduled carrier is configured by the BS as, for example, a carrier combination from multiple configured carriers, the scheduled carrier is known to the UE before detecting the scheduling DCI format. The UE can determine the payload size of the DCI format because the number of bits of the FDRA field can be predetermined based on the total number of RBs on the scheduled carrier (denoted as Y') and the configured or indicated resource allocation type. For example, the UE can sum the number of RBs on each of the scheduled carriers to determine the value of Y' and determine the number of bits of the FDRA field of the DCI format based on Y' and the resource allocation type according to a process similar to that described above.
[0061] For example, when configuring only resource allocation type 0, you might need bit is used to indicate the FDRA field. For example, when only resource allocation type 1 is configured, it may be necessary to The FDRA field may be used to indicate the FDRA field. For example, when both resource allocation types 0 and 1 are configured or when resource allocation is configured for dynamic switching, the FDRA field may be used to indicate the FDRA field. Bit is used to indicate the FDRA field.
[0062] The above embodiments may be applicable to scheduled carriers having the same or different SCS values. The above embodiments may be applicable to scenarios where all scheduled carriers are configured with the same resource allocation type.
[0063] In some embodiments of the present disclosure, when a single DCI format can schedule multiple carriers for downlink or uplink transmission, an indicator in the DCI format (e.g., a single FDRA field) indicates the RBs allocated on the scheduled carriers. Based on certain principles, the active bandwidth parts (BWPs) of the scheduled carriers can be virtually combined into a virtual active BWP. The FDRA field in the DCI format indicates the allocated RBs on the virtual BWP.
[0064] For example, with respect to the starting RB from the starting RB to the ending RB, all RBs within the active BWP on all scheduled carriers are virtually combined and numbered consecutively across all scheduled carriers. From the UE's perspective, the frequency resources of the active BWPs on all scheduled carriers are combined and can be logically viewed as a wider active BWP (e.g., a virtual active BWP). Due to the consecutive RB numbering of the active BWPs on all scheduled carriers, the bandwidth of the virtual active BWP may exceed the limit of the predefined maximum number of RBs per carrier (e.g., 275 RBs).
[0065] Various methods may be applied to group active BWPs on scheduled carriers and number RBs. For example, active BWPs on scheduled carriers may be grouped according to a predefined order (eg, carrier index or frequency position of the scheduled carriers).
[0066] In some embodiments, active BWPs on scheduled carriers may be combined into a virtual active BWP based on ascending order of the carrier index of the corresponding scheduled carriers. In some instances, the lowest RB on the active BWP on the lowest carrier among the scheduled carriers in the virtual BWP may be used as the starting RB for numbering RBs of the virtual BWP. The highest RB on the active BWP on the highest carrier among the scheduled carriers in the virtual BWP may be used as the ending RB for numbering RBs of the virtual BWP. In some other instances, the highest RB on the active BWP on the highest carrier among the scheduled carriers in the virtual BWP may be used as the starting RB for numbering RBs of the virtual BWP. The lowest RB on the active BWP on the lowest carrier among the scheduled carriers in the virtual BWP may be used as the ending RB for numbering RBs of the virtual BWP.
[0067] In some embodiments, active BWPs on scheduled carriers may be combined into a virtual active BWP based on ascending order of the carrier frequencies of the corresponding scheduled carriers. In some instances, the lowest RB on the active BWP on the lowest carrier among the scheduled carriers in the virtual BWP may be used as the starting RB for numbering the RBs of the virtual BWP. The highest RB on the active BWP on the highest carrier among the scheduled carriers in the virtual BWP may be used as the ending RB for numbering the RBs of the virtual BWP. In some other instances, the highest RB on the active BWP on the highest carrier among the scheduled carriers in the virtual BWP may be used as the starting RB for numbering the RBs of the virtual BWP. The lowest RB on the active BWP on the lowest carrier among the scheduled carriers in the virtual BWP may be used as the ending RB for numbering the RBs of the virtual BWP.
[0068] Various methods for indicating carriers scheduled by the DCI formats described above may also be applicable here.
[0069] For example, in some embodiments, a scheduled carrier may be dynamically indicated from a plurality of carriers configured for a UE via a DCI format. For example, the scheduled carriers may be arranged consecutively in the plurality of configured carriers according to a predefined order (e.g., carrier index or frequency position of the scheduled carriers). In some instances, the DCI format may indicate both the number of consecutive scheduled carriers in the plurality of configured carriers and the first scheduled carrier in the consecutive scheduled carriers. In some instances, the DCI format may indicate the number of consecutive scheduled carriers in the plurality of configured carriers. The carrier in which the DCI format is detected is assumed to be the first scheduled carrier in the consecutive scheduled carriers. In some instances, the DCI format may indicate a carrier combination from a set of carrier combinations. The set of carrier combinations may be configured by the BS via, for example, RRC signaling. In other instances, the DCI format may indicate a bitmap, where each bit corresponds to a corresponding carrier in the plurality of configured carriers.
[0070] For example, in some embodiments, the scheduled carriers may be configured by the BS via, for example, RRC signaling. For example, the BS may configure a carrier combination from a plurality of configured carriers. Thus, the scheduled carriers are known to the UE before detecting the scheduling DCI.
[0071] From the UE's perspective, if the scheduled carriers are dynamically indicated by the DCI format, the UE cannot know the DCI payload size before decoding the DCI. To avoid additional blind DCI detection, the DCI format payload size should be predetermined based on, for example, the maximum number of schedulable carriers for a single DCI and the maximum number of RBs on an active BWP.
[0072] In the following context, N still represents the maximum number of carriers that can be scheduled by a single DCI, K1 represents the maximum number of RBs on an active BWP, and Y1 represents the maximum total number of RBs that can be scheduled by a single DCI. In some examples, N can be configured through RRC signaling or predefined in the standard, for example.
[0073] In some embodiments, Y1=K1*N. In some instances, K1 is equal to a predefined maximum number of RBs per active BWP (e.g., 275). For example, when N=4 and K1=275, Y1=4×275=1100. In some instances, K1 is equal to the maximum number of RBs per active BWP within the set of configured carriers. For example, assume that n′ carriers are configured for a UE (e.g., carrier #1 to carrier #n′), and the current active BWP for carrier #1 includes k′1 RBs, the current active BWP for carrier #2 includes k′2 RBs, the current active BWP for carrier #3 includes k′3 RBs, ..., and the current active BWP for carrier #n′ includes k′ n’RBs, K1=max{k'1,k'2,k'3,...,k' n’ In some embodiments, Y1=Z'1+Z'2+…+Z' N , where Z'1, Z'2, ..., Z N is {k'1,k'2,k'3,…,k' n’} in the set of N largest values.
[0074] The UE may determine the FDRA field size based on the maximum total number of schedulable RBs (Y1) and the configured or indicated resource allocation type (eg, resource allocation type 0, resource allocation type 1, or both as specified in 3GPP specifications).
[0075] For example, when only resource allocation type 0 is configured, the FDRA field indicates a bitmap indicating the RBGs allocated to the UE. As described above, the RBG is based on a group of consecutive RBs (eg, VRBs) defined in Table 1 above. Bit is used to indicate the FDRA field.
[0076] For example, when configuring only resource allocation type 1, you might need Bit is used to indicate the FDRA field.
[0077] For example, when both resource allocation types 0 and 1 are configured, or when resource allocation is configured to be dynamically switched, then it may be necessary to A bit is used to indicate the FDRA field. A specific bit (e.g., the MSB) of the FDRA field can be used to indicate resource allocation type 0 or resource allocation type 1. For example, a bit value of "0" of the MSB indicates resource allocation type 0, and a bit value of "1" of the MSB indicates resource allocation type 1; or vice versa. For resource allocation type 0, a specific bit of the FDRA field (e.g., the MSB) can be used to indicate resource allocation type 0 or resource allocation type 1. RBG bit (e.g., N1 RBG LSBs) can provide resource allocation according to Table 1. For resource allocation type 1, the specific bits (e.g., LSBs) can provide resource allocation based on RIV-based indications.
[0078] On the UE side, the UE can blindly detect the DCI format based on the payload size determined by the maximum number of RBs that can be scheduled by the DCI format and the resource allocation type. In response to receiving the DCI format, the UE can first determine the scheduled carriers and, based on the DCI format, determine the RBs allocated on the scheduled carriers. For example, the UE can group the scheduled carriers (or the active BWPs of the scheduled carriers) according to a predefined order (e.g., by carrier index or carrier frequency position), number all RBs in the virtual BWP from the start RB to the end RB, and determine the allocated RBs based on the FDRA field and the resource allocation type. Once the allocated RBs are determined, the UE knows the distribution of the allocated RBs on each scheduled carrier and can receive the PDSCH or transmit the PUSCH on the scheduled carriers.
[0079] In the case where the scheduled carrier is configured by the BS as, for example, a carrier combination from multiple configured carriers, the scheduled carrier and the active BWP of the scheduled carrier are known to the UE before detecting the scheduling DCI format. The UE can determine the payload size of the DCI format because the number of bits in the FDRA field can be predetermined based on the total number of RBs on the active BWPs of the scheduled carrier (denoted as Y1') and the configured or indicated resource allocation type. For example, the UE can sum the number of RBs on each active BWP of the scheduled carrier to determine the value of Y1' and determine the number of bits in the FDRA field of the DCI format based on Y1' and the resource allocation type according to a similar process as described above.
[0080] For example, when configuring only resource allocation type 0, you might need bit is used to indicate the FDRA field. For example, when only resource allocation type 1 is configured, it may be necessary to The FDRA field may be used to indicate the FDRA field. For example, when both resource allocation types 0 and 1 are configured or when resource allocation is configured for dynamic switching, the FDRA field may be used to indicate the FDRA field. Bit is used to indicate the FDRA field.
[0081] The above embodiments may be applicable to scheduled carriers having the same or different SCS values. The above embodiments may be applicable to scenarios where all scheduled carriers are configured with the same resource allocation type.
[0082] In some embodiments of the present disclosure, when a single DCI format can schedule multiple carriers for downlink or uplink transmission, an FDRA pattern list may be configured via RRC signaling or predefined, for example, in a standard. Each entry in the list may include: a carrier index (also known as a "serving cell index"), a BWP indicator, and an FDRA indicator, or a specific combination of one or both of the carrier index, the BWP indicator, and the FDRA indicator. The indicator in the DCI format that multiple carriers are scheduled may indicate an entry from the list. In response to receiving the DCI format, the UE may be aware of the scheduled carriers, the BWP indicator, and the allocated RBs on the corresponding scheduled carriers.
[0083] In some embodiments, each entry of the list may indicate at least one scheduled carrier, at least one BWP associated with the at least one scheduled carrier, and at least one FDRA indicator associated with the at least one scheduled carrier. For convenience, such an FDRA pattern list is hereinafter referred to as "Pattern List A." In some examples, the number of scheduled carriers in an entry may be equal to the number of BWP indicators and the number of FDRA indicators in the corresponding entry. An example of Pattern List A is shown in Table 2a below.
[0084] Table 2a: List of FDRA modes
[0085]
[0086] In some embodiments, each entry of the list may indicate at least one combination of a scheduled carrier, a BWP associated with the scheduled carrier, and an FDRA indicator associated with the scheduled carrier. For convenience, such an FDRA pattern list is hereinafter referred to as "Pattern List B." An example of Pattern List B is shown in Table 2b below.
[0087] Table 2b: List of FDRA modes
[0088]
[0089]
[0090] In some embodiments, each entry in the list may indicate at least one scheduled carrier and at least one BWP associated with the at least one scheduled carrier. For convenience, this FDRA pattern list is referred to below as "Pattern List C." An example of Pattern List C is shown in Table 2c below. In some embodiments, each entry in the list may indicate at least one combination of a scheduled carrier and a BWP associated with the scheduled carrier. For convenience, this FDRA pattern list is referred to below as "Pattern List D." An example of Pattern List D is shown in Table 2d below. The FDRA for each scheduled carrier may be separately indicated by the corresponding FDRA field in the scheduling DCI.
[0091] Table 2c: List of FDRA modes
[0092]
[0093] Table 2d: List of FDRA modes
[0094]
[0095]
[0096] In some embodiments, each entry in the list may indicate at least one FDRA indicator associated with at least one scheduled carrier. For convenience, such an FDRA pattern list is referred to below as "Pattern List E." An example of Pattern List E is shown in Table 2e below. The carrier index and BWP indicator for each scheduled carrier may be indicated by fields in the scheduling DCI format. For example, the DCI format may include separate fields for indicating the carrier index and BWP indicator for the scheduled carrier.
[0097] Table 2e: List of FDRA modes
[0098]
[0099] In some embodiments, a specific scheduled carrier (e.g., the first one in Tables 2a to 2d, e.g., "first scheduled carrier") in an entry of an FDRA pattern list (e.g., Pattern Lists A to D) may be the carrier on which the scheduling DCI is detected. The carrier index of this scheduled carrier (e.g., "first scheduled carrier" in Tables 2a to 2d) in the above FDRA pattern list (e.g., Pattern Lists A to D) may be omitted. For example, Table 2c may be modified to the following Table 2c'. In some embodiments, in Table 2c', when the active BWP on which the scheduling DCI is received is assumed to be the BWP on the first scheduled carrier, the BWP indicator on the first scheduled carrier may also be omitted.
[0100] Table 2c': List of FDRA modes
[0101]
[0102] In some examples, each entry in the above-mentioned FDRA pattern lists (e.g., pattern lists A to E) may not include more scheduled carriers than the maximum number of carriers that can be scheduled by a single DCI, which can be configured through RRC signaling or predefined in the standard, for example. For example, assuming that N represents the maximum number of carriers that can be scheduled by a single DCI, the number of FDRA indicators in each entry of pattern list E (e.g., Table 2e) may not be greater than N.
[0103] In some examples, the maximum number of carriers that can be scheduled by a single DCI may be implicitly indicated by the number of scheduled carriers in each entry of the FDRA pattern list.In some examples, the maximum number of carriers that can be scheduled by a single DCI may not necessarily be configured by separate RRC signaling.
[0104] In the above-described embodiment utilizing an FDRA pattern list, the schedule DCI payload size may be determined based on the maximum number of bits required for each entry among all entries in the list. Once the list is configured for the UE, or when the list is predefined, the UE may determine the required number of bits for each entry and assume a DCI payload size based on the maximum number of bits required for each entry. In some embodiments, the schedule DCI payload size may be determined based on the number of entries in the corresponding FDRA pattern list.
[0105] For example, using Pattern List A and Pattern List B as examples, the payload size of a DCI format may be determined based on the number of entries in the corresponding FDRA pattern list. For example, assuming 16 entries are configured in Pattern List A or B, where each entry includes, for example, up to 8 combinations for a maximum of 8 carriers schedulable by the DCI format, the DCI format may include an indicator of at least 4 bits (log216) to indicate the entry from the list. Since each entry includes FDRA information, the FDRA field does not exist in the DCI format.
[0106] Taking Pattern List C and Pattern List D as examples, in some embodiments, the payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list, the maximum number of scheduled carriers indicated in the entries, and the maximum number of RBs for each carrier among the multiple carriers configured for the UE (e.g., the carrier among the multiple configured carriers with the maximum number of RBs).
[0107] In some embodiments, the payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list, the maximum number of scheduled carriers indicated in the entries, and the maximum number of RBs for each carrier among the carriers indicated in the pattern list (e.g., the carrier with the maximum number of RBs indicated in the entry of the pattern list).
[0108] In some embodiments, the payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list, the maximum number of scheduled carriers indicated in the entry, and the maximum number of RBs per BWP among the carriers indicated in the pattern list as indicated by the BWP indicator (e.g., for each "carrier and BWP" combination in each entry of the pattern list, the BWP is determined based on the corresponding "carrier and BWP" combination with the maximum number of RBs).
[0109] For example, for each scheduled carrier, the DCI format may include a corresponding FDRA field. The size of the FDRA field may be determined based on the maximum number of RBs per carrier among the multiple carriers configured for the UE, or the maximum number of RBs per carrier among the carriers indicated in the pattern list, or the maximum number of RBs per BWP among the carriers indicated in the pattern list as indicated by the BWP indicator. The maximum size of all FDRA fields may be based on the maximum number of scheduled carriers indicated in the entry (e.g., the maximum number of "carrier and BWP" combinations in pattern list D) and the determined size of the FDRA field (e.g., by multiplying the two values). The payload size of the DCI format may be determined based on the maximum size of all FDRA fields and the number of entries in the FDRA pattern list (e.g., for an indicator indicating an entry from the list).
[0110] Taking pattern list E as an example, the payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list and the maximum number of FDRA indicators indicated in the entry. For example, for each scheduled carrier, the DCI format may include a corresponding carrier index field (e.g., p bits) and a corresponding BWP indicator field (e.g., q bits). Assuming 16 entries are configured in pattern list E, where each entry includes, for example, up to 8 FDRA indicators for a maximum of 8 carriers that can be scheduled by the DCI format, the payload size of the DCI format may be determined based on: (p+q)×8 bits (e.g., for the carrier index field and the BWP indicator field) and 4 bits (log216) (e.g., for the indicator indicating the entry from the list).
[0111] The above-described embodiments utilizing the FDRA pattern list may be applicable to scheduled carriers having the same or different SCS values. The above-described embodiments utilizing the FDRA pattern list may be applicable to scenarios where different scheduled carriers are configured with the same or different resource allocation types.
[0112] In some embodiments of the present disclosure, when a single DCI format can schedule multiple carriers for downlink or uplink transmission, one or more indicators (e.g., one or more FDRA fields) in the DCI format can indicate the RBs allocated on the scheduled carriers. For example, as will be described below, the number of FDRA fields may depend on the number of frequency bands or frequency ranges of the multiple configured carriers of the UE.
[0113] In some embodiments, the carriers scheduled by the DCI format may be dynamically indicated from a plurality of configured carriers of the UE via the DCI format. For example, the scheduled carriers may be arranged consecutively in the plurality of configured carriers according to a predefined order (e.g., the carrier index or frequency position of the scheduled carriers). In some instances, the DCI format may jointly indicate the number of consecutive scheduled carriers in the plurality of configured carriers and the first scheduled carrier in the consecutive scheduled carriers. In some instances, the DCI format may indicate the number of consecutive scheduled carriers in the plurality of configured carriers. The carrier in which the DCI format is detected is assumed to be the first scheduled carrier. In some instances, the DCI format may indicate a carrier combination from a set of carrier combinations. The set of carrier combinations may be configured by the BS via, for example, RRC signaling. In some instances, the DCI format may indicate a bitmap, wherein each bit corresponds to a corresponding carrier in the plurality of configured carriers.
[0114] In some embodiments, the scheduled carriers may be configured by the BS via, for example, RRC signaling. For example, the BS may configure a carrier combination from a plurality of configured carriers. Thus, the scheduled carriers are known to the UE before detecting the scheduling DCI.
[0115] In some embodiments, the number of FDRA fields in the DCI format may depend on the number of frequency bands of the configured carriers for the UE. For configured carriers on the same frequency band, such as intra-band carrier aggregation, the same FDRA field is shared among the carriers on the frequency band. That is, the same FDRA field applies to scheduled carriers within the same frequency band. The same resource allocation type is configured for carriers in the same frequency band. For configured carriers on different frequency bands, such as inter-band carrier aggregation, multiple FDRA fields are required, each corresponding to a corresponding frequency band. Separate resource allocation types can be configured for carriers in different frequency bands.
[0116] Based on the configured carriers signaled via RRC, the UE may determine the number of frequency bands used for the configured carriers and determine the number of FDRA fields in the scheduling DCI format based on the number of frequency bands used for the configured carriers. For each FDRA field in the DCI format, the required number of bits may be set to the maximum required number of bits for each carrier among multiple carriers in the same frequency band.
[0117] For example, where the scheduled carrier is dynamically indicated by a DCI format, the payload size of the DCI format and the size of the FDRA field in the DCI format may depend on the maximum number of RBs per carrier among multiple configured carriers in the same frequency band.
[0118] For example, when the scheduled carrier is configured by the BS, the scheduled carrier is known to the UE before detecting the scheduling DCI format. The payload size of the DCI format and the size of the FDRA field in the DCI format may depend on the maximum number of RBs per carrier among the scheduled carriers in the same frequency band.
[0119] At the UE side, in response to receiving multiple configured carriers, the UE can determine the number of frequency bands of these configured carriers and, therefore, the number of FDRA fields in the DCI format. The UE can then determine the required number of bits of the FDRA field corresponding to each frequency band and determine the payload size of the scheduling DCI based on the number of frequency bands and the maximum number of bits of the FDRA field corresponding to each frequency band.
[0120] For example, reference Figure 4 , a UE may be configured with multiple CCs (e.g. Figure 4 CCs 431 to 434 in a frequency band 441 may have the same or different SCS values. CCs 431 and 432 are within frequency band 441, and CCs 433 and 434 are within frequency band 442. CCs 431 and 432 in the same frequency band may be configured with the same resource allocation type, and CCs 433 and 434 in the same frequency band may be configured with the same resource allocation type. The resource allocation type of CCs 431 and 432 may be different from or the same as the resource allocation type of CCs 433 and 434.
[0121] The UE may determine the presence of two FDRA fields included in the DCI format, where each FDRA field corresponds to a frequency band. Assume that FDRA field #1 and FDRA field #2 correspond to frequency band 441 and frequency band 442, respectively. Further assume that the number of RBs on CC 432 is greater than the number of RBs on CC 431, and that the number of RBs on CC 433 is greater than the number of RBs on CC 434.
[0122] In some examples, the carriers scheduled by the DCI format may be dynamically indicated by the DCI format. For example, the DCI format may schedule transmissions on CCs 431, 433, and 434. The UE may determine the payload size of the DCI format and the size of the FDRA field (e.g., FDRA field #1 or FDRA field #2) based on the maximum number of RBs for each carrier among multiple configured carriers in the same frequency band. For example, since the number of RBs on CC 432 is greater than the number of RBs on CC 431, and the number of RBs on CC 433 is greater than the number of RBs on CC 434, the UE may determine the size of FDRA field #1 based on the number of RBs on CC 432 and the size of FDRA field #2 based on the number of RBs on CC 433.
[0123] For example, the size of the FDRA field #1 may be determined based on the number of RBs on CC 432 (denoted as "Y2") and the resource allocation types of CC 431 and CC 432. For example, when only resource allocation type 0 is configured, the size of the FDRA field #1 may be determined by For example, when only resource allocation type 1 is configured, the size of FDRA field #1 can be determined by When both resource allocation types 0 and 1 are configured, or when resource allocation is configured for dynamic switching, the size of the FDRA field #1 may be determined by Sure.
[0124] In some examples, the scheduled carriers may be configured by the BS. The UE may determine the payload size of the DCI format and the size of the FDRA field (e.g., FDRA field #1 or FDRA field #2) based on the maximum number of RBs for each carrier among the scheduled carriers in the same frequency band. For example, assuming that the BS configures transmissions on CCs 431, 433, and 434 to be scheduled by a DCI format, the UE may determine the size of FDRA field #1 based on the number of RBs on CC 431 and the size of FDRA field #2 based on the number of RBs on CC 433. For example, the method for determining the size of the FDRA field described above may also be applied here.
[0125] In some embodiments, the number of FDRA fields in the DCI format may depend on the number of frequency ranges of the configured carriers of the UE. The frequency ranges may include FR1 and FR2 or FR1, FR2-1, and FR2-2. FR1 may include a frequency range of 410 MHz to 7125 MHz. FR2 may include a frequency range of 24,250 MHz to 52,600 MHz. FR2-1 may include a frequency range of 24,250 MHz to 52,600 MHz. FR2-2 may include a frequency range of 52,600 MHz to 71,000 MHz. For configured carriers in the same frequency range, the same FDRA field is shared among carriers in the frequency range. That is, the same FDRA applies to scheduled carriers in the same frequency range. The same resource allocation type is configured for carriers in the same frequency range. For configured carriers in different frequency ranges, multiple FDRA fields are required, each corresponding to a corresponding frequency range. Separate resource allocation types may be configured for carriers in different frequency ranges.
[0126] Based on the configured carriers signaled via RRC, the UE may determine the number of frequency ranges for the configured carriers and determine the number of FDRA fields in the scheduling DCI format based on the number of frequency ranges for the configured carriers. For each FDRA field in the DCI format, the required number of bits may be set to the maximum required number of bits for each carrier among multiple carriers in the same frequency range.
[0127] For example, where the scheduled carrier is dynamically indicated by a DCI format, the payload size of the DCI format and the size of the FDRA field in the DCI format may depend on the maximum number of RBs per carrier among multiple configured carriers in the same frequency range.
[0128] For example, when the scheduled carrier is configured by the BS, the scheduled carrier is known to the UE before detecting the scheduling DCI format. The payload size of the DCI format and the size of the FDRA field in the DCI format may depend on the maximum number of RBs per carrier among the scheduled carriers in the same frequency range.
[0129] At the UE side, in response to receiving multiple configured carriers, the UE can determine the number of frequency ranges of these configured carriers and, therefore, the number of FDRA fields in the DCI format. The UE can then determine the required number of bits of the FDRA field corresponding to each frequency range and determine the payload size of the scheduling DCI based on the number of frequency ranges and the maximum number of bits of the FDRA field corresponding to each frequency range.
[0130] For example, reference Figure 5 , a UE may be configured with multiple CCs (e.g. Figure 5 CCs 531 to 534 in the same frequency region are configured. CCs 531 and 532 are within frequency range 551, and CCs 533 and 534 are within frequency range 552. CCs 531 and 532 within the same frequency range may be configured with the same resource allocation type, and CCs 533 and 534 within the same frequency region may be configured with the same resource allocation type. The resource allocation type of CCs 531 and 532 may be different from or the same as the resource allocation type of CCs 533 and 534.
[0131] The UE may determine the presence of two FDRA fields included in the DCI format, where each FDRA field corresponds to a frequency range. It is assumed that FDRA field #A1 and FDRA field #A2 correspond to frequency range 551 and frequency range 552, respectively. It is assumed that the number of RBs on CC 532 is greater than the number of RBs on CC 531, and the number of RBs on CC 533 is greater than the number of RBs on CC 534.
[0132] In some examples, the carriers scheduled by the DCI format may be dynamically indicated by the DCI format. For example, the DCI format may schedule transmissions on CCs 531 and 533. The UE may determine the payload size of the DCI format and the size of the FDRA field (e.g., FDRA field #A1 or FDRA field #A2) based on the maximum number of RBs for each carrier among multiple configured carriers in the same frequency range. For example, since the number of RBs on CC 532 is greater than the number of RBs on CC 531, and the number of RBs on CC 533 is greater than the number of RBs on CC 534, the UE may determine the size of the FDRA field #A1 based on the number of RBs on CC 532, and determine the size of the FDRA field #A2 based on the number of RBs on CC 533. For example, the method for determining the size of the FDRA field described above may also be applied here.
[0133] In some examples, scheduled carriers may be configured by the BS. The UE may determine the payload size of the DCI format and the size of the FDRA field (e.g., FDRA field #A1 or FDRA field #A2) based on the maximum number of RBs per carrier among the scheduled carriers in the same frequency range. For example, assuming that the BS configures transmissions on CCs 531, 533, and 534 to be scheduled by a DCI format, the UE may determine the size of the FDRA field #A1 based on the number of RBs on CC 531 and the size of the FDRA field #A2 based on the number of RBs on CC 533. For example, the method described above for determining the size of the FDRA field may also be applied here.
[0134] Figure 6Flowchart illustrating an exemplary process 600 for wireless communication according to some embodiments of the present disclosure. Figure 6 In some instances, the process may be performed by a UE (e.g., Figure 1 UE 101 in executes.
[0135] refer to Figure 6 In operation 611, the UE may determine a payload size of a DCI format, wherein the DCI format schedules a first plurality of carriers among a second plurality of carriers, wherein the second plurality of carriers is configured by the BS.
[0136] In operation 613, the UE may receive a DCI format from the BS according to the determined payload size, wherein the first plurality of carriers is indicated by a first indicator of the DCI format or configured by the BS. In operation 615, the UE may determine RBs allocated on the first plurality of carriers based on the DCI format.
[0137] In operation 617 , the UE may receive downlink transmission on the allocated RBs if the DCI format schedules downlink transmission, or transmit uplink transmission on the allocated RBs if the DCI format schedules uplink transmission.
[0138] In some embodiments, the first indicator may indicate: a first scheduled carrier in a first plurality of carriers and the number of the first plurality of carriers, wherein the first plurality of carriers are consecutively arranged in a second plurality of carriers according to a predefined order; the number of the first plurality of carriers, wherein the first plurality of carriers are consecutively arranged in the second plurality of carriers according to a predefined order, and the DCI format is received on the first scheduled carrier in the first plurality of carriers; a carrier combination from a set of carrier combinations; or a bitmap, wherein each bit corresponds to a corresponding carrier in the second plurality of carriers.
[0139] In some embodiments, determining the allocated RBs on each of the first plurality of carriers may include: combining the first plurality of carriers into a virtual carrier according to a predefined order; and determining the allocated RBs on the virtual carrier according to the second indicator in the DCI format and the resource allocation type associated with the first plurality of carriers.
[0140] In some embodiments, determining the allocated RBs on each of the first plurality of carriers may include: combining active bandwidth parts (BWPs) of the first plurality of carriers into a virtual BWP according to a predefined order; and determining the allocated RBs on the virtual BWP according to a second indicator in the DCI format and a resource allocation type associated with the first plurality of carriers.
[0141] In some embodiments, the predefined order may be based on carrier indices or frequency positions of the first plurality of carriers.
[0142] In some embodiments, the field size of the second indicator may depend on the resource allocation type associated with the first plurality of carriers and one of the maximum total number of RBs that can be scheduled by the DCI format, the total number of RBs on the first plurality of carriers, or the total number of RBs on the active bandwidth part (BWP) of the first plurality of carriers.
[0143] In some embodiments, where the first plurality of carriers is indicated by the first indicator, the payload size of the DCI format may be determined based on a maximum total number of RBs that may be scheduled by the DCI format.
[0144] In some embodiments, the maximum total number of RBs may be determined based on one of: N and a predefined maximum number of RBs per carrier (e.g., 275 RBs); N and a maximum number of RBs per carrier in a second plurality of carriers; or the total number of RBs for N carriers in the second plurality of carriers, where N carriers include the maximum number of RBs in the second plurality of carriers. N represents the maximum number of carriers that can be scheduled by the DCI format.
[0145] In some embodiments, the maximum total number of RBs may be determined based on one of: N and a predefined maximum number of RBs per carrier; N and a maximum number of RBs per active bandwidth part (BWP) for each carrier in the second plurality of carriers; or the total number of RBs in the active BWPs of N carriers in the second plurality of carriers, where the active BWPs of N carriers include the maximum number of RBs in the active BWPs of the second plurality of carriers. N represents the maximum number of carriers that can be scheduled by the DCI format.
[0146] In some embodiments, where the first plurality of carriers is configured by the BS, the payload size of the DCI format may be determined based on the total number of RBs on the first plurality of carriers or the total number of RBs on an active bandwidth part (BWP) of the first plurality of carriers.
[0147] In some embodiments, the UE may receive a frequency domain resource allocation (FDRA) pattern list from the BS.
[0148] In some examples, the FDRA pattern list may include at least one entry, each of which may indicate one of: at least one scheduled carrier, at least one bandwidth part (BWP) associated with the at least one scheduled carrier, and at least one FDRA indicator associated with the at least one scheduled carrier; and at least one combination of a scheduled carrier, a BWP associated with the scheduled carrier, and an FDRA indicator associated with the scheduled carrier. The first indicator may indicate an entry from the FDRA pattern list. The payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list.
[0149] In some examples, the FDRA pattern list may include at least one entry, each of which may indicate one of: at least one scheduled carrier and at least one bandwidth part (BWP) associated with the at least one scheduled carrier; and at least one combination of a scheduled carrier and a BWP associated with the scheduled carrier. The first indicator may indicate a first entry of the at least one entry. The DCI format may further include an FDRA indicator corresponding to each scheduled carrier indicated by the first entry. The payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list, the maximum number of scheduled carriers indicated in the entry, and the maximum number of RBs per carrier among the second plurality of carriers.
[0150] In some examples, the FDRA pattern list may include at least one entry, each of which may indicate at least one FDRA indicator associated with at least one scheduled carrier. The DCI format may include a second indicator indicating a first entry of the at least one entry. The first entry may indicate a set of FDRA indicators associated with a first plurality of carriers indicated by the first indicator. The DCI format may further include a third indicator indicating a set of bandwidth parts (BWPs) associated with the first plurality of carriers. The payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list and the maximum number of FDRA indicators indicated in the entries.
[0151] In some embodiments, the DCI format may include at least one second indicator for frequency domain resource allocation. The number of the at least one second indicator may depend on the number of frequency bands or frequency ranges of the second plurality of carriers. In some examples, the payload size of the DCI format and the field size of the second indicator may depend on the maximum number of RBs per carrier among carriers in the second plurality of carriers in the same frequency band or frequency range, or the maximum number of RBs per carrier among carriers in the first plurality of carriers in the same frequency band or frequency range. In some examples, the same second indicator may apply to carriers in the first plurality of carriers in the same frequency band or frequency range.
[0152] Those skilled in the art will appreciate that the sequence of operations in exemplary process 600 may be changed, and some of the operations in exemplary process 600 may be eliminated or modified, without departing from the spirit and scope of the present disclosure.
[0153] Figure 7 Flowchart illustrating an exemplary process 700 for wireless communication according to some embodiments of the present disclosure. Figure 7 In some examples, the process may be performed by a BS (e.g., Figure 1 BS102 in is executed.
[0154] refer to Figure 7 In operation 711, the BS may configure a second plurality of carriers for the UE. In operation 713, the BS may transmit to the UE a DCI format for scheduling a plurality of RBs on a first plurality of carriers among the second plurality of carriers for transmission, wherein the first plurality of carriers is indicated by a first indicator in the DCI format or configured by the BS to the UE.
[0155] In operation 715, the BS may transmit downlink transmission on a plurality of RBs in case the DCI format schedules downlink transmission, or receive uplink transmission on a plurality of RBs in case the DCI format schedules uplink transmission.
[0156] In some embodiments, the first indicator may indicate: a specific (first) carrier in a first plurality of carriers and the number of the first plurality of carriers, wherein the first plurality of carriers are consecutively arranged in a second plurality of carriers according to a predefined order; the number of the first plurality of carriers, wherein the first plurality of carriers are consecutively arranged in the second plurality of carriers according to a predefined order, and the DCI format is received on the specific (first) carrier in the first plurality of carriers; a carrier combination from a set of carrier combinations; or a bitmap, wherein each bit corresponds to a corresponding carrier in the second plurality of carriers.
[0157] In some embodiments, the BS may further: combine the first plurality of carriers into a virtual carrier according to a predefined order; and determine a plurality of RBs on the virtual carrier according to the second indicator in the DCI format and a resource allocation type associated with the first plurality of carriers.
[0158] In some embodiments, the BS may further: combine active bandwidth parts (BWPs) of the first plurality of carriers into a virtual BWP according to a predefined order; and determine a number of RBs on the virtual BWP according to a second indicator in the DCI format and a resource allocation type associated with the first plurality of carriers.
[0159] In some embodiments, the predefined order may be based on carrier indices or frequency positions of the first plurality of carriers.
[0160] In some embodiments, the field size of the second indicator may depend on the resource allocation type associated with the first plurality of carriers and one of the maximum total number of RBs that can be scheduled by the DCI format, the total number of RBs on the first plurality of carriers, or the total number of RBs on the active bandwidth part (BWP) of the first plurality of carriers.
[0161] In some embodiments, where the first plurality of carriers is indicated by the first indicator, the payload size of the DCI format may be determined based on a maximum total number of RBs that may be scheduled by the DCI format.
[0162] In some embodiments, the maximum total number of RBs may be determined based on one of: N and a predefined maximum number of RBs per carrier (e.g., 275 RBs); N and a maximum number of RBs per carrier in a second plurality of carriers; or the total number of RBs for N carriers in the second plurality of carriers, where N carriers includes the maximum number of RBs in the second plurality of carriers. N is the maximum number of carriers that can be scheduled by the DCI format.
[0163] In some embodiments, the maximum total number of RBs may be determined based on one of: N and a predefined maximum number of RBs per carrier; N and a maximum number of RBs per active bandwidth part (BWP) for each carrier in the second plurality of carriers; or the total number of RBs in the active BWPs of N carriers in the second plurality of carriers, where the active BWPs of N carriers include the maximum number of RBs in the active BWPs of the second plurality of carriers. N is the maximum number of carriers that can be scheduled by the DCI format.
[0164] In some embodiments, where the first plurality of carriers is configured by the BS, the payload size of the DCI format is determined based on the total number of RBs on the first plurality of carriers or the total number of RBs on an active bandwidth part (BWP) of the first plurality of carriers.
[0165] In some embodiments, the BS may transmit a radio domain resource allocation (FDRA) pattern list to the UE.
[0166] In some examples, the FDRA pattern list may include at least one entry, each of which may indicate one of: at least one scheduled carrier, at least one bandwidth part (BWP) associated with the at least one scheduled carrier, and at least one FDRA indicator associated with the at least one scheduled carrier; and at least one combination of a scheduled carrier, a BWP associated with the scheduled carrier, and an FDRA indicator associated with the scheduled carrier; and wherein the first indicator may indicate an entry from the FDRA pattern list. The payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list.
[0167] In some examples, the FDRA pattern list may include at least one entry, each of which may indicate one of: at least one scheduled carrier and at least one bandwidth part (BWP) associated with the at least one scheduled carrier; and at least one combination of a scheduled carrier and a BWP associated with the scheduled carrier. The first indicator may indicate a first entry of the at least one entry. The DCI format may further include an FDRA indicator corresponding to each scheduled carrier indicated by the first entry. The payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list, the maximum number of scheduled carriers indicated in the entry, and the maximum number of RBs per carrier among the second plurality of carriers.
[0168] In some examples, the FDRA pattern list may include at least one entry, each of which may indicate at least one FDRA indicator associated with at least one scheduled carrier. The DCI format may include a second indicator indicating a first entry of the at least one entry. The first entry may indicate a set of FDRA indicators associated with a first plurality of carriers indicated by the first indicator. The DCI format may further include a third indicator indicating a set of bandwidth parts (BWPs) associated with the first plurality of carriers. The payload size of the DCI format may be determined based on the number of entries in the FDRA pattern list and the maximum number of FDRA indicators indicated in the entries.
[0169] In some embodiments, the DCI format may include at least one second indicator for frequency domain resource allocation. The number of the at least one second indicator may depend on the number of frequency bands or frequency ranges of the second plurality of carriers. In some examples, the payload size of the DCI format and the field size of the second indicator may depend on the maximum number of RBs per carrier among carriers in the second plurality of carriers in the same frequency band or frequency range, or the maximum number of RBs per carrier among carriers in the first plurality of carriers in the same frequency band or frequency range. In some examples, the same second indicator may apply to carriers in the first plurality of carriers in the same frequency band or frequency range.
[0170] Those skilled in the art will appreciate that the sequence of operations in exemplary process 700 may be changed, and some of the operations in exemplary process 700 may be eliminated or modified, without departing from the spirit and scope of the present disclosure.
[0171] Figure 8 8 is a block diagram illustrating an exemplary device 800 according to some embodiments of the present disclosure. Figure 8 , apparatus 800 may include at least one processor 806 and at least one transceiver 802 coupled to the processor 806. Apparatus 800 may be a UE or a BS.
[0172] Although elements such as at least one transceiver 802 and processor 806 are described in the singular in this figure, the plural form is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present application, the transceiver 802 can be divided into two devices, such as a receive circuit system and a transmit circuit system. In some embodiments of the present application, the apparatus 800 can further include an input device, a memory, and / or other components.
[0173] In some embodiments of the present application, the device 800 may be a UE. The transceiver 802 and the processor 806 may interact with each other to perform Figures 1 to 7 In some embodiments of the present application, the device 800 may be a BS. The transceiver 802 and the processor 806 may interact with each other to perform Figures 1 to 7 The operation of BS is described in .
[0174] In some embodiments of the present application, the apparatus 800 may further include at least one non-transitory computer-readable medium.
[0175] For example, in some embodiments of the present disclosure, a non-transitory computer-readable medium may have computer-executable instructions stored thereon to cause the processor 806 to implement the method described above with respect to the UE. For example, when executed, the computer-executable instructions cause the processor 806 to interact with the transceiver 802 to perform Figures 1 to 7 The operations of the UE are described in .
[0176] In some embodiments of the present disclosure, a non-transitory computer-readable medium may have computer-executable instructions stored thereon to cause the processor 806 to implement the method described above with respect to the BS. For example, when executed, the computer-executable instructions cause the processor 806 to interact with the transceiver 802 to perform Figures 1 to 7 The operation of BS is described in .
[0177] Those skilled in the art will appreciate that the operations or steps of the methods described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Furthermore, in some aspects, the operations or steps of the methods may reside as one or any combination or set of codes and / or instructions on a non-transitory computer-readable medium that may be incorporated into a computer program product.
[0178] Although the present disclosure has been described using its specific embodiments, it is apparent that many alternatives, modifications, and variations may be apparent to those skilled in the art. For example, the various components of the embodiments may be interchanged, added, or replaced in other embodiments. In addition, not all elements of each figure are necessary for the operation of the disclosed embodiments. For example, it will enable those skilled in the art of the disclosed embodiments to make and use the teachings of the present disclosure by simply adopting elements of independent technical solutions. Therefore, the embodiments of the present disclosure as described herein are intended to be illustrative, not restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.
[0179] In this document, the term "includes, including" or any other variant thereof is intended to encompass non-exclusive inclusion, so that the process, method, article or equipment comprising a series of elements not only comprises those elements, but may also comprise other elements that are not explicitly listed or inherent to such processes, methods, articles or equipment. Without further constraints, an element beginning with "a, an" or the like does not exclude the presence of additional identical elements in the process, method, article or equipment comprising the element. In addition, the term "another" is defined as at least a second or more. As used herein, the term "having" and the like are defined as "comprising". For example, the expression of "A and / or B" or "at least one of A and B" may include any and all combinations of the words listed together with the expression. For example, the expression "A and / or B" or "at least one of A and B" may include A, B or both A and B. The phrases "first", "second" or the like are only used to clearly illustrate the embodiments of the present application, and are not used to limit the substantive content of the present application.
Claims
1. A user equipment UE, wherein include: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: determining a payload size of a downlink control information DCI format, wherein the DCI format schedules a first plurality of carriers of a second plurality of carriers, wherein the second plurality of carriers is configured by a base station BS; receiving the DCI format from the BS according to the determined payload size, wherein the first plurality of carriers is indicated by a first indicator of the DCI format or configured by the BS; Determine resource blocks (RBs) allocated on the first plurality of carriers based on the DCI format; and In case the DCI format schedules a downlink transmission, the downlink transmission is received on the allocated RB, or in case the DCI format schedules an uplink transmission, the uplink transmission is transmitted on the allocated RB.
2. The UE according to claim 1, wherein the first indicator indicates: a first carrier in the first plurality of carriers and a number of the first plurality of carriers, wherein the first plurality of carriers are consecutively arranged in the second plurality of carriers according to a predefined order; the number of the first plurality of carriers, wherein the first plurality of carriers are consecutively arranged in the second plurality of carriers according to a predefined order, and the DCI format is received on a first carrier in the first plurality of carriers; a carrier combination from a set of carrier combinations; or A bitmap wherein each bit corresponds to a corresponding carrier in the second plurality of carriers.
3. The UE of claim 1 , wherein determining the allocated RBs on each of the first plurality of carriers include: combining the first plurality of carriers into a virtual carrier according to a predefined order; and The allocated RBs on the virtual carrier are determined based on a second indicator in the DCI format and a resource allocation type associated with the first plurality of carriers.
4. The UE of claim 1 , wherein determining the allocated RBs on each of the first plurality of carriers include: combining active bandwidth parts BWP of the first plurality of carriers into a virtual BWP according to a predefined order; and The allocated RBs on the virtual BWP are determined based on a second indicator in the DCI format and a resource allocation type associated with the first plurality of carriers.
5. The UE according to claim 3 or 4, wherein the field size of the second indicator depends on the resource allocation type associated with the first plurality of carriers, and one of the maximum total number of RBs that can be scheduled by the DCI format, the total number of RBs on the first plurality of carriers, or the total number of RBs on the active bandwidth part (BWP) of the first plurality of carriers.
6. The UE of claim 1, 3 or 4, wherein, in a case where the first plurality of carriers is indicated by the first indicator, the payload size of the DCI format is determined based on a maximum total number of RBs that can be scheduled by the DCI format.
7. The UE of claim 6, wherein the maximum total number of RBs is determined based on one of: N and the predefined maximum number of RBs per carrier; N and a maximum number of RBs for each carrier of the second plurality of carriers; or the total number of RBs of N carriers of the second plurality of carriers, wherein the N carriers comprise a maximum number of RBs of the second plurality of carriers; Where N is the maximum number of carriers that can be scheduled by the DCI format.
8. The UE of claim 6, wherein the maximum total number of RBs is determined based on one of: N and the predefined maximum number of RBs per carrier; N and the maximum number of RBs per active bandwidth part BWP for each carrier of the second plurality of carriers ; or the total number of RBs of an active BWP of N carriers of the second plurality of carriers, wherein the active BWP of N carriers includes the maximum number of RBs of the active BWP of the second plurality of carriers; Wherein N is the maximum number of carriers that can be scheduled by the DCI format.
9. The UE of claim 1, wherein the processor is configured to receive a frequency domain resource allocation (FDRA) pattern list from the BS.
10. The UE of claim 9, wherein the FDRA mode list comprises at least one entry, each of which indicates one of the following: at least one scheduled carrier, at least one bandwidth part (BWP) associated with the at least one scheduled carrier, and at least one FDRA indicator associated with the at least one scheduled carrier; and at least one combination of a scheduled carrier, a BWP associated with the scheduled carrier, and a FDRA indicator associated with the scheduled carrier; and Wherein the first indicator indicates an entry from the FDRA mode list.
11. The UE of claim 9, wherein the FDRA mode list comprises at least one entry, each of which indicates one of the following: at least one scheduled carrier and at least one bandwidth part BWP associated with the at least one scheduled carrier; and At least one combination of a scheduled carrier and a BWP associated with the scheduled carrier.
12. The UE of claim 9, wherein the FDRA pattern list comprises at least one entry, each of which indicates at least one FDRA indicator associated with at least one scheduled carrier. 13 . The UE according to claim 1 , wherein the DCI format comprises at least one second indicator for frequency domain resource allocation, and the number of the at least one second indicator depends on the number of frequency bands or frequency ranges of the second plurality of carriers.
14. A base station BS, include: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: configuring a second plurality of carriers for user equipment UE; transmitting, to the UE, a downlink control information DCI format for scheduling a plurality of resource blocks RBs on a first plurality of carriers among the second plurality of carriers for transmission, wherein the first plurality of carriers is indicated by a first indicator in the DCI format or configured to the UE by the BS; and In case the DCI format schedules downlink transmission, downlink transmission is transmitted on the plurality of RBs, or in case the DCI format schedules uplink transmission, uplink transmission is received on the plurality of RBs.
15. A method performed by a user equipment UE, the method include: determining a payload size of a downlink control information DCI format, wherein the DCI format schedules a first plurality of carriers of a second plurality of carriers, wherein the second plurality of carriers is configured by a base station BS; receiving the DCI format from the BS according to the determined payload size, wherein the first plurality of carriers is indicated by a first indicator of the DCI format or configured by the BS; Determine resource blocks (RBs) allocated on the first plurality of carriers based on the DCI format; and In case the DCI format schedules a downlink transmission, the downlink transmission is received on the allocated RB, or in case the DCI format schedules an uplink transmission, the uplink transmission is transmitted on the allocated RB.
