WO2022082715A1 - Procédé et appareil d'attribution de ressources de domaine fréquentiel pour transmissions de liaison descendante - Google Patents

Procédé et appareil d'attribution de ressources de domaine fréquentiel pour transmissions de liaison descendante Download PDF

Info

Publication number
WO2022082715A1
WO2022082715A1 PCT/CN2020/123180 CN2020123180W WO2022082715A1 WO 2022082715 A1 WO2022082715 A1 WO 2022082715A1 CN 2020123180 W CN2020123180 W CN 2020123180W WO 2022082715 A1 WO2022082715 A1 WO 2022082715A1
Authority
WO
WIPO (PCT)
Prior art keywords
coreset
rbs
frequency region
bwp
lowest
Prior art date
Application number
PCT/CN2020/123180
Other languages
English (en)
Inventor
Haipeng Lei
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to CN202080106491.1A priority Critical patent/CN116491198A/zh
Priority to EP20958297.2A priority patent/EP4233451A1/fr
Priority to PCT/CN2020/123180 priority patent/WO2022082715A1/fr
Priority to US18/249,690 priority patent/US20230388092A1/en
Publication of WO2022082715A1 publication Critical patent/WO2022082715A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments of the present disclosure generally relate to wireless communication technology, and more particularly to frequency domain resource allocation for downlink (DL) transmissions.
  • DL downlink
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, and so on.
  • 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 may include fourth generation (4G) systems such as long term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may also be referred to as new radio (NR) systems.
  • 4G systems such as long term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may also be referred to as new radio (NR) systems.
  • a user equipment may monitor a physical downlink control channel (PDCCH) , which may carry downlink control information (DCI) .
  • the DCI may schedule uplink channels, such as a physical uplink shared channel (PUSCH) , or downlink channels, such as a physical downlink shared channel (PDSCH) .
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • the UE may transmit hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback (e.g., included in a HARQ-ACK codebook) corresponding to the PDSCH through a PUSCH or a physical uplink control channel (PUCCH) .
  • HARQ-ACK hybrid automatic repeat request acknowledgement
  • Some embodiments of the present disclosure provide a method for wireless communication performed by a user equipment (UE) .
  • the method may include: receiving a physical downlink control channel (PDCCH) within a control resource set (CORESET) , wherein the PDCCH carries a downlink control information (DCI) format for scheduling a physical downlink shared channel (PDSCH) ; and receiving the PDSCH on a plurality of resource blocks (RBs) based on the DCI format, wherein the plurality of RBs are within a frequency region.
  • PDCCH physical downlink control channel
  • CORESET control resource set
  • DCI downlink control information
  • RBs resource blocks
  • the method may further include receiving a radio resource control (RRC) signaling message configuring the frequency region.
  • the frequency region may be shared between the UE and another UE.
  • the RRC signaling message may indicate a starting RB and a number of contiguous RBs of the frequency region.
  • the RRC signaling message may indicate a starting RB and an ending RB of the frequency region.
  • the CORESET may be within the frequency region.
  • the plurality of RBs may be determined in reference to the starting RB of the frequency region.
  • a payload size of the DCI format may be based on a total number of RBs contained within the frequency region.
  • the method may further include receiving a radio resource control (RRC) signaling message configuring the CORESET.
  • RRC radio resource control
  • the CORESET may be shared between the UE and another UE.
  • the frequency region may be based on the CORESET.
  • the CORESET may be within an active bandwidth part (BWP) of the UE and an active BWP of the another UE.
  • the plurality of RBs may be determined in reference to the lowest RB of the CORESET.
  • a payload size of the DCI format may be based on a total number of contiguous RBs from the lowest RB of the CORESET to the highest RB of the CORESET.
  • the CORESET may be within an initial downlink bandwidth part (BWP) of the UE and an initial downlink BWP of the another UE.
  • the plurality of RBs may be determined in reference to the RB corresponding to the lowest resource element group (REG) of the PDCCH.
  • a payload size of the DCI format may be based on the initial downlink BWP of the UE.
  • the CORESET and the frequency region may be within an initial downlink bandwidth part (BWP) of the UE and an initial downlink BWP of another UE.
  • the plurality of RBs may be determined in reference to the lowest RB of the initial downlink BWP of the UE.
  • a payload size of the DCI format may be based on the initial downlink BWP of the UE.
  • Some embodiments of the present disclosure provide a method for wireless communication performed by a base station (BS) .
  • the method may include: transmitting, to at least one user equipment (UE) , a physical downlink control channel (PDCCH) within a control resource set (CORESET) , wherein the PDCCH carries a downlink control information (DCI) format for scheduling a physical downlink shared channel (PDSCH) ; and transmitting, to the at least one UE, the PDSCH on a plurality of resource blocks (RBs) based on the DCI format, wherein the plurality of RBs are within a frequency region.
  • UE user equipment
  • CORESET control resource set
  • DCI downlink control information
  • RBs resource blocks
  • the method may further include transmitting a radio resource control (RRC) signaling message configuring the frequency region.
  • the frequency region may be shared between the at least one UE.
  • the RRC signaling message may indicate a starting RB and a number of contiguous RBs of the frequency region.
  • the RRC signaling message may indicate a starting RB and an ending RB of the frequency region.
  • the CORESET may be within the frequency region.
  • the plurality of RBs may be determined in reference to the starting RB of the frequency region.
  • a payload size of the DCI format may be based on a total number of RBs contained within the frequency region.
  • the method may further include transmitting a radio resource control (RRC) signaling message configuring the CORESET.
  • RRC radio resource control
  • the CORESET may be shared between the at least one UE.
  • the frequency region may be based on the CORESET.
  • the CORESET may be within an active bandwidth part (BWP) of the at least one UE.
  • the plurality of RBs may be in reference to the lowest RB of the CORESET.
  • a payload size of the DCI format may be based on a total number of contiguous RBs from the lowest RB of the CORESET to the highest RB of the CORESET.
  • the CORESET may be within an initial downlink bandwidth part (BWP) of the at least one UE.
  • the plurality of RBs may be determined in reference to the RB corresponding to the lowest resource element group (REG) of the PDCCH.
  • a payload size of the DCI format may be based on the initial downlink BWP of the at least one UE.
  • the CORESET and the frequency region may be within an initial downlink bandwidth part (BWP) of the at least one UE.
  • the plurality of RBs may be determined in reference to the lowest RB of the initial downlink BWP of the at least one UE.
  • a payload size of the DCI format may be based on the initial downlink BWP of the at least one UE.
  • the apparatus may include: at least one non-transitory computer-readable medium having stored thereon computer-executable instructions; 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, with the at least one processor, cause the apparatus to perform a method according to some embodiments of the present disclosure.
  • FIG. 1 illustrates a schematic diagram of a wireless communication system in accordance with some embodiments of the present disclosure
  • FIG. 2 illustrates exemplary radio resource allocation in accordance with some embodiments of the present disclosure
  • FIG. 3 illustrates exemplary radio resource allocation in accordance with some embodiments of the present disclosure
  • FIG. 4 illustrates exemplary radio resource allocation in accordance with some embodiments of the present disclosure
  • FIG. 5 illustrates exemplary radio resource allocation in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates a flow chart of an exemplary procedure of wireless communications in accordance with some embodiments of the present disclosure
  • FIG. 7 illustrates a flow chart of an exemplary procedure of wireless communications in accordance with some embodiments of the present disclosure.
  • FIG. 8 illustrates a block diagram of an exemplary apparatus in accordance with some embodiments of the present disclosure.
  • FIG. 1 illustrates a schematic diagram of a wireless communication system 100 in accordance with some embodiments of the present disclosure.
  • 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) . Although a specific number of UEs 101 and BS 102 are depicted in FIG. 1, it is contemplated that any number of UEs and BSs may be included in the wireless communication system 100.
  • the UE (s) 101 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • the UE (s) 101 may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the UE (s) 101 includes wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the UE (s) 101 may be referred to as a subscriber unit, a mobile, 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 terminology used in the art.
  • the UE (s) 101 may communicate with the BS 102 via uplink (UL) communication signals.
  • UL uplink
  • the BS 102 may be distributed over a geographic region.
  • the BS 102 may also be referred to as an access point, an access terminal, a base, a base unit, a macro cell, a Node-B, an evolved Node B (eNB) , a gNB, a Home Node-B, a relay node, or a device, or described using other terminology used in the art.
  • the BS 102 is generally a part of a radio access network that may include one or more controllers communicably coupled to one or more corresponding BSs 102.
  • the BS 102 may communicate with UE (s) 101 via downlink (DL) communication signals.
  • DL downlink
  • the wireless communication system 100 may be compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, an LTE network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • the wireless communication system 100 is compatible with the 5G NR of the 3GPP protocol.
  • BS 102 may transmit data using an orthogonal frequency division multiple (OFDM) modulation scheme on the DL and the UE (s) 101 may transmit data on the UL using a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-S-OFDM) or cyclic prefix-OFDM (CP-OFDM) scheme.
  • DFT-S-OFDM discrete Fourier transform-spread-orthogonal frequency division multiplexing
  • CP-OFDM cyclic prefix-OFDM
  • the wireless communication system 100 may implement some other open or proprietary communication protocols, for example, WiMAX, among other protocols.
  • the BS 102 and UE (s) 101 may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Further, in some embodiments of the present disclosure, the BS 102 and UE (s) 101 may communicate over licensed spectrums, whereas in some other embodiments, the BS 102 and UE (s) 101 may communicate over unlicensed spectrums.
  • the present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
  • 3GPP release 17 (R17) work item description (WID) includes a set of objectives for multicast and broadcast services (MBSs) , including, for example:
  • ⁇ Specify required changes to improve reliability of Broadcast/Multicast service, e.g., by UL feedback.
  • the level of reliability should be based on the requirements of the application/service provided.
  • ⁇ Specify required changes to enable the reception of Point to Multipoint transmissions by UEs in RRC_IDLE/RRC_INACTIVE states, with the aim of keeping maximum commonality between RRC_CONNECTED state and RRC_IDLE/RRC_INACTIVE state for the configuration of PTM (point to multipoint) reception
  • HARQ-ACK feedback from UEs corresponding to downlink multicast transmission is essential for the multicast services in order to satisfy the quality of service (QoS) requirements, e.g., reliability.
  • QoS quality of service
  • the above objectives also state that the level of reliability should be based on the requirements of the application/service which is provided by a MBS.
  • the group cell radio network temporary identifier (G-RNTI) is introduced for MBS so that a UE can differentiate a DCI scheduling a MBS PDSCH from a DCI scheduling a unicast PDSCH.
  • the cyclic redundancy check (CRC) of the DCI scheduling the MBS PDSCH as well as the scheduled MBS PDSCH is scrambled by a G-RNTI.
  • a common frequency resource for a group of UEs to receive the MBS PDSCH.
  • the following two options may be employed to define the common frequency resource:
  • An MBS specific bandwidth part may be configured by the BS as a group-common BWP.
  • the same frequency domain resource and subcarrier spacing as well as cyclic prefix are configured for a group of UEs.
  • the unicast BWP if the BWP configured for unicast transmission (hereinafter, “the unicast BWP” ) does not overlap with the MBS specific BWP, the UE has to perform BWP switching back and forth between the MBS specific BWP and the unicast BWP because only a single active BWP is allowed at a given time in NR systems. Otherwise, in the case that two (or more) active BWPs at a given time are supported, BWP switching may not be required.
  • a common frequency resource which is the intersection of the frequency resources supported by a group of UEs may be defined or configured. That is to say, within each member UE’s active BWP, a common MBS frequency resource can be defined for each member UE to receive the group-common DCI and the associated group-common PDSCH.
  • Option 2 it would be beneficial to employ Option 2 since it does not require BWP switching between the MBS specific BWP and the unicast BWP, which may be somewhat frequent.
  • Another issue is how to determine the payload size (e.g., the size of the frequency domain resource assignment (FDRA) indicator) in a DCI format from a UE’s perspective.
  • the number of bits required for a FDRA indicator is based on the bandwidth of the UE’s BWP. Since different UEs may have different BWP bandwidths, a solution for determining the same payload size of a DCI format scheduling the group-common PDSCH is required.
  • Embodiments of present disclosure provide solutions to facilitate DL transmissions, especially, MBS PDSCH transmissions.
  • the disclosed solutions can solve the above problems. More details on the embodiments of the present disclosure will be illustrated in the following text in combination with the appended drawings.
  • a common frequency region may be configured by RRC signaling (e.g., master information block (MIB) , system information block (SIB) signaling or UE-specific RRC signaling) .
  • RRC signaling e.g., master information block (MIB) , system information block (SIB) signaling or UE-specific RRC signaling
  • MIB master information block
  • SIB system information block
  • UE-specific RRC signaling e.g., UE-specific RRC signaling
  • Each member UE of the group of UEs may be in an RRC_CONNECTED state.
  • the common frequency region is within the active BWP of each member UE of the group of UEs.
  • the PDCCH carrying a group-common DCI format e.g., DCI format 1_0
  • the scheduled PDSCH also referred to as “group-common PDSCH”
  • the UE may receive the PDCCH carrying a group-common DCI format within a control resource set (CORESET) , which may be configured by RRC signaling.
  • the CORESET may be within the common frequency region.
  • the scheduled PDSCH may be carried on a plurality of RBs within the common frequency region.
  • the RRC signaling may indicate the starting RB (hereinafter, “RB start ” ) and the number of contiguous RBs (hereinafter, “L” ) in the frequency domain.
  • the group-common DCI may include a FDRA indicator indicating resource block assignment information. The number of bits of the FDRA indicator in the group-common DCI may be based on the number of contiguous RBs of the common frequency region. For the group-common PDSCH scheduled by the group-common DCI, the RB numbering may start from the configured starting RB.
  • RB start is used as the reference point (e.g., indexed as RB 0) for resource allocation indication in the frequency domain, i.e., RB start is used as the lowest RB for determining the frequency resource allocation of the group-common PDSCH.
  • the RRC signaling may indicate the starting RB (i.e., RB start ) and the ending RB (hereinafter, “RB end ” ) in the frequency domain. All the RBs between the starting RB and the ending RB are assumed as the common frequency region from a UE’s perspective.
  • the number of bits of the FDRA indicator in the group-common DCI may be based on the number of contiguous RBs (i.e., L) between RB start and RB end .
  • RB start is used as the reference point (e.g., indexed as RB 0) for resource allocation indication in the frequency domain, i.e., RB start is used as the lowest RB for determining the frequency resource allocation of the group-common PDSCH.
  • the number of bits of the FDRA indicator in the group-common DCI can be determined according to where is set to L.
  • resource allocation type 0 is applied for downlink transmissions.
  • the resource block assignment information indicated by the FDRA indicator may include a bitmap indicating the resource block groups (RBGs) that are allocated to the scheduled UEs.
  • An RBG may be a set of consecutive RBs (e.g., virtual resource blocks (VRBs) ) defined based on, for example, the following Table 1, where the bandwidth part size is set to L. It should be understood that Table 1 is only for illustrative purposes, and should not be construed as limiting the embodiments of the present disclosure.
  • VRBs virtual resource blocks
  • the number of contiguous RBs (L) in the frequency domain is 20 (i.e., between “1 –36” )
  • the number of VRBs in a RBG is 2 in the case of configuration 1 and is 4 in the case of configuration 2.
  • An RRC signaling may indicate whether configuration 1 or configuration 2 is employed.
  • the number of bits of the bitmap is equal to the total number of RBGs (N RBG ) for the common frequency region, which can be determined by
  • resource allocation type 1 is applied for downlink transmissions.
  • the resource block assignment information may indicate a resource indication value (RIV) corresponding to a starting RB and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH e.g., MBS PDSCH
  • RB start is in reference to the starting RB (RB start ) of the common frequency region, and the length may not exceed L.
  • RB start may be indexed as RB 0 for determining PDSCH resource block assignment.
  • the same subcarrier spacing and cyclic prefix of the common frequency region are also configured to the group of UEs.
  • FIG. 2 illustrates exemplary radio resource allocation 200 in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 2. It should be understood that FIG. 2 is only for illustrative purposes, and should not be construed as limiting the embodiments of the present disclosure.
  • a UE may support an active BWP 210 (e.g., an active DL BWP) .
  • the UE may be a member UE of a group of UEs.
  • Other UEs in the group of UEs support the same or different active BWPs (not shown in FIG. 2) .
  • a BS may configure a common frequency region 220 to the group of UEs via an RRC signaling message.
  • the common frequency region 220 may be within active BWP 210 of UE#1, as well as active BWPs of other UEs of the group of UEs.
  • the RRC signaling message may indicate the starting RB 230 of the frequency region and the number of contiguous RBs 250 in the frequency domain. In some examples, the RRC signaling message may indicate the starting RB 230 and the ending RB 240 of the frequency region.
  • a member UE e.g., UE#1 may determine the common frequency region 220 within its active BWP (e.g., active BWP 210) . The numbering of the starting RB 230 and the ending RB 240 may be in reference to the lowest RB 260 (lowest in the frequency domain) of the active BWP 210.
  • the BS may transmit a DCI format (e.g., a group-common DCI format) and the scheduled PDSCH to the group of UEs in the frequency region 220.
  • the BS may configure a CORESET in the frequency region 220 to the group of UEs by RRC signaling (e.g., in the form of a RBG-based bitmap) , and may transmit a PDCCH carrying a DCI format in the CORESET.
  • the DCI format may include a FDRA indicator indicating the resource block assignment information for the scheduled PDSCH (e.g., a plurality of RBs for carrying the scheduled PDSCH) .
  • the number of bits of the FDRA indicator may be determined based on the number of contiguous RBs 250 (e.g., L) , as described above.
  • the resource block assignment information may be determined in reference to the starting RB 230 of the frequency region 220.
  • the starting RB 230 may be indexed as RB 0, and in the case that the resource block assignment information indicates that RB n is for the scheduled PDSCH, the UE would know that the scheduled PDSCH is transmitted at a frequency resource n RBs higher than the starting RB 230 in the frequency domain.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the scheduled UEs.
  • the number of bits of the bitmap can be determined based on the number of contiguous RBs 250 (e.g., L) , as described above.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB (in reference to the starting RB 230) and a length in terms of contiguously allocated resource blocks. The length does not exceed the number of contiguous RBs 250.
  • the member UEs can receive the scheduled PDSCH on a plurality of RBs within the frequency region 220 based on the DCI format.
  • a common CORESET may be configured by RRC signaling (e.g., MIB, SIB signaling or UE-specific RRC signaling) for a group of UEs to monitor the group-common DCI scheduling a PDSCH (e.g., MBS PDSCH) .
  • RRC signaling e.g., MIB, SIB signaling or UE-specific RRC signaling
  • Each UE of the group of UEs may be in an RRC_CONNECTED state.
  • the common CORESET may be within the active BWP of each member UE of the group of UEs.
  • the common CORESET may be indicated by a RBG-based bitmap, where, for example, each RBG includes 6 contiguous RBs with reference to Point A (i.e., the lowest subcarrier on the carrier, subcarrier 0 of common resource block (CRB) 0) .
  • Point A i.e., the lowest subcarrier on the carrier, subcarrier 0 of common resource block (CRB) 0
  • the PDCCH carrying a group-common DCI may be transmitted in the CORESET.
  • the scheduled PDSCH may be carried on a plurality of RBs within a frequency region ranging from the lowest RB (hereinafter, “RB x ” ) of the CORESET to the highest RB (hereinafter, “RB y ” ) of the CORESET.
  • the number of bits of a FDRA indicator in the group-common DCI may be determined based on the number of contiguous RBs within the frequency region ranging from the lowest RB of the CORESET to the highest RB of the CORESET.
  • the RB numbering may start from the lowest RB (lowest in the frequency domain) of the CORESET to the highest RB (highest in the frequency domain) of the CORESET.
  • RB x is used as the reference point (e.g., indexed as RB 0) for resource allocation indication in the frequency domain, i.e., RB x is used as the lowest RB for determining the frequency resource allocation of the group-common PDSCH.
  • the number of bits of the FDRA indicator in the group-common DCI can be determined according to where is set to RB y -RB x +1.
  • resource allocation type 0 is applied for downlink transmissions.
  • the resource block assignment information indicated by the FDRA indicator may include a bitmap indicating the resource block groups (RBGs) that are allocated to the scheduled UEs.
  • An RBG may be a set of consecutive RBs (e.g., VRBs) defined based on, for example, the above Table 1, where the bandwidth part size is set to RB y -RB x +1. For example, according to the above Table 1, when RB y -RB x +1 is 20 (i.e., between “1 –36” ) , the number of VRBs in a RBG is 2 in the case of configuration 1 and is 4 in the case of configuration 2.
  • An RRC signaling may indicate whether configuration 1 or configuration 2 is employed.
  • the number of bits of the bitmap is equal to the total number of RBGs (N RBG ) for the frequency region, which can be determined by
  • resource allocation type 1 is applied for downlink transmissions.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the lowest RB (hereinafter, “RB x ” ) of the CORESET, and the length does not exceed RB y -RB x +1.
  • RB x may be indexed as RB 0 for PDSCH resource block assignment i.e., RB x is used as the lowest RB for determining the frequency resource allocation of the group-common PDSCH.
  • FIG. 3 illustrates exemplary radio resource allocation 300 in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 3. It should be understood that FIG. 3 is only for illustrative purposes, and should not be construed as limiting the embodiments of the present disclosure.
  • a UE may support an active BWP 310.
  • the UE may be a member UE of a group of UEs.
  • Other UEs in the group of UEs support the same or different active BWPs (not shown in FIG. 3) .
  • a BS may configure a common CORESET 370 to the group of UEs via an RRC signaling message.
  • the common CORESET 370 may be within active BWP 310 of UE#1, as well as active BWPs of other UEs of the group of UEs.
  • the common CORESET 370 may start from the lowest RB 330 and may end at the highest RB 340 in the frequency domain.
  • the common CORESET 370 seems to occupy a number of contiguous RBs in the frequency domain, it should be appreciated by persons skilled in the art that the common CORESET may include a number of discrete RBs in the frequency domain.
  • the BS may transmit a DCI format (e.g., a group-common DCI format) to the group of UEs in the common CORESET 370.
  • the BS may transmit the PDSCH scheduled by the DCI format to the group of UEs in frequency region 320, ranging from the lowest RB 330 to the highest RB 340 of the CORESET 370.
  • the DCI format may include a FDRA indicator indicating the resource block assignment information for the scheduled PDSCH (e.g., a plurality of RBs for carrying the scheduled PDSCH in the frequency region) .
  • the number of bits of the FDRA indicator may be determined based on the number of contiguous RBs 350 (e.g., RB y -RB x +1) .
  • the resource block assignment information may be determined in reference to the lowest RB 330 of the CORESET 370. For example, in the case that the resource block assignment information indicates that RB n is for the scheduled PDSCH, the UE would know that the scheduled PDSCH is transmitted at a frequency resource n RBs higher than the lowest RB 330 in the frequency domain. That is, the lowest RB 330 is indexed as RB 0 when determining the frequency resource for the scheduled PDSCH.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the scheduled UEs.
  • the number of bits of the bitmap can be determined based on the number of contiguous RBs 350 (e.g., RB y -RB x +1) , as described above.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB (in reference to the lowest RB 330) and a length in terms of contiguously allocated resource blocks. The length does not exceed the number of contiguous RBs 350.
  • the member UEs can receive the scheduled PDSCH on a plurality of RBs within the frequency region 320 based on the DCI format.
  • the CORESET configured by RRC signaling (e.g., MIB, SIB signaling or UE-specific RRC signaling) for a group of UEs to monitor the group-common DCI scheduling a PDSCH may be within the initial DL BWP, rather than the active BWP.
  • the initial DL BWP may be configured to cover the CORESET where the group-common DCI is transmitted.
  • the PDCCH carrying a group-common DCI may be transmitted in the CORESET.
  • the PDCCH may be transmitted in several REGs within the CORESET.
  • Each REG may represent, for example, one RB in the frequency domain and one OFDM symbol in the time domain.
  • the lowest REG (s) (lowest in the frequency domain) of the PDCCH and the bandwidth of the initial DL BWP of a UE may define a frequency region for transmitting or receiving the scheduled PDSCH.
  • the number of bits of the FDRA indicator in the group-common DCI may be determined based on the number of RBs within the initial DL BWP of the UE.
  • RB numbering may start from the RB corresponding to the lowest REG (s) (lowest in the frequency domain) of the PDCCH. That is, the RB associated with the lowest REG of the PDCCH is used as reference RB 0 (e.g., indexed as RB 0) for determining resource allocation indication in the frequency domain.
  • the number of bits of the FDRA indicator in the group-common DCI can be determined according to where is set to the number of RBs within the initial DL BWP of a UE.
  • resource allocation type 0 is applied for downlink transmissions.
  • the resource block assignment information indicated by the FDRA indicator may include a bitmap indicating the RBGs that are allocated to the scheduled UEs.
  • An RBG may be a set of consecutive RBs (e.g., VRBs) defined based on, for example, the above Table 1, where the bandwidth part size is set to the number of RBs within the initial DL BWP of a UE.
  • the number of bits of this bitmap is equal to the total number of RBGs (N RBG ) for the frequency region, which can be determined by and is set to the number of RBs within the initial DL BWP of a UE.
  • resource allocation type 1 is applied for downlink transmissions.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the RB associated with the lowest REG of the PDCCH.
  • the length does not exceed the bandwidth of the initial DL BWP of a UE.
  • FIG. 4 illustrates exemplary radio resource allocation 400 in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 4. It should be understood that FIG. 4 is only for illustrative purposes, and should not be construed as limiting the embodiments of the present disclosure.
  • a UE may be configured with an initial BWP 410.
  • the UE may be a member UE of a group of UEs.
  • Other UEs in the group of UEs may be configured with the same or different initial BWPs (not shown in FIG. 4) .
  • a BS may configure a CORESET (not shown in FIG. 4) to the group of UEs via an RRC signaling message.
  • the CORESET may be within initial BWP 410 of UE#1, as well as the initial BWPs of other UEs of the group of UEs.
  • the BS may transmit a PDCCH 440 carrying a DCI format to the group of UEs in the configured CORESET.
  • the RB corresponding to the lowest REG (lowest in the frequency domain) of the PDCCH 440 is denoted as RB 430 in FIG. 4.
  • the BS may transmit the PDSCH 450 scheduled by the DCI format to the group of UEs in a frequency region (not shown in FIG. 4) starting from RB 430.
  • the DCI format may include a FDRA indicator indicating the resource block assignment information for the scheduled PDSCH (e.g., a plurality of RBs for carrying the scheduled PDSCH in the frequency region) .
  • the number of bits of the FDRA indicator may be determined based on the number of RBs within the initial BWP (e.g., initial BWP 410) .
  • the resource block assignment information may be determined in reference to RB 430. For example, in the case that the resource block assignment information indicates that RB n is for the scheduled PDSCH, the UE would know that the scheduled PDSCH is transmitted at a frequency resource n RBs higher than RB 430 in the frequency domain. That is, RB 430 is indexed as RB 0 when determining the frequency resource for the scheduled PDSCH.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the scheduled UEs.
  • the number of bits of the bitmap can be determined based on the number of RBs within the initial BWP (e.g., initial BWP 410) .
  • the resource block assignment information may indicate an RIV corresponding to a starting RB (in reference to RB 430) and a length in terms of contiguously allocated resource blocks. The length does not exceed the number of RBs within the initial BWP (e.g., initial BWP 410) .
  • the member UEs can receive the scheduled PDSCH 450 on a plurality of RBs within the frequency region based on the DCI format.
  • the lowest RB (lowest in the frequency domain) of the initial DL BWP and the bandwidth of the initial DL BWP of a UE may define a frequency region for transmitting or receiving the scheduled PDSCH.
  • the number of bits of the FDRA indicator in the group-common DCI may be determined based on the number of RBs within the initial DL BWP of the UE.
  • RB numbering may start from the lowest RB (lowest in the frequency domain) of the initial DL BWP. That is, the lowest RB of the initial DL BWP is used as reference RB 0 (e.g., indexed as RB 0) for resource allocation indication in the frequency domain.
  • the number of bits of the FDRA indicator in the group-common DCI can be determined according to where is set to the number of RBs within the initial DL BWP of a UE.
  • resource allocation type 0 is applied for downlink transmissions.
  • the resource block assignment information indicated by the FDRA indicator may include a bitmap indicating the RBGs that are allocated to the scheduled UEs.
  • An RBG may be a set of consecutive RBs (e.g., VRBs) defined based on, for example, the above Table 1, where the bandwidth part size is set to the number of RBs within the initial DL BWP of a UE.
  • the number of bits of the bitmap is equal to the total number of RBGs (N RBG ) for the frequency region, which is given by and is set to the number of RBs within the initial DL BWP.
  • the resource block assignment information indicates an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the lowest RB of the initial DL BWP.
  • the length does not exceed the bandwidth of the initial DL BWP of a UE.
  • UE#1 may receive an RRC signaling message from a BS configuring a CORESET (not shown in FIG. 4) for monitoring a PDCCH carrying a DCI format.
  • the CORESET may be within initial BWP 410 of UE#1, as well as initial BWPs of other UEs of the group of UEs.
  • the lowest RB of the initial BWP 410 is denoted as RB 460 in FIG. 4.
  • the BS may transmit the PDSCH 450 scheduled by the DCI format to the group of UEs in a frequency region within the initial BWPs of the group of UEs.
  • the DCI format may include a FDRA indicator indicating the resource block assignment information for the scheduled PDSCH 450 (e.g., a plurality of RBs for carrying the scheduled PDSCH in the frequency region) .
  • the number of bits of the FDRA indicator may be determined based on the number of RBs within the initial BWP (e.g., initial BWP 410) .
  • the resource block assignment information may be determined in reference to RB 460. For example, in the case that the resource block assignment information indicates that RB n is for the scheduled PDSCH, the UE would know that the scheduled PDSCH is transmitted at a frequency resource n RBs higher than RB 460 in the frequency domain. That is, RB 460 is indexed as RB 0 when determining the frequency resource for the scheduled PDSCH.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the scheduled UEs.
  • the number of bits of the bitmap can be determined based on the number of RBs within the initial BWP (e.g., initial BWP 410) .
  • the resource block assignment information may indicate an RIV corresponding to a starting RB (in reference to RB 460) and a length in terms of contiguously allocated resource blocks. The length does not exceed the number of RBs within the initial BWP (e.g., initial BWP 410) .
  • the member UEs can receive the scheduled PDSCH 450 on a plurality of RBs within the frequency region based on the DCI format.
  • the group-common DCI has to be transmitted in CORESET 0, and the scheduled group-common PDSCH has to be transmitted within the frequency region ranging from the lowest RB (hereinafter, “RB x0 ” ) of the CORESET 0 to the highest RB (hereinafter, “RB y0 ” ) of the CORESET 0.
  • the number of bits of a FDRA indicator in the group-common DCI may be determined based on the number of contiguous RBs within the frequency region ranging from the lowest RB of the CORESET 0 to the highest RB of the CORESET 0.
  • the RB numbering may start from the lowest RB (lowest in the frequency domain) of CORESET 0 to the highest RB (highest in the frequency domain) of CORESET 0.
  • RB x0 is used as the reference point (e.g., indexed as RB 0) for resource allocation indication in the frequency domain i.e., RB x0 is used as the lowest RB for determining the frequency resource allocation of the group-common PDSCH.
  • the number of bits of the FDRA indicator in the group-common DCI can be determined according to where is set to RB y0 -RB x0 +1.
  • resource allocation type 0 is applied for downlink transmissions.
  • the resource block assignment information indicated by the FDRA indicator may include a bitmap indicating the RBGs that are allocated to the scheduled UEs.
  • An RBG may be a set of consecutive RBs (e.g., VRBs) defined based on, for example, the above Table 1, where the bandwidth part size is set to RB y0 -RB x0 +1.
  • the number of bits of the bitmap is equal to the total number of RBGs (N RBG ) for the frequency region, which can be determined by
  • resource allocation type 1 is applied for downlink transmissions.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the lowest RB of CORESET 0, and the length does not exceed RB y0 -RB x0 +1.
  • RB x0 may be indexed as RB 0 for PDSCH resource block assignment.
  • the idle UE or inactive UE can receive the group-common DCI in CORESET 0 and the group-common PDSCH in the frequency region defined by the lowest RB and highest RB of CORESET 0.
  • FIG. 5 illustrates exemplary radio resource allocation 500 in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 5. It should be understood that FIG. 5 is only for illustrative purposes, and should not be construed as limiting the embodiments of the present disclosure.
  • a UE may be in an RRC_IDLE state or an RRC_INACTIVE state.
  • UE#1 may be a member UE of a group of UEs.
  • Other UEs in the group of UEs may be an RRC_IDLE state, an RRC_INACTIVE state, or an RRC_CONNECTED state.
  • a BS may transmit a DCI format (e.g., a group-common DCI format) to the group of UEs in CORESET 0 (e.g., CORESET 570) .
  • the BS may transmit the PDSCH scheduled by the DCI format to the group of UEs in frequency region 520, ranging from the lowest RB 530 of the CORESET 570 to the highest RB 540 of the CORESET 570.
  • the common CORESET 570 seems to occupy a number of contiguous RBs in the frequency domain, it should be appreciated by persons skilled in the art that the common CORESET may include a number of discrete RBs in the frequency domain.
  • the DCI format may include a FDRA indicator indicating the resource block assignment information for the scheduled PDSCH (e.g., a plurality of RBs for carrying the scheduled PDSCH in the frequency region) .
  • the number of bits of the FDRA indicator may be determined based on the number of contiguous RBs 550 (e.g., RB y0 -RB x0 +1) .
  • the resource block assignment information may be determined in reference to the lowest RB 530 of the CORESET 570. For example, in the case that the resource block assignment information indicates that RB n is for the scheduled PDSCH, the UE would know that the scheduled PDSCH is transmitted at a frequency resource n RBs higher than the lowest RB 530 in the frequency domain. That is, the lowest RB 530 is indexed as RB 0 when determining the frequency resource for the scheduled PDSCH.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the scheduled UEs.
  • the number of bits of the bitmap can be determined based on the number of contiguous RBs 550 (e.g., RB y0 -RB x0 +1) .
  • the resource block assignment information may indicate an RIV corresponding to a starting RB (in reference to the lowest RB 530) and a length in terms of contiguously allocated resource blocks. The length does not exceed the number of contiguous RBs 550.
  • an idle UE or inactive UE can receive the group-common DCI in CORESET 0 and the group-common PDSCH in the frequency region defined by the lowest RB and highest RB of CORESET 0.
  • the group-common DCI in the case that a MBS is transmitted to a group of UEs including both connected UEs and idle or inactive UEs, the group-common DCI has to be transmitted in CORESET 0 and the scheduled group-common PDSCH has to be transmitted within the frequency region starting from the lowest RB of the CORESET 0 and ending at the highest RB of the CORESET 0.
  • both connected mode UEs and idle/inactive mode UEs in the group of UEs may receive the group-common DCI in CORESET 0 and the group-common PDSCH in the frequency region defined by the lowest RB and highest RB of CORESET 0.
  • FIG. 6 illustrates a flow chart of an exemplary procedure 600 for wireless communications in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 6.
  • the procedure may be performed by a UE, for example, UE 101 in FIG. 1.
  • a UE may receive a PDCCH within a CORESET.
  • the PDCCH may carry a DCI format for scheduling a PDSCH.
  • the DCI format may be a group-common DCI format.
  • the UE may receive the PDSCH on a plurality of RBs based on the DCI format.
  • the plurality of RBs may be within a frequency region.
  • the UE may receive an RRC signaling message configuring the frequency region.
  • the frequency region may be shared between the UE and another UE.
  • a group of UEs may be configured with a common frequency region.
  • the RRC signaling message may indicate a starting RB (e.g., starting RB 230 in FIG. 2) and a number of contiguous RBs (e.g., the number of contiguous RBs 260 in FIG. 2) of the frequency region.
  • the RRC signaling message may indicate a starting RB and an ending RB (e.g., the ending RB 240 in FIG. 2) of the frequency region.
  • the CORESET may be within the frequency region.
  • the plurality of RBs may be determined in reference to the starting RB of the frequency region.
  • the DCI format may indicate resource block assignment information in reference to the starting RB of the frequency region.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the UE for receiving the scheduled PDSCH.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the starting RB of the frequency region. The length may not exceed the total number of RBs contained within the frequency region.
  • a payload size of the DCI format may be based on the total number of RBs contained within the frequency region. For example, the number of bits of a FDRA indicator in the DCI may be determined based on the total number of RBs in the frequency region.
  • the UE may receive an RRC signaling message configuring the CORESET.
  • the CORESET may be shared between the UE and another UE.
  • the frequency region may be based on the CORESET.
  • the CORESET (e.g., CORESET 370 in FIG. 3) may be within an active BWP (e.g., active BWP 310 in FIG. 3) of the UE and an active BWP of the another UE.
  • the frequency region may range from the lowest RB (e.g., the lowest RB 330 in FIG. 3) of the CORESET to the highest RB (e.g., the highest RB 340 in FIG. 3) of the CORESET.
  • the plurality of RBs may be determined in reference to the lowest RB of the CORESET.
  • the DCI format may indicate resource block assignment information in reference to the lowest RB of the CORESET.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the UE for receiving the scheduled PDSCH.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the lowest RB of the CORESET.
  • the length may not exceed the total number of contiguous RBs from the lowest RB of the CORESET to the highest RB of the CORESET.
  • a payload size of the DCI format may be based on the total number of contiguous RBs from the lowest RB of the CORESET to the highest RB of the CORESET. For example, the number of bits of a FDRA indicator in the DCI may be determined based on the total number of contiguous RBs from the lowest RB of the CORESET to the highest RB of the CORESET.
  • the CORESET in which the PDCCH is transmitted may be within an initial DL BWP (e.g., initial BWP 410 in FIG. 4) of the UE and an initial DL BWP of the another UE.
  • the frequency region may start from the RB (e.g., RB 430 in FIG. 4) corresponding to the lowest REG of the PDCCH.
  • the plurality of RBs may be determined in reference to the RB corresponding to the lowest REG of the PDCCH.
  • the DCI format may indicate resource block assignment information in reference to the RB corresponding to the lowest REG of the PDCCH.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the UE for receiving the scheduled PDSCH.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the RB corresponding to the lowest REG of the PDCCH. The length may not exceed the bandwidth of the initial DL BWP of the UE.
  • a payload size of the DCI format may be based on the initial DL BWP of the UE. For example, the number of bits of a FDRA indicator in the DCI may be determined based on the number of RBs within the initial DL BWP of the UE.
  • the CORESET and the frequency region may be within an initial DL BWP (e.g., initial BWP 410 in FIG. 4) of the UE and an initial DL BWP of another UE.
  • the plurality of RBs may be determined in reference to the lowest RB of the initial downlink BWP of the UE.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the UE for receiving the scheduled PDSCH.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the lowest RB of the initial downlink BWP of the UE.
  • the length may not exceed the bandwidth of the initial DL BWP of the UE.
  • a payload size of the DCI format may be based on the initial DL BWP of the UE. For example, the number of bits of a FDRA indicator in the DCI may be determined based on the number of RBs within the initial DL BWP of the UE.
  • the CORESET in which the PDCCH in received by the UE is CORESET 0.
  • the PDSCH scheduled by the DCI format is received by the UE within a frequency region ranging from the lowest RB (e.g., “RB x0 ” ) of the CORESET 0 to the highest RB (e.g., “RB y0 ” ) of the CORESET 0.
  • FIG. 7 illustrates a flow chart of an exemplary procedure 700 for wireless communications in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 7.
  • the procedure may be performed by a BS, for example, BS 102 in FIG. 1.
  • a BS may transmit, to at least one UE, a PDCCH within a CORESET.
  • the PDCCH may carry a DCI format for scheduling a PDSCH.
  • the BS may transmit, to the at least one UE, the PDSCH on a plurality of RBs based on the DCI format.
  • the plurality of RBs may be within a frequency region.
  • the BS may transmit an RRC signaling message configuring the frequency region.
  • the frequency region may be shared between the at least one UE.
  • a group of UEs may be configured with a common frequency region.
  • the RRC signaling message may indicate a starting RB (e.g., starting RB 230 in FIG. 2) and a number of contiguous RBs (e.g., the number of contiguous RBs 250 in FIG. 2) of the frequency region.
  • the RRC signaling message may indicate a starting RB and an ending RB (e.g., the ending RB 240 in FIG. 2) of the frequency region.
  • the CORESET may be within the frequency region.
  • the plurality of RBs may be in reference to the starting RB of the frequency region.
  • the DCI format may indicate resource block assignment information in reference to the starting RB of the frequency region.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the UE for receiving the scheduled PDSCH.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the starting RB of the frequency region. The length may not exceed the total number of RBs contained within the frequency region.
  • a payload size of the DCI format may be based on the total number of RBs contained within the frequency region. For example, the number of bits of a FDRA indicator in the DCI may be determined based on the total number of RBs in the frequency region.
  • the BS may transmit an RRC signaling message configuring the CORESET.
  • the CORESET may be shared between the at least one UE.
  • the frequency region may be based on the CORESET.
  • the CORESET (e.g., CORESET 370 in FIG. 3) may be within an active BWP (e.g., active BWP 310 in FIG. 3) of the at least one UE.
  • the frequency region may range from the lowest RB (e.g., the lowest RB 330 in FIG. 3) of the CORESET to the highest RB (e.g., the highest RB 340 in FIG. 3) of the CORESET.
  • the plurality of RBs may be determined in reference to the lowest RB of the CORESET.
  • the DCI format may indicate resource block assignment information in reference to the lowest RB of the CORESET.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the UE for receiving the scheduled PDSCH.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the lowest RB of the CORESET.
  • the length may not exceed the total number of contiguous RBs from the lowest RB of the CORESET to the highest RB of the CORESET.
  • a payload size of the DCI format may be based on the total number of contiguous RBs from the lowest RB of the CORESET to the highest RB of the CORESET. For example, the number of bits of a FDRA indicator in the DCI may be determined based on the total number of contiguous RBs from the lowest RB of the CORESET to the highest RB of the CORESET.
  • the CORESET in which the PDCCH is transmitted may be within an initial DL BWP (e.g., initial BWP 410 in FIG. 4) of the at least one UE.
  • the frequency region may start from the RB (e.g., RB 430 in FIG. 4) corresponding to the lowest REG of the PDCCH.
  • the plurality of RBs may be determined in reference to the RB corresponding to the lowest REG of the PDCCH.
  • the DCI format may indicate resource block assignment information in reference to the RB corresponding to the lowest REG of the PDCCH.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the UE for receiving the scheduled PDSCH.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the RB corresponding to the lowest REG of the PDCCH. The length may not exceed the bandwidth of the initial DL BWP of the UE.
  • a payload size of the DCI format may be based on the initial DL BWP of the UE. For example, the number of bits of a FDRA indicator in the DCI may be determined based on the number of RBs within the initial DL BWP of the UE.
  • the CORESET and the frequency region may be within an initial DL BWP (e.g., initial BWP 410 in FIG. 4) of the at least one UE.
  • the plurality of RBs may be determined in reference to the lowest RB of the initial downlink BWP of the at least one UE.
  • the resource block assignment information may include a bitmap indicating the RBGs that are allocated to the UE for receiving the scheduled PDSCH.
  • the resource block assignment information may indicate an RIV corresponding to a starting RB of the scheduled PDSCH and a length in terms of contiguously allocated resource blocks.
  • the starting RB of the scheduled PDSCH is in reference to the lowest RB of the initial downlink BWP of the at least one UE.
  • the length may not exceed the bandwidth of the initial DL BWP of the at least one UE.
  • a payload size of the DCI format may be based on the initial DL BWP of the at least one UE. For example, the number of bits of a FDRA indicator in the DCI may be determined based on the number of RBs within the initial DL BWP of the at least one UE.
  • the CORESET in which the PDCCH in transmitted is CORESET 0.
  • the PDSCH scheduled by the DCI format is transmitted within a frequency region ranging from the lowest RB (e.g., “RB x0 ” ) of the CORESET 0 to the highest RB (e.g., “RB y0 ” ) of the CORESET 0.
  • FIG. 8 illustrates a block diagram of an exemplary apparatus 800 according to some embodiments of the present disclosure.
  • the apparatus 800 may include at least one non-transitory computer-readable medium 801, at least one receiving circuitry 802, at least one transmitting circuitry 804, and at least one processor 806 coupled to the non-transitory computer-readable medium 801, the receiving circuitry 802 and the transmitting circuitry 804.
  • the apparatus 800 may be a base station side apparatus (e.g., a BS) or a communication device (e.g., a UE) .
  • the at least one processor 806, transmitting circuitry 804, and receiving circuitry 802 are described in the singular, the plural is contemplated unless a limitation to the singular is explicitly stated.
  • the receiving circuitry 802 and the transmitting circuitry 804 are combined into a single device, such as a transceiver.
  • the apparatus 800 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 801 may have stored thereon computer-executable instructions to cause a processor to implement the method with respect to the UEs as described above.
  • the computer-executable instructions when executed, cause the processor 806 interacting with receiving circuitry 802 and transmitting circuitry 804, so as to perform the operations with respect to the UEs described in FIGS. 1-7.
  • the non-transitory computer-readable medium 801 may have stored thereon computer-executable instructions to cause a processor to implement the method with respect to the BSs as described above.
  • the computer-executable instructions when executed, cause the processor 806 interacting with receiving circuitry 802 and transmitting circuitry 804, so as to perform the operations with respect to the BSs described in FIGS. 1-7.
  • a 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.
  • the operations or steps of a method may reside as one or any combination or set of codes and/or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.
  • the terms “includes, “ “including, “ or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • An element proceeded by “a, “ “an, “ or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.
  • the term “another” is defined as at least a second or more.
  • the term “having” and the like, as used herein, are defined as “including. " The wording "the first, “ “the second” or the like is only used to clearly illustrate the embodiments of the present application, but is not used to limit the substance of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Dans des modes de réalisation, l'invention concerne l'attribution de ressources de domaine fréquentiel pour des transmissions de liaison descendante. Selon certains modes de réalisation de l'invention, un procédé de communication sans fil est réalisé par un équipement utilisateur (UE) peut comprendre : la réception d'un canal physique de contrôle descendant (PDCCH) dans un ensemble de ressources de commande (CORESET), le PDCCH transportant un format d'informations de commande de liaison descendante (DCI) pour planifier un canal physique partagé descendant (PDSCH) ; et la réception du PDSCH sur une pluralité de blocs de ressources (RB) sur la base du format DCI, la pluralité de RB étant dans une région de fréquence.
PCT/CN2020/123180 2020-10-23 2020-10-23 Procédé et appareil d'attribution de ressources de domaine fréquentiel pour transmissions de liaison descendante WO2022082715A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202080106491.1A CN116491198A (zh) 2020-10-23 2020-10-23 用于下行链路传输的频域资源分配的方法及设备
EP20958297.2A EP4233451A1 (fr) 2020-10-23 2020-10-23 Procédé et appareil d'attribution de ressources de domaine fréquentiel pour transmissions de liaison descendante
PCT/CN2020/123180 WO2022082715A1 (fr) 2020-10-23 2020-10-23 Procédé et appareil d'attribution de ressources de domaine fréquentiel pour transmissions de liaison descendante
US18/249,690 US20230388092A1 (en) 2020-10-23 2020-10-23 Method and apparatus for frequency domain resource allocation for downlink transmissions

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/123180 WO2022082715A1 (fr) 2020-10-23 2020-10-23 Procédé et appareil d'attribution de ressources de domaine fréquentiel pour transmissions de liaison descendante

Publications (1)

Publication Number Publication Date
WO2022082715A1 true WO2022082715A1 (fr) 2022-04-28

Family

ID=81291169

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123180 WO2022082715A1 (fr) 2020-10-23 2020-10-23 Procédé et appareil d'attribution de ressources de domaine fréquentiel pour transmissions de liaison descendante

Country Status (4)

Country Link
US (1) US20230388092A1 (fr)
EP (1) EP4233451A1 (fr)
CN (1) CN116491198A (fr)
WO (1) WO2022082715A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109152023A (zh) * 2017-06-16 2019-01-04 华为技术有限公司 资源分配的方法、网络设备和终端设备
CN110168972A (zh) * 2017-01-04 2019-08-23 三星电子株式会社 用于无线通信系统中的系统信息传递的方法和装置
US20200022168A1 (en) * 2018-07-11 2020-01-16 Qualcomm Incorporated Shared channel rate matching with wideband demodulation reference signal for a control channel
CN110786045A (zh) * 2017-06-16 2020-02-11 韩国电子通信研究院 通信系统中用于支持宽带载波的带宽设定方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110168972A (zh) * 2017-01-04 2019-08-23 三星电子株式会社 用于无线通信系统中的系统信息传递的方法和装置
CN109152023A (zh) * 2017-06-16 2019-01-04 华为技术有限公司 资源分配的方法、网络设备和终端设备
CN110786045A (zh) * 2017-06-16 2020-02-11 韩国电子通信研究院 通信系统中用于支持宽带载波的带宽设定方法
US20200022168A1 (en) * 2018-07-11 2020-01-16 Qualcomm Incorporated Shared channel rate matching with wideband demodulation reference signal for a control channel

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, ALCATEL-LUCENT SHANGHAI BELL: "On the PDCCH control resource set and its connection to the search space for NR", 3GPP DRAFT; R1-1710980_CORESET CONFIG_FINAL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Qingdao, P.R. China; 20170627 - 20170630, 26 June 2017 (2017-06-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051300180 *

Also Published As

Publication number Publication date
CN116491198A (zh) 2023-07-25
EP4233451A1 (fr) 2023-08-30
US20230388092A1 (en) 2023-11-30

Similar Documents

Publication Publication Date Title
CN111742510B (zh) 无线通信系统中发送上行链路控制信息的方法及使用其的装置
US20220304059A1 (en) Method and Apparatus for Sharing Channel Occupancy Time on Unlicensed Spectrum
US20220394601A1 (en) Method and apparatus for wireless communication
WO2022151348A1 (fr) Procédé et appareil d'alignement de taille d'informations de commande de liaison descendante
WO2022082715A1 (fr) Procédé et appareil d'attribution de ressources de domaine fréquentiel pour transmissions de liaison descendante
WO2023010279A1 (fr) Procédé et appareil de configuration de ressources pucch pour service de multidiffusion
WO2023044718A1 (fr) Procédé et appareil d'attribution de ressources de domaine fréquentiel pour transmissions de liaison descendante en multicast
WO2023050448A1 (fr) Procédé et appareil pour détermination de taille de charge utile dci commune à un groupe
WO2022151346A1 (fr) Procédé et appareil de transmission en multidiffusion
US20240137183A1 (en) Method and apparatus for harq-ack feedback transmission
WO2023184488A1 (fr) Procédé et appareil d'attribution de ressources de domaine fréquentiel sur de multiples porteuses
WO2022226988A1 (fr) Procédé et appareil de transmission pucch
WO2024082433A1 (fr) Procédé et appareil d'indication d'informations relatives à un accès à un canal dans un scénario d'agrégation de porteuses
WO2022067641A1 (fr) Procédé et appareil pour l'ordonnancement et la transmission dans les sens montant et descendant
WO2023115519A1 (fr) Procédé et appareil de détermination de livre de codes harq-ack
WO2022236673A1 (fr) Procédé et appareil de détermination de livre de codes harq-ack de type 1
WO2022056844A1 (fr) Procédé et appareil pour transmissions multiples programmées par un seul format dci
WO2023130461A1 (fr) Procédé et appareil de détermination de livre de codes harq-ack semi-statique pour multidiffusion
WO2024074003A1 (fr) Procédé et appareil d'indication de ressource de domaine temporel dans un scénario de planification multicellulaire
WO2023130459A1 (fr) Procédé et appareil de détermination de retour harq-ack de multidiffusion
WO2022205296A1 (fr) Procédé et appareil de rétroaction harq-ack pour une transmission de planification semi-persistante
WO2024073996A1 (fr) Procédé et appareil d'indication de ressource de domaine fréquentiel dans un scénario de planification multicellulaire
WO2024000476A1 (fr) Procédé et appareil de transmission sur liaison latérale à base de groupes sur un spectre sans licence
WO2024011501A1 (fr) Procédé et appareil de partage de cot pour diffusion de groupe de liaison latérale
WO2023137703A1 (fr) Procédé et appareil pour des réceptions de multidiffusion sur de multiples porteuses

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20958297

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18249690

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 202080106491.1

Country of ref document: CN

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112023007645

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020958297

Country of ref document: EP

Effective date: 20230523

ENP Entry into the national phase

Ref document number: 112023007645

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20230424