Resource allocation indication in unrestricted bandwidth portion

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may determine resource allocation information while operating on an unrestricted bandwidth portion (BWP) that is not configured with a control resource set (CORESET) associated with system information (SI) acquisition. For example, the UE may receive first control information indicating a first CORESET associated with SI acquisition. The UE may receive second control information indicating an unrestricted BWP, the unrestricted BWP being configured with a second CORESET that is different from the first CORESET. A bandwidth of the unrestricted BWP may be equal to, greater than, or less than a bandwidth of the first CORESET. The UE may determine a resource indicator value (RIV) to be included in a frequency domain resource allocation (FDRA) field for the unrestricted BWP. The UE may communicate via the unrestricted BWP based on the RIV.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 790,990, filed July 31, 2024, entitled “RESOURCE ALLOCATION INDICATION IN UNRESTRICTED BANDWIDTH PART,” and U.S. Provisional Patent Application No. 63 / 578,942, filed August 25, 2023, entitled “RESOURCE ALLOCATION INDICATION IN UNRESTRICTED BANDWIDTH PART,” each of which is assigned to the assignee of this application and each of which is expressly incorporated herein by reference. Technical Field

[0003] The following content relates to wireless communications, including resource allocation instructions in the Unrestricted Bandwidth Part (BWP). Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). UEs may be configured to monitor control messages that can be received in a Control Resource Set (CORESET). The UE typically monitors the default CORESET (CORESET #0) to receive control messages related to common system information (SI) (such as those that may be included in the default system information block (SIB1)). However, the UE can operate in the bandwidth portion (BWP) where CORESET #0 is not configured. Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting resource allocation indications in a bandwidth portion (BWP) that is not configured with a default control resource set (CORESET) #0. Such a BWP is also referred to as an unrestricted BWP. The technology described herein enables a user equipment (UE) to determine resource allocation information when operating on an unrestricted BWP. For example, a network entity may configure the UE with a first CORESET (e.g., CORESET #0) associated with system information (SI) acquisition (e.g., via control information). The network entity may also configure the UE with a BWP (e.g., an unrestricted BWP) configured with a second CORESET (e.g., the unrestricted BWP is not configured with CORESET #0). The bandwidth of the first CORESET may differ from the bandwidth of the unrestricted BWP. The UE may determine the resource indicator value (RIV) to be included in the Frequency Domain Resource Allocation (FDRA) field for the unrestricted BWP based on the fact that the unrestricted BWP is configured with a CORESET other than CORESET #0. The UE and the network entity can communicate via the unrestricted BWP based on the determined RIV.

[0006] A method for wireless communication by a UE is described. The method may include: receiving first control information indicating a first core set associated with system information acquisition, the first core set having a first bandwidth; receiving second control information indicating a first base station (BWP) configured with a second core set different from the first core set, wherein the first BWP has a second bandwidth; determining, at least in part, a resource indicator value to be included in a frequency domain resource allocation field for the first BWP based on the first BWP being configured with a core set different from the first core set; and communicating via the first BWP based on the resource indicator value.

[0007] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the UE to: receive first control information indicating a first core set associated with system information acquisition, the first core set having a first bandwidth; receive second control information indicating a first baseband window (BWP) configured with a second core set different from the first core set, wherein the first BWP has a second bandwidth; determine a resource indicator value to be included in a frequency domain resource allocation field for the first BWP, at least in part based on the first BWP being configured with a core set different from the first core set; and communicate via the first BWP, at least in part based on the resource indicator value.

[0008] Another UE for wireless communication is described. The UE may include: means for receiving first control information indicating a first CORESET associated with system information acquisition, the first CORESET having a first bandwidth; means for receiving second control information indicating a first BWP, the first BWP being configured with a second CORESET different from the first CORESET, wherein the first BWP has a second bandwidth; means for determining, at least in part, a resource indicator value to be included in a frequency domain resource allocation field for the first BWP based on the first BWP being configured with a CORESET different from the first CORESET; and means for communicating via the first BWP based on the resource indicator value.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive first control information indicating a first core set associated with system information acquisition, the first core set having a first bandwidth; receive second control information indicating a first baseband window (BWP) configured with a second core set different from the first core set, wherein the first BWP has a second bandwidth; determine, at least in part, a resource indicator value to be included in a frequency domain resource allocation field for the first BWP based on the first BWP being configured with a core set different from the first core set; and communicate via the first BWP at least in part based on the resource indicator value.

[0010] The methods, UEs, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving third control information for scheduling a physical downlink shared channel associated with a third bandwidth and a first resource block, wherein the third bandwidth is within the second bandwidth, and wherein the first resource block may be the lowest resource block index of the physical downlink shared channel, and the value of the first resource block may be greater than or equal to the lowest resource block index of the first BWP. In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first bandwidth may be greater than the second bandwidth.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the resource indicator value may include operations, features, components, or instructions for: determining the virtual bandwidth and the third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth may be equal to the first bandwidth, and the highest resource block index of the physical downlink shared channel may be equal to or less than the minimum of the following: the highest resource block index of the first BWP; or the difference between the virtual bandwidth and the value of the first resource block, wherein the resource indicator value may be determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the resource indicator value may include operations, features, components, or instructions for: determining a virtual bandwidth and a third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth may be equal to the second bandwidth, and the highest resource block index of the physical downlink shared channel may be equal to or less than the difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value may be determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the resource indicator value may include operations, features, components, or instructions for: calculating a first bit width based on the number (e.g., quantity) of resource blocks in the first CORESET, wherein the second bit width may be the bit width of the resource indicator value; and including the resource indicator value in the frequency domain resource allocation field if the second bit width may be equal to the first bit width, or including the resource indicator value and bit padding in the frequency domain resource allocation field if the second bit width may be less than the first bit width, wherein the bit padding may be equal to the difference between the first bit width and the second bit width.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the second bandwidth may be greater than the first bandwidth. In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the resource indicator value may include operations, features, components, or instructions for: determining a virtual bandwidth and a third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth may be equal to the first bandwidth, and the highest resource block index of the physical downlink shared channel may be equal to or less than the difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value may be determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the resource indicator value may include operations, features, components, or instructions for: determining a virtual bandwidth and a third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth may be equal to the second bandwidth, and the highest resource block index of the physical downlink shared channel may be equal to or less than the difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value may be determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the resource indicator value may include operations, features, components, or instructions for: calculating a first bit width based on the first CORESET, wherein the second bit width may be the bit width of the resource indicator value; and including the resource indicator value in the frequency domain resource allocation field if the second bit width may be equal to the first bit width, or including the resource indicator value and a truncated resource indicator value in the frequency domain resource allocation field if the second bit width may be less than the first bit width, wherein the truncated resource indicator value may be equal to the difference between the second bit width and the first bit width.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the resource indicator value may include operations, features, components, or instructions for: determining the virtual bandwidth and the third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth may be equal to the second bandwidth, and the highest resource block index of the physical downlink shared channel may be equal to or less than the difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value may be determined using the virtual bandwidth, the size of the first BWP, the value of the first resource block, and the third bandwidth.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the resource indicator value may include operations, features, components, or instructions for determining the size of a resource block group based on the second bandwidth and the baseline bandwidth, wherein the baseline bandwidth may be equal to the first bandwidth or a fourth bandwidth associated with the second BWP, and wherein the resource indicator value may be determined using at least the size of the resource block group.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the CORESET identifier of the first CORESET may be zero. In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving the second control information indicating the first BWP may include operations, features, components, or instructions for receiving the second control information via a radio resource control message or a system information message, wherein the first BWP may be an unrestricted downlink BWP that is not associated with the first CORESET.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the unrestricted downlink BWP can be a dedicated downlink BWP configured by the radio resource control message for an enhanced mobile broadband (eMBB) UE in a radio resource control connected state.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the unrestricted downlink BWP may be a dedicated downlink BWP configured by the radio resource control message for a connected, reduced-capability (RedCap) or enhanced-capability (eRedCap) UE.

[0022] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the unrestricted downlink BWP may be an initial downlink BWP configured by a system information message for random access by a RedCap or eRedCap UE in an idle or inactive state.

[0023] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the lowest resource block index of the first bandwidth portion may be greater than or equal to the resource block index of the first CORESET. Attached Figure Description

[0024] Figure 1 An example of a wireless communication system is shown that supports resource allocation instructions in an unrestricted bandwidth portion (BWP) according to one or more aspects of this disclosure.

[0025] Figure 2An example of a wireless communication system supporting resource allocation instructions in an unrestricted BWP, according to one or more aspects of this disclosure, is shown.

[0026] Figure 3 An example of a relative bandwidth comparison associated with a resource allocation instruction in an unrestricted BWP, according to one or more aspects of this disclosure, is shown.

[0027] Figure 4 An example of a relative bandwidth comparison associated with a resource allocation instruction in an unrestricted BWP, according to one or more aspects of this disclosure, is shown.

[0028] Figure 5 An example of a process flow supporting resource allocation instructions in an unrestricted BWP is shown, according to one or more aspects of this disclosure.

[0029] Figure 6 and Figure 7 A diagram is shown of an apparatus that supports resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure.

[0030] Figure 8 A diagram is shown of a communication manager that supports resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure.

[0031] Figure 9 A diagram of a system including a device supporting resource allocation instructions in an unrestricted BWP is shown, according to one or more aspects of this disclosure.

[0032] Figure 10 and Figure 11 A flowchart illustrating a method for supporting resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure is shown. Detailed Implementation

[0033] In some cases, a User Equipment (UE) may support Bandwidth Partial (BWP) operation. A BWP can be a set of Common Resource Blocks (RBs) that constitute a portion of the total channel bandwidth configured for the cell. The UE can communicate with network entities via this BWP. In some instances, a UE (e.g., an eMBB UE, a RedCap UE, or an eRedCap UE) may be configured with a dedicated downlink BWP. This dedicated downlink BWP can be configured by Radio Resource Control (RRC) messages or System Information (SI) messages. However, a BWP configured by RRC or SI messages may not include a Control Resource Set (CORESET), such as the default CORESET #0. Therefore, the bandwidth of this BWP may differ from the bandwidth of CORESET #0. CORESET #0 may include the Physical Downlink Control Channel (PDCCH) and Downlink Control Information (DCI) for SI Blocks (SIBs) (e.g., SIB1). That is, the UE can typically determine resource allocation information (e.g., time-domain and frequency-domain resource allocation) based on the configured CORESET #0. However, the UE can be configured with a BWP corresponding to a non-zero CORESET (e.g., a CORESET identified as 1, 2, 3, etc.).

[0034] In some examples, the UE can determine resource allocation information when operating on an unrestricted BWP (e.g., an unrestricted downlink BWP not associated with CORESET #0). For example, the UE can operate on a cell configured with CORESET #0 and an unrestricted BWP. The bandwidth of the unrestricted BWP can be equal to, less than, or greater than the bandwidth of CORESET #0. Furthermore, the UE can receive control information for scheduling a Physical Downlink Shared Channel (PDSCH) whose bandwidth is within the bandwidth of the unrestricted BWP. The UE can determine the Resource Indicator Value (RIV) to be included in the FDRA field based on information corresponding to CORESET #0, the unrestricted BWP, and the PDSCH. Therefore, the UE can communicate with network entities (e.g., send or receive messages) based on the determined RIV.

[0035] The aspects of this disclosure are first described in the context of a wireless communication system, RB index diagram, and process flow. The aspects of this disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to resource allocation instructions in an unrestricted BWP.

[0036] Figure 1An example of a wireless communication system 100 supporting resource allocation instructions in an unrestricted BWP, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be an LTE network, an LTE-A network, an LTE-APro network, an NR network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not expressly mentioned herein.

[0037] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0038] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0039] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0040] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0041] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0042] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0043] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., RRC, Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0044] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0045] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of that decomposed RAN architecture can be configured to support resource allocation indications in an unrestricted BWP as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0046] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0047] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0048] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of an RF spectrum band (e.g., BWP) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signal, SI), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0049] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0050] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured using multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0051] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0052] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0053] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0054] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. A control region (e.g., CORESET) for the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0055] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0056] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0057] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), eMBB).

[0058] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0059] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., subcarriers or RB sets) within the carrier, within the carrier's guard band, or outside the carrier.

[0060] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0061] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0062] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0063] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0064] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0065] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0066] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0067] In some cases, UE 115 may support BWP operation. A BWP can be a set of common redundancies (RBs) that constitute a portion of the total channel bandwidth configured for the cell. UE 115 can communicate with network entity 105 via this BWP. In some instances, UE 115 (e.g., eMBB UE 115, RedCap UE 115, or eRedCap UE 115) may be configured with a dedicated downlink BWP.

[0068] In some cases, the dedicated downlink BWP can be configured by RRC messages or SI messages. For example, eMBB UE 115 can support BWP operation without cell (e.g., primary cell (PCell), secondary cell (SCell), and primary-secondary cell (PSCell) restrictions) when in a connected state (e.g., the BWP can be configured by an RRC message). Furthermore, eMBB UE 115 operating in an active BWP excluding CORESET #0 can support Radio Link Monitoring (RLM), Beam Management (BM), and Beam Failure Detection (BFD) measurements based on a received cell-defined synchronization signal block (CD-SSB) outside the active BWP or a non-CD-SSB (NCD-SSB) within the active BWP. In another example, RedCap UE can support random access (RA) procedures (e.g., RA-based) on the PCell in a RedCap-specific initial downlink BWP. When RedCap UE 115 is in an idle or inactive state, network entity 105 can configure the BWP via an SI message excluding an SSB or CORESET #0. In an additional example, when RedCap UE 115 is in a connected state, RedCap UE 115 with advanced capabilities... UE 115 can support downlink BWPs on PCells that do not have an SSB or CORESET #0 (e.g., the BWP can be configured by an RRC message). However, unrestricted BWPs configured by RRC or SI messages may not include CORESET #0.

[0069] In some cases, UE 115 may determine resource allocation information (e.g., time-domain and frequency-domain resource allocation) based on a configured CORESET #0. However, UE 115 may be configured with an unrestricted BWP corresponding to a non-zero CORESET (e.g., a CORESET identified as 1, 2, 3, etc.). Additionally, this unrestricted BWP may be associated with a control search space (CSS) that includes a DCI (e.g., DCI format 1_0). This DCI format (e.g., decoded in the CSS) may be given by the size of CORESET #0 (e.g., if CORESET #0 is configured for a cell) or the size on the downlink BWP (e.g., if CORESET #0 is not configured for a cell).

[0070] UE 115 operating in an unrestricted BWP can receive a DCI (e.g., DCI format 1_0) that schedules PDSCH. This PDSCH can be scheduled within the bandwidth of the unrestricted BWP. However, when the bandwidth of CORESET #0 differs from the bandwidth of the unrestricted BWP, downlink resource allocation in the frequency domain can be inefficient. For example, in a Type 1 resource allocation, when CORESET #0 is configured for a cell (e.g., a cell connected to UE 115) but not in the unrestricted BWP (e.g., the BWP is configured with a non-zero CORESET), UE 115 can determine the RIV in the DCI (e.g., DCI 1_0) based on the size of CORESET #0. In one example, the bandwidth of the unrestricted BWP may be greater than the bandwidth of CORESET #0. This can impose scheduling constraints on the PDSCH, potentially leading to reliability losses (e.g., frequency diversity gain loss) and / or throughput losses (reduced transport block size (TBS)). In another example, the bandwidth of the unrestricted BWP may be less than the bandwidth of CORESET #0. This scenario could lead to ambiguity in PDSCH scheduling and decoding between network entity 105 and UE 115. Therefore, downlink resource allocation can be clarified so that when UE 115 operates in an unrestricted BWP, UE 115 can determine the RIV to be included in the FDRA (e.g., in DCI format 1_0 in CSS).

[0071] In some cases, UE 115 may determine resource allocation information when operating on an unrestricted BWP (e.g., an unrestricted downlink BWP not associated with CORESET #0). For example, UE 115 may operate on a cell configured with CORESET #0 and an unrestricted BWP. The bandwidth of the unrestricted BWP may be equal to, less than, or greater than the bandwidth of CORESET #0. Furthermore, UE 115 may receive control information from network entity 105 for scheduling PDSCH, the bandwidth of which is within the bandwidth of the unrestricted BWP. UE 115 may determine (e.g., calculate) the RIV to be included in the FDRA field based on information corresponding to CORESET #0, the unrestricted BWP, and the PDSCH. Therefore, UE 115 may communicate with network entity 105 (e.g., send or receive messages) based on the determined RIV.

[0072] Figure 2 An example of a wireless communication system 200 supporting resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may include network entities 105-a and UE 115-a, which may be as described in reference... Figure 1 Examples of network entity 105 and UE 115 described.

[0073] Wireless communication system 200 can support communication between network entity 105-a and UE 115-a via unrestricted BWP 210. More specifically, network entity 105-a can send control information 205 indicating resource allocation information to UE 115-a. UE 115-a can use control information 205-a to determine the RIV to be included in the FDRA field used for unrestricted BWP 210. The FDRA field can be a DCI field associated with the FDRA of PDSCH or Physical Uplink Shared Channel (PUSCH) on the active BWP (e.g., uplink or downlink BWP). The size (e.g., bit width) of the FDRA field can depend on the bandwidth of the active BWP or baseline BWP (e.g., CORESET #0 or initial downlink BWP). The RIV in the FDRA field can represent a value specifying the PDSCH and / or PUSCH allocation in the DCI (e.g., uplink DCI or downlink DCI).

[0074] In some cases, network entity 105-a may send control information 205-a to UE 115-a indicating a CORESET#0 associated with SI acquisition. This CORESET#0 may be a CORESET with ID 0 and configured by the Master Information Block (MIB) of the CD-SSB. This CORESET#0 may be associated with SI acquisition (e.g., SIB1). In some instances, UE 115-a may be an eMBB UE or a RedCap UE in an idle (e.g., inactive) state. In at least these instances, this CORESET#0 may be the default initial downlink BWP.

[0075] In some cases, network entity 105-a may send control information 205-b to UE 115-a indicating an unrestricted BWP 210 configured with a non-zero CORESET (e.g., a CORESET different from CORESET #0). The bandwidth of the CORESET configured for the unrestricted BWP 210 may be different from the bandwidth of CORESET #0. In some instances, UE 115-a may be an eMBB UE in an RRC connected state. In these instances, RRC messages may configure the unrestricted BWP 210 (e.g., a dedicated downlink BWP). In some other instances, UE 115-a may be a RedCap or eRedCap UE in a connected state. In these instances, RRC messages may configure the unrestricted BWP 210 (e.g., a dedicated downlink BWP). Additionally or alternatively, UE 115-a may be a RedCap or eRedCap UE in an idle or inactive state. In these instances, the SI message for random access may be configured with an unrestricted BWP 210 (e.g., an initial downlink BWP). That is, the unrestricted BWP 210 may represent a BWP configured in at least one of the instances described above. However, the SI message and the RRC message may not contain CORESET #0 associated with SIB1 acquisition.

[0076] In some cases, network entity 105-a may send control information 205-c to UE 115-a. Control information 205-c may include a DCI (e.g., DCI 1_0) that carries PDSCH scheduling information. Control information 205-c may include fields such as FDRA and modulation and decoding scheme (MCS). Control information 205-c may indicate the bandwidth associated with the PDSCH and a first RB. The bandwidth associated with the PDSCH may be within the bandwidth of the unrestricted BWP 210. The first RB may be the lowest RB index of the physical downlink shared channel. Additionally or alternatively, the value of the first RB may be greater than or equal to the lowest RB index of the unrestricted BWP 210.

[0077] In some cases, UE 115-a can operate on a cell configured with CORESET #0 and an unrestricted BWP 210. Network entity 105-a can limit (e.g., constrain) the bandwidth of the unrestricted BWP 210. This network entity can configure the bandwidth of the unrestricted BWP 210 (e.g., via control information 205-b) to be lowered by the bandwidth of CORESET #0. In other words, the lowest RB index of CORESET #0 can be greater than or equal to the lowest RB index of the unrestricted BWP 210 (e.g., the first RB). Therefore, UE 115-a may not operate on unrestricted BWP 210s with a bandwidth smaller than that of CORESET #0.

[0078] Additionally or alternatively, UE 115-a may determine the RIV to be included in the FDMA field for the unrestricted BWP based on the fact that the unrestricted BWP 210 is configured with a CORESET different from that CORESET #0. Furthermore, UE 115-a may determine (e.g., calculate) the RIV using resource allocation information from control information 205-a, control information 205-b, control information 205-c, or any combination thereof. In some cases, UE 115-a and network entity 105-a may communicate via (e.g., across or through) the unrestricted BWP 210 based on the determined RIV. More specifically, UE 115-a and network entity 105-a may communicate via the unrestricted BWP 210 regardless of whether the bandwidth of CORESET #0 is the same as the bandwidth of the unrestricted BWP 210.

[0079] Figure 3 Examples of relative bandwidth comparison 300 associated with resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure are shown. In some examples, relative bandwidth comparison 300 may be implemented by or by aspects of wireless communication system 100 or wireless communication system 200.

[0080] The relative bandwidth comparison 300 may exemplify one or more RB index configurations. For example, the relative bandwidth comparison 300 may include corresponding RB index configurations for the unrestricted BWP 305, CORESET #0, and PDSCH 310. Although described as a particular RB index configuration for illustrative purposes, the corresponding RB index configuration for the unrestricted BWP 305, the CORESET #0, and the PDSCH 310 may be any number of RBs and may be in any order or configuration.

[0081] In some cases, the bandwidth of CORESET #0 can be greater than the bandwidth of the unrestricted BWP 305. For example, the bandwidth of CORESET #0 (e.g., the CORESET associated with SIB1 acquisition) can be... One RB, and can be equal to virtual bandwidth. For example, the bandwidth of CORESET #0 can span from RB index 320-a to RB index 320-e. The bandwidth of the unrestricted BWP 305 can span from RB index 320-a to RB index 320-d. That is, the bandwidth of CORESET #0 can span the bandwidth of the unrestricted BWP 305 and one or more virtual RBs 315. A virtual RB 315 may represent an index of a virtual RB that is not applicable to PDSCH scheduling (e.g., PDSCH 310 may not be scheduled within virtual RB 315).

[0082] In some cases, the bandwidth of this PDSCH can be within the bandwidth of the unrestricted BWP 305. For example, the bandwidth of PDSCH 310 can span from RB index 320-b to RB index 320-c. Network entities can limit the lowest RB index assigned to PDSCH 310 ( (e.g., RB index 320-b) and bandwidth ( (For example, the bandwidth from RB index 320-b to RB index 320-c). This network entity can... Configured to be greater than or equal to the lowest RB index configured for an unrestricted BWP 305 (e.g., RB index 320-a). Additionally, the network entity can... Configured to be greater than or equal to one, where This corresponds to the highest RB index configured for PDSCH 310 (e.g., RB index 320-c). RB index 320-c may be less than or equal to the minimum of the following: RB index 320-d (e.g., the highest RB index configured for the unrestricted BWP 305); or Therefore, the network entity can limit the number of PDSCH 310s associated with the DCI size aligned with that of CORESET #0. and .

[0083] In some cases, the UE can determine the RIV to be included in the FDRA field for the unrestricted BWP 305 based on the fact that the unrestricted BWP 305 is configured with a different CORESET than CORESET #0. The UE can then determine this virtual bandwidth. (For example, the bandwidth of CORESET #0) and the bandwidth of PDSCH. Then, the UE can determine (e.g., calculate) the RIV according to the formula illustrated in Equation 1 below.

[0084] (1)

[0085] Otherwise, if Then the UE can determine the RIV according to the formula illustrated in Equation 2 below.

[0086] (2)

[0087] The UE can use the determined RIV to fill (e.g., DCI 1_0) the FDRA field. The size of the FDRA field can be illustrated by Equation 3 below, where N is the number of RBs belonging to CORESET #0, and L represents the size of the FDRA bits.

[0088] (3)

[0089] In some cases, the UE may include (e.g., add) bit padding in the FDRA field. For example, virtual bandwidth. This can be equal to the bandwidth of an unrestricted BWP 305 (e.g., the number of RBs belonging to an unrestricted BWP 305). Network entities can limit... (For example, the lowest RB index assigned to PDSCH 310) and (For example, the bandwidth assigned to PDSCH 310). This network entity can... Configured to be greater than or equal to the lowest RB index configured for an unrestricted BWP 305. Additionally, the network entity can... Configured to be greater than or equal to one, where This corresponds to the highest RB index configured for PDSCH 310. The highest RB index configured for PDSCH 310 can be less than or equal to... Then, the UE can calculate the RIV according to equations 1 and 2 above. Therefore, the UE can use the virtual bandwidth (e.g., the bandwidth of the unrestricted BWP). and To determine the RIV.

[0090] In some cases, the UE can calculate one or more bit widths. For example, the UE can calculate the first bit width (e.g., L) according to Equation 3 above. Furthermore, the UE can calculate a second bit width (e.g., L) representing the bit width of the determined (e.g., calculated) RIV. The UE can compare the number of bits in the first width with the number of bits in the second width. If the first width is equal to the second width, the UE can include the determined RIV value in the FDRA field. Alternatively, if the first width is greater than the second width, the UE can include the determined RIV value in the FDRA field and pad the FDRA bits. The padded bits can be equal to the difference between the first width and the second width (e.g., L minus L). (bits). The UE may include the filled bits at the beginning or end of the FDRA field. That is, the UE may include the filled bits before or after the RIV in the FDRA field.

[0091] Figure 4 Examples of relative bandwidth comparison 400 associated with resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure are shown. In some examples, relative bandwidth comparison 400 may be implemented by or by aspects of wireless communication system 100 or wireless communication system 200.

[0092] The relative bandwidth comparison 400 may exemplify one or more RB index configurations. For example, the relative bandwidth comparison 400 may include corresponding RB index configurations for the unrestricted BWP 405, CORESET #0, and PDSCH 410. Although described as a particular RB index configuration for illustrative purposes, the corresponding RB index configuration for the unrestricted BWP 405, the CORESET #0, and the PDSCH 410 may be any number of RBs in any order or configuration.

[0093] In some cases, the bandwidth of CORESET #0 may be less than the bandwidth of the unrestricted BWP 405. For example, the bandwidth of CORESET #0 (e.g., the CORESET associated with SIB1 acquisition) may be... One RB, and can be equal to virtual bandwidth. For example, the bandwidth of CORESET #0 can span from RB index 420-a to RB index 420-d. The bandwidth of the unrestricted BWP405 can span from RB index 320-a to RB index 420-e. That is, the bandwidth of CORESET #0 can span the bandwidth of the unrestricted BWP 305.

[0094] In some cases, the bandwidth of PDSCH 410 can be within the bandwidth of the unrestricted BWP 405. For example, the bandwidth of PDSCH 410 can span from RB index 420-b to RB index 420-c. Network entities can limit the lowest RB index assigned to PDSCH 310 (…). (e.g., RB index 420-b) and bandwidth ( (For example, the bandwidth from RB index 420-b to RB index 420-c). This network entity can... Configured to be greater than or equal to the lowest RB index configured for an unrestricted BWP 405 (e.g., RB index 420-a). Additionally, the network entity can... Configured to be greater than or equal to one, where This corresponds to the highest RB index configured for PDSCH 410 (e.g., RB index 420-c). RB index 420-c can be less than or equal to... Therefore, the network entity can limit the number of PDSCH 410s associated with the DCI size aligned with that of CORESET #0. and .

[0095] In some cases, the UE can determine the RIV to be included in the FDRA field for the unrestricted BWP 405 based on the fact that the unrestricted BWP 405 is configured with a different CORESET than CORESET #0. The UE can then determine this virtual bandwidth. (For example, the bandwidth of CORESET #0) and the bandwidth of PDSCH 410. Then, the UE can determine (e.g., calculate) the RIV according to the formula illustrated in Equation 4 below.

[0096] (4)

[0097] Otherwise, if Then the UE can determine (e.g., calculate) the RIV according to the formula illustrated in Equation 5 below.

[0098] (5)

[0099] The UE can use the calculated RIV to populate (e.g., DCI 1_0) the FDRA field.

[0100] The size of the FDRA field can be illustrated by Equation 6 below, where N is the number of RBs belonging to CORESET #0, and L represents the size of the FDRA bits.

[0101] (6)

[0102] In some cases, the UE may truncate (e.g., shorten) the RIV in the FDRA field. For example, virtual bandwidth. This can be equal to the bandwidth of an unrestricted BWP 405 (e.g., the number of RBs belonging to an unrestricted BWP 405). Network entities can limit... (For example, the lowest RB index assigned to PDSCH 410) and (For example, the bandwidth assigned to PDSCH 410). This network entity can... Configured to be greater than or equal to the lowest RB index configured for an unrestricted BWP 405. Additionally, the network entity can... Configured to be greater than or equal to one, where This corresponds to the highest RB index configured for PDSCH 410. The highest RB index configured for PDSCH 410 can be less than or equal to... Then, the UE can calculate the RIV according to equations 4 and 5 above. Therefore, the UE can use the virtual bandwidth (e.g., the bandwidth of the unrestricted BWP). and To determine the RIV.

[0103] In some cases, the UE can calculate one or more bit widths. For example, the UE can calculate the first bit width (e.g., L) according to Equation 6 above. Furthermore, the UE can calculate a second bit width (e.g., L) representing the bit width of the determined (e.g., calculated) RIV. The UE can compare the number of bits in the first bit width with the number of bits in the second bit width. If the first bit width is equal to the second bit width, the UE can include the determined RIV value in the FDRA field. Alternatively, if the first bit width is less than the first bit width, the UE can include a truncated value of the RIV value (e.g., a truncated RIV) in the FDRA field. For example, the truncated RIV can be equal to the difference between the second bit width and the first bit width (e.g., L). (Subtract L bits). The UE can truncate the most significant bit (MSB) (e.g., the bit at the beginning of the determined RIV) or the least significant bit (LSB) (e.g., the bit at the end of the determined RIV) of the binary array. In other words, the UE can truncate the MSB and / or LSB that may not map to the FDRA field (e.g., the determined RIV).

[0104] In some cases (e.g., DCI 1_0 in CSS), the size of the FDRA field can be a fixed bit width associated with CORESET #0, regardless of the bit width of the unrestricted BWP 405. A fixed FDRA bit width simplifies UE procedures for DCI decoding, RIV interpretation, BWP handover, or any combination thereof. However, this fixed FDRA bit width may result in a loss of scheduling flexibility, frequency diversity gain, and throughput. In some other cases, the FDRA field can have a variable bit width (e.g., a bit width associated with the bandwidth of the active unrestricted BWP 405). A variable FDRA bit width improves scheduling flexibility and throughput while achieving higher frequency diversity gain. However, this variable FDRA bit width may increase the complexity of DCI decoding, RIV interpretation, and BWP handover for the UE.

[0105] In some cases, the UE may determine the size of the FDRA field transmitted in the unrestricted BWP 405 and the RIV transmitted in that unrestricted BWP based on the size of the unrestricted BWP 405 (e.g., the actual size of the unrestricted downlink BWP 405) and regardless of the size of the CORESET #0. For example, the size of the FDRA field in the DCI (e.g., DCI 1_0) is illustrated by Equation 7 below, where This represents the size of the unrestricted BWP 405 (e.g., the number of RBs), and L represents the size of the FDRA field: (7) In some cases, virtual bandwidth This is equivalent to the bandwidth of an unrestricted BWP 405. Network entities can limit... (For example, the lowest RB index assigned to PDSCH 410) and (For example, the bandwidth assigned to PDSCH 410). This network entity can... Configured to be greater than or equal to the lowest RB index configured for an unrestricted BWP 405. Additionally, the network entity can... Configured to be greater than or equal to one, where This corresponds to the highest RB index configured for PDSCH 410. The highest RB index configured for this PDSCH can be less than or equal to... Therefore, the network entity can be limited according to the size of the unrestricted BWP 405. and .

[0106] In some cases, the UE can determine the RIV to be included in the FDRA field for the unrestricted downlink BWP 405 based on the actual size of the unrestricted downlink BWP 405. The UE can determine this virtual bandwidth. (e.g., the bandwidth of the unrestricted BWP405) and the bandwidth of the PDSCH 410 (e.g., Then, the UE can determine (e.g., calculate) the RIV according to the formula illustrated in Equation 8 below.

[0107] (8)

[0108] Otherwise, if Then the UE can determine (e.g., calculate) the RIV according to the formula illustrated in Equation 9 below.

[0109] (9)

[0110] The UE can use the calculated RIV from Equation 8 or 9 to populate (e.g., DCI 1_0) the FDRA field.

[0111] In some cases, the UE can use RB packets to determine the RIV to be included in the FDRA field. For example, when the bandwidth of the unrestricted BWP 405 is greater than the bandwidth of the baseline BWP, the UE can use RB packets to determine the RIV to be included in the FDRA field. The baseline BWP can be CORESET #0 or a different narrowband downlink BWP with a non-zero CORESET.

[0112] In some cases, the UE can determine (e.g., calculate) the RB group according to Equation 10 as illustrated below. K Size.

[0113] (10)

[0114] In equation 10, This can represent the bandwidth of the unrestricted BWP 405 activity, while This can represent the bandwidth of the baseline BWP (e.g., the initial downlink BWP with a non-zero CORESET).

[0115] This network entity can Configured in { 0, K, 2K, ..., ( 1)K Within the range of}, and defined according to Equation 11 as illustrated below. .

[0116] (11)

[0117] Alternatively, the network entity can be configured based on consecutively allocated RB groups. For example, the network entity can Configured in { K, 2K, ..., ( )K Within the range of}, and defined according to Equation 12 as illustrated below. .

[0118] (11) Can be less than or equal to .

[0119] In some cases, the UE can then determine (e.g., calculate) the RIV according to the formula illustrated in Equation 12 below.

[0120] (12)

[0121] Otherwise, if Then the UE can determine the RIV according to the formula illustrated in Equation 13 below.

[0122] (13)

[0123] The UE can use the calculated RIV from Equation 12 or 13 to populate (e.g., DCI 1_0) the FDRA field. Therefore, the UE can use RB group information (e.g., the size of the RB group) to determine the RIV to be included in the FDRA field. The size of the FDRA field transmitted in the active unrestricted BWP 405 can be consistent with the size of the FDRA field of the DCI transmitted in the baseline BWP.

[0124] Figure 5An example of a process flow 500 supporting resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure is shown. Process flow 500 may implement, or be implemented by, aspects of wireless communication system 100, wireless communication system 200, relative bandwidth comparison 300, or relative bandwidth comparison 400. Process flow 500 may include UE 115-b and network entity 105-b, which may be examples of UE 115 and network entity 105 as described herein. In the following description of process flow 500, operations between UE 115-b and network entity 105-b may be transmitted in a different order than the example order shown, or operations performed by UE 115-b and network entity 105-b may be performed in a different order or at different times. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0125] At 505, UE 115-b may receive from network entity 105-b a first control information indicating that a first CORESET associated with SI is acquired. The first CORESET may be CORESET #0 with a first bandwidth.

[0126] At 510, UE 115-b may receive second control information from network entity 105-b indicating a first BWP (e.g., an unrestricted BWP). Network entity 105-b may configure the unrestricted BWP with a second CORESET different from the first CORESET (e.g., the CORESET configured for the unrestricted BWP is not CORESET #0). The unrestricted BWP may have a second bandwidth. The second bandwidth may be equal to, greater than, or less than the first bandwidth.

[0127] At point 515, UE 115-b can receive third control information for scheduling the PDSCH from network entity 105-b. Network entity 105-b can configure the PDSCH with a third bandwidth and a first RB. The third bandwidth can be within the second bandwidth. The first RB can be the lowest RB index of the PDSCH, and the value of the first RB can be greater than or equal to the lowest RB of the unrestricted BWP. That is, the PDSCH may be subject to the lower bound constraint of the unrestricted BWP.

[0128] At 520, UE 115-b may determine the RIV to be included in the FDRA field for the unrestricted BWP based on the fact that the unrestricted BWP is configured with a non-zero CORESET. The UE may determine (e.g., calculate) the RIV based on information corresponding to the CORESET #0, the unrestricted BWP, the PDSCH, or any combination thereof.

[0129] At 525, UE 115-b and network entity 105-b can communicate via the unrestricted BWP based on the RIV. That is, UE 115-b and network entity 105-b can use the RIV included in the FDRA field of the unrestricted BWP to send messages to each other (e.g., receive messages from each other) via the unrestricted BWP.

[0130] Figure 6 Figure 600 illustrates a device 605 supporting resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure. Device 605 may be an example of aspects of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0131] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to resource allocation instructions in an unrestricted BWP). The information may be transmitted to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0132] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to resource allocation indications in an unrestricted BWP). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0133] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of resource allocation instructions in an unrestricted BWP as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0134] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0135] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0136] In some examples, the communication manager 620 may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0137] Communication manager 620 may support wireless communication according to examples disclosed herein. For example, communication manager 620 may be capable of, configured to, or operable to support components for receiving first control information indicating a first core set associated with SI acquisition, the first core set having a first bandwidth. Communication manager 620 may be capable of, configured to, or operable to support components for receiving second control information indicating a first base plate (BWP) configured with a second core set different from the first core set, wherein the first BWP has a second bandwidth. Communication manager 620 may be capable of, configured to, or operable to support components for determining, at least in part, the RIV to be included in the FDRA field for the first BWP based on the fact that the first BWP is configured with a core set different from the first core set. Communication manager 620 may be capable of, configured to, or operable to support components for communicating via the first BWP based on the RIV.

[0138] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., at least one processor that controls or otherwise couples to receiver 610, transmitter 615, communication manager 620, or a combination thereof) can support techniques for reducing processing and utilizing communication resources more efficiently.

[0139] Figure 7 Figure 700 illustrates a device 705 supporting resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720), may include at least one processor that can be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0140] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to resource allocation instructions in an unrestricted BWP). The information may be transmitted to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0141] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to resource allocation indications in an unrestricted BWP). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0142] Device 705 or its various components may be examples of various aspects of components used to perform resource allocation instructions in an unrestricted BWP as described herein. For example, communication manager 720 may include CORESET component 725, BWP component 730, RIV component 735, communication component 740, or any combination thereof. Communication manager 720 may be examples of various aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0143] Communication manager 720 can support wireless communication according to examples disclosed herein. CORESET component 725 is capable of, configured to, or operable to support means for receiving first control information indicating a first CORESET associated with SI acquisition, the first CORESET having a first bandwidth. BWP component 730 is capable of, configured to, or operable to support means for receiving second control information indicating a first BWP configured with a second CORESET different from the first CORESET, wherein the first BWP has a second bandwidth. RIV component 735 is capable of, configured to, or operable to support means for determining, at least in part, a RIV to be included in the FDRA field of the first BWP based on the fact that the first BWP is configured with a CORESET different from the first CORESET. Communication component 740 is capable of, configured to, or operable to support means for communicating via the first BWP based on the RIV.

[0144] Figure 8Figure 800 illustrates a communication manager 820 supporting resource allocation instructions in an unrestricted BWP according to one or more aspects of this disclosure. The communication manager 820 may be an example of aspects of the communication manager 620, communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of resource allocation instructions in an unrestricted BWP as described herein. For example, the communication manager 820 may include a CORESET component 825, a BWP component 830, a RIV component 835, a communication component 840, a physical downlink shared channel component 845, a bit-width component 850, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0145] Communication manager 820 may support wireless communication according to examples disclosed herein. CORESET component 825 is capable of, configured to, or operable to support means for receiving first control information indicating a first CORESET associated with SI acquisition, the first CORESET having a first bandwidth. BWP component 830 is capable of, configured to, or operable to support means for receiving second control information indicating a first BWP configured with a second CORESET different from the first CORESET, wherein the first BWP has a second bandwidth. RIV component 835 is capable of, configured to, or operable to support means for determining, at least in part, a RIV to be included in the FDRA field of the first BWP based on the fact that the first BWP is configured with a CORESET different from the first CORESET. Communication component 840 is capable of, configured to, or operable to support means for communicating via the first BWP based on the RIV.

[0146] In some examples, the physical downlink shared channel component 845 is capable of, configured to, or able to operate to support components for receiving third control information for scheduling a physical downlink shared channel associated with a third bandwidth and a first RB, wherein the third bandwidth is within the second bandwidth, and wherein the first RB is the lowest RB index of the physical downlink shared channel, and the value of the first RB is greater than or equal to the lowest RB index of the first BWP.

[0147] In some examples, the first bandwidth is greater than the second bandwidth.

[0148] In some examples, to support the determination of the RIV, the RIV component 835 is capable of, configured to, or operable to support components for determining the virtual bandwidth and the third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth is equal to the first bandwidth, and the highest RB index of the physical downlink shared channel is equal to or less than the minimum of the following: the highest RB index of the first BWP; or the difference between the virtual bandwidth and the value of the first RB, wherein the RIV is determined using the virtual bandwidth, the value of the first RB, and the third bandwidth.

[0149] In some examples, to support the determination of the RIV, the RIV component 835 is capable of, configured to, or able to operate to support components for determining the virtual bandwidth and the third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth is equal to the second bandwidth, and the highest RB index of the physical downlink shared channel is equal to or less than the difference between the virtual bandwidth and the value of the first RB, and wherein the RIV is determined using the virtual bandwidth, the value of the first RB, and the third bandwidth.

[0150] In some examples, to support the determination of the RIV, the bit width component 850 is capable, configured, or operable to support components for calculating the first bit width based on the number of RBs in the first CORESET, wherein the second bit width is the bit width of the RIV. In some examples, to support the determination of the RIV, the RIV component 835 is capable, configured, or operable to support components for performing the following operations: including the RIV in the FDRA field when the second bit width is equal to the first bit width, or including the RIV and bit padding in the FDRA field when the second bit width is less than the first bit width, wherein the bit padding is equal to the difference between the first bit width and the second bit width.

[0151] In some examples, the second bandwidth is greater than the first bandwidth. In some examples, to support the determination of the RIV, the RIV component 835 is capable of, configured to, or operable to support components for determining the virtual bandwidth and the third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth is equal to the first bandwidth, and the highest RB index of the physical downlink shared channel is equal to or less than the difference between the virtual bandwidth and the value of the first RB, and wherein the RIV is determined using the virtual bandwidth, the value of the first RB, and the third bandwidth.

[0152] In some examples, to support the determination of the RIV, the RIV component 835 is capable of, configured to, or able to operate to support components for determining the virtual bandwidth and the third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth is equal to the second bandwidth, and the highest RB index of the physical downlink shared channel is equal to or less than the difference between the virtual bandwidth and the value of the first RB, and wherein the RIV is determined using the virtual bandwidth, the value of the first RB, and the third bandwidth.

[0153] In some examples, to support the determination of the RIV, the bit width component 850 is capable of, configured to, or operable to support components for calculating the first bit width based on the first CORESET, wherein the second bit width is the bit width of the RIV. In some examples, to support the determination of the RIV, the RIV component 835 is capable of, configured to, or operable to support components for performing the following operations: including the RIV in the FDRA field when the second bit width is equal to the first bit width, or including the RIV and a truncated RIV in the FDRA field when the second bit width is greater than the first bit width, wherein the truncated RIV is equal to the difference between the second bit width and the first bit width.

[0154] In some examples, to support the determination of the RIV, the RIV component 835 is capable of, configured to, or able to operate to support components for determining the virtual bandwidth and the third bandwidth of the physical downlink shared channel, wherein the virtual bandwidth is equal to the second bandwidth, and the highest RB index of the physical downlink shared channel is equal to or less than the difference between the virtual bandwidth and the value of the first RB, and wherein the RIV is determined using the virtual bandwidth, the size of the first BWP, the value of the first RB, and the third bandwidth.

[0155] In some examples, in order to support the determination of the RIV, the RIV component 835 is capable of, can be configured to, or can operate to support components for determining the size of the RB group based on the second bandwidth and the baseline bandwidth, wherein the baseline bandwidth is equal to the first bandwidth or the fourth bandwidth associated with the second BWP, and wherein the RIV is determined using at least the size of the RB group.

[0156] In some examples, the CORESET identifier of the first CORESET is zero. In some examples, in order to support receiving the second control information indicating the first BWP, the BWP component 830 is capable, configured, or operable to support components for receiving the second control information via RRC messages or SI messages, wherein the first BWP is an unrestricted downlink BWP not associated with the first CORESET.

[0157] In some examples, the unrestricted downlink BWP is a dedicated downlink BWP configured by the RRC message for an eMBB UE in a radio resource control connected state. In other examples, the unrestricted downlink BWP is a dedicated downlink BWP configured by the RRC message for a RedCap or eRedCap UE in a connected state.

[0158] In some examples, the unrestricted downlink BWP is the initial downlink BWP configured by the SI message for random access by a RedCap or eRedCap UE in an idle or inactive state. In some examples, the lowest RB index of the first BWP is greater than or equal to the RB index of the first CORESET.

[0159] Figure 9 A diagram of a system 900 including device 905 supporting resource allocation instructions in an unrestricted BWP, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or a component including such devices. Device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 945).

[0160] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ®Or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0161] In some cases, device 905 may include a single antenna 925. However, in other cases, device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0162] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable, computer-executable code 935, including instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium, such as system memory, or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 930 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0163] At least one processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., supporting various functions or tasks indicated by resource allocation in an unrestricted BWP). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, wherein at least one processor 940 and at least one memory 930 are configured to perform the various functions described herein. In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 940 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 940) and memory circuitry (which may include at least one memory 930)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 930 or otherwise.

[0164] Communication manager 920 may support wireless communication according to examples disclosed herein. For example, communication manager 920 may be capable of, configured to, or operable to support components for receiving first control information indicating a first core set associated with SI acquisition, the first core set having a first bandwidth. Communication manager 920 may be capable of, configured to, or operable to support components for receiving second control information indicating a first base plate (BWP) configured with a second core set different from the first core set, wherein the first BWP has a second bandwidth. Communication manager 920 may be capable of, configured to, or operable to support components for determining, at least in part, a RIV to be included in the FDRA field of the first BWP based on the fact that the first BWP is configured with a core set different from the first core set. Communication manager 920 may be capable of, configured to, or operable to support components for communicating via the first BWP based on the RIV.

[0165] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support techniques for improving and reducing the user experience associated with processing, utilizing communication resources more efficiently, improving coordination between devices, and improving the utilization of processing power.

[0166] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with transceiver 915, one or more antennas 925, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported by or performed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of resource allocation indications as described herein in an unrestricted BWP, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0167] Figure 10 A flowchart illustrating a method 1000 for supporting resource allocation instructions in an unrestricted BWP according to various aspects of this disclosure is shown. The operation of method 1000 can be implemented by a UE or its components as described herein. For example, the operation of method 1000 can be implemented by, as referenced... Figures 1 to 9 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0168] At 1005, the method may include: receiving first control information indicating a first CORESET associated with SI acquisition, the first CORESET having a first bandwidth. Operation of block 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1005 may be provided by reference to... Figure 8 The described CORESET component 825 is executed.

[0169] At 1010, the method may include: receiving second control information indicating a first BWP, the first BWP being configured with a second CORESET different from the first CORESET, wherein the first BWP has a second bandwidth. Operation of block 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1010 may be provided by reference to [reference needed]. Figure 8 The described BWP component 830 is executed.

[0170] At 1015, the method may include: determining, at least in part, the RIV to be included in the FDRA field for the first BWP based on the fact that the first BWP is configured with a CORESET different from the first CORESET. The operation of box 1015 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1015 may be derived from references... Figure 8 The described RIV component 835 is executed.

[0171] At 1020, the method may include: communicating via the first BWP based on the RIV. The operation of block 1020 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1020 may be provided by reference to [reference needed]. Figure 8 The described communication component 840 is executed.

[0172] Figure 11 A flowchart illustrating a method 1100 for supporting resource allocation instructions in an unrestricted BWP according to various aspects of this disclosure is shown. Operation of method 1100 may be implemented by a UE or its components as described herein. For example, operation of method 1100 may be implemented by, as referenced... Figures 1 to 9 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0173] At 1105, the method may include: receiving first control information indicating an association with a first CORESET, the first CORESET having a first bandwidth. Operation of block 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1105 may be provided by reference to... Figure 8 The described CORESET component 825 is executed.

[0174] At 1110, the method may include: receiving second control information indicating a first BWP, the first BWP being configured with a second CORESET different from the first CORESET, wherein the first BWP has a second bandwidth. Operation of block 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1110 may be provided by reference to [reference needed]. Figure 8 The described BWP component 830 is executed.

[0175] At 1115, the method may include: receiving third control information for scheduling a physical downlink shared channel associated with a third bandwidth and a first RB, wherein the third bandwidth is within the second bandwidth, and wherein the first RB is the lowest RB index of the physical downlink shared channel, and the value of the first RB is greater than or equal to the lowest RB index of the first BWP. The operation of block 1115 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1115 may be derived from references... Figure 8 The physical downlink shared channel component 845 described is implemented.

[0176] At 1120, the method may include: determining, at least in part, the RIV to be included in the FDRA field for the first BWP based on the fact that the first BWP is configured with a CORESET different from the first CORESET. The operation of box 1120 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1120 may be derived from references... Figure 8 The described RIV component 835 is executed.

[0177] At 1125, the method may include: communicating via the first BWP based on the RIV. The operation of block 1125 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1125 may be derived from references... Figure 8 The described communication component 840 is executed.

[0178] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving first control information indicating a first CORESET associated with system information acquisition, the first CORESET having a first bandwidth; receiving second control information indicating a first BWP, the first BWP being configured with a second CORESET different from the first CORESET, wherein the first BWP has a second bandwidth; determining a resource indicator value to be included in a frequency domain resource allocation field for the first BWP based at least in part on the first BWP being configured with a CORESET different from the first CORESET; and communicating via the first BWP at least in part based on the resource indicator value.

[0179] Aspect 2: According to the method of aspect 1, the method further includes: receiving third control information for scheduling a physical downlink shared channel associated with a third bandwidth and a first resource block, wherein the third bandwidth is located within the second bandwidth, and wherein the first resource block is the lowest resource block index of the physical downlink shared channel, and the value of the first resource block is greater than or equal to the lowest resource block index of the first BWP.

[0180] Aspect 3: The method according to aspect 2, wherein the first bandwidth is greater than the second bandwidth.

[0181] Aspect 4: According to the method of aspect 3, determining the resource indicator value further includes: determining the virtual bandwidth of the physical downlink shared channel and the third bandwidth, wherein the virtual bandwidth is equal to the first bandwidth, and the highest resource block index of the physical downlink shared channel is equal to or less than the minimum of the following: the highest resource block index of the first BWP; or the difference between the virtual bandwidth and the value of the first resource block, wherein the resource indicator value is determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

[0182] Aspect 5: According to the method of aspect 3, determining the resource indicator value further includes: determining the virtual bandwidth of the physical downlink shared channel and the third bandwidth, wherein the virtual bandwidth is equal to the second bandwidth, and the highest resource block index of the physical downlink shared channel is equal to or less than the difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value is determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

[0183] Aspect 6: According to the method of aspect 5, determining the resource indicator value further includes: calculating a first bit width based at least in part on the number of resource blocks of the first CORESET, wherein the second bit width is the bit width of the resource indicator value; and including the resource indicator value in the frequency domain resource allocation field when the second bit width is equal to the first bit width, or including the resource indicator value and bit padding in the frequency domain resource allocation field when the second bit width is less than the first bit width, wherein the bit padding is equal to the difference between the first bit width and the second bit width.

[0184] Aspect 7: The method according to aspect 2, wherein the second bandwidth is greater than the first bandwidth.

[0185] Aspect 8: According to the method of aspect 7, determining the resource indicator value further includes: determining the virtual bandwidth of the physical downlink shared channel and the third bandwidth, wherein the virtual bandwidth is equal to the first bandwidth, and the highest resource block index of the physical downlink shared channel is equal to or less than the difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value is determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

[0186] Aspect 9: According to the method of aspect 7, determining the resource indicator value further includes: determining the virtual bandwidth of the physical downlink shared channel and the third bandwidth, wherein the virtual bandwidth is equal to the second bandwidth, and the highest resource block index of the physical downlink shared channel is equal to or less than the difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value is determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

[0187] Aspect 10: According to the method of aspect 9, determining the resource indicator value further includes: calculating a first bit width based at least in part on the first CORESET, wherein the second bit width is the bit width of the resource indicator value; and including the resource indicator value in the frequency domain resource allocation field when the second bit width is equal to the first bit width, or including the resource indicator value and a truncated resource indicator value in the frequency domain resource allocation field when the second bit width is greater than the first bit width, wherein the truncated resource indicator value is equal to the difference between the second bit width and the first bit width.

[0188] Aspect 11: According to the method of aspect 2, determining the resource indicator value further includes: determining the virtual bandwidth of the physical downlink shared channel and the third bandwidth, wherein the virtual bandwidth is equal to the second bandwidth, and the highest resource block index of the physical downlink shared channel is equal to or less than the difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value is determined using the virtual bandwidth, the size of the first BWP, the value of the first resource block, and the third bandwidth.

[0189] Aspect 12: The method according to aspects 2 and 7, wherein determining the resource indicator value further comprises: determining the size of the resource block group based at least in part on the second bandwidth and the baseline bandwidth, wherein the baseline bandwidth is equal to the first bandwidth or a fourth bandwidth associated with the second BWP, and wherein the resource indicator value is determined using at least the size of the resource block group.

[0190] Aspect 13: The method according to any one of aspects 1 to 12, wherein the CORESET identifier of the first CORESET is zero.

[0191] Aspect 14: According to the method of aspect 13, receiving the second control information indicating the first BWP further includes: receiving the second control information via a radio resource control message or a system information message, wherein the first BWP is an unrestricted downlink BWP not associated with the first CORESET.

[0192] Aspect 15: According to the method of aspect 14, the unrestricted downlink BWP is a dedicated downlink BWP configured by the radio resource control message for an eMBB UE in a radio resource control connection state.

[0193] Aspect 16: The method according to any one of Aspects 14 to 15, wherein the unrestricted downlink BWP is a dedicated downlink BWP configured by the radio resource control message for a connected RedCap or eRedCap UE.

[0194] Aspect 17: The method according to any one of Aspects 14 to 16, wherein the unrestricted downlink BWP is an initial downlink BWP configured by the system information message for random access by a RedCap or eRedCap UE in an idle or inactive state.

[0195] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the lowest resource block index of the first BWP is greater than or equal to the resource block index of the first CORESET.

[0196] Aspect 19: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 18.

[0197] Aspect 20: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 1 to 18.

[0198] Aspect 21: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 18.

[0199] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0200] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0201] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0202] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0203] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or code on or transmitted via a computer-readable medium. Other examples and specific implementations fall within the scope and spirit of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including portions distributed such that the functions are implemented at different physical locations. As used herein (including in the claims), the term “and / or” when used in a list of two or more items means that any one of the listed items may be employed individually, or any combination of two or more of the listed items may be employed. For example, if a composition is described as comprising components A, B, and / or C, the composition may comprise A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Additionally, as used herein (including in the claims), the word “or” used in a list of items (e.g., a list of items accompanied by phrases such as “at least one of” or “one or more of”) indicates an inclusive list such that a list of at least one of, for example, A, B or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0204] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0205] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0206] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0207] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0208] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0209] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown graphically to avoid obscuring the concept of the described examples.

[0210] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and capable of operating, alone or in combination, to execute the code to cause the UE to: receive first control information indicating a first control resource set associated with system information acquisition, the first control resource set having a first bandwidth; receive second control information indicating a first bandwidth part, the first bandwidth part configured with a second control resource set different from the first control resource set, wherein the first bandwidth part has a second bandwidth; determine, based at least in part on the first bandwidth part being configured with a control resource set different from the first control resource set, a resource indicator value to include in a frequency domain resource allocation field for the first bandwidth part; and communicate, based at least in part on the resource indicator value, via the first bandwidth part.

2. The UE of claim 1, wherein a control resource set identification of the first control resource set is zero. To receive the second control information indicating the first bandwidth part, the one or more processors are further capable of operating, alone or in combination, to execute the code to cause the UE to:

3. The UE of claim 2, wherein, receive the second control information by a radio resource control message or a system information message, wherein the first bandwidth part is a non-restricted downlink bandwidth part not associated with the first control resource set.

4. The UE of claim 3, wherein the non-restricted downlink bandwidth part is a dedicated downlink bandwidth part configured for an enhanced mobile broadband (eMBB) UE in a radio resource control connected state by the radio resource control message.

5. The UE of claim 3, wherein the non-restricted downlink bandwidth part is a dedicated downlink bandwidth part configured for a reduced capability (RedCap) or enhanced RedCap (eRedCap) UE in a connected state by the radio resource control message.

6. The UE of claim 3, wherein the non-restricted downlink bandwidth part is an initial downlink bandwidth part configured for a reduced capability (RedCap) or enhanced RedCap (eRedCap) UE in an idle or inactive state by the system information message for random access.

7. The UE of claim 1, wherein the one or more processors are further capable of operating, alone or in combination, to execute the code to cause the UE to: receive third control information scheduling a physical downlink shared channel associated with a third bandwidth and a first resource block, wherein the third bandwidth is within the second bandwidth, and wherein the first resource block is a lowest resource block index of the physical downlink shared channel, and a value of the first resource block is greater than or equal to a lowest resource block index of the first bandwidth part. ​ 8. The UE of claim 7, wherein, To determine the resource indicator value, the one or more processors, alone or in combination, can be further operable to execute the code to cause the UE to: determine a size of a resource block group based at least in part on the second bandwidth and a baseline bandwidth, wherein the baseline bandwidth is equal to the first bandwidth or a fourth bandwidth associated with the second bandwidth part, and wherein the resource indicator value is determined using at least the size of the resource block group.

9. The UE of claim 7, wherein, To determine the resource indicator value, the one or more processors, alone or in combination, can be further operable to execute the code to cause the UE to: determine a virtual bandwidth of the physical downlink shared channel and the third bandwidth, wherein the virtual bandwidth is equal to the second bandwidth, and a highest resource block index of the physical downlink shared channel is equal to or less than a difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value is determined using the virtual bandwidth, a size of the first bandwidth part, the value of the first resource block, and the third bandwidth.

10. The UE of claim 7, wherein the first bandwidth is greater than the second bandwidth.

11. The UE of claim 10, wherein, To determine the resource indicator value, the one or more processors, alone or in combination, can be further operable to execute the code to cause the UE to: determine a virtual bandwidth of the physical downlink shared channel and the third bandwidth, wherein the virtual bandwidth is equal to the first bandwidth, and a highest resource block index of the physical downlink shared channel is equal to or less than a minimum of: a highest resource block index of the first bandwidth part; or a difference between the virtual bandwidth and the value of the first resource block, wherein the resource indicator value is determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

12. The UE of claim 10, wherein, To determine the resource indicator value, the one or more processors, alone or in combination, can be further operable to execute the code to cause the UE to: determine a virtual bandwidth of the physical downlink shared channel and the third bandwidth, wherein the virtual bandwidth is equal to the second bandwidth, and a highest resource block index of the physical downlink shared channel is equal to or less than a difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value is determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

13. The UE of claim 12, wherein, To determine the resource indicator value, the one or more processors, alone or in combination, can be further operable to execute the code to cause the UE to: determine a virtual bandwidth of the physical downlink shared channel and the third bandwidth, wherein the virtual bandwidth is equal to the second bandwidth, and a highest resource block index of the physical downlink shared channel is equal to or less than a difference between the virtual bandwidth and the value of the first resource block, and wherein the resource indicator value is determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth. To determine the resource indicator value, the one or more processors, alone or in combination, can be further operable to execute the code to cause the UE to: calculate a first bit width based at least in part on a number of resource blocks of the first control resource set, wherein a second bit width is a bit width of the resource indicator value; and In a case that the second bit width is equal to the first bit width, including the resource indicator value in the frequency domain resource allocation field, or in a case that the second bit width is less than the first bit width, including the resource indicator value and bit padding in the frequency domain resource allocation field, where the bit padding is equal to a difference between the first bit width and the second bit width.

14. The UE of claim 7, wherein the second bandwidth is greater than the first bandwidth.

15. The UE of claim 14, wherein, To determine the resource indicator value, the one or more processors can individually or collectively further operate to execute the code to cause the UE to: determine a virtual bandwidth of the physical downlink shared channel and the third bandwidth, where the virtual bandwidth is equal to the first bandwidth, and a highest resource block index of the physical downlink shared channel is equal to or less than a difference between the virtual bandwidth and the value of the first resource block, and where the resource indicator value is determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

16. The UE of claim 14, wherein, To determine the resource indicator value, the one or more processors can individually or collectively further operate to execute the code to cause the UE to: determine a virtual bandwidth of the physical downlink shared channel and the third bandwidth, where the virtual bandwidth is equal to the second bandwidth, and a highest resource block index of the physical downlink shared channel is equal to or less than a difference between the virtual bandwidth and the value of the first resource block, and where the resource indicator value is determined using the virtual bandwidth, the value of the first resource block, and the third bandwidth.

17. The UE of claim 16, wherein, To determine the resource indicator value, the one or more processors can individually or collectively further operate to execute the code to cause the UE to: calculate a first bit width based at least in part on the first control resource set, where a second bit width is a bit width of the resource indicator value; and In a case that the second bit width is equal to the first bit width, including the resource indicator value in the frequency domain resource allocation field, or in a case that the second bit width is greater than the first bit width, including the resource indicator value and a truncated resource indicator value in the frequency domain resource allocation field, where the truncated resource indicator value is equal to a difference between the second bit width and the first bit width.

18. The UE of claim 1, wherein a lowest resource block index of the first bandwidth part is greater than or equal to a resource block index of the first control resource set.

19. A method for wireless communication at a user equipment (UE), the method comprising: receiving first control information indicating a first control resource set associated with system information acquisition, the first control resource set having a first bandwidth; receiving second control information indicating a first bandwidth part, the first bandwidth part being configured with a second control resource set different from the first control resource set, wherein the first bandwidth part has a second bandwidth; determining, based at least in part on the first bandwidth part being configured with a different control resource set than the first control resource set, a resource indicator value to include in a frequency domain resource allocation field for the first bandwidth part; and communicating via the first bandwidth part based at least in part on the resource indicator value.

20. A user equipment (UE) for wireless communication, comprising: means for receiving first control information indicating a first control resource set associated with system information acquisition, the first control resource set having a first bandwidth; means for receiving second control information indicating a first bandwidth part, the first bandwidth part being configured with a second control resource set different than the first control resource set, wherein the first bandwidth part has a second bandwidth; means for determining, based at least in part on the first bandwidth part being configured with a different control resource set than the first control resource set, a resource indicator value to include in a frequency domain resource allocation field for the first bandwidth part; and means for communicating via the first bandwidth part based at least in part on the resource indicator value.

Images